Gamescope breaks mouse input for deathloop

[duskmoss]

Is there an existing issue for this?

• I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

• The issue occurs on upstream gamescope without any modifications

Current Behavior

With current gamescope mouse input for deathloop causes the character to perpetually stare straight downward. Moving them mouse spins wildly but still staring downward.

Gamepad input works fine.

I see someone on ProtonDB has also reported this https://www.protondb.com/app/1252330#eukJ2_oNMd

It was working for me on version. 3.14.24 but broken on 3.16, which my distro updated to. Going to try and bisect to see if I can point to a commit.

Steps To Reproduce

1. Launch deathloop with gamescope

2. start game, move mouse once game is waiting for you to move around.

Hardware information

- Distro: Void
- CPU: 5900x
- GPU: 6700xt
- Driver Version: mesa 24.3.2

Software information

- Desktop environment: KDE 6.2.5
- Session type: Wayland
- Gamescope version: 3.16,
- Gamescope launch command(s):  `DXVK_HDR=1 gamescope -f --hdr-enabled -W 3440 -H 1440  -- %command% `

Which gamescope backends have the issue you are reporting?

• Wayland (default for nested gamescope)
• DRM (default for embedded gamescope, i.e. gamescope-session)
• SDL
• OpenVR

Logging, screenshots, or anything else

No response

[matte-schwartz]

have you tried with --force-grab-cursor as well?

[duskmoss]

69610ec is the first bad commit

commit 69610ec52429fecbe94c4c042cc42ab43e0491f8
Author: Autumn Ashton <misyl@froggi.es>
Date:   Wed Jul 24 18:22:11 2024 +0100

    steamcompmgr: Relative mouse fixes and improvements

[duskmoss]

It looks like --force-grab-cursor works.

This still seems like a regression to me that should be addressed given it was working before. What do you think @misyltoad

seems like --force-grab-cursor should also be documented in the readme?

[matte-schwartz]

seems like a duplicate of this issue then if --force-grab-cursor resolves it #1470

[duskmoss]

It could be, but it could be a different issue, the symptoms are somewhat different. Theirs might actually be from 3c5a232 , but probably not dade663