Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2018.4
2019.4
2020.2
2021.1
2021.1.0b3
2021.2
Issue ID
1309075
Regression
Yes
Objects of the SortingGroup are sorted incorrectly after instantiating new objects inside of SortingGroup member
Reproduction steps:
1. Open the user's attached project and SortingGroup_BrokenHierarchySorting scene
2. Enter the play mode and observe the sorting of the objects In the Game view (for example red and white squares)
3. Press A and observe the sorting of the objects
Expected result: Sorting of the objects did not change
Actual result: Sorting of the objects changed
Reproducible with: 2018.4.31f1, 2019.4.20f1, 2020.2.3f1, 2021.1.0b5, 2021.2.0a4
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
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a7