Steam - Revision history

Makuru: Additional workaround for when gamescope fails to start.

2026-10-21T00:41:00Z

Additional workaround for when gamescope fails to start.

← Older revision		Revision as of 00:41, 21 October 2026
Line 399:		Line 399:
	The [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]] headset is discovered through these Remote Play ports. See [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]].		The [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]] headset is discovered through these Remote Play ports. See [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]].

	=== Gamescope fails to launch when used within Steam === <!--T:46-->		=== Gamescope fails to launch when used within Steam ===


			Gamescope runs into an error when it starts with the wrong GPU, to fix this determine the Vulkan ID with: <code>vulkaninfo --summary</code> and add <code>--prefer-vk-device '''$vendorID''':'''$deviceID'''</code> from the output of the previous command.<!--T:46-->

	<!--T:47-->		<!--T:47-->

Cvcore: add a workaround for tiny mouse cursor issue

2026-10-15T13:04:15Z

add a workaround for tiny mouse cursor issue

@@ Line 453: / Line 453: @@
      extest.enable = true;
    };
 </syntaxhighlight>

Ardenet: Marked this version for translation

2026-10-05T14:18:36Z

Marked this version for translation

← Older revision		Revision as of 14:18, 5 October 2026
Line 396:		Line 396:
	<code>sudo setcap CAP_SYS_NICE+ep ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher</code>		<code>sudo setcap CAP_SYS_NICE+ep ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher</code>

			<!--T:73-->
	The [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]] headset is discovered through these Remote Play ports. See [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]].		The [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]] headset is discovered through these Remote Play ports. See [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]].

Ardenet: Add tvar tag to the link

2026-10-05T14:17:36Z

Add tvar tag to the link

← Older revision		Revision as of 14:17, 5 October 2026
Line 396:		Line 396:
	<code>sudo setcap CAP_SYS_NICE+ep ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher</code>		<code>sudo setcap CAP_SYS_NICE+ep ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher</code>

	The [[Steam Frame]] headset is discovered through these Remote Play ports. See [[Steam Frame]].		The [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]] headset is discovered through these Remote Play ports. See [[<tvar name=1>Special:MyLanguage/Steam Frame</tvar>\|Steam Frame]].

	=== Gamescope fails to launch when used within Steam === <!--T:46-->		=== Gamescope fails to launch when used within Steam === <!--T:46-->

Malix: Undid revision 34718 by Leroy (talk)

2026-10-01T15:11:02Z

Undid revision 34718 by Leroy (talk)

← Older revision		Revision as of 15:11, 1 October 2026
Line 130:		Line 130:

	<!--T:63-->		<!--T:63-->
	In order for HDR to work within gamescope, enable ~~it and disable~~ the ~~following~~ option:		In order for HDR to work within gamescope, you might need to separately enable the <code>enableWsi</code> option
	</translate>		</translate>

	<syntaxhighlight lang="nix">programs.gamescope = {		<syntaxhighlight lang="nix">programs.gamescope = {
	enable = true;		enable = true;
			enableWsi = true;
	capSysNice = false;		capSysNice = false;
	};</syntaxhighlight>		};</syntaxhighlight>
Line 140:		Line 141:
	<translate>		<translate>
	<!--T:64-->		<!--T:64-->
	It may be necessary to force HDR in gamescope with the argument <code>--hdr-debug-force-output</code> when configuring your game's launch options in steam (see the example below).		Additionally, it may be necessary to force HDR in gamescope with the argument <code>--hdr-debug-force-output</code> when configuring your game's launch options in steam (see the example below).
	</translate>		</translate>

MarkusZoppelt: Added [Steam Frame] reference below SteamVR

2026-09-27T15:35:59Z

Added [Steam Frame] reference below SteamVR

← Older revision		Revision as of 15:35, 27 September 2026
Line 394:		Line 394:
	The setcap issue at SteamVR start can be fixed with:		The setcap issue at SteamVR start can be fixed with:
	<code>sudo setcap CAP_SYS_NICE+ep ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher</code>		<code>sudo setcap CAP_SYS_NICE+ep ~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher</code>

			The [[Steam Frame]] headset is discovered through these Remote Play ports. See [[Steam Frame]].

	=== Gamescope fails to launch when used within Steam === <!--T:46-->		=== Gamescope fails to launch when used within Steam === <!--T:46-->

Leroy: "enableWsi" does not exist anymore.

2026-09-24T21:38:28Z

"enableWsi" does not exist anymore.

← Older revision		Revision as of 21:38, 24 September 2026
Line 130:		Line 130:

	<!--T:63-->		<!--T:63-->
	In order for HDR to work within gamescope, ~~you might need to separately~~ enable the ~~<code>enableWsi</code>~~ option		In order for HDR to work within gamescope, enable it and disable the following option:
	</translate>		</translate>

	<syntaxhighlight lang="nix">programs.gamescope = {		<syntaxhighlight lang="nix">programs.gamescope = {
	enable = true;		enable = true;
	~~enableWsi = true;~~
	capSysNice = false;		capSysNice = false;
	};</syntaxhighlight>		};</syntaxhighlight>
Line 141:		Line 140:
	<translate>		<translate>
	<!--T:64-->		<!--T:64-->
	~~Additionally, it~~ may be necessary to force HDR in gamescope with the argument <code>--hdr-debug-force-output</code> when configuring your game's launch options in steam (see the example below).		It may be necessary to force HDR in gamescope with the argument <code>--hdr-debug-force-output</code> when configuring your game's launch options in steam (see the example below).
	</translate>		</translate>

Ardenet: Marked this version for translation

2026-06-14T15:27:32Z

Marked this version for translation

← Older revision		Revision as of 15:27, 14 June 2026
Line 69:		Line 69:
	{{note\|<translate><!--T:11--> If you are using a Steam Controller or a Valve Index, Steam hardware support is implicitly enabled by <code>programs.steam.enable {{=}} true;</code> which sets <tvar name=steam_hardware_option>{{nixos:option\|hardware.steam-hardware.enable}}</tvar> to true.</translate>}}		{{note\|<translate><!--T:11--> If you are using a Steam Controller or a Valve Index, Steam hardware support is implicitly enabled by <code>programs.steam.enable {{=}} true;</code> which sets <tvar name=steam_hardware_option>{{nixos:option\|hardware.steam-hardware.enable}}</tvar> to true.</translate>}}

	{{note\|<translate>If you are using the Steam Controller released in 2026, the Steam client has an additional dependency on hidapi, needed to correctly communicate with the controller. If you are seeing repeated errors about failed firmware updates, this is likely why. You can add the dependency directly to the Steam environment like so: <code>programs.steam.extraPackages {{=}} [pkgs.hidapi];</code></translate>}}		{{note\|<translate><!--T:67--> If you are using the Steam Controller released in 2026, the Steam client has an additional dependency on hidapi, needed to correctly communicate with the controller. If you are seeing repeated errors about failed firmware updates, this is likely why. You can add the dependency directly to the Steam environment like so: <code>programs.steam.extraPackages {{=}} [pkgs.hidapi];</code></translate>}}

	<translate>		<translate>
	== Tips and tricks ==		== Tips and tricks == <!--T:68-->

	=== Improving Performance ===		=== Improving Performance === <!--T:69-->

			<!--T:70-->
	You can utilize <tvar name=gamemode>[https://github.com/FeralInteractive/gamemode GameMode]</tvar>, a combination of a library and daemon for Linux that allows games to request a set of optimizations to be temporarily applied to the host operating system and/or a game process.		You can utilize <tvar name=gamemode>[https://github.com/FeralInteractive/gamemode GameMode]</tvar>, a combination of a library and daemon for Linux that allows games to request a set of optimizations to be temporarily applied to the host operating system and/or a game process.
	</translate>		</translate>
Line 439:		Line 440:
	To find the vendor and product ID of a device <tvar name=usbutils>[https://search.nixos.org/packages?channel=unstable&show=usbutils&from=0&size=50&sort=relevance&type=packages&query=usbutils usbutils]</tvar> might be useful		To find the vendor and product ID of a device <tvar name=usbutils>[https://search.nixos.org/packages?channel=unstable&show=usbutils&from=0&size=50&sort=relevance&type=packages&query=usbutils usbutils]</tvar> might be useful

	=== Steam controller mouse input issues ===		=== Steam controller mouse input issues === <!--T:71-->

			<!--T:72-->
	Mouse input on the controller may fail to take control of the visual cursor. In this instance, the input is still registered, but the cursor does not move. A fix for this is to preload Steam with extest. The Steam package already has an option for it:		Mouse input on the controller may fail to take control of the visual cursor. In this instance, the input is still registered, but the cursor does not move. A fix for this is to preload Steam with extest. The Steam package already has an option for it:
	</translate>		</translate>

Ardenet: Fixed the error in the translation tag; converted the link to tvar

2026-06-14T15:25:17Z

Fixed the error in the translation tag; converted the link to tvar

← Older revision		Revision as of 15:25, 14 June 2026
Line 2:		Line 2:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	[https://store.steampowered.com/ Steam] is a digital distribution platform for video games, offering a vast library for purchase, download, and management. On NixOS, Steam is generally easy to install and use, often working "out-of-the-box". It supports running many Windows games on Linux through its compatibility layer, [[<tvar name=1>#Proton</tvar>~~\|Proton]]~~.<ref>https://store.steampowered.com/</ref>		<tvar name=steam>[https://store.steampowered.com/ Steam]</tvar> is a digital distribution platform for video games, offering a vast library for purchase, download, and management. On NixOS, Steam is generally easy to install and use, often working "out-of-the-box". It supports running many Windows games on Linux through its compatibility layer, <tvar name=proton>[[#Proton\|Proton]]</tvar>.<ref>https://store.steampowered.com/</ref>
	~~</translate~~>

	~~<translate>~~
	== Installation == <!--T:2-->		== Installation == <!--T:2-->

Line 22:		Line 20:
	<!--T:5-->		<!--T:5-->
	This provides the tools in your current shell without adding them to your system configuration. For <code>steamcmd</code> to work correctly for some tasks (like initializing for steam-tui), you might need to run it once to generate necessary files, as shown in the [[<tvar name=1>#steam-tui</tvar>\| steam-tui section]].		This provides the tools in your current shell without adding them to your system configuration. For <code>steamcmd</code> to work correctly for some tasks (like initializing for steam-tui), you might need to run it once to generate necessary files, as shown in the [[<tvar name=1>#steam-tui</tvar>\| steam-tui section]].
	~~</translate>~~

	~~<translate>~~
	==== System setup ==== <!--T:6-->		==== System setup ==== <!--T:6-->

Line 71:		Line 67:
	</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}

	{{note\|<translate><!--T:11--> If you are using a Steam Controller or a Valve Index, Steam hardware support is implicitly enabled by <code>programs.steam.enable {{=}} true;</code> which sets {{nixos:option\|hardware.steam-hardware.enable}} to true.</translate>}}		{{note\|<translate><!--T:11--> If you are using a Steam Controller or a Valve Index, Steam hardware support is implicitly enabled by <code>programs.steam.enable {{=}} true;</code> which sets <tvar name=steam_hardware_option>{{nixos:option\|hardware.steam-hardware.enable}}</tvar> to true.</translate>}}

	{{note\|<translate> If you are using the Steam Controller released in 2026, the Steam client has an additional dependency on hidapi, needed to correctly communicate with the controller. If you are seeing repeated errors about failed firmware updates, this is likely why. You can add the dependency directly to the Steam environment like so: <code>programs.steam.extraPackages {{=}} [pkgs.hidapi];</code></translate>}}		{{note\|<translate>If you are using the Steam Controller released in 2026, the Steam client has an additional dependency on hidapi, needed to correctly communicate with the controller. If you are seeing repeated errors about failed firmware updates, this is likely why. You can add the dependency directly to the Steam environment like so: <code>programs.steam.extraPackages {{=}} [pkgs.hidapi];</code></translate>}}

	<translate>		<translate>

	== Tips and tricks ==		== Tips and tricks ==

	=== Improving Performance ===		=== Improving Performance ===
	You can utilize [https://github.com/FeralInteractive/gamemode GameMode], a combination of a library and daemon for Linux that allows games to request a set of optimizations to be temporarily applied to the host operating system and/or a game process.<syntaxhighlight lang="nixos">
			You can utilize <tvar name=gamemode>[https://github.com/FeralInteractive/gamemode GameMode]</tvar>, a combination of a library and daemon for Linux that allows games to request a set of optimizations to be temporarily applied to the host operating system and/or a game process.
			</translate>

			<syntaxhighlight lang="nixos">
	programs.gamemode.enable = true;		programs.gamemode.enable = true;
	</syntaxhighlight>		</syntaxhighlight>

			<translate>
	=== Gamescope Compositor / "Boot to Steam Deck" === <!--T:13-->		=== Gamescope Compositor / "Boot to Steam Deck" === <!--T:13-->

Line 281:		Line 281:

	<!--T:58-->		<!--T:58-->
	For games running through Proton, the value should be <code>steam_app_<game_id></code> (where <code><game_id></code> matches the value after steam://rungameid/ on the <code>Exec</code> line). To automate this with [[Home Manager]] (executed on every rebuild):		For games running through Proton, the value should be <code>steam_app_<game_id></code> (where <code><game_id></code> matches the value after steam://rungameid/ on the <code>Exec</code> line). To automate this with <tvar name=hm>[[Special:MyLanguage/Home Manager\|Home Manager]]</tvar> (executed on every rebuild):
	</translate>		</translate>

Line 341:		Line 341:

	<!--T:36-->		<!--T:36-->
	When you restart Steam after an update, it starts the old version. ([https://github.com/NixOS/nixpkgs/issues/181904 #181904])		When you restart Steam after an update, it starts the old version. (<tvar name=issue>[https://github.com/NixOS/nixpkgs/issues/181904 #181904]</tvar>)
	A workaround is to remove the user files in <code>/home/<USER>/.local/share/Steam/userdata</code>. This can be done with <code>rm -rf /home/<USER>/.local/share/Steam/userdata</code> in the terminal or with your file manager. After that, Steam can be set up again by restarting.		A workaround is to remove the user files in <code>/home/<USER>/.local/share/Steam/userdata</code>. This can be done with <code>rm -rf /home/<USER>/.local/share/Steam/userdata</code> in the terminal or with your file manager. After that, Steam can be set up again by restarting.

Line 361:		Line 361:
	Note: If a game gets stuck on Installing scripts, check for a DXSETUP.EXE process and run it manually, then restart the game launch.		Note: If a game gets stuck on Installing scripts, check for a DXSETUP.EXE process and run it manually, then restart the game launch.

	==== Changing the driver on AMD GPUs <!-- this is not recommended due radv drivers performing better and generally more stable than amdvlk. My suggestion remove this section. source: https://forums.guru3d.com/threads/the-mesa-radv-amdvlk-thread.449774/ -->==== <!--T:40-->		==== Changing the driver on AMD GPUs <tvar name=comment><!-- this is not recommended due radv drivers performing better and generally more stable than amdvlk. My suggestion remove this section. source: https://forums.guru3d.com/threads/the-mesa-radv-amdvlk-thread.449774/ --></tvar>==== <!--T:40-->
	</translate>		</translate>

Line 398:		Line 398:

	<!--T:47-->		<!--T:47-->
	Gamescope may fail to start due to missing Xorg libraries. ([https://github.com/NixOS/nixpkgs/issues/214275 #214275]) To resolve this override the steam package to add them:		Gamescope may fail to start due to missing Xorg libraries. (<tvar name=issue>[https://github.com/NixOS/nixpkgs/issues/214275 #214275]</tvar>) To resolve this override the steam package to add them:
	</translate>		</translate>

Line 439:		Line 439:
	To find the vendor and product ID of a device <tvar name=usbutils>[https://search.nixos.org/packages?channel=unstable&show=usbutils&from=0&size=50&sort=relevance&type=packages&query=usbutils usbutils]</tvar> might be useful		To find the vendor and product ID of a device <tvar name=usbutils>[https://search.nixos.org/packages?channel=unstable&show=usbutils&from=0&size=50&sort=relevance&type=packages&query=usbutils usbutils]</tvar> might be useful

	=== Steam controller mouse input issues === ~~<!--T:52-->~~		=== Steam controller mouse input issues ===

	Mouse input on the controller may fail to take control of the visual cursor. In this instance, the input is still registered, but the cursor does not move. A fix for this is to preload Steam with extest. The Steam package already has an option for it:		Mouse input on the controller may fail to take control of the visual cursor. In this instance, the input is still registered, but the cursor does not move. A fix for this is to preload Steam with extest. The Steam package already has an option for it:

Malix: /* Gamescope HDR */ update: enableWsi option

2026-06-02T15:36:04Z

Gamescope HDR: update: enableWsi option

← Older revision		Revision as of 15:36, 2 June 2026
Line 129:		Line 129:

	<!--T:63-->		<!--T:63-->
	In order for HDR to work within gamescope, you need to separately ~~install~~ the <code>~~gamescope-wsi~~</code> ~~package alongside enabling the <code>gamescope</code> program.~~		In order for HDR to work within gamescope, you might need to separately enable the <code>enableWsi</code> option
	</translate>		</translate>

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">programs.gamescope = {
	programs.gamescope = {
	enable = true;		enable = true;
			enableWsi = true;
	capSysNice = false;		capSysNice = false;
	};		};</syntaxhighlight>
	~~environment.systemPackages = with pkgs; [~~
	~~gamescope-wsi # HDR might not work without this~~
	];
	</syntaxhighlight>

	<translate>		<translate>