
What a signal is waiting for
Urban Games' Highlights developer blog identifies TF3 signaling as path-based. A train can proceed when it can reserve its particular route ahead. Traffic on a separate, non-overlapping path is not the same conflict as a train blocking the path it needs.
The developer also describes reservations continuing beyond an intermediate stop. A station stop is therefore not a dependable substitute for a signal where you want trains to pass. The current manual's examples use signals to separate those reservations.
One paragraph in the manual still names Transport Fever 2. This guide uses the TF3 developer blog to establish TF3's path-based rule and the current manual for layout examples; it does not treat every legacy sentence as a newly tested TF3 claim.
A simple passing-loop layout
Consider two terminal stations joined by a shared single-track route with a two-track passing area. This is a conceptual example, not a tested blueprint.
- Draw both intended journeys first. Mark where each train can wait while the other uses the shared section.
- Keep the waiting area clear of the merge. A train stopped there should not have its tail across the track that the other train needs.
- Use signals to separate the outgoing reserved paths. The official manual's passing-siding example adds signals at the ends of the siding so both trains no longer try to reserve conflicting routes through to the opposite terminal.
- Inspect the assigned route before running both trains. Check the stops, selected terminals and direction restrictions.
- Observe both directions. If a train waits, identify the conflicting path rather than adding signals everywhere.
Size the clearance for the longest train you intend to use. No fixed spacing distance is prescribed here.
Direction matters
The manual distinguishes ordinary signals from the One-way setting. An ordinary signal facing away from a train is ignored; a one-way signal cannot be passed from its back side. Check that setting if a previously usable return journey becomes unreachable.
Before changing direction rules, inspect the actual line path. A visually connected second track does not mean the line is assigned to it.
Diagnose the stop before rebuilding
| Symptom | Useful check |
|---|---|
| Two trains cannot leave opposite stations | Look for overlapping reservations through the passing area. |
| A waiting train blocks a junction | Move the stopping position clear enough for the entire train. |
| A line becomes unreachable | Inspect track connection, terminal assignment and one-way restrictions. |
| A train queues outside an occupied platform | Check whether configured alternative terminals are reachable. |
| An express is delayed at a merge | Review line priority and the surrounding route; priority cannot make a physically blocked path free. |
The line manager reports connection problems on affected segments and terminals. Read those warnings before adjusting fleet size. For an intercity passenger service, also check the passenger journey; signaling solves track movement, not missing demand.
Sources and testing status
Checked October 5, 2026: Railway Signals manual, Lines and Vehicles manual, and Dev Blog — Highlights.
Watch the official Infrastructure overview. The watch link is the same corrected official video previously selected for this page. Instructions are based on documentation; no first-hand signal playtest is claimed.

