Marvel Rivals (2767030)

[EnnuiL]

Compatibility Report

• Name of the game with compatibility issues: Marvel Rivals
• Steam AppID of the game: 2767030

System Information

• GPU: Intel Arc A380
• Video driver version: Mesa 24.3.1
• Kernel version: 6.12.3-arch1-1
• Link to full system information report as Gist: The gist
• Proton version: Experimental

I confirm:

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

Proton log: steam-2767030.log

Symptoms

When attempting to launch Marvel Rivals through its launcher, the game will spit this dialog out and then it will return to the launcher:

Reproduction

1. Have a system with an Intel Arc GPU (?)
2. Start the launcher on Steam
3. Dismiss the outdated OS and outdated GPU drivers warning
4. Click on "Launch"

[Jonathing]

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.

[FuzzyQuils]

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.

[ghost]

this is not an issue with proton

image

[kisak-valve]

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.

[EnnuiL]

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

[Jonathing]

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.

[EnnuiL]

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

[WMan22]

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.

[SpiritWinD86]

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).

[EnnuiL]

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!

[EnnuiL]

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

[Eris7090]

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

[rejedai]

Have no media in game, all cutscenes black on rx6700xt

[Hondawyyy]

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

[hjpaul7]

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

[ryao]

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.

[WMan22]

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.

[gquinche]

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.

[gab462]

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!

[bohanubis]

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

[PadTrick]

Replying to #8300 (comment)

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 ?

[yofukashino]

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 %

[EnnuiL]

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

[bohanubis]

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

[ezequielramos]

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.

[bohanubis]

no was never able

[PadTrick]

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.

[bohanubis]

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

[FuzzyQuils]

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)

[EnnuiL]

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