Someone kidnaps drivers after resuming save?

[sniper297]

Not sure if this is global or specific to one version, but I'm getting this in TS2010. Saved a session after 46 minutes, then resumed and drove for another 20-25 or so, found an AI freight train waiting at a red signal. Didn't see another train nearby that would be locking the switch ahead of him, but locked it was, couldn't throw it. Tried selecting the engine to bring him up in the driver menu - can't select the engine! Looking in the driver menu he wasn't listed there either. Further investigation found another train that also wasn't in the list.

Dunno how many AI trains are running at the same time, but there were 20 in the list, and apparently at least 2 that were not in the list. After the next following train passed him 15 minutes later I was able to throw the trailing point switch ahead of him to his track, and he proceeded to finish his schedule - assuming he had a schedule, he did eventually end up in the correct destination portal.

Anyway, he was clear of the portal that spawned him by at least 1 train length, but I noticed he was listed as "Consist 46" on the map - the other one not in the F6 driver list had a similar listing, this is the usual way they spawn with a "Consist" then a number until they're all the way out of the portal when they pick up the driver name. I suspect the problem is, don't save a game at a time when trains are due to spawn, try to allow a leeway five minutes either side.

 

[fran1]

You wouldn't be using portals would you ?
Sounds like you may have come out of driver while consist not fully emitted. AH I see you've sussed it.

 

[fran1]

If you can, set the portals to emit at the same time eg 30 mins.

 

[sniper297]

Yeah, now that I know about the glitch I'm trying to figure a way around it - problem is, the save itself resets everything to time zero. If I set AI trains to spawn from different portals at 10 and 20 minute intervals, you're perfectly safe with the first save at any time ending with 5 - 11:05, 11:15, 11:35, whatever won't catch a train coming out at 11:10, 11:30, 11:40, whatever. Except that if I save at 11:45, that becomes the new "Time Zero" for all portals - so after I resume the session at 11:45, the next set spawns at 11:55 instead of 11:50, 12:05 instead of 12:00, and so on. So the next save has to be on the 10s instead of the fives, and this one I discovered this in IS a save of a save, save at 00:33:53, resume from that, save again at 00:46:33, resuming from that causes the gripe. Amazing part is it don't wreck it completely, wait for a couple of faster trains to pass the stalled one, then throw the switches for it and it continues the secret schedule to the destination portal.

 

[sniper297]

Taking a diverge onto Surreal Siding now. Due to the other glitch where a session don't pick up KUID numbers off trains spawning from portals, I first placed one each consist somewhere near the corresponding spawning portal (10 total on the route), then deleted a dozen or so drivers from driver setup to keep the list from getting cluttered. Then before activating the portals I added one driver for the player start train.

Running the session now, with all the drivers removed those trains sitting in yards are listed as "consist 21" etc. on the map - yet I CAN click on any of them and drive them.