Networks / Field manual

Signals & train pathing

TF3 uses path-based signaling, with improved reservation behavior and route priorities.

Official systemsChecked September 8, 2026Pre-release guide

Passenger trains meeting on forest tracks · Official pre-release image ↗

The confirmed picture

What we know

The Highlights blog describes trains reserving paths through switches rather than treating every crossing as wholly occupied.^↗

Infrastructure priorities affect which waiting service receives preference.^↗

Higher priority can extend reservation distance; no numerical range is published here.^↗

Operations schematicConceptual

Before changing a signal

Intended routeCorrect destination?

ReservationConflicting movement?

Receiving terminalPrimary or alternative?

Exit pathSpace to continue?

Conceptual inspection flow for the official path-based signaling system.

From information to action

How to approach the decision

Editorial planning advice based on the confirmed systems above.

Inspect the reserved path and the train’s destination before changing signals.
Check whether the receiving platform or exit is occupied.
Use a small controlled network to verify the behavior in the launch build.

What changed in reservation behavior?

The Highlights dev blog explains that a train can reserve beyond its next stop, continuing toward a stop where it can reverse or the next signal. Configured alternative terminals may be considered when the primary terminal’s path cannot be reserved.

Path-based signaling itself is not presented as entirely new to the series. The change is the reservation behavior and supporting controls. Confirm placement and passing behavior in a small launch-build test before applying a layout across the map.

Operations schematicConceptual

Two services, one shared junction

Passenger serviceObserve waiting

Freight serviceCheck deadlines

Shared reservationPriority affects preference

Clear destinationPhysical space still matters

Priority changes preference. It does not create extra track capacity.

A mistake to avoid

More signals cannot solve a route that has nowhere free to exit.

Verify at launch

What still needs live data

Signal placement limits, exact reservation rules and verified deadlock solutions.

We will update this guide before opening individual database records. Unverified shells are excluded from search and the sitemap.

Put it to work

station throughput

Use your own scenario values. No guessed TF3 presets.

Open tool

Official sources

Highlights dev blog Infrastructure dev blog

Last editorial review: September 8, 2026. Evidence policy and source ledger.