Search Issue Tracker
Fixed
Fixed in 2022.3.21f1, 2023.2.12f1, 2023.3.0b9, 7000.0.0a1
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
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