Curious if the lack of working MP is due to proton inaccuracies and can be fixed overtime, or a conscious block from Sony/Anticheat.

Curious if the lack of working MP is due to proton inaccuracies and can be fixed overtime, or a conscious block from Sony/Anticheat.

what's MP?

Curious if the lack of working MP is due to proton inaccuracies and can be fixed overtime, or a conscious block from Sony/Anticheat.

what's MP?

Multiplayer, devs made a post before release taking about how it runs fine on deck but marked unsupported due to broken multiplayer, their wording implied it was "only supported on windows" but didn't elaborate if this was a intentional choice or just due to proton bugs.

Really hope they didn't do something like disable the option on deck if it's a fixable proton bug.

Got this error, intro logos played after that the game froze. Proton Experimental & Arch

Got this error, intro logos played after that the game froze. Proton Experimental & Arch

May be related to https://gitlab.freedesktop.org/drm/amd/-/issues/3343

For me the game seems to run fine aside from controller issues. I am using a Dualsense controller and in-game whenever I press a button it rapidly switches between Xbox and Playstation prompts, and it press buttons many times repeatedly. Same issue both wired and wireless. Proton experimental. I am going to try some different versions to see if it makes a difference.

Edit: Mmm... it seems to do this with all input devices, might be an issue with the game itself.

Edit: It was a Steam bug, I restarted the client and the problem is now gone. Unsure if Steam Input related, disabling it made no difference in testing.

Confirmed the game locks out the multiplayer if they detect you're on deck, if it's just a proton bug preventing the mp, it might forever be disabled on deck if a fix isn't out soon enough, devs really don't like to undo their weird hacks.

To add onto issues I'm experiencing with this game:

I'm using Proton Experimental on Fedora Silverblue 40 with the Flatpak mesa version 24.0.6 drivers. I have an AMD 7900 XTX, and a 7900X3D.

I have horrible flickering and pop-in that my friend on Windows using a 4070 Ti isn't experiencing.
Here is a short clip of the issue in question: https://streamable.com/7eha3o

There is also a separate issue experienced when turning on AMD FSR 3 Frame Generation, which is the frame timing being extremely jittery and occasionally leading to crashes.

This is present on Proton Experimental, 9, 8, and GE 9-5 at least. I haven't tested further versions.

Breaking it down as per the compatibility report template:

GPU: AMD Radeon RX 7900 XTX
Kernel: 6.8.9-300.fc40.x86_64 (Fedora Silverblue 40)
Video driver version: Mesa 24.0.6
Proton Version: Experimental, 9, 8, GE 9-5

Proton Log output attached from a recent FSR 3 Frame Generation crash.
steam-2215430.log

I enabled the 4G memory thing in my BIOS, now it works, and the Wine errors are not happening any more. This is apparently a problem with recent kernels combined with this BIOS option.
Thanks for the link @Bitwolfies
You might want to try this too @hamburgerghini1

For anyone on Nvidia, 525/535 drivers results in a bunch of missing textures. Latest Nvidia drivers solve it.

@powerofthe69 Do you still have your save standing at that spot or close to it? If so, can you upload it?

@K0bin I had to make a new manual save next to the outpost, but I can upload that now.

To be clear, this is also happening on the title screen and everywhere else in the overworld as well. I just thought it was most egregious at that one fence. Here is a link to the title screen flickering, and here is another video approaching the outside of the same outpost in the original video I'd posted.

Here is the save file I made - I had to rename it to .log to be able to upload it here for some reason, so this file should be modified to be .sav instead.
manual_0002.log

MP does not work, pssdk tries to install itself but it ends up removing itself when launched, manually initializing the pssdkappmgr.exe results in wine not supported error, bypassing it by hiding wine version still gives pretty much the same error

MP does not work, pssdk tries to install itself but it ends up removing itself when launched, manually initializing the pssdkappmgr.exe results in wine not supported error, bypassing it by hiding wine version still gives pretty much the same error

Installing via standard wine actually brings up a crash window with a crashtrace, which ive linked below.
backtrace.txt

Though you mentioning an explicit "wine not supported" error message really makes me wonder if they borked this on purpose.

@powerofthe69 I tried on my rdna2 gpu and I haven't seen anything off on either mesa 24.0.7 or .6 (just in case).
I haven't seen any oddities with the frametimes when FG is enabled, but I haven't used it enough to rule out crashes.

@simifor thank you for letting me know. I'm currently verifying my files then going to try again. Maybe something got messed up during preload. If the issue persists, I'll do a complete uninstall / reinstall and see if that helps.

I'm not sure if this problem is related to Proton itself, but this game keeps freezing/crashing every 2-4 minutes and I need to kill the process. This is not happening on any other game. I am running Proton Experimental.

Every time it crashed, I kept getting this error message:

[2024-05-17 19:58:49] Nothing to do
radv: GPUVM fault detected at address 0x8000a45ba000.
GCVM_L2_PROTECTION_FAULT_STATUS: 0x501430
CLIENT_ID: (SQC (data)) 0xa
MORE_FAULTS: 0
WALKER_ERROR: 0
PERMISSION_FAULTS: 3
MAPPING_ERROR: 0
RW: 0

GPU: AMD Radeon RX 7900 XTX
Kernel: 6.7.12-amd64
Video Driver: Mesa 24.0.7-1

@clnne crashes like that happened to me only while using FSR 3 Frame Generation. If you have it on, that's probably the culprit. There's a Reddit post about it as well.

@powerofthe69 Thanks, but I've already tried that, but unfortunately it didn't help.

@powerofthe69 Some further testing with FG and over 1 hour and a half session and no crashing. However, I am noticing some jittering, specially when in battle and other dynamic situations where the framerate varies.

Checking on windows, the framerate is equivalent to linux with both FG on and off, however, with FG on, the frame times seem a bit more consistent than on linux. At least with my rx 6600.

I was able to install mesa-git finally, so now my current driver version is 24.2.0-devel, but the issue is still persisting with the intense flickering, and it seems no better at all.

getting this error randomly on arch linux using steam flatpak

@powerofthe69 Some further testing with FG and over 1 hour and a half session and no crashing. However, I am noticing some jittering, specially when in battle and other dynamic situations where the framerate varies.

Checking on windows, the framerate is equivalent to linux with both FG on and off, however, with FG on, the frame times seem a bit more consistent than on linux. At least with my rx 6600.

@simifor Are you running under Gamescope with Mangohud? I was running with:

MANGOHUD=1 gamescope -f -e --adaptive-sync -W 2560 -H 1440 -- vk_radv %command%

And the frame pacing was atrocious with FG3 enabled on my RX6800. It went from stable 90fps to unstable 110fps, which was pretty obvious that something was messing with FSR3 FG. With V-Sync enabled (which is the recommended for FSR3 FG) things improved a bit, but it was still very weird, going from 90fps to 110fps instead of doubling. I tried to put a FPS limit directly on Manghud and the game would always run 20fps lower than the set limit.

So I tried running without Mangohud (which is known to cause performance problems in some cases) and Gamescope, now FSR3FG is working flawlessly, actually, it's the best implementation of FSR3FG I've ever seen (it's actually FSR 3.1). It still need V-Sync ON as recommended by AMD, otherwise you'll get a weird motion effect whenever the frame rate drops.

edit: a minor problem that I've noticed is that the game renders some moving UI elements at Native Frame Rate, if you have a high enough frame rate natively, this is not noticeable, but for lower native frame rates, the UI looks like it's "skipping".

@simifor I found last night that the frame times become more consistent when V-Sync is disabled. This is most likely due to the frame gen producing higher frames than my monitor's maximum refresh rate. Nvidia's DLSS 3, however, automatically turns off V-Sync and doesn't allow you to modify it at all. AMD's FG doesn't turn it off and you have to do that manually, but when I did that I no longer had jitteriness nor did I have any crashes while FG was enabled.

Does anyone get graphics driver warning when launching?
Playing via Bottles Steam. The game gives me completely different versions than what is true.
I'm on latest nvidia Linux drivers 550.78
When launch game a warning says blahblah recommend at least 552.44 I will have issues current driver which is 552.12.
Does Proton/Wine map Linux drivers to a different version number? Game runs perfectly fine I just don't like the warning pop up every time I launch (often as i'm an Uber driver) and I must dismiss it by pressing OK.

@ghtesting2020 yes I get that warning on my NVIDIA rigs as well, probably something that will be worked out with a Proton update hopefully.

apparently disabling motion blur reduces the freezes. freezes tend to happen when I open the game menu / map while character is doing something (landing or something) - seems like a bug in the game intself

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

yeah same here, its getting worse as the game progresses it seems, at this point it freezes every time I open the map, I'm on second island

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

yeah same here, its getting worse as the game progresses it seems, at this point it freezes every time I open the map, I'm on second island

The worst thing is that even the game won't show the Sony logo and it will crash anyway

and randomly as frick

@powerofthe69 for the record, I already had vsync disabled as the game ran over 60 fps for me and it'd have affected comparisons in the end by capping what the game can show. That said, I retested in fairer conditions by having both being after a fresh boot and the result is basically the same to my eyes.

@JonathanxD I wasn't using gamescope.

@KomiksPL Any particular reason you're using GE proton for this title? The current default for this game is proton experimental, do you get such issues there as well?

@Niedzwiedzw I haven't had the game freeze on me, tried to show and dismiss the map continuously to no effect, with motion blur enabled. You say that progression might be affecting frequency, but were the issues present from the start? Could you upload a save file for me to check? And could you upload a proton log where the issue occurs?
Simply add PROTON_LOG=1 %command% to the game's launch parameters and next time you run the game you'll get a steam-2215430.log in your home folder.

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2119382445

I have the same error on Proton Experimental and GE

From what I noticed, this bug occurs when you run FSR3, without it the game does not seem crash.

So I'm still having the issue with the awful pop-in to the point where I've shelved the game because it's detrimental to the experience. However, in doing some digging in the logs, I noticed that my logs for Horizon Forbidden West (another Nixxes port) display a driver version for my AMD GPU, but my logs for Ghost of Tsushima do not. My logs for Ghost of Tsushima also explicitly state "Loading ADL... Failed to load ADL!" earlier in the logs. I'm attaching my Ghost of Tsushima logs.

The lines in question are lines 39 & 40 and line 153. Can someone else (on AMD) please compare their own logs to mine?
Ghost of Tsushima DIRECTOR'S CUT.log

NOTE: These are the only discrepancies between my GoT logs and my HFW logs. On Mesa 24.0.6 Flatpak drivers, using Proton Experimental, tested within minutes of each other.

@powerofthe69

Can someone else (on AMD) please compare their own logs to mine? Ghost of Tsushima DIRECTOR'S CUT.log

• I have a 7900 XTX too
• Up-to-Date Arch Linux
  • Mesa 1:24.0.7-3
  • vulkan-radeon 1:24.0.7-3
  • Proton - Experimental (default branch)
• Game installed on a PCIe4 m2 SSD
• didn't notice any pop-in-issues
• running most settings maxed
• FSR3 upscaling with dynamic resolution scaling targeting 3440x1440 @ 144Hz

My Ghost of Tsushima DIRECTOR'S CUT.log

Your and my log file compared with Kdiff3 (timestamps at the beginning of lines removed, so that the comparison can actually identify equal lines)

Thanks so much for going the extra mile to compare things. I'm starting to wonder if this might be an issue specific to the Flatpak runtime for Mesa as it seems like those on Arch that (I assume) are running system libraries aren't having these issues, and I don't think anyone else has specified that they're using Flatpak either....

I should think that if someone else is using Flatpak then we should see similar issues, rather than it only be me, since we'd have the exact same libraries.

I layered the system version of Steam on Fedora Silverblue 40 and all my visual glitches that I'd been experiencing lately have been resolved. No more flickering in Ghost of Tsushima, no more weird lighting shimmering on certain textures like skin in basically any game, and no more flickering in Lords of the Fallen.

PSA: Steam Flatpak is botched 🤷🏻‍♂️

I get a random freeze and then I have to restart the game, sometimes it's during startup, sometimes while playing. Here steam logs: steam-2215430.log

yeah same here, its getting worse as the game progresses it seems, at this point it freezes every time I open the map, I'm on second island

I just ran into this after playing the game for over 8 hours on my OLED Steam Deck.

I'm curious if anyone is having freezing issues after today's update. I managed to get them twice before today's update, but given that it took 90 minutes each time, it's not something I can check easily for what's to blame for them.

To be precise, the freezing issue I observed allowed some environment sound to keep playing from the game (though nothing related to player input), it didn't affect the gpu, or the desktop environment, and there were no other effects to the system after closing the game.

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2118137769

I am having the same issue under Arch (Plasma6) with a 1080 GTX card (FRS 3 is off).

I'm curious if anyone is having freezing issues after today's update. I managed to get them twice before today's update, but given that it took 90 minutes each time, it's not something I can check easily for what's to blame for them.

To be precise, the freezing issue I observed allowed some environment sound to keep playing from the game (though nothing related to player input), it didn't affect the gpu, or the desktop environment, and there were no other effects to the system after closing the game.

After the new patch the freezing is worse for me now to where I can only play for 1 or 2 minutes.

@afettouhi does audio keep playing when the game freezes? Can you add logs for the game? Go to the game/s properties on steam and add the following to launch parameters PROTON_LOG=1 %command%, this will create a file called steam-2215430.log, upload it here. If the file is too big, then zip it before uploading it.

@afettouhi does audio keep playing when the game freezes? Can you add logs for the game? Go to the game/s properties on steam and add the following to launch parameters PROTON_LOG=1 %command%, this will create a file called steam-2215430.log, upload it here. If the file is too big, then zip it before uploading it.

Yes, the audio keeps running.

Here is the steam log output
steam-2215430.zip

I tried several Proton versions, different combinations of Upscaling/FG. The only configuration that makes this game an absolute dream with zero crashes and/or microstutters is the following:

If you are, like me, on NVIDIA, DISABLE NV-API!! This is night and day. With NV-API enabled I get bad frametimes with DLSS/FSR3 and only ~120FPS. Without tho, I get completely stable frametimes and contant 130-150FPS.

For Proton8, just don't add PROTON_ENABLE_NVAPI=1, for Proton9 add PROTON_DISABLE_NVAPI=1 to the start command.

• Proton: 8.0-5
• Res: 1440p
• Graphic settings: very high, only set SSAO to "SSAO performance"
• Window mode: exclusive fullscreen
• Upscaling: FSR 3.0 (Not DLSS, disable NV-API, even on NVIDIA)
• FG: FSR 3
• VSync: On

My System:

• CPU: Ryzen 5800X3D
• GPU: NVIDIA RTX 4070Ti
• RAM: 64GB
• DE: Gnome 46.2
• Distro Fedora 40
• Driver: NVIDIA 555.42.02

I don't know why this behaves the way it does. One would guess DLSS and NV-API would increase performance on an NVIDIA card, but in this case it does not. Hope this helps some people.

EDIT:

Also works with Proton9 when setting PROTON_DISABLE_NVAPI=1

Does anyone happen to know why the PS Overlay isn't functioning at the moment? Is it due to Proton bugs not allowing it to function or smth?

Does anyone happen to know why the PS Overlay isn't functioning at the moment? Is it due to Proton bugs not allowing it to function or smth?

pssdk that comes with the game doesn't install itself, even if you get them files from windows and try starting manually it will just error out, check my last comment above

I also experience frequent crashes on NVIDIA 555.42.02 on both Arch Linux and Fedora 40, typically when using the map. It sounds very similar to others in this thread since the audio still plays even while the game locks up. I am not using FSR, DLSS, or any upscaling/frame-gen tech. Just native 3440x1440p with HDR in gamescope on Plasma 6.
steam-2215430.log

The log appeared to hang at warn:vkd3d-proton:d3d12_device_GetResourceAllocationInfo3: Invalid resource desc. until I Alt + F4'd gamescope at which point the log was extended greatly. Gamescope also gives a SEGV coredump, which I'll put in a gist here:
https://gist.github.com/matte-schwartz/ff7b2bebf90b05b31b63f3dbc8b3cad2

steam system info + runtime diagnostics here:
https://gist.github.com/matte-schwartz/efce7683d60b7abfd81a446d7ae6bece

It should be noted that the game got another update. It mentions stability improvements, so it's worth checking if any previously encountered issues still happen in the current version.

It should be noted that the game got another update. It mentions stability improvements, so it's worth checking if any previously encountered issues still happen in the current version.

I get the same game freeze on the map after a few toggles and map interactions, seems to happen especially quickly while using gamescope (built from https://github.com/ValveSoftware/gamescope/commit/09cb7b451d8825e597d15ab9d30e43aee8418670)

steam-2215430.log

exact gamescope command:
gamescope -e -r 144 -f -H 1440 -W 3440 --hdr-enabled --hide-cursor-delay 3000 -- steam -steamdeck -steamos3 -steampal -gamepadui in nested gamescope on Plasma 6

edit: i have not been able to get it to crash anymore outside of nested gamescope... however Tsushima is the only game I've been having this freeze with

After watching my journal and triggering a game freeze within gamescope, I'm actually getting

[ 1874.052823] NVRM: Xid (PCI:0000:01:00): 109, pid='<unknown>', name=<unknown>, Ch 000000d6, errorString CTX SWITCH TIMEOUT, Info 0x6c069

in dmesg and my journal when the game freezes. This is on a 4090 with driver version 555.52.04

@marco-kretz

Also works with Proton9 when setting PROTON_DISABLE_NVAPI=1

Thank you! This makes FSR3 work and the game is now playable for me and with no stuttering! I was wondering how some people got FSR3 working on Nvidia.

I'm curious, but why would Nixxes block the Playstation Overlay on Proton?

I tried reaching out to them on X (or really Twitter) about it, but they didn't respond to me.

Did anyone manage to have Dualsense haptics working ?

Adaptative triggers works on my side, but no luck about haptics.
Using Helvum, i can see that the game doesn't output other audio channels than the front l/r

I tried with ClearlyClaire's last build as well.

@marco-kretz Your NVAPI issue should now be fixed in the latest bleeding-edge branch build of Proton Experimental. To be more specific, dxvk-nvapi needs this commit for the workaround to be applied: https://github.com/jp7677/dxvk-nvapi/commit/f86f56b24737d117098a80133516edfb553fe39a

@marco-kretz Your NVAPI issue should now be fixed in the latest bleeding-edge branch build of Proton Experimental. To be more specific, dxvk-nvapi needs this commit for the workaround to be applied: jp7677/dxvk-nvapi@f86f56b

This is great news. Thank you!

I've been getting hit with consistent GPU hangs and soft resets now that I'm part of the way through Act 2. I don't know if it's the region that the Act takes place in or what, but I'm lucky to get about 2 minutes before a freeze and crash occurs. My BIOS settings are as recommended (above 4G, rebar enabled) and no other games have this type of freeze that I've found yet.

System Information
GPU: Radeon RX 7900 XTX
Kernel version: Linux 6.9.8-200.fsync.fc40 (custom Fedora 40 kernel) - I've tried down to Linux 6.5 and it has the same issue
Link to full system information report as Gist: https://gist.github.com/matte-schwartz/b81f28385c88f62c66727e9b4a77ba85
Proton version: experimental-bleeding-edge-9.0-106225-20240705-p4f856c-wd468829-db2d89d-v5cd726

Most recent freeze and gpu reset (~600mb):
steam-2215430.tar.gz

dmesg output after an earlier repeated mini-freeze followed by a crash:
tsushima-crash.log

Perhaps I should be reporting this as a Mesa issue? I'll try and see if anything matches the reset log.

edit:

bisected to: https://gitlab.freedesktop.org/mesa/mesa/-/commit/c452a4d1ccaa7fc33d3ae22bfc23d7c1e3e63c9f
link to associated issue report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11480

Does anyone happen to know why the PS Overlay isn't functioning at the moment? Is it due to Proton bugs not allowing it to function or smth?

probably some feature that wine doesnt have implemented for it to work properly, the overlay probs works just fine but its the PlayStation Network integrated features part that probs doesnt work properly yet, only a matter of time..

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2235699432

PS overlay is considered an unsupported anti cheat by valve, it even contains error data about how proton is explicitly not supported. It's highly likely Sony has chosen to manually block it, or that relies on things wine cannot do (kernel level stuff)

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2237216453

This issue is already impacting Concord as well and I fear this will even block GOW: Ragnorak (which is a singleplayer game) since it will require PSN.

Replying to https://github.com/ValveSoftware/Proton/issues/7735#issuecomment-2246876882

Yep sony being anti consumer friendly :D

I just noticed that Valve marked this game as they are still working on adding support for it when it was formally classified as using an unsupported anti-cheat.

Same thing happened to Concord (who else hasn't forgotten about it yet?). Does this mean the PS Overlay will be supported soon, thereby allowing Legends?

I took a look at the button prompt issue and as an extra tidbit, it only seems to happen when using a deck-uhid or deck controller target, which is used by default on all non-Deck handhelds running SteamOS like the Legion Go S. The issue also occurs on my MSI Claw 8 A2VM where the glyphs used for deck-uhid/deck in Steam are a different style than on the Legion Go S.

Changing the target to xbox-elite will show Xbox glyphs without any missing button prompts.

So is this game's problem or the steam os's problem?

I can't find any solution about this problem on google.

Can I deceive the game like I connect xbox elite controller?

I had the same issue on a ROG Ally + SteamOS 3.7.9 with Spiderman 1.
The target is defined for xbox-elite in input plumber configuration file.

@ncocaign steamos-manager sets it into deck-uhid so the default is ignored on SteamOS

sudo inputplumber device 0 targets info should who you the current target iirc

I finally succeed to fix it by going to desktop mode, and execute the following command in Konsole:

sudo inputplumber device 0 targets set xbox-elite

This replace the steam deck input by Xbox input and the proper buttons appears ingame!

MP does not work, pssdk tries to install itself but it ends up removing itself when launched, manually initializing the pssdkappmgr.exe results in wine not supported error, bypassing it by hiding wine version still gives pretty much the same error

Does this workaround work in GoT? It works in GoW:R, but no one has tested if this works in this game yet:

https://github.com/ValveSoftware/Proton/issues/8107#issuecomment-2632297758

On ANV, I get an error on launch about no GPU being installed (although the game runs fine after this warning)

steam-2215430.log

System:
  Host: msi-claw8-a2vm Kernel: 6.16.7-3-cachyos-deckify arch: x86_64 bits: 64 compiler: gcc
    v: 15.2.1
  Console: pty pts/0 DM: SDDM Distro: CachyOS base: Arch Linux
CPU:
  Info: 8-core model: Intel Core Ultra 7 258V bits: 64 type: MCP arch: Lunar Lake rev: 1 cache:
    L1: 832 KiB L2: 14 MiB L3: 12 MiB
  Speed (MHz): avg: 1504 min/max: 400/4700:4800:3700 cores: 1: 1504 2: 1504 3: 1504 4: 1504
    5: 1504 6: 1504 7: 1504 8: 1504 bogomips: 52838
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] vendor: Micro-Star MSI driver: xe
    v: kernel arch: Xe2 ports: active: eDP-1 empty: DP-1,DP-2 bus-ID: 00:02.0 chip-ID: 8086:64a0
  Display: unspecified server: X.org v: 1.21.1.18 with: Xwayland v: 24.1.8 compositor: Gamescope
    driver: gpu: xe tty: 290x42
  Monitor-1: eDP-1 model: PN8007QB1-2 res: 1920x1200 dpi: 284 diag: 203mm (8")
  API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm: drv: iris
    surfaceless: drv: iris inactive: wayland,x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.3.0-devel note: console (EGL sourced)
    renderer: Mesa Intel Graphics (LNL), llvmpipe (LLVM 20.1.8 256 bits)
  API: Vulkan v: 1.4.321 surfaces: N/A device: 0 type: integrated-gpu driver: mesa intel
    device-ID: 8086:64a0
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    gpu: gputop, intel_gpu_top, lsgpu wl: wayland-info x11: xdpyinfo, xprop, xrandr

Not sure if this a known thing here but the game is borked for NVidia drivers with a version newer than 170.x.x (so since quite a few weeks) The game will freeze within seconds after loading into the actual gameplay. Everything before that works so the intro movies, main game menu etc will work but the whole thing freezes as soon as you load a save. Tested with the latest patch 8 of the game that just came out recently. ProtonDB users also report this issue since about 3 weeks or so.

Steam game log attached: steam-2215430.log

PrtotonDB link: https://www.protondb.com/app/2215430

Edit:

After the recent update to the game the following setting combo seems to work consistently without any freezing

VSync ON
DLAA (or DLSS) ON
NVidia Reflex ON
Framegen OFF

Framegen is off because it would otherwise create a heavy amount of lag and drag. The game will freeze the moment VSync is disabled again.

I can't even get the game to run at all on nvidia 570 or 580. Have not been able to pin down the problem, I also see some weird issues at the launcher, with menu items showing oddly as if variable names weren't being properly localized.

Hey, so the problem here was not in fact the game or proton, it runs fine with a 60FPS limit on nvidia 580.95... it was in fact because I had a duplicate folder upstream of the game.

In my case, somewhere along the line I had created a second, empty, steam folder next to my Steam installation folder, but importantly, it doesn't matter what folder is duplicated - Since windows applications are used to an NTFS file system that is case-insensitive, they can get messed up when looking for files where there's two folders with "the same name" as far as they're concerned; in my case, somewhere along the lines it was being run from ~/.local/share/Steam/steamapps/common/... but getting routed to .local/share/steam/..., a folder that was empty/didn't exist.

Naturally, it's a good practice to avoid having multiple folders on a linux machine with the same name and different casing, but when Wine/Proton (or any windows applications, in any form) come into play, it's doubly important to maintain sanitized folder structures. Just posting this to help other folks avoid running into my issue. It might even be something worth integrating into troubleshooting steps for proton!

thanks, i'll check it out and follow up on the issue

@xAtegox Please share information about your system (gpu model and driver, for example), and having more information about the issue would be appreciated, like a video where the issue is visible as well as a location where it triggers.

@xAtegox Please share information about your system (gpu model and driver, for example), and having more information about the issue would be appreciated, like a video where the issue is visible as well as a location where it triggers.

right now for some reason the fog flicked disapeared, i did find another issue where tree leaves texture is all weird, i could not upload the video directly here so im linking it to my youtube chanel. My specs are: r7 260 with rtx 5050, latest packages on cachyos

https://youtu.be/FDb3TwfEn5Q if i do encounter the fog bug i will link it here, if more info is needed i will be glad to respond

fog flicker would basicaly constantly draw weird lines on the fog, like old monitors

im sorry youtube compression totaly killed the visuals, here its an updated video: https://www.youtube.com/watch?v=M7k6jrzuvDU

i hope its a little better, but its way more noticable in game

@xAtegox so the fog flickering isn't constant and happens in some sessions and not others. Was the shimmering around leaves something that was happening before as well, or is it something that also happens sometimes? it'd be good to have graphics and display settings, including dlss settings.

@xAtegox so the fog flickering isn't constant and happens in some sessions and not others. Was the shimmering around leaves something that was happening before as well, or is it something that also happens sometimes? it'd be good to have graphics and display settings, including dlss settings.

yeah its happeening randomly on some sesions here and there, the leaves also happen in sesions, sometimes it does that sometimes it doesnt.

my graphics settings are high with only thing edited motion blue to 0

and display:

the visuals persist even with vsync off / on
the fullscreen, exclusive fulscreen and windowed also doesnt fix
i didnt use the nvidia low latency option
dlls was set to quality, but that also doesnt seem to fix if i toggle it off
frame generation was turned off
contrast was set to cinematic, brightness to normal

i think this should be about it

@xAtegox took half a dozen times but I think I got both issues to appear on my nvidia laptop. Fog would looked as though it'd flicker darker and brighter at random, while some tree branches looked as though they were vibrating. For now, I tried to see if the same happened on steam machine but didn't see the issue there, so this might be nvidia specific.