Problem asset crashes Trainz 22 HELP

[rwk]

A center stall for a TEH roundhouse is causing Trainz to quit. I can't delete it because when it appears in CMP Trainz just freezes then quits. How do I get rid of it or go back to a state before the problem occurred? I tested it on my other Trainz 22 SP6 by changing the data folder to the one from SP5 but I can't change it back because when I try to navigate to the data folder it quits. I might have to reinstall again, but how do I get data from the SP5 Trainz if it keeps quitting? I think I'm just going to have to reinstall a fresh copy and try to get any data off of the SP5 but it quits after so many seconds. I do have data on 2019 though that I might have to go back to and import into the new install of 22. JCitron, can you help me with this one? OK, I managed to delete the pesky file from SP5 and fixed the SP6 by pointing back to the right data folder. Maybe I'll consider upgrading the SP5 version at some point. That roundhouse stall seems to cause problems when I install it in SP5 but not in SP6.

 

[JCitron]

Reinstall SP5 if you have a copy of the download and run a database repair on that database.

Opening the SP5 database in SP6 will corrupt your SP5 database by corrupting the assets.tdx file unless you upgrade that to SP6.

 

[rwk]

Oops, I opened the SP5 database in SP6 already but managed to change it back. Now I have SP5 working again but those two roundhouse assets for Scratchy’s Horseshoe Curve route still cause SP5 to become unstable and quit if I install them. They work fine in a separate SP6 installation. I guess I could upgrade my SP5 to SP6 and that might fix things but I think there is no way to get SP5 back, it doesn’t seem to be available anymore in my Trainz. So if I upgrade my SP5, I’m stuck with SP6 with no way to roll back. Were any of those throttle and route draw problems fixed in SP6?

 

[rwk]

Ok, now I did it. I upgraded to SP6 on the SP5 and I reinstalled the problem asset and now it doesn't even give me a chance to delete it. It just quits before it even appears. I don't want to lose data. I want to copy data over to a fresh install where the problem asset doesn't cause Trainz to quit. But I can't copy data if Trainz just quits after several seconds. I guess I can copy data from 2019 and lose some progress, I did manage to copy two important routes yesterday by cdp from the SP5 but didn't import them into the other Trainz yet. I might just scrub the Trainz SP6 and delete it and use the other Trainz but it's a lower build than SP6, do I have to upgrade that one, too in order to move files over from the SP5 Trainz 22 which is now SP6 if I get that problem fixed? I think my SP5 install was corrupted. I don't know what to do to get data off of the Trainz 22 that I upgraded to SP6 because now it just quits several seconds after loading CMP. I can't run a DBR either because it quits, too after running a bit.

I deleted the assets.tdx files and now I was able to delete the problem asset again. I might just migrate stuff over to the other Trainz 22.

 

[JCitron]

Did you try reinstalling the assets? Reinstall them and submit them rather than revert to original. That should replace the corrupted ones. All the other assets in the cdp file, if they come that way because I don't remember, can be reverted to original.

 

[rwk]

Now it seems to be fixed, my SP5 is now SP6 and the other install is actually a build number below SP6, 131965. Sometimes asset files will error because of tzarc errors but usually if I delete them and redownload or reinstall them then the errors will go away. What is the difference between builds? My SP5 build was at a 129 something number but the latest SP5 is 131965, and now it's SP6 but the newer install is 131965 which is probably SP5. So far, the roundhouse asset doesn't seem to cause any problems like Trainz quitting.

 

[JCitron]

Now it seems to be fixed, my SP5 is now SP6 and the other install is actually a build number below SP6, 131965. Sometimes asset files will error because of tzarc errors but usually if I delete them and redownload or reinstall them then the errors will go away. What is the difference between builds? My SP5 build was at a 129 something number but the latest SP5 is 131965, and now it's SP6 but the newer install is 131965 which is probably SP5. So far, the roundhouse asset doesn't seem to cause any problems like Trainz quitting.

You have errors because there were content updates to reflect the changes in SP6. Check for updates for the content instead of deleting and downloading deleting assets is a last resort thing when all other methods fail.

SP6 updates, bug fixes, and changes:
https://forums.auran.com/threads/trainz-update-announcement-sp6.181861/

SP5 had a hotfix to take care of a performance issue related to the new tree system that caused track and other splines to load in chunks.

 

[rwk]

Now there is a problem with the Trainz that was updated to SP6 with more assets on it. When I try to launch into Surveyor it just goes to a black screen and I have to kill Trainz in task manager. I can get into CMP. The other more recent install which is build 131965 works ok. I think I'm just going to have to scrub the SP6 Trainz and move my data over to the other Trainz 22 by saving cdp's. I tried a DBR and it didn't help.

 

[JCitron]

Now there is a problem with the Trainz that was updated to SP6 with more assets on it. When I try to launch into Surveyor it just goes to a black screen and I have to kill Trainz in task manager. I can get into CMP. The other more recent install which is build 131965 works ok. I think I'm just going to have to scrub the SP6 Trainz and move my data over to the other Trainz 22 by saving cdp's. I tried a DBR and it didn't help.

Don't kill it! Don't ever kill the program without checking Task Manager first by pressing CTRL+SHIFT+ESC for disk activity. If you see disk activity, the program is busy.

What's happening is the program is caching content and validating your install. This process can take some time depending upon how much content you have.

You can see this process by clicking on the Developer menu located on the Launcher or on Content Manager, or by checking Task Manager ----> Performance ----> Hard disk where you need to choose the one where your content is installed if you have more than one drive.

Just an FYI... If you have nearly 2 TB of content, this process can take 26 hours on spinning rust. I left my computer alone and did other things while this was processing. The break was refreshing too and worth it. I may do that more often, not an EDBR, but taking longer breaks.

 

[rwk]

I didn't kill it during a DBR, I killed it when launching Surveyor and it went to a black screen and clicking the X did nothing. I have a newer install with the 131965 build that works ok so I'm going to use that version and move stuff over from the other Trainz that I upgraded to SP6 that isn't working right now. I can launch CMP though in the one that was upgraded to SP6 so I can get files off by cdp. Now I loaded the SP6 and it goes to the menu with the C&O steam locomotive in the background. I wonder what happened yesterday why it went to a black screen but now it works.

 

[JCitron]

I didn't kill it during a DBR, I killed it when launching Surveyor and it went to a black screen and clicking the X did nothing. I have a newer install with the 131965 build that works ok so I'm going to use that version and move stuff over from the other Trainz that I upgraded to SP6 that isn't working right now. I can launch CMP though in the one that was upgraded to SP6 so I can get files off by cdp. Now I loaded the SP6 and it goes to the menu with the C&O steam locomotive in the background. I wonder what happened yesterday why it went to a black screen but now it works.

Understood. When TRS22 first starts, it'll validate your content. The program is busy doing things and your hard disk utilization is at 100% which is why your screen was black. Once everything is done being validated and cached, everything will load quickly as you saw. By killing the program while it's doing this, you risk corrupting the database requiring a new EDR to run.