Fatal Error What Does It Mean And How Can It Be Fixed? Details Inside

I got the following error trying to start the scenario [GP38-2] 07. UP Mission Bay Hauler from the Peninsula Coridor DLC. Accroding to steam there are people who were able to play this scenario because they got the achievement.

Exception info: Out of memory

Fatal error in mode LOAD_SCENARIO during update withtin DISPATCHER

I can't open this scenario from the builder either, i even tried to clone it and still doesn't open

 

Confirmed. It used to work before.

TrainSim-Steve can you fire that scenario up and have a look why it's not working any more? RailWorks64.exe v75.8a

 

Ran a quick test, it crashes in Beta, Standard 64bit and 32 bit. I am running borderless.
Tested 5 other scenarios without issue. Last few lines of Logmate:
\cTurnoutPattern.cpp : 211
2023/11/18 11:51:52.899 - [RunTimeError] - Assertion failed
2023/11/18 11:51:52.899 - [RunTimeError] -
2023/11/18 11:51:52.899 - [RunTimeError] - ASSERT(conn0Index == mainLineInRibbon || conn0Index == mainLineOutRibbon || conn0Index == turnOutRibbon);
2023/11/18 11:51:52.899 - [RunTimeError] -
2023/11/18 11:51:52.899 - [RunTimeErro

 

This is very concerning, I've also tried 32bit but we are having a different issue here. I've also cloned it, removed the scenario script, to no avail.

A dispatcher crash (never seen that before). I have tried running the scenario on v72.3b (pre core update build), it's running well there.

TSC v72.3b:

 

I wonder if the "Dispatcher Crash" is a new way of reporting errors to the user - instead of the standard out of memory

 

How can i roll back to a previous version?

 

It's at least telling you where exactly in the code the crash happens, instead of the old single-excuse-for-everything pseudo "OOM" message. Makes it easier to bugfix - Steve can be sure there's something in the dispatcher code that won't let this scenario run.

 

I've written a guide some months ago, how to install previous versions next to your main installation.
Currently I'm having a small v72.3b installation featuring only Ashford-Lille and Peninsula Corridor (No other routes have issues so far afaik - of course it may take some time and somebody might stumble over some new incompatibility like this one.)

https://forums.dovetailgames.com/th...ly-install-old-ts-versions-next-to-tsc.71041/

 

Great, thanks for the info and the work you put for the guide. I'm waiting now for the download to complete, feels like an eternity...

L.E. if this is a separate install achievements won't syncronize right?

 

It is just a file download you can put anywhere and will not be synchronized or monitored by Steam. All it does is check the "steam_appid.txt" in its folder on start, and checking for ownership, no matter where it's run from.

Achievements have nothing to do with it, they are tied to your Steam profile. You won't lose anything.

 

Now this is interesting. I'm rebuilding that scenario from scratch to see how far I can get.

I have created all three coupling instructions. Now creating a Go via over South San Francisco Track 2 to enter the mainline results in an instant editor crash in the dispatcher module.



TrainSim-Steve This might be interesting for debugging.

Using the same custom marker (Redwood Direct) - the routing is impossible under v75.8a. Compared timetable (opened with v72, and my remake under v75, player train only, no AI yet)



You can use this scenario for testing. Open it, and add a "Stop At" instruction @South San Francisco Track 2 and you can reproduce the crash. As soon as you select the destination (via map or listview) the editor quits out. EDIT: Moving the rakes back a little fixes the crash - but the routing is impossible.

 

I've managed to convince the dispatcher to run this scenario by removing the last car of the third string of cars. And adding a Test waypoint for the needed setback to access the mainline. (edit: not needed)



So my conclusion - somehow the consist got "too long" - maybe just an inch, I don't know. Some rounding errors / changes in the dispatcher code affecting marshalling in tight spaces?

 

Your efforts are higly apreciated but it doesn't look like someone from dtg is actually looking at this and the problems you've identified...

 

Thanks - it seems no one is there, and Steve used to reply to things...

DTG Jamie Why is there no response? Is TrainSim-Steve on leave? And why was this secret update pushed out without a warning?

 

I didn't get through it. I got the same thing. Spikee and you can make a quick fix, which will need to replace some file?

 

Yes, due to my findings I can make the changes to the scenario in v72.3b (move back the cars a little and delete one) and upload it as a patch, but first I really want DTG to look into this as a change in the dispatcher is likely to break other scenarios which have not yet been discovered.

The cause can be as little as changing from truncating to rounding numbers (which has been done to my knowledge for control value percentage display in the v74 update).

 

Just open the demo scenario I've submitted in post #11 with instructions, and you're right at the cause of the dispatcher crash! Add the instruction to the timetable to trigger the crash.

Logmate supplied by rwaday above, crash in TurnoutPattern.cpp

 

Four months have passed, the beta has been updated, but where is the fix? Can't play the scenario for 4 months, I paid money for the route, I didn't win it for free.

 

If the other scenarios are broke and unplayable you have a good complaint.
If its only one scenario then you will have to wait for a third party fix.

Broken scenarios have existed since the game was released
I bought the original Woodhead route and a scenario starts with an electric train on non electrified track