Games that require me to move my mouse quickly or far to the right cause my cursor to appear just at the edge of the next monitor and no further, but as long as I move my mouse back to the left before clicking it doesn’t escape the fullscreen game. If I do click after a quick movement to the right then the mouse entirely escapes the game and I have to click back on to keep controlling the game. The weird part is, it doesnt happen with all games, just few. I’ve made sure my settings are set to full screen, not boarderless windowed. I have also tried a few gamescope steam launch options, but they have either made no difference or caused the game to stop launching entirely.
Anyone have any tips or things I can try?
Edit: image attached to show my mouse going onto the right monitor, but it wont go any further than this and it feels like its still captured by the game until I left click
Edit 2, more information:
I’m running wayland, I got it to work when i switch to xorg using this gamescope -w 3440 -h 1440 -f -r 160 --force-grab-cursor – %command%
but honestly I would like to just stick to wayland since some games seem to run poorly or not at all when Im on xorg.
Are you using gamescope or gamescope-git? For some reason --force-grab-cursor never works for me on standard but when I use the git edition it works (for my case).
Sharing a solution I found to work without having to log out and switch to xorg for problematic games, apparently I can use xwayland with gamescope to run xorg within my wayland environment. Which Im fine with because I dont need to do any extra steps to play the games that just work in wayland.
I am entirely unsure what is the problem entirely, what DE are you using ? I am currently on KDE and it works there but I honest to god can’t see any issues on the log itself. You can try adding using the --expose-waylandcommand and seeing if that works, or try using gamescope-plus on the AUR, built by the Chimera devs. If all else fails, I would send a bug report to the gamescope github.
Sorry for my crashout, I eventually realized the issue gamescopes newest version introduced this bug on wayland and downgrading was able to get it to launch. Its apearing on the wrong monitor now but at least its fixed, so i think the main issue of this thread is (hopefully) resolved. And I hope anyone else frantically googling this issue with gamescope finds this and a downgrade helps them