How to install the GAMMA modpack on a Valve Steam Machine with STALKER GAMMA COMMANDER 1.3.1, including the workarounds this hardware needs. Follow it in order and tick each step as you finish. The last section shows how to remove all of it again.
An unofficial community guide. It isn't affiliated with Valve, the GAMMA team or COMMANDER's developer. It was tested on one Steam Machine in October 2026, so menu names may differ slightly after updates.
Do these in order. Your ticks are saved in this browser only.
On the 1.3.1 release page, download STALKER-GAMMA-COMMANDER-1.3.1-x86_64.AppImage into Downloads. This guide was tested with 1.3.1. Newer releases, including the "Unstable" pre-releases, may change the steps.
Open Konsole, then move the file somewhere permanent and make it runnable:
mkdir -p ~/Applications && mv ~/Downloads/STALKER-GAMMA-COMMANDER-1.3.1-x86_64.AppImage ~/Applications/ && chmod +x ~/Applications/STALKER-GAMMA-COMMANDER-1.3.1-x86_64.AppImageOpen Discover, search Protontricks and install it. Or install it from Konsole:
flatpak install -y flathub com.github.Matoking.protontricksThe Discover version has no plain protontricks command, so COMMANDER can't find it. Add a two-line helper that it can find:
mkdir -p ~/.local/bin && printf '#!/bin/sh\nexec flatpak run com.github.Matoking.protontricks "$@"\n' > ~/.local/bin/protontricks && chmod +x ~/.local/bin/protontricksCheck it works:
~/.local/bin/protontricks --versionExpect a line like protontricks (1.x.x).
Why: COMMANDER won't install the game's runtimes until it finds protontricks, even though the GE-Proton setup never actually runs it. Don't install system Wine; you don't need it.
In Dolphin, open Applications in your home folder and double-click the AppImage. It opens the normal desktop window; it won't offer Deck Mode on its own here.
On Play, click Install GE-Proton and wait until the button reads GE-Proton installed ✓.
Do this before step 6. Each Proton version keeps its own Windows setup, so the runtimes in step 6 need to go into this one.
Click Install → Install GAMMA. It installs Anomaly first, then every GAMMA addon, and shows progress for each one.
Keep the machine awake. The desktop window doesn't stop the Steam Machine from sleeping during the download. Turn off automatic sleep in System Settings → Power Management first. Or run the install from Deck Mode's Install tab (press X), which keeps the machine awake on its own.
The desktop window's Install Dependencies button stops with "Wine is required". That's a known gap on SteamOS, so use Deck Mode's button instead:
It installs winetricks, then umu-run (both into ~/.local/bin), then these Windows runtimes through GE-Proton:
d3dcompiler_43d3dcompiler_47d3dx10d3dx11_43d3dx9quartzdx8vbvcrun2022On Play, check that the runner shows GE-Proton, then click Launch Game. The first launch downloads Steam's Linux runtime, so give it a few minutes before the game window appears.
If it reaches the main menu, quit the game normally. Problems are easier to fix here than in Game Mode.
Nothing happens, or Mod Organizer closes after a few seconds? On GE-Proton 11-9 that's a crash in Proton's VR support. The fix is one command: see Mod Organizer closes straight away under troubleshooting.
Click Settings → Steam → Add COMMANDER to Steam. Steam closes, the shortcuts are written, and Steam starts again. You get two entries: STALKER COMMANDER and STALKER COMMANDER DECK.
Desktop Mode only. This closes Steam, which would end a Game Mode session. COMMANDER can't tell it's in Game Mode on a Steam Machine, so it won't stop you.
In Steam, right-click STALKER COMMANDER DECK → Properties, and replace Launch Options with:
SteamDeck=1 %command% --deckWhy: COMMANDER only recognises the Steam Deck's hardware names, and the Steam Machine reports a different one. SteamDeck=1 tells it it's on SteamOS, so Deck Mode opens full screen on your TV.
If the game hangs, press the Steam button to get back, open COMMANDER's Play tab and choose Force Stop Game.
COMMANDER reads the controller directly, so Steam's default controller layout works in Game Mode.
| Button | Action |
|---|---|
| D-pad / left stick | Move (hold to repeat) |
| A | Select or toggle |
| B | Back |
| X | The screen's main action |
| Y | The screen's second action, or search |
| L1 / R1 | Previous / next tab |
| L2 / R2 | Page up / down |
| ☰ Menu | Play GAMMA, Exit Deck Mode or Quit |
| ⧉ View | Controls help |
| Screen | X | Y |
|---|---|---|
| Dashboard | Whatever the banner says: Play, Install, Resume or Update | Re-check |
| Play | Play GAMMA (Force Stop while running) | Open Mod Organizer |
| Mods | Category menu | Search |
| Update | Check or apply updates | Show changes |
| Install | Install or resume GAMMA | Install dependencies |
wrapper exited code=3, and files named ModOrganizer-2.5.2-*.dmp appear in ~/Games/GAMMA/gamma.wineopenxr) crashes when no VR headset software is installed, and takes Mod Organizer down with it. GAMMA doesn't use VR, so it's safe to turn off.ls ~/.local/share/Steam/compatibilitytools.dGE-Proton11-9-x86_64, change that part of the next command to match. The command turns the VR component off in the game's Wine prefix, so every launch picks it up and you don't need to change COMMANDER's settings.WINEPREFIX=~/Games/umu/umu-default PROTONPATH=~/.local/share/Steam/compatibilitytools.d/GE-Proton11-9-x86_64 ~/.local/bin/umu-run reg add 'HKCU\Software\Wine\DllOverrides' /v wineopenxr /d '' /freg: The operation completed successfully. To check it stuck:grep '"wineopenxr"' ~/Games/umu/umu-default/user.reg"wineopenxr"="". Then click Play again.reg add onwards with reg delete 'HKCU\Software\Wine\DllOverrides' /v wineopenxr /f.--version check from step 2, then try again.COMMANDER was built for the Steam Deck, which runs the same SteamOS. Two parts of it don't recognise a Steam Machine yet.
SteamDeck=1, which may not be set on a Steam Machine. Step 9 sets it.Removes GAMMA, COMMANDER and every tool the setup added. SteamOS itself needs no undoing, because the setup never changed it. Work in Desktop Mode and in this order: steps 1 and 2 need COMMANDER, so do them before you delete it. Copy the commands exactly rather than retyping them.
Open COMMANDER and click Utilities → Full Uninstall. In Deck Mode it's on the Utilities tab, under Uninstall.
user.ltx and MCM settings first, to ~/.local/share/stalker-gamma-commander/backups. If that backup fails, it deletes nothing. Mods you added yourself aren't backed up.More than one profile? Switch to each one on the Profiles page and run Full Uninstall again for it.
On Play, click Manage GE-Proton…, then Remove All Unused, or select a build and click Remove Selected. COMMANDER won't remove a build that a Steam game is set to use.
Skip this if you use GE-Proton for other games.
If you already deleted COMMANDER, remove the builds from Konsole instead. Steam stops listing them after its next restart:
rm -rf ~/.local/share/Steam/compatibilitytools.d/GE-Proton*In your Steam library, right-click STALKER COMMANDER → Manage → Remove non-Steam game from your library. Do the same for STALKER COMMANDER DECK. Its launch option from setup step 9 goes with it.
"Add to Steam" also saved a backup of your old shortcut list. Delete it with:
rm -f ~/.local/share/Steam/userdata/*/config/shortcuts.vdf.gammagui.bakQuit COMMANDER first. Then delete the app:
rm -f ~/Applications/STALKER-GAMMA-COMMANDER-*-x86_64.AppImageIts settings, profiles and logs:
rm -rf ~/.config/stalker-gammaIts app-menu entry, icon, and the start-at-login entry if you turned that on:
rm -f ~/.local/share/applications/stalker-gamma-commander.desktop ~/.local/share/icons/stalker-gamma-commander.png ~/.config/autostart/stalker-gamma-commander.desktopIf you made desktop shortcuts from the Play page, delete them from your Desktop too.
The game's Windows setup, with the VC++ and DirectX runtimes from setup step 6, survives Full Uninstall on purpose. Delete it:
rm -rf ~/Games/umu/umu-defaultThis is umu's default prefix. If you run other Windows programs with umu-run yourself, they may use it too. If you changed the prefix on COMMANDER's Play page, delete that folder instead.
Then remove the folders that are now empty. rmdir only deletes empty folders, so it can't remove anything you still keep in them. If you picked a different base folder in setup step 3, use that path instead of ~/Games/GAMMA.
rmdir ~/Games/GAMMA ~/Games/umu ~/Games 2>/dev/nullKeep any of these you use for other games. On a fresh SteamOS, all of them came from this setup.
The three commands in ~/.local/bin, including the Protontricks helper from setup step 2:
rm -f ~/.local/bin/umu-run ~/.local/bin/winetricks ~/.local/bin/protontricksThe Linux runtime umu downloaded on the first launch, and winetricks' download cache:
rm -rf ~/.local/share/umu ~/.cache/winetricksThe Protontricks app itself. The second command removes Flatpak runtimes that no installed app needs any more:
flatpak uninstall -y com.github.Matoking.protontricks && flatpak uninstall -y --unusedOr remove Protontricks in Discover, under Installed.
Full Uninstall put your saves and game settings here. Only delete them if you're sure you won't come back to GAMMA. To keep a copy in Documents first:
cp -r ~/.local/share/stalker-gamma-commander/backups ~/Documents/gamma-save-backupsThen delete COMMANDER's data folder:
rm -rf ~/.local/share/stalker-gamma-commanderIf you turned off automatic sleep in setup step 5, turn it back on in System Settings → Power Management.
Then list anything that's still there:
ls -d ~/Games/GAMMA ~/Games/umu ~/Games/proton ~/.config/stalker-gamma ~/.local/share/stalker-gamma-commander ~/.local/share/umu ~/.local/bin/umu-run ~/.local/bin/winetricks ~/.local/bin/protontricks ~/.local/share/Steam/compatibilitytools.d/GE-Proton* 2>/dev/nullNo output means everything is gone. Anything listed is still there, which is fine if you kept it on purpose, such as GE-Proton or your save backups. ~/Games/proton only exists if you ever picked a Steam Proton runner; delete it with rm -rf ~/Games/proton if it shows up.