Valve updated Proton Experimental for September 19th, adding their usual assortment of fixes for running Windows games new and old on Linux PCs and Steam Deck. The last update was September 10th which pulled in even more fixes.
Noted to be now playable includes:
- Act of War: Direct Action (with AMD GPUs).
- Starlight Re:Volver.
- Gemstones.
- Warnament.
Other fixes and improvements include:
- Mitigated OpenSSL-related issues in Agony UNRATED that happen on newer Intel CPUs.
- Fixed Counter-Strike rarely crashing when connecting to matches.
- Fixed Sea Power not playing background music.
- Fixed Alone in the Dark (2008), DiRT, Disney Universe, Hard Truck Apocalypse: Rise of Clans / Ex Machina: Meridian 113, Dino D-Day and Prototype 2 not running on CPU with high core count.
- Fixed Disgaea PC not displaying controller icons correctly.
- Fixed language selection not working in Black Squad's launcher.
- Fixed video playback in The Heart of Influencer and Superscout.
- Fixed Proton Experimental regressions:
- Some AVPro videos in VRChat should no longer be distorted.
Pictured - Prototype 2
Source: GitHub
This update for Proton Experimental will show up as an update in your Steam Downloads. Or, it will install automatically if Valve have it set by default for a game when you go to play it. Otherwise, search for Proton Experimental in your Steam Library to install it.
Check out some of our popular GamingOnLinux Guides:
- Alternatives to popular games that don't work on Linux, Steam Deck and SteamOS
- How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
- Why some games on Linux, SteamOS / Steam Deck have broken videos and what you can do
Can relate.
Previously, there was a patch that fixed this, but the game's publisher saw fit to remove it, making the game unplayable on Linux, probably to sell more new games ;-(
However, there is a workaround.
Create a shortcut to launch this game, for example on your desktop. Right-click on it, then select properties, under "Command", add the following line :
taskset -c 0,1,2,3 steam steam://rungameid/8930
This command will force the use of only 4 CPUs (which is more than enough to play it).
This will prevent the game from randomly crashing mid-game.
!!! But be careful, Steam must not already be running for this to work. If this is the case, you must first exit Steam, then restart it by double-clicking on the game icon !!!
This should also work with other games that have this same type of problem… But Steam will only run with 4 CPUs maximum, if you want to play another game after that, I would recommend you to quit Steam and restart it normally.
Another solution is to launch Steam with the option :
taskset -c 0,1,2,3 /usr/games/steam %U
Regards.
!!! But be careful, Steam must not already be running for this to work. If this is the case, you must first exit Steam, then restart it by double-clicking on the game icon !!!
You should be able to have
taskset -c 0,1,2,3 %command%
as the game's launch options in its Properties to have it apply just for that game.
Could never make it work.

...and all I want is a plug and play working functionality for the realtone cable and Rocksmith 2014.
Hmm, I definitely got this working maybe a couple of years ago. I think I might have been running EndeavourOS back then? But I didn't have to do anything special. The cable just appeared as an input, so I could record from it directly in things like OBS, although it was like a line in, so maybe I had to put it through my amp? I can't remember, sorry.
I'll maybe try to find it again and give it another shot.
!!! But be careful, Steam must not already be running for this to work. If this is the case, you must first exit Steam, then restart it by double-clicking on the game icon !!!
You should be able to have taskset -c 0,1,2,3 %command% as the game's launch options in its Properties to have it apply just for that game.No, my dear, it's Steam that launches the games via the command I mentioned. And if Steam is already running, it won't take into account the core restriction of the number of cores we're trying to impose on it. In such a case, the game will crash. If you had tested it, you would know...
so what is <currently> considered a high number of cores?For the games listed and from their bug reports it looks to be from 24 threads and up (so 12 cores and above with hyperthreading activated).
Last edited by F.Ultra on 22 Sep 2025 at 12:47 am UTC
No, my dearIt's impossible to use that phrase without sounding incredibly condescending. Not sure if you have English as your first language, so pointing out here that it sounds very douchy, and hopefully that wasn't your intention!