A newly-discovered feature is the schedule sequence. This is like a schedule, but instead of bringing up a list of blocks to visit, it brings up a list of complete sequences that will be executed instead.

The schedule sequence is needed where a given train route would go through the same block more than once. A schedule can't do that (other than by running the same sequence several times). So if I want a train to go on a long journey - for example from Portsmouth, round the railway 3 times then back - it can't done in a single schedule. What you can do is make up discrete schedules, then chain them together in a sequence. So my "long journey" can be:

Portsmouth to green fiddle yard ( a short run);

Green fiddle yard to green fiddle yard, twice;

Green fiddle yard to orange fiddle yard;

Orange fiddle yard to orange fiddle yard, twice;

Orange fiddle yard to Portsmouth.

That now takes several minutes with lots of activity!

 

Another possible benefit of sequences is to cut down the number of sequences required. Instead of lots of individual sequences, you can instead have sequences for all of the main "point to point" operations required then treat a train journey as a sequence of them.

1st Oct 2016 - we have discovered more about sequences. There are some things to remember: