diff options
| author | Mikołaj Lercher <bandicoots94@gmail.com> | 2025-02-11 05:52:53 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-11 07:52:53 +0300 |
| commit | 3a481b5250b1cd832768c5c3ca9e516ba9963120 (patch) | |
| tree | ead5a8a990aca9ba1f3b67cc18b27e3c449ea6df | |
| parent | 20769b4c2f843566880f020f117e7bde36edc332 (diff) | |
| download | niri-3a481b5250b1cd832768c5c3ca9e516ba9963120.tar.gz niri-3a481b5250b1cd832768c5c3ca9e516ba9963120.tar.bz2 niri-3a481b5250b1cd832768c5c3ca9e516ba9963120.zip | |
wiki: describe running games with gamescope (#1112)
* wiki: describe running games with gamescope
* Update wiki/Application-Issues.md
---------
Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com>
| -rw-r--r-- | wiki/Application-Issues.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/wiki/Application-Issues.md b/wiki/Application-Issues.md index 6a0e3de5..4ace5736 100644 --- a/wiki/Application-Issues.md +++ b/wiki/Application-Issues.md @@ -30,3 +30,22 @@ To fix this, run them with the `_JAVA_AWT_WM_NONREPARENTING=1` environment varia There's a bug in rofi-wayland that prevents it from accepting keyboard input on niri with errors in the output. It's been fixed in rofi, but the fix had not been released yet: https://github.com/davatorium/rofi/discussions/2008 + +### Fullscreen games + +Some video games, both Linux-native and on Wine, have various issues when using non-stacking desktop environments. +Most of these can be avoided with Valve's [gamescope](https://github.com/ValveSoftware/gamescope), for example: + +```sh +gamescope -f -w 1920 -h 1080 -W 1920 -H 1080 --force-grab-cursor --backend sdl -- <game> +``` + +This command will run *<game>* in 1080p fullscreen—make sure to replace the width and height values to match your desired resolution. +`--force-grab-cursor` forces gamescope to use relative mouse movement which prevents the cursor from escaping the game's window on multi-monitor setups. +Note that `--backend sdl` is currently also required as gamescope's default Wayland backend doesn't lock the cursor properly (possibly related to [https://github.com/ValveSoftware/gamescope/issues/1711]). + +Steam users should use gamescope through a game's [launch options](https://help.steampowered.com/en/faqs/view/7D01-D2DD-D75E-2955) by replacing the game executable with `%command%`. +Other game launchers such as [Lutris](https://lutris.net/) have their own ways of setting gamescope options. + +Running X11-based games with this method doesn't require Xwayland as gamescope creates its own Xwayland server. +You can run Wayland-native games as well by passing `--expose-wayland` to gamescope, therefore eliminating X11 from the equation. |