VerifiedShow Details
Unknown
-novid -nojoy -nosteamcontroller -vulkan
There are minor graphical bugs, but there's nothing to worry about.
Since the game works on both Native and Proton, you're good playing this gem on Linux! Also, it is recommended to add -vulkan in the launch options for better experience (and also performance).
Played the entire game using the Windows version, and didn't encounter any serious issues!
Everything worked flawlessly, and even could play the Workshop maps. On top of that, this game is a gem!
gamemoderun %command% -novid -vulkan
adding -vulkan to launch options seemed to be standard procedure for the native linux version, so i havent tried without it as the game ran perfectly stable from start to finish (including both episodes) to the point i could 100% the achievements for it
Windows version installs and plays without issues
I did a whole playthrough using the windows version. It ran very smoothly. The game is, of course, a real gem.
gamemoderun %command%
Runs great native and with proton
Download and Play
The native version works perfectly well.
gamemoderun %command% -vulkan
If your game crashes after starting a new game or loading a save file add -vulkan to launch options and it will fix the issue
-language english -audiolanguage english +cc_lang english
The launch options I used were just to set the game to English as it ignores the language you set in the properties window and uses whatever your Steam client is set to, other than that I was able to play through the entire HL2 main game and Episode One without any issues at all.
-language english -audiolanguage english +cc_lang english
The launch options I used were just to set the game to English as it ignores the language you set in the properties window and uses whatever your Steam client is set to, other than that I was able to play through the entire HL2 main game without any issues at all.
flawless native build
No Proton required, it's a linux-native game and it runs just fine.
mangohud %command% -vulkan -windowed -noborder
My friends keep telling me that HL2 looks weird compared to the Windows native version
Same problem with every -vulkan option on source games in Xorg that doesn't happen on Wayland. HL2 freezes the entire screen in fullscreen mode requiring the parameters "-noborder -windowed" and rebooting
If you play this game on vulkan make sure you use -noborder -windowed especially on xorg otherwise you might be hardlocked and be require to reboot your system.
-vulkan
runs buttery smooth with -vulkan added to the launch options. you should probably use gamemoderun %command% too
game freezes and craches at the black screen when trying to start a new game.
gamemoderun %command%
i already had lib32-nvidia-dkms installed
Native support and works right out of the box. On Fedora, you will have to let SELinux have an exception for `hl2_linux`.
If you are encountering issues with audio on Fedora, try running this command.
sudo ausearch -c 'hl2_linux' --raw | audit2allow -M my-hl2linux
sudo semodule -i my-hl2linux.pp
I mentioned in tickering on the terminal commands, after that it works.
Half-Life works right out of the box because it has native support. Some audio is missing, but after setting an exception for SELinux, it works. In a worse scenario, you can run the Windows version with Proton or Wine, but I haven't dealt with that issue.
Just works. Everyone should play this masterpiece especially after the 20th anniversary update.
-novid -vulkan
Use -vulkan in launch options for better performance
Works perfectly. Maybe a tad sluggish compared to native but reliably works.
Linux native works fine for Half Life 2 but not for Episode 1 as it has shadow glitches and doesn't play the intro properly. I played Episode 1 & 2 with Proton.
As soon as you take the first steps towards the fisherman after you spawn, it freezes, loops the audio and just don't get out of it.
-w 1280 -h 720
I have already waited a couple of minutes to see if it de-freezes after some time. It acts like this with some versions of Proton too.
Proton manages to get almost 1to1 with W10, but sometimes it just bugs out. Source doesn't play that nice with Proton for some reason...
-w 1280 -h 720
Sometimes it crackles while it slows down a little for a moment, it's like it's caching something...
Sometimes the water's rendering "skips" with a white zone where the reflection "gets stuck" instead of moving with the camera.
Framerate caps at screen's refresh rate.
THIS is the most stable Proton version for this game. I read Lost Coast runs natively, but that's not my goal, I want to figure out how to make Source Engine games perform AS WELL as they do on Windows 10 before oct2025 because I don't like my hardware working harder to get the same or lower results.
"Typical gamers" don't fixate on hardware or performance. Most just drop €1000 or more on either PC or Console and as long as it looks good and the FPS is enough for the action (BG3 technically needs only 30 stable) they'll be happy with it, even if the rig may waste some power for the same performance. I instead want to understand the problems with Source and Proton and fix them.
- Bound L stick press to sprint toggle
- Boung R stick press to crouch toggle
- Bound L bumper to do the following: L press selects grenade, L hold executes fire command.
Sometimes after waking the game up from sleep the whole Deck's audio starts crackling. It is necessary to reboot the device.
Minor shadow glitches
Works perfectly out of the box.
use the "-vulkan" launch argument to enable DXVK instead of the older ToGL layer
Use Vulkan to increase performance
-vulkan
On Arch Linux you must install lib32-nvidia-utils from the multilib repo. The game would not launch for me otherwise.
The pacman multilib repository is not enabled by default. You can do that in /etc/pacman.conf with steps here on the Arch Wiki
Apparently you can also install this without enabling multilib by using an AUR helper.
Works native out of the box. After downloading let the vulkans shaders compile I had to restart my PC in order to launch the game (because it wouldn't launch). After that it works perfectly.
I did not pick up that can
Because it works ig
Works Natively out of the box
Works Natively out of the box. Didn't need to tinker
Given that proton-cachyos is pretty much the standard Proton version in the Distro I'll see this as a non tinker report
Since CachyOS has the DLSS Frame Gen fixes already applied the HUD is prone to heavy ghosting. It's amazing that we have Frame Gen now, but isn't fully there yet. Just deactivate it and you are good to go!
Game runs also well with normal Proton. GE-Proton and - in this case - proton-cachyos will just give it that extra boost in performance. It basically feels like a native game: Easy plug and play. Love playing it under Linux on my big rig :)
Fantastic ! Running this game on Linux is awesome ! Linux gaming is growing every year, hopefully we will not need MS Windows for gaming!
I'm switching from MS Windows gaming to Linux gaming, and so far DICE is the only one disappointing. Other than that, EXCELLENT experience with Linux gaming with Steam (native or using Proton). Keep up the FANTASTIC JOB Steam!
SteamDeck=1 gamemoderun %command% -vulkan nosteamcontroller -novid -nojoy
Steam Input is a bit fiddly occasionally. Usually opening the game settings and switching Steam Input disabled and the enabled again fixes this. Might need to do it couple of times but it's rare.
Works without issues out of the box if playing with mouse and keyboard.
-novid -vulkan
SteamInput produces some weirdness when playing simultaneously with KB/M and controller. Ladders can't be climbed with one input method if mounted with the other, and switching between input methods can cause you to become stuck on the ladder.
One part of the game lets you control an industrial crane. This sequence does not work properly with Steam Input, as you can't move it back or forward, only left and right.
Disabling Steam Input and enabling the in-game legacy controller input (Settings -> Mouse -> "Enable the gamepad") fixes all of these issues, but you don't get fancy button prompts or the ability to drive with the gas/brake on triggers.
The issues seem to stem from using a real mouse and (analog) keyboard. Just using a controller with the SteamInput actions should work flawlessly.
