Debian SID : After update, Monster Hunter World : Iceborn gives : "ERR23: Direct3D 12 supported device not found"

[NewNova88]

Compatibility Report

• Name of the game with compatibility issues: Monster Hunter World: Iceborne
• Steam AppID of the game: 582010

System Information

• GPU: NVIDIA RTX 3060 12GB
• Video driver version: NVIDIA 570.123.10
• Kernel version: 6.12.25
• Link to full system information report as Gist:
• Proton version: Experimental, Hotfix, 9.0-4 and 7.0-6

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.

steam-582010.log

Symptoms

I use the DirectX 12 option enabled for years since I have the game on Debian, and had no problem. The game ran fine. But I recently updated my distro after I was offline and now the game spits out "ERR23: Direct3D 12 supported device not found".

I updated, downgraded, reinstalled NVIDIA drivers but no luck. I used a bunch of different versions of Proton, and even Proton-GE, but no luck. I changed multiple options and tried to launch without options, but no luck again.

Though with tinkering it, it sometimes work, though RARELY, and after lots of uninstalling/downgrading/upgrading and reboots.

Sometimes, when trying to run the game, it allocates the CPU RAM infinitely, so I have to kill the process through the monitor to avoid complete system crash.

Changing the game option to disable DirectX 12 via the ini files worked, but I want to understand what happened, and where does it come from.

Any help is appreciated !

PS : I never posted an issue statement in GitHub, so if I made mistake, please correct me. I also linked the log file of the game, but if there was a problem, please tell me so I post it again.

EDIT : I just tried Proton 8.0-5 as I got the clue from this : #8651
And it worked, multiple time, but I had to remove the options (especially gamemoderun) since it did the infinite RAM allocation again.

[kisak-valve]

Hello @NewNova88, we're using one issue report per unofficially supported game title, so I've gone ahead and transferred this issue report to #175 (comment).