Track Gotchas, tricks and other interesting facts

Portal Junctions and Capacity

A train leaving a portal with the "act as junction" option on will not be stopped from entering the next section even though a look ahead condition at the other end of the section may be blocking the train.

This is because the train has already been allocated a token to the section leaving the junction portal so it doesn't need to check that section is clear.

The current track system doesn't support junctions with capacity (where a train could become blocked). The train needs to be blocked at the last location of "track" capacity (loop or portal). Track capacity is not model capacity when the junction option is used. Once it leaves the last location of capacity it assumes it has right of way untill the next location of track capacity.

Loop Exit Routines and Blocking

Loops do not run their exit routines on lookahead! If you want to do any lookahead logic that can cause a block its best to use the loop out gate or out decision to block the train in the loop

Loop Exit Routines and Exit Delays

If you use a loop out gate/out decision to block a train in a loop, then bear in mind that if a loop exit delay is being used, the loop's Exit Routine will not get called until the loop exit delay completes. This will allow other events between making the decision to leave and calling the exit routine - an issue if you are managing capacity.

Loops have an option "Exit Routine Before Exit Delay" which will cause the exit routine to be called at the time the decision to leave is made (when the exit delay starts) rather than when the exit delay ends.

idkbase note 310

---

idkbase note 310