I'm having this issue too, but mine also hangs when SSGI is used, or Global Illumination is turned off. Seems to cause a full GPU crash in the end. Still occurs with Mesa 25.0.4 and amdvlk 2025-Q2.

How long does it take for it to hang? There has been a known issue with GPU hangs in this game on AMD GPUs which can happen randomly every few hours or so, so that's very difficult to debug. If it's something that happens more reliably, feel free to upload a Proton log with more info and I'll see if I can reproduce it.

Usually within a minute or so after getting into a match, maybe longer but it never lasts long enough to finish a match. I'll try it again tomorrow or sometime soon and generate logs.

Alright tried it again, it still causes a gpu crash. Ran it with PROTON_LOG=1 to get this: https://drive.google.com/file/d/1L_sV7UV-E6bPdAAnp_C2oQ5_UTBwIAdr/view?usp=drive_link. I also have a log of journalctl output from when I started steam: https://drive.google.com/file/d/1GeaOqBv61tDTLt-yFsOSBT2et-n-5PJ_/view?usp=drive_link. I don't know if there's any other logs I should try and get.

Those are good, thank you. I can reproduce this, and it seems to be very similar to the original hang I described above, so it doesn't want to give up much info, unfortunately. It hangs in a generic vertex shader this time, so the shader name wasn't any help either.

It does seem like setting "effects detail" to low helps, at least when I've tried it (the remaining settings I had were preset high with SSGI and FSR3 quality). I finished a few matches with that and always got a hang fairly quickly when I set it to high, so it could be worth a try in the meantime.

Yeah tried it again, and sure enough I can get through a full game without crashing with the effects quality set to low. Thanks for reporting!

Seems like this issue still persist in 2026, but as @runar-work said, setting Effects=low and SSGI prevents the crashes.

Not sure if it's a vkd3d specific issue though, doesn't seem to happen on other hardware either.

For me it seems to crash no matter what unless the FPS is capped to 60. I've been playing on PS5, waiting till the 5700XT works again.

@Rippeee What graphics settings did you use apart from the FPS cap?

I checked with RX 5700 XT on latest Mesa and Proton Experimental with bleeding-edge vkd3d-proton yesterday on high preset, but unfortunately it still hangs in a way that doesn't provide much info about what's actually going on (i.e. still no active waves).

@runar-work I had everything low, but it doesn't seem to matter. I can even set the antialiasing to Native or Ultra Quality as long as the FPS is capped at 60. It won't crash, but I can see that it's truly 60 fps and laggy since the monitor is 165 Hz. I can play uncapped, and with some luck I can maybe squeeze out 1-2 games without crashing. But if I'm at ranked, I can't gamble with it, and I set it to 60fps. It's kind of ironic that the card that is listed as their RECOMMENDED hardware does not work.

@runar-work Also, I have pretty hardcore overclocks on, way more than standard XMP and Precision Boost. I have min-maxed RAM timings and CPU clocks, but I have benchmarked them, and I know they are 1000% stable, and the same clocks worked perfectly fine in seasons 0-6, but just for testing, I loaded default BIOS settings, and so far I haven't crashed in a few 18v18 games. Need more testing, but so far it seems like Marvel didn't like the maxed-out overclocks. I try a few more games and then try to pinpoint if it is a CPU or RAM issue. I will let you know once I have a bigger pool sample.

@runar-work Okay, I have some data now, and so far it seems that I have found the solution. I played 10 matches, 5x 18v18 and then 5x quick plays, and I didn't get any crashes or hiccups. I don't know if this will apply to other people, but at least for me, it seemed like the root cause of the crashing was the RAM overclocks. I loaded in my saved "OC BIOS" settings. I kept the all-core CPU overclocks and overclocked RAM's primary, secondary, and tertiary timings. The only thing that I changed in RAM timings was TRFC. TRFC is the timing that has the absolute most impact on the RAM. I loosened it from 560 to 576 (default value from DOCP/XMP is 630). People have said that disabling above 4G decoding Resizable BAR has helped, but in my case, I kept it on. I haven't tested high settings since the optimal settings are low anyways, for example, Sypeh (Rank 1) settings are literally everything, either Off or low, and super resolution mode is set to Ultra performance. I keep it at Performance because for my eyes the Ultra one looks too blurry. I would assume high settings work fine as long as effect details are set to low, and avoid Lumen, a lot of people have said that that's the primary reason for crashing. My avg FPS was very healthy, around 200-240. So if you are having crashes, first try to increase your TRFC a little bit. In general, it's good to be at a value that can be divided by 8 or 16. And if loosening TRFC won't help, then you could try to disable XMP and just use the loose stock timings. Also, if the XMP/DOCP values are crashing, you could just copy and paste those values and set it manually so it's not using XMP/DOCP profiles. The values are the same, but they are set MANUALLY.

My specs are a Ryzen 9 3900x, 32GB (4 x 8GB) DDR4 RAM, and a Sapphire Nitro+ 5700XT. Testing was done on Linux Mint 22.3 (Cachy and Windows had the same crashes, but I assume this would apply to them too). And my Proton was "Proton-cachyos-10.0-20260330-slr-x86_64_v3" (downloaded with ProtonUP-Qt). I would assume Proton experimental works too, I'm just used to using Cachy's Protons. Also, I did not use ANY launch options, but I guess you could add gamemode, etc., etc.

GOOD LUCK! And I hope this could help someone who is struggling with this game.