[2.1.9] Reverse rotation fails on object previews with limited valid rotations

Bugs which we just recently fixed in our development version and will reach you in the next release.
Randymations
Manual Inserter
Manual Inserter
Posts: 1
Joined: Sat Jul 11, 2026 2:26 pm
Contact:

[2.1.9] Reverse rotation fails on object previews with limited valid rotations

Post by Randymations »

For objects with a limited number of valid rotations (e.g. Train stop and Offshore pump), rotating the preview of the object should skip invalid rotations. This occurs successfully when rotating "forward" or clockwise (R on default controls). When rotating in "reverse" or counterclockwise (Shift + R on default controls), the object preview fails to skip the invalid position and instead does not rotate. The expected behavior mirrors the clockwise behavior and skips the invalid rotation.

Rail signals and Rail chain signals fail to reverse rotate at all under any circumstances.

This gif demonstrates the issue. In each valid Train stop position, the object preview is first rotated clockwise successfully, then rotated counterclockwise where it gets "stuck". This behavior is consistent in all permutations of the scenario including two parallel rails (not pictured). Also shown is consistent behavior with the Offshore pump. Although not all permutations are shown, behavior is consistent. Also not pictured are Rail signals or Rail chain signals which show no reaction when attempting to reverse rotate.
Bug.gif
Bug.gif (18.68 MiB) Viewed 233 times

This issue is not related to Shift also being bound to ghost placement as it occurs even when binding a dedicated key to reverse rotation.

This is admittedly a partial duplicate of 108635 but I have attempted to generalize the issue and demonstrate that it still occurs on the current version.
Rseding91
Factorio Staff
Factorio Staff
Posts: 17216
Joined: Wed Jun 11, 2014 5:23 am
Contact:

Re: [2.1.9] Reverse rotation fails on object previews with limited valid rotations

Post by Rseding91 »

Thanks for the report. This is now fixed for the next release.
If you want to get ahold of me I'm almost always on Discord.
Post Reply

Return to “Resolved for the next release”