Wait Until Rule

oldfruit · May 3, 2020

On 2009 there was a driver rule Wait Until.
This enabled you to tell a consist to wait and you could put in a time in hours and minutes before it would move off.
It was a great way to run to a timetable.
On 2019 DS I can’t locate it.
Anyone know where I can find it.
Thanks in advance

pware · May 3, 2020

There are some possible candidates.

Wait Rule which is built-in to TRS19 so you won't find it on the DLS - see details at http://online.ts2009.com/mediaWiki/index.php/Session_Rule_List_with_Parameters#Wait_Rule

Time Check Rule likewise also built-in to TRS19 - details at http://online.ts2009.com/mediaWiki/index.php/Session_Rule_List_with_Parameters#Timecheck_Rule

WaitFor Driver Command also built-n - details at http://online.ts2009.com/mediaWiki/index.php/Driver_Commands_List#WaitFor

and additional related driver commands WaitForTrigger, WaitUntil, WaitRandom can also be found at the above link.

llebrez · May 3, 2020

On my TRS19 I have a built-in Kuid2:4009:900005:1 named WaitUntil. It works, but on T:ANE, after saving the session, sometimes it lost the setting and the train would continue running ignoring the setting.

pware · May 3, 2020

Some of the Driver Commands that use a "Wait" function, "WaitForTrigger" is one that has been mentioned, seem to have a bug that may be related to the number of drivers operating in a session. The more drivers you have the more likely these commands will fail. A variety of reasons have been proposed, such as script problems or time outs while checking all the drivers.

If you do have a large number of drivers then one workaround that seemed to work in TANE is to split your drivers between two separate Driver Setup Rules with a short time delay (e.g. 1 or 2 seconds) between the two rules. The Trainz Wiki page at http://online.ts2009.com/mediaWiki/index.php/How_to_Use_Driver_Setup_Rule gives an example.

llebrez · May 3, 2020

pware said:
Some of the Driver Commands that use a "Wait" function, "WaitForTrigger" is one that has been mentioned, seem to have a bug that may be related to the number of drivers operating in a session. The more drivers you have the more likely these commands will fail. A variety of reasons have been proposed, such as script problems or time outs while checking all the drivers.

If you do have a large number of drivers then one workaround that seemed to work in TANE is to split your drivers between two separate Driver Setup Rules with a short time delay (e.g. 1 or 2 seconds) between the two rules. The Trainz Wiki page at http://online.ts2009.com/mediaWiki/index.php/How_to_Use_Driver_Setup_Rule gives an example.

I have a gazillion number of locos. Wait for trigger does not work. But WaitUntil does. I realize that these rules are very different. Even doing the trick at the Driver Set-up, does not help on Wait For Trigger. However, using rules with check trigger and child ones, accomplishes the same, so I don't have to use the "Wait For trigger". End result: I can live with it.

p-dehnert · May 3, 2020

The following driver commands are on the DLS
<kuid:32711:100025> Wait Until II
<kuid2:41009:900005:1> WaitUntil
<kuid:178892:80002> Wait Until Hour
<kuid2:178892:80003:1> Wait Until Minute

Peter

Wait Until Rule

oldfruit

Oldfruit

pware

Trainz Veteran

llebrez

Active member

pware

Trainz Veteran

llebrez

Active member

p-dehnert

Well-known member

Similar threads