Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.37f1
2022.3.23f1
2023.2.18f1
6000.0.0b14
Issue ID
UUM-70625
Regression
No
RenderParam.renderPriority is ignored when rendering Mesh with Graphics.RenderMesh()
Reproduction steps:
1. Open the attached “Bug.zip” project
2. Open the “SampleScene” scene
3. Open the Frame Debugger Window (Window > Analysis > Frame Debugger)
4. Enable the Frame Debugger
5. On the slider at the top go through Events and observe the Output screen
Expected result: The cubes in the center are rendered based on their RenderParam.renderPriority value
Actual result: The cubes in the center have the same render priority as Mesh with layer order set to “0”
Reproducible with: 2021.3.37f1, 2022.3.23f1, 2023.2.18f1, 6000.0.0b14
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note:
- The generated cubes get rendered in-between “Mesh Cube red S0” and “Mesh Cube blue S0” which both have their “Order in Layer” set as “0”
- The mesh draw script is attached to the “Bug” GameObject in the Hierarchy
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NavMesh Surface is baked too high above the ground, making the NavMesh Agents hover above the ground when the HeightMesh is not built
- [Android] Crash on ProcessDynamicBatchGeometryJob with OpenGL or on DrawSharedGeometryJobs with Vulkan
- VFX Graph Memory leak when calling the ClearPropertyBinders and AddRemoveVFXProperty
- Entering "Configure Avatar" inside the Inspector locks it
- [Render Graph Viewer] Resource list icons cropped and in inconsistent positions
Add comment