Emulator

The above issue is likely to be driver-related. Test on the AMD 23.7.3 release to verify/reproduce the problem.

Correction, 23.7.2.

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.)

So disabling the Fast Depth Calculation had no effect.

More than willing to provide a fifolog - I haven't really used Fifo player before, where are the logs stored and how many frames should I set it to record? Thanks.

Attaching a FIFO log of the Golf title screen...not sure I did this correctly but I recorded 3 frames when the title screen was open and loaded (Vulkan back-end). I had to post the file on a file upload site because even 3 frames vastly exceeded 5MB...

https://file.io/gz1aayA7bYKD

In case someone else downloaded the file from the link above, here's another one that'll persist for a week...

https://easyupload.io/9mca2u

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.)

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.

I will report it via AMD's user forums - that's about the best I can do, not having a direct contact at AMD.

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.

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).

This problem has been fixed, no Vulkan issues with Dolphin 5.0-19951 under the latest AMD drivers.

What was the fix??