Bug 103999

Summary: 4x MSAA with RG32F shows garbage on triangle edges
Product: Mesa Reporter: maister
Component: Drivers/Vulkan/radeonAssignee: mesa-dev
Status: RESOLVED FIXED QA Contact: mesa-dev
Severity: normal    
Priority: medium    
Version: 17.2   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Bug

Description maister 2017-11-30 19:12:12 UTC
Created attachment 135833 [details]
Bug

On 17.2.6, edges don't resolve correctly in MSAA.
I'm using pResolveAttachments for this.
I could upload a renderdoc trace, but it's too big for the tracker (90MB).
Tested on RX470.
Comment 1 Ernst Sjöstrand 2017-11-30 20:32:20 UTC
Are you saying it worked with 17.2.5?
Comment 2 maister 2017-11-30 23:04:46 UTC
No idea, haven't tried this on any other drivers.
Comment 3 maister 2017-11-30 23:05:12 UTC
RADV that is. Works on other driver stacks I've tested.
Comment 4 Bas Nieuwenhuizen 2017-12-29 23:24:02 UTC
Is this still an issue as of git master with the recent multisample resolve fixes? (e.g. has commits up to https://cgit.freedesktop.org/mesa/mesa/commit/?id=a636208ace00e5ba7ddb331362b3e95fd4cea422)
Comment 5 maister 2018-01-07 10:18:34 UTC
Still buggy on latest git.
Comment 6 Clément Guérin 2018-03-29 20:32:49 UTC
@maister could you host your apitrace and share it here?
Comment 7 maister 2018-03-30 13:24:32 UTC
This seems to work fine now on 17.3.7.
Comment 8 maister 2018-03-30 13:31:44 UTC
Here's a renderdoc 1.0 capture on RX470 for reference:
https://drive.google.com/file/d/1e9zIRVhZxtdA5DodASi3FK75fuRBuqxO/view?usp=sharing
Comment 9 Samuel Pitoiset 2018-03-30 15:57:40 UTC
Cool, could try again mesa master to confirm the issue is really fixed? Thanks!
Comment 10 Samuel Pitoiset 2018-04-17 19:55:21 UTC
We fixed a bunch of multisample resolve issues recently, and if it works fine with mesa 17.3.7 it should be OK on master.

Closing, please re-open if the issue still occurs.

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.