ExtraSoap
Published
Worked on Steam Link out of the box with stock Proton 5.0-10. One minor issue in 2+ hours of play.
In Big Picture over Steam Link the controller wouldn't be detected if the initial controller ran out of batteries and you connected a second one. I'm not sure if this is on Proton, the game itself, Steam Link or Big Picture but it's worth noting regardless.
No customization other than using Proton 5.0-10
When the initially-connected controller (that was working flawlessly) ran out of batteries, the game wouldn't recognize the second controller that I connected. I'm not sure if that's because of proton, the game itself, Big Picture or Steam Link.
EXTREMELY slight hitches when new shaders are populated as they occur.
The overall experience is great. identical performance to Windows, one minor input issue in over 10 hours of Proton play.
Once out of the 10+ hours I've played on Proton, after alt+tabbing I had on odd mouse issue where it would "hang" while moving towards the center of the mousepad, but a simple Steam restart fixed the issue.
Proton-6.16-GE-1 GloriousEggroll
It doesn't like switching audio outputs (headphones to speakers, for example) after the game's been launched. It'll stick with the output it launched with regardless of what the OS says.
On occasion the mouse wouldn't register after Alt+Tabbing back in to the game.
Very slight performance issues as the shader cache builds in new areas, pretty standard stuff. Occasional crashes after cutscenes which are inconvenient but not the worst thing in the world. Definitely not native performance, but close enough to it where I'm perfectly comfortable playing the game for a few hours.
Occasional crashes at the end of cutscenes as noted above.
Proton-6.18-GE-2 GloriousEggroll
Created a text file 'dxvk.conf' that contains a single line of text: “dxgi.syncInterval = 0” as described in other reports. I don't know what it does specifically, but it makes the game run far better.
Occasionally refuses to start when launched from Steam, fixed by pressing the 'play' button again. The frametime skyrockets to ~60ms from ~7ms in the class/weapon select menu, but goes back to normal in other menus and during gameplay.
It took some googling but my DualShock 3 now works perfectly, albeit with keyboard prompts/icons instead of Xbox/PlayStation controller prompts. The solution was (from Steam) go to Settings -> Controller -> Desktop Configuration, verifying that your controls are correct as Elden Ring apparently uses the desktop configuration via Proton, and then going to Elden Ring (in your library) -> Properties -> Controller -> Override Drop-Down -> Enable Steam Input
It took me a full half hour of troubleshooting to get past the white-screen bug on launching the game. I don't know what I did that fixed it as I no longer get it very often on the same Proton-GE version (7-43) I started out on. All I can say is start with Proton-GE7-10 as recommended here, pull your hair out for a bit, and then try whatever proton version you started out with. The best description I can give is that the game needs to 'warm up' to your system before it cooperates and no longer gives the white screen very often. I get it maybe 1/10 launches now, and a simple restart fixes it every time.
The game crashes once you start to load in to someone else's session for coop (I haven't tried invasions).
A more casual player most likely wouldn't have significant issue with this, but Quake isn't the most casual game...
The first time I started the game, it crashed after 2-3 duels. I have not had another after another 2-3 hours played, but I remain weary.
I also get seemingly random frame drops/stutters, usually at very inopportune times. Usually not horrific, not enough to make me boot into Windows to play a few duels.
Overall, Gold experience for sure. I'd love to give it Platinum but the stutters in a game like this take that out of the equation.
As noted before, a single crash in 2-3 hours of gameplay so far.
It doesn't seem to take to one or two servers so far, which causes a crash. There's also an occasional mid-game crash as well. Inconvenient but not horrific.
Origin will crash the first time it's launched. Simply relaunch the game and you're good to go.
Proton-6.16-GE-1 Proton-GE GitHub
Doesn't like switching audio outputs (via the OS) while the game's running sometimes. It'll continue to play audio on the output that it launched with.
Standard stutter as the shader cache builds for first minute or so of play, occasional seemingly random hitch but nothing that doesn't stop me from being in the top quarter of the team when I'm playing well. Outside of those two scenarios I'm getting native performance.
After initial installation and launch, I DL'd and extracted the same files as other users (link can be found below) to /home//SteamLibrary/steamapps/compatdata/393380/pfx/drive_c/users/steamuser/Application Data/EasyAntiCheat/55/, set that folder to read-only as well as /home//SteamLibrary/steamapps/compatdata/393380/pfx/drive_c/users/steamuser/Temp/
An excellent experience. Very impressed with the progress Proton has made in the last year or two. Performance on par with Windows.
On occasion (twice in several hours of play) the game will freeze and GPU utilization will drop to 0 for a second or two. It always comes back to prior performance but this is less than ideal in a game like Squad - you miss commands/relayed information via voip or you might get shot.
A known issue is the VRAM filling and Proton/Squad being unable to deal with it, resulting in single-digit frames after otherwise native performance. I ran into this both on my old GPU (a 1080) and on prior drivers for my current card. A fix that has worked for other people (never for me, unfortunately) is to open the in-game console and type 'HighResShot 320x200.'
Northstar Client (https://northstar.tf/), not needed for multiplayer but it's a better overall experience.
On the vanilla client there was an occasional disconnect from the master server in between games (never during a match), and the Northstar client would crash on boot, which is a known bug and is fixed by trying Proton-GE 7.3 or 7.2.
Extremely enjoyable experience with both vanilla and Northstar clients; I would highly recommend giving it a go. Any tinkering that needs to be done is easy and unintrusive.
