Orts.Viewer3D.Processes.ThreadHangException at Orts.Simulation.AIs.AI..ctor (1.3.1.4328, certain trains in Timetable Mode causes crash on startup)

[Greg Jaramillo]

I have been testing a new Timetable that I created using the timetable editor. There is 45 trains currently in the timetable. Some trains will load and run in the game error-free. Others, however cause the game to crash on startup.

[Kevin Bakina (tokenb98)]

Some wagons seem to be missing: "Warning: Ignored missing wagon C:\Program Files\Microsoft Games\Train Simulator\Trains\trainset\G-Rail_Trainset\G-Rail_245.wag in consist G-Rail 721, 1102"

maybe that might be causing the issue.

[Greg Jaramillo (coastergreg2104)]

I'll try fixing that, and see if it resolves the issue. Thanks!

[r.roeterdink (r-roeterdink)]

There's two problems here.
First, you have a lock in your timetable. The player train won't start because some other train is blocking the track. Probable reason is a 'lock-up', two or more trains are somehow waiting for one another.
Best way to try and sort this out is to start a 'dummy' train on a track which is not used at all, around the time of the intended player train start time.
Then, check both F5 dispatcher info and the dispatcher window to see if you can locate the trains which are stuck.
The second problem is that the start-up sequence takes such a long time that the watch-dog timer times out. This is what is actually causing the crash. That will probably sort itself out if the train can get started on time.
By the way, you need to clean up the signals on this route. There are many signal warnings and errors and this might cause problems with train control. That is often not so much a problem with activities but the for the more complex situation for timetables with more trains to handle this could cause problems.

Regards,
Rob Roeterdink