Open gtosh4 opened 2 years ago
I suspect WSL2 is incorrectly reporting mouse motion to us through X11 or Wayland.
Do you know who/how to track this down so that I may forward the issue? Do you think it might be here: https://github.com/microsoft/wslg ? Also, I could use some help gathering some additional context to help them out - is there a particular API or system I should specify that is used to help them figure out what's wrong?
First, you have to figure out whether it's happening with X11 or Wayland. Then, you can track down the places where we emit DeviceEvent::MouseMotion
in the relevant backend to find the API that we get bad data through.
When running a bevy program in WSL2, the MouseMotion event appears to be returning the position:
And the values are never negative.
Whereas, when running the same program in native Windows, I see the correct deltas:
I presume this is a winit issue, as bevy appears to just be forwarding the values (see bevy_winit); however, I'm not sure so I apologize if this is incorrect.