Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.4
2019.4.7f1
2020.1
2020.2
Issue ID
1271764
Regression
No
Depth Buffer Offset value is converted to integer in calculations
How to reproduce:
1. Open attached project "depthbuffer.zip"
2. Open "SampleScene" scene
Expected result: Notice that the green cube is rendered on top of the red cube
Actual result: Red cube is rendered on top since it has a lower Depth Buffer Offset value
Reproducible with - 2018.4.28f1, 2019.4.9f1, 2020.1.4f1, 2020.2.0b7
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2021.1.X):
Both offset parameters are hardware- and driver-dependent.
On my machine I can see the expected results when using the Factor parameter.