Search Issue Tracker
Fixed in 5.3.1
Votes
6
Found in
5.2.0f3
Issue ID
732566
Regression
Yes
[Hierarchy] Order is not saved when scene is reloaded/started
Repro steps:
1) Open the project and test1 scene
2) Change the Divider position in Hierarchy window and save the scene
3) Play the scene and notice that the change in Hierarchy was undone
Regression after 5.1.4f1
Comments (32)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
sir_luke
May 27, 2016 21:35
I can confirm this issue is still present in 5.3.4f1...
Renegat
Apr 15, 2016 11:45
edit: had this issue in 5.3.4f1
Renegat
Apr 15, 2016 11:44
Can't believe this bug is real and not fixed sinced half a year! Can't build a proper UI at all, WTF?!
starikcetin
Apr 13, 2016 22:12
Issue is still there with Unity 5.3.4f.
mfontoura
Apr 08, 2016 09:42
not fixed please reopen
captainTfireball
Mar 23, 2016 20:16
I can confirm that this issue is still present in version 5.3.3p1. The order of objects in hierarchy is not saved when scene is closed and then re-opened.
Daemon0x0
Feb 04, 2016 15:28
If you want to sort hierarchy just go to Edit - Preference and tick Enable Alpha numeric sorting
http://docs.unity3d.com/Manual/Hierarchy.html
japotter
Jan 10, 2016 17:28
I found that putting all top-level gameobjects as children of an empty gameobject provides a temporary workout until this is fixed.
laurentlavigne
Jan 06, 2016 23:24
hierarchy order still broken in 531p2
IES
Dec 28, 2015 09:56
This is not fixed in 5.3.1 and Please reopened it.