UnsupportedShow Details
UnknownNative Support
Although this game has a Linux-native build available, Steam does not list it as having Linux support. This can happen if a game has an unofficial, unfinished, or unsupported build. You may need to force Steam to enable Proton for the game in order to run properly.
Native Linux build does not support Windows saves so you'll need to start from scratch or use Proton
SteamVR crashed during the initial Eli's call when using the native Linux build
Native Linux build did not work very well compared to the Windows build under Proton
- Download ALVR Launcher for Linux.
- Install SteamVR. (If not already installed)
- Install Half-Life: Alyx. (If not already installed)
- Make sure your headset is connected to the same network as your PC.
- Use Meta Horizon app on mobile device to enable developer mode on headset. (Meta headsets only)
- Launch ALVR.
- Launch SteamVR from within ALVR on the PC.
- Launch ALVR in your headset.
- Switch to Steam in the VR interface. (On Quest 2, quest button on left controller, then click the Steam icon.)
- Launch Half-Life: Alyx.
- Play out of the box.
Audio only plays from the PC speakers, and not the headset speakers.
Subtitles are not rendered, when enabled in-game.
Game saves from Windows do not transfer to Linux, so you have to start from the beginning on first launch.
Performance and lag can vary, depending on network/LAN congestion.
DRI_PRIME=1 %command%
Audio wont play through the vr headset but from the desktop.
You will have to switch to the OrionMoonclaw's priorites fork of OpenComposite to stop snap rotating when pressing a or x.
ALVR + SteamVR is borked and crashes during level transistions notably the train sequence when you get your first gun, however Envsion + WiVRn + OpenComposite (OrionMoonclaw's priorities fork) is soild and has little to no issues. It may give you an error for the fork, but this is a simple fix by going into the OpenComposite directory and running git submodules update --recursive.
Tried playing the game on quest 2 + WiVRn. but everything would glitch out and disappear.
PRESSURE_VESSEL_FILESYSTEMS_RW=$XDG_RUNTIME_DIR/wivrn/comp_ipc:/var/lib/flatpak/app/io.github.wivrn.wivrn %command%
Try using Windows VM
%command% -novid
Tried with Oculus Quest 2 (wireless) on SteamVR + ALVR, the game keeps stuttering every now and then. After switching to Envision + WiVRN + OpenComposite I noticed increased performance and stability. For OpenComposite, make sure to switch to the "priorities" branch of OrionMoonclaw's fork which fixes some issues with the controls. I don't recommend the native version of the game due to frequent crashes and the subtitles not working.
SteamVR will almost always result in the game crashing on loading screens.
On AMD hardware in particular it appears the game will always crash on loading screens when trying to use SteamVR however OpenComposite seems to be a simple fix to this, Envision is a nice simple GUI solution that most people should be able to use. Just make sure to start the game once with SteamVR (ALVR is a common way to do this if you have a Quest) and then you can start the game with OpenComposite. I highly suggest using the priority branch of OpenComposite otherwise there is a control mapping issue that makes the eject button also make you turn.
It runs basically fine via ALVR, save for the graphical glitches, which are more annoying than game-ruining.
gamemoderun %command%
Frequent flashes as if the scene lighting was suddenly brighter across the entire display
Saves do not carry between the Linux and Windows versions
Do not waste your time running the native Linux version - it ships with old libraries so audio is broken and the game invariably crashed for me when getting on the train after the tutorial. Vulkan generally causes the crashing also. Using Windows version through Proton-GE and DX11 gave a smooth-ish experience.
-novid -nowindow
Stutters every now and then.
The game crashes on loading screens nearly every time, taking SteamVR down with it (error code -203), and causing a GPU driver timeout, often requiring me to reboot my computer.
I've been tinkering with this for days, trying every possible configration under the sun, and I have yet to be able to resolve these frequent and consistent crashes at loading screens.
I'm still not sure if it's an issue with the game, SteamVR, video drivers, or a combination of all three that is causing it.
Crashes after getting the gun and entering the train
Using a Quest 3S with ALVR either via Proton or Native the game crashes after entering the train with an amdgpu timeout - just like the report from user "Note" who claims to have fixed it with a "boot parameter" but doesn't specify which......
the game will not launch nativly without replacing game/bin/linuxsteamrt64/libtcmalloc_minimal.so.0 with the system version located at /lib/x86_64-linux-gnu/libtcmalloc_minimal.so.4.5.9, make sure to keep the old name and the game should run just fine.
Use the linux Native build, you will not have a good expierience without it.
AMD_VULKAN_ICD=amdvlk DRI_PRIME=1 %command%
"DefaultRenderSystemOption" "-dx11" ~/.local/shar…/Half-Life Alyx/game/hlvr/cfg/boot.vcfg
Very stable no issue I even play some return to rapture workshop map
Tried SteamVR beta
SteamVR crashes with code -203 on the train right after you get your first gun
The game starts and runs smoothly, but can't be played right after you get your first gun - SteamVR crashes with error code -203 and no other message.
I tried SteamVR beta, nothing changes. I just can't paly it past this part at all.
Hyprland v0.45.0-60-g55ec8bd5 built against aquamarine 0.5.0, Pico 4 wireless over ALVR
Played on a Quest 2 via ALVR
DRI_PRIME=1 %command%
I used ALVR + Steam VR beta, I used to have a bug where my GPU would crap out when I got on the train part, however I resolved that issue by changing a boot parameter.
DRI_PRIME=1 %command%
Crashes at the part when you get on the train to save Eli Vance
I tried multiple setups and configurations, and to no avail. The game crashes on the windows version and on the native version when I enter the train.
It's only playable until the train part, the Linux version has massive fps drops, and both crash as after the tutorial.
-novid -safe-mode
I had to change the output device in pavucontrol
Sometime everything goes super bright
Heavy framedrops with KDE Palsma Wayland, but gone with x11
Everything runs smooth until the right after the tutorial, then everything goes black and stays black.
Can't recommend like this. I probably have to set up dual booting only for vr even though valve says the valve index and Half Life Alyx works with Linux (Arch, Plasma Wayland, I normally use this).
During some of the chapter loading the game crashes.
I initially started the game with the latest GE-Proton available at the time of writing (9-16). However, I was facing some weird graphical issues regarding lighting in the game. Then I switched to the native Linux version, and it was much better. I did face 1-2 crashes when the game transitioned from one chapter to another. For those chapters, I just temporarily enabled Steam Play with the latest GE-Proton, played a little bit, saved the game, and went back to the native Linux version. I used ALVR + SteamVR Beta. It worked great.
It works perfectly with my Valve Index. I used Plasma Wayland to play it.
Proton 9.0-2 (current as of this writing), works OOTB
FWIW I'm using the NoVR mod and the game is playing with Vulkan and DX11 options—there's slight stutters with Vulkan so I'd recommend leaving DX11 rendering API default. Otherwise an OOTB experience.
-novid -safe_mode
With the different options, don't see the Valve Logo Video and the charging part
Had to reinstall Steam in order to have my Knuckles working again on Alyx. Pain in the A** to make it work but now it is good
-safe_mode
It sometimes crashes when entering a loading screen, it also crashes if vulcan is used.
works great, majority of issues were caused by me misussing alvr
Arch + Hyprland + ALVR + Pico 4. Surprisingly smooth and working as expected. Wireless mode.
Maybe it's just me but the newer versions of Proton-GE or newer Nvidia drivers made it much more smoother since Proton-GE was always in my compatibility settings and HL:A was never forced to use compatibility settings.
Will randomly crash at loading screens. I have not had a single session where I did not crash at least once.
Subtitles do not seem to work.
%command% -language russian
Crashes in native linux mode with Vulkan API
Played with ALVR 20.8.1 Had to switch SteamVR to previous release and set SteamVR launch options to ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%
Using ALVR + Quest 2. When launched with the default compatibility tool, I was stuck with the "Up Next" tile in the Steam VR Void. The game didn't launch. Simply forcing Proton Experimental immediately got me up and running. Performance is comparable to what I experience on Windows 10.
ALVR + SideQuest
do not start with vulkan api
My harware: PC + Quest 3 My software: ALVR + SideQuest + usb 3.1 cable you can easily find how to use ALVR and SideQuest i can give you guy
SteamVR cannot detect Quest 3 without ALVR (SideQuest i used for usb connection because wi-fi 5Ggz not enough strengh signal in my area)
only dx11vr (vulcan crash my system)
Playable with work
Noticable loss in performance compared to Windows, but still runs at a playable framerate.
Played with Quest 1, ALVR, and ADBForwarder for wired connection. I had to manually start ADB with "./ADB start-server", then launch ADBForwarder. Connection is inconsistent, but once connected it has been stable. I had to manually add a connection in ALVR to get my headset to show, then change stream protocal to TCP, see ALVR's wired connection page for a guide. ALVR's lowest resolution preset was higher than the Quest 1's resolution, so I had to manually set resolution. Steam overlay in game is inconsistent, but can work.
Small lag on input, probably related to Oculus Link than Alyx itself
When trying to open the native version the game starts and closes following. Windows version with Proton worked very good aside for a very small input lag that probably is more related to Oculus Link than to Alyx itself.
Ran with a Oulus Quest 2 and ALVR for about 2 hours (the battery life of the quest 2) no problems, had a lot of fun.
removed libmpg123.so.0 from game directory to get sound on nvidia
removing libmpg123.so.0 made audio work
runs perfectly using ALVR on my quest 2 after the file change to get audio working
I don't have a VR headset anymore but the No VR mod works perfect using Proton experimental, you can play the whole game with no problem
On arch linux, to play native version you need to replace game library with system one, Proton version runs fine, but seems to lag
gamemoderun %command%
cp -f /lib/libtcmalloc_minimal.so.4.5.14 ~/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_environments/game/bin/linuxsteamrt64/libtcmalloc_minimal.so.0
After setting up NoVR with the tutorial for Deck on the NoVR mod FAQ page, the game runs at around 50fps, which I capped to 30.
-novr -vsync +vr_enable_fake_vr 1
I did use the lowest performance settings.
works fine but fedora linux will need to remove a file called libmpg123.so.0 from the game folder to get sound
-novid -nowindow
sound wont work on fedora linux if you have a Nvidia card, to fix this you mist remove a file called "libmpg123.so.0" in the games directory, then sound will work.
on
