[0.15.10] Train signals not reconnecting to replaced rails

[lovely_santa]

As in 0.14 I sometimes rip up a rail (don't ask me why) and then replace it, and everything works fine.

On 0.15.10 I did it, and whatever I do, the signals seems to reconnect (not flasing green, yellow, red anymore), but they keep standing on red, whatever it should be.

An example below:

Step 1 : functional rail

2017-05-13_192455.png (332.09 KiB) Viewed 1759 times

On the picture above you see my chain signal for comming out of the station. It's connected to the curved rail.

Step 2 : remove the rail

2017-05-13_192508.png (166.1 KiB) Viewed 1759 times

Here I removed the curved rail where the chain signal was connected too, as you see, the chain signal starts blinking (on a picture you can't see that obvious)

Step 3 : Replace the rail

2017-05-13_192525.png (396.27 KiB) Viewed 1759 times

And last, I replace the rail, and the signal is red, as it was green before in the first picture. When I replace the chain signal, it's green again.

NOTE: Same problem occure with rail signals

This isn't a big problem for 1 rail, but I had this problem too when I was placing blueprints with bots, so when the bots place the signals first (as simple example, when you run out of rails) and place the rail aftherward, the signal is red too... And obviously the trains get stuck on it.

I included my save file too, not that you will have any interesting with it as this is a fairly new world...

Greetings,
Lovely Santa

[jonatkins]

I've seen the same issue. Happens with both regular signals and chain signals. Only seems to happen when you remove+replace a pirce of rail that the signal is actually on - replacing bits further ahead seems fine.

[jonatkins]

Oh, and to add, you don't even need to remove a rail that would put the signal in an invalid (flashing red/yellow/green) state - just removing the highlighted rail in this example will change the signal next to the player to red, and it will stay that way until removed + replaced.

factorio=stuck-signal.jpg (209.42 KiB) Viewed 1728 times

[Rseding91]

Thanks for the report. This is fixed for the next version of 0.15.