this post was submitted on 12 Sep 2025
170 points (99.4% liked)
PC Gaming
12275 readers
411 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What proton version are you running? I tried with the latest proton he.
I didn't find the auto detect super helpful, kept trying to run at very high with full res, was not stellar. Was able to get decent frames with dlss + frame gen, balanced on high, dropping from 3440x1440 to 2560x1080 went into the 100s, dlss looks really bad with it though, like the edge artifacts are rough looking. Settled on tsr, find fsr really blurry, and no frame gen.
Didn't do matchmaking, but co-op with my partner worked just fine.
I tried on the steamdeck, didn't tweak much, didn't expect it to be great but don't think I expected PowerPoint level frames.
Edit, specs 4070ti 11900k 32 GB ram On arch with most recent drivers
Using GE-Proton10-15, HDR works great too.
I did notice the edge flickering artifacts with upscaling. XeSS is a bit higher quality than TSR but it also has the flickering. FSR framegen causes the flickering to happen on some particle effect that they use for atmosphere effects (like pieces of dust floating in the air) so it isn't very usable currerntly.
The game isn't perfect, but it's very playable for me after some settings adjustments. I didn't have any crashes in 5.5 hours of playtime, but I did notice the shader compiling stutter and there were some spots where you could tell that it was loading a zone if you walked over a specific point and I was in combat at the time so I ran across that point a few times and that caused some framerate issues.
A HUGE amount of the stuttering was eliminated by setting the Textures Streaming Speed to Very High, it looks like this is throttling disk IO for performance reasons. If you have an NVME SSD then I can't think of a reason not to set it to reason not to set it to very high.
That's good to know that Steam co-op works. I'll try it later today, my friends are all running Linux too and didn't want to buy a copy if it wasn't going to work. I happened to be home yesterday so I was the guinea pig.
I tried updating the DLSS version (using PROTON_ENABLE_NGX_UPDATER=1), the flickering still occurs. Same with using RENDER_PRESET_K. It almost looks like they're applying too much sharpening when you're using DLSS, but I don't see a way to adjust that specifically.
AFAIK: PROTON_ENABLE_NGX_UPDATER=1 doesn't update the dlss version/dll files, just some game-specific profile settings. You'd still need to replace the .dll files if you want newer/different dlss files.
https://github.com/jp7677/dxvk-nvapi/wiki/Passing-driver-settings#ngx-snippet-updates-and-preset-overrides - at least the documentation here only talks about some snippets that envvar allows updating
Ah, I didn't RTFM completely. I just read a snippet that mentioned the NGX updater and misunderstood the context.
I'll give it a shot, thanks.
tbh, I did the exact same thing, but came across that documentation today and realized my error... :P
hope it works!
So many envs and no central documentation makes it hard to handle for everyone.
it gets weird when there's multiple software layers. each one has their own env's, dxvk, proton, nvidia, and then there's the few random 3rd party ones (eg. libmimalloc if you want to tinker with memory allocation options)
it gets messy.