Dragon's Dogma 2 (2054970)

[frozen-sea]

Compatibility Report

• Name of the game with compatibility issues: Dragon's Dogma 2
• Steam AppID of the game: 2054970

System Information

• GPU: RTX 4070 Ti
• Video driver version: Nvidia 550.67
• Kernel version: 6.8.1
• Link to full system information report as Gist: https://gist.github.com/frozen-sea/3e3b1b2eab46f5ecb15ad3ce7e2f7cfa https://gist.github.com/frozen-sea/cc2ca58035fcac0fb06d79b391f071f6
• Proton version: 9.0 (Beta), Experimental bleeding-edge

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

Not possible to enable ray tracing in the options menu. DLSS can be enabled. Tried with launch options: PROTON_LOG=1 PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr %command%

Log from starting to menu and quitting: steam-2054970.log

Also tried on Experimental bleeding-edge, which crashes immediately at the main menu if you run without PROTON_LOG and hangs on black screen at the same point when logging is enabled. Log after killing the process:
steam-2054970.zip

Reproduction

Start the game, check the graphics options

[tajeraich]

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

[pprobst]

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.

[rspavel]

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

I had that exact same issue. Between this thread and a few others I found the following consistently lets me get into the game:

1. Set compatibility to Proton 8.0-5
2. Set launch options to PROTON_ENABLE_NVAPI=1 VKD3D_CONFIG=dxr VKD3D_FEATURE_LEVEL=12_2 VKD3D_SHADER_MODEL=6_7 %command%

That gets me into the game and I played up until The Arisen heads to the capital. One of the NPCs that accompany you's model would glitch out and make the game unplayable until I restarted. And denuvo considers every restart (even if proton and flags don't change) to count as an activation.

Could probably narrow down the required options but with 5 or so attempts to play the game per day... I just don't care enough to do a deep dive debug. But hopefully this helps.

[tajeraich]

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.

[tajeraich]

So, switching to from fullscreen to borderless stopped the crash from causing my entire system to freeze up, but it still froze the game. With PROTON_LOG=1 %command%, I was able to get this from the log:

3375.565:0128:022c: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) 3385.592:0128:0180:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 3385.592:0128:0178:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 3385.592:0128:0180:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000743e0080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").

[tajeraich]

So, switching to from fullscreen to borderless stopped the crash from causing my entire system to freeze up, but it still froze the game. With PROTON_LOG=1 %command%, I was able to get this from the log:

3375.565:0128:022c: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) 3385.592:0128:0180:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 3385.592:0128:0178:err:vkd3d-proton:vkd3d_wait_for_gpu_timeline_semaphore: Failed to wait for Vulkan timeline semaphore, vr -4. 3385.592:0128:0180:warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000743e0080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").

Disregard. It went back to freezing the whole system on the next run.

[abc-mikey]

Replying to #7595 (comment)

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

[LuxLucian]

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

[voorhees3388]

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.

[Frank-MN]

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?

[dkoch84]

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.

[Frank-MN]

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

[Frank-MN]

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

[tajeraich]

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.

[Frank-MN]

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.

[LuxLucian]

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

[alosarjos]

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

[LuxLucian]

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.

[Frank-MN]

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.

[tajeraich]

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.

[Frank-MN]

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.

[tajeraich]

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.

[vparitskiy]

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

[Frank-MN]

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

[frozen-sea]

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.

[weeviltime]

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

[screwylightbulb]

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.

[Frank-MN]

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.

[simifor]

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.

[Frank-MN]

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

[Billli11]

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

[simifor]

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: @.***>

[abc-mikey]

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: [gfxhub] page fault

``` 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

steam hwinfo

``` 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 ```

[frozen-sea]

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%

[Frank-MN]

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.

[frozen-sea]

Replying to #7595 (comment)

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%

[tajeraich]

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.

[Frank-MN]

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/arch-announce@lists.archlinux.org/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

[LuxLucian]

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.

[bpc1]

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.

[RyuSeisuke1992]

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

[Frank-MN]

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: @.***>

[vparitskiy]

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

[Frank-MN]

Replying to #7595 (comment)

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.

[weeviltime]

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.

[Billli11]

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

[weeviltime]

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

[Frank-MN]

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.

[Billli11]

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.

[calabar]

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.