Low performance and graphical issues with AMDVLK in Detroit Become Human (Windows only Vulkan exc game)-compared to RADV about amdvlk HOT 8 OPEN

@Leopard1907 I have downloaded your RenderDoc captures, so you can clear them from your Google Drive if you need to free space.

I am able to reproduce the visual corruption using the RenderDoc captures; however, I do not see the same corruption in the game. It's possible that this is a driver/game interaction issue which may already have been resolved. I will attempt to reproduce with the exact driver you used.

I can reproduce the AMDVLK frame rate for the scene shown, but I have yet to get the game to work with the Mesa version specified. It seems to stall during the "Shader Compilation Process".

from amdvlk.

@perlfu Weird, just compiled mesa-git freshly againts this https://gitlab.freedesktop.org/mesa/mesa/-/commit/480ec5b1d480c62bc9984a44bbb6453bca1970be and it still goes through shader compile screen.

from amdvlk.

@perlfu Did you compile RADV as debug build, i compiled as release.

 meson build64 --libdir lib64 --prefix $HOME/mesa -Dgallium-drivers= -Dvulkan-drivers=amd -Dgallium-nine=false -Dvideo-codecs=h264dec,h264enc,h265dec,h265enc,vc1dec -Dbuildtype=release

from amdvlk.

As leopard suggested, there seems to be an issue with debug builds of Mesa; I don't know exactly why, but release or debugoptimized builds should let the game go through shader compilation without problems.

If that still doesn't work, please try compiling this branch: https://gitlab.freedesktop.org/ishitatsuyuki/mesa/-/tree/more-dbh-hack. The branch contains a targeted workaround for the fact that the game refuses to consider any pipeline cache below 128KB to be "finished".

from amdvlk.

Thanks for the pointers, I had completely forgotten default mesa build is debug.
I can get the game running with a release build.

One important reproduction detail is that the game resets graphics settings when switching ICD. So game has to be launched once to build pipelines, before setting resolution and editing .ini file to unlock frame rate.

For LLPC I got ~95 fps, with 85% GPU, 35% CPU.
For RADV I got ~125fps, with 70% GPU, 50% CPU.

My test CPU is older and slower than your test system, which I think explains the RADV difference between our results.
I think RADV is CPU bound in this test. I never saw RADV use more than 70% GPU.
This seems to be a strong reproduction of a performance gap from my perspective.

Memory usage is definitely higher in LLPC, particularly in the pipeline compilation phase of game launch there seems to be some possible leakage.

from amdvlk.

Thanks for the test. Windows side seems to be also suffering from perf issues but with potentially much less cpu usage. But ofc i don't have Windows to test.

https://youtu.be/5IBmkPMQMUA?si=rjC-tDQoOTIORm1x

There is just an insane difference here.

from amdvlk.

Thanks for the test. Windows side seems to be also suffering from perf issues but with potentially much less cpu usage. But ofc i don't have Windows to test.

https://youtu.be/5IBmkPMQMUA?si=rjC-tDQoOTIORm1x

There is just an insane difference here.

Btw my screenshots/testing also shows much higher cpu usage on Radv side. 75-80 percent on all cores.

from amdvlk.