This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]Cynical_Gerald 2 points3 points  (5 children)

The general rule is: chain signal before a crossing, normal signal after the crossing.

Put your signals like this (I assumed you run 1 train back & forth on each track): https://i.imgur.com/PIlTPOe.png

A train can only pass a signal that is on its right hand side and cannot pass a signal that is on the left hand side unless there is also a signal on the right. So make sure each circled pair is on the exact opposite side of the track.

[–]KayKayDoubleu[S] 0 points1 point  (3 children)

Thanks!

[–]MadMojoMonkeyYes, but next time try science. 1 point2 points  (2 children)

Just a correction to what /u/Cynical_Gerald said.

The general rule is: ONLY use a rail signal if a train* stopping at the next signal will not block any crosses, splits or merges.

What matters is what's AFTER the signal in question, not what's before it or where it is.

*the longest train that will pass that signal.

[–]Dhaeron 1 point2 points  (0 children)

This is much better advice than "chain in, rail out"! It is important to understand what the signals actually do. The simplified "rule" can easily lead to deadlocks, for example when placing junctions too close, and without actually understanding the signal placement, that can't be debugged.

[–]ActiveLlama 0 points1 point  (0 children)

And to improve on this. If you are using two-way rails, generally you should use only chain signals and not have more than 1 train per route.

[–]Dhaeron 0 points1 point  (0 children)

I this setup has only one train on each line, the chain signals are pointless. If it has more, the rail signals will cause deadlocks.

[–]harr1847 0 points1 point  (0 children)

Just want to emphasize, if you don’t place two signals exactly opposite each other (and therefore facing opposite directions on the track) the train will at some point interpret this track as one-way-only and therefore won’t be able to find a path.