Search Issue Tracker
Duplicate
Votes
0
Found in
2021.3.18f1
2022.2.6f1
2023.1.0b1
2023.2.0a1
Issue ID
UUM-26390
Regression
No
Some pixels fail to render when using Depth Priming
Reproduction steps:
1. Open the attached project "DepthPrimeBugClean"
2. Open "SampleScene"
3. Enter Play mode
4. Hold RMB and move the mouse around
Expected result: the tree looks normal, no black or blue pixels moving around the leaves
Actual result: there are black or blue pixels moving around the leaves
Reproducible with: 2021.3.18f1, 2022.2.6f1, 2023.1.0b1, 2023.2.0a1
Not reproducible with: 2020.3.45f1
Reproducible on: macOS 12.4 (Intel)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
a duplicate issue was fixed. The problem was depth priming breaking the depth normal prepass when MSAA is on. This was fixed and backported in December 2022 so closing this as duplicate.
Duplicate of another internal issue: UUM-5684: Depth Priming breaks the depth normals prepass when MSAA is on