[1.1.110] Rail signals placed with wrong rotation when using copy&paste

Bugs that are actually features.
Metaing
Burner Inserter
Burner Inserter
Posts: 8
Joined: Mon Sep 09, 2024 4:55 pm
Contact:

[1.1.110] Rail signals placed with wrong rotation when using copy&paste

Post by Metaing »

Rail (chain) signals are placed with wrong rotation when using copy&paste.
If you copy a signal from a track in one direction (eg. 45 degree angle) and paste it next to a track in another direction (eg. 0 degree) the signal keeps the original orientation. It does not rotate to the correct orientation.
The Rail signal is also blinking as not connected to a rail.

Loewchen
Global Moderator
Global Moderator
Posts: 8969
Joined: Wed Jan 07, 2015 5:53 pm
Contact:

Re: [1.1.110] Rail signals placed with wrong rotation when using copy&paste

Post by Loewchen »

Blueprinting copies orientation, that is intended.

robot256
Filter Inserter
Filter Inserter
Posts: 819
Joined: Sun Mar 17, 2019 1:52 am
Contact:

Re: [1.1.110] Rail signals placed with wrong rotation when using copy&paste

Post by robot256 »

If you don't want the exact orientation, instead of copying the other signal, press Q to pipette it into your cursor to place normally.

Metaing
Burner Inserter
Burner Inserter
Posts: 8
Joined: Mon Sep 09, 2024 4:55 pm
Contact:

Re: [1.1.110] Rail signals placed with wrong rotation when using copy&paste

Post by Metaing »

To pipette requires you have it in your inventory. Which is kind of stupid if remote placed anyway.
Why I prefer to use the copy&paste.

Loewchen
Global Moderator
Global Moderator
Posts: 8969
Joined: Wed Jan 07, 2015 5:53 pm
Contact:

Re: [1.1.110] Rail signals placed with wrong rotation when using copy&paste

Post by Loewchen »

Metaing wrote:
Wed Oct 02, 2024 6:01 pm
To pipette requires you have it in your inventory. Which is kind of stupid if remote placed anyway.
Only if you specifically set it to not switch to ghosts. If you want to discuss this further, open a gameplay help topic or make a feature request.

Locked

Return to “Not a bug”