I had this issue for quite a while and was not sure what caused it until I did some testing.
Steps to produce the issue:
1. Place a blueprint with multiple parameters (for example an item and a count).
2. Pick another blueprint that have a relative grid checked.
3. Trying to place the second blueprint will behave as if it is an absolute snap-to-grid and not relative.
4. placing anything else will reset the state and the 2nd blueprint will behave as expected.
This is a simple BP Book that contain two BP's to test the scenario:
Place the combinator BP first then the Assembly BP to replicate the issue. For me it happens at least 9/10 times.
[Kovarex] [2.0.32] Placing Multi-Parametrized Blueprint makes next Blueprint with Relative Snap-to-Grid Absolute
Re: [Kovarex] [2.0.32] Placing Multi-Parametrized Blueprint makes next Blueprint with Relative Snap-to-Grid Absolute
Hello, I can't reproduce this in the current version, so I guess it was fixed in the meantime.
Re: [Kovarex] [2.0.32] Placing Multi-Parametrized Blueprint makes next Blueprint with Relative Snap-to-Grid Absolute
I am still having the same issue in 2.0.45.
I have attached a sample video. Hope it helps.
I have attached a sample video. Hope it helps.
Re: [Kovarex] [2.0.32] Placing Multi-Parametrized Blueprint makes next Blueprint with Relative Snap-to-Grid Absolute
I'm also having this issue in 2.0.47. It's difficult to reproduce, it's never been an issue before but it's now happened to me twice in the past 3 days. I'll try to figure out a consistent way to reproduce but just wanted to post in the meantime to reiterate that this is an ongoing problem.
Re: [Kovarex] [2.0.32] Placing Multi-Parametrized Blueprint makes next Blueprint with Relative Snap-to-Grid Absolute
I think I have found a duplicate of this bug report, and also experience this bug: viewtopic.php?t=113094
Re: [Kovarex] [2.0.32] Placing Multi-Parametrized Blueprint makes next Blueprint with Relative Snap-to-Grid Absolute
After having written all the below, I realized this is a "resolved" thread. I've copy/pasted this to viewtopic.php?t=132915
---
I'm encountering this on 2.0.76 build 84451 on Windows on a new, random seed (tested multiple times, all seeds exhibit this bug).
This blueprint is a a simple constant combinator, with parameter-0 and 1 parametrised constant.
With it, I discovered it only happens when a click occurs outside of the "Parametrised build" window. When selecting an option for parameter-0, the pixel you click on must be a pixel on top of the "Parametrised build" window. Clicking any pixel outside of the "Parametrised Build" window, such as the ground around it or even selecting the option for parameter-0, causes the bug. In fact, selecting parameter-0 that has half the icon above the "Parameterised build" window and half not, which half you click on determines whether the bug occurs.
Notably, dragging the "Select a signal" window for parameter-0 via the top bar such that an icon can be selected above the "Parametrised build" window does not cause the bug. Clicking the top bar of "Select a signal" does not cause the bug, even though it lies outside the boudns of "Parametrised build". Click+dragging the side of "Select a signal" and dragging to the ground, then selecting an icon that is withing the bounds of "Parametrised build" still causes the bug. It seems the framing/background of the UI does not cause the bug. You can spam click anywhere on the UI that doesn't select an icon, then select an icon within the bounds of the "Parametrised build" window and it does not cause the bug.
However, you can drag click from outside the "Parametrised build" window into the "Parameterised build" window, and the bug does not occur; even though the initial "down" of the click was outside of the window. It seems the "up" of a click is the trigger. Indeed, selecting an icon for parameter-0 that is outside the bounds, you can click down on the icon, drag into the window bounds, then release; it selects the correct icon (the one you pressed down on) but does not trigger the bug.
It seems like opening most entity's UI clears the bug. Opening inventory, blueprint library, factoriopedia does not.
---
I'm encountering this on 2.0.76 build 84451 on Windows on a new, random seed (tested multiple times, all seeds exhibit this bug).
This blueprint is a a simple constant combinator, with parameter-0 and 1 parametrised constant.
With it, I discovered it only happens when a click occurs outside of the "Parametrised build" window. When selecting an option for parameter-0, the pixel you click on must be a pixel on top of the "Parametrised build" window. Clicking any pixel outside of the "Parametrised Build" window, such as the ground around it or even selecting the option for parameter-0, causes the bug. In fact, selecting parameter-0 that has half the icon above the "Parameterised build" window and half not, which half you click on determines whether the bug occurs.
Notably, dragging the "Select a signal" window for parameter-0 via the top bar such that an icon can be selected above the "Parametrised build" window does not cause the bug. Clicking the top bar of "Select a signal" does not cause the bug, even though it lies outside the boudns of "Parametrised build". Click+dragging the side of "Select a signal" and dragging to the ground, then selecting an icon that is withing the bounds of "Parametrised build" still causes the bug. It seems the framing/background of the UI does not cause the bug. You can spam click anywhere on the UI that doesn't select an icon, then select an icon within the bounds of the "Parametrised build" window and it does not cause the bug.
However, you can drag click from outside the "Parametrised build" window into the "Parameterised build" window, and the bug does not occur; even though the initial "down" of the click was outside of the window. It seems the "up" of a click is the trigger. Indeed, selecting an icon for parameter-0 that is outside the bounds, you can click down on the icon, drag into the window bounds, then release; it selects the correct icon (the one you pressed down on) but does not trigger the bug.
It seems like opening most entity's UI clears the bug. Opening inventory, blueprint library, factoriopedia does not.