Zitch
Published
Definite if you can get past the audio issues, and with more powerful system, the cut-scene slowdowns wouldn't be as noticeable.
During cutscenes, some dialog is skipped or repeated in wrong places.
Occasional significant slowdowns issues during cut scenes, but no such performance issues during gameplay.
Sometimes game will freeze. Able to tab out, and kill it via xkill
I'd imagine a much more powerful system than mine would have a perfect experience with this game.
In Steam, set Launch Options for the game to PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%. Adding these options does slow down game performance by around 10 FPS, but this seems to fix the dialog issues that plagued runs on Proton (A problem that apparently affected Windows users too!)
Occasionally, the game severely slows down during cut-scenes. This didn't seem to affect screenplay, though.
No crashes after disabling ESYNC and FSYNC via the Launch Options configuration, but no guarantee they still won't happen. Other issues like occasional slowdowns during cut-scenes still happen.
Game is borked when running on a hybrid GPU laptop (Intel/Nvidia RTX 2070 in my case) on the laptop screen itself.
Running off the discrete GPU (Nvidia RTX 2070 in my case) on an external monitor works very well, but this limits being able to play AC:O on the road unless I have access to a monitor :(
It seems the game insists on running on the integrated Intel GPU, even if having the environment setup to tell it to run on the Nvidia GPU, when running on the laptop screen. If running in Hybrid mode, the game locks up right before the menu screen, and you may have to force a reboot to get your system responsive again (requires SSH from another machine and running sudo shutdown -r now to do this safely).
If running with just Nvidia Graphics mode on the laptop's screen, the game never gets started. I am able to alt-tab to my Steam window and press "Stop" for shutdown the game.
I've witnessed a few other games that work this same way.
Need to add a gamefix script (as linked above), and some graphical issues, otherwise, the game is very playable on day one of early access.
Using GloriousEggroll's Proton-5.9-GE-7-ST with gamefixes script from here
Some severe visual issues during a crash scene, otherwise graphics look really good.
If you're using real fullscreen mode, alt-tabbing out will cause the game to crash. Using Windowed Fullscreen seems to work fine though.
The launcher does not run on proton. The script change for the GloriousEggroll fork will bypass the launcher app and runs the game directly.
Getting 55 FPS on a 3440x1440 ultra-wide with Ultra settings. Turning on FSR to Auto would bring that up to 110 FPS.
AMD_VULKAN_ICD=RADV gamemoderun %command%
Was having problems with guns and other audio cutting out (not crackling, but a weird looping click sound would occur. Of all the things I've tried, unplugging my Steam Controller USB receiver seems to have solved this, at least on initial testing. Using GE versions of Proton was for seeking how to solve this issue. So if you have problems with audio being missing, especially guns, try unplugging any controllers as an easy early test.
I'd suspect Cyberpunk 2077 would run just fine without the Launch options I used, and with the standard 7.0.1 proton, for most people. Not sure about performance compared to Windows, but without my audio issues, the game runs very well.
Worked nearly perfectly out-of-the-box with no tweaks needed. Switched to Vulkan graphics, 1440p resolution, and ultra settings.
There was one point where the game went down to less than 10 FPS (when I got the Argent Energy Cell), but otherwise, the game played at the max 165 FPS for my 1440p monitor
Other than working Force Feedback on my Logitech G29, it seems Dirt Rally 2.0 will work just fine with Proton 7 or experimental.
Disable Steam Input to get the full experience on a Logitech G29 wheel, pedal, and shifter set
To get Force Feedback working on a Logitech G29 wheel, I had to disable steam input for the game (in preferences -> controller)
First, Disabling Steam Input allows me to have Force Feedback on my G29 wheel with Proton 7.0.2 or Experimental rather than being limited to Proton 6.3.8. I also remember having to remap my pedals in game, though this may be an issue in Windows too.
If you're not using a wheel, the game should work out-of-the-box without any changes needed, but the game is so much more immersive with a fully functioning wheel, pedal, and shifter setup.
You will need pretty beefy hardware, but I'm enjoying it so far.
Game seems to start windowed mode, then switches to borderless fullscreen mode after a few of the intro videos. Doesn't seem to cause any further problems, but something to be aware of.
Once in 7 hours of play, the system hard-locked with a black screen with mouse cursor stuck at center of screen and required a hard-shutdown with the power button.
The performance problems people are having with the game on Windows also translates here. Hopefully, Capcom can address these issues, but the game is otherwise playable on my system.
Using Glorious Eggroll's fork: Proton-5.9-GE-6-ST
Some crackling was fixed with adding to launch options: PULSE_LATENCY_MSEC=60 %command%
In the past, certain networking issues persisted (likely, getting information from the server from other players using your pawn in their game) wasn't working. This was very noticeable when you sleep at the inn and get 2 networking error prompts. As of last night, those stopped; the only thing I can think of is using the Proton-5.9-GE-6-ST proton fork release.
My current launch command for DD:DA: PROTON_USE_D9VK=1 PULSE_LATENCY_MSEC=60 %command%
Currently may require some tweaking depending on your distrobution, but I think it's very enjoyable once workarounds are employed.
ulimit -n 1048576; %command%
Without Launch Options I had set, audio such as speech would cut out, and eventually game would lock up requiring you to force-quit it. Seems to be hitting open file descriptors limit. Setting Launch Options with ulimit -n 1048576; %command% fixed this for me. Max value available may be different, check with ulimit -Hn in console.
The game occaisionally has fraction of a second freezes that usually doesn't affect gameplay for me. If this happens during cut-scenes, audio may be out-of-sync for that phrase, but it fixes itself shortly. Otherwise, game performs pretty well on my setup on Very High graphics settings on a 5120x1440 screen (32/9).
Would likely work with Proton 9 or Proton Experimental, but I was looking into fixing the audio cutout & crash issues. Increasing the soft open file descriptor limit using Launch Options is likely the fix needed. Some distros may have this set to a sufficient value, but Bazzite only allows 1024 by default.
Will need at least VKD3D 2.3.1 (currently in Proton Experimental) and may need a boot parameter, but otherwise, the game ran flawlessly.
(Reported experimental version: Proton Experimental)
Running Proton Experiment with VKD3D 2.3.1 had many fixes specifically for this game that made for a (to me) perfect experience in my 57+ hours of play.
The game only froze if I left the system alone for a while and the screen-blanking kicked in, at least sometimes. Sometimes the game was able to recover, sometimes not and I had to alt-tab to Steam to stop the game.
With newer kernels (5.10 or higher) and newer processors (I'm running on my AMD 5600x CPU), animations in the game play at a much slower speed (some people report 50%, I experienced around 75% to 80% speed), and hence the audio will be out of sync in rendered cutscenes, and animations in general will be slower (I.E., Aloy diving out of the way, or enemies attacking will play in slow-motion). Pre-rendered video will play just fine.
Fixing this requires either using kernel 5.9 or older, or adding cpufreq.off=1 to the GRUB_CMDLINE_LINUX_DEFAULT line (add to other flags with a space) in /etc/default/grub, running update-grub as root, then rebooting. I'll likely remove this line once I'm completely done with HZD or if this issue with the newer kernels have been resolved, though I've not noticed anything different in how my system run. Adding this line means the game animations run at 100% speed.
The game, with the newer VKD3D versions, played at around 80 to 120 fps at 1440p with Ultra quality on my setup. Older versions of VKD3D (older than 2.3.0) loses about 20 fps, so be sure to use a version of proton that uses VKD3D 2.3.1 (2.3.0 and older had problems with blocky shadows in HZD, which didn't really detract from my experience) or newer for best experience.
Vivox voice chat does not work. Otherwise, the game is perfectly playable, and I'm usually using Discord with friends anyways.
Vivox voice chat has been refusing to support Proton; hopefully the Steam Deck changes their minds about that. Other than that third-party issue, Killing Floor 2 has been a mainstay in my gaming rotation.
Set launch options to "PULSE_LATENCY_MSEC=60 %command%" to fix issues with audio.
Alt tabbing from Fullscreen had problems. Switch to Borderless Window
Proton-5.9-GE-8-ST GloriousEggroll
Proton-5.9-GE-8-ST
Seems to be working perfectly well with Proton-5.9-GE-8-ST
Would lock after few hours of playing on a loading screen. Pop!_OS is still responsive, and you can open the terminal or system monitor to kill the process.
Was lots of fun to play, even at this stage!
Some shader issues with the groud was the only issue I saw.
Other than the shader issues on the ground, the game ran quite smoothly on Ultra graphics settings on a 5120x1440 screen. The game is still in early access, so hopefully the graphical issues get resolved. Not sure if the graphical issues also show up on Windows.
