Steam/ru: Difference between revisions

<languages/>

<div lang="en" dir="ltr" class="mw-content-ltr">

</div>

To temporarily use Steam-related tools like <code>steam-run</code> (for FHS environments) or <code>steamcmd</code> (for server management or tools like steam-tui setup) in a shell environment, you can run:

</div>

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

</div>

programs.steam = {

   enable = true;

};

# you might consider using the LTS kernel or a known stable version.

# boot.kernelPackages = pkgs.linuxPackages_lts; # Example for LTS

<div lang="en" dir="ltr" class="mw-content-ltr">

[https://news.ycombinator.com/item?id=41549030 Anecdata on kernel 6.10 issues]

</div>

<syntaxhighlight lang="nix">

   nixpkgs.config.allowUnfreePredicate = pkg: builtins.elem (lib.getName pkg) [

     "steam"

     "steam-unwrapped"

   ];

</syntaxhighlight>

}}

<div lang="en" dir="ltr" class="mw-content-ltr">

</div>

programs.steam = {

   enable = true; # Master switch, already covered in installation

   # Other general flags if available can be set here.

};

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

# programs.gamemode.enable = true;

<div lang="en" dir="ltr" class="mw-content-ltr">

</div>

<span id="Tips_and_tricks"></span>

== Советы и рекомендации ==

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

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

Gamescope can function as a minimal desktop environment, meaning you can launch it from a TTY and have an experience very similar to the Steam Deck hardware console.

</div>

<syntaxhighlight lang="nix">

# Clean Quiet Boot

};

# Gamescope Auto Boot from TTY (example)

   enable = true;

};

</syntaxhighlight>

=== steam-tui ===

<div lang="en" dir="ltr" class="mw-content-ltr">

If you want the steam-tui client, you'll have to install it. It relies on <code>steamcmd</code> being set up, so you'll need to run <code>steamcmd</code> once to generate the necessary configuration files.

First, ensure <code>steamcmd</code> is available (e.g., via <code>nix-shell -p steamcmd</code> or by adding it to <code>environment.systemPackages</code>), then run:

</div>

<syntaxhighlight lang="bash">

steamcmd +quit # This initializes steamcmd's directory structure

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

Then install and run `steam-tui`. You may need to log in within `steamcmd` first if `steam-tui` has issues:

</div>

<syntaxhighlight lang="bash">

# (Inside steamcmd prompt, if needed for full login before steam-tui)

# quit

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

After setup, <code>steam-tui</code> (if installed e.g. via <code>home.packages</code> or <code>environment.systemPackages</code>) should start fine.

=== FHS environment only ===

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

To run proprietary games or software downloaded from the internet that expect a typical Linux Filesystem Hierarchy Standard (FHS), you can use <code>steam-run</code>. This provides an FHS-like environment without needing to patch the software.

1. Install <code>steam-run</code> system-wide or user-specifically:

</div>

<syntaxhighlight lang="nix">

# In /etc/nixos/configuration.nix

];

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

2. If you need more flexibility or want to use an overridden Steam package's FHS environment:

</div>

<syntaxhighlight lang="nix">

# In /etc/nixos/configuration.nix

];

</syntaxhighlight>

=== Proton ===

<div lang="en" dir="ltr" class="mw-content-ltr">

You should be able to play most Windows games using Proton. If a game has a native Linux version that causes issues on NixOS, you can force the use of Proton by selecting a specific Proton version in the game's compatibility settings in Steam.

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

By default, Steam also looks for custom Proton versions in <code>~/.steam/root/compatibilitytools.d</code>. The environment variable <code>STEAM_EXTRA_COMPAT_TOOLS_PATHS</code> can be set to add other search paths.

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

Declarative install of custom Proton versions (e.g. GE-Proton):

</div>

<syntaxhighlight lang="nix">

programs.steam.extraCompatPackages = with pkgs; [

];

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

Manual management of multiple Proton versions can be done with ProtonUp-Qt:

</div>

<syntaxhighlight lang="nix">

environment.systemPackages = with pkgs; [

];

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

=== Overriding the Steam package ===

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

In some cases, you may need to override the default Steam package to provide missing dependencies or modify its build. Use the <code>programs.steam.package</code> option for this. Steam on NixOS runs many games in an FHS environment, but the Steam client itself or certain tools might need extra libraries.

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

Example: Adding Bumblebee and Primus (for NVIDIA Optimus):

</div>

<syntaxhighlight lang="nix">

programs.steam.package = pkgs.steam.override {

Example: Adding Xorg libraries for Gamescope (when used within Steam):

</div>

<syntaxhighlight lang="nix">

programs.steam.package = pkgs.steam.override {

   extraPkgs = pkgs': with pkgs'; [

     libpng

     libpulseaudio

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

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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

StartupWMClass=valheim.x86_64

</syntaxhighlight>

<span id="Troubleshooting"></span>

== Устранение неполадок ==

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

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

</div>

=== Steam is not updated ===

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

When you restart [[Steam]] after an update, it starts the old version. ([https://github.com/NixOS/nixpkgs/issues/181904 #181904])

=== Game fails to start ===

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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:

* Using the LD_LIBRARY_PATH from the nix/store steam script, with some additions, launch the game binary

</div>

<syntaxhighlight lang="bash">

LD_LIBRARY_PATH=~/.steam/bin32:$LD_LIBRARY_PATH:/nix/store/pfsa... blabla ...curl-7.29.0/lib:. ./Osmos.bin32 (if you could not patchelf the game, call ld.so directly with the binary as parameter)

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

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/ -->====

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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

</div>

<syntaxhighlight lang="nix">

hardware.graphics = {

};

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

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.

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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.

</div>

=== SteamVR ===

<div lang="en" dir="ltr" class="mw-content-ltr">

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>

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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:

</div>

<syntaxhighlight lang="nix">

programs.steam.package = pkgs.steam.override {

   extraPkgs = pkgs': with pkgs'; [

     libpng

     libpulseaudio

};

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

=== Udev rules for additional Gamepads ===

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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

</div>

<div lang="en" dir="ltr" class="mw-content-ltr">

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

</div>

<syntaxhighlight lang="nix">

   services.udev.extraRules = ''

   '';

</syntaxhighlight>

<div lang="en" dir="ltr" class="mw-content-ltr">

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

</div>

<span id="Known_issues"></span>

== Известные проблемы ==

<div lang="en" dir="ltr" class="mw-content-ltr">

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

</div>

<span id="References"></span>

== Ссылки ==