Wait Until Problems

About a month ago, I posted a question about "Wait Until" not working, and putting my trains on permanent hold. Nobody else seemed to have the same problem. I have since figured out when the problem occurs:

If a train is given a "wait until" command in a session, it will work fine while that same session is running, and TrainZ has not been turned off. The problem occurs when a train is given a "wait until" command that happens after TrainZ is turned off, then returned to. For example, it is 5:30 am and an AI train has a command of "wait until 8:30 am". If TrainZ is not turned off for at least three hours, the command will work fine. If I quit TrainZ after one hour, then come back a day later and continue, then the AI train will be on permanent hold, even after the time reaches 8:30 am.

This problem makes the "wait until" command useless for me. I always run the Never-ending session, and continue from where I left off the last time.

Dean
 
Would be nice if this was addressed as it would make timetabling a lil easier and possible. The wait until can be used quite well to get trains to stick to a timetable but once closing program that's it, gone. i've had 1 train working an 8 hour shift for 3 days doing same thing each day, was gonna do it for other 20 odd passenger trains to run different 8 hour shifts to resemble a timetable of several lines etc, but once closing program all goes to ........ Timetabling seems doable as long as you don't shutdown using 'wait until' at a trackmark.

garry
 
Back
Top