Since mesa vulkan-radeon-19.0.3 (RADV) playing AC Odyssey via lutris and DXVK (version of DXVK does not matter) the system hangs after finishing to load the savegame. The loading screen shows flickering and blotchy particle effects of the fire pit. Reverting to 19.0.2 immediately fixes the issues, no particle issues and no system hang. I have also tested the current master and the issue is still persistent there. Is there any trace I can deliver to help getting this fixed? System: Sapphire AMD Vega 56 model name : AMD Ryzen 7 1700X Eight-Core Processor Linux antergos 5.0.10-arch1-1-ARCH #1 SMP PREEMPT
I narrowed the issue to a specific commit: https://github.com/mesa3d/mesa/commit/b5ea4378c3260ff003532c8138a81a57091bdaa0#diff-078b981b454c93e62531f44768fca61d ac/nir: only use the new raw/struct image atomic intrinsics with LLVM 9+ b5ea4378c3260ff003532c8138a81a57091bdaa0
Just FYI currently on running LLVM 8
I have the same issue, bisected to the same commit as you. I have a Vega 56 and LLVM 8 also. FYI. If you edit it back to be if (HAVE_LLVM >= 0x800) { The artifacts and crashing disappear.
This is really weird, the fix is actually for LLVM 8 and it just breaks...
Can you record an apitrace of the problem? I would like to understand it before doing a revert eventually.
apitrace will not help us here. Use case: ACO (Windows Game) -> Wine -> DXVK -> vulkan apitrace cannot catch vulkan stuff. Is there a better tool to trace the vulkan api ?
apitrace will catch D3D11 and then we can replay the trace through Wine/DXVK/RADV. See the DXVK wiki for more info about that.
I recorded an apitrace of AC:O back in october to help debug a dxvk issue, but at least back then it crashed with apitrace before you could load a savegame, so it might not be possible to reproduce this issue with apitrace. Anyways, here is the old trace: https://drive.google.com/open?id=1vFyghPpwZ_M5K16-xv1Vp97jauL4Ma9l
Yeah, the trace crashes and doesn't expose the problem for me.
Is there any other trace I can provide for debugging purposes?
What you can do is to try to record a renderdoc capture with 19.0.2 and see if you can reproduce the problem by replaying it with 19.0.3. You probably need to be a bit lucky to record the right frame. :)
I think I found the problem with a different game, I'm working on.
Can you try https://patchwork.freedesktop.org/series/60252/ ? That should fix the regression.
Yes that seems to fix the issue! No more visual artifacts or system hangs. Thanks a lot for the help!
Fixed with https://cgit.freedesktop.org/mesa/mesa/commit/?id=4f18c43d1df64135e8968a7d4fbfd2c9918b76ae It should be in the 19.0.4 and 19.1 releases.
Great work, thanks again!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.