Search Issue Tracker
Active
Fixed in 2022.3.21f1, 2023.2.12f1, 2023.3.0b9
Votes
0
Found in
2022.3.19f1
2023.2.9f1
2023.3.0b6
Issue ID
UUM-62716
Regression
No
“Invalid SortingGroup index set in Renderer” error is thrown when a collision replaces a GameObject with another one
How to reproduce:
1. Open the “Floralis-Verdelight” project
2. Open the “Assets/- Game/Scenes/Gameplay.unity” scene
3. Enter Play Mode
4. From the list of “Orb” GameObjects select “Nurturer Orb”
5. Place 2 “Nurturer Orbs” on the right-most “Genesis Nexus” (green orb)
6. From the list of “Orb” GameObjects select “Infectious Anchor Orb”
7. Place the “Infectious Anchor Orb” next to the previously placed “Nurturer Orbs”
8. Observe the Console
Expected result: No errors are thrown
Actual result: The “Invalid SortingGroup index set in Renderer” error is thrown
Reproduced with: 2022.3.19f1, 2023.2.9f1, 2023.3.0b6
Could not test with: 2021.3.35f1 (Could not resolve package errors)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
1. A reproduction video showing the steps more clearly is attached internally
2. Could not test in Player → Build errors are thrown
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.3.0b9):
Fix for this issue is available on Unity 2023.3.0b9 and above
Resolution Note (fix version 2023.2.12f1):
Fix for this issue is available on Unity 2023.2.12f1 and above
Resolution Note (fix version 2022.3.21f1):
Fix for this issue is available on Unity 2022.3.21f1 and above