Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Panning visual shader editor in Wayland is not 1:1 with certain scaling settings #93981

Closed
Tracked by #88346
eobet opened this issue Jul 5, 2024 · 1 comment · Fixed by #94021
Closed
Tracked by #88346

Panning visual shader editor in Wayland is not 1:1 with certain scaling settings #93981

eobet opened this issue Jul 5, 2024 · 1 comment · Fixed by #94021

Comments

@eobet
Copy link
Contributor

eobet commented Jul 5, 2024

Tested versions

4.3 beta 2

System information

Godot v4.3.beta2 - Nobara Linux 40 (GNOME Edition) - Wayland - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 3050 Ti Laptop GPU - 11th Gen Intel(R) Core(TM) i7-11370H @ 3.30GHz (8 Threads)

Issue description

When dragging with the middle mouse button in the visual shader editor to pan the view around, the view lags behind the mouse in Wayland when you have the desktop set to a display scaling of 175% and the display scaling inside of Godot forced to 100% (this was done in an attempt to work around #93788).

Steps to reproduce

  1. Set the desktop display scaling to 175% in Gnome Wayland.
  2. Open Godot with "prefer Wayland" enabled and then change the display scale editor setting to 100%
  3. Middle mouse drag in the visual shader editor and note how it lags behind, compared to when the desktop and Godot is set to the same scale.

Minimal reproduction project (MRP)

Not applicable, any project will do.

@Riteo
Copy link
Contributor

Riteo commented Jul 7, 2024

(sorry for the tasklist edit, I accidentally clicked its button as I was messing with display scaling 😅)

Thank you for all your testing on a scaled setup! I could replicate this on sway and it looks like I forgot to scale the relative motion event, so it should be easy peasy. Fix incoming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants