Search Issue Tracker
In Progress
Fix In Review for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.0a3
Votes
0
Found in
6000.0.58f1
6000.2.5f1
6000.3.0b2
Issue ID
UUM-119198
Regression
Yes
"Invalid SortingGroup index set in Renderer" errors when making many modifications in same frame
Reproduction steps:
1. Open the attached “IN-115988.zip” project
2. Open the “SampleScene”
3. Enter Play mode and wait a few seconds
4. Observe the Console
Expected result: No errors
Actual result: “Invalid SortingGroup index set in Renderer” errors
Reproducible with: 2023.3.0b9, 6000.0.58f1, 6000.2.5f1, 6000.3.0b2
Not reproducible with: 2023.3.0b8 (only other errors are present)
Reproducible on: Windows 11, macOS 15.6.1 (M1 Max)
Not reproducible on: no other environments tested
Note:
- This is a stress test for a real-world scenario: “Invalid SortingGroup index set in Renderer” is triggered by the object pool where it can end up returning an object to the pool and pulling it out in the same frame (ie, multiple enable/disables per frame, together with re-parenting the object
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment