Bisected to 97e4a2a822b81714ffd447dc4cf50f6193b1e65f

@HansKristian-Work do you have a saved game for the area where you say there's massive CPU overhead? I just finished the intro and I don't see any issues without that workaround so far.

@adolfintel some scenes where there is a lot of text rendered. Either due to a bunch of items/other gameplay stuff, or during the credits scene, which drops to like 20 fps without no_upload_hvv if i recall correctly. I don't remember getting any hangs though while using no_upload_hvv manually a while back.

Oh yeah it does slow down a bit on the delivery screen where there's a lot of text.

Either way, I can replicate this 100% of the time with no_upload_hvv, at least on a 9070xt, I can't even get to the first cave without it crashing the whole computer at least once.

Any ideas on how I can debug it further?

If I launch the game without no_upload_hvv but use RADV_PERFTEST=nosam, it doesn't crash and I don't see slowdowns in text heavy areas. Maybe it's an issue with how no_upload_hvv is implemented?

You can look into https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/docs/drivers/amd/hang-debugging.rst?ref_type=heads, this smells like a driver/kernel bug to me.

I tried to replicate the crash with RADV_DEBUG=hang but it doesn't crash. The game runs at 20-30 fps though. I think it's because that option forces RADV_DEBUG=syncshaders, if I use this alone I get the same result.

I suppose I could open an issue in mesa, but I'm not sure it's a mesa bug yet, if I disable application quirks and set RADV_PERFTEST=nosam the game doesn't crash.

I'll try to figure out how no_upload_hvv works and update the issue if I can find the cause.

Yeah it can't be a vkd3d bug, it just activates a flag in vulkan. I'll report this to the mesa devs.

In the mean time, if anyone else is having this issue:

export VKD3D_CONFIG=skip_application_workarounds
export RADV_DEBUG=nosam

@HansKristian-Work Immediately after the intro cutscene, I can't even get to the cave where you meet Fragile without it crashing.

Nothing, it's stock, and other games work. You can't reproduce the issue?

Oh, ok.
For completeness, I've also tested wine mainline and mesa stable, and the problem is still present. I haven't tried a different kernel but I can probably try an LTS version, it should support this card.

The oldest kernel that supports the 9000 series is 6.12, and it crashes there as well.

no issues with proton experimental bleeding edge, linux 6.18.9, mesa git and 9070 (non xt). Yesterday, I played the intro sequence up until after the cave thrice. Today played for over an hour, no issues on my end

@simifor Mesa version? Do you just launch the game from steam with no options? I can replicate this problem consistently even on a clean install of the OS

I wouldn't be surprised if this turns out to be a power management issue tbh, I have little faith in RDNA4's stability in this regard on linux. I'd try the step recommended here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/14516#note_3278570, or maybe just try to enable overdrive support using the kernel command line, which in turn will disable automatic power profile switching.

That doesn't seem to fix it, but limiting the framerate to 60 did, so maybe you're onto something. @simifor do you have a 60hz monitor?

@adolfintel it's 2k 180Hz

Weird, but I'm glad it's not a bug.