Emulator Issues #13310
closedVulkan back-end, Graphical rendering problems w/newest AMD 23.7.2 Drivers
0%
Description
Game Name?
Any Wii or GC Title - Mario Golf: Toadstool Tour will be the example
Game ID? (right click the game in the game list, Properties, Info tab)
GFTE01
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
5fd9909e73df7fb704d2e443e17346b5
What's the problem? Describe what went wrong.
When starting the game, Vulkan as the Graphics back-end, the intro will play fine, but the interactive elements as well as the moving graphical elements will not render properly.
What steps will reproduce the problem?
Select Vulkan as the Graphics back-end
Launch game
It's that easy to reproduce
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
yes - 5.0-19836
Is the issue present in the latest stable version?
N/A - not sure
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
Have tested dev builds back to 5.0-19798, all exhibit the same issue with Vulkan
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
Refer to this thread for screenshots:
https://forums.dolphin-emu.org/Thread-vulkan-back-end-broken-latest-dev-builds-perhaps-by-newest-amd-drivers
What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 11 Pro x64 latest build
AMD 5950X CPU
AMD RX 6900XT GPU
AMD Radeon Driver 23.7.2 (released 7/25/2023)
64GB of RAM
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Quite easy to reproduce this problem as launching the game w/Vulkan back-end will immediately present the issue.
Files
Updated by pokechu22 5 months ago
Could you attach a fifolog of the Mario Golf title screen? I don't have an AMD GPU currently, but having a fifolog would allow me to check if the game's doing something weird there.
As a random thing to try, you could uncheck "Fast Depth Calculation" in Graphics -> Hacks. (I have no idea if this would actually make a difference or not here, and if it's a driver bug ultimately the driver needs to be fixed, but it's at least a possibility.)
Updated by pokechu22 5 months ago
Thanks. I received that file, but it seems to be broken in a weird way. If you had dual core enabled before, can you try recording a new fifolog with it disabled? (Dual core shouldn't matter, but it seems like the most likely culprit for a broken fifolog.)
Fifologs also generally compress fairly well, so you can generally use 7-zip to compress it under 5MB. In this case it seems like it would still have been bigger, but maybe a different one would be smaller. (7-zip also supports splitting files into chunks, which could be used here if needed.)
Updated by pokechu22 5 months ago
Thanks, that one works.
My guess is that AMD broke dual -source blending, which is a fairly niche feature that Dolphin uses extensively and needs for correct emulation, but most regular games do not use at all. Based on that fifolog and another mario golf one I have lying around, that would be consistent with the title not rendering but the title screen's background rendering, and also consistent with the world being completely missing ingame.
I don't know if there's a good way to confirm if it's dual source blending or how to report it to AMD, though.
Updated by ForkWNY 5 months ago
I've reported the issue through AMD's user forums - I doubt anyone from AMD will respond but at least this brings the issue to their attention, and perhaps other users will chime in because this issue may impact other apps (even though you mention it's a niche feature, I would imagine it's used in other graphics applications).
Not knowing a lot of technical details behind graphics rendering, why aren't D3D11/12 or other back-ends impacted? Only Vulkan has this particular problem.
Updated by pokechu22 5 months ago
Not knowing a lot of technical details behind graphics rendering, why aren't D3D11/12 or other back-ends impacted? Only Vulkan has this particular problem.
They might have broken it in the part of the driver that handles Vulkan-specific stuff. My understanding is parts of the driver are shared, but you still have to deal with Vulkan's way of setting up blending versus D3D11's way of setting up blending versus D3D12's way of setting up blending. It doesn't seem too weird to me that only one is broken (but all of them being broken at the same time would seem equally normal).
Updated by OatmealDome 4 months ago
- Status changed from New to Fixed
- Fixed in set to 5.0-19916
Thanks for the update.
AMD reported to us that a workaround we added 5 years ago for AMD's Windows 8.1 drivers was causing problems. Since we don't support that OS anymore, we removed the workaround.