Thia is a bit of a weird one. Overlays seem to either end up going below or above everything else on the plane depending on if a plane master is present.
I'll drop in some more info when I figure out what's going on
ID:2025641
Jan 27 2016, 3:19 pm
|
|||||||||||||
Not a bug
| |||||||||||||
Jan 27 2016, 3:26 pm
|
|
This partially seems to have to do with me trying to use a screen object to fill in a "background" for the plane. Not sure how you're supposed to do this with the new HUD layering rules.
|
Seems that even using a normal object at layer 20, the overlays of a lower object just go above everything anyways, even though the main object is far below.
|
That sadly limits me to either placing whole-plane operations either below or above the whole thing, could be somewhat limiting.
Either way, the problem here is that overlays seem to layer basically however they want within planes - even above HUD objects (wedging those inbetween the "main" object and the overlay). Not even KEEP_TOGETHER seems to help. |
Can you give me an example of how the overlays aren't working? Any kind of test case to look at?
|
image/fuck If "foo2" is green, "" is red and "foo" is black, this produces yellow for some reason. It seems the overlay is just going under everything in this case, but I've had it appear pretty much wherever it wants. |
I tried out your test and was able to figure out the problem: The image you added does not have the same plane as the parent object.
Planes aren't inherited, so that's why. I suppose I can see some justification for inheriting when plane=0 though. That's something I should consider. |