I haven't been able to reproduce this on RX 9070 with Mesa 26.1.4 and 26.1.5, Proton GE 10-34, Proton 9, 10, 11 and Experimental (plain and bleeding-edge), kernel 7.1.3 and 7.1.5, so it may not be a general RDNA4 issue. I also didn't run into any launch issues with these Proton versions. Do you have Proton logs from those launch failures as well?
The reason the -dx11 option makes no difference is that the game only launches with DX12. You can use MangoHud to show which API the game is launching with if you're ever in doubt.
Good to know about the dx11 option. I don't have the original logs, but I reproduced the issue on proton 9, 10, and 11. On 10/11, the game seemed to load but at a lower resolution. Trying to adjust either the resolution or the refresh rate instantly crashes the game, though it seemed to work at a lower resolution, at least for a few minutes.
Happy to help as best I can on this. Doing my best to troubleshoot this on my own, but I'm not as savvy with computer stuff as I would like. It's especially frustrating as this is the only game giving me this issue, so I'm fairly certain it's not a hardware error, though I could be wrong.
Proton11-steam-1446780.log
Proton10-steam-1446780.log
Proton9-steam-1446780.log
proton 10.0-4x1 2026-07proton 11.1x1 2026-07VKD3D_CONFIG=retain_descriptor_heapsx1 2026-07
Software information
Monster Hunter Rise. Crash occurs shortly after entering gameplay/menu. Reproduced with default settings and with -dx11.
System information
GPU: AMD Radeon RX 9070 XT
Driver: RADV, Mesa 26.1.4-arch1.1
Kernel: 7.1.3-arch1-2
Proton versions tested: Proton 10.0-4 (official), GE-Proton 10-34, Steam default — all hang identically. GE-Proton 11.1 and Proton-GE Latest fail to launch (separate issue).
VKD3D-Proton: build d686616d170f510
Log files - Attached
steam-1446780.log
mhr_gpu_hang_1783752733.bin.gz
Monster Hunter Rise reliably triggers a GPU hang shortly after entering the title menu. dmesg shows a repeated ring gfx_0.0.0 timeout tied to the vkd3d_queue thread; amdgpu recovers via ring reset, but the game becomes unresponsive and requires restart.
dmesg signature (PIDs vary run to run; pattern is consistent):
amdgpu 0000:09:00.0: ring gfx_0.0.0 timeout, signaled seq=1802560, emitted seq=1802562
amdgpu 0000:09:00.0: Process MonsterHunterRi pid 17870 thread vkd3d_queue pid 17928
amdgpu 0000:09:00.0: Starting gfx_0.0.0 ring reset
amdgpu 0000:09:00.0: Ring gfx_0.0.0 reset succeeded
Ruled out:
vkd3d-proton already applies shader quirks for MonsterHunterRise.exe ("Detected game MonsterHunterRise.exe, adding shader quirks for specific shaders"), but this doesn't prevent the hang. Same game/content runs fine on Steam Deck (RDNA2); reliably hangs on desktop RX 9070 XT (RDNA4).