Wait for > ...?

[Midland]

The Wait for... command is very useful but there seem to be some oddities with it.

For example if a session starts at 10:00 and I want to have a train start at 10:23 I can select

Wait for...
10 minutes

Wait for...
10 minutes

Wait for...
2 minutes

Wait for...
1 minute

Then give it its movement commands (Drive via trackmark XXX).

Yet I've noticed when I'm in Driver that instead of starting at 10:23 the train may actually start quite a bit later than that.

Why is that?

It makes precise control of AI movements almost impossible.

Is there any way round this?





Cheers

Nix

[cathouse]

Perhaps the drivers get of bed late :hehe: :hehe: :hehe:

cheers
Roy

[Capt_Haddock]

Nix
The same might apply to all timed events. I’m working on a session that uses Pguy’s excellent “Portal Timetable” rule. The consists never emerge at the exact time specified; maybe this is just the time that A1 starts to think about the command in question. Also there does appear to be a slight randomness built into the system, otherwise why would sessions work perfectly for weeks then go pear-shaped when Alistair and his friends suddenly decide to interpret the rules differently.

Your four lots of “Wait For..” could easily accumulate an error, specially if
A1 has to some processing to do between each one.

There was a thread about timetables in the autumn, can’t remember the exact details but I think one conclusion was that it is difficult to achieve accurate timetable running without using Portals to emit the trains.

Regards

Chris