the opening checking for faulty and deleted assets

[camawa]

Wondering if there is a way to dictate when the game does the faulty, deleted etc. checking of assets when you first go to open the game. Before the latest update it would take a couple of minutes to cycle through which is no big deal. After the latest update it takes 2+ hours for it to cycle through. Last night I just went to bed and after I got up it completed it at sometime. It was again 2+ hours into it when I went to bed. It says it has around 307,000 things to check and at times you can literally watch it go up 1 digit at a time. Any help would be greatly appreciated thank you.

 

[shaneturner12]

The simplest way of avoiding this is to wait after Trainz has closed for about 5 minutes before shutting your system down.

Shane

 

[JCitron]

Hi Cam,

"What dictates this" is something you can prevent actually, and yes you can carry out this process manually if you wish. Let me explain...

What dictates is database corruption or the program thinking things are corrupt occurs when Trainz TS12 is not shutdown properly. When TS12 has been shutdown unexpectedly or you've restarted your computer before the program has completed updating, TADDaemon, or the database server built-into Trainz, doesn't know the status of the files. So rather than just launching the program, and working with corrupt data, the TADDaemon will start verifying the data and checking the tables before it allows the program to start up. As you've found out, this process can take some time.

Shutting down improperly isn't always your fault because the program continues processing, closing files and shutting down files in the background, after the program closes its interface. The way around this verification process is to wait about 5 minutes after closing Trainz before turning off or restarting your computer.

To initiate the process manually, go into Content Manager and choose Quick Database Repair (QDR) from the File menu. If there are extensive problems, such as program crashing, you need to sometimes run an Extended Database Repair or EDR. This is a lot more extensive and the process can take forever. Due to some things caused by this process, this is recommended only as a last resort when nothing else fails.

Hope this helps.