Open troy0h opened 3 weeks ago
I got a similar problem, and it changes from game to game. The command I use is
ENABLE_HDR_WSI=1 gamescope -f -W 3840 -H 2160 --hdr-enabled --hdr-debug-force-output --force-grab-cursor -e -- env ENABLE_GAMESCOPE_WSI=1 DXVK_HDR=1 DISABLE_HDR_WSI=1 steam
Steam options like -steamdeck
or -bigpicture
doesn't seem to affect the cursor behaviour in-game, other than making Steam annoying to use with a mouse and keyboard.
--force-grab-cursor
fixes the visibility part, but it kills the movement of the mouse outside menus altogether;--force-grab-cursor
mitigates the double cursor problem, but as it happened with Assassin's Creed: Odyssey it locks up the mouse movement, the difference being that this time it's locked even in menus as opposed to only when trying to move the camera. I managed to work around that by alt-tabbing back and forth from the game, however that doesn't seem consistent;While --force-grab-cursor
fixes problems with varying amounts of success, it's important to notice that it confines your cursor to the gamescope window. I personally prefer to have my cursor free to move between windows and displays, so that unnecessary constraint can be an annoyance.
+1 on this, it seems to be much more common in recent proton versions, might be a bug with 3.14.29 since that changed cursor stuff and was pushed to arch linux repos recently
In CS2, Dark Souls 1, and Deadlock, using Gamescope results in the game not capturing my cursor properly, meaning that I can only turn slightly, before my cursor either hits the edge of my screen, or goes on to my second monitor.