by torfmeister » Fri Jun 23, 2023 1:46 am
I'll go hunting.
I've already discovered in the past, that some of G-TraX's blueprints were manually copy-pasted and sometimes an ID was given twice - which can lead to a crash. Seems the new core is much stricter now in terms of blueprint structure (can only speculate as I don't have access to the RW source code obviously)
So the search process has two branches: Assets and Route. I can only check assets.
A thing to rule out first would be rolling stock isses - create a new freeroam from scratch without adding any stock and press play - if it works, we can concentrate on the stock (I had already found a typo in the ES44 InputMapper a few years ago). EDIT: Scenario crashes regardless of stock placed, just tested.
Next thing would be to unserz all assets using SerzMaster.
For checking duplicate IDs, which is a hell of work doing manually, I'd need a script wizard who could come up with a PowerShell script, reading each .xml in a specified folder, storing each "ID" tag value and notifying when a duplicate ID is found in the same blueprint. Anyone here who is skilled in scripting?
What I am doing now is installing the version before the route was patched on June 22nd, 2022.
(You can do it yourself: Press Win+R, enter "steam://open/console". Now enter the following:
download_depot 24010 1055338 5233909651527126064
This will download the route in the state of December 2019 in Steam\steamapps\content\app_24010\depot_1055338.)
OK, the 2019 HiLine also crashes. Hmmm. At least we can now rule the route update out as cause of the crash.
I'll take a different approach - first the route folder. Renaming Terrain to Terrain.bak - do this with each folder and check if route doesn't crash. Repeat this with Assets if nothing found, renaming each subfolder to pinpoint the folder where the cause lies.