Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X
Votes
0
Found in
2017.4
2018.4
2018.4.6f1
2019.2
2019.3
2020.1
Issue ID
1202432
Regression
No
SortingGroup has no effect to Game Objects immediately after instantiating them
To reproduce:
1. Open attached project ("case_1202432-Sample.zip")
2. Press Play and observe two circles in the Game View
Expected result: Both circles have a visible red cross inside
Actual result: Only the right circle has a visible red cross inside
Reproducible in: 2017.4.35f1, 2018.4.14f1, 2019.2.16f1, 2019.3.0f2, 2020.1.0a15
Comments (1)
-
matiasticbits
Feb 27, 2020 09:44
Which version of 2018.4 track was this fix introduced? I haven't been able to find a mention of this in any release notes on that track.
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 2019.3):
Added SortingGroup.UpdateAllSortingGroups to allow users to update SortingGroups immediately when called.