Vectron Service no 53218 starts at 10:13am but there is red signal from start as the OBB 4042 is stuck at next signal. It doesn't move at all. I even tried to delete the train using Free Roam feature. It crashes the game. And if i was successful in deleting the train and i get the green signal. The game crashes when i reach the next signal. The OBB 4042 jumps the signal and stuck at it. Platform:- PC Steam
From Bludenz towards Lindau there are at least two freight services that present the same problem. Maybe we can bypass the problem by spawning by foot 5 minutes before that service starts.
Good morning everyone, thank you for letting us know, I just checked and this issue is known and logged. But I will update that spawning on foot works as a temporary workaround. All the best, Jan
Deleting the stuck train worked for me (no crashes), but you then get a completely clear run instead of being balked by a stopping passenger train in front. I'll try spawning on foot as suggested by Jan.
This issue has been seen on multiple routes, GWE had one if I remember correctly where the HST service you spawn into from the timetable gets blocked outside Paddington by a Class 166 on some points right at the end of the run, but worked perfectly fine if you spawned on foot and took the service over at Reading.
I think it's got to do with the datatrack, which as I understand automatically generates snapshots of where each train is supposed to be on a given time. It seems, if some of these snapshots are generated when a train is crossing a signal you get these effects, the same can happen when saving a game at the wrong moment. This is the reason Zusi has the F4 function, the timetable is calculated in realtime from its starting time till your spawning time and does not use a data track (which speeds up loading a timetable though, whereas you'll have to wait in Zusi if you load a timetable starting at 4am and you select a train starting at 1pm for example, as the whole timetable is simulated in fast forward until then.)