Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2017.4.0f1
2018.2.0a1
2018.3.0a1
2018.3.0b12
2019.1.0a1
Issue ID
1106381
Regression
No
"Invalid SortingGroup index set in Renderer" after removing Sorting Group component on an object with nested Sorting Groups
To reproduce:
1. Open attached project "SortingGroupAssertion.zip"
2. Open "Group1" prefab in Prefab mode
3. Remove the Sorting Group component from "Group1" prefab in Inspector
An alternate way to reproduce without Prefab Mode:
1. Open attached project "SortingGroupAssertion.zip"
2. Select "Group3" object in Hierarchy and remove Sorting Group component in Inspector
3. Undo (Ctrl+Z) deletion of the Sorting Group
4. Select "Group4" object in Hierarchy and remove Sorting Group component in Inspector
5. Undo (Ctrl+Z) deletion of the Sorting Group
Expected: No errors appear
Actual: Assertion errors appear
Invalid SortingGroup index set in Renderer
UnityEditor.EditorApplication:Internal_CallUpdateFunctions()
Reproduced in: 2019.1.0a11, 2019.1.0a1, 2018.3.0b12, 2018.3.0a1, 2018.2.0f19, 2018.2.0a1, 2017.4.17f1, 2017.4.0f1
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
wechat_os_Qy04dLnyinv57w_omGLuIEDso
Sep 26, 2019 10:04
it happend here too!