Train Signal Help

[stevedave09]

I have watched videos and read articles but I'am still having issues getting the train signals to work properly. I know I'm doing something wrong but I cannot figure it out.
I have a small loop system and i just want to be able to run multiple trains on it to pick up and drop off at different places. Do I need to put signals all the way around and certain intervals? They have to be around the whole loop correct? I have been getting very frustrated trying to figure out my issue.
Any help is appreciated.
Thanks!

[Kage Goomba]

Blocks reserve "blocks" (think city block) of track - just like the description on the signal says.

If Train#1 passes a block - that block is locked out from Train #2 that's following until its cleared.

Pathing signals "Reserve" a path for a given train to prevent a subsequent train from taking said path - again - just like the description says.

So if Train #1 comes across a path signal - the route it chooses becomes "locked" and Train #2 is denied access until the path is freed up - don't confuse this with a block signal however.

You generally can do most things and get away with just block signals - path signals generally are only employed if your using switch rails/intersections.

Pretty straight forward.

If you have just a single rail loop - block signals every so often would be suggested - basically you place a block where you have enough space to let a train through and the one following park until the following block is clear.

If that makes sense.

[Porked!]

Yeah just chop up the track into blocks if you want more trains into a single loop. Path signal is only used at the start of track split for me.

[Hashy1000]

At the very least you will need signals at the end of each station. this makes the station a block and the track in between the stations a block. Only 1 train can occupy block at once . so with 2 stations on a loop with only signals at the station you could have 3 trains max as you have 4 blocks in total. 3 blocks are occupied by trains leaving 1 block for the lead train to move in to . more blocks means you can fit more trains on the same section of track.

As a rule of thumb a block should be the length of the train.

a Path signal literally reads the next signal down the line. ie putting a path signal before a junction means the train doesn't enter a junction unless it can pass all the way through it.

for a fully optimised track the block after a junction should always be larger than the length of the train, and try to plan your tracks not to have junctions closer than the length of the longest train. this will eliminate any gridlock.

side note you can place multiple path signals before a block signal.

This game doesn't do signalling amazing well, but its good enough to make complicated networks.

if you want a train to travel in both directions on a piece of rail the you need signals next to each other in both directions otherwise a train will never go through a signal in the wrong direction . alternatively watch a tutorial from another game with trains like factorio, voxel tycoon or sweet transit, they probably explain things better

[stevedave09]

My other issue I forgot to ask, what way do you point the arrow?
If I'm at the end of the station do I point the arrow into or out of the station?

[Hashy1000]

The direction of travel for the train, is the arrow. points to station on way in, points away on way out

[Kage Goomba]

Originally posted by stevedave09:

My other issue I forgot to ask, what way do you point the arrow?
If I'm at the end of the station do I point the arrow into or out of the station?

Arrow on the station is the direction of the train.
If it helps - the Sign hanging off the station is the nose of the train when it stops - basically.

[Bobucles]

the station is a D shape on top. Point the D in the direction of travel like
====D

[Ultimoron]

if you only work with block signals its pretty much straight forward and you can see color-coding on the rails if you are are building signal...

most of my signal related problem involve path signal....
sadly the game doe snot comunicate well when tehre is a problem with path signals... :(

an error, readable on the conclicted signal - of what ever reasing is causing an issue - would be so much better ...

[The Big Brzezinski]

Path Signal: "Brother, may I have some track?"

Block Signal: "No."

Path Signal: "Brother, I am overdue."

Basically, you need block signals wherever track sections meet by default. Trains don't like to share if they don't have to on account of their tendency to knock each other over when they collide. Block signals help make sure only one train is in any give block of track at a time, preventing this problem.

At the entrance to intersections, you use a path signal instead. This allows a train to reserve just a path through the block instead of the whole block. If another train comes, and the path it wants doesn't intersect the first train's, it will enter the block as well since they won't get in each other's way. If its path does intersect, the second train will wait its turn.

For just a simple loop, block signals are plenty. Things will become more complicated if you add multiple platforms or expand the railroad in new directions, however.

[Eiko]

Originally posted by The Big Brzezinski:

Path Signal: "Brother, may I have some track?"

Block Signal: "No."

Path Signal: "Brother, I am overdue."

The train that approaches you is still 60 seconds away, brother. It is no fault of mine that the tall skinny one places us down too sparingly. My own trains need to proceed now, brother!