Factorio Forums

EDIT 2: Reliable vanilla reproduction below: viewtopic.php?f=29&t=43839#p253896


While working on a reproduction save for another bug report I somehow managed to get into this situation. I have no idea what triggered it but the setup is as follows:

Five rail signals are placed on a track right after each other. They are chained together with red wire and all have the close condition (medium pole = 0). The first one is somehow green, the rest are closed as expected.

Disconnecting it from the circuit network fixes it, changing the condition operator also fixes it, changing the condition signals does not seem to fix it. Changing the signal condition from (anything) to any other signal seems to fix it as well. Giving it a signal that should open the rail signal and then close it again will fix it.

Save attached. Used creative mode mod, but it should not be required for this part of the save to work.

Edit: They still react to trains as they should but it does not stay closed after the train leaves the block.

Can you reproduce it without using mods?

Not sure at the moment, the save loads fine without mods though, and the problem persists if that means anything.

I didn't notice right when it happened so I'm not sure what triggered it, I'll try to get a better reproduction, no promises though.

aaargha wrote:Not sure at the moment, the save loads fine without mods though, and the problem persists if that means anything.

I didn't notice right when it happened so I'm not sure what triggered it, I'll try to get a better reproduction, no promises though.

The question is, if it can get in the incorrect state without the mod, if not, then it's not a bug. I tried in vanilla and it worked flawlessly.

Found the cause using vanilla: Its that the leftmost signal was placed before the curved rail was placed.

To reproduce in this save:
Remove the leftmost rail piece on the top rail.
Add a curved rail in its place

What made it happen in the first one was probably the instant blueprint building from creative mode

This should be fixed in 0.15.

Please post a video showing what's breaking because when I test it in 0.15.6 it works perfectly.

Nevermind, I see now what you're talking about.

Fixed in Version: 0.15.10