Run a game using gamescope - Revision history

Theleruby at 20:14, 9 February 2026

2026-02-09T20:14:07Z

← Older revision		Revision as of 20:14, 9 February 2026
Line 17:		Line 17:
	Fix a crash that happens sometimes minimizing the game:		Fix a crash that happens sometimes minimizing the game:
	--expose-wayland		--expose-wayland
			==== Commands that should work but don't seem to ====
	Don't hide cursor		Don't hide cursor
	--hide-cursor-delay -1		--hide-cursor-delay -1

Theleruby at 20:11, 9 February 2026

2026-02-09T20:11:44Z

← Older revision		Revision as of 20:11, 9 February 2026
Line 17:		Line 17:
	Fix a crash that happens sometimes minimizing the game:		Fix a crash that happens sometimes minimizing the game:
	--expose-wayland		--expose-wayland
			Don't hide cursor
			--hide-cursor-delay -1
	==== Known bugs ====		==== Known bugs ====
	* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.		* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.
	* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777		* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777

Theleruby at 19:57, 9 February 2026

2026-02-09T19:57:20Z

← Older revision		Revision as of 19:57, 9 February 2026
Line 1:		Line 1:
	Gamescope is Valve's micro-compositor that allows games to run in an isolated virtual display. It is used on the Steam Deck but also works in desktop Linux.		Gamescope is Valve's micro-compositor that allows games to run in an isolated virtual display. It is used on the Steam Deck but also works in desktop Linux.

	To run using gamescope 2560x1440@120:		To run a game using a gamescope virtual display targeting 2560x1440@120:
	gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE		gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE
	For example this runs WoW using proton inside gamescope ([[Running Windows games via Proton without going through Steam or Lutris]]):		For example this runs WoW using proton inside gamescope ([[Running Windows games via Proton without going through Steam or Lutris]]):

Theleruby at 19:57, 9 February 2026

2026-02-09T19:57:04Z

← Older revision		Revision as of 19:57, 9 February 2026
Line 1:		Line 1:
			Gamescope is Valve's micro-compositor that allows games to run in an isolated virtual display. It is used on the Steam Deck but also works in desktop Linux.

	To run using gamescope 2560x1440@120:		To run using gamescope 2560x1440@120:
	gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE		gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE

Theleruby at 19:55, 9 February 2026

2026-02-09T19:55:43Z

← Older revision		Revision as of 19:55, 9 February 2026
Line 13:		Line 13:
	To display mangohud:		To display mangohud:
	--mangoapp		--mangoapp
	~~====~~ Fix a crash that happens sometimes minimizing the game ~~====~~		Fix a crash that happens sometimes minimizing the game:
	--expose-wayland		--expose-wayland
	==== Known bugs ====		==== Known bugs ====
	* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.		* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.
	* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777		* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777

Theleruby at 19:55, 9 February 2026

2026-02-09T19:55:32Z

← Older revision		Revision as of 19:55, 9 February 2026
Line 13:		Line 13:
	To display mangohud:		To display mangohud:
	--mangoapp		--mangoapp
			==== Fix a crash that happens sometimes minimizing the game ====
			--expose-wayland
	==== Known bugs ====		==== Known bugs ====
	* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.		* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.
	* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777		* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777

Theleruby at 19:20, 9 February 2026

2026-02-09T19:20:45Z

← Older revision		Revision as of 19:20, 9 February 2026
Line 14:		Line 14:
	--mangoapp		--mangoapp
	==== Known bugs ====		==== Known bugs ====
	* Gamescope doesn't exit properly afterwards ~~and~~ you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777		* If you call gamescope with no command line arguments, then CTRL+C out of it in Terminal, the whole Wayland session crashes and you'll have to reset the PC using power button. Herp derp.
			* Gamescope doesn't exit properly afterwards once the game is closed; you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777

Theleruby: Created page with "To run using gamescope 2560x1440@120: gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE For example this runs WoW using proton inside gamescope (Running Windows games via Proton without going through Steam or Lutris): #!/bin/bash export STEAM_COMPAT_DATA_PATH="/opt/_pfx/wow" export STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.steam/steam pushd "/opt/games/World of Warcraft/" gamescope -w 2560 -h 1440 -r 120 -- $STEAM_COMPAT_CLIENT_INSTALL_PATH/compatibili..."

2026-02-09T19:18:38Z

Created page with "To run using gamescope 2560x1440@120: gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE For example this runs WoW using proton inside gamescope (Running Windows games via Proton without going through Steam or Lutris): #!/bin/bash export STEAM_COMPAT_DATA_PATH="/opt/_pfx/wow" export STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.steam/steam pushd "/opt/games/World of Warcraft/" gamescope -w 2560 -h 1440 -r 120 -- $STEAM_COMPAT_CLIENT_INSTALL_PATH/compatibili..."

New page

To run using gamescope 2560x1440@120:
gamescope -w 2560 -h 1440 -r 120 -- OTHER COMMAND LINE ARGS HERE
For example this runs WoW using proton inside gamescope ([[Running Windows games via Proton without going through Steam or Lutris]]):
#!/bin/bash
export STEAM_COMPAT_DATA_PATH="/opt/_pfx/wow"
export STEAM_COMPAT_CLIENT_INSTALL_PATH=~/.steam/steam
pushd "/opt/games/World of Warcraft/"
gamescope -w 2560 -h 1440 -r 120 -- $STEAM_COMPAT_CLIENT_INSTALL_PATH/compatibilitytools.d/GE-Proton10-29/proton run "/opt/games/World of Warcraft/Wow.exe" & disown
popd
==== Commands you can add before the -- ====
To stretch game to fill window:
-S stretch
To display mangohud:
--mangoapp
==== Known bugs ====
* Gamescope doesn't exit properly afterwards and you have to endtask winedevice.exe and possibly gamescope and gamescopereaper. See https://github.com/ValveSoftware/gamescope/issues/777