Search Issue Tracker
Fix In Review for 2018.4.X
Votes
1
Found in
2017.1.0b8
Issue ID
918443
Regression
Yes
Sorting of UI elements in Hierarchy changes after entered to Play mode
To reproduce:
1. Download attached project "stellar-trail copy.zip" and open in Unity
2. Open "MissionDev" Scene
3. In Hierarchy expand Canvas / VehicleAssemblyPanel3
Note: Observe that UIActionButton_Attach is sibling 0 and UIBody_Background is sibling 1
4. Move UIActionButton_Attach lower down the Hierarchy and save the scene.
5. Enter Play mode
Expected Result: Hierarchy stays up the same
Actual Result: In Hierarchy UIActionButton_Attach object returns to the original position
Note: If you will break the prefab that is UIActionButton_Attach and then create a new one, Hierarchy will stay up as it was before the Play mode
Note: Cases 589430 and 668282 are with the same problem, but they were fixed, so there is regression
Reproduced on Unity 2017.1.0f1 and 2017.2.0b1
Could not check on Unity 5.6 because scripts becomes corrupted
-
Olulekan01
Dec 24, 2019 10:24
I cannot believe I'm reading a wonderful presentation like this. You have really done a great job gathering this great and interesting experience. Thanks for sharing. For further experience:
https://www.happybirthdaysisters.com
https://serc.carleton.edu/person/129726.html
https://www.sbnation.com/users/Olufajo%20Olulekan%20Victor.
-
JacobSmaga
Sep 11, 2017 12:45
2017.2.0b10 Still has the problem.
-
DeepfieldVR
Sep 10, 2017 20:14
I have this issue with prefab UI elements in Unity 2017.1.0p4.
A temporary workaround is to break the prefab reference.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2018.4):
Fixed in 2018.4 LTS (tested with 2018.4.27f1)