pjt1974 wrote:the dump does sound like a corrupted Route Properties.xml or a corrupted scenario properties.xml.
Even though we've been assured that nothing has been changed or edited that is now the likeliest cause of the issue.
bigmull...rather than spend weeks/months adding stuff piece-meal simply cut your 'now working' assets folder out of the game to somewhere safe and copy/paste your old assets folder in. Then test; if it works fine then the problem
must be in the routes.
If it doesn't work, then the assets folder holds a rogue so to double check delete that assets folder and copy/paste your 'now working' one back in and test agin, just to make sure that they still work.
As that will (confidence!!) repeat the testing but this time focus on the Contents folder.
If that works then it
must be in the assets..... get the idea?
Once you've determined which folder set the problem really lies in just add half of the routes or assets, depending on which set is the one being worked on, and test again.
If it works add half of the remaining half...test. If it works, add half of the remaining half of the second half..... binary progression; a very quick and easy way to narrow the search down to a particular chunk of folders. Once you've worked out which chunk, go through the process again within that chunk, to narrow it down further, eventually finding the culprit.
If you can remember editing a scenario/route, even just saving progress in a scenario/route is a
change, then that would give you a narrowed down list to start with.
