Search Issue Tracker
Third Party Issue
Votes
38
Found in [Package]
12.0.0
Issue ID
1300594
Regression
No
[HDRP] Visual artifacts are seen when using Forward renderer with MSAA
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Change Quality to Medium profile (Edit->Project Settings->Quality)
3. Wait for all compilation processes to finish
4. Inspect the Game View
Expected result: No visual artifacts are seen
Actual result: Visual artifacts are seen
Reproducible with: 10.5.0 (2020.3.8f1), 11.0.0 (2021.1.7f1), 12.0.0 (2021.2.0a17)
Couldn't test with: 4.10.0-preview (2018.4.35f1), 7.6.0 (2019.4.26f1) (Project breaks when downgrading. Couldn't reproduce the same issue on a fresh project)
Note:
- Artifacts can be seen in standalone Player with Unity 2020.3.8f1
Comments (1)
-
Jasper-Flick
May 11, 2021 13:51
An underlying issue is that Unity cannot correctly deal with multisample textures that aren't set to auto-resolve. Custom SRPs also suffer from artifacts and the frame debugger cannot deal with such textures either.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This an issue within the graphics driver. The issue has been reported to Apple as rdar://81401163.