For me it's crashing a lot when opening the game menu

Proton Experimental
AMD 7800XT
Mesa Git

For folks tinkering, please just be aware of the Denuvo anti-tamper. If you change Proton versions a few times it will lock you out of the game for 24 hours like the well-respected customer you are.

I remember re4 blocking rt if it detect it is running on wine, may be this is also true for dd2. and need to promote to dxr ultimate like the reset of the re engine game.
Also disable sam(system access memory) for vkd3d seem to improve performance when cpu bound, at least on main menu.https://github.com/HansKristian-Work/vkd3d-proton/issues/1406#issuecomment-2014752410

I remember re4 blocking rt if it detect it is running on wine, may be this is also true for dd2. and need to promote to dxr ultimate like the reset of the re engine game. Also disable sam(system access memory) for vkd3d seem to improve performance when cpu bound, at least on main menu.HansKristian-Work/vkd3d-proton#1406 (comment)

I did hidewineexports=enable via Protontricks and added VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_7, but still no dice. Anything I'm missing?

Setting no_upload_hvv looks to be a good call, that takes me from being stuck at 50% GPU usage and barely hitting 60 fps to peaking at 80% sometimes!

I remember re4 blocking rt if it detect it is running on wine, may be this is also true for dd2. and need to promote to dxr ultimate like the reset of the re engine game. Also disable sam(system access memory) for vkd3d seem to improve performance when cpu bound, at least on main menu.HansKristian-Work/vkd3d-proton#1406 (comment)

Tried the no_upload_hvv, with an 7800XT, also getting better GPU utilization and performance :D

For folks tinkering, please just be aware of the Denuvo anti-tamper. If you change Proton versions a few times it will lock you out of the game for 24 hours like the well-respected customer you are.

It locked me out without having to change versions much. I've only changed versions ONCE when experimental didn't work back to 8.

When accessing the options menu from the title screen or in-game, the cursor movement sound starts looping and it becomes impossible to exit the menu or change any options. It's not a total freeze, though, as the option categories can still be navigated. This happens on both Proton 9 and experimental.

GPU: AMD Radeon RX 7900 XTX
Kernel version: 6.7.9
Link to full system information report as Gist: System Information, System Runtime Diagnostics

Log from launching the game, navigating to the options menu to trigger the bug, and closing the game using window controls: steam-2054970.zip

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016072761

I had the same problem fixed it by using amdvlk instead of radv.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016252055

how did you go about launching with amdvlk instead of the default? I think I'm too stupid and tired after trying to get this working for 20+ hours using 5 accounts

EDIT: Figured out how to do it and yeah, this is the answer; AMDVLK get's it to work; average 60+ frames and no more crashes!
"mangohud gamemoderun vk_amdvlk %command%"

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016301950

I had the same problem but the driver was the opposite of LordJakki, the default for me was amdvlk, using radv instead fixed the problem.

I used the AMD Vulkan Prefixes script from the Arch wiki. https://wiki.archlinux.org/title/Vulkan#Selecting_via_AMD_Vulkan_Prefixes

AMD_VULKAN_ICD=RADV didn't seem to work.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016301950

I have amd-vulkan-prefixes package installed from AUR.
https://aur.archlinux.org/packages/amd-vulkan-prefixes/
This allows me to easily chose if I want to use RADV or AMDVLK. I only needed to add vk_amdvlk %command% as a launch option in a steam.

When accessing the options menu from the title screen or in-game, the cursor movement sound starts looping and it becomes impossible to exit the menu or change any options. It's not a total freeze, though, as the option categories can still be navigated. This happens on both Proton 9 and experimental.

I ran in to the same issue on Nvidia and was able to make it go away by disconnecting my HDMI capture card before starting the game.

So this is going to be a curveball because my report will be different from everyone else. Using an Intel Arc A770 and Proton Experimental (although I tried it with a couple of Proton versions and they all have the same issue), the shader precompilation step never completes. I will get roughly 60% of the way before crashing with this popup.

Clicking cancel or ok makes no difference, they both close the program afterwards. It is also impossible to generate a Proton log because while it will compile the shaders as expected, it will get stuck instead of crashing generating the logs and I waited until the log bloated up to around 10GB before calling it quits because it just seemed too abnormal for a log file to grow that big if it was doing actual work. Looking at a portion of the file, the last line of useful work done was this line in precompiling a certain graphics shader pipeline before a backtrace gets generated.

1454.892:0124:0224:warn:vkd3d-proton:d3d12_pipeline_library_load_pipeline: Pipeline "TSDeferredPreTransformInstancingVfx_00000000483b7b67ba4477b11e329020" does not exist.
1454.923:0124:0238:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Incrementing frame latency semaphore beyond max latency. Did application forget to acquire? (new count = 2, max latency = 1)
1455.006:0124:0238:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Incrementing frame latency semaphore beyond max latency. Did application forget to acquire? (new count = 2, max latency = 1)
1455.022:0124:016c:trace:seh:handle_syscall_fault code=c0000005 flags=0 addr=0x7f09338d5c07 ip=7f09338d5c07 tid=016c
1455.023:0124:016c:trace:seh:handle_syscall_fault  info[0]=0000000000000001
1455.023:0124:016c:trace:seh:handle_syscall_fault  info[1]=0000000000000000
1455.023:0124:016c:trace:seh:handle_syscall_fault  rax=0000000000000000 rbx=00007f069fc37170 rcx=000000000002fa20 rdx=000000000002fa20
1455.023:0124:016c:trace:seh:handle_syscall_fault  rsi=00007f05e6eb9aa0 rdi=0000000000000000 rbp=0000000100ffa750 rsp=0000000100ffa568
1455.023:0124:016c:trace:seh:handle_syscall_fault   r8=0000000000000000  r9=0000000000000000 r10=0000000000000011 r11=00000000000000c0
1455.023:0124:016c:trace:seh:handle_syscall_fault  r12=0000000100ffc7d8 r13=0000555556735720 r14=000000000002fa20 r15=0000000000000018
1455.023:0124:016c:warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7f09338d5c07: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x15ec07.
1455.023:0124:016c:trace:unwind:dwarf_virtual_unwind function 7f09338d5c07 base 0x7f09338d5900 cie 0x7f093392a478 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
1455.023:0124:016c:warn:seh:dwarf_virtual_unwind backtrace: 0x7f09338d5c07: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x15ec07.
1455.023:0124:016c:trace:unwind:execute_cfa_instructions 7f09338d5900: DW_CFA_def_cfa %rsp, 8
1455.023:0124:016c:trace:unwind:execute_cfa_instructions 7f09338d5900: DW_CFA_offset %rip, -8
1455.023:0124:016c:trace:unwind:dwarf_virtual_unwind fde 0x7f0933936f1c len 10 personality (nil) lsda (nil) code 7f09338d5900-7f09338d5fde
1455.023:0124:016c:trace:unwind:dwarf_virtual_unwind next function rip=00007f0910aeb862
1455.023:0124:016c:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=00007f069fc37170 rcx=000000000002fa20 rdx=000000000002fa20
1455.023:0124:016c:trace:unwind:dwarf_virtual_unwind   rsi=00007f05e6eb9aa0 rdi=0000000000000000 rbp=0000000100ffa750 rsp=0000000100ffa570
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind    r8=0000000000000000  r9=0000000000000000 r10=0000000000000011 r11=00000000000000c0
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   r12=0000000100ffc7d8 r13=0000555556735720 r14=000000000002fa20 r15=0000000000000018
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind function 7f0910aeb862 base 0x7f0910aeb4c0 cie 0x7f091183b3d8 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
1455.024:0124:016c:warn:seh:dwarf_virtual_unwind backtrace: 0x7f0910aeb862: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/vulkan/03/libvulkan_intel.so + 0xeb862.
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4c0: DW_CFA_def_cfa %rsp, 8
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4c0: DW_CFA_offset %rip, -8
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind fde 0x7f091184078c len 2c personality (nil) lsda (nil) code 7f0910aeb4c0-7f0910aebddc
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4c0: DW_CFA_advance_loc 1
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4c1: DW_CFA_def_cfa_offset 16
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4c1: DW_CFA_offset %rbp, -16
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4c1: DW_CFA_advance_loc 11
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4cc: DW_CFA_def_cfa_register %rbp
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4cc: DW_CFA_advance_loc 2
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4ce: DW_CFA_offset %r15, -24
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4ce: DW_CFA_advance_loc 5
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4d3: DW_CFA_offset %r14, -32
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4d3: DW_CFA_advance_loc 5
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4d8: DW_CFA_offset %r13, -40
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4d8: DW_CFA_advance_loc 20
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4ec: DW_CFA_offset %r12, -48
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4ec: DW_CFA_offset %rbx, -56
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aeb4ec: DW_CFA_advance_loc2 1936
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind next function rip=00007f0910aec28f
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=0000555556545ef0 rcx=000000000002fa20 rdx=000000000002fa20
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   rsi=00007f05e6eb9aa0 rdi=0000000000000000 rbp=0000000100ffa7b0 rsp=0000000100ffa760
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind    r8=0000000000000000  r9=0000000000000000 r10=0000000000000011 r11=00000000000000c0
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   r12=0000000100ffc870 r13=0000000100ffc730 r14=0000000000000004 r15=00007f069d09a3f0
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind function 7f0910aec28f base 0x7f0910aec240 cie 0x7f091183b3d8 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
1455.024:0124:016c:warn:seh:dwarf_virtual_unwind backtrace: 0x7f0910aec28f: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/vulkan/03/libvulkan_intel.so + 0xec28f.
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec240: DW_CFA_def_cfa %rsp, 8
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec240: DW_CFA_offset %rip, -8
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind fde 0x7f0911840818 len 24 personality (nil) lsda (nil) code 7f0910aec240-7f0910aec2c8
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec240: DW_CFA_advance_loc 5
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec245: DW_CFA_def_cfa_offset 16
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec245: DW_CFA_offset %rbp, -16
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec245: DW_CFA_advance_loc 3
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec248: DW_CFA_def_cfa_register %rbp
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec248: DW_CFA_advance_loc 1
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec249: DW_CFA_offset %rbx, -24
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f0910aec249: DW_CFA_advance_loc1 90
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind next function rip=00007f0910ae5648
...

1455.024:0124:016c:warn:seh:dwarf_virtual_unwind backtrace: 0x7f093388c80c: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libc.so.6 + 0x11580c.
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f093388c805: DW_CFA_def_cfa %rsp, 8
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f093388c805: DW_CFA_offset %rip, -8
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind fde 0x7f093393f8d8 len 10 personality (nil) lsda (nil) code 7f093388c805-7f093388c816
1455.024:0124:016c:trace:unwind:execute_cfa_instructions 7f093388c805: DW_CFA_undefined %rip
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind next function rip=00007f093388c80c
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=00007f09338055a0 rcx=000000000002fa20 rdx=000000000002fa20
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   rsi=00007f05e6eb9aa0 rdi=0000000000000000 rbp=0000000000000000 rsp=0000000100ffeb98
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind    r8=0000000000000000  r9=0000000000000000 r10=0000000000000011 r11=00000000000000c0
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind   r12=0000000100fff6c0 r13=fffffffffffffb68 r14=000000000000003d r15=00000001000ff870
1455.024:0124:016c:trace:unwind:dwarf_virtual_unwind function 7f093388c80c base 0x7f093388c805 cie 0x7f093392a478 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip

Is this a Proton issue or as the crash implies, is Intel's Vulkan driver is at fault and I should file a Mesa bug report?

Not sure if this is the best place to report this, but I'm getting crashes from time to time:

Also had multiple crashes with what looks like the same message, usually when opening map or menu. Started turning everything but steam off, including 2nd display, ran with gamemode and RADV_PERFTEST=nosam VKD3D_CONFIG=no_upload_hvv env variables, had 2 about 2 hours long crash-free sessions, so fingers crossed it's not coincidence/random stroke of luck.

Not sure if this is the best place to report this, but I'm getting crashes from time to time:

Also had multiple crashes with what looks like the same message, usually when opening map or menu. Started turning everything but steam off, including 2nd display, ran with gamemode and RADV_PERFTEST=nosam VKD3D_CONFIG=no_upload_hvv env variables, had 2 about 2 hours long crash-free sessions, so fingers crossed it's not coincidence/random stroke of luck.

Even with that, I get random freezes where I get kick to the GDM login screen

@alosarjos please add PROTON_LOG=1 %command% to the launch parameters and upload the resulting steam-2054970.log (it will be in your home folder) after the game crashes, if the log is too big then compress as a .zip before uploading it. It would also be helpful to say how many crashes you've had and how long they have taken to occur.

@simifor Hope this helps:

steam-2054970.log

I have had lots of crashes, nothing in particular triggers them, could be 5 minutes of gameplay or 20....

But some of those times happened to be when opening the menu (But other times I opened it and worked just fine)

EDIT: Another log, this ime loading the game, didn't even get into gameplay: steam-2054970.log

Replying to [#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016301950)

I have amd-vulkan-prefixes package installed from AUR. https://aur.archlinux.org/packages/amd-vulkan-prefixes/ This allows me to easily chose if I want to use RADV or AMDVLK. I only needed to add vk_amdvlk %command% as a launch option in a steam.

Okay I made few more tests and it's kinda weird.
If I don't use any launch options then options menu bugs out.
If I use vk_amdvlk or vk_radv then everything works.
What makes no sense to me is why vk_radv is working when it is just suppose to be same as if I don't specify any driver.
I have set radv as a default driver to be used if not otherwise specified with AMD_VULKAN_ICD=RADV variable.

So, I never really had any issues launching the game, though certain proton versions cause it to crash on start up.

I can get 40-50fps in cities and 80-90fps in the countryside after starting the game, but every single time, after about 5-30 minutes the framerate will drop to 20-30fps and stay there no matter what area i'm in.
Restarting the game fixes it but only for another 5-30 minutes.

I'm not really sure if this is a linux configuration issue or an issue with the game itself though.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016561825

I experience the same thing. I am on an RTX 3060Ti with a Ryzen 5 3600, so for me that slowdown means going from just barely playable to completely useless.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016563062

I'm starting to think that there's a memory leak that's causing it. How much memory does the game use on average for you? It typically uses around 12-13gb for me.

I've been trying all the various launch commands suggested on my RX6950XT in this thread, but never got the fps higher than 25. Kept trying to change Proton versions without getting locked out and had nvtop on the other monitor and only got 5% gpu utilization. What I found maddening was when I open the System menu I get 60 fps and the gpu jumps up to 11%. Under all the tests the CPU has been at 20% except for when compiling shaders, then almost all are at 100.

Is there any possible way to make the game use more of the GPU or is entirely on the application itself.

I've been trying all the various launch commands suggested on my RX6950XT in this thread, but never got the fps higher than 25. Kept trying to change Proton versions without getting locked out and had nvtop on the other monitor and only got 5% gpu utilization. What I found maddening was when I open the System menu I get 60 fps and the gpu jumps up to 11%. Under all the tests the CPU has been at 20% except for when compiling shaders, then almost all are at 100.

Is there any possible way to make the game use more of the GPU or is entirely on the application itself.

That's how the game works, and the complain everyone has. How much CPU bottlenecked it is

When people say crash are your games actually crashing or is your driver timing out?
I didnt have a single crash but amdgpu kept timing out. On the 1st day i had really good performance around 50-100fps with RADV_PERFTEST=nosam command but then randomly it stopped doing anything and no matter what i did it never got past 20-50fps. At this point im on my 2nd 24h ban (i dont think its only the proton switching triggering it) and im refunding it and waiting for cracked version without denuvo or when they actually fix this because this is ridiculous. You literally cant troubleshoot anything because you just get banned.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016489633

I have the same exact issue but I have an Nvidia 1070, which doesn't use Mesa. I think the problem is not Mesa related. I am on ArchLinux, stable kernel.

On the 1st day i had really good performance around 50-100fps with RADV_PERFTEST=nosam command but then randomly it stopped doing anything and no matter what i did it never got past 20-50fps. At this point im on my 2nd 24h ban

Same thing happened to me. I had the game running decently, changed literally nothing, and then it would never start up with good performance again. For some reason it also started resetting all options every startup and going through the initial options/EULA step every time when going to main menu, even when quitting from gameplay. I tried deleting the prefix, deleting shader cache, uninstalled and redownloaded the game, no change to either issue. Also on my 2nd ban by now.

Game has a weird behaviour where it seems to not utilize CPU completely. Straight from the main menu CPU usage is capped around 35%(pic 1) and doesn't change throughout gameplay. When it does launch "properly"(pic 2) both resource usage and performance is comparable to Windows.

Disabling SAM has no impact on this, and whether the game launches with a good CPU utilization is seemingly random.
Here's proton logs for both launches on Proton 9 Beta. Proton 8.0-5 behaves the same, however I wasn't able to reproduce this on either Experimental or Bleeding Edge, where it seems to always get reduced CPU usage.
Low cpu usage log: steam-2054970.log
Expected cpu usage log: steam-2054970.log

And then there's also crashes as per comment above, although at least some of them are on game's side, since one of the common crashes on opening menu is widely reported on Windows as well. There's definitely some Linux crashes, but I guess that's better left for mesa folks.

EDIT: Thinking about it, not sure why I pegged it as a CPU usage issue, since it might also be the same deal but with GPU, and one just bottlenecks the other. But there's definitely something wrong in regard to resource usage.

Something about the very first time you run the game after a fresh install makes it run good and this can't be replicated neither by deleting the prefix nor the save data. Here are some findings that might be useful to someone.

On the first run the game does a long shader pre-compile which creates a file called shader.cache2 in the game directory. It looks like the game doesn't load it on subsequent runs, since deleting it will make the game pretend to do the pre-compile (much faster than the real one), but it either doesn't create the file at all or it's 24 MB instead of the real 2 GB. Performance with the fake cache is the same as subsequent launches with the real one.

You can make the game always do a real pre-compile by deleting the cache file and running with VKD3D_SHADER_CACHE_PATH=0, but you still get the bad performance.

So, what else does uninstalling the game through Steam remove that I might have missed? Because looking at the timestamps of the game files, they didn't get modified when I ran it the first time.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016940237

Thanks for the idea. After reading everyone's trial and error, and other things externally like docs I managed to put my game from 15-25fps to 100+ fps (still pending to reach vernworth, I reset my game for tests).

This only works for AMD GPU, I am sorry NVIDIA. But I will also thanks NVIDIA for giving the same idea, Shaders were my problem. NVIDIA solution was (in windows) to put shader cache limit to infinite.

Here's what I did.

1. Have RADV (MESA) installed, install AMDVLK.
2. Delete vkd3d-proton.cache* (all)
3. Delete shader.cache2 (games folder)
4. Install https://aur.archlinux.org/packages/amd-vulkan-prefixes/ (this is very important)
5. I haven't tested with other protons, but I am using GE-Proton-9-2 (eggroll)
6. Put as custom launcher for the game: vk_amdvlk %command%

The important part is deleting the old shader and using amd vulkan prefixes. I tried the default way, my default drivers are RADV and the game wouldn't stop crashing, low performance and menu looping as some people said it happened. I did the AMD_VULKAN_ICD= and AMD_VULKAN_ICD=AMDVLK and nothing changed, but after trying to manually load the AMDVLK Vulkan drivers via ICD Path it finally worked after deleting the shaders (that took a LOT of time), no crash so far and very stable and high FPS.

It seems we have a problem with RADV Shaders and loading correctly Vulkan Drivers with this game in specific. Other games behave normally without the need to use amd vulkan prefix. On them AMD_VULKAN_ICD works nicely, I know because I tested.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2017119513

I initially launched the game without any launch options (so using AMDVLK by default I assume?) and had the options menu bug described above with the looping cursor noise.

Based on above suggestion I launched with vk_amdvlk and that fixed the options problem and let me start the game. Worth noting it didn't rebuild the shader cache. However after closing the game, it would no longer get past the splash screens and got stuck on a black screen instead of the main menu. I've attached the log file from when this happened:

steam-2054970.log

Edit: I wonder if following your instructions and rebuilding the shader cache after setting vk_amdvlk would've got beyond the black screen issue.

I then switched to vk_radv. It rebuilt the shader cache and launched fine and the options menu bug was gone. I was able to play till after the tutorial (with decent performance) but then stopped as it was crashing pretty frequently.

It seems to work with either driver (although AMDVLK not so well for me) but what seemed to matter more was whatever the amd-vulkan-prefixes script is doing.

As far as I know it is only doing simple env setting to load vulkan drivers. Nothing more nothing less.

It makes the system to use the old method of finding drivers and set 32bits then 64bits into the env. Vulkan Arch Wiki

This only works for AMD GPU, I am sorry NVIDIA. But I will also thanks NVIDIA for giving the same idea, Shaders were my problem. NVIDIA solution was (in windows) to put shader cache limit to infinite.

I'm reading on the Steam forums that putting the shader cache limit to infinite has been consistently making performance better on Windows. Does anyone know how to do the same on Linux with an NVIDIA GPU? I get good results using the other launch params people are sharing, but unfortunately, I get nasty graphical glitches after playing for some time.

Hello @LordJakki, @brenmous, there's not a lot of components to https://gitlab.com/AndrewShark/amd-vulkan-prefixes/-/raw/main/amd_vulkan_prefixes.sh. I'm mildly curious if one of you can reproduce the misrendering, then try running the game with DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 %command% and see if that has any effect. I suspect it's not going to make a difference, but there's nothing else in that helper script besides forcing the game to see a single video driver vendor.

I removed vk_amdvlk, and I was able to reproduce the looping frozen options menu bug. I also get flickering black bars at the top and bottom of the screen.

Adding DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 has the same result.

Going back to vk_amdvlk fixes the issue.

Removing vk_amdvlk and instead trying AMD_VULKAN_ICD=amdvlk results in the options menu bug and flickering bars.

Pretty sure my previous issue of the black screen with amdvlk was because I was trying to launch with gamescope as well, so ignore that.

I can see that script is just setting variables so I understand it seems weird.

Hello @LordJakki, @brenmous, there's not a lot of components to https://gitlab.com/AndrewShark/amd-vulkan-prefixes/-/raw/main/amd_vulkan_prefixes.sh. I'm mildly curious if one of you can reproduce the misrendering, then try running the game with DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 %command% and see if that has any effect. I suspect it's not going to make a difference, but there's nothing else in that helper script besides forcing the game to see a single video driver vendor.

Replacing vk_amdvlk %command% with DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 %command% caused the options menu to bug out again and monitor to flicker between game and desktop like it was trying to render both at the same time.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2020864264

I have a RX 7900 XT and the driver crashes were also forcing me to reboot the computer. After updating to the latest Mesa main branch and disabling bar in vkd3d through no_upload_hvv I was able to play for a few hours without the driver crashing. I will do more tests today to see if I was just lucky.

For folks tinkering, please just be aware of the Denuvo anti-tamper. If you change Proton versions a few times it will lock you out of the game for 24 hours like the well-respected customer you are.

I have suggested to Valve customer service to add a warning something similar to "If the program you are changing versions of Proton on has anti-tamer DRM with a limited number of installs per day, changing this may count as a separate install and may lock you out of your software for a limited time". My first result seemed to be an automated reply stating the software isn't guaranteed to work and sent me to github for "troubleshooting". The game runs fine...we just need warnings against this kind of stuff. I understand it's new to Valve and their support team but this is something that does need addressed.

Replying to [#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2020864264)

Currently in a almost two hour session myself without crashes, using
VKD3D_CONFIG=no_upload_hvv gamemoderun gamescope -e -f -r 165 -h 2160 -H 2160 --hdr-enabled -- %command%

Plasma 6 with HDR on Arch with mesa from repositories, not mesa-git

HDR actually works better than on Windows. Performance right now is also good somehow, but I've also not been in the city for a while

https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2020864264 basically this. As much as I prefer RADV and their performance, in this game specifically I will say its impossible to play, low fps, menu looping (bug referenced earlier in comments), crashes every so often. AMDVLK is not crashing and the FPS is stable and high enough to enjoy the game so far.

My Mesa Drivers are package managed, maybe I should look into git and bite the bullet.

[#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2020864264) basically this. As much as I prefer RADV and their performance, in this game specifically I will say its impossible to play, low fps, menu looping (bug referenced earlier in comments), crashes every so often. AMDVLK is not crashing and the FPS is stable and high enough to enjoy the game so far.

My Mesa Drivers are package managed, maybe I should look into git and bite the bullet.

I can confirm it's not crashing on my machine as well. FPS is stable, but the frametime is still all over the place making it stuttery. From what I've heard, this is an issue with the game itself.

Today i installed Pop!_OS and when launching the game it gives me this error after the RE Engine logo, before the start menù.
Anyone has any idea on what is it?
I'm on NVIDIA GPU

Today i installed Pop!_OS and when launching the game it gives me this error after the RE Engine logo, before the start menù. Anyone has any idea on what is it? I'm on NVIDIA GPU

Add VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 to launch parameters

It doesn't change anything, sadly.
BTW Capcom Crash report is unable to provide a log, apparently, as it is abruptly ended. Error code 0x2000000.

Something I did today and got great results with my machine. I added 2 things so I can't say which one helped or both, but I am having great results.

1. Delete shader.cache2 and vkd3d-proton.cache(.write)
2. PROTON_NO_FSYNC=1 and gamemoderun to Steam Paramters Launch.
3. And I changed from Proton-GE-9.2 to Proton Experimental. Its late and I didn't test individually and I am not in the mood to be blocked by Denuvo, I am sorry, but I want to play tomorrow and not wait 24h.

Something is telling me gamemoderun and NO_FSYNC=1 made the difference for the stability of game.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2027872648

Can you at least define "great results"? How is it different than it was for you before? More FPS? More stable? What changed?

https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2027887172 I wasn't monitoring before since it was always low FPS (below FSYNC minimum, which means 30 or less, even less in cities).

The great result for me came the stability and actually smooth fps with freesync. Still not 60 fps dream, but I take a smooth above 30 fps for this game for now. Good enough.

I also tried running the game with PROTON_NO_FSYNC=1 set and managed to play for a noticeably longer time without the game crashing. Usually the game crashes anywhere between 5 to 120 minutes from launch and completely resets the session back to login screen.

I will do more testing later today to see if this indeed does effect the stability when compared to FSYNC being enabled.

I observed noticeably worse performance when FSYNC is disabled which I think is to be expected. Without exact measurements, I estimate the performance hit to be around 20% less in FPS at least on my system. For me the priority would be to have the game run stable even by sacrificing some performance.

I'm running the game on a rig with the following:

• AMD R7 3700X CPU
• AMD RX 7900XTX GPU
• 32GB of DDR4 RAM
• Arch Linux
• Hyprland VM (Wayland)
• Proton Experimental
• Latest mesa-git drivers (chaotic AUR)
• Performance CPU governor

• UPDATE *
  Game did crash very early into the next play session. This option does not effect stability but causes a noticeable performance hit.
  Randomness of the crashing makes it very hard to test different options.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016812988

After my own testing, I'm now convinced this is definitely correct in my case. Disable SAM/BAR has no actual effect. Sometimes I get a high framerate with high GPU usage when the game starts, and sometimes I don't, regardless of whether I have any environment variables at all.

Unfortunately, I've found that AMDVLK also does not actually prevent crashing. I was able to get a couple of hours of play without the system crashing, but that also seems to be random, and it happens with RADV as well. Still, sometimes, I start the game, and within a few minutes, I get a full lock up of the system and have to ALT + SysRq + REISUB to even get out of it.

AMD Ryzen 7 7800x3D
AMD Radeon RX 6800 XT
32 GB of RAM
Kubuntu 23.10
Wayland

After my own testing, I'm now convinced this is definitely correct in my case. Disable SAM/BAR has no actual effect. Sometimes I get a high framerate with high GPU usage when the game starts, and sometimes I don't, regardless of whether I have any environment variables at all.

I can also confirm this, and I have an Intel CPU and Nvidia GPU, so it does not seem to be tied to any specific architecture. The game sometimes starts with a good framerate, and sometimes it does not.

Also, I do not know if other people are experiencing this, but while on menus (e.g., inventory/trade screen/vocation skills), my FPS diminishes by a lot. I believe most of my crashes have been while on menus.

Furthermore, I have not experienced the "long shader cache loading" that some people had when starting the game for the first time. It took maybe 20 sec tops and the generated shader.cache2 has about 23 MiB; this also seems abnormal.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2028444012

I did some digging and found that people using Windows are experiencing the same crashes and other issues described here. It's the game, and mostly likely, only the devs can fix it.

Replying to [#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2028444012)

I did some digging and found that people using Windows are experiencing the same crashes and other issues described here. It's the game, and mostly likely, only the devs can fix it.

I have ~60h playtime and have had 2 crashes that hardlocked the machine and one which produced a report crash dialogue. I suspect only the latter was the game crashing. (One of the hardlocks was directly after leaving the mine start dungeon, and I have seen others reporting the same crash.)

People on windows are reporting being able to get 60 FPS in the cities. I get 40 (by the palace only 30) and wild jitter. My frame rate graph looks like a seismograph.

GPU 7900XTX
CPU 5950X

After running the game on windows, I get massively improved performance. It seems something is just not right on the linux side of things.

After running the game on windows, I get massively improved performance. It seems something is just not right on the linux side of things.

I don't like to admit it either but, completely true. Outside of the city on my RTX 3080 + Ryzen 5800x3D on windows the game feels great even with RT on. Switch over to Linux and....30-40 FPS in same area with no RT even. Unsure if DLSS is properly running but it's hard to mess with thanks to Denuvo constantly locking me out.

So you're saying that we are doomed to settle down to using Windows for this game? Hell, no. Can someone well versed on coding figure out what's making the game work properly on windows and preventing it from doing so on linux?

Come on folks, can we please remember that we're playing through a translation layer?

I've been playing this on Linux so far, thanks to folks in here offering tips. Is it great? No. Give it time, things will improve. Let's add constructive comments with logs and shit. This isn't a gamer forum, if your comment doesn't contain useful information for the community or devs, maybe go post in Steam's community.

Latest log of my latest session. Let's hope it helps. I'm using an r5 5600 and RX 6700XT. Can't wait for it to improve and get playable frame rates. It's a been a long time since the I got "good" frames... I miss them.

steam-2054970.log

Someone recently posted on protondb about trying out linux-lqx and having good performance on both cities and open world. I decided to put it to test on my own system and to my surprise it really works wonderfully. I add logs in case anyone wants to go through them.

steam-2054970.log

Someone recently posted on protondb about trying out linux-lqx and having good performance on both cities and open world. I decided to put it to test on my own system and to my surprise it really works wonderfully. I add logs in case anyone wants to go through them.

steam-2054970.log

What we really need is someone to test multiple times and compare results because they differ from one instance to the next with this game. People think they have a fix when they only tested once. I can start the game 5 times and get 45 fps in the main menu 3 times and 90 fps the other 2 times.

If you can tell us the fps in the same location you had before the kernel compared to after (after testing multiple starts), that would be helpful.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2039339646

Vermudian forest, I used to get erratic fps (about 20 to 30) with the low GPU usage. After installing the kernel and not using any options but PROTON _LOG=1 gamemoderun %command% the game manages to use 90% or more of the GPU constantly and about 60 to 70 fps on open areas as well as 50 to 80 fps on areas like Checkpoint rest area. By the way, linux-lqx uses performance governor by default instead of the schedutil employed by linux-zen. Is it bruteforcing fps by using this governor? Maybe.

I can also say that linux-lqx doubled my framerate, now I'm getting full system resource usage and performance close to windows.

To those testing the lqx kernel, on what Distro are you? What kernel were you using before? I'm curious if anyone with Arch and Zen kernel vs lqx

To those testing the lqx kernel, on what Distro are you? What kernel were you using before? I'm curious if anyone with Arch and Zen kernel vs lqx

EndeavorOS with Zen was what I was using, same distro but with LQX now.

To those testing the lqx kernel, on what Distro are you? What kernel were you using before? I'm curious if anyone with Arch and Zen kernel vs lqx

I'm on Arch BTW... jokes aside I was using linux-zen before making the change and the performance was awful.

I tested the lqx kernel on Kubuntu 23.10, and it did not fix anything. It still randomly has low framerate sometimes when I start the game and then randomly has high framerate when I start it other times. It also still randomly locks up the computer, forcing me to do a hard reset. I played for about 2 hours without any problems earlier but just started it now, and it froze within minutes.

I tested the lqx kernel on Kubuntu 23.10, and it did not fix anything. It still randomly has low framerate sometimes when I start the game and then randomly has high framerate when I start it other times. It also still randomly locks up the computer, forcing me to do a hard reset. I played for about 2 hours without any problems earlier but just started it now, and it froze within minutes.

The lock ups are still present on my system (arch) and they still preserve their random nature. I might've ommited to say that I have gamemode as one of steam's variables (gamemoderun %command%). I'll try without it and report back to see if it makes any difference whether it's on or off.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2040901166

That was one of the first things I tried. I've tried with gamemode on and off. I tried disabling MangoHud and the Steam Overlay. The Steam forums are filled with Windows players having the same issues. Getting better overall framerates is probably the best we can do for now. I think the crashes, bad frame timing in cities, etc. are things the game devs will have to fix.

Tried lqx kernel, performance definitely improved, like day and night. Game still randomly freezes, and with lqx kernel it freezes as fast as in 2-3 minutes, on default Arch kernel could last for hours, albeit at 12 fps.

UPD: Okay, now I got a system freeze on lqx kernel just while browsing files in dolphin, reverting back to stock kernel

Game became a stuttery mess as soon as I removed gamemode from the start options and audio is buggy af. On the other hand cpu and gpu usage skyrocketed in the start menu both got to 90% like wtf. This game needs a serious revamp on the optimization department. EDIT: It got fixed by deleting both caches in the game's folder.

steam-2054970.log

This LQX talk got me curious, so I whipped up a fresh Endeavour install to test it out. Quick specs summary: 5800X3D, 32 GB unremarkable RAM, 4070 Ti. Nvidia 550.67, kernel 6.7.12-lqx1-1-lqx. Game running on Proton Experimental bleeding-edge, launch options to avoid crashing in main menu due to Reflex: VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 %command%

The performance I'm getting still randomly alternates between two distinct states with about a 2x difference between them. Settings don't really seem to matter, but I tested this at 1440p on the High preset.

Good:

Bad:

You can keep flipping the coin and eventually get the good one, simply by quitting and restarting the game. I've also experienced it changing between the two states while playing. Subjectively I'd say that Liquorix gives a higher probability of getting the good outcome, something like >50% compared to the default CachyOS kernel where I see maybe 10%.

Edit: FWIW, after posting this I spent an hour grinding vocation XP with no stability issues.

I also tried Linux-lqx, not AUR version but the binary (they are the same for Archers, from AUR you build yourself and Community you get the same already in binary).

But before that I tried Linux-Zen, Stock then Liquorix, the truth is basically what our friend here said https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2041046605 there seems to be a higher probability to get the GOLDEN START with Lqx, I restarted the game 10 times and I don't need to go after the menu to verify, since the menu always runs 25 fps. And with the best start, I get a nice, beautiful 60 (60-75 variable) fps. They were basically 20% chance. Still low but Stock Kernel I wasn't able to get once a good start.

So no, my conclusion is that Liquorix doesn't fix the problem, its the game itself, it won't have a fix without the game patch, but Liquorix does provide a better chance to get higher performance in game.

But Liquorix, at least for me does come with some disadvantages, I noticed my boot time is noticeably worst and I am yet to see the full consequences of that (had to restart twice, first time made my whole system unstable), so use it at your own risk.

I ran the game with only PROTON_LOG=1 gamemoderun %command%.

I'll be providing logs with Stock Kernel and Liquorix. (as I was typing this part I was closing the game from a bad start and my system froze. which I won't say its because of Liquorix because this game has been doing this from time to time).

Liquorix Kernel

Bad Start

steam-2054970_bad_start.log

Good Start

Yet to be achieved, its HARD to get it with good fps, sorry after the 20th time I lost my will to try again, I only succeeded twice. Both times where only after full restart of pc.

Stock Kernel

Always a bad start

steam-2054970.log

Also tried lqx kernel (on Manjaro) and my first time running the game I am now getting up to 60fps in the wilderness, whereas before it would hover around the 30-ish mark. I can't report on bad starts yet, as it appears I got lucky first time. Just wondering then, what makes this kernel different? I do see better CPU usage than before.

Also tried lqx kernel (on Manjaro) and my first time running the game I am now getting up to 60fps in the wilderness, whereas before it would hover around the 30-ish mark. I can't report on bad starts yet, as it appears I got lucky first time. Just wondering then, what makes this kernel different? I do see better CPU usage than before.

I guess it has to do with the CPU governor set to performance and the optimizations tailored towards gaming. I haven't had any issues with framerates outside Vermund. That city is a CPU hog.

I should note that in my experience with the default arch kernel, the game will usually launch with "good performance" when the game is opened just after rebooting, dilly-dallying with other stuff first will usually result in a big performance hit. I Wonder if the observed liquorix improvement is due to trying the game just after rebooting.

I should note that in my experience with the default arch kernel, the game will usually launch with "good performance" when the game is opened just after rebooting, dilly-dallying with other stuff first will usually result in a big performance hit. I Wonder if the observed liquorix improvement is due to trying the game just after rebooting.

I just tried with the vanilla arch linux kernel and it gets me the same result as with the zen variant. Low frames and horrid performance. I think you're misleading people, man. It doesn't work. The only kernel that is able to bring good performance every time the game is loaded is linux-lqx. I know because I tested it many times. The crashes still exist and whenever they happen they crash the DE but don't lock up the system as with zen or vanilla kernels do, but the game can't be launched again unless the system is rebooted.

steam-2054970.log

Can any one with amdgpu try setting the card's power_dpm_force_performance_level to high or profile_peak

I have RX7800xt and when setting to high, the game have better chance to run in better performance (~80% success rate).
The game's main menu can run either ~30fps or 60fps capped randomly with my setup

What I shared is what I consistently saw across a dozen reboots, but just
because it happens with my configuration doesn't mean it'll also happen
with yours

On Sun, Apr 7, 2024, 12:11 AM Frank-MN @.***> wrote:

I should note that in my experience with the default arch kernel, the game
will usually launch with "good performance" when the game is opened just
after rebooting, dilly-dallying with other stuff first will usually result
in a big performance hit. I Wonder if the observed liquorix improvement is
due to trying the game just after rebooting.

I just tried with the vanilla arch linux kernel and it gets me the same
result as with the zen variant. Low frames and horrid performance. I think
you're misleading people, man. It doesn't work. The only kernel that is
able to bring good performance every time the game is loaded is linux-lqx.
I know because I tested it many times. The crashes still exist and whenever
they happen they crash the DE but don't lock up the system as with zen or
vanilla kernels do, but the game can't be launched again unless the system
is rebooted.

steam-2054970.log
https://github.com/ValveSoftware/Proton/files/14895720/steam-2054970.log

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2041303073,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EGWUNWV2NRSHKMLBHTY4DBPDAVCNFSM6AAAAABFD6R6SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGMYDGMBXGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

I am definitely seeing amdgpu crashes for this game (both on liquorix and default kernels):

DD2-gfxhub-pagefault-liquorix-kernel.log
DD2-gfxhub-pagefault-default-kernel.log

See error:

amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32787, for process DD2.exe pid 6676 thread vkd3d_queue pid 6841)
amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000000000000c000 from client 10
amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00600A31
amdgpu 0000:2f:00.0: amdgpu:          Faulty UTCL2 client ID: CPC (0x5)
amdgpu 0000:2f:00.0: amdgpu:          MORE_FAULTS: 0x1
amdgpu 0000:2f:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:2f:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          RW: 0x0
amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:6 pasid:32787, for process DD2.exe pid 6676 thread vkd3d_queue pid 6841)
amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000000000000c000 from client 10
amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:2f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:2f:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:2f:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
amdgpu 0000:2f:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          RW: 0x0
amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32787, for process DD2.exe pid 6676 thread vkd3d_queue pid 6841)
amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000000000000c000 from client 10
amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00600A31
amdgpu 0000:2f:00.0: amdgpu:          Faulty UTCL2 client ID: CPC (0x5)
amdgpu 0000:2f:00.0: amdgpu:          MORE_FAULTS: 0x1
amdgpu 0000:2f:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:2f:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          RW: 0x0
amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:6 pasid:32787, for process DD2.exe pid 6676 thread vkd3d_queue pid 6841)
amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000000000000c000 from client 10
amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:2f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:2f:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:2f:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
amdgpu 0000:2f:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          RW: 0x0
amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:7 pasid:32784, for process gamescope pid 6332 thread gamescope pid 6332)
amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000000000000c000 from client 10
amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00700A31
amdgpu 0000:2f:00.0: amdgpu:          Faulty UTCL2 client ID: CPC (0x5)
amdgpu 0000:2f:00.0: amdgpu:          MORE_FAULTS: 0x1
amdgpu 0000:2f:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
amdgpu 0000:2f:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          RW: 0x0
amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:7 pasid:32784, for process gamescope pid 6332 thread gamescope pid 6332)
amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x000000000000c000 from client 10
amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
amdgpu 0000:2f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
amdgpu 0000:2f:00.0: amdgpu:          MORE_FAULTS: 0x0
amdgpu 0000:2f:00.0: amdgpu:          WALKER_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
amdgpu 0000:2f:00.0: amdgpu:          MAPPING_ERROR: 0x0
amdgpu 0000:2f:00.0: amdgpu:          RW: 0x0

Also hwinfo and drivers:

• AMD Ryzen 9 5950X
• AMD Radeon RX 7900 XTX

Computer Information:
Manufacturer: Micro-Star International Co., Ltd.
Model: MPG X570 GAMING EDGE WIFI (MS-7C37)
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 9 5950X 16-Core Processor
CPU Family: 0x19
CPU Model: 0x21
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 5083 MHz
32 logical processors
16 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Operating System Version:
"openSUSE Tumbleweed" (64 bit)
Kernel Name: Linux
Kernel Version: 6.8.2-1-default
X Server Vendor: SUSE LINUX
X Server Release: 12302005
X Window Manager: wlroots wm
Steam Runtime Version: steam-runtime_0.20240304.79797
Video Card:
Driver: AMD AMD Radeon RX 7900 XTX (radeonsi, navi31, LLVM 17.0.6, DRM 3.57, 6.8.2-1-default)
Driver Version: 4.6 (Compatibility Profile) Mesa 24.0.3
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 119 Hz
VendorID: 0x1002
DeviceID: 0x744c
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 27.56" x 15.35" (31.54" diag), 70.0cm x 39.0cm (80.1cm diag)
Primary VRAM: 24576 MB
Sound card:
Audio device: ATI R6xx HDMI
Memory:
RAM: 15902 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 937803 MB
Largest Free Hard Disk Block: 235676 MB
Storage:
Number of SSDs: 4
SSD sizes: 2000G,1000G,1000G,60G
Number of HDDs: 0
Number of removable drives: 0

I should note that in my experience with the default arch kernel, the game will usually launch with "good performance" when the game is opened just after rebooting, dilly-dallying with other stuff first will usually result in a big performance hit. I Wonder if the observed liquorix improvement is due to trying the game just after rebooting.

Here's a nice plot twist. After a fresh boot with the kernel under test I started the game 10 times and checked how often I got the good performance. Nothing else changed.

6.6.25-1-lts: 10%
6.8.4-arch1-1: 10%
6.8.4-lqx1-1-lqx: 20%
6.7.12-lqx1-1-lqx: 90%
6.7.9-arch1-1: 30%

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2041470318

Do you have amd-pstate enable on your boot parameters? I have it on on both grub and systemd-boot (amd_pstate=active/guided) and the game launches at full speed in tandem with linux-lqx 6.8.4 every time. I'll try without the boot parameters and report back. I assume it will use acpi driver instead because that's what it's doing on intel cpus.

EDIT: There's no difference in performance but using acpi_freq driver hard locks the system whenever the game crashes.

Replying to [#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2041470318)

Do you have amd-pstate enable on your boot parameters? I have it on on both grub and systemd-boot (amd_pstate=enable/guided) and the game launches at full speed in tandem with linux-lqx 6.8.4 every time. I'll try without the boot parameters and report back. I assume it will use acpi driver instead because that's what it's doing on intel cpus.

EDIT: There's no difference in performance but using acpi_freq driver hard locks the system whenever the game crashes.

I'm normally on acpi_cpufreq, here are the results for amd_pstate. In all cases using governor performance.

6.8.4-lqx1-1-lqx + amd_pstate=guided: 10%
6.8.4-lqx1-1-lqx + amd_pstate=active: 0%
6.7.12-lqx1-1-lqx + amd_pstate=guided: 30%
6.7.12-lqx1-1-lqx + amd_pstate=active: 50%

I also tried to replicate the standout result from before, but that didn't quite end up panning out:
6.7.12-lqx1-1-lqx + acpi_cpufreq: 60%

After disabling VRR and locking to 60Hz, my gameplay is pretty much solid 60 fps with only drops to the 50s in vernworth. Perhaps not coincidentally, it seems like most, if not all, of my freezes take place in vernworth, which explains why I can go hours without freezing when I'm outside that city. All of this is my observation after several play sessions with the lqx kernel on AMD 7800x3d and 6800 XT.

New developments that might help us, linux gamers on Arch or Arch-based distros. TLDR. You can enable like this:

Create /etc/sysctl.d/80-gamecompatibility.conf and add this,
vm.max_map_count = 2147483642
vm.min_free_kbytes = 1048576​

https://lists.archlinux.org/archives/list/[email protected]/thread/7I4PNTZNRKUYFATOKXU3P6LKL33H5PMW/

EDIT: It might be already enabled by now on ARCH. You can check with this: cat /usr/lib/sysctl.d/10-arch.conf

One thing I've noticed is minimizing the game seems to make the game enter bad performance mode, I haven't seen it work the other way round yet. This is on EOS with the lqx kernel.

lqx kernel is the only kernel for me that reliably gets the "good performance" boot. The problem is that "good performance" has very frequent system hangs. So the options right now are 20-50fps but very rare hangs or 40-100 fps but frequent system hangs. Pick your poison.

Do you think it would still be possible to make it playable on the Steam Deck? I see in many videos that the performance monitor only shows 30 percent utilization for the CPU and around 60-70 for the GPU, which is too low for it to run properly. I think that 30 FPS would be possible with low graphics settings

I think it would depend on a Linux kernel rework specifically for that
device.

On Mon, Apr 8, 2024, 2:38 PM Seisuke @.***> wrote:

Do you think it would still be possible to make it playable on the Steam
Deck? I see in many videos that the performance monitor only shows 30
percent utilization for the CPU and around 60-70 for the GPU, which is too
low for it to run properly. I think that 30 FPS would be possible with low
graphics settings

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2043603432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHTDTUYVZT2WSMM4M3HWA73Y4L54VAVCNFSM6AAAAABFD6R6SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBTGYYDGNBTGI
.
You are receiving this because you commented.Message ID:
@.***>

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2041827913

Be careful with this, in the article it says that vm.max_map_count will be set to 1048576, not 2147483642, you have these mixed up.

And I am not sure where from vm.min_free_kbytes and value of 2147483642 come from, I wouldn't touch defaults on this one

Replying to [#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2041827913)

Be careful with this, in the article it says that vm.max_map_count will be set to 1048576, not 2147483642, you have these mixed up.

And I am not sure where from vm.min_free_kbytes and value of 2147483642 come from, I wouldn't touch defaults on this one

I got it from some people who had it working fine for a while, but now that Arch released their fix officially I stuck to the distro's solution.

You are not only fiddling with things you have no idea how it will affect your kernel memory usage as well doing it completely wrong.

1. vm.max_map_count can't go above 1048576.
2. vm.min_free_kbytes is reserved kilobytes for kernel, you are literally putting 1GB ram aside just for kernel. Waste of memory and you get nothing from that amount. 256MB? Ok, still a lot but not that worrisome. You are setting yourself to be OOM if you have small RAM in your system.

You are not only fiddling with things you have no idea how it will affect your kernel memory usage as well doing it completely wrong.

1. vm.max_map_count can't go above 1048576.

You can set vm.max_map_count to 2147483647(max value of signed 32bit int)

sudo sysctl -w vm.max_map_count=2147483647
vm.max_map_count = 2147483647

sudo sysctl -w vm.max_map_count=2147483648
sysctl: setting key "vm.max_map_count": Invalid argument

cat /proc/sys/vm/max_map_count
2147483647

The value 2147483642 is used by Valve for their Steam OS.

ssh deck@billli11-steampal cat /proc/sys/vm/max_map_count 
2147483642

I understand you can put a i32, but do you have this much memory? You are basically putting 2TB to map memory. We gotta be careful when we tell people to do things that affect kernel usage. Mine is set default to 1GB because I can and needed for Star Citizen.

Here's the default result.

And here is with 2147483642 set for max_map_count. No difference.

What I am saying is: While I agree increasing this can help (which helped me a lot in many games) we need to be careful before telling people to put huge numbers

Just for lolz, I decided to test setting the performance governor on vanilla arch Linux and linux-zen just to see if the performance on this game would be similar to lqx Linux. Results, lqx outperforms both linux and linux-zen. I don't know what black magic liquorix developers enable on their linux kernel flavor.

I understand you can put a i32, but do you have this much memory? You are basically putting 2TB to map memory. We gotta be careful when we tell people to do things that affect kernel usage. Mine is set default to 1GB because I can and needed for Star Citizen.

The problem is the word can, the setting "can" set as high as max of i32, should or should not is a difference matter.

When accessing the options menu from the title screen or in-game, the cursor movement sound starts looping and it becomes impossible to exit the menu or change any options. It's not a total freeze, though, as the option categories can still be navigated. This happens on both Proton 9 and experimental.

I ran in to the same issue on Nvidia and was able to make it go away by disconnecting my HDMI capture card before starting the game.

That's interesting: I've read about many performance issues (and I can't even start a new game), but apparently there aren't many who share our options menu problem? I also noticed subtle flickering of the items on the right side of the screen, as if some input is rapidly switching between them. I don't have a capture card, but I've tried to isolate anything that might be considered an input device -- controllers, mice and keyboards, tablet, external audio interface, and so on -- but nothing seems to work in my case. I'm probably missing something.

Been following here for a bit, something I haven't seen mentioned that I do notice is a strange correlation between CPU and GPU utilization. There are certain directions I can look that raises CPU utilization that then causes a decrease in GPU utilization and often times vice versa. I notice this in the first village, if looking towards the only inn there CPU util rises and GPU will drop to around 30-40%. A little stranger then is that looking at the ground will cause GPU util to go up but CPU to go down which doesn't make much sense.

For reference
CPU: R5 5600
GPU: RX 6700 XT

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2049775689

Don't know how much RAM you have but we share the same system specs and the game is running much better (not perfect) with mesa-git and linux-lqx

GPU usage going down while FPS still under target is one or more CPU threads blocking and limiting how much your GPU gets to do and fully expected.
That's the whole optimization = bad thing, basically.

Personally I find it more interesting that no one has even mentioned ray tracing being unavailable past pretty much the initial report. Does anyone care? Is anyone working on it? Does anyone even know why it isn't working? Is Capcom deliberately blocking it under Wine like they have done before?

Lqx does seem to allow the game to run well enough sometimes, I find I also need to force GPU core clock to run at the fastest it can at all times to actually get up to 60fps ever. I agree with the previous comment about some of this at least being a linux specific issue, same hardware on windows does perform much better with proper utilization

System Specs
OS: Arch Linux x86_64
Kernel: 6.8.4-zen1-1-zen
Resolution: 1920x1080
DE: GNOME 46.0
WM: Mutter
CPU: AMD Ryzen 5 5600 (12) @ 3.800GHz
GPU: AMD ATI Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT
Memory: 5201MiB / 32002MiB

The fact we're playing through a compatibity layer and we're getting somehow playable fps is a win for us linux players. I'm sure valve engineers will find a fix such as the one devised when Elden Ring was a stutter fest. Time will tell. By now with the linux-lqx I have logged closed to 100 hours playtime and only struggling with Venworth and some small towns with lots of NPCs.

One very obvious thing that linux-lqx does is to heavily prioritize scheduling on the physical cores instead of the "hyperthreads". However, setting WINE_CPU_TOPOLOGY=8 doesn't improve chances of a good launch, instead it also ruins the chances with linux-lqx. I tried messing around with higher limits to find the breaking point, but all that got me was yet another Denuvo ban.

I tried comparing logs between a good and bad launch, but I can't tell them apart. I'll attach them in case someone else can find something.
steam-2054970-bad.log
steam-2054970-good.log

I tried comparing logs between a good and bad launch, but I can't tell them apart. I'll attach them in case someone else can find something. steam-2054970-bad.log steam-2054970-good.log

The frequency of most log messages is roughly the same, though in the bad log there's a 70% increase in the following:

    498 warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Incrementing frame latency semaphore beyond max latency. Did application forget to acquire? (new count = 2, max latency = 1)
    255 warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Incrementing frame latency semaphore beyond max latency. Did application forget to acquire? (new count = 3, max latency = 1)

Not really sure what to do with that, though.

The good log also exclusively has: warn:vkd3d-proton:dxgi_vk_swap_chain_record_render_pass: Application is presenting user index 1, but it has never been rendered to.

About ray tracing, there is a file steamapps/common/Dragons Dogma 2/config.ini where you can set RayTracingEnable=ON . Then in game settings graphics menu it shows Raytracing ON, however, it is greyed out and cannot be changed further. Also, I am not sure if that actually changes the rendering in the game.

About ray tracing, there is a file steamapps/common/Dragons Dogma 2/config.ini where you can set RayTracingEnable=ON . Then in game settings graphics menu it shows Raytracing ON, however, it is greyed out and cannot be changed further. Also, I am not sure if that actually changes the rendering in the game.

No. You can also turn on NVIDIA Reflex (which works and doesn't crash the game at launch if you're using REFramework, BTW) and then disable the Vulkan extension and the game will still say it's on (which it cannot possibly be) but grayed out.

@simifor Hope this helps:

steam-2054970.log

I have had lots of crashes, nothing in particular triggers them, could be 5 minutes of gameplay or 20....

But some of those times happened to be when opening the menu (But other times I opened it and worked just fine)

EDIT: Another log, this ime loading the game, didn't even get into gameplay: steam-2054970.log

I would just like to add onto the pile because I am absolutely sick of this game crashing every 5 minutes. Either I get good performance and it crashes quickly or I am hard locked to 30fps and it doesn't seem to crash (I stop playing after a few minutes anyways due to the unbearable stuttering). I'm on a fresh Arch install, corectrl underclocked my 7900XTX, tried every command arg listed here and even more than that in as many orders as Denuvo will allow, switched to lqx-kernel, nothing has worked for me. Here is my log:
steam-2054970.log
I can also post my journalctl, but I checked through it and didn't see anything related to gpu crashes.

Hardware:
AMD Ryzen 7 5800X3D
AMD Radeon RX 7900 XTX (Merc)

Weird. I'm also on lqx and it has booted with good performance every time.
Try deleting game cache and reboot your system. A weird bug that I've
noticed is that the game will crash my PC as soon as it resumes from sleep
and the game is run. Once again the issue seems to be on the GPU drivers
(radeonsi). Hope new upcoming patch and, hopefully, new drivers make the
game more bearable. I also forget this common occurrence with the game. The
audio gets all glitchy in the start menu.

On Tue, Apr 23, 2024, 7:29 PM Clark Hoffman @.***>
wrote:

@simifor https://github.com/simifor Hope this helps:

steam-2054970.log
https://github.com/ValveSoftware/Proton/files/14732070/steam-2054970.log

I have had lots of crashes, nothing in particular triggers them, could be
5 minutes of gameplay or 20....

But some of those times happened to be when opening the menu (But other
times I opened it and worked just fine)

EDIT: Another log, this ime loading the game, didn't even get into
gameplay: steam-2054970.log
https://github.com/ValveSoftware/Proton/files/14732878/steam-2054970.log

I would just like to add onto the pile because I am absolutely sick of
this game crashing every 5 minutes. Either I get good performance and it
crashes quickly or I am hard locked to 30fps and it doesn't seem to
crash (I stop playing after a few minutes anyways due to the unbearable
stuttering). I'm on a fresh Arch install, corectrl underclocked my 7900XTX,
tried every command arg listed here and even more than that in as many
orders as Denuvo will allow, switched to lqx-kernel, nothing has worked for
me. Here is my log:
steam-2054970.log
https://github.com/ValveSoftware/Proton/files/15084735/steam-2054970.log
I can also post my journalctl, but I checked through it and didn't see
anything related to gpu crashes.

Hardware:
AMD Ryzen 7 5800X3D
AMD Radeon RX 7900 XTX (Merc)

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2073810082,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHTDTUZPVAAN2FNZF3U5HVDY64DHZAVCNFSM6AAAAABFD6R6SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZTHAYTAMBYGI
.
You are receiving this because you commented.Message ID:
@.***>

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2073810082

I gave up and dual booted into Windows. And apparently game kinda acts more or less the same there. The only key difference is that in case of a crash it actually allows to continue playing. It starts with good performance, rather quickly it "crashes", crash report tool appears on screen, but game process does not exit or freezes/hangs like on Linux, instead it proceeds in this "low performance" mode, with stuttering and 30fps. Something really wrong with the game itself, I doubt tweaking settings and environment can fix software problem in game code.

I had a a lot of experiences with crashing, then I ran mprime and got errors. After that I fixed ram clocks in bios, made sure mprime default torture test run for half an hour without errors. Now the game runs very reliably with - what seems to me - pretty good performance (no windows install to compare). That is arch linux, x11, zen kernel, nvidia.

After today's game update, at least I think that's what did it, the game now always launches with the good performance even on plain old 6.8.7-arch1-1. As for crashing, I've put about 70 hours into it on Linux and have had maybe 3 crashes during gameplay.

I can confirm that the update brought the ultimate fix for the game. I'm
currently using linux-zen and mesa (stable) and the game launches at full
speed. It also feels smoother in the frame time department.

On Thu, Apr 25, 2024, 12:35 AM Robert Syring @.***>
wrote:

After today's game update, at least I think that's what did it, the game
now always launches with the good performance even on plain old
6.8.7-arch1-1. As for crashing, I've put about 70 hours into it on Linux
and have had maybe 3 crashes during gameplay.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2076470055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHTDTU7TAL6GK73O5BVFXELY7CP4JAVCNFSM6AAAAABFD6R6SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZWGQ3TAMBVGU
.
You are receiving this because you commented.Message ID:
@.***>

Just tried this morning hoping the new update would fix the crashing. Performance is definitely better, but I still crashed after about 5 minutes. I also ran mprime tests and it passed all sizes (after a long time)
steam-2054970.log.zip
EDIT: Just tried playing again, and this time it resulted in a fullblown gpu page fault. I will post the journalctl logs for this one to:
steam-2054970.log.zip
http://0x0.st/XHab.txt

Yep, the new patch certainly brings joy for us. Restarted the game 5 times and 5 times got this result.

Double fps right from beginning, I'm sorry I can't test right now since I am working, but the old results are here: https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2045087130

All the update did was make the game launch with good performance all the time, the crashes are still there.

Has anyone tried the new update on the Steam Deck? And whether the frame rate is better there?

Don't have the steam deck but I don't think you'll see benefits.

On Thu, Apr 25, 2024, 2:30 PM Seisuke @.***> wrote:

Has anyone tried the new update on the Steam Deck? And whether the frame
rate is better there?

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2078121358,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHTDTU3ZPSYNJGKWJZY7WQTY7FRW5AVCNFSM6AAAAABFD6R6SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYGEZDCMZVHA
.
You are receiving this because you commented.Message ID:
@.***>

Can do a +1 to the update helping linux performance.

Has anyone tried the new update on the Steam Deck? And whether the frame rate is better there?

Still running bad on Steam Deck.

sub 30 roaming sub 20 in town.
It's mostly cpu and ram (using ~19GiB of ram and cause swaping) bottleneck, not fps diff between FSR quality or performance.

The game also keep changing graphics setting by itself.
Setting texture to high(0.25GB) (which can cause running out of memory) and rendering mode to progressive.

So I am trying this again after the most recent patch and now, I can't even get into the game with a "malloc(): unsorted double linked list corrupted with logging" with the latest Mesa and an Intel Arc A770. Not sure what has exactly changed to cause this but this has gotten even worse.

Edit: Removing mangohud fixed it, although it worked before.

Has anyone tried the new update on the Steam Deck? And whether the frame rate is better there?

Still running bad on Steam Deck.

sub 30 roaming sub 20 in town. It's mostly cpu and ram (using ~19GiB of ram and cause swaping) bottleneck, not fps diff between FSR quality or performance.

The game also keep changing graphics setting by itself. Setting texture to high(0.25GB) (which can cause running out of memory) and rendering mode to progressive.

Thanks for the feedback. It seems like the resource usage is better on the Steam deck. At least not quite optimal yet, which has a more positive effect on the FPS. However, even without FSR, the game runs almost 50 percent better on the deck with the update. There is still a lot of room for improvement. And maybe Valve will also bring an update to make it playable at full speed.

This is still causing system freezes for me. Do we know if it's something on the game side or on the Proton side?

This is still causing system freezes for me. Do we know if it's something on the game side or on the Proton side?

This is just speculation, but I noticed that AMD users on Windows were having this freeze and reported that it was fixed after AMD released a driver update for it. There is currently a Mesa issue, but it has gained just about as much traction from devs as this one.

Anyone tried HDR? it's disabled for me in the game settings despite being enabled in plasma display settings, monitor HUD also says HDR is enabled.

HDR worked fine for me when I tried it in the weeks after release. Also on Plasma 6, with gamescope --hdr-enabled (I don't think there's a way to get HDR working without gamescope)

I was able to make the game go to its full potential with my setup.

cpu: 7800x3d
gpu: 7900xtx
os: archlinux

fix for ring gfx_0.0.0 timeout:

follow issue https://gitlab.freedesktop.org/drm/amd/-/issues/3131

fix for random gpu page fault:

it seems that with radv something wrong is generated using aco, this crashes the game.
the same problems are not present with amdvlk.

workaround for enable ray tracing:

it seems that the game checks if you are using wine and does not allow to enable ray tracing, just use this command to bypass the check

sed -i 's/wine_/hack_/g' ~/.local/share/Steam/steamapps/common/Dragons\ Dogma\ 2/DD2.exe

workaround for enable ray tracing with amdvlk:

it seems that with the amdvlk driver not all the features required by vkd3d are available, but the ones used by this game are available, I modified the source to circumvent the control

 diff --git a/libs/vkd3d/device.c b/libs/vkd3d/device.c
index 9163cb8f..a6a88fdf 100644
--- a/libs/vkd3d/device.c
+++ b/libs/vkd3d/device.c
@@ -7509,6 +7509,7 @@ static D3D12_CONSERVATIVE_RASTERIZATION_TIER d3d12_device_determine_conservative
 
 static bool d3d12_device_supports_rtas_formats(struct d3d12_device *device, const VkFormat *format, size_t count)
 {
+    return true;
     const struct vkd3d_vk_instance_procs *vk_procs = &device->vkd3d_instance->vk_procs;
     VkFormatProperties properties;
     size_t i;

fix for frame rate drop in big city

the game especially inside the cities has a constant change of fps that make the game seem even more laggy than it should be.

• you have to turn off vsync in the game
• you must have a 144hz monitor
• you have to turn off the maximum fps in the game

now via mangohud you need to force maximum 48fps.
48 fps is not a random number, it is exactly 144(hz)/3.

with a monitor where hz is not a multiple of fps it is not possible to do this because some frames would be dropped or shown late.

60fps besides not being great anyway my hardware can't handle it in 4k in ultra+rt without fsr3.

MANGOHUD_CONFIG="no_display,fps_limit=48,fps_limit_method=early,fps_sampling_period=333,vsync"

@andrew-ld Thanks. I tried the RTX fix and it seems to work.

I think the problem of crashing persists with Proton experimental. Opening the pause menu often, but not always, freezes the system and destroys the desktop session.

steam-2054970.zip

heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: TCP (0x8)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x1
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32785)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:  in process DD2.exe pid 12329 thread vkd3d_queue pid 12429)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:   in page starting at address 0x00003afa38f93000 from client 10
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MORE_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          WALKER_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          MAPPING_ERROR: 0x0
heinä 01 01:13:36 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu:          RW: 0x0
heinä 01 01:13:46 mycomputer kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4221506, emitted seq=4221509
heinä 01 01:13:46 mycomputer kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process DD2.exe pid 12329 thread vkd3d_queue pid 12367
heinä 01 01:13:46 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GPU reset begin!
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:47 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:47 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:48 mycomputer kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
heinä 01 01:13:48 mycomputer kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
heinä 01 01:13:48 mycomputer kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
heinä 01 01:13:48 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: MODE1 reset
heinä 01 01:13:48 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GPU mode1 reset
heinä 01 01:13:48 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GPU smu mode1 reset
heinä 01 01:13:48 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GPU reset succeeded, trying to resume
heinä 01 01:13:48 mycomputer kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
heinä 01 01:13:48 mycomputer kernel: [drm] VRAM is lost due to GPU reset!
heinä 01 01:13:48 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: PSP is resuming...
heinä 01 01:13:48 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: reserve 0x1300000 from 0x84fc000000 for PSP TMR
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: RAP: optional rap ta ucode is not available
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: SMU is resuming...
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e7e00 (78.126.0)
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: SMU driver if version not matched
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: SMU is resumed successfully!
heinä 01 01:13:49 mycomputer kernel: [drm] DMUB hardware initialized: version=0x07002A00
heinä 01 01:13:49 mycomputer kernel: [drm] kiq ring mec 3 pipe 1 q 0
heinä 01 01:13:49 mycomputer kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: recover vram bo from shadow start
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: recover vram bo from shadow done
heinä 01 01:13:49 mycomputer kernel: amdgpu 0000:0f:00.0: amdgpu: GPU reset(2) succeeded!

System:
  Kernel: 6.9.7-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.2 Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Desktop Mobo: ASRock model: X570 Taichi serial: <superuser required>
    UEFI: American Megatrends v: P5.60 date: 01/18/2024
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
    charge: 100% (should be ignored) status: discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 5800X3D bits: 64 type: MT MCP arch: Zen 3+
    rev: 2 cache: L1: 512 KiB L2: 4 MiB L3: 96 MiB
  Speed (MHz): avg: 2566 high: 3400 min/max: 2200/4549 boost: enabled cores:
    1: 2879 2: 2200 3: 2878 4: 3400 5: 2880 6: 2200 7: 2200 8: 2200 9: 2800
    10: 2200 11: 2200 12: 2200 13: 2878 14: 2878 15: 2200 16: 2876
    bogomips: 108800
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
    vendor: Sapphire PULSE driver: amdgpu v: kernel arch: RDNA-3 bus-ID: 0f:00.0
  Device-2: Realtek Streamplify CAM driver: snd-usb-audio,uvcvideo type: USB
    bus-ID: 5-3:3
  Display: wayland server: X.Org v: 24.1 with: Xwayland v: 24.1.0
    compositor: gnome-shell driver: dri: radeonsi gpu: amdgpu resolution:
    1: 2560x1440~240Hz 2: 2560x1440~75Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.1.2 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 7900 XT (radeonsi navi31 LLVM
    18.1.6 DRM 3.57 6.9.7-200.fc40.x86_64)
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel
    bus-ID: 0f:00.1
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel bus-ID: 11:00.4
  Device-3: HP HyperX Cloud Alpha Wireless
    driver: cdc_acm,hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 1-2.2:5
  Device-4: RODE Microphones RØDE NT-USB Mini
    driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 3-5:4
  Device-5: Realtek Streamplify CAM driver: snd-usb-audio,uvcvideo type: USB
    bus-ID: 5-3:3
  API: ALSA v: k6.9.7-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 05:00.0
  IF: wlp5s0 state: down mac: <filter>
  Device-2: Intel I211 Gigabit Network vendor: ASRock driver: igb v: kernel
    port: f000 bus-ID: 07:00.0
  IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB bus-ID: 3-2:2
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 3.64 TiB used: 1.79 TiB (49.1%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 4TB size: 3.64 TiB
    temp: 48.9 C
Partition:
  ID-1: / size: 3.64 TiB used: 1.79 TiB (49.1%) fs: btrfs dev: /dev/dm-0
    mapped: luks-765cb1ef-1195-42ea-a526-06f1e57c6cbc
  ID-2: /boot size: 973.4 MiB used: 389.8 MiB (40.0%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 3.64 TiB used: 1.79 TiB (49.1%) fs: btrfs dev: /dev/dm-0
    mapped: luks-765cb1ef-1195-42ea-a526-06f1e57c6cbc
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.2 MiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 38.5 C mobo: 41.0 C gpu: amdgpu temp: 58.0 C
  Fan Speeds (rpm): fan-1: 612 fan-2: 0 fan-3: 910 fan-4: 548 fan-5: 553
    fan-6: 2596 fan-7: 540 gpu: amdgpu fan: 595
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 4.94 GiB (15.8%)
  Processes: 448 Uptime: 1h 36m Init: systemd target: graphical (5)
  Packages: 23 Compilers: gcc: 14.1.1 Shell: Zsh v: 5.9 inxi: 3.3.34

I think the problem of crashing persists with Proton experimental. Opening the pause menu often, but not always, freezes the system and destroys the desktop session.

steam-2054970.zip
Journal output
System specs

After a tipoff elsewhere, I started testing the game with different versions of GE-Proton9. This wasn't easy thanks to Denuvo (😮‍💨) but working backwards from GE-Proton9-9, I found that GE-Proton9-6 was the latest version I could find that consistently exhibits this crash. While I can't say with 100% confidence that the crash is entirely gone, I can say that with GE-Proton9-5 I've been able to have multiple long game sessions with no crashing. Perhaps something changed in Proton thereabouts?

@mattipulkkinen try with amdvlk instead of mesa

follow my tips
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2143465327

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2016489633

Have exact same issue with NVIDIA.

Was able to launch game with Proton-8, Steam on Arch. Plays ok, but has massive artifact issues in cutscenes and sometimes crashes.

@Billli11
thanks! Yeah smth was borked and I don't know why but the game was on proton 8 for some reasons.....putting it on experimental and then applying the workaround helped! Thanks!

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2143465327

I can verify that I'm also havin page fault crashes when running this game through mesa. Installing amdvlk seems to have solved the crashes and also smoothed the frame times a bit. I was unable to enable RT though.

I've not experienced any crashes duo to default power or frequency settings with the latest kernel (6.8-6.10.6). Using lact, I've increased the power limit to 402w (average draw 350w) and max clock is set to 2975mhz. VRAM remains untouched (my GPU doesnt like vram overclock).

My setup:

• CPU: 7800X3D
• GPU: 7900XTX sapphire pulse
• Kernel: xanmod-6.10.6
• OS: Nixos (nixos-unstable branch)
• Proton: Experimental and Proton GE 9.11 (Older proton versions seem to have issues)

Hello everybody

i have a issue with this game and steam support ask me to go here with it
so as you know its about DD2

the game play smoothly most of the time and is more stable than 3 month ago
but, since i play it on Linux it crashes with the same Xid 109 error in dmesg
trough thoses 3 months i always stayed updated on my drivers and kernel even reinstalling my distro 2 times

on sep 4 i found something after a crash that i show the support team to notify the proton team if it was a problem with proton

it says in journal seconds before the crash
Sep 04 15:06:53 Kosmos steam[1543]: ERROR: ld.so: object 'libgamemodeauto.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
Sep 04 15:06:53 Kosmos steam[1543]: assert_20240904150652_3.dmp[40711]: Uploading dump (out-of-process)
Sep 04 15:06:53 Kosmos steam[1543]: /tmp/dumps/assert_20240904150652_3.dmp
Sep 04 15:06:53 Kosmos steam[1543]: Adding process 40701 for gameID 2054970
Sep 04 15:06:55 Kosmos steam[1543]: assert_20240904150652_3.dmp[40711]: Finished uploading minidump (out-of-process): success = yes
Sep 04 15:06:55 Kosmos steam[1543]: assert_20240904150652_3.dmp[40711]: response: Discarded=1
Sep 04 15:06:55 Kosmos steam[1543]: assert_20240904150652_3.dmp[40711]: file ''/tmp/dumps/assert_20240904150652_3.dmp'', upload yes: ''Discarded=1''
Sep 04 15:06:55 Kosmos steam[1543]: pid 40711 != 40701, skipping destruction (fork without exec?)

steam support ask me to get what i found here
and today right before a crash it said this
steam[1635]: Fossilize WARN: Pipeline library handle 0x00007e90ac114c40 is not registered.
Sep 12 20:35:21 Kosmos steam[1635]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).

so im comming here if anything can help make the game more stable for nvidia and to know if anybody can told me what the pid error means (pid 40711)

my setup is
CPU ;R7 5700x
GPU ;RTX 2060 6gb
Kernel ; 6.10.9-arch1-2
OS ; Arch linux
Proton experimental
launch Options ; VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 PROTON_ENABLE_NVAPI=1 gamemoderun %command% VKD3D_CONFIG=no_upload_hvv DXVK_ENABLE_NVAPI=1 DXVK_ASYNC=1 PROTON_NO_FSYNC=1 PROTON_LOG=1 %command% --dlss-nvapi=mock WINEDLLOVERRIDES="version,dxgi=n,b"

yes i know i have a lot of launch options not even shure most of them work with my setup but the game is smooth with them and i am open to change some things if you wanted me to test others lauch options

in hope to find way to not crash anymore without needing to change GPU

Best regards
TheCrabeuh720

Newest update disabled Raytracing again and the workaround from here don't work anymore either....

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2143465327

@Azyrion it works on my computer, i reapplied the workaround after update and ray-tracing is still activable, maybe you are using amd with amdvlk?

@andrew-ld no never installed/had amdvlk on my system, I am using mesa. What Proton Version are you using?

@andrew-ld no never installed/had amdvlk on my system, I am using mesa. What Proton Version are you using?

proton-ge 9.13 on mesa with latest commit

With proton Experimental stable and bledding i got this screen on videos

Operating System: Manjaro Linux rolling
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.9-x64v4-xanmod1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × Intel® Core™ i5-14500
Memory: 46.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 770

The game works very well but in some videos like the videos of magic spell examples, i get this screen, or splash init screen when the game run as firts time.

how can I solve this? Some ENV? or what thing?

@andrew-ld

sed -i 's/wine_/hack_/g' ~/.local/share/Steam/steamapps/common/Dragons\ Dogma\ 2/DD2.exe

Using this command makes the game crash on launch, same as manually replacing the string using hex. :(

I tried replacing the string on launch using a dll, but it seems to have some sort of anti tamper in place now.

@andrew-ld no never installed/had amdvlk on my system, I am using mesa. What Proton Version are you using?

proton-ge 9.13 on mesa with latest commit

Sorry somehow didn't answer this. Here is the log that comes out right after crash.
steam-2054970_1.log
Game only works after verifying files and replaces 2 broken files but raytracing is still not usable afterwards
EDIT:
Forgot that the log above is the attempt to see if it works with REFramework. Here the log without any mods
steam-2054970_2.log

Also currently on:
OS: Nobara 40
DE: Plasma 6.2.3 wayland
Kernel: 6.11.9-200.fsync.fc40.x86_64 (64-bit)
Mesa: 24.4.0-git.20241121
CPU: Ryzen 7 5800X3D
GPU: RX 6900 XT

Game randomly freezes/crashes , particularly when opening menus but also just at random. Most recent crash I attempted to switch to another tty to kill it and noticed this output.

Dec 22 08:56:39 xela-X870 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] ERROR Failed to initialize parser -125!
Dec 22 08:56:49 xela-X870 kernel: amdgpu 0000:03:00.0: [drm] ERROR [CRTC:79:crtc-0] flip_done timed out
Dec 22 08:56:59 xela-X870 kernel: amdgpu 0000:03:00.0: [drm] ERROR flip_done timed out
Dec 22 08:56:59 xela-X870 kernel: amdgpu 0000:03:00.0: [drm] ERROR [CRTC:79:crtc-0] commit wait timed out
Dec 22 08:57:09 xela-X870 kernel: amdgpu 0000:03:00.0: [drm] ERROR flip_done timed out
Dec 22 08:57:09 xela-X870 kernel: amdgpu 0000:03:00.0: [drm] ERROR [PLANE:58:plane-3] commit wait timed out
Dec 22 08:57:53 xela-X870 kernel: amdgpu 0000:03:00.0: [drm] ERROR [CRTC:79:crtc-0] flip_done timed out

System Report:
steam_system_report.txt

System Info:
steam_system_info.txt

I was gonna try to add a proton log here, but it decided not to crash this time.

@rednaxela600
try RADV_DEBUG=nocache %command% link
or MESA_DISK_CACHE_SINGLE_FILE=0 %command% link

@Billli11
The nocache line reduced the crashing drastically, several hours of play today with only one freeze/crash as opposed to dozens. Thank you very much!

So i was testing the game today, and it seems the performance is pretty damn worse when compared with windows performance, on one hand i've had terrible FPS on villages and city's (i know, i know, the FPS in this case is really horrible, even on windows but, when i was comparing the FPS was pretty damn low and with a lot of stutters on linux, 40-56 FPS with extreme FPS spikes and drops by just changing the camera angle, and on windows i've had almost smooth 60 FPS always without any drops or FPS spikes,) and on the overworld the game under linux runned about 10-20 FPS less when compared to windows.
I presume that we have two problems on this equation, GPU and CPU related, GPU not working correctly under linux with this specific game (drivers and maybe proton related) and CPU because the game is just CPU bound, and on linux the processes works differently so we just can't prioritize the game process just like on windows (giving it high priority on task manager, and yes, this helps a lot to the point someone made a mod to automatically do that on windows).

My specs if it helps:
OS: Arch Linux x86_64
Kernel: Linux 6.12.10-1-cachyos-bore
DE: GNOME 47.3
CPU: AMD Ryzen 7 5700X (16) @ 4.87 GHz
GPU: AMD Radeon RX 7800 XT [Discrete]
Memory: 5.62 GiB / 31.27 GiB (18%)
Swap: 37.75 MiB / 4.00 GiB (1%)
Proton version: Proton experimental (bleeding edge beta branch) and Proton 9.0-4

if you are using mesa below 23.2, try this RADV_PERFTEST='rt' as a launch command

Oh well, at least we tried

@rednaxela600 try RADV_DEBUG=nocache %command% link or MESA_DISK_CACHE_SINGLE_FILE=0 %command% link

So, I've been trying to capture more information about this. Just posted on mesa git as well.
In my case, if I run with this argument "VKD3D_DEBUG=err" or "VKD3D_SHADER_DEBUG=err", it prevents the page fault without the performance penalty of RADV_DEBUG=hang or stutter from cleaning the cache. Can someone test this to see if it applys to anyone else?

The full command I'm using in steam is "VKD3D_SHADER_DEBUG=err gamemoderun %command%" or "VKD3D_DEBUG=err gamemoderun %command%", both prevented the crash.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2512853255

his? Some ENV? or what thing

@Milor123 Have you tried proton-ge?
You can install it via protonplus.

Replying to [#7595 (comment)](https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2512853255)

his? Some ENV? or what thing

@Milor123 Have you tried proton-ge? You can install it via protonplus.

Hello brother, I'm sorry at the moment I can't tell you, I'm momentarily away from linux. but you can try somethings check my guide for linux and windows in https://www.nexusmods.com/dragonsdogma2/mods/1039/

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2625023358

I'm afraid I think you didn't read it right, the guide is for the debug version of DD2, if you have the debug version on your computer, then you can make use of the guide, otherwise not. However, Frame generation's advice could be applied to both versions.

Found another way to prevent the crashes, was looking for gfx page faults and found this closed issue https://gitlab.freedesktop.org/drm/amd/-/issues/2971, with mention gfx page faults when using amdgpu.mcbp enabled, wich I wasn't using, but decided to add to the kernel parameters and set it to disabled, tought it was worth the shot.

And again, adding this to the kernel parameters also prevents crashes, this time no parameters are added to the game besides gamescope and gamemoderun, 2 hours smooth gameplay.

Will remove the kernel parameters tomorrow to see if the problem comes back, then put it back on and see if its not a fluke, if someone want to take a shot too, starting to get curious about this.

To run the game without crashes you have to change Vulkan headers to
AMDVLK. That's the only thing you need.

RADV crashes, for whatever reason. There are games where it happens the
same thing. Valheim and MH Wilds Beta for example.

On Sun, 2 Feb 2025, 04:09 Rafael Mercado, @.***> wrote:

Found another way to prevent the crashes, was looking for gfx page faults
and found this closed issue
https://gitlab.freedesktop.org/drm/amd/-/issues/2971, with mention gfx
page faults when using amdgpu.mcbp enabled, wich I wasn't using, but
decided to add to the kernel parameters and set it to disabled, tought it
was worth the shot.

And again, adding this to the kernel parameters also prevents crashes,
this time no parameters are added to the game besides gamescope and
gamemoderun, 2 hours smooth gameplay.

Will remove the kernel parameters tomorrow to see if the problem comes
back, then put it back on and see if its not a fluke, if someone want to
take a shot too, starting to get curious about this.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2629220716,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFABCB67UJJYVXZ44HZRLXL2NWD5VAVCNFSM6AAAAABFD6R6SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRZGIZDANZRGY
.
You are receiving this because you commented.Message ID:
@.***>

Thank you for the info! Would you agree that most people will not go so far to find this info? And this make dificult for most people to use Linux and game on it? My intent is Just help understand why It crashs with Radv, cause it looks like no one is interested in solve the issue with Radv since using amdvlk prevent the crashs.

That said, have you tried the parameter? To me it appears to be an alternative to Prevent crashs, and allows me to have good results without amdvlk. Maybe It can help devs/players further understand whats wrong?

Or is justified for Radv to have bugs because amdvlk exists?

Not trying to be rude, Just dont understand the "You need amdvlk, that's all you need" part. Seems like this is avoiding the fact that Radv may have a bug, and without info or reports the bug probably will not be fixed.

I'll leave here just for helping purpose.

I'm on Arch stable branch and I have a 7900xtx and confirm that within 30 min / 1 hours the game crashes. No env variable / parameter helped. Everything I tried didn't move the needle into one direction or was worth trying. Various updates to Mesa / RADV didn't solve the issue. AMDVLK solved for it for me and never had a crash again.

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2629463229

In my experience, the first run post shader compilation runs perfect, after the First restart of the game the problems starts to show. Even after changing driver starting and playing after shaders runs smooth. But nice to know that bazzite runs well.

Ok, removed everything. Even the kernel parameter, played 4 hours straight no crashes... I'm lost now, will report back if the issue comes back. If anyone having the issue can test the parameters I said above, would be good to know if it does or does not help.

I'm getting those same gfxhub page fault crashes. Usually after a few hours of playtime

Replying to https://github.com/ValveSoftware/Proton/issues/7595#issuecomment-2764554244

Can you try again with proton-experimental (Bleeding-edge) there was a shader cache bug that was fixed after MHWilds launch.

If this does not work take a look at this kernel bug, that can also cause this:
https://gitlab.freedesktop.org/drm/amd/-/issues/3131 (you can use lact to avoid this one in the meantime)

There is a fix for the misrender on ARC B580 : https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41501

If someone else can confirm it fixes the issue for them, much appreciated!

There is a fix for the misrender on ARC B580 : https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/41501

If someone else can confirm it fixes the issue for them, much appreciated!

Tested my Arc B580 on CachyOS after installing drivers but the issue is still present. Not sure if that's related to how CachyOS delivers updates to mesa. Will see if anymore updates come through and test more later.

@JassiFrickaNation

Which mesa version is installed?

The Merge request is not merged to main branch yet and I don't think CathyOS mesa-git package include additional patches by default.

You most likely need to build it yourself.

@Billli11
Ran glxinfo | grep "Mesa" for the output.

client glx vendor string: Mesa Project and SGI
Device: Mesa Intel(R) Arc(tm) B580 Graphics (BMG G21) (0xe20b)
OpenGL renderer string: Mesa Intel(R) Arc(tm) B580 Graphics (BMG G21)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 26.1.0-arch2.1
OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.1.0-arch2.1
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 26.1.0-arch2.1

I figured it could be something like that. I'll work on figuring that out here and report my findings later. If there's a specific guide one could recommend for building Mesa on CachyOS, I'd appreciate it (I'm not that smart, but I can probably figure it out eventually).

After I thought I built and installed the fix, my Mesa version was the same after I ran glxinfo | grep "Mesa". I still tried running Dragon's Dogma 2 and the bad geometry issue seems to be resolved.

However, now I'm having a new issue. While in some of the game menus, I get a weird rapid input problem where the game is seemingly scrolling through submenus at a rapid pace. I can still scroll up and down and use the keyboard, mouse, and controller, though confirm and back inputs have difficulty registering. Sharing a Steam log of me trying to navigate the main menu and settings, in case it helps.

steam-2054970.zip

Tried to reinstall all packages through CachyOS as a sanity check. Now I can't reproduce the geometry issue. So, I don't even know what I did with my system today.

Edit: Swapped out the Arc B580 for an RX 6600 so I could go back to playing Dragon's Dogma 2 but the hyper scrolling issue is still there. So, it's agnostic to the graphics card installed. Sorry if this isn't helpful, but figured I should give an update.