[0.17.66] Rails: chain signal opens on occupied rail
Posted: Sun Sep 01, 2019 11:46 am
I'm not sure if this was reported or not; there are some signal related bugs open, maybe this is a side effect of another bug. So before I make a bigger, complete issue with save etc. I show just the screenshoots and a small explanation:
This is the situation. From player position the rail number 2 there is a train, that blocks the whole connection. But - as you might also see, when you think of this picture logically - this train can never allowed to be there, cause the signal that allows him to enter was red, cause the train before just occupied the entry signal, like on track 3, 4 and 5.
Here is the same situation as map-view with debug signals.
I saw this error now the first time, which wonders me, as this construction now works really near perfection since V0.16. So what has changed is the Factorio version.
And I can also explain how this happened 20 seconds before:
On the right side there are the 3 entry rails. The rightmost was occupied with the train which now blocks, but from the center rail a train drove into track number 3, which was at that time not occupied. In the moment when that train stopped, the rightmost train starts driving into track number 2. But the entry-signal for track 2 was still red! I saw this exactly, cause I was looking at this moment onto the map with this debug view open.
So what I saw was in end-effect, that a train, that drives through an allowed chain-signal-passage, that this train opens the path for another train into a blocked signal-path.
As said, I've the save etc. If you need more explanation just PM me.
PS: Maybe it's something with the very close to the end-of-train signals (the red signals track #3, #4, #5, where the orange chunk-border goes through)? This is done to enable entering faster into the waiting-area; immediatley when the train before moves, the next train can follow.
This is the situation. From player position the rail number 2 there is a train, that blocks the whole connection. But - as you might also see, when you think of this picture logically - this train can never allowed to be there, cause the signal that allows him to enter was red, cause the train before just occupied the entry signal, like on track 3, 4 and 5.
Here is the same situation as map-view with debug signals.
I saw this error now the first time, which wonders me, as this construction now works really near perfection since V0.16. So what has changed is the Factorio version.
And I can also explain how this happened 20 seconds before:
On the right side there are the 3 entry rails. The rightmost was occupied with the train which now blocks, but from the center rail a train drove into track number 3, which was at that time not occupied. In the moment when that train stopped, the rightmost train starts driving into track number 2. But the entry-signal for track 2 was still red! I saw this exactly, cause I was looking at this moment onto the map with this debug view open.
So what I saw was in end-effect, that a train, that drives through an allowed chain-signal-passage, that this train opens the path for another train into a blocked signal-path.
As said, I've the save etc. If you need more explanation just PM me.
PS: Maybe it's something with the very close to the end-of-train signals (the red signals track #3, #4, #5, where the orange chunk-border goes through)? This is done to enable entering faster into the waiting-area; immediatley when the train before moves, the next train can follow.