Steam: Difference between revisions

(7 intermediate revisions by 4 users not shown)

Line 6:

== Installation ==

~~== Installation ==~~

</translate>

==== Shell ====

~~==== Shell ====~~

</translate>

Line 29:

Line 27:

==== System setup ====

~~==== System setup ====~~

</translate>

Line 66:

Line 63:

== Configuration ==

~~== Configuration ==~~

</translate>

Line 80:

Line 76:

dedicatedServer.openFirewall = true; # For Source Dedicated Server hosting

# Other general flags if available can be set here.

~~# Tip: For improved gaming performance, you can also enable GameMode:~~

~~# programs.gamemode.enable = true;~~

};

# Tip: For improved gaming performance, you can also enable GameMode:

# programs.gamemode.enable = true;

</syntaxhighlight>

Line 92:

Line 88:

</syntaxhighlight>

== Tips and tricks ==

~~== Tips and tricks ==~~

</translate>

~~~~

=== Gamescope Compositor / "Boot to Steam Deck" ===

=== Gamescope Compositor / "Boot to Steam Deck" ===

</translate>

Line 107:

Line 101:

# Clean Quiet Boot

boot.kernelParams = [ "quiet" "splash" "console=/dev/null" ];

plymouth.enable = true;

boot.plymouth.enable = true;

programs.gamescope = {

Line 123:

Line 117:

settings = {

default_session = {

command = "${pkgs.gamescope}/bin/gamescope -W 1920 -H 1080 -f -e --xwayland-count 2 --hdr-enabled --hdr-itm-enabled -- steam -pipewire-dmabuf -gamepadui -~~steamos~~ > /dev/null 2>&1";

command = "${pkgs.gamescope}/bin/gamescope -W 1920 -H 1080 -f -e --xwayland-count 2 --hdr-enabled --hdr-itm-enabled -- steam -pipewire-dmabuf -gamepadui -steamdeck -steamos3 > /dev/null 2>&1";

user = "USERNAME_HERE";

};

Line 131:

Line 125:

=== steam-tui ===

~~=== steam-tui ===~~

</translate>

Line 157:

Line 150:

=== FHS environment only ===

~~=== FHS environment only ===~~

</translate>

Line 184:

Line 176:

</syntaxhighlight>

=== Proton ===

~~=== Proton ===~~

</translate>

Line 214:

Line 205:

</syntaxhighlight>

=== Overriding the Steam package ===

~~=== Overriding the Steam package ===~~

</translate>

Line 257:

Line 247:

=== Fix missing icons for games in GNOME dock and activities overview ===

== Troubleshooting ==

</translate>

GNOME uses the window class to determine the icon associated with a window. Steam currently doesn't set the required key for this in its .desktop files<ref>https://github.com/ValveSoftware/steam-for-linux/issues/12207</ref>, but you can fix this manually by editing the <code>StartupWMClass</code> key for each game's .desktop file, found under <code>~/.local/share/applications/</code>.

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).

For games running natively, the value should match the game's main executable.

For example, the modified .desktop file for Valheim looks like this:

</translate>

[Desktop Entry]

Name=Valheim

Comment=Play this game on Steam

Exec=steam steam://rungameid/892970

Icon=steam_icon_892970

Terminal=false

Type=Application

Categories=Game;

StartupWMClass=valheim.x86_64

</syntaxhighlight>

== Troubleshooting ==

</translate>

Line 267:

Line 284:

~~~~

=== Steam fails to start. What do I do? ===

=== Steam fails to start. What do I do? ===

</translate>

Line 276:

Line 292:

=== Steam is not updated ===

~~=== Steam is not updated ===~~

</translate>

Line 286:

Line 301:

~~~~

=== Game fails to start ===

=== Game fails to start ===

</translate>

Games may fail to start because they lack dependencies (this should be added to the script, for now), or because they cannot be patched. The steps to launch a game directly are:

* Patch the script/binary if you can

Line 300:

Line 314:

</syntaxhighlight>

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

</translate>

~~~~

==== Changing the driver on AMD GPUs ====

==== Changing the driver on AMD GPUs ====

</translate>

{{note|This is not recommended because radv drivers tend to perform better and are generally more stable than amdvlk.}}

Sometimes, changing the driver on AMD GPUs helps. To try this, first, install multiple drivers such as radv and amdvlk:

</translate>

Line 324:

Line 337:

</syntaxhighlight>

In the presence of both drivers, [[Steam]] will default to amdvlk. The amdvlk driver can be considered more correct regarding Vulkan specification implementation, but less performant than radv. However, this tradeoff between correctness and performance can sometimes make or break the gaming experience.

</translate>

To "reset" your driver to radv when both radv and amdvlk are installed, set either <code>AMD_VULKAN_ICD = "RADV"</code> or <code>VK_ICD_FILENAMES = "/run/opengl-driver/share/vulkan/icd.d/radeon_icd.x86_64.json"</code> environment variable. For example, if you start [[Steam]] from the shell, you can enable radv for the current session by running <code>AMD_VULKAN_ICD="RADV" steam</code>. If you are unsure which driver you currently use, you can launch a game with [https://github.com/flightlessmango/MangoHud MangoHud] enabled, which has the capability to show what driver is currently in use.

</translate>

=== SteamVR ===

~~=== SteamVR ===~~

</translate>

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>

</translate>

~~~~

=== Gamescope fails to launch when used within Steam ===

=== Gamescope fails to launch when used within Steam ===

</translate>

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:

</translate>

Line 366:

Line 377:

</syntaxhighlight>

~~~~

=== Udev rules for additional Gamepads ===

=== Udev rules for additional Gamepads ===

</translate>

In specific scenarios gamepads, might require some additional configuration in order to function properly in the form of udev rules. This can be achieved with <code>services.udev.extraRules</code>.

</translate>

The following example is for the 8bitdo Ultimate Bluetooth controller, different controllers will require knowledge of the vendor and product ID for the device:

</translate>

Line 383:

Line 393:

</syntaxhighlight>

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

</translate>

=== Known issues ===

~~=== Known issues ===~~

</translate>

"Project Zomboid" may report "couldn't determine 32/64 bit of java". This is not related to java at all, it carries its own outdated java binary that refuses to start if path contains non-Latin characters. Check for errors by directly starting local java binary within <code>steam-run bash</code>.

Resetting your password through the [[Steam]] app may fail at the CAPTCHA step repeatedly, with [[Steam]] itself reporting that the CAPTCHA was not correct, even though the CAPTCHA UI shows success. Resetting password through the [[Steam]] website should work around that.

</translate>

== References ==

~~== References ==~~

</translate>

[[Category:Applications]]

[[Category:Gaming]]

@@ Line 6: / Line 6: @@
 <translate>
-<!--T:2-->
+== Installation == <!--T:2-->
-== Installation ==
 </translate>
 <translate>
-<!--T:3-->
+==== Shell ==== <!--T:3-->
-==== Shell ====
 </translate>
@@ Line 29: / Line 27: @@
 <translate>
-<!--T:6-->
+==== System setup ==== <!--T:6-->
-==== System setup ====
 </translate>
@@ Line 66: / Line 63: @@
 <translate>
-<!--T:9-->
+== Configuration == <!--T:9-->
-== Configuration ==
 </translate>
@@ Line 80: / Line 76: @@
    dedicatedServer.openFirewall = true; # For Source Dedicated Server hosting
    # Other general flags if available can be set here.
-  # Tip: For improved gaming performance, you can also enable GameMode:
-  # programs.gamemode.enable = true;
 };
+# Tip: For improved gaming performance, you can also enable GameMode:
+# programs.gamemode.enable = true;
 </syntaxhighlight>
 <translate>
@@ Line 92: / Line 88: @@
 </syntaxhighlight>
 <translate>
-<!--T:12-->
+== Tips and tricks == <!--T:12-->
-== Tips and tricks ==
 </translate>
 <translate>
-<!--T:13-->
+=== Gamescope Compositor / "Boot to Steam Deck" === <!--T:13-->
-=== Gamescope Compositor / "Boot to Steam Deck" ===
 </translate>
 <translate>
@@ Line 107: / Line 101: @@
 # Clean Quiet Boot
 boot.kernelParams = [ "quiet" "splash" "console=/dev/null" ];
-plymouth.enable = true;
+boot.plymouth.enable = true;
 programs.gamescope = {
@@ Line 123: / Line 117: @@
    settings = {
      default_session = {
-       command = "${pkgs.gamescope}/bin/gamescope -W 1920 -H 1080 -f -e --xwayland-count 2 --hdr-enabled --hdr-itm-enabled -- steam -pipewire-dmabuf -gamepadui -steamos > /dev/null 2>&1";
+       command = "${pkgs.gamescope}/bin/gamescope -W 1920 -H 1080 -f -e --xwayland-count 2 --hdr-enabled --hdr-itm-enabled -- steam -pipewire-dmabuf -gamepadui -steamdeck -steamos3 > /dev/null 2>&1";
        user = "USERNAME_HERE";
      };
@@ Line 131: / Line 125: @@
 <translate>
-<!--T:15-->
+=== steam-tui === <!--T:15-->
-=== steam-tui ===
 </translate>
 <translate>
@@ Line 157: / Line 150: @@
 <translate>
-<!--T:19-->
+=== FHS environment only === <!--T:19-->
-=== FHS environment only ===
 </translate>
 <translate>
@@ Line 184: / Line 176: @@
 </syntaxhighlight>
 <translate>
-<!--T:22-->
+=== Proton === <!--T:22-->
-=== Proton ===
 </translate>
 <translate>
@@ Line 214: / Line 205: @@
 </syntaxhighlight>
 <translate>
-<!--T:27-->
+=== Overriding the Steam package === <!--T:27-->
-=== Overriding the Steam package ===
 </translate>
 <translate>
@@ Line 257: / Line 247: @@
 <translate>
-<!--T:31-->
+=== Fix missing icons for games in GNOME dock and activities overview === <!--T:56-->
-== Troubleshooting ==
+</translate>
+<translate>
+<!--T:57-->
+GNOME uses the window class to determine the icon associated with a window. Steam currently doesn't set the required key for this in its .desktop files<ref>https://github.com/ValveSoftware/steam-for-linux/issues/12207</ref>, but you can fix this manually by editing the <code>StartupWMClass</code> key for each game's .desktop file, found under <code>~/.local/share/applications/</code>.
+<!--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).
+<!--T:59-->
+For games running natively, the value should match the game's main executable.
+<!--T:60-->
+For example, the modified .desktop file for Valheim looks like this:
+</translate>
+<syntaxhighlight lang="desktop">
+[Desktop Entry]
+Name=Valheim
+Comment=Play this game on Steam
+Exec=steam steam://rungameid/892970
+Icon=steam_icon_892970
+Terminal=false
+Type=Application
+Categories=Game;
+StartupWMClass=valheim.x86_64
+</syntaxhighlight>
+<translate>
+== Troubleshooting == <!--T:31-->
 </translate>
@@ Line 267: / Line 284: @@
 <translate>
-<!--T:33-->
+=== Steam fails to start. What do I do? === <!--T:33-->
-=== Steam fails to start. What do I do? ===
 </translate>
 <translate>
@@ Line 276: / Line 292: @@
 <translate>
-<!--T:35-->
+=== Steam is not updated === <!--T:35-->
-=== Steam is not updated ===
 </translate>
 <translate>
@@ Line 286: / Line 301: @@
 <translate>
-<!--T:36-->
+=== Game fails to start === <!--T:37-->
-=== Game fails to start ===
 </translate>
 <translate>
-<!--T:37-->
+<!--T:38-->
 Games may fail to start because they lack dependencies (this should be added to the script, for now), or because they cannot be patched. The steps to launch a game directly are:
 * Patch the script/binary if you can
@@ Line 300: / Line 314: @@
 </syntaxhighlight>
 <translate>
-<!--T:38-->
+<!--T:39-->
 Note: If a game gets stuck on Installing scripts, check for a DXSETUP.EXE process and run it manually, then restart the game launch.
 </translate>
 <translate>
-<!--T:39-->
+==== 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 <!-- 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/ -->====
 </translate>
 {{note|This is not recommended because radv drivers tend to perform better and are generally more stable than amdvlk.}}
 <translate>
-<!--T:40-->
+<!--T:41-->
 Sometimes, changing the driver on AMD GPUs helps. To try this, first, install multiple drivers such as radv and amdvlk:
 </translate>
@@ Line 324: / Line 337: @@
 </syntaxhighlight>
 <translate>
-<!--T:41-->
+<!--T:42-->
 In the presence of both drivers, [[Steam]] will default to amdvlk. The amdvlk driver can be considered more correct regarding Vulkan specification implementation, but less performant than radv. However, this tradeoff between correctness and performance can sometimes make or break the gaming experience.
 </translate>
 <translate>
-<!--T:42-->
+<!--T:43-->
 To "reset" your driver to radv when both radv and amdvlk are installed, set either <code>AMD_VULKAN_ICD = "RADV"</code> or <code>VK_ICD_FILENAMES = "/run/opengl-driver/share/vulkan/icd.d/radeon_icd.x86_64.json"</code> environment variable. For example, if you start [[Steam]] from the shell, you can enable radv for the current session by running <code>AMD_VULKAN_ICD="RADV" steam</code>. If you are unsure which driver you currently use, you can launch a game with [https://github.com/flightlessmango/MangoHud MangoHud] enabled, which has the capability to show what driver is currently in use.
 </translate>
 <translate>
-<!--T:43-->
+=== SteamVR === <!--T:44-->
-=== SteamVR ===
 </translate>
 <translate>
-<!--T:44-->
+<!--T:45-->
 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>
 </translate>
 <translate>
-<!--T:45-->
+=== Gamescope fails to launch when used within Steam === <!--T:46-->
-=== Gamescope fails to launch when used within Steam ===
 </translate>
 <translate>
-<!--T:46-->
+<!--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:
 </translate>
@@ Line 366: / Line 377: @@
 </syntaxhighlight>
 <translate>
-<!--T:47-->
+=== Udev rules for additional Gamepads === <!--T:48-->
-=== Udev rules for additional Gamepads ===
 </translate>
 <translate>
-<!--T:48-->
+<!--T:49-->
 In specific scenarios gamepads, might require some additional configuration in order to function properly in the form of udev rules. This can be achieved with <code>services.udev.extraRules</code>.
 </translate>
 <translate>
-<!--T:49-->
+<!--T:50-->
 The following example is for the 8bitdo Ultimate Bluetooth controller, different controllers will require knowledge of the vendor and product ID for the device:
 </translate>
@@ Line 383: / Line 393: @@
 </syntaxhighlight>
 <translate>
-<!--T:50-->
+<!--T:51-->
 To find the vendor and product ID of a device [https://search.nixos.org/packages?channel=unstable&show=usbutils&from=0&size=50&sort=relevance&type=packages&query=usbutils usbutils] might be useful
 </translate>
 <translate>
-<!--T:51-->
+=== Known issues === <!--T:52-->
-=== Known issues ===
 </translate>
 <translate>
-<!--T:52-->
+<!--T:53-->
 "Project Zomboid" may report "couldn't determine 32/64 bit of java". This is not related to java at all, it carries its own outdated java binary that refuses to start if path contains non-Latin characters. Check for errors by directly starting local java binary within <code>steam-run bash</code>.
+<!--T:55-->
 Resetting your password through the [[Steam]] app may fail at the CAPTCHA step repeatedly, with [[Steam]] itself reporting that the CAPTCHA was not correct, even though the CAPTCHA UI shows success. Resetting password through the [[Steam]] website should work around that.
 </translate>
 <translate>
-<!--T:53-->
+== References == <!--T:54-->
-== References ==
 </translate>
 [[Category:Applications]]
 [[Category:Gaming]]