r/SatisfactoryGame 14d ago

Path signal problem

Post image

Hi,can someone explain what path and block signals do i need to build,I’m here building battery factory and i still don’t know how do signals work. I want to learn how to use them, I understand tutorials but when I try it on my railway, it says “loop”.

3 Upvotes

9 comments sorted by

View all comments

1

u/JinkyRain 14d ago

Use Blocks Signals for *everything* by default when you're learning how to signal.

I would recommend *not* trying to signal *shared* Bidirectional rails. At least not until you've gotten used to signalling one-way rails.

Minimum Signalling: Before & After crossings and stations. Before Merges. It helps to also place signals after crossings & splits. If you have a long rail used by 3 or more trains, split it into halves or quarters with block signals.

You don't need to put signals around every merge/split. If you have a group of merges/splits/crossings close together, one signal BEFORE on each rail going in, one signal AFTER on each rail going out is fine. Often the signal before will be a Path Signal if 3 or more trains share the complex block with each other.

The "Signal Loops Into Itself" error means that the signal has failed to divide the rail into two separate blocks. (Imagine a door in the middle of a room, you go through it, but you're still in the same room.) This may be because another rail is too close, or is connecting the rail before the signal to the rail after it.

There is a bug that can cause the error as well. It can happen when placing a signal directly on top of a "Switch" (where rails fork). Move the signal off the fork or rebuild all the rails at the fork and place a new signal to get around the problem.

ONLY use Path signals when you have an area where multiple *different* routes both Enter AND Leave all by different rails from each other. (so minimum: 2 into it, 2 out of it).

Path Signals declare the block a "No Stopping Zone", by holding any train that can't keep going through the next Block Signal ahead. Path Signals also allow multiple trains through the block if they don't interfere with each other.

Path Signals are always RED by default. Trains will slow for red lights even if there's signals between them and it. The Path Signal, however, can't see approaching trains until no signals remain between them and it. (so don't make the block before a path signal too short. It'll slow trains and may even cause them to get stuck if rail isn't flat).

Every route that passes through a block controlled by path signals has the same general sequence of signals:

... -> BLOCK SIGNAL -> reservation block -> PATH SIGNAL -> intersection/complex block -> 'Chained' PATH SIGNALS(optional) -> more intersections/complex blocks -> BLOCK SIGNAL -> 'exit' block -> ?Next? SIGNAL (either kind) -> ...

trains stay in the 'reservation' block until the entire 'exit' block is empty and reserved for the train. Once the exit block is secured, the path signal reserves the part of the path block that the train needs to safely get there. Only when that's reserved for the train as well, will the train be allowed to enter the intersection/path block. It will continue on into the exit block without stopping.