Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.6.0f3
Issue ID
905518
Regression
Yes
overrideSorting property is not set if an object was parented to a Canvas and a Canvas component was added to it
If the game object was first parented to a Canvas and then the Canvas component was added to it, the overrideSorting property cannot be set. However, if the Canvas component was added to the object before parenting it to another Canvas, overrideSorting property will be set properly.
To reproduce:
1. Open the project, attached by the tester (overrideSortingBug.zip)
2. Open the "scene" scene
3. Enter Play mode
4. Observe the "new Canvas" game object's Canvas component, overrideSorting will be false (should be true)
Expected: overrideSorting property is set properly with any order of operations
Reproduced in 5.6.0f1, 5.6.0f3
Did not reproduce in 5.5.4f1, 5.6.0b11, 5.6.1f1, 5.6.2p2, 2017.1.0f2, 2017.2.0b2
Regression introduced in 5.6.0f1
Fixed in 5.6.1f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Add comment