| 29 May 2025 |
Nila The Dragon | NixOS 25.11 (Xantusia) x86_64 (Unstable) | 15:08:00 |
Nila The Dragon | The game will launch fine without gamescope + it will launch if I launch the entire steam client through gamescope as well | 15:08:15 |
K900 | Try removing --backend sdl | 15:08:19 |
K900 | Actually | 15:08:21 |
Nila The Dragon | That will not work on GNOME currently due to https://github.com/ValveSoftware/gamescope/issues/1825 | 15:08:38 |
K900 | Honestly no idea then, you'll want to attach a debugger to the game or something | 15:10:07 |
K900 | Or just don't run Gamescope because all the HDR bits should be working out of the box now | 15:10:22 |
Nila The Dragon | The reason I'd like to use it is that on Gnome my mouse is not being properly locked to the game window. So if I do fast movements towards my second monitor and click, the mouse will actually escape the game. | 15:12:41 |
Nila The Dragon | Otherwise I'd be more than pleased to not use another in-between layer. But the only solution I found to the mouse capturing issue is to use gamescope with the --force-grab... option | 15:13:19 |
K900 | Does the game just not grab the cursor? | 15:15:38 |
K900 | Or is this a Wine issue of some sort? | 15:15:45 |
Nila The Dragon | So the game does "grab" it. It stays locked to the game during motion and I can spin around infinitely. The problem occurs specifically when I do a fast, longer motion towards the second screen, the cursor then (invisibly) actually moves over whatever windows I have there and as soon as I click (while still moving, it does not happen when i stop moving and then click) the mouse will actually activate whatever window it was over. Really really weird bug. | 15:18:38 |
K900 | Maybe try latest Proton with wine-wayland? | 15:31:19 |
Nila The Dragon | I assume I need Proton-GE for that? | 15:56:34 |
K900 | No | 16:07:51 |