Search Issue Tracker
By Design
Votes
0
Found in [Package]
11.0.0
Issue ID
1295485
Regression
No
Depth sorting is not working when using a Custom render feature with a custom shader
How to reproduce:
1. Open the attached project named "Case_1295485"
2. Open the MainScene02a located in Assets/Scenes
3. Enter Play mode
4. Click Custom Mode -> Suspension
5. Observe the Front Right suspension strut
Expected results: The Front Right suspension strut is rendered in front of the Back Left strut
Actual results: The Front Right suspension strut is obscured by the Back Left strut
Reproducible with: 10.1.0(2020.2.0b10), 10.2.2(2020.2.0f1), 11.0.0(2021.1.0a10)
Could not test with: 2018.4(URP was in early preview stage), 2019.4, 2020.1(Scripts breaking on downgrade)
Notes:
1. Reproducible in Scene and Game views
2. Graphics APIs tested - D3D11, D3D12, Vulkan, OpenGLCore
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
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
- Material Component has two horizontal lines under it when its foldouts are closed
- Some selected Mesh Renderer Materials lead to Assets folder when pinged
- Editor colors appear darkened out when HDR Display Output is enabled
Resolution Note:
It is intended functionality, because Callouts pass uses GEqual depth function which is in d3d11 converted to LEqual (Reverse z).
Simply change depth compare function to LEqual.