[AMD NAVI] MSAA (un)resolve pass does not work correctly using proprietary drivers

[kd-11]

This is a meta tracker for the Navi series' problems with MSAA resolve and unresolve shaders. While I have several ideas what the underlying problem is, I need one centralized thread for testing and discussion.

1. Has anyone checked what happens with the much better RADV driver on linux? Would be good to know if this is a hardware quirk or just bad drivers before crafting a workaround.
2. Are there any titles where disabling MSAA does not fix Navi-specific glitches?

[mignolo4]

1. Trying different s.o. with MSAA on ( Navi - 5700XT):

Ubuntu 19.10 + RADV

Win10 + 19.11.2 amd drivers

2. It seems all my games are affected with MSAA on and they are ok with MSAA off

[kd-11]

So this issue is limited to the AMD drivers and is therefore a driver issue. Makes it easier to attempt crafting workarounds. I can somewhat tell what is going on looking at the pattern, I'll set up a fallback path for AMD and Intel drivers but that may hurt performance a bit.

[githuborer]

I see this on all emulated games with navi card RX5700 xt. I disabled AntiAliasing but see the same.
In RDR it looks very bad. Lot of those lines at screen

[kd-11]

Please retest with #7253

[mignolo4]

Nope :(

[Clearmist]

I concur that this issue is occurring with Radeon RX5700 XT. Here is what it looks like emulating Uncharted: Drake's Fortune. I am available to test patches.

Disabling anti-aliasing fixes the issue.

[please2000]

I was trying TLOU with the latest patch file. These were the result. What seems to be the problem?
Combo : R5 3600 + RX5700XT
Radeon Driver Version: 20.5.1
**AA disabled in RPCS3

[illusion0001]

It's a bug with the windows driver. And is caused by one of the patches. Linux with RADV doesn't have this issue.

[kd-11]

RDNA1x issues are fixed by #9324.
RDNA2x has a different variation of this bug but we still don't know if it is an issue that will be fixed with upcoming drivers or not.

[kd-11]

Remaining RDNA2x bugs solved with the new raytracing driver 20.11.2. This issue is fixed.