Search Issue Tracker

Fixed in 2017.3.0f3

Votes

0

Found in

2017.3.0b6

Issue ID

962872

Regression

Yes

"Assertion failed: Invalid SortingGroup..."is thrown when deactivating GameObject that has a child GameObject with Sorting Group

2D

-

How to reproduce:
1. Open the attached "AssertSortingGroup" project and "Level0" scene
2. Enter playmode and observe the console

Expected result: Playmode is entered, no assertions are thrown
Actual result: Playmode is entered, "Assertion failed: Invalid SortingGroup index set in Renderer" is thrown

Regression introduced in - 2017.3.0b4
Reproducible with - 2018.1.0a2, 2017.3.0b8, 2017.3.0b4
Not reproducible with - 2017.3.0b3, 2017.2.0p1, 2017.1.2p2

Notes:
1. The assertion does not happen when disabling "WaterLightingEffect" GameObjects (both of them has Sorting Group components attached)
2. The assertion is caused by line 75 (gameObject.SetActive(false) in "Wander" script. Asserts only reproduces when gameObject is deactivated in IEnumerator function, it does not reproduce, when deactivating it from void method

Fixed in 2017.3.0b10

Comments (9)

  1. trunghieu95tb

    Apr 08, 2021 03:20

    Still getting the bug on Unity 2019.4.15f1
    They haven't fixed them yet or still have many other cases where this error occurs.

  2. zzgrzyt

    Apr 17, 2018 15:37

    Correction, what we are seeing might be slightly different. In our case, we hit this assert regardless if it is an enumerator or not. Also tested in and still happens in 2017.4.1f1.

  3. zzgrzyt

    Apr 17, 2018 14:51

    Still happens in 2017.4.0f1.

  4. _____nakj

    Mar 16, 2018 03:19

    It is reproduced in 2017.3.1p3, I think

  5. GusViegas

    Mar 14, 2018 21:18

    It came back on 2017.3.1f1. Help

  6. Jhsosa

    Mar 02, 2018 05:50

    You get this same error when attempting to set a GameObject's (with Sorting Group) transform parent to another GameObject who has a rect transform and is a child of a Canvas.

  7. jijianquan

    Feb 09, 2018 06:54

    Same Error in 2017.3.0f3

  8. DangerouZ720

    Dec 27, 2017 15:50

    still getting the error on version 2017.3.0p1

  9. geff

    Nov 18, 2017 13:10

    Same Error in 2017.2.0p2

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.