Content manager and TS12, a possible work around....

[n8phu]

It seems that the larger the database the more susceptible it is to the lockup....

Next time give this a try, it is the only thing that I have found that will keep you from having to do the dreaded database update.

1. Content Manager hangs up, you get the never ending blue circle of waiting.... close content manager or wait for the notification the program has stopped responding and then close it.

2. Immediately restart Content Manager and let it open normally.

3. Open the task Manager.

4. Close Content manager... you should get the yellow bar on the bottom saying "please wait, applying filter", but nothing happens.

5. In task manager, kill TADameon process.

6. Content manager will close, but a new instance of TADaemon will start up and run. Let it run and do not interfere with it. It will shut down by itself.

7. Restart Content Manager, it should open normally.

After a few of these incidents, I go ahead and do a database update myself. Best thing to do is start it before you go to bed.

I would ask that a few others try this and see if it helps them out....

 

[Swordfish]

Thank you very much!
Some days ago I had to make a EDR. After around 48 hours it was finished, with my several hundreds of GBs of content.

Regards
Swordfish

 

[bnsf50]

I've been shutting TADameon off for years with task mgr., ever since Auran wouldn't put an on off switch for TADameon in CMP way back in 06 like we asked them to. And I don't shut CMP down when I do it I just leave it running. :wave:

 

[deneban]

It seems that the larger the database the more susceptible it is to the lockup....

Next time give this a try, it is the only thing that I have found that will keep you from having to do the dreaded database update

Another approach is:

1. Make a copy of your userdata/assets.tdx before each trainz operating session that will affect the database (I do this anyway in case my custom Content Manager filters get wiped out).
2. Upon being subjected to a forced database update, cancel it immediately. It is safe to cancel if you do it immediately because the initial phase is only reading your files and didn't make any changes yet. Exit the program.
3. Restore your latest backup of assets.tdx
4. Restart and no forced database rebuild will intercede.

Such restoration should only be done if you are confident the database is in good condition and the forced repair was only the result of an improper final closure of the database.

Also if you make extensive downloads or content changes, exit the program and refresh the assets.tdx backup.