I am having this same issue on my Framework Laptop 16 with AMD Radeon 7700S, a card that supports Vulkan, DX12, etc and has been more than capable of running these games (including Overwatch) in the past.

I've tried using Protontricks to include DXVK manually and the 2017 and 2022 VC++ redists, but none have helped so far. I've tried on Proton 9.0, Proton Experimental, and GE-Proton9-20, all with the same result.

I was able to get in-game but halfway through a match, I got a GPU hang.

amdgpu 0000:09:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=9668550, emitted seq=9668552
amdgpu 0000:09:00.0: amdgpu: Process information: process GameThread pid 20633 thread vkd3d_queue pid 20733"
<GPU reset snip>
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

Proton Experimental Bleeding-Edge.
Radeon RX 5700XT on Mesa 24.3.1
Kernel 6.11, Arch Linux, KDE Wayland.

This is with the game's default settings it picks for a 5700XT on first startup. I'd briefly tested frame generation then turned it off.

I was also using Discord Canary's new streaming features at the same time, however the GPU hang report clearly points to the game causing the hang.

Hello @EnnuiL, try setting the game's launch options to force_vk_vendor=-1 %command% (from https://gitlab.freedesktop.org/mesa/mesa/-/issues/12280).

Note: This is a mesa/ANV specific driver workaround.

I tried it just now (and did try the WINE_HIDE_INTEL_GPU=1 environment variable while I was trying to make it run), but I still get the same "DirectX 12 is not supported on your system" error

I've resolved this issue by using Winetricks/Protontricks to install vcrun2022 and vkd3d. It might be prudent on either Valve or NetEase to set the proton configuration for this game to use those DLLs.

AMD GPU btw, has nothing to do with the Intel Arc this issue is about, but I figured I'd mention since I also couldn't boot the game with the same issue.

I've resolved this issue by using Winetricks/Protontricks to install vcrun2022 and vkd3d. It might be prudent on either Valve or NetEase to set the proton configuration for this game to use those DLLs.

AMD GPU btw, has nothing to do with the Intel Arc this issue is about, but I figured I'd mention since I also couldn't boot the game with the same issue.

I tried that now and well? Still didn't work, I have the same issue as before; I did also try Proton GE 9-20 as well as Proton 9.0-3 (other than Proton Experimental), and yeah, no dice

So I had a similar issue, and I fixed it by adding force_vk_vendor=-1 %command% to the launch options. Apparently, Marvel Rivals does not like intel GPUs, even if it's your iGPU and not the dGPU that actually runs the game. I sent a bug report to mesa and apparently it might be getting resolved.

Edit: Oh, my bad, kisak-valve already mentioned it, sorry.

for players with same error on an old gpu's such as radeon r9 290x\390 - game will run with VKD3D_FEATURE_LEVEL=12_0 %command% in the launch options, proton experimental. (just skip pop-up notices about outdated os and driver -> confirm-continue and launch).

Huh, I have dug further into this; I have finally found a ProtonDB entry from someone else having this issue (and with an Arc card) while on the vkd3d-proton repo, I found https://github.com/HansKristian-Work/vkd3d-proton/issues/2042 as well as mesa#11469, which points out that all Unreal Engine 5 titles are apparently broken on Intel Arc cards on Linux; That's not good!

Attention Intel Arc card users! (or Intel iGPUs, so really, anything that uses the ANV driver and is post-Xe)
I have found the fix to this: it turns out ANV didn't support a specific Vulkan extension that was needed in order to emulate Unreal Engine 5 on DX12; by compiling mesa#32525 and running Steam on its devenv, it works flawlessly!
There's only one issue: the Mesa workaround needs to be used if you use the compiled Mesa, but once the patch's actually merged? It won't be a problem anymore since the commit that links the workaround to Marvel Rivals is already on upstream

But yeah, the only thing left is to wait for the Mesa patch to be reviewed and merged (and hopefully released soon alongside the force_vk_vendor=-1 workaround)
As a sidenote, the videos are particularly laggy, but so far, it's not a big problem

Hello @EnnuiL, try setting the game's launch options to force_vk_vendor=-1 %command% (from https://gitlab.freedesktop.org/mesa/mesa/-/issues/12280).

Note: This is a mesa/ANV specific driver workaround.

Tried this but sadly didn't work. I'm on fedora 41 with an A750

Have no media in game, all cutscenes black on rx6700xt

Hello @EnnuiL, try setting the game's launch options to force_vk_vendor=-1 %command% (from https://gitlab.freedesktop.org/mesa/mesa/-/issues/12280).

Note: This is a mesa/ANV specific driver workaround.

how can i use that? like when i type "force_vk_vendor=-1 %command%" in launch option it says cannot be found

Tried multiple versions of proton, but I get this error and crash after "Press any button to start":

Sometimes, when alt-tabbing under Wayland, the game stops registering mouse clicks. Alt-tabbing out of the game and back into the game restores mouse click recognition. I am running Proton Experimental's bleeding_edge branch.

I have not tested it under the Xorg X11 server, although I had issues like this in other games in the past when I used it, so I assume it is a Wine bug.

Sometimes, when alt-tabbing under Wayland, the game stops registering mouse clicks. Alt-tabbing out of the game and back into the game restores mouse click recognition. I am running Proton Experimental's bleeding_edge branch.

I have not tested it under the Xorg X11 server, although I had issues like this in other games in the past when I used it, so I assume it is a Wine bug.

Are you on KDE Plasma? I have this problem with Warframe. It usually happens when I click over to another screen then back, usually I can fix it by opening up the steam overlay with shift tab, clicking on it, then closing steam overlay with shift tab again.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2533433893

Thanks for the report and digging a non trivial solution! Can you clarify for which graphic cards this fix will work? so maybe I don't get my hopes up before time.

I see a mention of 12.5 GFX in the merge requests you linked (but not on this one which seems to be the most probable merge to happen https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32676 ) and also I see you mention post-XE iGPUs, however in wikipedia I don't find any iGPUs after the 12 generation. I suspect you refer to raptor lake gpus which in theory seem are not XE and probably shouldn't be in the 12 gen section, and that both tiger lake and alder lake are not supported. Thanks!

EDIT: From the last comments on the merge I see they mention trying to keep Iris possible in the future with a change in the code (I think this equivalent to XE) that suggest that this currently isn't possible but might be in the future, feel free to correct me if I'm wrong below.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2533433893

I can confirm that compiling this MR and setting VK_ICD_FILENAMES accordingly fixes the game on my Intel Arc A750. Thanks for the investigative work!

I have a gtx 1650 ti and I am lost on why this doesn't work
I am on nixos but I am using flatpak version so IDK
here is the log file
steam-2767030.log
I tried everything from proton 9 to experimental to bleeding edge to ge and tkg so yeah help

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

I can confirm that compiling this MR and setting VK_ICD_FILENAMES accordingly fixes the game on my Intel Arc A750. Thanks for the investigative work!

archlinux bumped to 24.3.2 but i cant get it to work. still getting this error with all UE5 dx12 games.
can you check if it works and maybe provide a guide ?

But yeah, the only thing left is to wait for the Mesa patch to be reviewed and merged (and hopefully released soon alongside the force_vk_vendor=-1 workaround) As a sidenote, the videos are particularly laggy, but so far, it's not a big problem

Can confirm as an intel Arc user this fixes dx12 errors but for me, the game still crashes while compiling shaders. Everytime at 40/42 %

Hm, I feel like an elephant on the room that I notice is pretty recurring should be mentioned on this issue: MRivals is really unstable, and within 1 or 2 rounds (or even shortly after joining a match!), it will hard crash;

I have suspected it was the fault of https://github.com/ValveSoftware/steam-for-linux/issues/11446, but by renaming gameoverlayrenderer.so, the overlay is 100% disabled (confirmed by devenv Mesa's logs) and yet it crashes anyway; I then suspected that Fossilize was being confused by the launcher, so I disabled libVkLayer_steam_fossilize.so and as a result, the Fossilize logs have disappeared from Mesa's logs; Still, it still crashes?

I know it isn't an Intel Arc-only issue because well, I am using Mesa with the PR applied as well as force_vk_vendor=-1 being automatically applied by it (I've switched to the one mentioned here!), and yeah, ProtonDB complains about a mid-round crash a lot, with Nvidia and AMD GPUs being involved;

I'm willing to share relevant logs for this, I'll just need to know what would be useful

EDIT: oh god I forgot to mention actually useful information: the crashes that happen are more like a freeze followed by the UE crash reporter (I tried to grab logs from there, but I failed at that); Also this freeze-crash can be reproduced easily (and safely) by creating a custom game with the Spider-Islands map, fill it with hard bots (optional step?), and then play as many rounds as necessary; so far? It quickly freezes during the first minute or two;

A custom game is necessary because if you try this with online matches, the moderation system will consider that you have left in the middle of a round and will add a strike towards you; I did stop playing online due to that!

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2558519502

So, I suspect that once the PR is merged (it's still being reviewed), it would be part of Mesa 25.0.0, so it will take a while until it releases; I could maybe put up a guide in order to build the indev Mesa on Arch and use it on Steam, but I am worried about that, since indev Mesa is indev and can explode on different ways (and a commit did explode here! it got fixed though), plus having to always open Steam through a command in order to avoid the DX12 error prompt will be pretty annoying;

If it's fine anyway to post said guide, I'll put together one and post here

I have a gtx 1650 ti and I am lost on why this doesn't work I am on nixos but I am using flatpak version so IDK here is the log file steam-2767030.log I tried everything from proton 9 to experimental to bleeding edge to ge and tkg so yeah help

I still can't launch the game in the first place IDK if this is a direct x12 problem or what but can anyone look the logs and say if they are even right

Tried multiple versions of proton, but I get this error and crash after "Press any button to start":

did you find any solution to this? I'm facing the same problem.

no was never able

no was never able

try a different proton version, have similar issue with a game, tried 9.0.4 and was getting this error, went back to proton 8 and game was working.

it doesn't even launch for me in proton 8
I would really appreciate if some developer actually looked at the logs
and is there a better way to get support ??

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2560203329

What maps was this occurring on?

I am currently running an RTX 3060 Ti in my machine but on both this GPU and my previous RX 5700XT, the game had a chance of getting a random GPU hang if the GI settings were set to any of the Lumen variants. (SSGI doesn't seem affected)

In addition both Tokyo 2099 maps were pretty consistent triggers for this crash. (Happens inside the Lumen GI shaders from what myself and one other person troubleshooting was able to figure out)

If this is strictly an Intel hardware thing, there's also a chance ANV isn't agreeing with a shader Marvel Rivals is trying to render with. (Perhaps the same one in this case; GPU hangs reset significantly more reliably without really taking out the entire desktop on Intel Arc GPUs in my experience)

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2561249522

It can happen with any map if you play for long enough (I got a freeze at one of the Yggsgard maps for example), but yeah, in my own desperate testing? I have come to the conclusion that both Shin-Shibuya and Spider-Islands are crash-prone, with Spider-Islands in particular being able to cause a crash within the first minute pretty easily (flukes are possible though, and this means it is possible to play a round or two without crashes; it'll inevitably crash though)

I do find interesting that the apparent fix for you was switching out of Lumen, because my GI settings were already on SSGI (Low Quality), and yet the hang keeps happening; I did try the Custom Game + Spider-Islands test once more, and I could confirm that SSGI on High Quality was still affected

I guess a Proton log of the issue would be useful, so here's mine: steam-2767030.log (Proton Experimental, Lowest Settings, AMD FSR 3 enabled (?); Proton GE 9-21 is affected too though)

(oh also yes, the hang only affected the game itself; the desktop did struggle deeply during it, but you can still (barely) interact with it despite the massive lag)

EDIT: Useful information: being on the Defense team on Spider-Islands will consistently crash earlier than being on the Attack team; also I found out that going fullscreen and lowering the resolution to 1280x720 will reduce the crash frequency to the point you can squeeze 20-30 seconds of stable gameplay on the test before It Actually Happens

I can't get this game to run neither in nvk nor in propriatary nvidia drivers in my gtx 1650ti

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2561317265

I came to the thrilling conclusion that it's not a Linux issue, but rather one that affects Windows too! Yeah.. looking at some places, it appears that yeah, the crash is something that affects a random portion of everyone, it doesn't discriminate by any specific hardware (a friend of mine had a RX 7900 XTX (Linux) be affected by this issue), it's just the game having a serious issue itself;

I guess this is the part where I give up debugging this any further; Here's the rest of my findings:

• Any of the Lumen options results into an insta-freeze on 720p
• I tried force-enabling ReBAR on vkd3d-proton (a big thing of the Arc cards is ReBAR being mandatory after all!) by removing the 8 GB requirement, compiling it, and using it on Proton GE 9-21 (which is easier to modify), it appears to only exacerbate the issue and make the freeze happen earlier on the test compared to pure Proton Experimental (I'm not sure how this scales up with GPUs with more VRAM)
• There is a graphical glitch on this machine (Intel Arc A380, etc.) that manifests on 1080p (non-crashing map has been chosen for this) where a black rectangle will appear randomly appear near the character's icon (image); I might try reporting this to Mesa (or vkd3d-proton if not driver-specific?) later, but yeah.. honestly? My main concern right now is getting this game not to crash
• EDIT: Merging mesa#32305 into mesa#32676 will not fix this game! In fact, it will ensure that the ingame shader compilation crashes at 40% consistently (mesa#32676 alone is fine though)

• EDIT: Merging mesa#32305 into mesa#32676 will not fix this game! In fact, it will ensure that the ingame shader compilation crashes at 40% consistently (mesa#32676 alone is fine though)

As my game is crashing at 40%, I Tried the mesa#32676 but it still does crash. Error Mentioned Below

l\Binaries\Win64\Marvel-Win64-Shipping.exe: ../src/intel/compiler/brw_reg_type.h:164: brw_reg_type brw_type_larger_of(brw_reg_type, brw_reg_type): Assertion `(a & ~BRW_TYPE_SIZE_MASK) == (b & ~BRW_TYPE_SIZE_MASK)' failed.

Without it, just the DX12 Error

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2563238026

Oh, I see the problem: it turns out mesa#32305 isn't the issue, it's a Mesa bug at the point where mesa#32676 is based; rebasing into upstream Mesa's main branch (or just merging it) fixes the 40% crash and makes the game kinda playable, at least until The Dreaded Freeze happens;

After testing mesa#32305 + mesa#32676 + merge of upstream main, I can conclude that mesa#32305 is irrelevant here and that Stalker 2 fixes are not Marvel Rivals fixes despite both using UE5; The only useful PR here that I've seen is mesa#32676, which fixes the "DX12 not supported" prompt UE5 crash that happens on start (DX12 prompt is fixed by indev Mesa 24.3.2+ automatically applying force_vk_vendor=-1)

Welp! It turns out it is very likely that I have reached to a wrong conclusion; I have determined that the Spider-Islands (and friends) crash is one exclusive to Intel GPUs, or at least to the Intel Arc A380; From what I've seen, there are reports of crashes and general instability and they are quite bad, but this specific one with the reproduction steps detailed in https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2561317265? There is a fix:

By using DXVK_FILTER_DEVICE_NAME="AMD" as an env var and using the Ryzen 7900's iGPU, I have successfully played like, 10 rounds without a crash! The performance is quite bad though despite the extreme measures I've used (Gamescope on 600p, minimum settings, etc.), but it's good enough to be playable, and most importantly? It doesn't crash

If someone else has an Intel GPU and can run the patched Mesa, please let me know if a Custom Game with Spider-Islands selected ends crashing or not; I'm considering reporting this to Mesa itself if this is indeed a driver issue

@beh-10257 Did you ever get it to work? I am having the same issue with NVIDIA on NixOS

I have a gtx 1650 ti and I am lost on why this doesn't work I am on nixos but I am using flatpak version so IDK here is the log file steam-2767030.log I tried everything from proton 9 to experimental to bleeding edge to ge and tkg so yeah help

From looking at your log, try disabling/uninstalling MangoHUD, it's been acting funky for a lot of people lately.

I have a gtx 1650 ti and I am lost on why this doesn't work I am on nixos but I am using flatpak version so IDK here is the log file steam-2767030.log I tried everything from proton 9 to experimental to bleeding edge to ge and tkg so yeah help

From looking at your log, try disabling/uninstalling MangoHUD, it's been acting funky for a lot of people lately.

didn't help

@beh-10257 Did you ever get it to work? I am having the same issue with NVIDIA on NixOS

no nothing worked I'm hoping a nixpkgs update or an nvidia driver update fixes this tbh it sucked not being able to play with friends but whatever

Switching to GE-Proton8-20 worked for me

@beh-10257 I had the same issue as you. I also got this Unreal Engine crash after clicking Launch from inside the Launcher. Actually setting the launch option DXVK_FILTER_DEVICE_NAME="AMD" worked for me (thank you for the hint @EnnuiL ♥️). Using GE Proton 9.22 btw.

I'm currently on an Intel 10500K CPU and an AMD RX Vega 64 GPU. Although not being an expert, I believe Proton (or dxvk for that matter) had trouble selecting the correct GPU and tried to use the integrated GPU of my CPU instead of my dedicated one. I guess setting this launch option set Proton (or dxvk) up to use my dedicated GPU instead.

Summing up, I believe you need to find a way to tell Proton (or dxvk) to use your dedicated GPU, right?
So maybe, in your case, try using the launch option DXVK_FILTER_DEVICE_NAME="NVIDIA" (not sure, if "NVIDIA" is the correct string for filtering, but if it isn't, it should be something similar.)

You can find out your GPU device name by using vulkaninfo and running it using vulkaninfo | grep deviceName. This prints out all of your available GPUs.

Also found another reference on Reddit, where somelese also mentioned, that you need to explicitly specify the GPU for dxvk in some cases: https://www.reddit.com/r/linux_gaming/comments/v0nbot/warning_for_multi_gpu_users_you_have_to_specify/

I hope this provides you with a new starting point for troubleshooting or maybe even resolves your issue.

I haven't been having any notable issues with crashes - but I HAVE noticed that saving highlights does not seem to work. The progress bar goes through and the GPU is under load, but no file ends up being saved.
Ennui tried this as well and could reproduce this issue.
I've tried digging into this a bit - and to me it sounds like this issue is caused by Wine's Media Foundation implementation missing an AAC encoder:

I've tried installing mfAACEnc.dll from Windows 7 SP2, but that only made it freeze at 90%. If you try installing the entire Media Foundation alongside it using <workaround removed by moderator>, even the intro video doesn't play... seems like the only way to solve this would be implementing that AAC encoder in Wine.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2564607574

ohhh it worked so proton can't do that automatically
thanks a lot anyway thanks a lot

Sometimes, when alt-tabbing under Wayland, the game stops registering mouse clicks. Alt-tabbing out of the game and back into the game restores mouse click recognition. I am running Proton Experimental's bleeding_edge branch.
I have not tested it under the Xorg X11 server, although I had issues like this in other games in the past when I used it, so I assume it is a Wine bug.

Are you on KDE Plasma? I have this problem with Warframe. It usually happens when I click over to another screen then back, usually I can fix it by opening up the steam overlay with shift tab, clicking on it, then closing steam overlay with shift tab again.

Yes. Thanks for the tip. The next time I have it happen, I will try it.

When in the turret as Punisher (via E), after beginning to fire, the game will often keep playing the firing sound, even if you stop firing.

The game will often freeze during the intro movies when nvidia reflex is enabled.

NVRM: nvAssertFailedNoLog: Assertion failed: pEventNotificationList->pendingEventNotifyCount == 0 @ event_notification.c:289 spams dmesg. The dmesg spam is a race condition according to NVIDIA/open-gpu-kernel-modules#716. A fix is queued for Nvidia has a fix for the 570 driver.

Also, the game sometimes freezes. I suspect it is related to nvidia reflex.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2567187742

I was able to get a Proton Log when reproducing the video playback hang with Reflex turned on; the trigger seems to be having the very last frame of the video decoded and displayed, as it always hangs at the end of the video playing in question. (Tutorial videos for character abilities in the menus also make the game hang with Reflex turned on)

The hang seems to be caused by vkLatencySleepNV crashing inside winevulkan/the driver itself:

1140.829:0648:064c:warn:seh:handle_syscall_fault backtrace: --- Exception 0xc0000005 at 0x7f6bc54b4740: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libnvidia-glcore.so.565.77 + 0x2b4740.
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind function 7f6bc54b4740 base 0x7f6bc54b4736 cie 0x7f6bc6ed6aa8 len 14 id 0 version 1 aug 'zR' code_align 1 data_align -8 retaddr %rip
1140.830:0648:064c:warn:seh:dwarf_virtual_unwind backtrace: 0x7f6bc54b4740: /usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/libnvidia-glcore.so.565.77 + 0x2b4740.
1140.830:0648:064c:trace:unwind:execute_cfa_instructions 7f6bc54b4736: DW_CFA_def_cfa %rsp, 8
1140.830:0648:064c:trace:unwind:execute_cfa_instructions 7f6bc54b4736: DW_CFA_offset %rip, -8
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind fde 0x7f6bc70b5b70 len 10 personality (nil) lsda (nil) code 7f6bc54b4736-7f6bc54b4740
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind next function rip=0000000000000000
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind   rax=0000000000000000 rbx=00007f6bc72cc860 rcx=00007f6be1fa6ced rdx=0000000000000001
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind   rsi=00000000c020462a rdi=00000000000000f8 rbp=000055556fafb9c0 rsp=00000001000ffb38
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind    r8=0000000000000000  r9=00000001000feacc r10=1814294de8bf1120 r11=0000000000000246
1140.830:0648:064c:trace:unwind:dwarf_virtual_unwind   r12=0000000000000422 r13=0000555573305780 r14=000055556e1268d0 r15=00005555733057d0
1140.830:0648:064c:warn:seh:dump_syscall_fault backtrace: returning to user mode ip=00006fffeeecf94a ret=c0000005
1140.830:0648:064c:err:msvcrt:_wassert (L"!status && \"vkLatencySleepNV\"",L"../src-wine/dlls/winevulkan/loader_thunks.c",5772)

I also noticed the firing sound thing but the last time I played Punisher was a while ago and may have been while I was still using Reflex.
Take it with a grain of salt but if this guy's telling the truth on the Steam Forums, this is potentially a game bug and not easily fixable Proton-side.
https://steamcommunity.com/app/2767030/discussions/0/596260472619048276/?ctp=3#c596260472619081188

I was able to get a Proton Log when reproducing the video playback hang with Reflex turned on; the trigger seems to be having the very last frame of the video decoded and displayed, as it always hangs at the end of the video playing in question. (Tutorial videos for character abilities in the menus also make the game hang with Reflex turned on)

That is where it appeared to freeze for me too.

The hang seems to be caused by vkLatencySleepNV crashing inside winevulkan/the driver itself:

Awesome work!

I also noticed the firing sound thing but the last time I played Punisher was a while ago and may have been while I was still using Reflex.

I have had it happen both with and without reflex. I have also once seen it not happen without reflex.

Pressing "VIEW AND SHARE HIGHLIGHTS" and clicking confirm fails to save the recording. It will say: "Unable to Save: Unknown Error".

Pressing "VIEW AND SHARE HIGHLIGHTS" and clicking confirm fails to save the recording. It will say: "Unable to Save: Unknown Error".

https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2564620864
Someone tried to debug this a while ago and came to the conclusion that Wine's Media Foundation implementation is missing an AAC encoder.

I've opened an issue for that on Wine's bugzilla: https://bugs.winehq.org/show_bug.cgi?id=57614
Not sure if that's of any help, though.

I've opened an issue for that on Wine's bugzilla: https://bugs.winehq.org/show_bug.cgi?id=57614 Not sure if that's of any help, though.

From what Kisak said about a "workaround" posted earlier, there might be licensing issues with the codec itself preventing Wine/Proton from having an AAC implementation in Media Foundation.

Only other fix to wait for is if NetEase add a WebM option or similar, like Overwatch 2 used to have. (Overwatch 2's webM export broke in a game update)

For those facing freezes and subsequently a crash, I was able to avoid the issue by wrapping the game within Gamescope, and I'm running the game with the following command:

gamescope -w 2560 -h 1080 -r 144 -o 144 -ef --force-grab-cursor --expose-wayland -- %command%

Gamescope version is 3.16.1, along with GE-Proton9-22. The Wayland compositor I use, River, does not refresh when the game is unfocused, causing frames to not be rendered until the game is focused again. That is probably causing some kind of issue for the game, then causing freezes and then crashing. Gamescope is able to refresh while unfocused, and since I started using it, I have not observed a single freeze, much less a crash.

EDIT: I forgot to say I'm on a full AMD system: Ryzen 7 + RX 6600XT. People with Intel/NVIDIA cards (or even with full AMD systems) might be facing another kind of issue, which might be even coming from the game itself, so what worked for me might not work for you.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2571474301

Funny thing is: I did eventually wrap the game on Gamescope! That unfortunately didn't fix the freeze, but it did fix minor issues such as problems with non-QWERTY keyboard layouts (I'm a weirdo who uses Colemak-DH!)

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2571464601

No, the issue with that thing is that they literally shipped Windows' version of the entire Media Foundation on GitHub until the repository was deleted, and then install it. Why that's not a great idea should be obvious.
Wine already has an AAC decoder, and both a H264 encoder and decoder, backed by gstreamer or ffmpeg from what I can tell.
In theory, since it's been 27 years ago, at least the base version of AAC (which would probably be used here) should be patent free by now (while HE-AAC is 21 years ago). Similarly for the main and high profiles of H264 which were made about 20-21 years ago.

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

No, the issue with that thing is that they literally shipped Windows' version of the entire Media Foundation on GitHub until the repository was deleted, and then install it. Why that's not a great idea should be obvious. Wine already has an AAC decoder, and both a H264 encoder and decoder, backed by gstreamer or ffmpeg from what I can tell. In theory, since it's been 27 years ago, at least the base version of AAC (which would probably be used here) should be patent free by now (while HE-AAC is 21 years ago). Similarly for the main and high profiles of H264 which were made about 20-21 years ago.

Ah, possibly a wine media foundation bug then. Fun.

After the season 1 patch the game now seems to crash on launch for everyone on Linux.
I've seen several people with this issue, and none who has said it works for them.
I have however seen someone say it crashes on their PC but works on Steam Deck.

Edit: Adding SteamDeck=1 to the launch options fixes it. Perhaps the anticheat (which seemed to load right before the crash) needs to be aware of being used with Proton/Linux to not cause issues.

Tried this myself - I can confirm that it works on Steam Deck, and doesn't on PC if it doesn't think it'd be on Steam Deck.
Something I've noticed is that they disabled the launcher dialog on Steam Deck and didn't with Proton on PC - this might actually not even be malice and more an unlucky bug?
Looking at the crash log, I see this:

And the patch notes:

Support Intel® XeSS 2: With Intel® Xe Super Sampling 2 (XeSS 2), experience faster, smoother gameplay with higher image quality and a more connected playing experience with Intel® Xe Frame Generation (XeFG), Intel® Xe Low Latency (XeLL).

Does sound a lot like XeSS is just shit and acting up again. Just on AMD as well this time (I have an 7800XT myself)

Edit: Oh and, side note, I said before I didn't run into any notable crash issues yet - I did since before the patch, first it was page faults in the kernel module in some cleanup task (instantly freezing the game and causing a permanent VRAM leak, but still being able to kill the game and restart in time to rejoin, and reboot afterwards), and since that page fault was fixed in 6.12.7 with https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a93b1020eb9386d7da11608477121b10079c076a that appears to have turned into GPU timeouts whose recovery crashes the entire DE including steam, and apparently makes the game unable to start again until rebooting, despite vulkaninfo looking normal.

After the season 1 patch the game now seems to crash on launch for everyone on Linux. I've seen several people with this issue, and none who has said it works for them. I have however seen someone say it crashes on their PC but works on Steam Deck.

Edit: Adding SteamDeck=1 to the launch options fixes it. Perhaps the anticheat (which seemed to load right before the crash) needs to be aware of being used with Proton/Linux to not cause issues.

I actually suspect the updated XeSS DLL more than NetEase Game Security acting up but I could be wrong.

After the season 1 patch the game now seems to crash on launch for everyone on Linux. I've seen several people with this issue, and none who has said it works for them. I have however seen someone say it crashes on their PC but works on Steam Deck.

Edit: Adding SteamDeck=1 to the launch options fixes it. Perhaps the anticheat (which seemed to load right before the crash) needs to be aware of being used with Proton/Linux to not cause issues.

To be clear, it's adding the environment variable SteamDeck=1, so the command would be something like

SteamDeck=1 gamemoderun %command%

(if you are using gamemode ofc)

To my own submission. I did not find this thread when I searched, but adding SteamDeck=1 did not fix my game :(
Also managed to get the pop up I mentioned prior

EDIT: SteamDeck=1 does work when you dont miss the %command% part... Thanks!!!

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2583319045

System Information:

==========================================
uname -r
6.12.8-zen1-1-zen
==========================================
lscpu
Vendor ID:                GenuineIntel
  Model name:             Intel(R) Core(TM) i7-8809G CPU @ 3.10GHz
==========================================
glxinfo | grep "Device"
    Device: AMD Radeon RX Vega M GH Graphics (radeonsi, vegam, LLVM 18.1.8, DRM 3.59, 6.12.8-zen1-1-zen) (0x694c)
==========================================
Steam Beta Branch:  Stable Client
Steam Version:  1733265492
Steam Client Build Date:  Mon, Dec 2 16:26 UTC -08:00
Steam Web Build Date:  Mon, Dec 2 16:20 UTC -08:00
Steam API Version:  SteamClient021
==========================================
Marvel Rivals Build ID: 16961146
==========================================

With Force Proton and Glorious Eggroll: GE-Proton9-12

And Launch Options: SteamDeck=1 %command%

Can confirm it works. I was able to play a full round as Invisible Woman. Before adding the SteamDeck=1 launch option it crashed after the update no matter which proton I tried or which of the other launch options provided above.

Still getting unreal crashes when closing the game and sometimes when going to back to the main menu after a round. If I continue to search for a new match, no crash.

Thanks for the reports everyone. The issue with Reflex is being tracked in NVIDIA bug 5048395. I will report back here when a driver has been shipped with a fix.

I cannot open Steam Overlay - I have it enabled both in global and Marvel Rivals settings, yet it doesn't open. This behaviour was in S0 as well.

the overlay opens fine on my end, do you have this issue with other games as well?
Change the game's launch parameters to PROTON_LOG=1 %command% and you'll get a file in your home folder called steam-2767030.log, it might tell us if anything is going wrong.

I cannot open Steam Overlay - I have it enabled both in global and Marvel Rivals settings, yet it doesn't open. This behaviour was in S0 as well.

I was having the same issue but removing gamemoderun fixed it for me.

I am having issues in Marvel Rivals right after opening the game, it crashes at 65-66% of shader compilation. I have reinstalled, verified files, and cleared the shader cache, but if I verify files after opening the game it always says that a file needs to be reinstalled so it downloads a 48kb file. (I have tried looking for the file but I cant tell which one is being reinstalled)

CPU: AMD Ryzen 7 7700X
GPU: AMD RX 7800 XT
Kernel: 6.12.8-200.fc41.x86_64
Mesa Version: Mesa 24.3.2
Distro: Fedora 41; KDE

This issue happens on every Proton Version I've tried. Proton-GE 9-22. Proton 9.0-4, and Proton Experimental (non bleeding edge version).

The log below is from Proton Experimental, Bleeding Edge.
steam-2767030.log

If i missed anything, please let me know. Thanks!

Hi @kisak-valve, Thanks for the lead, I was able to get it opening under Mesa 24.2.8. I will file a bug report with Mesa for future versions shortly. Thanks!

After the season 1 patch the game now seems to crash on launch for everyone on Linux. I've seen several people with this issue, and none who has said it works for them. I have however seen someone say it crashes on their PC but works on Steam Deck.

Edit: Adding SteamDeck=1 to the launch options fixes it. Perhaps the anticheat (which seemed to load right before the crash) needs to be aware of being used with Proton/Linux to not cause issues.

This is a workaround, but doesn't work well with Multiple monitor setup. I had to play around with the config to get the correct monitor with the correct resolution, in full screen instead of some partial mode. (Because certain config items are locked when you add SteamDeck=1) Furthermore, after playing with the config, I had to take away write permissions so the game wouldn't alter it.

Not sure if this is the best place to post, SteamDeck=1 enabled me to launch the game but I would get crashes every game or every second game. Either loading into a match or a couple mins into the match.

This was on GE-Proton9-22, GE-Proton9-21 and Proton Experimental.

Audio would play fine but screen locked. Have to open terminal and kill the process, relaunch and hopefully reconnect in time before getting a penalty.

Swapping back to GE-Proton9-15 works perfectly, just played 8 games in a row no crashes.

Happy to test and post any output/debug/logs etc. just let me know what to do.

Currently, proton bleeding edge is needed outside deck. If you change your
launch parameter to "PROTON_LOG=1 %command%" (without the quotes) you'll
get a file in your home folder called steam-2767030.log, if you get the
game to crash, upload the log

On Sat, Jan 11, 2025, 9:56 PM weznagwama @.***> wrote:

Not sure if this is the best place to post, SteamDeck=1 enabled me to
launch the game but I would get crashes every game or every second game.
Either loading into a match or a couple mins into the match.

This was on GE-Proton9-22, GE-Proton9-21 and Proton Experimental.

Audio would play fine but screen locked. Have to open terminal and kill
the process, relaunch and hopefully reconnect in time before getting a
penalty.

Swapping back to GE-Proton9-15 works perfectly, just played 8 games in a
row no crashes.

Happy to test and post any output/debug/logs etc. just let me know what to
do.

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

Whenever I start the though steam this pops up before the launcher:

arguments: SteamDeck=1 gamemoderun mangohud %command%
I have tried with Proton Experimental, Hotxfix and GE9-22

OS: NixOS 25.05
Kernel: 6.12.8-cachyos
GPU: RTX 3070 Ti
GPU Driver: 550.142

Latest Marvel Rivals patch completely broke it

Issue transferred from #8384. @K1D77A posted on 2025-01-10T19:12:32:

Computer Information:
Manufacturer: ASUSTeK COMPUTER INC.
Model: ProArt B550-CREATOR
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: 5084 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
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported
Operating System Version:
"Gentoo Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.12.6-gentoo-x86_64
X Server Vendor: The X.Org Foundation
X Server Release: 12401004
X Window Manager: KWin
Steam Runtime Version: steam-runtime_0.20241024.105847
Client Information:
Version: 1733265492
Browser GPU Acceleration Status: Enabled
Browser Canvas: Enabled
Browser Canvas out-of-process rasterization: Enabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Enabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Enabled
Browser Rasterization: Enabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Enabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Enabled
Browser WebGL2: Enabled
Browser WebGPU: Disabled
Browser WebNN: Disabled
Video Card:
Driver: NVIDIA Corporation NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 565.77
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 143 Hz
VendorID: 0x10de
DeviceID: 0x2203
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: 23.46" x 13.19" (26.89" diag), 59.6cm x 33.5cm (68.3cm diag)
Primary VRAM: 24564 MB
Sound card:
Audio device: Nvidia GPU 9a HDMI/DP
Memory:
RAM: 128719 Mb
VR Hardware:
VR Headset: None detected
Miscellaneous:
UI Language: English
LANG: en_US.utf8
Total Hard Disk Space Available: 636166 MB
Largest Free Hard Disk Block: 135891 MB
Storage:
Number of SSDs: 5
SSD sizes: 4000G,0B,0B,0B,0B
Number of HDDs: 0
Number of removable drives: 0

[Internationalization]
Culture=en

[ScalabilityGroups]
sg.ReflectionQuality=1
sg.ViewDistanceQuality=1
sg.ShadowQuality=0
sg.PostProcessQuality=0
sg.TextureQuality=0
sg.EffectsQuality=0
sg.FoliageQuality=0
sg.ShadingQuality=0
sg.GlobalIlluminationQuality=1

[/Script/Engine.GameUserSettings]
bUseDesiredScreenHeight=False

[/Script/Marvel.MarvelGameUserSettings]
AntiAliasingSuperSamplingMode=4
SuperSamplingQuality=6
CASSharpness=0.800000
ScreenPercentage=100.000000
VoiceLanguage=
bNvidiaReflex=False
bXeLowLatency=False
bDlssFrameGeneration=False
bFSRFrameGeneration=False
bXeFrameGeneration=False
MonitorIndex=0
bEnableConsole120Fps=False
bUseVSync=False
bUseDynamicResolution=True
ResolutionSizeX=3840
ResolutionSizeY=2160
LastUserConfirmedResolutionSizeX=3840
LastUserConfirmedResolutionSizeY=2160
WindowPosX=0
WindowPosY=0
FullscreenMode=1
LastConfirmedFullscreenMode=1
PreferredFullscreenMode=1
Version=22
AudioQualityLevel=0
LastConfirmedAudioQualityLevel=0
FrameRateLimit=141.000000
DesiredScreenWidth=1280
DesiredScreenHeight=720
LastUserConfirmedDesiredScreenWidth=1280
LastUserConfirmedDesiredScreenHeight=720
LastRecommendedScreenWidth=-1.000000
LastRecommendedScreenHeight=-1.000000
LastCPUBenchmarkResult=-1.000000
LastGPUBenchmarkResult=-1.000000
LastGPUBenchmarkMultiplier=1.000000
bUseHDRDisplayOutput=False
HDRDisplayOutputNits=1000

[/Script/Engine.InputSettings]
bEnableMouseSmoothing=False
bViewAccelerationEnabled=False

My launch options are __GL_SHADER_DISK_CACHE_SIZE=10737418240 %command%, although that was just out of caution rather than to fix an actual issue. I probably can delete it with no ill effect.

If I enable reflex, I get crashes, but that is a known issue as per NVIDIA bug 5048395:

https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2584988319

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2586194299

Try Nvidia driver 565.77 and proton experimental's bleeding_edge branch to match what I use. It works fine for me on my RTX 3090 Ti and those are the biggest differences between what I use and what you use. Well, those two and the differences in commandline arguments. I don't use SteamDeck=1, mangohud or gamemode.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2586204323

I have a 3060 Ti but otherwise use the same configuration (565.77 driver, Experimental Bleeding-Edge)
Also note that use of SteamDeck=1 even if only launched once using it permanently enables silent launching of the game until game files are verified in Steam, so if you were confused as to why the launcher stops popping up after using this, that's why.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2586289067

Has anyone figured out what this actually changes to make the launcher silent? I made a copy of my compatdata directory before changing this and upon doing a diff, I cannot find anything obvious that was changed to cause this, yet I can confirm the persistance. I have not tried changing back to the old prefix to see if this is a server side thing.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2586403391

Given Steam redownloads a 48 byte file if you remove SteamDeck=1 then verify game files, it's a file removed from the actual game dir, not the Proton Prefix.

The Network Diagnostics appear to be broken. If I run them, it reports a 5000ms ping time and 100% packet loss, despite there being no issues when connecting to the servers. I just ran it out of curiosity and discovered this.

Am I the only one for which Proton doesn't seem to properly play video content ? It's just dark backgrounds etc..

RX 6950XT + Mesa 24.3.3

Are you using a current Proton version? and not some old custom build or something
This is working fine for me on Proton-GE 9-22, and was on current Proton Experimental as well
I did run into this while experimenting with media foundation workarounds (due to missing an AAC encoder) but on a standard prefix with a current Proton version it should just work

I just deleted the prefix and restarted, on proton experimental bleeding edge, still with dark backgrounds. It does indeed work with Proton-GE-9-22 but it's crashing now for me.

Distro: Fedora 41
DE: KDE Plasma
Proton: Proton Experimental

Game will cause amdgpu to timeout and soft recover a few times then finally crash.

[94262.404710] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94262.407259] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94262.407377] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94273.156573] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94273.158883] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94273.159087] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94283.396449] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94283.399071] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94283.399165] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94293.636323] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94293.639093] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94293.639216] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94386.819211] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94386.821984] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94386.822098] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94397.571072] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94397.573615] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94397.573821] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94407.810952] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94407.813735] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94407.813867] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94440.578564] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94440.580967] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94440.581549] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94451.330447] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94451.332859] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94451.333024] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94591.104743] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94591.107401] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94591.107572] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[94601.856617] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State
[94601.859202] amdgpu 0000:2f:00.0: amdgpu: Dumping IP State Completed
[94601.869217] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=43743320, emitted seq=43743322
[94601.869221] amdgpu 0000:2f:00.0: amdgpu: Process information: process GameThread pid 52246 thread vkd3d_queue pid 52347
[94603.869284] amdgpu 0000:2f:00.0: amdgpu: MES failed to respond to msg=RESET
[94603.869289] [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
[94603.869555] amdgpu 0000:2f:00.0: amdgpu: GPU reset begin!
[94606.248996] amdgpu 0000:2f:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
[94606.249002] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[94606.493512] [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
[94606.528820] amdgpu 0000:2f:00.0: amdgpu: MODE1 reset
[94606.528825] amdgpu 0000:2f:00.0: amdgpu: GPU mode1 reset
[94606.528892] amdgpu 0000:2f:00.0: amdgpu: GPU smu mode1 reset
[94607.032657] amdgpu 0000:2f:00.0: amdgpu: GPU reset succeeded, trying to resume
[94607.032794] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
[94607.032843] [drm] VRAM is lost due to GPU reset!
[94607.032844] amdgpu 0000:2f:00.0: amdgpu: PSP is resuming...
[94607.103569] amdgpu 0000:2f:00.0: amdgpu: reserve 0x1300000 from 0x85fc000000 for PSP TMR
[94607.250771] amdgpu 0000:2f:00.0: amdgpu: RAP: optional rap ta ucode is not available
[94607.250775] amdgpu 0000:2f:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[94607.250779] amdgpu 0000:2f:00.0: amdgpu: SMU is resuming...
[94607.250784] amdgpu 0000:2f:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e8000 (78.128.0)
[94607.250788] amdgpu 0000:2f:00.0: amdgpu: SMU driver if version not matched
[94607.430355] amdgpu 0000:2f:00.0: amdgpu: SMU is resumed successfully!
[94607.440247] [drm] DMUB hardware initialized: version=0x07002A00
[94607.663510] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[94607.663515] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[94607.663517] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[94607.663518] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
[94607.663520] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
[94607.663521] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
[94607.663523] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
[94607.663524] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
[94607.663529] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
[94607.663531] amdgpu 0000:2f:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[94607.663532] amdgpu 0000:2f:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[94607.663534] amdgpu 0000:2f:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
[94607.663535] amdgpu 0000:2f:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
[94607.663537] amdgpu 0000:2f:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
[94607.663538] amdgpu 0000:2f:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
[94607.666662] amdgpu 0000:2f:00.0: amdgpu: GPU reset(12) succeeded!
[94607.672681] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

The Network Diagnostics appear to be broken. If I run them, it reports a 5000ms ping time and 100% packet loss, despite there being no issues when connecting to the servers. I just ran it out of curiosity and discovered this.

Are you using a VPN?

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2596791119

Someone using crossover had that issue on MacOS:

https://www.youtube.com/watch?v=336wxfGPEnA

It is likely related to a missing video codec, although I cannot confirm that. I do not have this issue on Gentoo with nvidia hardware.

The Network Diagnostics appear to be broken. If I run them, it reports a 5000ms ping time and 100% packet loss, despite there being no issues when connecting to the servers. I just ran it out of curiosity and discovered this.

Are you using a VPN?

No.

reply to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2603424354

I'm experiencing the same issue. The game will crash, taking the AMD driver with it, it will try to recover and during said time, audio works and I can even talk through discord, with it in the end resulting in complete system hang, which requires a system reset / restart.

These would be my specs:

• OS: Nixos Unstable
• Kernel: mainline 6.13
• Mesa: 24.3.4
• CPU: 7800X3D
• GPU: Sapphire 7900XTX pulse
• Proton: GE-Proton 22 / 23

Here is the latest log file of the latest crash I had.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2617234076

Same thing happens to me. Game freezes and I have to restart my PC each time. To reduce the chances of this happening I restart my game every few rounds.

@neon-grim thank you for the information, but note that ge-proton is a third party project, you need to try with proton experimental. It would also be helpful to know your graphic settings, how long it takes to happen in your experience, and if it happens after playing certain maps or with certain characters in the match (that you've noticed).

For everyone else affected, also provide the same information, I haven't had much luck reproducing the issue.

reply to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2623134758

I just tested with the latest proton experimental and the same issue can be observed. What triggers this issue seems to be random, or at least I cant tell what it could be. It mainly happens after a few matches, or more specifically after the game has been running for a while.

reply to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2618109531

The crashes are happening across windows as well, a friend of mine with a 3070 also experiences crashes often. The driver crashing seems to be linux specific. Do you have an AMD or Nvidia GPU?

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2617234076

I experienced two crashes very similar in nature. Similar specs:

• OS: openSUSE Tumbleweed
• Kernel: 6.13.0
• Mesa: 24.3.4
• CPU: 7950X3D (game is pinned to the 3D cache CCD)
• GPU: 7800 XT
• Proton: crashed with GE-Proton 23 and Proton Experimental so far, now trying bleeding_edge

When this happens the game freezes briefly, then crashes to desktop, usually with all connected displays going black in-between due to the GPU driver crashing. It seems to take some running applications with it, especially Chromium-based ones. Yesterday when the crash occurred, Chromium-based TeamSpeak 6 beta crashed as well, while Firefox and several other applications were just fine.

But KDE (6.2.5) seems to be in a weird state after a GPU crash and doesn't fully recover, and while Steam itself works fine, the game doesn't want to start again until a full system reboot. What DE are you using?

Spent 5 hours trying to get the game to hang or crash with no luck, split into two sessions of 4 and 1 hour. Half of the 4 hour session was ran with fsr and fg off and low graphics preset, then the high graphics preset. Then I reopened the game and changed fsr to quality for an hour.

I'm already on KDE plasma 6.2.5 and mesa 24.3.4, and I'm on Linux 6.12.10. Checking protondb I found a report saying they their game would crash every 4 matches or so and I played more than that. While most reports are on rdna3 and I'm on rdna2, there's at least one reporter using rdna2.

At this point I imagine the graphics settings is an important factor for the issue happening or I'm being really unlucky

The 570.86.16 nvidia driver has a regression that causes a black screen in games when VRR is enabled. Marvel Rivals is affected. I just reported it at NVIDIA/open-gpu-kernel-modules#773. If you are on 570.86.16, either disable adaptive sync in your desktop environment's settings or downgrade to 565.77.

I'm getting these crashes consistently. I'm using Proton Experimental, KDE Plasma 6.2.5 (Wayland), Kernel 6.12.10-200.fc41.x86_64 (64-bit), Mesa 24.3.3. Hardware is i7-8086K CPU, 32GB RAM, AMD Radeon RX 7900 XTX.

If I run with the lowest graphics settings possible and FPS cap to 60, I can get five or so hours of gameplay without a hard system crash. If I set everything to max, it runs smoothly, but it will usually crash in under an hour. I've only ever seen it crash when combat was actively occurring on-screen. I've never seen it crash during the menus, the prematch waiting period in the 'safe room' area, or when just traversing the map. (But seeing as the game is mostly combat, that might just be coincidence.)

Usually the journal log for the crash period is just this, followed by my reboot:

Feb 04 05:48:08 groggle kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Feb 04 05:48:08 groggle kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Feb 04 05:48:08 groggle kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=41358099, emitted seq=41358101
Feb 04 05:48:08 groggle kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process GameThread pid 35404 thread vkd3d_queue pid 35526
Feb 04 05:48:10 groggle kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
Feb 04 05:48:10 groggle kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Feb 04 05:48:10 groggle kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!

Sometimes I can get to a TTY and login to safely reboot, and sometimes I have to hard reboot with the power switch.

I do have one journal log from 25th January that generated a lot more detail for some reason, but it's big, and I'm not sure if it would be helpful, or where to upload it.

If there are any further details I can collect that might help, please let me know and I'll try my best.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2631898369

This looks very similar to the error messages I'm getting when the game freezes:

Radeon 7800 XT:

Jan 26 01:35:56 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:56 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:56 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:56 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:56 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:57 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:57 bird-pc kwin_wayland[2401]: kwin_scene_opengl: 0x3: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Jan 26 01:35:57 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Jan 26 01:35:57 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Jan 26 01:35:57 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=53785564, emitted seq=53785566
Jan 26 01:35:57 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process GameThread pid 76773 thread vkd3d_queue pid 76967
Jan 26 01:35:57 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Jan 26 01:35:59 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
Jan 26 01:35:59 bird-pc kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Jan 26 01:35:59 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset failure
Jan 26 01:35:59 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
Jan 26 01:36:01 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Jan 26 01:36:01 bird-pc kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Jan 26 01:36:02 bird-pc kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Jan 26 01:36:02 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Jan 26 01:36:02 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Jan 26 01:36:02 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
Jan 26 01:36:02 bird-pc kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
Jan 26 01:36:02 bird-pc kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Jan 26 01:36:02 bird-pc kernel: [drm] VRAM is lost due to GPU reset!

More elaborate log here: amdgpu_hang_log.txt

I did test the game with an Intel Arc A750 and eventually the same kind of crash happened, logs:

Intel Arc A750:

Feb 03 21:17:29 bird-pc kwin_wayland[2376]: kwin_scene_opengl: 0x4: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 03 21:17:29 bird-pc kwin_wayland[2376]: kwin_scene_opengl: 0x4: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 03 21:17:29 bird-pc kwin_wayland[2376]: kwin_scene_opengl: 0x4: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 03 21:17:29 bird-pc kwin_wayland[2376]: kwin_scene_opengl: 0x4: GL_INVALID_OPERATION in glDrawBuffers(unsupported buffer GL_BACK_LEFT)
Feb 03 21:17:31 bird-pc plasmashell[2783]: error creating screencast "Could not find window id {7d2a22a5-4dfb-4d94-964d-fa1ff77d316f}"
Feb 03 21:17:33 bird-pc kernel: Fence expiration time out i915-0000:03:00.0:GameThread[8296]:13d963c!
Feb 03 21:17:37 bird-pc kwin_wayland[2376]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Feb 03 21:17:42 bird-pc kwin_wayland[2376]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Feb 03 21:17:47 bird-pc systemd-logind[1749]: Power key pressed short.
Feb 03 21:17:47 bird-pc kwin_wayland[2376]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug
Feb 03 21:17:48 bird-pc steam[4096]: src/clientdll/steamengine.cpp (2784) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
Feb 03 21:17:48 bird-pc steam[4096]: src/clientdll/steamengine.cpp (2784) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled
Feb 03 21:17:48 bird-pc steam[4096]: assert_20250203211748_143.dmp[34318]: Uploading dump (out-of-process)
Feb 03 21:17:48 bird-pc steam[4096]: /tmp/dumps/assert_20250203211748_143.dmp
Feb 03 21:17:48 bird-pc assert_20250203211748_143.dmp[34318]: Uploading dump (out-of-process)
                                                              /tmp/dumps/assert_20250203211748_143.dmp
Feb 03 21:17:52 bird-pc kwin_wayland[2376]: kwin_wayland_drm: Pageflip timed out! This is a kernel bug

(unfortunately that's the end of the log)

I just swapped out the GPU, rest of the system is the same as stated in my previous comment. I had to use Mesa from https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/32676 to be able to start the game without getting a DirectX error.

I assume the kwin_wayland errors happen because the GPU crashed and not the other way around (?).

But KDE (6.2.5) seems to be in a weird state after a GPU crash and doesn't fully recover, and while Steam itself works fine, the game doesn't want to start again until a full system reboot. What DE are you using?

I'm on KDE+Wayland too and is the exact same experience for me. My system is AMD Ryzen 7700X + Radeon RX 7600 on EndeavourOS and always up to date, using Proton Experimental by default. The crashes got really intense now, happen more often and a reboot takes much longer time now (there is a 3 min timeout when system goes down), with multiple penalties from the game.

I see lot of people use KDE here, but I guess this is just because its more popular, not because of an issue with KDE. Or is it? (VSauce music plays)

But KDE (6.2.5) seems to be in a weird state after a GPU crash and doesn't fully recover, and while Steam itself works fine, the game doesn't want to start again until a full system reboot. What DE are you using?

I'm on KDE+Wayland too and is the exact same experience for me. My system is AMD Ryzen 7700X + Radeon RX 7600 on EndeavourOS and always up to date, using Proton Experimental by default. The crashes got really intense now, happen more often and a reboot takes much longer time now (there is a 3 min timeout when system goes down), with multiple penalties from the game.

also kde, kubuntu 24.10, ive got ryzen 5 7600 and rx 6600

when it crashes itll sometimes partially recover and then hard crash after

pillowing my computer (holding power button) will put it in kernel recovery something something initramfs so i just reboot it again but usually my team have surrendered by the time i open steam again

in my opinion it's very likely a tesselation or compute shader issue with a race condition on one of the atomic variables, or a power draw issue as someone else said i dont remember where

the way i found to reduce it is setting everything to lowest possible settings, and restarting the game between games, the more maps/projectiles your game processes, the higher the chance you have of the crash happening

staying too long in the practice range aim training tends to do it, 2-3 domination matches with the 3 rounds, or the payload maps seem to do. seems to happen a lot on the wakanada payload map for me, but this might just be the amount of data/destructible terrain in those maps

ive started getting the same thing happen sometimes with other things, so im starting to think it's mesa related or kde related, but rivals tends to do it the most. mesa has some issue posts about it though

the way i found to reduce it is setting everything to lowest possible settings, and restarting the game between games, the more maps/projectiles your game processes, the higher the chance you have of the crash happening

Sometimes it hard crashes, so I have to hold power button too. Sometimes it recovers halfway and I have to restart manually. The weird thing is, yesterday I played the entire day for a few hours and had 0 crashes. Then later at night when I started another game it crashed midway suddenly. Its very inconsistent. The days before it was crashing every or every few games. I thought the new patch fixed it. I stopped playing since then, because of the penalty and I don't want to ruin my account.

I think you might be on to something. It often happens when I'm about to ult or in very hectic moments, when a lot is happening on the map. At least those are the most memorable to me, my memory could be skewed. I am playing at roughly 120 FPS (a bit lower, it fluctuates) and use FSR Quality. Maybe I'll try to lower settings too and try out tonight.

I am not sure if there's any causation here but there's correlation for sure... still, might be coincidence after all.
As before, I'm running AMD.
I've noticed that the game seems to get more crashy over time, even before the first january patch - like I said I had no issues at all at the start, and in the end it was crashing about once per hour. @EnnuiL suggested disabling lumen GI, and that did not help. (I'm still running the default settings for 7800XT, I think.)
So I decided to clean out the shader caches since that's the only thing that really changed over time (steam's downloaded caches, vkd3d caches, mesa caches, and UE caches)
It seems to have gotten more stable! (not crash-free, but no longer crashing once per hour) After steam redownloaded the caches, it seems to have gotten less stable again so I disabled shader cache precaching and cleaned the caches again. It still crashes occasionally, but it's rare (and I usually manage to reconnect in time)

Update 2: nevermind.. this was all a massive fluke and after nearly a dozen rounds, it crashed again and i managed to reproduce the consistent crash on Spider-Islands once more; i should just buy an AMD card

Update 2: nevermind.. this was all a massive fluke and after nearly a dozen rounds, it crashed again and i managed to reproduce the consistent crash on Spider-Islands once more; i should just buy an AMD card
Details about false hope

I don't think an AMD card will help you. I have an AMD card (7900xt + 14700k) and Rivals crashes pretty regularly. Seemingly more in Ranked than in Normal.

Other people have pasted their journalctl logs of the crash and mine are the same

crash.txt

Feb 08 19:04:36 gurren kernel: x86/split lock detection: #AC: MarvelRivals_La/32696 took a split_lock trap at address: 0x1465b8ca5
Feb 08 19:04:39 gurren kernel: x86/split lock detection: #AC: Marvel.exe/32895 took a split_lock trap at address: 0x140ca19c9
Feb 08 19:04:39 gurren kernel: x86/split lock detection: #AC: Marvel-Win64-Sh/32917 took a split_lock trap at address: 0x14f4335f2
Feb 08 19:10:14 gurren kernel: perf: interrupt took too long (3128 > 3127), lowering kernel.perf_event_max_sample_rate to 63000
Feb 08 19:57:13 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Feb 08 19:57:13 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Feb 08 19:57:13 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=23042984, emitted seq=23042986
Feb 08 19:57:13 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Process information: process GameThread pid 32917 thread vkd3d_queue pid 33130
Feb 08 19:57:15 gurren kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=RESET
Feb 08 19:57:15 gurren kernel: [drm:amdgpu_mes_reset_legacy_queue [amdgpu]] *ERROR* failed to reset legacy queue
Feb 08 19:57:15 gurren kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
Feb 08 19:57:17 gurren kernel: amdgpu 0000:03:00.0: amdgpu: MES failed to respond to msg=REMOVE_QUEUE
Feb 08 19:57:17 gurren kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
Feb 08 19:57:17 gurren kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
Feb 08 19:57:18 gurren kernel: [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
Feb 08 19:57:18 gurren kernel: [drm] VRAM is lost due to GPU reset!
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x84fc000000 for PSP TMR
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x004e8000 (78.128.0)
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Feb 08 19:57:18 gurren kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Feb 08 19:57:18 gurren kernel: [drm] DMUB hardware initialized: version=0x07002A00
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Feb 08 19:57:19 gurren kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset(2) succeeded!
Feb 08 19:57:19 gurren kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Feb 08 19:58:20 gurren kernel: x86/split lock detection: #AC: CJobMgr::m_Work/46599 took a split_lock trap at address: 0xe97d2caf
Feb 08 19:58:21 gurren kernel: x86/split lock detection: #AC: CJobMgr::m_Work/46135 took a split_lock trap at address: 0xe97d2caf

Sorry to pile on here.

Vulkaninfo

vulkaninfo.txt

Os info

~> uname -a
Linux gurren 6.12.11-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Jan 24 04:59:58 UTC 2025 x86_64 GNU/Linux
~> cat /etc/os-release 
NAME="Fedora Linux"
VERSION="41 (KDE Plasma)"
RELEASE_TYPE=stable
ID=fedora
VERSION_ID=41
VERSION_CODENAME=""
PLATFORM_ID="platform:f41"
PRETTY_NAME="Fedora Linux 41 (KDE Plasma)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:41"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f41/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=41
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=41
SUPPORT_END=2025-12-15
VARIANT="KDE Plasma"
VARIANT_ID=kde

edit: I probably shouldn't be commenting here since I was using GE-Proton-9.23 but it seems like people are experiencing the same crash on Proton Experimental

I don't think an AMD card will help you.

Well... AMD cards don't have consistent crashes on a single map and in my experience they're way rarer in general. At least, as of right now.
Like I wrote two comments before... I am getting the impression that having steam's shader cache files (and perhaps even your own after a while?) makes the game less stable - as seems suspend especially while the game is running.
It's currently crashing like once per 5-10 playtime hours for me maybe? And like I said I almost always manage to rejoin.

But anyways: It seems like today it tried crashing again - emphasis on tried.
Instantly after it froze I tried to alt+tab away (actually, might have been the desktop shortcut too, not sure anymore) - and to my big surprise after a few seconds it actually worked. I was left at the desktop, and I could just maximize the game again and finish the match.

[ 5437.712650] gmc_v11_0_process_interrupt: 60 callbacks suppressed
[ 5437.712655] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5437.712660] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5437.712662] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505f000 from client 10
[ 5437.712664] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
[ 5437.712666] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: TCP (0x8)
[ 5437.712668] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x1
[ 5437.712670] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5437.712671] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[ 5437.712673] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5437.712674] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5437.712678] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5437.712680] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5437.712682] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505c000 from client 10
[ 5437.712684] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5437.712686] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5437.712687] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5437.712689] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5437.712690] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5437.712692] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5437.712693] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5437.712809] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5437.712811] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5437.712813] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505d000 from client 10
[ 5437.712814] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5437.712816] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5437.712817] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5437.712819] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5437.712820] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5437.712821] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5437.712823] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5437.712827] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5437.712829] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5437.712830] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505e000 from client 10
[ 5437.712832] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5437.712833] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5437.712835] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5437.712836] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5437.712837] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5437.712839] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5437.712840] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5447.716022] amdgpu 0000:03:00.0: amdgpu: Dumping IP State
[ 5447.718507] amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
[ 5447.718837] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
[ 5447.719065] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5447.719069] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5447.719071] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505a000 from client 10
[ 5447.719073] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031
[ 5447.719075] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: TCP (0x8)
[ 5447.719076] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x1
[ 5447.719078] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5447.719079] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x3
[ 5447.719080] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5447.719081] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5447.719085] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5447.719087] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5447.719089] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505a000 from client 10
[ 5447.719090] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5447.719091] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5447.719093] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5447.719094] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5447.719095] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5447.719096] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5447.719097] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5447.719101] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5447.719103] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5447.719108] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505a000 from client 10
[ 5447.719109] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5447.719110] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5447.719111] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5447.719113] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5447.719114] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5447.719115] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5447.719116] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5447.719120] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5447.719122] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5447.719123] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505a000 from client 10
[ 5447.719124] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5447.719125] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5447.719127] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5447.719128] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5447.719129] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5447.719130] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5447.719131] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0
[ 5447.719135] amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32800)
[ 5447.719137] amdgpu 0000:03:00.0: amdgpu:  in process GameThread pid 5324 thread vkd3d_queue pid 5547)
[ 5447.719138] amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x000044444505a000 from client 10
[ 5447.719140] amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 5447.719142] amdgpu 0000:03:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 5447.719143] amdgpu 0000:03:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 5447.719144] amdgpu 0000:03:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 5447.719145] amdgpu 0000:03:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 5447.719146] amdgpu 0000:03:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 5447.719147] amdgpu 0000:03:00.0: amdgpu:      RW: 0x0

My theory here (that might of course be entirely wrong) is that this made the game cancel the render call that would have timed out before it could actually do so and cause the driver to reset the GPU, which would mean this could be the "true" error that'd be swallowed by the reset. Then again this could also be a completely distinct error with different symptoms.

I'm currently running Fedora 41 with Plasma 6.2.5, Linux 6.12.11-200.fc41, Mesa 24.3.4 and Proton-GE 9-22, with a Ryzen 7700 and an RX 7800XT.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2646054270

Was just trying to indicate that people still seeing crashes on AMD, albeit more randomly.

Can you elaborate on the things you did to the shader caches? i.e files you removed or settings you changed? That would be a big help.

Having the game be in a state where I can reconnect would be great, as currently I can only reconnect after a full reboot.

Looking at all the reports here, is anyone on NVIDIA GPUs crashing at all?

I haven't had a single crash since getting my 3060 Ti (not for this game, for an unrelated purpose) but even before with my RX 5700XT, I'd only get hangs if I turned on Lumen GI.

If that is so (NVIDIA/RDNA1 users being fine) then there's a chance this is an RDNA2/RDNA3 specific issue. :/

(I won't count Intel Arc as DX12 on Arc was still hit and miss in general last I checked)

Having the game be in a state where I can reconnect would be great, as currently I can only reconnect after a full reboot.

So, actually, you don't need a full reboot (although it can't harm after a crash, either). What's happening is that some system service processes of the wineprefix completely hang up after the GPU reset (only SIGKILL helps at that point), which prevents further using the prefix (a reboot, as you've noticed, does kill them obviously). Killing them makes it possible to start the game again, and reconnect if your PC is fast enough.

Well, my other trick is a bit less fair - I have a second device I can play on :p (Steam Deck)
Interestingly I've never seen it crash on there, and I think @EnnuiL was reporting it never had a GPU crash on her AMD iGPU either, although you can barely play the game on one only intended for diagnostics. So even for RDNA2/3 it sounds like "only" dGPUs are affected? Sounds a bit more like memory management might be involved.

Can you elaborate on the things you did to the shader caches?

I disabled Steam's precaching feature and then cleared the Mesa caches in ~/.cache, AppData/Local/Marvel/Saved/CollectedPSOs in the wineprefix (and the file in Saved) and MarvelGame/Marvel/Binaries/Win64/vkd3d-proton.cache* in the game install folder.

Oh, and I've got a replay id and timestamp for my earlier almost-"crash" if anyone's interested, but since it's not reproducible by watching the replay I don't think it's all too interesting.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2646193079

You just gave me an idea...
Try SteamDeck=1 and see if it helps.
That's provided your Steam Deck isn't crashing. Provided it isn't, it wouldn't surprise me if NetEase have a separate codepath for Steam Deck if it's known by them that RDNA2 GPUs hang at random.

(Try this too RDNA3 users!)

Also note that using SteamDeck=1 also bypasses the launcher permanently until the game updates itself again. (it deletes a file to trigger silent launching if it detects that environment variable, go figure)

A little out of scope: I used to have these crashes that required a full system reboot, and it stopped with proton-ge-23, did you guys give it a go ? (haven't tried proton-ge-24 yet)

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2646197277

I always play with SteamDeck=1, it doesn't fix the crashes for me (7800 XT). I think all it does is bypass the launcher.

A little out of scope: I used to have these crashes that required a full system reboot, and it stopped with proton-ge-23, did you guys give it a go ? (haven't tried proton-ge-24 yet)

I'm a bit skeptical. Because I have rare crashes now, from one day to another (there was updates of the game in between). Now I can play many games and only experienced twice a crash since then. Before this, (literally the day before the game update) the game was crashing every game or every 2 to 3 games. Either hard crash where I had to push the button or a soft crash with half recovery from KDE.

The game update was on February 6th. Did you switch to Proton GE at that time period maybe?

I always play with SteamDeck=1, it doesn't fix the crashes for me (7800 XT). I think all it does is bypass the launcher.

I can confirm this as well, although it also disables XeSS framegen (that's why it worked around the crash after the update) and whatever XeSS thing XeLL is.

I just noticed I never tried to disable Lumen GI after the shader cache cleaning, though, I'll do that and see if it crashes again.

I just remembered something else though, I was meaning to do a custom vkd3d build and try applying some of its newly added hacks for FF7R that were apparently supposed to fix an issue that sounds relatively similar, didn't get around to it yet though.

Looking at all the reports here, is anyone on NVIDIA GPUs crashing at all?

Yes, I am, running Hyprland on an NVIDIA RTX 4080 with Proton GE 9-23. My game used to crash frequently (like every 10 minutes), but avoiding Lumen GI settings has definitely improved that. Currently, I only crash once every 10 hours of playtime or so. A friend of mine playing natively on Windows with an NVIDIA RTX 3080 also crashes occasionally, so I guess this is an issue of the game itself, not of Proton. I have also tried various Proton versions, but couldn't really observe a difference.

Besides these (now rare) crashes, I am facing stuttering problems. After playing 2-3 games (quickplay, ranked, ...) my fps drop from being above 150 to about 30, maybe less. I can fix this by restarting the game. I have made it a habit by now to restart Marvel Rivals every 2 games I play to prevent this, which works for now, but is somewhat annoying.

Thanks @kb-1000 I'll try clearing those caches

So, actually, you don't need a full reboot (although it can't harm after a crash, either). What's happening is that some system service processes of the wineprefix completely hang up after the GPU reset (only SIGKILL helps at that point), which prevents further using the prefix (a reboot, as you've noticed, does kill them obviously). Killing them makes it possible to start the game again, and reconnect if your PC is fast enough.

Would be helpful if I knew what to SIGKILL. Any idea what processes to look for?

You are right that when I crash it usually takes me back to the desktop. But trying to launch the game after that doesn't work. Stean just says "Running" even though it isn't.

Also I always have SteamDeck=1 to people who mentioned it. The game won't launch on Linux otherwise to my knowledge.

Also I always have SteamDeck=1 to people who mentioned it. The game won't launch on Linux otherwise to my knowledge.

I think this was fixed in more recent Proton hotfix versions actually (making XeSS frame generation no longer crash during game initialization if not completely disabled which like I said SteamDeck=1 does)

Would be helpful if I knew what to SIGKILL. Any idea what processes to look for?

Primarily the winedevice.exe ones - I think killing those should make the other parts exit automatically? But in the end, all surviving wine processes.
winedevice seemed stuck in some sort of segfault loop:

Thanks, I'll give that a shot.

Which proton are you using @kb-1000 ?

edit: nvm you said in an earlier comment Proton GE 22. my bad

I'm a bit skeptical. Because I have rare crashes now, from one day to another (there was updates of the game in between). Now I can play many games and only experienced twice a crash since then. Before this, (literally the day before the game update) the game was crashing every game or every 2 to 3 games. Either hard crash where I had to push the button or a soft crash with half recovery from KDE.

The game update was on February 6th. Did you switch to Proton GE at that time period maybe?

That sounds more plausible indeed, I didn't pay attention to that. I don't play for too long (2-3h usually) to have met crashes ever since.

After doing @kb-1000 's cache clear out suggestions + shader pre-caching disabled I played quite a bit without crashes in quick play. Will be interested to see if it carries over to Ranked which is where I usually crash more.

My game sometimes crashes with an assertion like:
loader_thunks.c: !status && vkDestroy

My launch options are:
SteamDeck=1 __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1 %command%
and I'm on Proton Experimental with an RTX3060.

May be related https://gitlab.freedesktop.org/mesa/mesa/-/issues/12395

Also getting amdgpu driver crashes randomly, I thought it might be my GPU clocked too high or a power profile, I reduced the clocks by 300MHz each and changed power profile to High and it did not help.

May be related https://gitlab.freedesktop.org/mesa/mesa/-/issues/12395

Ah yes, that is my issue; I closed it thanks to the false hope I had that a second PR would fix it; Unfortunately, I don't think they have any interest on fixing that issue

Adding to my above report, I had another hard crash on my system today after a few days of no crashes. I have a proton log file (steam-2767030.log), but it's 2.3GiB in size (22.9MiB xz compressed). Is there a way I can share it? Github won't let me upload an xz file, and a ZIP file won't compress small enough.

Github won't let me upload an xz file, and a ZIP file won't compress small enough.

Maybe ZIP the XZ file. While it won't compress further, this might allow the upload.

Please find attached a Proton log for my previous post. This log covers a gaming session where Marvel Rivals hard crashed and apparently took the display driver with it.

20250214-1054-steam-2767030-hardcrash-ultrasettings.log.xz.zip

(I assume that there is no data in this log file that could compromise my accounts. Would that be correct?)

Interestingly I've never seen it crash on there, and I think @EnnuiL was reporting it never had a GPU crash on her AMD iGPU either, although you can barely play the game on one only intended for diagnostics. So even for RDNA2/3 it sounds like "only" dGPUs are affected? Sounds a bit more like memory management might be involved.

Update: She's had one now - so this does also affect AMD iGPUs.

Does anyone get a black window with the cursor on Wayland but load normally normally with X11? Running KDE on Archlinux. Had to revert to X11 due to this.

I've been having some success recently by clearing various caches before playing.

However I just ran into a crash playing my first comp match of the day after clearing the caches before playing.

Feb 16 13:40:31 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Feb 16 13:40:31 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Feb 16 13:40:31 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered
Feb 16 13:40:41 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Feb 16 13:40:41 gurren kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Feb 16 13:40:41 gurren kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, but soft recovered

It wasn't a hard crash this time, but the game just froze for probably 10 seconds then recovered.

w.r.t my last comment that is on Proton-GE22. I see that Proton Experimental has a couple of notes about Rivals in the Changelog.

Fixed Stalker 2, The Axis Unseen, Beyond Handwell, Marvel Rivals, The Finals, Creatures of Ava crashing with Intel GPUs.
Fixed Marvel Rivals crashing on non-Steam Deck devices after a recent game update.

would switching to Proton-GE25 or Proton Experimental possibly fix some of the amdgpu issues?

also does anyone know what commits these lines in the changelog are referencing? just curious

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2661596152

Huh, this is interesting; I have seen no explicit progress for Marvel Rivals and I couldn't find any changelog for Proton Experimental;
I did try the bleeding-edge branch of Proton Experimental though, and there is still a consistent crash on Spider-Islands

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2661596152

I couldn't find any changelog for Proton Experimental;

https://github.com/ValveSoftware/Proton/wiki/Changelog

This is what I was referring to

I assume that's the fix for the XeSS frame generation library they introduced a few updates ago, which SteamDeck=1 disables. It was crashing on initialization even if not enabled in the graphics settings.

I haven't experienced any crashes since clearing the shader cache (worth noting I don't do that each launch) and now disabling Lumen GI, but that might just have been luck. It's definitely nowhere near the almost constant hourly crash from before, though.
I've now went and applied this workaround for FF7R to Rivals locally in a custom vkd3d build: https://github.com/HansKristian-Work/vkd3d-proton/pull/2319 (installed it by copying it into the lib64/wine/vkd3d-proton folder of proton-ge 9-25)
But, of course, I have no idea if that actually improves anything. Still hasn't crashed since, but I haven't been playing for too long.

w.r.t my last comment that is on Proton-GE22. I see that Proton Experimental has a couple of notes about Rivals in the Changelog.

I have way way less crashes than before. Can't say if its because of Proton (I use Experimental by default) or if its the game updates itself, maybe a combination. I also lowered the graphical settings a bit, after I received a new message that was never seen before when launching the game. The message was about the Kernel having not enough Memory. I assume it meant the GPU VRAM (8gb) as my system RAM is 32gb and enough.

Overall I have a much better experience at the moment.

I assume that's the fix for the XeSS frame generation library they introduced a few updates ago, which SteamDeck=1 disables. It was crashing on initialization even if not enabled in the graphics settings.

I haven't experienced any crashes since clearing the shader cache (worth noting I don't do that each launch) and now disabling Lumen GI, but that might just have been luck. It's definitely nowhere near the almost constant hourly crash from before, though. I've now went and applied this workaround for FF7R to Rivals locally in a custom vkd3d build: HansKristian-Work/vkd3d-proton#2319 (installed it by copying it into the lib64/wine/vkd3d-proton folder of proton-ge 9-25) But, of course, I have no idea if that actually improves anything. Still hasn't crashed since, but I haven't been playing for too long.

That makes sense about the XeSS bit.

When you say disabling Lumen GI, what settings are you referring to specifically?

In the game there's "Global Illumination", which I have set to "SSGI"

And there's "Reflection Quality", which I have set to "Screen Space Reflections"

Lumen GI is just an option for Global Illumination. So by "disabling Lumen GI" do you mean choosing something that isn't Lumen GI, or setting "Global Illumination" to "Off"?

What does that vkd3d-proton patch do that would benefit Rivals? I'd say maintaining a custom patch in my vkd3d-proton is a bit beyond my comfort level.

When you say disabling Lumen GI, what settings are you referring to specifically?

For me, setting it to SSGI.

What does that vkd3d-proton patch do that would benefit Rivals? I'd say maintaining a custom patch in my vkd3d-proton is a bit beyond my comfort level.

If I'm not misunderstanding, it appears to be a workaround for GPU hangs that sound really similar on AMD in FF7 Rebirth, which seems to use UE5 as well. Like I'm saying though, I do not currently know if it actually benefits Rivals. It's hard to conclusively test when the only way to do so is playing for tens of hours and see if you're unlucky enough to run into a crash by then.
(All I did is adding another entry in that workaround list with Rivals' executable name, copying FF7R's)

Thanks @kb-1000 . That all makes sense

Updating to GE-Proton-9-25 did not help for me. I've seen two more crashes since doing so.

Wondering if the new Mesa 25 might alleviate some of the issues.

Rather than just mention ad-hoc crashes and journalctl logs I'm going to try and be more helpful and do
PROTON_LOG=1 %command% and report back here

Okay I tried PROTON_LOG=1 within like 20 seconds the log file was 3.4 GiB.

Given that my mean time to failure is anywhere from 2-10 games my disk would run out of space before I would hit the failure.

Is there a way to reduce the logging to only critical levels?

Okay I tried PROTON_LOG=1 within like 20 seconds the log file was 3.4 GiB.

Given that my mean time to failure is anywhere from 2-10 games my disk would run out of space before I would hit the failure.

Is there a way to reduce the logging to only critical levels?

I have an 87 GB log file that has a crash in it, but I don't necessarily know what I am looking for. I too am running a 5700XT on Pop OS.

You mentioned previously that you were clearing caches. Could you let me know what caches you were clearing so I can also try this?

I don't know what happened, but now the game is crashing almost every game; sometimes multiple times after I reconnect to same match. It was working really good the last week, with hours of playing every day without a crash. But since today, its unplayable, ranked and casual mode.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2670458300

Did what kb-1000 mentioned here https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2646193079

I think disabling steam precaching has helped a lot

I see Marvel Rivals mentioned in mesa 25 release notes related to shaders

https://docs.mesa3d.org/relnotes/25.0.0.html#bug-fixes

Crashing while Processing Shaders in Marvel Rivals on Mesa 24.3.2 & Mesa 24.3.3

wondering if this could be a source of crashes for people here

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2672967760

I'm going to be testing out Mesa 25 and see if my game crashes. Hopefully this is the fix.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2673151358

I'm not sure how to test this. Its not in Pop OS yet. Will see if I can find info on installation

I tried installing mesa 25.0.0 on pop via oibaf. I had no luck. It just wasn't finding the update. I was able to get kisak-mesa installed, but that didn't provide me mesa 25.0.0. I'll keep trying tomorrow. If anyone has step by step instructions, I would love to test.

I tried installing mesa 25.0.0 on pop via oibaf. I had no luck. It just wasn't finding the update. I was able to get kisak-mesa installed, but that didn't provide me mesa 25.0.0. I'll keep trying tomorrow. If anyone has step by step instructions, I would love to test.

I only found instruction very specific to fedora

Not sure if this helps at all, but I did play some rivals tonight and truncated my proton log every game. Unfortunately, I didn't see any errors in it, however, I did see this set of messages in dmesg.

[ 4008.475909] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=4397736, emitted seq=4397738
[ 4008.476242] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process GameThread pid 138210 thread vkd3d_queue pid 138375
[ 4008.476553] amdgpu 0000:2f:00.0: amdgpu: GPU reset begin!
[ 4008.765009] amdgpu 0000:2f:00.0: amdgpu: BACO reset
[ 4011.904396] amdgpu 0000:2f:00.0: amdgpu: GPU reset succeeded, trying to resume
[ 4011.904879] amdgpu 0000:2f:00.0: amdgpu: PSP is resuming...
[ 4011.950841] amdgpu 0000:2f:00.0: amdgpu: reserve 0x900000 from 0x81fd000000 for PSP TMR
[ 4011.994192] amdgpu 0000:2f:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 4012.000090] amdgpu 0000:2f:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 4012.000094] amdgpu 0000:2f:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[ 4012.000097] amdgpu 0000:2f:00.0: amdgpu: SMU is resuming...
[ 4012.000140] amdgpu 0000:2f:00.0: amdgpu: use vbios provided pptable
[ 4012.000143] amdgpu 0000:2f:00.0: amdgpu: smc_dpm_info table revision(format.content): 4.5
[ 4012.002946] amdgpu 0000:2f:00.0: amdgpu: SMU is resumed successfully!
[ 4012.216742] amdgpu 0000:2f:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[ 4012.216746] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 4012.216749] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 4012.216751] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 4012.216754] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 4012.216757] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 4012.216759] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 4012.216762] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 4012.216764] amdgpu 0000:2f:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 4012.216767] amdgpu 0000:2f:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[ 4012.216770] amdgpu 0000:2f:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[ 4012.216773] amdgpu 0000:2f:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[ 4012.216775] amdgpu 0000:2f:00.0: amdgpu: ring vcn_dec uses VM inv eng 0 on hub 8
[ 4012.216778] amdgpu 0000:2f:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 1 on hub 8
[ 4012.216781] amdgpu 0000:2f:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 4 on hub 8
[ 4012.216784] amdgpu 0000:2f:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[ 4012.219495] amdgpu 0000:2f:00.0: amdgpu: recover vram bo from shadow start
[ 4012.227809] amdgpu 0000:2f:00.0: amdgpu: recover vram bo from shadow done
[ 4012.227841] amdgpu 0000:2f:00.0: amdgpu: GPU reset(2) succeeded!

Going to dig through some of the other suggestions in this thread to see if anything helps.

The newest patch seems to freeze for 1s at 7-10 second intervals, game otherwise runs fine. Happens regardless of SteamDeck=1 or using gamemode or not, also still happens with Steam Overlay disabled. Any ideas?

Ryzen 7 3700X
NVIDIA RTX 3060 Ti with driver 570 (proprietary)
16GB RAM
Arch Linux, kernel 6.12

The newest patch seems to freeze for 1s at 7-10 second intervals, game otherwise runs fine.

Its possible that these are shader compilations, caused by the new update and making older Shaders to recompile. Did you deactivate the pre-cache for Shaders in Steam maybe? In that case it would compile while you game and this could explain this. If you keep getting those freezes, then that's another issue.

The newest patch seems to freeze for 1s at 7-10 second intervals, game otherwise runs fine.

Its possible that these are shader compilations, caused by the new update and making older Shaders to recompile. Did you deactivate the pre-cache for Shaders in Steam maybe? In that case it would compile while you game and this could explain this. If you keep getting those freezes, then that's another issue.

I never use shader pre-caching, have had it off since the feature was introduced as it kept trying to download something every single day I'd open Steam. It's definitely not that.
Given other games aren't affected I'm guessing a game bug at this point.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2674922826

Can Confirm, I also am having the same issue. Tried running the pre-shader cache and process vulkan shaders yet the same issue still persists.

Ryzen 7 3700x
RTX 2080ti
Pop OS 22.04

Seems like @FuzzyQuils and @bayedieng are both on Nvidia.

I'll have to see if I get the same thing with the new patch on AMD today.

Can confirm this does happen with AMD as well,
GPU: 7900 XT
CPU: 7950X

Can confirm this does happen with AMD as well,
GPU: 7900 XT
CPU: 7950X

@ajlittle which proton and mesa are you on? also what os info

and would be willing to test with mesa 25?

reply to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2674805740
reply to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2675146512

I can confirm this also happens on my end. The same build ran fine before the update.

Could the issue be connected with the addition of DLSS4 and anti lag 2?

GPU: 7900XTX
CPU: 7800X3D
Distro: Nixos Unstable
Kernel: Zen 6.13.1
Mesa: 24.3.4
Compositor: Hyprland 0.47.2
Proton: GE Proton 24

I tested with Mesa 25 from mesa-git, it still happens. For me the stutter is an extremely regular interval, as if it's doing some kind of loop (garbage collection?) in the background.

GPU: 7900XTX
CPU: 7950X
Distro: Arch
Kernel: 6.12.15 LTS (ZFS doesn't support 6.13 yet)
Mesa: 25.1.0_devel.202021.eb8017ca68f-1
Compositor: kwin 6.3.1
Proton: Tried Experimental and GE

I am relaying this comment from Reddit:

I have narrowed it down to this - the game is running a powershell script to pull CPU data every 20 seconds, spawning these two processes. I assume the second one is to write to the games internal db. Anytime the game does this (it does for various other things), the game freezes until it's done.

PID: 199061 -> /home/linux/.local/share/Steam/compatibilitytools.d/GE-Proton9-.. /home/linux/.local/share/Steam/compatibilitytools.d/GE-Proton9-25/files/bin/wine64-preloader /home/linux/.local/share/Steam/compatibilitytools.d/GE-Proton9-25/files/bin/wine64 powershell -Command 
Get-WmiObject -Query "SELECT Name, PercentProcessorTime FROM Win32_PerfFormattedData_PerfProc_Process 
WHERE PercentProcessorTime > 0 AND IDProcess=576 OR Name='_Total' OR Name='Idle'" | 
ForEach-Object { [PSCustomObject]@{ ProcessName=$_.Name; CPUUsage=$_.PercentProcessorTime } } | 
Format-Table -AutoSize

PID: 199063 -> /home/linux/.local/share/Steam/compatibilitytools.d/GE-Proton9-.. /home/linux/.local/share/Steam/compatibilitytools.d/GE-Proton9-25/files/bin/wine64-preloader /home/linux/.local/share/Steam/compatibilitytools.d/GE-Proton9-25/files/bin/wine64 C:\windows\system32\conhost.exe --server 0x2c --headless

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2675426085

Definitely isn't just a Wine/Proton issue. Users in the Discord are reporting the same issue on Windows and mentioning antivirus flags about Powershell. Will probably just need to be hotfixed by the devs and hopefully that happens within a day or two.

The newest patch seems to freeze for 1s at 7-10 second intervals, game otherwise runs fine. Happens regardless of SteamDeck=1 or using gamemode or not, also still happens with Steam Overlay disabled. Any ideas?

Ryzen 7 3700X NVIDIA RTX 3060 Ti with driver 570 (proprietary) 16GB RAM Arch Linux, kernel 6.12

I can't believe but it got even worse. Okay, got the new update and have the exact same issue - on top of the multiple crashes per match. It's depressing, as like to play and have over 180 hours playtime so far.

Ryzen 7 7700X + AMD RX 7600 with Mesa 24.3.4-arch1.1 (reported by glxinfo | grep "OpenGL version"), 32 GB RAM, EndeavourOS based on Arch, Kernel 6.13.3-arch1-1.

Current workaround found for issue (Linux only):

/home/USERNAMEHERE/.steam/steam/steamapps/compatdata/2767030/pfx/drive_c/windows/system32/WindowsPowerShell/v1.0

Rename powershell.exe to another name, this will only affect powershell in the instance for marvel rivals's proton, and will not mess with anything else. Fixes issue immediately with no apparent issues in multiple matches so far tested.

Current workaround found for issue (Linux only):

/home/USERNAMEHERE/.steam/steam/steamapps/compatdata/2767030/pfx/drive_c/windows/system32/WindowsPowerShell/v1.0

Rename powershell.exe to another name, this will only affect powershell in the instance for marvel rivals's proton, and will not mess with anything else. Fixes issue immediately with no apparent issues in multiple matches so far tested.

This is a hilarious fix if it works. I wonder if the script is trying to query or insert anything critical to the game or if it's just performance analytics. I'm actually surprised they just ignore powershell being missing and don't error out.

Current workaround found for issue (Linux only):

/home/USERNAMEHERE/.steam/steam/steamapps/compatdata/2767030/pfx/drive_c/windows/system32/WindowsPowerShell/v1.0

Rename powershell.exe to another name

I'm currently playing a few matches and it really fixed the awful stutter issue (no stutter at all, just like before the update). The crashes still happen.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2675730671

It seems like maybe a dev testing tool left on, it's querying CPU usage every 20 seconds and then pushing it to a database internally it looks like, probably an accident.

Current workaround found for issue (Linux only):

/home/USERNAMEHERE/.steam/steam/steamapps/compatdata/2767030/pfx/drive_c/windows/system32/WindowsPowerShell/v1.0

Rename powershell.exe to another name, this will only affect powershell in the instance for marvel rivals's proton, and will not mess with anything else. Fixes issue immediately with no apparent issues in multiple matches so far tested.

So when I do this it seems a new powershell.exe is created in its place. I am on Fedora

Edit: I tried just deleting the powershell.exe entirely and it fixed the issue.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2675881120

Interesting! Are you deleting the exe at all, or just renaming? Are you running any specific version of proton or launch commands that could be messing with things? I know steam stores its powershell exe in different locations depending on the flavor of proton you're using.

(Not a proton developer, just trying to help fellow linux users in the meantime until it's fixed properly!)

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2675426085

...You've got to be kidding me.
No wonder some people clown on the technical side of this game.
Anyway I'll try moving/renaming PowerShell in my Proton Prefix and see what happens.

The PowerShell.exe file appeared back. So don't forget to delete it over and over again...

The PowerShell.exe file appeared back. So don't forget to delete it over and over again...

Or just set up a cron

Can confirm proton ge with the hotfix py works.

With that said it looks like Gofman has already patched in a hack that disables powershell only for this game: https://github.com/ValveSoftware/wine/commit/e75684e73e3d68a838473c27c27fa0d6f4de601c

I suspect Proton Hotfix has this as well as I have a download for it here.

Using Mesa 25.1.0-devel, I played 16 matches without a crash. If this changes I'll update.

OS: Fedora Linux 41 (KDE Plasma)
KERNEL: 6.12.15-200.fc41.x86_64
CPU: 11th Gen Intel Core i7-11700F @ 2.50GHz
GPU: AMD Radeon RX 7900 XTX (radeonsi, navi31,
LLVM 19.1.7, DRM 3.60, 6.12.15-200.fc41.x86_64)
RAM: 32 GB

using Mesa 25, freeze/crash reproduced

To clarify: I removed the powershell.exe from my proton prefix. There is no file in that folder anymore. I didn't get another one popping up when running the game. The game runs perfectly.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2676102740

I was using mesa 25.0 last night (built manually from git on Fedora using a guide from Venemo) with the protonfixes for removing powershell and also saw no crashes. Will mention here if I see any.

I don't know if is linked to the powershell issue or not but I've been having random crashes even if I remove the powershell.exe out of the folder. The crash throws the following error message:

File: ../src-wine/dlls/winevulkan/loader_thunks.c
Line: 5953
Expression: !status && "vkLatencySleepNV"

My system info:
Ryzen 7 5800x3d
RTX 3080
Arch Linux 6.13.3-arch1-1
WM Hyprland 0.47.2
Nvidia Driver 570.86.16

Proton versions i've tried so far

• Proton Experimental
• Proton Hotfix
• Proton 9.0-4
• ProtonGE-24
• ProtonGE-25

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2676437966

I resolved this by adding launch option:

VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2676437966

Disable NVIDIA Reflex in the game options; known problem with the NVIDIA drivers that hasn't been fixed yet AFAIK.

You should be able to do this before logging in.

Perhaps I should post an update too - after the patch, on the same day I played one quick play game on the new map, then went to practice range and... crashed. (I was also running into those lagspikes)
So I think it's safe to say the vkd3d patch I applied is useless.
I haven't tried Mesa 25 yet, though, will do that later.
Side note, I've been playing 16 games in a row without crashes before too, but it still wasn't 100% stable evidently so that doesn't have to mean much.

work arounds i'm using

• I've found that if i restart the game after these, it becomes very rare and only seems to happen in longer games:
  • any competitive match
  • spectating/watching replay for any match
  • every 2 quickplay convoy/convergence maps
  • practice range usage
• i've renamed the powershell.exe rather than deleting it
• graphics settings all set to lowest or off, with 1280x720 resolution
• no other devices connected to local network (ping starts to get high randomly and it crashed once at the same time i put my apple watch in aeroplane mode which was odd)
• discord open rarely but usually closed, happens regardless
• single monitor

System information copy pasta

Operating System:       Kubuntu 24.10
KDE Plasma Version:     6.1.5
KDE Frameworks Version: 6.6.0
Qt Version:             6.6.2
Kernel Version:         6.11.0-18-generic (64-bit)
Graphics Platform:      X11
Processors:             12 × AMD Ryzen 5 7600 6-Core Processor
Memory:                 30.5 GiB of RAM
Graphics Processor:     AMD Radeon RX 6600
Manufacturer:           Micro-Star International Co., Ltd.
Product Name:           MS-7E28
System Version:         1.0

Setup

Steam:   flatpak
Proton:  GE-Proton9.25
Mesa:    Mesa 24.2.8-1ubuntu1~24.10.1

Command line arguements

SteamDeck=1 %command%

Perhaps I should post an update too - after the patch, on the same day I played one quick play game on the new map, then went to practice range and... crashed. (I was also running into those lagspikes)
So I think it's safe to say the vkd3d patch I applied is useless.
I haven't tried Mesa 25 yet, though, will do that later.
Side note, I've been playing 16 games in a row without crashes before too, but it still wasn't 100% stable evidently so that doesn't have to mean much.

curious how mesa 25 goes for you. for me i've played the last two days without crashes. not sure how many games

Perhaps I should post an update too - after the patch, on the same day I played one quick play game on the new map, then went to practice range and... crashed. (I was also running into those lagspikes)
So I think it's safe to say the vkd3d patch I applied is useless.
I haven't tried Mesa 25 yet, though, will do that later.
Side note, I've been playing 16 games in a row without crashes before too, but it still wasn't 100% stable evidently so that doesn't have to mean much.

curious how mesa 25 goes for you. for me i've played the last two days without crashes. not sure how many games

Safe for me. Played around 30 matches in the past 2 days and haven't crashed yet on the latest Mesa 25.

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

I resolved this by adding launch option:

VKD3D_DISABLE_EXTENSIONS=VK_NV_low_latency2 

Yep, that did it for me. After removing powershell.exe and adding that launching option that solved it. I believe they launched an update that removes the powershell thing in todays update.

Update: Good news! The MR needed to support Marvel Rivals on Intel GPUs has been merged on Mesa's main branch! And I managed to play with it for a while;
Bad news! It was a fluke! I eventually managed to get the crashes once more (Spider-Islands is consistent, but even more consistent is dying there)
I'll wait for someone else to open an issue on Mesa's issue tracker

For AMD GPUs, I've been having issues described with the mesa 24.3.3 driver here (poster using mesa 24.3.4 driver, not sure if 25.0 will include fixes, but I hope so!)

tl;dr amdgpu ring gfx_0.0.0 timeout that hard-crashes the driver and the game, and sometimes other apps like steam or a web browser. No idea how to fix it yet and I've been living with it, with the game sometimes going fine for hours of gameplay.

For AMD GPUs, I've been having issues described with the mesa 24.3.3 driver here (poster using mesa 24.3.4 driver, not sure if 25.0 will include fixes, but I hope so!)

tl;dr amdgpu ring gfx_0.0.0 timeout that hard-crashes the driver and the game, and sometimes other apps like steam or a web browser. No idea how to fix it yet and I've been living with it, with the game sometimes going fine for hours of gameplay.

The latest Mesa 25 seemed to fix crashes for me. I've played around ~35 games and haven't crashed yet. If you use Fedora, this is the guide I used to get the latest Mesa 25 without replacing it as a whole on my system. I'm able to call a script in my steam launch options that will have it run Mesa 25 instead of the default Mesa that is on my system. This is a safer way to try it out without completely risking the stability of your system. https://gist.github.com/Venemo/a9483106565df3a83fc67a411191edbd

Unsure if this is related to any other issues, but Rivals doesn't even launch for me.

CPU: Ryzen 7 5700g
GPU: RTX 3060
GPU Driver Version: Mesa 24.3.4-arch1.1
Distro: Arch Linux
Kernel Version: 6.13.4-arch1-1
System Info Report: gist
Proton Version: Experimental
Proton Log: steam-2767030.log

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2682949825

Do you have SteamDeck=1 in the launch options? I need that for it to launch. It just skips the regular launcher

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2683443006

I have tried that many times, nothing changes. Except for (possibly) the shader compiling notice appearing for a split second.

I have tried that many times, nothing changes. Except for (possibly) the shader compiling notice appearing for a split second.

one of the things the rivals team recommend first is to clear your shader cache and or turning off precaching, if it's only popping up for a second and especially if it's the ue5 error window and not a regular error then you may need to try those

(i dont know how to do that though, i rage quit often enough and need to redownload the game from scratch at least twice a week, so it's cleared for me)

not sure if it matters but ive had to undo the powershell renaming a couple times to send suggestions or pay for lattice.
the first kept showing network error but mightve been a server issue, the latter wanted me to upload an html file when i clicked authorise
probably just a coincidence though, but if anyone is able to reproduce it might help to know

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2682949825

i might be wrong but your system info looks like it's trying to run using 32 bit rather than 64?

maybe your steam might be installed using 32bit?

it has a bunch of stuff about not compatible in x11/vpaapi

x11/vulkan also seems to be suffering in that log, this might be something to do with your environment/regular proton, protonGE might work better for you, ive been running that since season 0 for the menu video fix it has

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2683518953

I'm not sure about the 64/32 bit stuff (or even how to check it), I have been trying to use GE but it does nothing.
EDIT: Not sure if it matters, but it did the same on wayland

Unsure if this is related to any other issues, but Rivals doesn't even launch for me.

CPU: Ryzen 7 5700g GPU: RTX 3060 GPU Driver Version: Mesa 24.3.4-arch1.1 Distro: Arch Linux Kernel Version: 6.13.4-arch1-1 System Info Report: gist Proton Version: Experimental Proton Log: steam-2767030.log

It looks like you don't have the proprietary NVIDIA driver installed at all here; nouveau will not work, especially not for this game.
I'd recommend installing NVIDIA driver 570 (nvidia-dkms or nvidia-open-dkms from arch repos) for that GPU, along with any 32-bit dependencies those drivers recommend.

Also if you have AMDVLK installed, remove it. Even if you wanted to use the APU graphics to play this game, RADV performs significantly better than this driver.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2684023100

tysm that fixed it. I had noticed earlier that my 3060 wasn't being used, but I thought that was unrelated. I didn't think that it would cause the game to not even load.

Just compiled mesa from git today and all UE5 Games which previously refused to start (dx 12 not supported error) are working now.
Havent tested much gameplay yet, currently checking how performance changed and if gfx glitches occure in other games.

steamcommands: "gamemoderun mangohud %command%"

current system config:
OS: Arch Linux
KERNEL: 6.13.4-zen1-1-zen
CPU: AMD Ryzen 7 5800X 8-Core
GPU: Intel Mesa Intel Arc A770 (DG2)
GPU DRIVER: 4.6 Mesa 25.1.0-devel (git-826acf5dce)
RAM: 32 GB

Been playing almost a week now on mesa 25 + proton GE 25 and seen no crashes. Really feels like that fixed my stability issues on AMD

curious how mesa 25 goes for you. for me i've played the last two days without crashes. not sure how many games

Yeah, so... I am not sure how representative this result is, however, I DID just run into a crash on Mesa 25. In fact, I ran into two crashes today...
I had done a local build of 25.0.0 together with LLVM main (with assertions enabled, unlike mesa) a few days ago, but I forgot I hadn't set it up inside steam (only by simply running steam inside meson devenv).
So I ran into a crash on Mesa 24 (a fairly interesting one actually, somehow it recovered just enough for the game to stay alive but stay frozen, steam let me just kill it and the match shows as victory in my history), didn't reboot or clear shader caches, and ran into another crash a few games on Mesa 25 later.
edit: Worth noting, AFAIK this was still on Linux 6.12.x, maybe 6.13 improved something?

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2689147375

I sadly just ran into a crash on Mesa 25 after quite a few games. So that might not be a total fix but it definitely seems less frequent for me.

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

I sadly just ran into a crash on Mesa 25 after quite a few games. So that might not be a total fix but it definitely seems less frequent for me.

Same for me, I've only ran into 1 crash after using the latest Mesa drivers for a week. A huge improvement from crashing pretty much after 3-4 games.

Wish I had only a crash after 3 games. Mine crashes usually at least once per match / game, and worst 4 times - each match. And if I am even more unlucky, then one of the crashes result randomly in a hard crash of the entire OS, with a hard reset on physical button...

Apparently reducing the GPU load (lower settings) will help. I've read it might be a memory leak in the game (not confirmed) and therefore cards with more VRAM have less issues. I have an AMD RX 7600 8gb model and it was terrible (as described before).

I'm currently playing with 720p, 75% resolution scale, every graphics setting to low or disabled and 90 fps limit. Now I can play multiple matches without any crash, maybe after 2 or 3 games once (before this, it crashed 4 times per match!). Game looks very pixelated, but only way for me to play at the moment.

On my 7800XT, with close default graphics settings except for using SSGI (upscaling set to Quality, otherwise set to High) on 1440p, it sits comfortably at a bit above 9GB VRAM used on Spider Islands for me, which is the heaviest map AFAICT. I don't think there's memory leaks, but the usage is certainly fairly high. That's "modern" games for you, really...

Oh and, I haven't ran into any crashes with Linux 6.13 + Mesa 25 yet - will report if I do, but I have been playing a lot since.

Just updated to Mesa 25.0.1 w/ Linux 6.13.6 (Bazzite) and played a whole session of Marvel Rivals, including with the Spider Islands map, and ZERO crashes. Also it could just be placebo but performance feels just a tad better.

P.S. 7800XT on bare-minimum settings and ultrawide (game looks no different on minimum).

I updated to Mesa 25 too (on Archlinux based EndeavourOS)

vulkaninfo --summary | grep -m1 driverInfo
driverInfo = Mesa 25.0.1-arch1.2

And still have crashes. Before and after update, I have sometimes random play sessions for multiple matches without a crash. Then after the first crash happens when playing for a while, the crashes get worse and more requently (game crash, just restart game works), until entire PC freezes and locks up.

So for me, Mesa update didn't fix the issue.

Since my last post, I had been playing with zero crashes, until 3 days ago. Yesterday I got 2 crashes in like 3 hours playtime... even after explicitly cleaning out the caches again, so that's not it. Mesa 25.0.0 and Linux 6.13.5, I'll be updating to 25.0.1 and 6.13.6 but I'm skeptical of that improving anything. Still on Proton-GE 9-25.

Before the crashes, you could see it starting to slightly lag, and I'm relatively sure I was close to a third crash.

In case anyone was under the impression that these freezes only happen when in a match, this does not appear to be the case, I just ran into a hard freeze on Mesa 25 on the pre-game loading screen.

EDIT switching to TAUU seems to have reduced the frequency of crashes for me (AMD)

Hello! I have tested Marvel Rivals again after hearing of the Switch Shader Compilation Mode feature; I'll still have to wait for Season 2 (and miss Season 1) for that, but!

I can confirm that the round loading screen (with the video running) stutters so much that it pretty much freezes the game; Intel XeSS apparently freezes, AMD FSR 3 stutters so much but it does slowly progress, but too slowly to the point of killing the custom game before it finishes loading; I can confirm TAAU fixes this

But! The GPU hang on the Intel Arc A380 still happens! And unfortunately, TAAU doesn't fix it; I'll see if that new optimization will help (likely not though)

EDIT: Switching to TAAU after an attempt to load with FSR 3 and having the video super stutter was effectively placebo here; maybe it's still trying to compile shaders on the fly? After compiling shaders?

I need to use SteamDeck=1 to play the game but that skip the launcher. The new shader compilation setting can only be enabled from there and I'm confused what to do. I found a file that looks like the launcher setting in AppData/Local/MarvelRivals_Launcher/meta_info, which contain experimental_feature_switch_record line.
I ask someone on windows and running the game with it disabled or enabled do change the value ("experimental_feature_switch_record": {"1": true} with it enabled) but I can't tell if it's really enabled on my end if I just edit the file.

EDIT : a user asked support and got the launch command : -PSOCompileMode=1. Props to him !

I can confirm also that across Proton 9.0-4, Proton Experimental and GE-Proton 9-27 that the game will not launch on Desktop Linux (Kubuntu) without adding the SteamDeck launch command.

Proton log file (Proton 9.0-4):

steam-2767030.log

In my case, suprisingly without SteamDeck=1 launcher still doesnt start and game goes on.

In my case, suprisingly without SteamDeck=1 launcher still doesnt start and game goes on.

IIRC, booting the game once with this envar modifies something the installation files, meaning that even if removed, its effects will stay (until you verify the files).

New Season 2 Dropped and I got the ring_gfx timeout mesa driver crash again. RIP

After having ring timeouts for a while, i ended up getting a new desktop with a 9070 XT. Here are some things I did that helped greatly reduce my crashes:

• Undervolt and Set GPU Clock (this worked for me for a bit, but i found it better to add a ppfeaturemask)
• Update to the latest Mesa drivers
• Kernel Parameters: amdgpu.ppfeaturemask=0xfffd3fff split_lock_detect=off amdgpu.runpm=0
  Notes on split_lock_detect (and some other helpful items): https://forum.level1techs.com/t/9070-and-9070-xt-setup-notes-for-linux/227038

I was playing without launch options, but since the new update today (or yesterday) I need to put SteamDeck=1 %command% in order to start the game and able to play. Why?

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2797157730

I may have figured out the launcher not working; the version of Qt6 NetEase use for the Marvel Rivals Launcher is trying to call EnableNonClientDpiScaling() which is currently stubbed in Wine/Proton from what I gather. This results in the window not appearing. I found a similar bug report dated back to 2024 for a different app run via Wine (In this app's case, the window appears but is blank): https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/377

My guess is that the Launcher will work again once this function's implemented, even as a semi-stub.

UPDATE: I attempted my own semi-stub but the launcher window is still not appearing, the DPI scaling thing may be a red herring.

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2798761026

https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2798771309 I explained what I think is going on.

If you want to try the shader compilation change, this comment (https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2797157730) has details.

The 575.51.02 nvidia driver is out. Nvidia says "Fixed a bug that could cause Marvel Rivals to crash on startup or when loading levels." I wonder if this is the crash on startup or loading levels when nvidia reflex is enabled (as I am not aware of any other):

https://www.nvidia.com/en-us/drivers/details/243334/

Thanks for the reports everyone. The issue with Reflex is being tracked in NVIDIA bug 5048395. I will report back here when a driver has been shipped with a fix.

@esullivan-nvidia Does 575.51.02 include a fix? So far, I have played a few games without crashes.

The 575.51.02 nvidia driver is out. Nvidia says "Fixed a bug that could cause Marvel Rivals to crash on startup or when loading levels." I wonder if this is the crash on startup or loading levels when nvidia reflex is enabled (as I am not aware of any other):

https://www.nvidia.com/en-us/drivers/details/243334/

Easiest way to test this would be to first turn on NVIDIA Reflex then enter the menu where you can view each character's abilities' tutorial videos. Just open one and let it loop a couple of times and the bug should trigger if it isn't fixed.

The Reflex crash always seemed to be triggered in Marvel Rivals if an in-game video's final frame was displayed while Reflex was enabled. If the bug is fixed, this will be why it's written as being a startup crash and a loading crash as both involve a video displaying its final frame.

@esullivan-nvidia Does 575.51.02 include a fix? So far, I have played a few games without crashes.

Yes, that driver has the fix for the Reflex crash that is being discussed in this bug. Let me know if you run into any other issues and I will take another look.

Update: I tried -PSOCompileMode=1, and it fixed the GPU hangs? The new problem with massive stuttering on loading stuff is still a thing on -PSOCompileMode=0 though, but that's apparently not Intel-only; oh well!

Once I play a few more rounds, I'll see if I get a hang on anything, else? I guess the Intel Arc Saga is over!

Update: The Intel Arc Saga is over

For whatever reason, I got the frequent crashes back since yesterday (April 21, 2025).

After playing the entire time for over a month excessively (I have over 500 hours playtime now), where I had crashes only once per day or so, now I get crashes every game. Even when I reconnect, it crashes shortly after, maybe 2 minutes in or so. Its 100% unplayable at the moment and I take a break (probably not a bad idea at all).

Not sure why this suddenly happens again. I play with low settings, at 720p or 1080p with lower internal resolution. No FSR or anything else. Playing with Proton Experimental. Here my current system information:

$ cat ~/".local/share/Steam/steamapps/common/Proton - Experimental/version"
1743617450 experimental-9.0-20250402

$ vulkaninfo --summary | grep -m1 driverInfo
driverInfo         = Mesa 25.0.4-arch1.1

$ fastfetch -l none
OS: EndeavourOS x86_64
Kernel: Linux 6.14.3-arch1-1
Uptime: 13 hours, 10 mins
Packages: 1390 (pacman), 28 (flatpak)
Shell: bash 5.2.37
Display (AG271QG): 2560x1440 @ 120 Hz in 27" [External]
DE: KDE Plasma 6.3.4
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (24px)
Terminal: konsole 25.4.0
CPU: AMD Ryzen 7 7700X (16) @ 5.58 GHz
GPU 1: AMD Radeon RX 7600 [Discrete]
GPU 2: AMD Raphael [Integrated]
Memory: 4.08 GiB / 30.49 GiB (13%)
Swap: 30.67 MiB / 64.00 GiB (0%)

For whatever reason, I got the frequent crashes back since yesterday (April 21, 2025).

After playing the entire time for over a month excessively (I have over 500 hours playtime now), where I had crashes only once per day or so, now I get crashes every game. Even when I reconnect, it crashes shortly after, maybe 2 minutes in or so. Its 100% unplayable at the moment and I take a break (probably not a bad idea at all).

You could try deleting the compatdata folder for the game then trying it again, I had some luck with that for about 3 weeks, seems like every new update I had to do it, but I'm not sure if luck was involved, I got annoyed enough to stop playing though especially since Windows users are crashing even as well.

You could try deleting the compatdata folder for the game then trying it again

Here is what I tried:

• delete ".local/share/Steam/steamapps/common/Proton - Experimental" directory
• verify Marvel Rivals installation (which redownloads Proton Experimental) from Steam
• disable "Game Recording > Background Recording" for Marvel Rivals (which uses the GPU as well, maybe helps)
• disable "Controller > Steam Input for Marvel Rivals"
• disable "General > Enable the Steam Overlay while in-game" for Marvel Rivals
• update my operating system once again and restart

Aaaand... the game doesn't even show up anymore, but is shown as running.

Setting the "disable" settings from above list back to previous configuration doesn't change anything. Forcing Proton Experimental or Hotfix will has no effect. Using an older Kernel "Linux 6.12.23-1-lts" same issue. I can run Final Fantasy 7 Remake in Steam, so the system is working fine otherwise. Maybe the system update broke something?

Since the update, the launcher is broken. You can disable it by using
SteamDeck=1

On Mon, Apr 21, 2025, 10:52 AM Tuncay @.***> wrote:

You could try deleting the compatdata folder for the game then trying it
again

Here is what I tried:

• delete ".local/share/Steam/steamapps/common/Proton - Experimental"
  directory
• verify Marvel Rivals installation (which redownloads Proton
  Experimental) from Steam
• disable "Game Recording > Background Recording" for Marvel Rivals
  (which uses the GPU as well, maybe helps)
• disable "Controller > Steam Input for Marvel Rivals"
• disable "General > Enable the Steam Overlay while in-game" for
  Marvel Rivals
• update my operating system once again and restart

Aaaand... the game doesn't even show up anymore, but is shown as running.

Setting the "disable" settings from above list back to previous
configuration doesn't change anything. Forcing Proton Experimental or
Hotfix will has no effect. Using an older Kernel "Linux 6.12.23-1-lts" same
issue. I can run Final Fantasy 7 Remake in Steam, so the system is working
fine otherwise. Maybe the system update broke something?

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2818654630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EA2UMD5Z6GGZPA2TZL22UA2LAVCNFSM6AAAAABTGW7Z4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGY2TINRTGA
.
You are receiving this because you commented.Message ID:
@.***>
thingsiplay left a comment (ValveSoftware/Proton#8300)
https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2818654630

You could try deleting the compatdata folder for the game then trying it
again

Here is what I tried:

• delete ".local/share/Steam/steamapps/common/Proton - Experimental"
  directory
• verify Marvel Rivals installation (which redownloads Proton
  Experimental) from Steam
• disable "Game Recording > Background Recording" for Marvel Rivals
  (which uses the GPU as well, maybe helps)
• disable "Controller > Steam Input for Marvel Rivals"
• disable "General > Enable the Steam Overlay while in-game" for
  Marvel Rivals
• update my operating system once again and restart

Aaaand... the game doesn't even show up anymore, but is shown as running.

Setting the "disable" settings from above list back to previous
configuration doesn't change anything. Forcing Proton Experimental or
Hotfix will has no effect. Using an older Kernel "Linux 6.12.23-1-lts" same
issue. I can run Final Fantasy 7 Remake in Steam, so the system is working
fine otherwise. Maybe the system update broke something?

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

Launch parameter SteamDeck=1 does not help here (I used that option couple of weeks before). Game still does not show up. I also could play the game since and before the update too (verify data almost daily).

Do you have 'SteamDeck=1 %command%' as your launch parameter?

On Mon, Apr 21, 2025, 11:04 AM Tuncay @.***> wrote:

Launch parameter SteamDeck=1 does not help here (I used that option
couple of weeks before). Game still does not show up. I also could play the
game since and before the update too (verify data almost daily).

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2818692519,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EECDQLQY4K2YMXZRVD22UCIDAVCNFSM6AAAAABTGW7Z4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJYGY4TENJRHE
.
You are receiving this because you commented.Message ID:
@.***>
thingsiplay left a comment (ValveSoftware/Proton#8300)
https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2818692519

Launch parameter SteamDeck=1 does not help here (I used that option
couple of weeks before). Game still does not show up. I also could play the
game since and before the update too (verify data almost daily).

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

I'm sorry, my bad! Totally forgot the %command% part. Adding the launch parameter correctly runs the game. And with the changes I made previously, I could also finish one match. Again sorry and thank you. It seems to be working fine for now.

Since bleeding-edge-10.0 there is a bug that does not allow to start the game.

@Vladimir-A Also - are you using any launch options or another trick to bypass the launcher? If so, which one?

Hello @Vladimir-A, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

@alasky17, I have the same result with SteamDeck=1 and without it.

@kisak-valve, here is the result.
Steam Runtime Diagnostics
steam-2767030.log

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2843218529

I'm assuming this is a no given your gist doesn't show any of the ICD files for it but do you happen to have AMDVLK installed?

EDIT: Appears it's a mesa regression, I've been told this MR fixes your issue: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34774

If you're on Arch and recently updated your system, I'd suggest finding a way to downgrade mesa to whatever you had before and seeing if that works as a workaround for now.

If you're on Arch and recently updated your system, I'd suggest finding a way to downgrade mesa to whatever you had before and seeing if that works as a workaround for now.

Or would be using an older Kernel (LTS in example) help here? I cannot test this myself at the moment, because I deal with yet another system issue...

If you're on Arch and recently updated your system, I'd suggest finding a way to downgrade mesa to whatever you had before and seeing if that works as a workaround for now.

Or would be using an older Kernel (LTS in example) help here? I cannot test this myself at the moment, because I deal with yet another system issue...

Unfortunately no; the bug causing Rivals to crash is in the userspace driver aka. mesa itself.

Since bleeding-edge-10.0 there is a bug that does not allow to start the game.

Arc Linux with latest Mesa (25.0.5-2)
What I tested going in to the menu (haven't got time to play) :

• 9.0-4 = game runs but no video ?
• 10.0-1 = game runs
• experimental = assert failed
• hotfix = assert failed
• bleeding edge = assert failed
• GE-Proton9-27 = game runs

Could it be the Marvel Rivals fix that's mentioned in the experimental changelog ?
And it would be nice for someone with mesa git to confirm if experimental/bleeding edge work normally ?

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-2846955325

Same assert as what the other guy got?
Please post specs and/or a screenshot of the assert.

I just tested this and can confirm game runs and starts with "Proton 10.0-1 (beta)", but get the same assert loader.c error message when using "Proton Experimental".

Here's my error with proton experimental :

My system :
OS : Arch Linux
Kernel : Linux 6.14.4-2-cachyos
GPU : Radeon RX6600
Driver : Mesa 25.0.5-2

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

EDIT: Appears it's a mesa regression, I've been told this MR fixes your issue: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/34774

If you're on Arch and recently updated your system, I'd suggest finding a way to downgrade mesa to whatever you had before and seeing if that works as a workaround for now.

@froz3n @thingsiplay Proton 10 Experimental is getting "unlucky" and now hitting this mesa bug, as @FuzzyQuils correctly pointed out. I suggest either working around this by changing mesa versions or using a working Proton build until mesa is updated.

Has anyone found a working combination yet?
I've tried downgrading mesa step by step all the way to 24.3.4, but i get the same Issue.
And the only Proton Versions that seem to work on my system are Experimental and Hotfix.
With 10.0 and below it only says "running" but the game never actually boots.

OS: Garuda Soaring Broadwing (Arch Distro)
Kernel: x86_64 Linux 6.14.4-lqx1-1-1qx
CPU: Ryzen 5 3600X
GPU: Radeon RX 7900 XT
Driver: Mesa 25.0.5-1

With 10.0 and below it only says "running" but the game never actually boots.

Seems to be a problem with the launcher. Did you try the launch option SteamDeck=1 %command%? Recently I need this, otherwise game would not show up as you described. With this option the launcher will be skipped and you should able to play.

With 10.0 and below it only says "running" but the game never actually boots.

Seems to be a problem with the launcher. Did you try the launch option SteamDeck=1 %command%? Recently I need this, otherwise game would not show up as you described. With this option the launcher will be skipped and you should able to play.

Ye, this solved the Problem. Game now runs on Proton 10.0. with that command <3

Hey, just wanted to chime in on the change from Proton-Experimental to Proton 10.0-beta fixed it for me as well for the loader.c error (I ran Proton-Expermental with SteamDeck=1 and still encountered the error or not loading at all).

I also had an update for mesa today on arch in-between me playing and then being unable to over the course of hours. This is with an Intel i9-10800K + AMD RX9070XT.

Hello! (first timer so forgive any issues with formatting or really anything.)

I have been troubleshooting all day. I cannot get the game to launch past the TOS not to mention I have to recomp the shaders multiple times per switch of proton version. regardless of what one I choose I cannot get past the terms of service screen. The game will freeze and not allow me to select or agree to the terms of service. I have tried a lot of argument strings and what not but I cannot seem to get the game to get past the TOS. That's also if I can get the game to play nice with the shaders.

I hope I have given enough info below.

Specs/OS
Razer blade 14
Ryzen 9 5900hx 8 core (with radeon g)
RTX 3070 (Mobile)
POP!_OS 22.04 LTS x86_64
Kernal: 6.12.10-76061203-generic
DE: GNOME 42.9
Please and thanks for any help I have been trying at this all after noon.

EDIT: VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json LD_PRELOAD="" SteamDeck=1 PROTON_LOG=1 %command% -PSOCompileMode=1

steam-2767030.log

Just wanted to mention that with debian trixie the mesa-vulkan-drivers are delivered at v25, which are currently not fully supported by proton. Therefor I'm still running v24.3.4-3 to be able to play marvel rivals.

My 5700xt Just won't stop crashing. Seems like no issues in the practice mode, but when I join quick play I can maybe play just long enough to get a kill before the GPU hangs. I then have to restart sddm. I have tried with and without PSOCompileMode, SteamDeck=1 and without. Launcher has no problems. I have tried Proton 10 and 10GE-9.

Fedora 42, Kernel 6.14 and 6.15. 5700xt Mesa 24/25. Nothing has worked. Steam is installed from RPM Fusion so no flatpak. I can try to capture a log later.

https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-3066336591

Is Lumen GI turned on? Try turning it off as that was what caused hangs on my 5700XT when I still used one. Same goes for Lumen Reflections but from memory it was the GI setting that did it. (You usually don’t want it on anyway if you’re wanting to take the game seriously, as it eats your framerate)

Additionally, if you frequently hang at idle or in other games randomly as well, this may indicate your 5700XT’s firmware has the common fault where lower VRAM P-states had too low a voltage to be stable. My previous 5700XT had this issue until I updated its vBIOS, it stopped hanging in general after that.

@FuzzyQuils Thanks for the response. Lumen was turned on. I'm not sure I recall this the being an issue in other games, but that is interesting. I will test with it disabled.

As for other gpu hangs. It never happens at idle. It typically seems related to hardware acceleration in other applications. For example, some games don't play nice if I have a YouTube video open. Even still that is extremely rare, and seems to get patched out in Mesa. After substantial Mesa updates, I can never seem to replicate it on the same game. I would also have this exact problem even on other AMD cards on Windows (HD 7850, 270x). I would like to look into the firmware tho, I have a Gigabyte Gaming OC 5700xt.

@DeathTBO Couldn't get the game to hang on my rdna4 after a couple of hours on low and high preset each. I remember the game used to have crashing issues that seem to have gotten ironed out over time, but I recall an issue that was apparently rdna1 specific, and it was that the spider island maps were likely to make those cards hang. Do you remember if you were hanging in those specific maps? In game mode, there's a "custom game" option where you can choose any map and then fill it with bots so you don't have to worry about random maps being selected.

I can't help you with the vbios update but make sure to check your card's revision, as there's a rev 1.0 with a bios update, and a rev 2.0 that has no update available (presumably, it already has it installed from the factory).

@FuzzyQuils @simifor Well I turned off Lumen/GI and SSR. I started a custom match with bots on Empire of Eternal Night Central Park. I still get the GPU hang. Happened maybe a few minutes into the match, fought some bots for a little before it happened.

I had MangoHUD up and saw I was below 6gb of VRAM, nothing unusual on temps/clocks. This the only game that hangs like this. I'm not sure how to check the revision number, without maybe opening up the case and working around the cooler. I bought it in late 2020.

@DeathTBO There are two settings I know of that can cause GPU hangs on RDNA1. Try disabling Lumen GI as well as setting effects detail to low and see if that helps.

I have been having two issues in the past few weeks on Marvel Rivals:

1. The game will occasionally freeze, about every 1 to 2 hours. 1 out of 5 times, it will unfreeze after about 10 seconds. Other times, it stays hung.
2. Stutter often occurs. The game will get into a state where it will hang for 1 second every 3 to 5 seconds. It seems to be related to alt tabbing.

I am using KDE Plasma 6.4.0. I have tried using nvidia driver versions 575.64.05 and 580.76.05. The first issue has not occurred since switching to 580.76.05, but I have not played enough to know if it is fixed. I am using a Nvidia RTX PRO 6000 Blackwell graphics card with a Ryzen 9 5950X.

Has anyone tried the latest Proton Experimental ? Seems I can't open the game with it (as of 08/11/2025). Proton 10 beta works fine.
EDIT : Added gist HERE and proton log steam-2767030.log as per @kisak-valve request.

It appears the game has completely broken following the Nov 6 update of Marvel Rivals. When attempting to launch the game via Proton Experimental on a Steam Deck OLED, it fails to start and immediately returns to Steam. Here's a log from my SD OLED (I've additionally confirmed the same behaviour on my desktop Arch as well)

steam-2767030.log

It appears the game has completely broken following the Nov 6 update of Marvel Rivals. When attempting to launch the game via Proton Experimental on a Steam Deck OLED, it fails to start and immediately returns to Steam. Here's a log from my SD OLED (I've additionally confirmed the same behaviour on my desktop Arch as well)

steam-2767030.log

For me game works fine (besides the crashes that happen on all Proton versions for me) since and before the update. But I play with Proton 10.02-2 (beta).

For me game works fine (besides the crashes that happen on all Proton versions for me) since and before the update. But I play with Proton 10.02-2 (beta).

Yes, the issue explicitly occurs with Experimental. Proton Hotfix also works. It still worth noting that Experimental changes will roll down into your working Proton 10 branch eventually, so we want to pick up what's causing the issue before it does.

@sh-jus @thingsiplay This crash should be fixed in expeirmental-bleeding-edge (beta branch of Proton - Experimental). Please let me know if you are still experiencing a failure or getting kicked from the game or anything like that :)

I was able to launch the game successfully on Experimental (bleeding-edge) and test a few matches and it's working as expected again. Thanks for being so quick on fixing this @alasky17 !

@CodeRulerNo1 It's known to not work on base experimental currently. For the time being you need to use bleeding edge https://github.com/ValveSoftware/Proton/wiki/Proton-Versions#proton-bleeding-edge

@sh-jus @thingsiplay This crash should be fixed in expeirmental-bleeding-edge (beta branch of Proton - Experimental). Please let me know if you are still experiencing a failure or getting kicked from the game or anything like that :)

Sorry for late reply. The problem with "Experimental" is, that the game does not even launch. I am currently testing the "Experimental - Bleeding Edge" version and game starts. Can't say about stability. In my experience, game is unstable with all Proton versions. I never get kicked out of game, but it crashes often. Need to test the Bleeding Edge longer for that.

@thingsiplay you';d have to give more information about your setup. hardware, drivers, game settings, frequency of the crashing or if it only happens in certain situations (specific maps and whatnot)

I'm having the same issues - cannot launch the game with Proton Experimental, but I can with Proton 9 and Proton Hotfix. I'm also experiencing crashes, although anecdotally it feels like Bleeding Edge crashes less than Hotfix, which itself seems to crash less than Proton 9. Most of the time it has crashed to the Unreal Engine "report" window, but recently it's just been freezing and eventually closing, with one instance causing a full system freeze.

steam-2767030.log.tar.gz

runtime.txt

I was suggested to use GE-Proton and its working for me.

I've switched to using GE-Proton10-25, and while it was promising at first, I just had another crash (well, more like a "freeze" in which I had to forcefully shut the game down). Will enable logging again to see if I can catch another instance of it crashing.

EDIT: Unfortunately still crashing every so often, seemingly at random - I'm worried it might be something wrong with my system, is anyone else also experiencing more frequent crashing? steam-2767030.log.tar.gz

I was suggested to use GE-Proton and its working for me.

Unrelated to your post I tried this as I was scrolling this thread before getting to the bottom. Works fine for me too, actually it's the only way after trying a bunch of things to get it going. In the end it was simply using GE-Proton10-25 with no other tweaks and everything seems to be working great. AMD CPU Nvidia GPU.

I'm having the same issues - cannot launch the game with Proton Experimental, but I can with Proton 9 and Proton Hotfix. I'm also experiencing crashes, although anecdotally it feels like Bleeding Edge crashes less than Hotfix, which itself seems to crash less than Proton 9. Most of the time it has crashed to the Unreal Engine "report" window, but recently it's just been freezing and eventually closing, with one instance causing a full system freeze.

steam-2767030.log.tar.gz

runtime.txt

I've been experiencing random crashes as well. Mine and @drwhut's log both have this:

[0000000000000ae8:] EXCEPTION handling: System.ComponentModel.Win32Exception: Invalid window handle.
 
[0000000000000118:] EXCEPTION handling: System.ComponentModel.Win32Exception: Invalid window handle.

[0000000000000118:] EXCEPTION handling: System.ComponentModel.Win32Exception: Invalid window handle.

@IsaacClank if you're generating logs, then it's always good to upload them as well as sharing as much information about your setup as possible. Hardware, drivers, game settings, frequency, etc.

Leaving this here in case anyone else happens to stumble across the same issue.

On season 5 release I started getting stuttering during gameplay that would occur even when nothing was happening in the game, i.e. walking out of spawn. After comparing logs between different proton versions and watching a log during gameplay over several matches I noticed this line being printed multiple times in quick succession during the stutters.
4377.139:095c:0960:fixme:netsh:wmain stub: L"netsh" L"advfirewall" L"firewall" L"show" L"rule" L"name=Allow ICMPv4" L"dir=out"

After renaming netsh.exe under $WINEPREFIX/drive_c/windows/{system32,syswow64} and $PROTONPATH/files/wine/{i386-windows,x86_64-windows} the stuttering has stopped. I believe what is happening is the game is occasionally calling netsh with CreateProcessInternalW in a small loop with seemingly no delay thus it spawns an equal amount of consoles for each call made.

For reference I tried Proton 10.0, experimental, bleeding edge and GE-Proton10-25. I tried a different window manager in case it was an issue specific to sway/tiling wms. I also tried using xwayland vs the wine wayland driver. All still had the issue until I renamed the netsh executable.

After renaming netsh.exe under $WINEPREFIX/drive_c/windows/{system32,syswow64} and $PROTONPATH/files/wine/{i386-windows,x86_64-windows} the stuttering has stopped. I believe what is happening is the game is occasionally calling netsh with CreateProcessInternalW in a small loop with seemingly no delay thus it spawns an equal amount of consoles for each call made.

Can you elaborate on the "$PROTONPATH" location? I've dealt with the compatdata folders a lot but never had a need to go into whatever that other path you're talking about is.

Can you elaborate on the "$PROTONPATH" location? I've dealt with the compatdata folders a lot but never had a need to go into whatever that other path you're talking about is.

The path to the specific proton version you are using. For experimental would be something like this $HOME/.local/share/Steam/steamapps/common/Proton - Experimental/

I'm not sure if it is necessary to modify those ones, I just did so under the assumption wine/proton might try replace them.

@idlyby doesn't look like this issue happens on my system. Neither the random slowdowns nor any mention of netsh, so I think something in your network setup might be a factor here.

Change your launch parameter to the following PROTON_LOG=+winsock,+iphlpapi,+nsi,+hnetcfg,+exec,+process %command%, compress and upload the resulting log, it might provide some relevant information.

@simifor swapped back those stubs so the stuttering would be present and played one quick vs AI match. on a cursory glance I'm noticing icmp echos to a single server that starts early and repeats throughout runtime, perhaps related to the launcher or the crash reporter that launches alongside the game? I'm not sure if this is relevant though. I did try pinging/tracerouting the server and was unable to get it to respond from either my pc or router.

EDIT: I should mention apart from the kernel param net.ifnames=0 I have made no changes to my local network and router configs, they are both stock standard dhcp.

steam-2767030.log.tar.gz

Small suggestion for anyone that may find it useful. Removing OBS_VKCAPTURE=1 resolved my issue.

@idlyby Ideally logs should be grabbed with stock proton. Leaving that aside, what happens if you try to manually ping 35.240.187.202 and 34.120.31.123? There's also a nonzero chance the epic build of the game might behave slightly different.

@simifor noted, 35.240.187.202 does not respond whilst the other address does.

My issue is resolved with the latest patch, no mentions of ICMP in logs and no stutters with stock proton. I'm guessing an outdated address was in use for diagnostics/heartbeat server in the SEA/OCE region.

Does anyone else have their PC internet down when trying to play the game ? Seems to be only my PC ( wired ) as my phone is okay. I need to restart my router to get back internet connection. Did not happen before the update, so I think this is new.
I'm on Arch Linux with Proton Experimental.

@froz3n no issues on my end. Does your internet go down for every program, or just this game? how often does it happen? have you tried connecting to a different server (assuming only this game's affected)?

@simifor thanks for confirming. I found the issue. The game triggers DoS protection in my router somehow and blocked my device. Dunno if disabling that is okay but for now I think I'll do that. I use TP-Link Archer A6 v3 router

EDIT : just installed openwrt on the router and everything seems fine for now

The crashes comeback sometimes with a Vulkan update on the system. Crashes at least 1 or more times per match.

My usual "fix" is a bit weird, but it helps. Go into your PCs Bios/UEFI and change the DRAM frequency one level down or up. It does not matter what the state before was, a change is all that is needed. In example "Auto" defaults to 4800 Mhz on my system. I change it to manual 4600. When the crashes start again, I change it back to "Auto". It makes no sense to me, but it works.

This game's launcher nearly crashed my entire PC just now. Once in game it runs fine.

System:

• Ryzen 7 7800x3D
• 2x16GB Ram
• RTX 4070 ti
• Nvidia Drivers 590
• Linux Mint 22.3
• Kernel 6.17

for players with same error on an old gpu's such as radeon r9 290x\390 - game will run with VKD3D_FEATURE_LEVEL=12_0 %command% in the launch options, proton experimental. (just skip pop-up notices about outdated os and driver -> confirm-continue and launch).

I have an R9 290 and I just used the command above but forced marvel rivals to use proton 10.0 instead of proton experimental and it works

Hello @Krypokt, it might be interesting to ponder a Proton log of that. With Proton Experimental, please set the game's launch options to PROTON_LOG=1 VKD3D_FEATURE_LEVEL=12_0 %command% and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

I can't run the game on Arch - it launches, but I get the "The anti-cheat is currently inactive." error every time after which the game quits.

I have tried just about everything I could think of:

• Validating the files
• Reinstalling
• Switching Proton versions (9, 10, Hotfix, Experimental, bleeding edge)
• Trying to launch the game from a Proton version that executes the launcher and setting it to hang around in the background while launching the game
• Setting the SteamDeck=1 variable
• Switching to flatpak version of Steam
• regenerating the prefix
• Turning off my software firewall as well as router firewall
• Turning off adblock on my router
• Turning off any daemons that could interfere with applications (lact, etc)

Absolutely nothing, still can't launch the game. I remember this happening already about a year ago, but I haven't been in a mood to troubleshoot, so I just uninstalled the game and didn't touch it since. No idea what could be the issue and I'm honestly out of ideas.

I've attached a log file from the flatpak version of Steam, just so I can be sure there's no weirdness going on with my system libs or anything.

steam-2767030.log

Replying to https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-4193778862

What gpu?

What gpu?

RX6700

What gpu?

RX6700
Well I don’t know to help with that GPU but with my R9 290 I just used the launch option that makes the game use DX 12_0 and proton 10 but with that GPU I don’t know so I can’t help sorry
But I will try with my RTX 3060-ti but in the meantime you can try uninstalling and reinstalling the game

Does anyone else have the issue where after the recent update, I have to manually kill all processes to launch the game again if I've already launched since I started my PC? Unsure if this is just specific to me or not.

Do you have Discord open? I actually found that issue was due to the most recent Discord update eating up all the X11 window connections (240+ out of 256) and was preventing pretty much anything else from launching on my PC until I closed Discord and suddenly everything worked again. I already submitted a bug to Discord about it.

Anyone else crashing on the latest patch ? Got UE5 crash report when launching the game.

EDIT: added log
steam-2767030.log

The game is immediately crashing to desktop just after the launcher as of the new update today (Build ID 24143200) on both Proton Hotfix and Experimental (Bleeding Edge), this is also being reported by multiple people on socials as well.

steam-2767030.log

Someone is reporting that they can get the newest patch to work on Proton 9, just not any proton that's newer. If anyone else wants to try that

Someone is reporting that they can get the newest patch to work on Proton 9, just not any proton that's newer. If anyone else wants to try that

It works but I need to remove SteamDeck=1 (and a fresh prefix but don't know if that has any effect).

EDIT :
Someone on cachy-proton said proton experimental (bleeding-edge?) already fixed this

It works but I need to remove SteamDeck=1 (and a fresh prefix but don't know if that has any effect).

i confirm, it works with proton 9, no new prefix needed.

but it sill might crash after a while

Should be working now in Proton Hotfix and Experimental (Bleeding Edge), patches have been made to Valves wine to add needed stubs for ADL2 Overdrive (thanks Paul).

Proton Hotfix launches the game successfully as of now, but the demonstration videos tied to each hero's ability tab in the Heroes page don't seem to play at all (total black screen).

Proton Hotfix launches the game successfully as of now, but the demonstration videos tied to each hero's ability tab in the Heroes page don't seem to play at all (total black screen).

that's because normal proton doesn't have video encoders, that's a ge-proton thing.

@EthanKairos those videos are h264, and those in particular need to be unlocked once, this can be done by running this once in your terminal steam steam://unlockh264/ and then rerun the game

@EthanKairos those videos are h264, and those in particular need to be unlocked once, this can be done by running this once in your terminal steam steam://unlockh264/ and then rerun the game

Good shout, this worked perfectly.

https://github.com/ValveSoftware/Proton/issues/8300#issuecomment-5013708989

NVIDIA 550

Your NVIDIA driver is ancient; try upgrading to the latest 595. (595.84 at the time of writing)

EDIT August 2026: I just rechecked your system information and your version of LMDE and your Linux kernel is severely out of date as well as your NVIDIA driver, you'll want to upgrade your distro in it's entirety in order to have the required NVIDIA driver version.

Ever since the crashing fix that happened around a week ago the game runs fine now but FSR4 no longer gets enabled. It was previously working with Proton Experimental and Proton-CachyOS but neither work anymore now for FSR4

Game: Marvel Rivals (AppID: 2767030)
Proton Versions Tested: Proton 11.0-1, Proton 11.0-2 RC

System Info:
OS: Bazzite Linux (Nvidia build)
Launch Options: PROTON_LOG=1 %command% (also tested with SteamDeck=1 %command%)

Symptoms:
The Marvel Rivals launcher opens, but clicking play fails to launch the game. The issue exists on both Proton 11.0-1 and the 11.0-2 Release Candidate beta 3rd August.

Log:

steam-2767030.log

@Dale-Pogona The game is starting normally on my amd desktop and nvidia laptop, did the game work in the past? does clearing the game's prefix help? Have you tried launching steam from the terminal with steam? bazzite makes changes to steam when launching from the system's shortcut so it's better to avoid them to see if it makes a difference.

@simifor Yes the game did work in the past and i tested launching Steam directly from the terminal, after clearing the game's prefix, but the behavior is still the same the launcher opens up, but clicking play fails to launch the game.