[2.0.66] Blueprint icon shakes while character moving

[FilipForFico]

Hi, I just found a very weird graphical bug concerning blueprint icons.

I wanted to record it, but I can't seem to install my usual recording software (will definitely provide a recording if you can't reproduce it, though).

So, to reproduce this graphical bug/glitch, create a blueprint and give it an icon (I set it to the A, B, C, and D symbols). Then, place the blueprint in the inventory. Open the inventory and click on the blueprint with your mouse. The blueprint should pop-up and stay attached to the mouse. Then, while still in the inventory, start moving around using WASD. You should see the icons of the blueprint shake relative to the item. The effect is most intense with default movement speed (no exoskeletons, no mech armour). It is also most visible moving diagonally as the icons shake in the direction of travel (since diagonal movement combines X and Y, the shaking goes in both up and down direction).

This also occurs holding the blueprint while it is in the toolbar.

Computer and game settings details:
Linux Fedora 42, X11 display server, 4K monitor;
max graphical settings


P.S. I just tested my game again to verify I am not going crazy and found some weird things.

This glitch depends on the zoom level. While zoomed out all the way, the strongest shake is obtained by moving in the cardinal directions. While zoomed all the way into the character (using default options), the effect is strongest moving diagonally.

Then, when `allow-increased-zoom` is on, zooming all the way in seems to fix the shake (the icon doesn't shake, but moves 1 pixel once and stays until you stop moving). Zooming out even one scroll click away, the effect returns.

Finally, the shaking effect also occurs when zooming in and out using the scroll wheel while holding the blueprint, and is most intense the more zoomed in you are.

[Rseding91]

Thanks for the report. I looked into this and I don't see a reasonable way to prevent this from happening. There's some precision loss going from the screen position the cursor wants to draw at to the end draw order sent to the drawing logic due to the position passing between screen-space and world-space multiple times.

[FilipForFico]

Ah, sounds very nasty.