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
As Jack said - Path at every entrance - block at every exit.
Generally you only need a path if you have a complex/multi route intersection - many get along fine with only blocks.
I had chit-chat with Chatgpt and i think i get it. So Path signal is just "go/stop signal, no "search for aviable path", as i expected by name "Path signal". As i understand it, "outer ring" will not be used in this example, but can be used, when entrace / exit will be in less than 180° angle.
Anyway thx for reply.
Block blocks only allow one train in them. Easy to understand.
Path blocks have the following rules:
* Any time a self-driving train enters the block BEFORE a path block, it requests a path through the path block from the signal that it's approaching.
* The TRAIN selects the path it wants to follow and requests that path from the signal
* If the path block doesn't have any paths already reserved, or if the existing paths do not intersect the path that was requested, then the signal will turn green and reserve that path. Now the train has exclusive access to that path and any intersecting paths until it goes through.
* If the requested path does intersect an already-reserved path then the signal stays red, the train will stop at the signal, and it will wait until the requested path is the oldest one or none of the older ones intersect with it.
* If no self-driving train is in the block before the path signal, it will stay red no matter what.
* In order for a path to be "clear", the next block after the path block must be clear for the train to enter it.
* When a path is reserved, the next block that the train will be moving into will also be reserved by that and other trains will be prevented from entering it as if it were already occupied.
Those rules create lots of complex emergent behavior that isn't necessarily obvious, but those are the rules. Also they combine with the rules trains follow for example the way they brake in anticipation of a red signal in ways that might be undesirable.
So the end result is usually that if you have COMPLEX intersections you want path signals on the inbound tracks and path signals on the outbound tracks. And basically any other situation you just should use block signals.
Build one train for one track, then you dont need signals. Then just add as many waggons to that train as you need. A single train will never be the bottleneck, no matter how long the train route is, it will always be the belts.
Unless you're a train enthusiast:
Then go for signals and crossings and all kind of complicate scenarios you enjoy while others get nightmares about it
https://ibb.co/Xrg34dpS
Okay, ill try. (Im now at work). Thx for tip ;)
keep in mind trains allways use the shortest way unless there blocked