Certain simulations can be chained together.

When chained, the simulations will run at the same speed, and trains leaving one area will appear in the adjacent area. Each simulation must have one server, but may have a number of clients as with a multiplayer simulation.

One simulation is designated as the Master, and its clock controls all the other simulations; if this simulation is paused, all the other 'Slave' simulations will also pause.

Each server is set up in the normal way from a multiplayer host. However, if more than one server is using the same connection/computer, each will need to use a different port number (to enable data to be routed to correct simulation server).

The required set-up sequence is different according to the age of the simulation:

Older Versions (Didcot paged, Liverpool Street, North London Line, Swindon paged, and Westbury paged)
Each simulation is set up by using the Network Play/Chained option, entering the required IP addresses and then following the New Game/Load game as with a normal single multiplayer simulation (if that makes sense!).

Newer versions (other simulations)
The servers are started up separately as for normal multiplayer games. Once established, the 'Slave' servers connect to the 'Master' server via 'Multiplayer/Connect to External Signalbox', and entering the appropriate information, and ticking the Synchronise time box.
Note that some simulations connect 3 ways eg Bristol - Exeter, Bristol - Westbury, Westbury - Exeter. Each of the 3 connections has to be individually linked, but with only 1 master clock (Bristol is recommended in this example!)

Simulations that can chain together are:

King's Cross - Cambridge - Peterborough - (North London Line*) *see next section : Also Royston will chain with King's Cross instead of Cambridge

Bristol - Exeter - Westbury - Gloucester - Swindon&Didcot : Western Chain Map

Sheffield - Trent - TBA

Edinburgh - Central Scotland - {North East Scotland, when issued}

S Humberside - Worksop - (Sheffield - when revised)

Brighton - Lancing (Lancing using this timetable)

Note that compatible Timetables are required for each simulation; if trains leaving one area are not in the timetable of the next area, they will simply runaway with no timetable allocated.

*Currently there are no NLL timetables suitable to chain with KX

Note that while Exeter and Westbury are both slaves to Bristol, they also need to be chained together to allow trains to run between them. This connection can be done from either box, but the Synch Time box is NOT ticked.

This page was created on the old website by AndyG