Train signals control which track a train may enter. They are what keeps multi-train networks from deadlocking.
Why this matters
Without signals, trains crash or freeze and the whole network stops. Signals are the difference between one train and a real rail network.
Step-by-step
- Lay track with junctions where trains merge.
- Place block signals before every junction.
- Place path signals for route reservations.
- Set signals so only one train occupies a block.
- Test each train on its route alone first.
- Add trains one at a time to the network.
- Watch for signals facing the wrong way.
- Keep sidings for trains to wait on.
Tips
- Block signals on single track, path signals at junctions
- One train per block at a time
- Sidings prevent network-wide stalls
- Test one route before adding a second train
Practical notes
Signals divide track into blocks, and only one train may occupy a block at a time. Place block signals on single track and path signals at junctions, where routes have to be reserved. Test each route with one train before adding a second, because a deadlock is much easier to diagnose alone.
Keep sidings so a waiting train does not block the main line. Watch for signals facing the wrong way, which is the most common network freeze. Add trains one at a time and check the network after each addition, and the rail network scales without deadlock.
Watch for signals facing the wrong way, the most common network freeze.
Add trains one at a time and check the network after each addition.
Common mistakes
- No signals at junctions
- Signals facing the wrong direction
- Two trains reserved for one block
- Testing a whole network at once