search

ValveSoftware / gamescope

SteamOS session compositing window manager
Other
2.99k stars 198 forks source link

Mouse not functioning correctly with the latest update (3.14.29) #1467

Open 4nexus5 opened 1 month ago

4nexus5 commented 1 month ago

I updated my gamescope to the latest version yesterday and after updating my mouse did everything except work correctly in Counter-Strike 2. On the first launch, the cursor was still visible while in match even though it shouldn't be and no matter in what direction or how fast I move my mouse, I keep looking down and spinning very fast. I tried relaunching CS2 and that gave me a different outcome: everything was inverted and a bit slow. Moving mouse to the left resulted in the cursor moving right and vice versa, same for up and down. On another relaunch, the cursor was moving correctly, it wasn't inverted, but it was limited to a small space, almost like it is limited to the top left part of the monitor. Downgrading to 3.10.24 through paccache fixed the problem for me.

xhenner commented 1 month ago

Same issue on cyberpunk 2077

PadTrick commented 3 weeks ago

same for me. went back to 3.14.24 and all works as expected

HenrikDK2 commented 2 weeks ago

Same for me, it used to work before the last update, now every game doesn't grab the cursor when gamescope is used

benbuch commented 2 weeks ago

--force-grab-cursor kinda fixes it, in my case it makes the cursor insanely fast and if you move it to a new workspace it will loss hold of the window unless you take it out of fullscreen mode

tobiasjakobi commented 1 day ago

I'm probably seeing the same issue here. I recently updated from v3.14.24 to v3.15.5. Noticed that there are now some games where the mouse input is no longer working. Examples are SOMA and Resident Evil 8.

The mouse still works in the game menu, i.e. when the game shows a mouse cursor which you can move around. But the mouse no longer generates any input when being in-game.

I bisected and this is the bad commit: https://github.com/ValveSoftware/gamescope/commit/69610ec52429fecbe94c4c042cc42ab43e0491f8

Well, this one is about relative mouse movements, so this bisection result is sensible I guess. I've also double-checked by reverting this specific commit on top of v3.14.28 -- which also works.

I'm using gamescope in conjunction with the DRM backend (greeter starts gamescope and inside a Steam session), so --force-grab-cursor does not help me here.