Working fine for me on an AMD 7800XT, but I'm seeing some visual glitches I've already reported on the mesa gitlab
@simonlui Does it work with force_vk_vendor=-1 %command% ?
Was there a Proton Experimental update? I was playing last night just fine at around 80fps, but launching today I cannot break 25fps no matter what. Launched multiple times, lowered all graphics settings, nothing. Bit confused.
4090
555.58.02
Does it work with
force_vk_vendor=-1 %command%?
No, was one of the first things I tried since integrating XeSS in games and trying to run it on Linux can crash if you have an Intel GPU with XMX support.
At this point, given ProtonDB reports and what is being said here, I'm going to escalate the issue to the Mesa gitlab for Intel devs to take a look.
Today after a few atempts to improve performance I got denuvo warning.
[Black Myth:Wukong] Specific scene makes game fps extremely low for several seconds
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8024.
@kamikaze211 posted on 2024-08-25T17:00:29:
Specific scene makes game fps extremely low for several seconds, with frame time extremely long, and GPU usage very low.
Attract archers to shoot arrows, then move to the bridge.
You will see the GPU usage will be very low, and the fps will be shown as none, and the frame time will be extremely long.
And I had tried to change another kernel, another Proton version, and updated the system to the latest, and set to the lowest graphic settings in the game.
I also tested on Windows 10, but without this issue.
@simonlui I'm also using an Intel Arc A770, and I can successfully launch Black Myth: Wukong (both Proton experimental and Proton 9.0-2 work). However, there are different kinds of flashing artifacts in the water when using TSR, FSR, or XeSS.
https://github.com/user-attachments/assets/35198a00-2628-4a3a-928f-917fafd46b48
(the mouse display error seems to be a Steam recording issue, it's normal in game.)
@Sittymin What kernel and Mesa are you using? The artifacts I think is from a graphical issue with global illumination where setting it higher causes issues, at least from what I saw from the benchmark tool. Otherwise, nothing else stands out, I have both Proton versions and they don't work and crash with the same unknown software exception error in the logs I noted earlier.
@simonlui My Mesa is 24.1.5 and my kernel is 6.10.4. I don't think it's a Mesa or kernel issue, but I'm not sure what else to suspect because I was able to launch Black Myth: Wukong from the start.
EDIT: I found that forcing the Xe kernel module to load fixes artifacts; however, the game is very choppy, although the displayed FPS is not low. This might be a driver issue on Intel's side.
My versions aren't that far off from yours. I am not using the Xe kernel module but I don't think that has anything to do with why the game crashes or not. Not sure what is wrong. Also, I know you already know this but I did open a Mesa issue and it is here
In my logs, the part corresponding to 9582.886:012c:0130:warn:seh:dispatch_exception unknown exception (code=c06d007e) raised looks like this, I'm not sure if it's useful.
23896.543:0128:012c:trace:seh:RtlAddFunctionTable 0000000001D63CD4 1 1d63a14
23896.546:0128:012c:trace:loaddll:build_module Loaded L"Z:\\home\\Sittymin\\.local\\share\\Steam\\steamapps\\common\\BlackMythWukong\\Engine\\Binaries\\ThirdParty\\PhysX3\\Win64\\VS2015\\NvCloth_x64.dll" at 00006FFFF9AC0000: native
23896.548:0128:012c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msmpeg2vdec.dll" at 00006FFFF9AA0000: builtin
23896.549:0128:012c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\MSAudDecMFT.dll" at 00006FFFF9A00000: builtin
info: Intel(R) Arc(tm) A770 Graphics (DG2):
PS: I was just looking for differences in the logs
The dust can not be rendered correctly.
when enable RTX parameter on my system after restart cannot load saved games. system hang on boot.
my system
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] driver: amdgpu
v: kernel
Device-2: AVerMedia Live Streamer CAM 513
driver: hid-generic,usbhid,uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
gpu: amdgpu resolution: 1: 3440x1440~165Hz 2: N/A
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.3 renderer: AMD
Radeon RX 6900 XT (radeonsi navi21 LLVM 19.1.1 DRM 3.59
6.12.9-1-liquorix-amd64)
API: Vulkan v: 1.3.290 drivers: N/A surfaces: xcb,xlib
Black Myth Wukong no longer works
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8445.
@robertgosz posted on 2025-02-08T18:10:26:
System info
https://gist.github.com/robertgosz/ad53070cb41e3a606d58257b88209a71
Proton log
steam-2358720.zip
As I described here: https://github.com/ValveSoftware/Proton/issues/8444
The game crashes few seconds after being launched.
Just run Steam, go to library, click play. Crashes every time.
Hello @robertgosz, these look like some lines of interest from your Proton log:
err:vkd3d-proton:dxgi_vk_swap_chain_create_surface: Surface is not supported for presentation.
[...]
err: DXGI: CreateSwapChainForHwnd: Failed to create swap chain, hr -2147024809
https://github.com/HansKristian-Work/vkd3d-proton/issues/1618#issuecomment-1618039762 might be relevant.
https://gist.github.com/robertgosz/1bbb56acf7bbda1ebdd47efd40a69adc#file-gistfile1-txt-L2078-L2110 in you runtime diagnostics gives the rest of the picture. For some reason the game and VKD3D-Proton is trying to use your RTX 3090, but that video card can't render to the display in your current system configuration.
Ok, thank you @kisak-valve. Looks like it's not an issue with a system update as I was suspecting, but a hardware change. I have recently added additional GPU to my machine, but it's not used for gaming. Do you know if I can somehow convince Proton to use the main GPU with some kind of launch option or something, or I need to physically remove the second GPU ?
Maybe setting the game's launch options to DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4080" %command% to try to make the game only see the video card that can render to the display?
It works. @kisak-valve you're cooking. Thank you again and sorry for disturbances!
Log file: steam-2358720.log
System info
Game suddenly freezes during 2 attacks from Fuban (One attack when he shove his head onto the ground, a second attack right after the animation in the beginning of phase 2). The only way I found to get out of that situation is to kill the process.
Start a fight with Fuban, get in front of him, wait until he does an attack with his head or hit him hard enough to trigger the phase 2, and let him do the first attack after you grabbed the artefact.
Black Myth: Wukong FSR 4 bad Frame pacing.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9971.
@Texzor posted on 2026-07-13T21:01:08:
When using FSR4 reported Frame Rate is okay (20% lower than FSR3), but Game feels extremely sluggish compared to FSR3 with same Quality Settings.
Thanks for making Gaming on Linux possible :-)
proton experimentalx5 2026-07proton 9.0-2x1 2024-08DXVK_FILTER_DEVICE_NAME="NVIDIA GeForce RTX 4080" %command%x1 2025-02force_vk_vendor=-1 %command%x2 2024-08msauddecmft.dllx1 2024-08msmpeg2vdec.dllx1 2024-08nvcloth_x64.dllx1 2024-08
Compatibility Report
System Information
I confirm:
steam-2358720.log
Symptoms
The game doesn't launch on my system but it seems to do so anecdotally on other Linux systems I've seen. Admittedly, I am using Intel Arc which is unusual so it can be an issue here. The line in the log in question that the game seems to hit and exit on is this one, most likely.
9582.886:012c:0130:warn:seh:dispatch_exception unknown exception (code=c06d007e) raisedc06d007e is Unknown Software Exception in Windows, it seems, so doesn't seem to be helpful here in saying what is actually wrong here.
Reproduction
Open the game with a similar setup and see the game open up a window briefly before crashing and having the window disappear. Either using the compatibility mode or not versions of the game and other versions of Proton like Proton experimental and Proton 8 yields similar results.
If all other vendors work and Intel is the only GPU platform with issues with this game, I will escalate and create an issue inside Mesa Gitlab for the Intel kernel developers to take a look at.