I’m working on a project in unity 5.0 and when upgraded to unity 5.1 and the order of the UI elements in the hierarchy isn’t working fine for me. Some elements get behind their parent and they appear in the correct order when duplicating the children and disabling the original child. I have no idea how this works but that’s the solution I’ve figured out so far
Please report this bug.
I’ve isolated and reported a similar issue, they’ve replied that it was fixed and will be available in 5.2.
Maybe if they’ll get more reports of this issue, they’ll escalate the priority and the fix will be released sooner in a patch release.
same to me , a lot of elements disappear on 5.1 … I got to roll back to 5.0
We have the same issue,
I hope that they release some patch before 5.2
Report the bug and maybe they will
I have similar issues after upgrading from Unity 4.6.4 to 4.6.6. The order of certain UI elements randomly won’t follow their place in the hierarchy now. I’m trying to isolate it in a small project now.
Same issue here since upgrading to 5.1.
1 Like
Ditto here and reported. Very annoying.
Same for me.
Same for me on 4.6.5 and 4.6.6 releases. Will try 4.6.6p3 soon.
P.S. I think it is related to new batching algorithm: Drawcalls go up with the latest version of Unity 4.6 (4.6.4p2)
Same here when going from 5.0.x to 5.1.Will report the bug.
I believe it’s fixed in 5.1.1p1
Make sure to check the latest patch before reporting.
Hey Alexander, it happens in 4.6.6p3 as well so don’t bother upgrading. Hopefully they will put out a 4.6x patch for this as well.
Hey Gamba, 4.6.6p3 actually fixed my problems.
Has anyone reported this bug? Where can I vote for it?
Have you tried the 5.1.1p1 or 4.6.6p3?
I have tried 5.1.1p1, but there were other bugs with Linq. I noticed UI bugs only in Editor window (but not in the Game view and on device).
The UI order bug is still broken in 5.1.1p1.
I’ve rolled my project back to 5.0. 5.1 is not ready for production if you use Unity UI.
Edit: Just noticed p2 is out toay. But I’m sticking with 5.0 for now.
Im still affected by this and had to downgrade to 5.0, please fix!
so all the bugs i know about regarding this were fixed in 5.1.1p1 and 4.6.6p3 so if it still happens we need bug reports.