Draw-Order issues since 5.1.0f3

Unity Engine
1

Hey guys,
I have (had) my UI-System up and running. But since the update to 5.1.0f3 I am having weird draw order (?) issues:
2170046--143592--DrawOrder.png
The image is being rendered as being “behind” the slightly transparent button. The “offset” of the image is actually the image being moved towards the camera for presentation purpose. Issue is the same when looking from the other side. See bottom right of the image for scene hierarchy.
When moving the image out of the hierarchy and below its parent, the draw order is working correctly.

Any ideas? Thanks!

2

I have tried around a little. The issue seems to arrise from overlapping elements. See attached Screenshots:
2170404--143608--OverlayError.jpg
Some observations:

  • None of my scripts works with drawing orders.

  • The issue takes transparency “into account”. So: Deactivating the red button square of the top (image component of button) will draw the bottom button correct again, until the first opaque pixel of the red cars touch the bottom button again:

  • 2170404--143612--OverlayError_PixelPerfect_2.jpg
    2170404--143612--OverlayError_PixelPerfect_2.jpg795×468 76.5 KB

  • There doesn’t appear to be a system regarding which elements create or receive the error. Button A corrupts Button B; Button C corrupts button A but Button B doesn’t do anything (and so on).

  • The change in draw order is also visible in the editor view, but only if the game is running.

3

I noticed the same issue. It comes and goes when I scroll through my UI. i.e. as it moves some things jump behind and in front of others.

4

I suppose you don’t have an solution? Any further Observation?

5

Get 5.1.1p1 when it comes out should resolve the issue

6

Thanks!
Any Timeline on that new release?

7

Its live now.

8

Hi Phil,

Do you know if there are any patch builds of 4.6x that have this fix in? I have similar problems with draw order on 4.6.6p3 and 4.6.5p4.

Also, what’s the IssueID?

Thanks.

9

then you must be dealing with a different issue then the ones i know about. the ordering issues that was fixed in 5.1.1p1 is the same fix in 4.6.6p3