Wait Until

[terry_wagstaff]

Hi all

Any assistance would be appreciated.

In the first release of TANE (and earlier Trainz versions) I used the 'Wait Until' driver command in my sessions so that the AI trains ran to a time.

I now find that the AI train ignores the command and just ploughs on to the next command. Is there a work around or alternative command?

Thanks

Terry

 

[peterwhite]

I use 'Waituntill11'. That works perfectly.

 

[terry_wagstaff]

I have tried that as well, it does not seem to work under TANE SP2 HF1

 

[peterwhite]

It worked for me in TANE SP2 HF1 but was not very accurate, but in the Beta build 90716 it is absolutely accurate.

 

[clam1952]

I have tried that as well, it does not seem to work under TANE SP2 HF1

Wait for works in the current HF1 beta.

 

[Dap]

FYI - the two wait until commands:

<kuid:32711:100025> Wait Until II will show the time set to wait for when you run your mouse over the command.
<kuid2:41009:900005:1> WaitUntil Haven't tested it lately, but it never used to do it. (That's why I created Wait Until II)


David

 

[llebrez]

I found "wait until" to work quite well. Now save the route and the time to wait disappears and you have to set it again: Maybe a gremlin of TANE?. On the subject of "wait", since you know about this things, is it possible to make a proper "wait for trigger" ? The one available now is very unreliable and I have never been able to make it to work, or slows down very substantially the commands selector of the driver menu.

 

[trev999]

No, the gremlin is in WaitUntil. Wait Until II fixes it.

WaitForTrigger tries to list all the triggers found in the map and session. A route such as ECLM contains thousands of triggers used for the AWS system. The TANE timeout limit steps in and prevents the command from completing the menu.

The command needs a filter mechanism to ignore triggers names that start with Trigger. Then you, the user, would need to ensure that any triggers that should be listed have another naming scheme.

Trevor

 

[llebrez]

Out of frustration, I am starting to use a signal controlled by another consist on another track. This way, there is no need to use the wait for trigger. Consist waiting is held by a signal, and will proceed only when the signal would go green, triggered by the other consist. It works for me. Anyhow, thanks for the clarification above.