Changes

* ''At the switch'' where train can choose '''any''' tracks and should wait for '''the first available''' , if all of the tracks are occupied. Most common use is at multi-platform stations (as long as the exit lines from all the platforms lead to another common destination / node / switch, so train can use any available platform), at parallel tunnels (signals cannot be placed inside the tunnel, so longer tunnel becomes a bottleneck for the rail network. That could be mitigated by building parallel tunnel in the same direction, which doubles the number of trains traveling at once) or at any other parallel tracks built to increase the throughput of the network.

Using chain signal at switch is extremely important at the end station where there are bi-directional signals. Placing block signal here there would cause the train getting stuck nose-to-nose (see the image in bi-directional signals section above)

Even quite complex crossing can be managed successfully by correct use of correctly using both chain and block signals:

Of course, every crossing has a limit how many trains can go through before it gets overwhelmed. Crossings are good for low to moderate traffic, but for high traffic areas one way drive-through stations and interchange with bridges and tunnels should be used. <br><br>

* placing chain signal at the ''exit'' track of the crossing. There is absolutely no harm in doing so, but the train will needlessly wait for whole another block to be clear while it could have been moving already - it is harmless but very inefficient using use of the chain signals.