protonscr

[First Descendant - Menu Screens Crash bug]

vkd3dclosed
HansKristian-Work/vkd3d-proton#2610 · opened 2025-09-09 by reaperx7 · updated 2026-09-16 · 14 comments · github
Rreaperx7 2025-09-09 github

When entering the Customization Screens for the character avatars, pets, and vehicles, the game will generate a crash.

Image

Software information

First Descendant - Default (Auto Medium) settings

System information

  • GPU: Radeon RX 5700 XT
  • Driver: amdvlk Q2 2025
  • Wine version: Proton 10.0-2 beta
  • VKD3D-Proton version: n/a

Log files

[Unable to upload log file for unknown reason, but link to shared log is provided.]

(https://drive.google.com/file/d/1ASpOLUk7Zts7utLhzRM2gQc-VzuHaTEs/view?usp=drive_link)

HHansKristian-Work maintainer 2025-09-11 github

Try using RADV. amdvlk usually fails on DXVK/vkd3d-proton.

Rreaperx7 2025-09-11 github

I did that also, and I also attempted vulkan-amdgpu-pro to cover all bases. The same error keeps popping up unfortunately.

HHansKristian-Work maintainer 2025-09-11 github

When entering the Customization Screens for the character avatars, pets, and vehicles

How many hours do you need to reach the point where you can do that?

Rreaperx7 2025-09-11 github

Immediately if I even try. As soon as I try entering the menu, error.

HHansKristian-Work maintainer 2025-09-11 github

I mean, can a fresh file reproduce this? No need to play for hours to unlock that feature?

Rreaperx7 2025-09-11 github

Yes, it should be able to. I also tried various Proton installs from Experimental, Hotfix, 10.0-2 Beta, ProtonGE 10 as well. Same results. Same error.

HHansKristian-Work maintainer 2025-09-11 github

Can you try mkdir /tmp/shaders, then VKD3D_SHADER_DEBUG=info VKD3D_DEBUG=info VKD3D_SHADER_DUMP_PATH=/tmp/shaders %command in Steam? It should be able to say which shader is causing the crash.

Rreaperx7 2025-09-11 github

I will try later when I'm home. Thank you.

HHansKristian-Work maintainer 2025-09-11 github

Tried 9070xt on RADV 25.2.2 and I couldn't reproduce. Not a great start ...

When you do the run, make sure to run on RADV to rule out any obvious shader compiler bugs in amdvlk.

Rreaperx7 2025-09-11 github

Will do. I'm on a 5700XT also.

Rrunar-work 2025-09-17 github

I seem to be unable to reproduce this on my end as well. RX 5700 XT, Proton Experimental (also with the same vkd3d-proton build as in the log), 6.16.4-arch1-1 and 6.12.47-1-lts, AMDVLK 2025.Q2.1 and Mesa 25.2.2, with and without shader pre-caching enabled, medium preset.

Rreaperx7 2025-09-17 github

I seem to be unable to reproduce this on my end as well. RX 5700 XT, Proton Experimental (also with the same vkd3d-proton build as in the log), 6.16.4-arch1-1 and 6.12.47-1-lts, AMDVLK 2025.Q2.1 and Mesa 25.2.2, with and without shader pre-caching enabled, medium preset.

I'll try flushing the shader cache later when I'm awake. Problem is often when I have a crash, the whole shader stack is rebuilt which takes like 2-3 minutes. So maybe something else is at play here.

BBlisto91 maintainer 2026-09-16 github

@reaperx7 Have anything changed in regards to this issue?

Rreaperx7 2026-09-16 github

Yes, it seems to have stabilized since the last few updates, but unfortunately, due to how Easy Anticheat is treated, we are forced to use Proton-GE rather than the normal Proton releases, however, yes it does work as intended finally. Thank you.

I'm uncertain if it might have been amdvlk as it was deprecated by AMD in favor of Mesa-radv though. I'll keep an eye out and report anything else if and when something pops up.

Proton versions

Launch options