Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Path signals are chain signals. They don't work at all, their display is broken.
A block signal creates a block to another block signal. You use this to create areas where only one train can enter.
A path signals checks the path of the next block, if the path is clear then a train can go thru. path signals need a block signal on each track coming out of it if you have an intersection.
If the signal cannot make a block cause the track isnt connected properly, then they will flash with a yellow triangle.
Or if a path signal goes to another path signal, also doesnt work.
Path signals will by default show a stop sign, and will not update until a train enters the block before the path signal. This is intended behaviour.
OP: Usually when a signal is flashing it doesn't mean you need to delete that signal it means you need to add another one. If you're holding a signal hologram the game displays where it thinks the blocks are. If that doesn't match where you expected them to be you know where the problem is.
I'll have tracks and signals working, come back later and they're just messed up even though I didn't change a thing. It seems making any edits to the track anywhere on the map can mess with a previously laid intersection somewhere else. I haven't been able to recreate this on demand, but I've fought this issue often enough.
The trick I've learned over time is to pay attention the switching signals. Sometimes a switch signal will appear when there is no intersection; when that happens you have to delete that piece and place it again. Sometimes I'll create an intersection and either the switch is on the wrong side or one isn't created at all. Here again, it's delete one or more rails until all the switch signals appear correctly located.
Lastly, drive the engine yourself. Sometimes even though the track looks fine, the train will stop dead in its tracks or will start to spin on the spot as if the rail is turning 180 degrees in that instant. Here again, delete rails and try again.
You're not crazy, it's just a gremlin in the system that you have to watch out for.
you should watch a few signal tuts on youtube.. there are really good ones.
This is what happened to me. I went to my base at the Grassy Plains from the Rocky Desert and added a some new track, when I got back to Rocky Desert, everything was flashing and all of my trains were stopped. If it can detect a problem, maybe it should draw the path it's tracing and show me where the "loop" is. I've driven the paths many times and the only time I find an issue is where the track wasn't connected correctly.
I also find the way it does signals, is that once you place one, you've pretty much committed to keep adding them. Add one, and now everything on the other side of it stops the train. In Transport Fever, you have an in and an out. After the out, you've completed the signal.
1. You can't mix and match path vs block signals for intersections for any particular direction. Use all path, or all block, can't be mix of both. What this means -->
ex) T-junction intersection with three tracks in, three tracks out.
a) Path signal for each of 3 tracks in, Block signals for each corresponding track out
b) Block signal for each of 3 tracks in, Block signals for each corresponding track out
c) Error - Mix of 2 Path signals in, 1 Block signal in, 3 Block signals out. You'll get blinking signal because game doesn't like mix of logic for any color rail. The T-junction can have all Path in, or none. If you use 1 Path, then every entrance into that junction must also be Path.
The signal is red when the path is open.
The signal is red when the path is closed.
In what world is this considered "fine"?
I think b is my issue. I also think it's easy to accidentally forget to place an exit signal so when you have an odd number of signals, it can be hard to figure out where the odd one is.
I love how everyone ignores you, they work just fine. You simply dont use them correctly.
Then it needs a better tutorial, or if it knows there is something wrong, show us where it is. "Loops into itself" isn't very helpful on more complex rail networks. If it's trying to calculate a path, then it can show me where it stopped working.
Right now, I have no other signals on my network, yet, when I place two block signals, one of them is flashing yellow and telling me its looping in on itself.