I am afraid I can't reproduce this as it was in the middle of a firefight, but hopefully the explanation will be enough to go off. I was clearing out some nests, and I was about to kill the last worm, but all of a sudden it seemed like my gun jammed. I pressed fire repeatedly and nothing happened. I...

When placing even a very simple blueprint from map view, the placement needs to be much more exact than it used to be. The entire blueprint is green and snapped in the correct place but cannot be placed until the mouse is in a very specific position. No errors are produced. I would guess that the sy...

addendum: shift and left click also now seems to destroy the blueprint, even though that's not in the tooltip

Please bring back the clear blueprint functionality, updating an existing blueprint is so much less intuitive now :/

Addendum 2: -Building (non-blueprint) wagon/train ghosts on diagonal rails seems to be impossible (although I'm not sure if I've ever tried this before TBH). -Building (non-blueprint) wagon/train ghosts on vertical rails also seems to be impossible, but works on horizontal. -Building (non-blueprint)...

As an addendum - the vertical mouse placement (for horizontal rails), seems to be the only thing that matters, and vice versa. The horizontal mouse placement on horizontal rails (and vertical on vertical), seems to make no difference at all.

Thanks for reporting this, I get the same issue, just a tad annoying and weird. :/

I can confirm this fixes the bug I posted.

Thanks - I think (this means by main game is no longer broken and I can go back to playing... just when I thought I'd nearly broken the addiction...)

Glad to see that someone else has noticed this! :) It happened with the 0.49 release. I posted about it twice, first time it was thought resolved with a different fix, and the second time it was assigned as not a bug :( . https://forums.factorio.com/viewtopic.php?f=7&t=72111 https://forums.facto...

Has this behaviour changed intentionally since .49? Prior to this, when a reserved signal was closed by the circuit network (after the reservation was made), it would still read the reserved state, and the transition to the red state - it would only stop reading when the signal went back to green. T...

Re-posting below as bug was not fixed as reported in: https://forums.factorio.com/viewtopic.php?f=11&t=72111 Doesn't happen in .48, started in .49, still broken in .50-.52 If a train reserves a path through, but does not start passing, a signal that is subsequently closed via the circuit network...

Unfortunately this has not been resolved in 0.17.50

OK, update after more experimentation to recreate: If a train reserves a path through but does not start passing the signal before it closes, then it will not read the change in state to red (the amber state stops being red correctly, but red doesn't start). If the same train reserves a path through...

Doesn't happen in .48, started in .49 When a train reserves a path through a signal that is subsequently closed via the circuit network before the train has finished passing, the signal stops reading it's colour state as soon as it is closed. Prior to .49, it would keep reading it's state until the ...

Nope, this still occurs in 0.17.39

Thanks for the update kovarex - it would be really nice to see this fixed in future, as it really is immersion breaking, if nothing else.

This seems to have only started in a very recent update. I am probably going to regret asking for this to be fixed, as I am finding it useful, but I am afraid that for balance purposes it seems like far too overpowered a tool. The ability to build infinite length rails as long as you are near the st...

Ok, but that sounds odd to me. Is this behaviour explained in an FFF or somewhere?

Blueprint should be fairly self explanatory, just stick it in a bot network with iron plates, or load the chests manually with 100 iron each. I would expect both items to reach the end at the same time - after all they should be travelling the same distance. 0eNrtm1ty4zYQRfeCbzFFvPhQVVaSmlLpAc2gQpEM...

Just a quick update, don't mean this to be a bump, but I can confirm that this bug still exists in 0.17.21 - the same save file still produces the same outcome.

100% support this, would make life so much easier!