Unity 4.5 New Hierarchy Window sorting

I don't understand this sorting - Why is it if I manually order objects in the hierarchy, pressing Play in the editor will automatically move things around and once I stop it doesn't go back to what I had? Is this a bug or expected behavior?

 

I don't see that behavior. If I put stuff in a certain order, it stays like that.

--Eric

 

I'm only noticing it in one particular scene - strange. Oh well.

EDIT: Ok, I've figured it out - definitely a bug it seems? The manual sorting works as expected except when I have objects that are cloned via Instantiate(). I have some pooling stuff happening and as soon as the gameObjects are created and are added to the hierarchy, it permanently completely screws up my ordering.

Can anyone verify this? Or am I just doing something wrong/misunderstanding? Thanks.

 

What's annoying most is that when I Ctrl+D, the new object appears in the bottom of the whole list other than appearing next to the object being duplicated.

 

Current implementation IS inconsistent. The order has different behavior based on the object type (i.e. sorting the drawing order of GUI vs. "normal" game objects like cubes where it does not affect the z-ordering..). The idea of some special container for GUI object is actually very good. Why you have to mess up the functionality of the whole Hierarchy view just to get the new GUI sorting to work? Expecting lots of problems when doing things dynamically from script...

 

I have already submitted a bug report.
It doesn't matter if you have alphabetical sorting or not.
As long as you have an active hierarchy window open with a very large scene, the editor will freeze up whenever the hierarchy window tries to refresh, which happens every time you click on an asset in the project window, or if you change object hierarchy during runtime

In a new project, just create a scene with 10K+ empty game objects. Open a few hierarchy windows. Click on any asset in project window and your editor WILL freeze for minutes.

The moment you close or "hide" the hierarchy windows by adding a different tab over it, the problem will disappear.

 

Yup, the same thing happens to me. Have you submitted a bug report?

 

Not yet - wanted to verify if this was happening to anyone else or if it was just me doing something wrong. Good to know.

 

Your description "permanently completely screws up my ordering" is a bit vague. I've tried to reproduce your problem, but can't. Creating many random child/parentless objects didn't effect my current order at all.

It appears that all newly instantiated (non-child) objects are placed at the very top of the scene hierarchy. While any instantiated child objects are placed at the very end of the parent's hierarchy. I suspect that your "bug" is in the object pooling system code itself. Is it messing with the parent/child transform relationships?

Any newly added/duplicated object created in the editor is automatically placed at the end of the scene or parent hierarchy. This is probably by design to ensure that the existing order of things is not tampered with. Having a manual alphanumeric sorting option like the one I suggested earlier could help with this issue.

It also seems like an in-depth article on the blog about the actual functionality and reasoning behind the changes to Unity's sorting system could be quite beneficial to the community and perhaps help clear up some of the confusion and frustration.

 

I have a similar problem, but it happens in a different way.

I have a prefab with 9 children, ordered in a certain way.

I add a new child in this prefab transform.parent = prefab.

Then when I click on Play, all the transforms are randomly moved, and when I come back to the editor mode they keep their strange order.


Another bug:
- I use the script to set the transform alphabetically. It works in the editor.
In a Start function, I get all the children of the prefab and put them in an array.

When I read the array, the children are in a random order (as described above), while in the hierarchy they are in the alphabetical order...

 

Can I get list of game objects exactly as in hierarchy window?

A
---B
---C
------D
E
F
---G


as

ABCDEFG


I have not very big 2d scenes and want to automatically set Order in Layer by hierarchy order.

 

Thanks. Please add in future releases Unity Editor API method for getting hierarchy tree by sorting method. Hierarchy is a valuable part of development and it will be usefull to have its structure.

 

It's buggy.
I reorder my game object, hit play, and the hirarchy reset.
So there is no way for me right now to get my old hierachy and to be able to use the new GUI system when it will be out.
I had game object name: Map1_, Map2_ etc.. Now it's Map1,Map3,Map12 etc..
The reorder is not saved. So nice buggy feature. Did you test it ?

> a) Its often better to deliver one consistent 'way of doing things', than special case objects in the same list, having this > two ways to order inside the list, users would have to actively think about which areas of his hierarchy are reorderable > and the ones that aren't.

Typical Prog mistake: try to manage a particular case (GUI) into generic (object hierachie).
There is no improvement into the hirarchy. Now you can't find object by following the alphabetical order anymore...

You could have:
- Add another way to order GUI Layer (flag, tag, editor etc..).
- Handle 2D gui in a particular way inside the hierarchy of your canvas children (adding a layer icon/color etc..)
Both solution are better.

Also one big mistake:
- When we "import" our project with the Unity 4.5, the alphanumiracal should have been kept. And if the user want to reorder he can.
I don't see any reason why the migration messed with the hierarchy and force us to reorder everything like it used to be.

But one good thing:
- You can add your own script to reorder objects.

 

Yes, I discovered this fact when I was doing some testing with the new & old hierarchy views. It explained a strange problem I had before: When adding child objects to an array in code they always seemed to be stored in a random order completely different from what I saw in the hierarchy. I now realize that this was because the hierarchy view I was seeing before was not the true order of the children at all!

Being able to see the real order now is a big improvement, but letting users use both the fake/real sort views is only asking for big problems. I think the only real solution would be to remove the fake sort view completely and replace it with a real alphanumeric sort option. You wouldn't necessarily need to expose the feature in code. Just let users perform an alphanumerical sort in the editor on command.

I've tried to reproduce this random sorting bug with no luck. Could you upload an example project or script of the problem for me to test out (after you submit the bug). I don't understand why the order would remain messed up after exiting play mode. Are you modifying prefabs at runtime?

 

Is the object a prefab? If you reorder children inside a prefab and don't apply the changes to the prefab. It will revert back to it's default state upon entering play mode.

So it turns out that the old alphanumeric sorting view was only a "visual" thing like Phil said earlier. Meaning you weren't actually seeing the real hierarchy at all! This is why your upgraded projects look like a mess. You now get to see the ugly truth!

I do agree that they should have had some kind of feature in place to correct this issue when upgrading projects, but maybe it was too hard to implement yet. However, I'm sure they will come up with a good solution to fix this.

 

Nope, it stays where you put it; that's what transform order means. It doesn't get re-sorted, since there is no other criteria to be sorted by.

--Eric

 

The naming is somewhat misleading. "Transform Sort" shows how everything is actually organized. "Alphanumeric Sort" only changes the way the hierarchy is displayed, but doesn't actually sort anything. If you try moving objects around and then switching between the two sort modes you'll see this.

 

So hitting "play" mess your prefab? That's a bug, don't you think? "Play" shouldn't change anything in your project.
The order of the game object in the prefab should be like any informations, you can override it for your instance.
Yes that's a little complicate to handle, but that's how it has to be done if you want to keep Unity "clean".

The hierachy view is a view to facilitate user navigation. I really don't care what's behind it and I shouldn't.
That's how you need to think when you work on a user interface.
You can let the user reorder object. But only when he wants it...

They should at least give us a script that reorder game object permanently (and not only in the view). So we can get our project like they used to be.

 

I am adding some transform inside the prefab in a Start function, with transform.parent = prefab.

I will try tu submit the bug.

By the way, when doing "transform.parent = prefab", is it possible to chose the position of the transform? Can we change the order of transforms at runtime by script?

 

You're right. I guess I never thought of it as a bug because It's just restoring the prefab to it's original state, but it shouldn't do that and this will cause a lot of problems.

I completely agree with everything you said here. I was only trying to explain why the upgrade seemed to mess up your project, but your right in that users shouldn't need to care about the "why". They just want to use it the way they expect to use it.

 

You don't see why you need to display things in Alphabitical order. Is it a joke ?
How your system file manager works ? Why is it working like that ?
One other big reason: it's because Unity was working that way for many years. People have organize their project with this constraint. Sometime you need to change things and you can't convert everything. But that's not the case here

Couldn't you keep the old order when doing the conversion from 4.3 to 4.5 ?

Let's imagine that I use your script to reorder of how game objects are displayed. But imagine that at the same time I want to modify the order of the GUI layer -> possible or not ?
It's going to be a problem that you will have with every script that reorder game object hierarchy. I'm not sure you had think about that.

View order and layer position are correlate, but you want people to use script to change the display order like if it was not correlate. It's not going to work But maybe I made a mistake (I didn't tryied the GUI..)

And I'm not telling that you should keep the old system how it was. I say that you should have done the conversion better.

 

This ... thing is driving me crazy. I have to search for my objects evert time I want to select them. No I do not want to sort their order by hand every time I add an object. Also moving their order is such a pain in the ass. It's a challenge on its own. God forbid if you dont aim for the right pixel now you have a bunch of objects become child of another. Is this going to be fixed or not?

 

Thank you phil for your answer. I don't know if I will have time to fill a bug report (I shouldn't write on this forum right now..)
I, of course, don't say to store the data alphabetical forever by using some type of container
Just a script that reorder them when a user ask for it.

You are free of not being fond of the alphabetical order, but that's very convinient for most people.
That's why file manager use this convention and that's probably why previous Unity version use this convention.

 

I am making an editor extension right now that will allow users to permanently sort the hierarchy alphanumerically. I'll post it here ASAP. Please stand by...

 

Okay here it is. I'm calling it the "Hierarchy Organizer". You can download it over here on the new forum topic.

 

I submitted a bug: 612637

There is no script in the projects, just a few transform inside a parent prefab. When hitting Play, the transforms in the parent gets reordered, and remain like this when quitting.
I have 3 transforms in the parent: 2 "normal" ones and a prefab. If I put the prefab as the first child, then it becomes the last one when hitting Play. If I put it at any other position (aka not the first one), then it's fine.

I hope you will manage to reproduce it with my project.

 

Interesting... It appears that this random resorting bug is related to the prefab override bug.

 

Great thank you.

 

Hi!

I have done this task in current Unity version. Script must be a sort of:

Code (CSharp):

1. using UnityEngine;
2. using System.Collections;
3. using UnityEditor;
4.  
5. public class SortOrderClass : Editor
6. {
7.     [MenuItem ("Quest/Resort sprites")]
8.     static void SortOrder ()
9.     {
10.         EditorApplication.hierarchyWindowChanged += SortOrderCallback;
11.         SortOrderCallback();
12.     }
13.  
14.     static void SortOrderCallback ()
15.     {
16.         SpriteRenderer[] all = GameObject.Find("Stage").GetComponentsInChildren<SpriteRenderer>(true);
17.         int value = 0;
18.      
19.         for(int i=0; i<all.Length;){
20.             SpriteRenderer sr = all[i];
21.          
22.             SpriteController sc = sr.gameObject.GetComponent<SpriteController>();
23.          
24.             if(sc.renderAfterChilds){
25.                 int count = i+1;
26.                 while(count<all.Length){
27.                     if(!all[count].transform.IsChildOf(sr.transform)){
28.                         break;
29.                     }
30.                     ++count;
31.                 }
32.                 sr.sortingOrder = value + (count - i - 1)*100;
33.                 ++i;
34.             }else{
35.                 sr.sortingOrder = value;
36.                 value += 100;
37.                 ++i;
38.             }
39.          
40.             EditorUtility.SetDirty(sr);
41.         }
42.      
43.         SceneView.RepaintAll();
44.     }
45. }

 

I'm cool with this as long as it would work and there would be a way to sort the scene or parts of it reliably (ie. no perf hit crashes or anything).

If you have prefab instances in the scene, the sorting goes wonky when loading. It's broken. Also the fact that you need to implement a editor script to get alphabetical sorting for the hierarchy is just insanely stupid.

I would be so awesome if Unity would bother to properly test these kind of fundamental changes before releasing them in the wild.

 

Something useful at last ! Thank you! Thank you very much! The new hierarchy is crap, I can't find a thing.

 

I have not grabbed 4.5 yet but I love this update as @leo.carneiro mentioned , it's consistent with how most other software display lists work .. index based with manual drag and drop change support!

but Im sad to hear about the performance bug @Ares Games reported , this is enough for me not to download 4.5

 

a) Then based on that comment of "being consistent" I would suggest a component<GUI_Object> that is attached to a GameObject that can be moved up and move down the list like other GameObjects with components. That gives the expected function of being alpha sort with the ability to layer sort GUI items.

GameObject_MainMenu
- component<GUI_Object> Titlebar
- component<GUI_Object> Play Game
- component<GUI_Object> Options
- component<GUI_Object> Credits

GameObject_GameHUD
- component<GUI_Object> Points
- component<GUI_Object> Lives
- component<GUI_Object> Radar
- component<GUI_Object> Options

where moving component<GUI_Object> up and down changed its GUI.Index based on its location in the Component array index.

That is how myself personally would see changing the sort order to accommodate your new GUI (which I admit to not having seen yet) as being consistent to other interfaces in Unity Editor.

b) /crickets

c) Transform sort keeps changing in my project regardless of how I manually sort things. So I have given up manually sorting things every session; added a script to alpha sort and when I have to address the new GUI system I will end up manually indexing the GameObjects as "~10", "~20", "~30". I waste more time locating objects in the "Random" Transform Sort "feature" than getting work done.

Thank you for your consideration.

 

How is this "being consistent"? You are talking about creating "special case objects" with a system that was not designed for it. You can't make an object a "component" of itself or another, that isn't what components are for. This is completely inconsistent with the way Unity works.

If you want to manually sort objects you have to do so by transform. Creating another special system just for sorting GUI elements sounds like a very bad idea to me. What happens when you want to manually sort something other then a GUI object?

 

Educate me, I'd like to learn something; why would I want to make a "GameObject" into a "Component"? Perhaps my comment was a bit vague. If this whole sorting issue is to accommodate GUI Objects, why can't they be (new flavor of) GUI Components rather than GameObjects? Then I could enable/disable whole GUI systems by enable/disable their GameObject? Not unlike what we (I) do to enable/disable the Scripts on said GameObjects. As most of my GUI scripts reuse the same variables over and over (Actually I use a custom class, but that's besides the point).

Second question so I might learn something today; Why would I care what order transforms are in (other than GUI layers)?

Regardless of how it ends up being done in the end my issues are/were;
a) Manual sorting doesn't stay put. It changes between session to session and from "Play" to "Stop". Just when you think you know where to find something (especially if you spent the time to manually sort things [repeatedly]) they shift about. (as already mentioned)
b) With Transform-Sort finding things is very time consuming; relative to alphabetically. (see comment A). (Network debugging is fun enough without breaking train-of-thought to locate something that starts with 'A' and can't be found; where I put it, where it should be, where it might be, or near the top of the hierarchy... /Squirrel!
c) The upgrade process should have left things where they were rather than jumping out there and screaming "Surprise!". From there, they could continue as Transform Sort if they must. (as you stated above)

I get that most people are resistant to change - I like to consider myself relatively flexible. Unity's Transform-Sort has consumed my time with locating objects rather than debugging my (network) code. In short, so-far a not so "useful" but time-consuming feature (subject to change). And as this is a 'hobby' and not my day job, I am far too engaged in this conversation for only intending to offer an opinion/suggestion.

Thank you for your time ---

 

This is a fairly big deal. I (and apparently others), would really....really like UT to take another peak at an integrated alpha sort option. On behave myself and the others caught off guard with this 'feature'...for the love of God, if you are going to change something so base and expected in the software, perhaps someone could float the proposed change publicly first instead of steamrolling it through? Good or bad, useful or just annoying, this was a significant change to workflow. Springing this 'feature' on your user base(even if some think it's better than sliced bread), then telling us to live with it seems...arrogant and dismissive.

 

This is going somewhat off-topic, but I'll try to help explain.

I think you meant to say "why wouldn't I want to make an object a component?" Objects have components, but components are not objects. You can create a component (script) that references an object(s), but the component itself is not an object. This is an important point to remember. Components are only used to define what an object is and how it functions.

A component is just a part of an object and if you look at the new GUI system, you will see that each GUI object has GUI components attached to it. So GUI elements are components already, but they have to be attached to an object! This is because you need to have a way to group multiple components for a single GUI element together.

You can also disable objects just like components. So you already can enable/disable whole GUI systems this way.

It's very useful when you want to keep something at a particular position in the hierarchy, Like a game manager object, etc.. Actually, the whole point of manual sorting is to make things stay where they are. It sounds like you're experiencing the bug that's randomly changing sort order on play mode. I also agree that there should of been a way to preserve the original sort order when upgrading to 4.5.

I'm sorry to hear that. I think automatic alphabetical sorting is great for a lot of things, but not always a good thing. I'm sure unity will come up with a good compromise for this.

Have you tried my Hierarchy Organizer tool? It should help you some.

Edit: Thanks Superpig! You beat me to it and probably addressed chargedneuron's questions better then me.

 

I thank you both for the detailed explanations.

I will have to think deeper on this; with my programming style I have no use for Transform-Sort (at this point) - other than for GUI Elements (regardless of their actual form) which I already control via my Window Manager Script Component. (I fully understand the difference between GameObject and an attached Component, but I thank you for the explanation all the same.)

A large part of my Network based game calls for Prefabs to be instantiated; my "Spawners" assign their instantiated objects as children (for internal logic reasons). I am certain that the use of these Prefabs is what is scrambling my Hierarchy when I use Transform-Sort.

Isaiah Kelly; I use the Editor Script near the top of this thread "AlphaNumberSort.cs" - (Credit to StarManta for pointing it out on page 1) Thank you for also providing a stop-gap solution.

My NPCs use a Script Component to not only monitor their waypoints but also their "isThinkingAbout" values (in short, none of my waypoints would ever be just a Transform without a Waypoint Script Component attached, which also handles sorting). They sort themselves out on Awake() and locate the waypoint nearest to the NPC regardless of where the NPC is relative to the waypoint chain. So no need for a Transform-Sort there; but I understand your example.

I will think more on your examples but I'm not sold on the Transform-Sort idea yet - the scramble bug isn't helping either.

I apologize for continuing to grind this topic, and I thank your and applaud you for your efforts.

(PS - As I look at my Hierarchy behind this window, it has ignored the Alpha-Sort and scrambled again... Back to work.)

 

This thing is a huge mess! It feels like it was one of those new "features" that got zero testing and was rushed out of the door. Can't believe that such a fundamental thing was so overlooked.

In my projects I have no idea what's going on with the hierarchy... Sometimes objects appear to sort alphabetically, sometimes I position them manually and next thing I know everything is mixed again...

Unity, please get your stuff together and fix this!