
SeaIggy
Published
I do notice a lot of crackling. However, I believe I found a resolution. I found this site https://web.archive.org/web/20191126145156/https://ludwig.im/en/projects/steam-pulseaudio-sound-latency-lagging-problem-noise which has a bunch of recommended settings. From my own trial and error (and cross checking the arch wiki pulseaudio and pulseaudio troubleshooting articles), I found that these changes to my /etc/pulse/daemon.conf worked best
daemonize = yes
high-priority = yes
realtime-scheduling = yes
realtime-priority = 9
default-fragments = 5
default-fragment-size-msec = 2
YMMV. If this doesn't work, try out some settings to see what works best for you.
When I first started the game, it wouldn't work at all with two monitors. I disabled the second monitor, but then it forced my main monitor resolution down from 1440 to 1080. I had to change the game setting to borderless window so that it did not force the resolution down. Once there, I could re-enable my second monitor, change my main monitor resolution back to 1440 and then re-open the game and change its resolution to 1440.
NOTE: I actually run the game with a custom build of proton. The build was compiled with the proton tkg pkgbuild on Dec. 7th 2020. The version that got assigned by the tkg pkgbuild in pacman is 6.0rc1.r3.gfce121fc-1
.
The game initially did not work with the vulkan setting on proton 5.13. Other posts here pointed out that if you would like to use the vulkan setting, you should update proton to use the latest wine version (as well as dxvk and all the other good stuff). I can confirm this is true. Game runs rock solid using the vulkan setting when using the latest versions of the libraries.
Initial Grappling Hook Crash Seems to be Resolved with GE-Proton7-38. No other crashes noitced so far on this version either.
GE-Proton7-37 crashes on the tutorial when you first try to grapple an object.
I also experienced the grappling hook crash on proton GE-Proton7-37. Following the advice of other reports, I got past the tutorial without crashing on proton 7.0-2. Luckily, earlier today, GE-Proton7-38 was released and the tutorial did not crash for this new version either.
Took about a half second for scenes to pop in, but performance is fantastic after that.
gamemoderun WINE_FULLSCREEN_FSR=1 %command%
game-debate dot com provides a really good overview of the performance options that give you the most value for turning down. For my set up, I set the resolution to 1080 (which is upscaled with FSR). I set the quality to ultra, then made the following changes:
- Anti-aliasing set to FXAA
Turn off
- Shadow Detail
- SSAO
- Screen space shadows
- Depth of Field
- Screen space reflections
Set to Low
- Lighting Quality
- Fog
Set to Medium
- Grass Detail
- Building Detail
Set to High
- VFX Detail
With this, I average around 90 FPS in battles whereas I was previously averaging around 40 FPS. Additionally, I ran both benchmarks and it's pretty difficult to spot the graphical differences between native rendering and FSR.