Invalid SortingGroup index set in Renderer

Hi! We are facing an issue with SortingGroups causing crashes. Every now and then when we activate/deactivate a GameObject with a SortingGroup (either in the GameObject itself or any of its children), or when we activate a ParticleSystem under a SortingGroup, the game crashes with this error:

After that the console is being spammed with this error:

I have made sure all the sorting layers being set are valid (always setting the same layer and it's working most of the time).

There are two bugs in the tracker, but they have been marked as fixed long time ago:
https://issuetracker.unity3d.com/is...hat-has-a-child-gameobject-with-sorting-group
https://issuetracker.unity3d.com/is...group-id-assert-when-removing-a-sorting-group

We are using 2018.2.9f1. Currently unable to update to newer versions because of an external plugin that we are required to implement.

I haven't sent a bug report yet, since I haven't been able to create a reliable reprocase. Still working on that. In the meantime, has anyone else faced this same issue and is there a known fix?

EDIT:
Not sure if it matters, but: The SortingGroup components are being added dynamically during runtime. The ParticleSystem under one of the SortingGroups is also being added dynamically from a pool.

EDIT2:
Moving the ParticleSystem to be a sibling of the top-most SortingGroup (in the hierarchy, not sorting order) made the crash rarer, but did not completely fix it.

Also had another case, where it was crashing most of the time and I was able to fix that by first setting the sorting layers and orders, waiting for a frame, and then finally activating the ParticleSystem.

 

i have same issue in 2018.2.11f1 very anoying la;sdkfj a;lwiefj;laksjd fsda

 

ha.. I fix this

In My Case Do NOT Use Same Time(inRuntime) Change Parent and SetActive Renderer.

 

Not sure if I'm seeing the same issue on my side, but it certainly seems quite similar, which would leave me to believe it is the same as this bug reported on the issue tracker: https://issuetracker.unity3d.com/is...-when-managing-sortinggroups-children-objects

In our case, we were able to circumvent the issue by disabling the sorting group before reparenting or enabling/disabling any children of the sorting group, then enabling it again afterwards.

After waaay too many hours tinkering around we finally managed to end up on this easy solution that worked for us. But it is still a crappy workaround and can't wait for Unity to fix the issue properly.

The worst part is, I can't even figure out the exact circumstances that cause the problem, it seems to happen pretty inconsistently. It's certainly related to parenting/unparenting and enabling/disabling child objects of a SortingGroup. It also seems like waiting at least until "end of frame" (using a coroutine) makes the issue much less frequent.

 

I have same issue in 2018.4.3f1.

Also add a particle from a pool to be a child of a sortinggroup gameobject.

 

This still happens in 2019.1.12f1

 

same in 2018.4.4f

is there a way to debug this? I see it on my console in unity, but no stack track

 

Unity 2018.4.2f1 working in 2D, I managed to solve this problem by just adding a sorting group to the problematic pooled object. The new parent of the pooled object had a soprting group too, which overwrited the new "dummy" sorting group of the pooled object anyway, so adding this dummy seemed to cause no sorting issues.

This worked for me too, by delaying the "setactive" by 1 frame- but this wasn't graceful enough for me.

For reference, my pooled object was just a spriterenderer with particle system on the game gameobject, stored as a prefab. No sorting group. But adding a sorting group to this prefab seemed to prevent the issue.

Hope this helps

 

Hi, I've faced the similar issue. My solution was:

Code (CSharp):

1.  
2.     SortingGroup[] sortingGroups;
3.     SortingGroup[] SortingGroups => sortingGroups ?? (sortingGroups = GetComponentsInChildren<SortingGroup>());
4.  
5.     void OnEnable()
6.     {
7.         foreach (SortingGroup sortingGroup in SortingGroups)
8.             sortingGroup.enabled = true;
9.     }
10.  
11.     void OnDisable()
12.     {
13.         foreach (SortingGroup sortingGroup in SortingGroups)
14.             sortingGroup.enabled = false;
15.     }

The script with the similar code should be attached to the root of pooled object.
Hope, it will help you.

 

Still happening in 2020.1.10 ... looks like this is caused, for me, by creating an object from a pool and setting one of its children to active in the same frame.

Happens very infrequently, added a sorting group to the parent object in an attempt to hack around this, will update if this doesn't work.

 

Also having this issue with 2020.3.8f1, I will try the solutions mentioned above!

 

I am having this issue in 2020.3..13f1, but the above sollutions did not work for me and I'm not sure why.

 

Unity 2022 still happened I don't know which one created this error or where to fix

 

I had this same bug today; I simply switched the line that set the sorting order to be AFTER the line that activated the object. I haven't seen it since.

 

Same in 2019.1.0f2 and above versions.

 

Oh it still happen in 2022.1.0b2.2474

 

Same error 2021.3.11f1

 

I have same issue in 2018.4.3f1.