Go to file
Nyaaori d39000aa9f
feat: add out-of-spec but mostly working display frequencies to steam deck
2023-11-28 07:35:32 +01:00
.github/workflows ci: Add benchmark as a dependency 2023-05-09 16:20:56 +00:00
layer layer: Disable EXT_swapchain_maintenance1 2023-11-09 18:47:46 +00:00
protocol Use wayland-protocols instead of vendoring upstream protocols 2023-11-24 12:03:36 +01:00
src feat: add out-of-spec but mostly working display frequencies to steam deck 2023-11-28 07:35:32 +01:00
subprojects Port to wlroots 0.17 2023-11-22 15:22:19 +01:00
thirdparty build: Add reshade submodule 2023-09-14 09:03:12 -07:00
.editorconfig Add .editorconfig 2021-04-08 09:15:39 +02:00
.gitmodules build: Add reshade submodule 2023-09-14 09:03:12 -07:00
LICENSE build: Add reshade submodule 2023-09-14 09:03:12 -07:00
README.md readme: Add reshade info to readme 2023-09-14 09:03:12 -07:00
meson.build build: Force fallback for vkroots 2023-11-21 14:38:53 -08:00
meson_options.txt build: make benchmark optional 2023-10-11 16:00:23 +02:00


gamescope: the micro-compositor formerly known as steamcompmgr

In an embedded session usecase, gamescope does the same thing as steamcompmgr, but with less extra copies and latency:

  • It's getting game frames through Wayland by way of Xwayland, so there's no copy within X itself before it gets the frame.
  • It can use DRM/KMS to directly flip game frames to the screen, even when stretching or when notifications are up, removing another copy.
  • When it does need to composite with the GPU, it does so with async Vulkan compute, meaning you get to see your frame quick even if the game already has the GPU busy with the next frame.

It also runs on top of a regular desktop, the 'nested' usecase steamcompmgr didn't support.

  • Because the game is running in its own personal Xwayland sandbox desktop, it can't interfere with your desktop and your desktop can't interfere with it.
  • You can spoof a virtual screen with a desired resolution and refresh rate as the only thing the game sees, and control/resize the output as needed. This can be useful in exotic display configurations like ultrawide or multi-monitor setups that involve rotation.

It runs on Mesa + AMD or Intel, and could be made to run on other Mesa/DRM drivers with minimal work. AMD requires Mesa 20.3+, Intel requires Mesa 21.2+. For NVIDIA's proprietary driver, version 515.43.04+ is required (make sure the nvidia-drm.modeset=1 kernel parameter is set).

If running RadeonSI clients with older cards (GFX8 and below), currently have to set R600_DEBUG=nodcc, or corruption will be observed until the stack picks up DRM modifiers support.


git submodule update --init
meson build/
ninja -C build/
build/gamescope -- <game>

Install with:

meson install -C build/ --skip-subprojects

Keyboard shortcuts

  • Super + F : Toggle fullscreen
  • Super + N : Toggle nearest neighbour filtering
  • Super + U : Toggle FSR upscaling
  • Super + Y : Toggle NIS upscaling
  • Super + I : Increase FSR sharpness by 1
  • Super + O : Decrease FSR sharpness by 1
  • Super + S : Take screenshot (currently goes to /tmp/gamescope_$DATE.png)
  • Super + G : Toggle keyboard grab
  • Super + C : Update clipboard


On any X11 or Wayland desktop, you can set the Steam launch arguments of your game as follows:

# Upscale a 720p game to 1440p with integer scaling
gamescope -h 720 -H 1440 -S integer -- %command%

# Limit a vsynced game to 30 FPS
gamescope -r 30 -- %command%

# Run the game at 1080p, but scale output to a fullscreen 3440×1440 pillarboxed ultrawide window
gamescope -w 1920 -h 1080 -W 3440 -H 1440 -b -- %command%


See gamescope --help for a full list of options.

  • -W, -H: set the resolution used by gamescope. Resizing the gamescope window will update these settings. Ignored in embedded mode. If -H is specified but -W isn't, a 16:9 aspect ratio is assumed. Defaults to 1280×720.
  • -w, -h: set the resolution used by the game. If -h is specified but -w isn't, a 16:9 aspect ratio is assumed. Defaults to the values specified in -W and -H.
  • -r: set a frame-rate limit for the game. Specified in frames per second. Defaults to unlimited.
  • -o: set a frame-rate limit for the game when unfocused. Specified in frames per second. Defaults to unlimited.
  • -F fsr: use AMD FidelityFX™ Super Resolution 1.0 for upscaling
  • -F nis: use NVIDIA Image Scaling v1.0.3 for upscaling
  • -S integer: use integer scaling.
  • -S stretch: use stretch scaling, the game will fill the window. (e.g. 4:3 to 16:9)
  • -b: create a border-less window.
  • -f: create a full-screen window.

Reshade support

Gamescope supports a subset of Reshade effects/shaders using the --reshade-effect [path] and --reshade-technique-idx [idx] command line parameters.

This provides an easy way to do shader effects (ie. CRT shader, film grain, debugging HDR with histograms, etc) on top of whatever is being displayed in Gamescope without having to hook into the underlying process.

There is currently no way to set the value of uniforms/options, they will just be their initializer values currently.

Using Reshade effects will increase latency as there will be work performed on the general gfx + compute queue as opposed to only using the realtime async compute queue which can run in tandem with the game's gfx work.

Using Reshade effects is highly discouraged for doing simple transformations which can be achieved with LUTs/CTMs which are possible to do in the DC (Display Core) on AMDGPU at scanout time, or with the current regular async compute composite path. The looks system where you can specify your own 3D LUTs would be a better alternative for such transformations.

Pull requests for improving Reshade compatibility support are appreciated.

Status of Gamescope Packages

Packaging status