I've found CMP to be at the same time great and frustrating. For the most part it works as advertised and is a great boon to downloading/installing/removing assets and looking inside their config files - even modifying the configs. There are times when CMP freezes and can take as many as four or five reboots to get TRS and CMP properly working again.
I'm still studying this beast, but have discovered that if, after a few days of non-TRS use (I have it on several machines) CMP takes too long to update its database, I just shut down Trainz and restart it. Then CMP usually updates right away. I also find that if I try poking around in CMP while it is still in its updating mode, or otherwise not fully settled with itself, I can be in for a long cycle of reboots. I can, often, still import CDPs while the updating is going on - but not always. (I usually DL CDPs to file, so I can save and label them for future reinstallation. If a particular asset, such as a locomotive or a route has lots of dependencies, I just save the main asset and let CMP DL/install the rest. It does this very well.)
Al

I'm still studying this beast, but have discovered that if, after a few days of non-TRS use (I have it on several machines) CMP takes too long to update its database, I just shut down Trainz and restart it. Then CMP usually updates right away. I also find that if I try poking around in CMP while it is still in its updating mode, or otherwise not fully settled with itself, I can be in for a long cycle of reboots. I can, often, still import CDPs while the updating is going on - but not always. (I usually DL CDPs to file, so I can save and label them for future reinstallation. If a particular asset, such as a locomotive or a route has lots of dependencies, I just save the main asset and let CMP DL/install the rest. It does this very well.)
Al
