Open kode54 opened 2 months ago
I reproduced this on RX 7600. Seems to be related to ray tracing, at least. I didn't see an option to disable it in the game, so I ran with VKD3D_CONFIG=nodxr
, and then it worked fine.
Yes, it does indeed appear to be ray tracing related. So whose bug is this now, Mesa's? Or still the game's for having buggy (and undocumented) ray tracing code?
A lot of UE4 games, built on 4.19 or newer, can use -dx12 as a launch command to run in DX12 instead of DX11. To my knowledge, Stray, as a normally DX11 only UE4 title, is the only game where running this launch command also triggers RT effects, assuming the hardware/software is RT capable.
Now, this is clearly a design quirk, given devs don't expect customers to run the game in DX12. But RT effects get triggered and the game doesn't crash on Windows on RT capable GPUs. So it shouldn't crash on Linux either, given DXR is now enabled by default on Mesa.
There was some talks where either Mesa or VKD3D was meant to blacklist RT in Stray in DX12 due to Steam Deck in particular, but I'm not sure how that discussion went.
RT effects can be disabled on Linux either with said command above: VKD3D_CONFIG=nodxr or just UE4 config that disables RT: r.raytracing=0 or smth like that xd.
Mhhm, didn't know RT in Stray was a thing. Seems to work with Nvidia so perhaps an AMD mesa bug?
Please describe your issue as accurately as possible. Include screenshots or videos if relevant
The game crashes after a minute or two of runtime, with an amdgpu gfx pipe lockup.
Software information
Stray (Steam AppID 1332010) Running with -dx12 startup switch
System information
Log files
steam-1332010.log dmesg.stray.log
Notes
Happens with both Mesa and amdvlk, so it's likely either a game bug or vkd3d bug.