Metal Fatigue (888040)

[Littletiger]

Compatibility Report

• Name of the game with compatibility issues: Metal Fatigue
• Steam AppID of the game: 888040

System Information

• GPU: RTX 5090
• Video driver version: Nvidia 590.48.01
• Kernel version: 6.18.2
• Link to full system information report as Gist:
• Proton version: Experimental

I confirm:

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

Experimental-steam-888040.log

4.11-steam-888040.log

Symptoms

The game does not run on newer proton versions, a window pops up for a split second then nothing, game has to be forced stopped via Steam.

Last working proton version is 4.11-13

Reproduction

Run the game

[kisak-valve]

Hello @Littletiger, DXVK in Proton 5.0 grew to support D3D9, but I don't see DXVK initializing in your Proton Experimental log. How does the game behave if you set the game's launch options to PROTON_USE_WINED3D=1 %command%?

I suspect the issue you're seeing is being shown at https://gist.github.com/Littletiger/e0486a5f461c0c61930a14c1a311f20c#file-gistfile1-txt-L7256-L7296 in your extended diagnostics info. The 32 bit EGL/OpenGL render path is not healthy and is being forced to fallback to llvmpipe instead of showing the NVIDIA GPU in your system.

[Littletiger]

Thanks for taking a look @kisak-valve, I have tried using PROTON_USE_WINED3D=1 however the same thing occurs, I have attached another log below.

I'm not sure why it's showing that in the diagnostics, I've not been able to find anything missing and glxgears32 does run using the Nvidia card.

I have also tested this on my Steam Deck running the latest Beta OS and the same issue occurs with or without the env variable.

steam-888040.log

[pquerner]

The game is using glide graphics for me (as per ingame settings menu), not directx. Game resolution can be fixed with address patching of the glider dll.

No videos seem to be working.

[kisak-valve]

I wouldn't expect glxgears to exercise EGL, since it's using GLX instead and the glx/gl section is healthy. eglinfo32 might be more interesting, but it''s still based on guesswork on my part.