System.NullReferenceException at ORTS.AITrain.UpdateFollowingState (SLI BNSF Seligman 2, Headin to Phoenix)

[Edward Keenan]

I am currently using V2189 and tested as far back as V2180. There was an immediate crash that took place at the start of the activity. This is the first experiencing this issue since I can run a different activity under the same route and not crash so its possible this may be activity related. The route is "SLI's BNSF Seligman 2" and the activity is "Headin to Phoenix". Log file is included.

Edward K.

[r.roeterdink (r-roeterdink)]

The crash is indeed related to the activity.
From the info on the crash, it seems to me that an AI train is routed through a permissive signal unto a track allready occupied by a static train, and this happens before the activity is actually started.
Surprisingly, it is the first time I have come accross such a situation in the two-and-a-bit years I'm now working on OR.
So there is always a chance for something new ...

I've made a patch but cannot commit at the moment due to other ongoing work which will take a couple of days to complete.
WIll let you know when the patch is committed.

[jeroenp (j-paasschens)]

Dear Rob,
Just for completeness, I did find, just now, the same issue in a completely other route (Bernina pass, running X2186). I am attaching the log to make it perhaps easier to debug (if not already solved by your patch). Also, probably it is not that uncommon, or something changed recently such that this now pops up.
In the debugger, I found that the 'OtherTrain' is not an AITrain, but a regular Train. Does this include static trains? Or is this the player train that is mistakingly already present?
Best regards. Jeroen.