Search Issue Tracker
By Design
Votes
0
Found in [Package]
9.0.0-preview.33
Issue ID
1362609
Regression
Yes
Sorting Priority does not work when Receive SSR Transparent is enabled on a Transparent Material
Reproduction steps:
1. Open the attached "1362609.zip" project
2. Open "OutdoorsScene" Scene
3. Go to "River 2" GameObject and expand "River 2 (Material)" by clicking the small triangle next to it
4. In the Surface Options of "River 2 (Material)" enable Receive SSR Transparent
5. Enter the Play Mode and observe the Plane GameObjects
Expected result: GameObject with higher Sorting Priority gets rendered over the GameObject with lower Sorting Priority
Actual result: GameObject with lower Sorting Priority gets rendered over the GameObject with higher Sorting Priority
Reproducible with: 9.0.0-preview.33 (2020.1.0b13), 10.6.0 (2020.3.18f1), 11.0.0 (2021.1.20f1), 12.0.0 (2021.2.0b11, 2022.1.0a8)
Not reproducible with: 7.7.0 (2019.4.30f1), 9.0.0-preview.13 (2020.1.0b12)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note:
The SSR transparent effect required to write into the depth buffer for the receiving Material. This is not compatible with the priority system. Priority is only between Material who don't write in depth buffer. Documentation will be updated to reflect it.