I have a relatively complex scene with several objects in it. I want to make sure that Away3D always renders one of those objects last.

I want to use the Context3DCompareMode.GREATER mode on the material of said object, so that only the pixels that are behind other objects are rendered.

But this obviously doesn’t work if it isn’t the last object in the scene to be rendered. Can someone help me with this?

Okay, I’ve looked into the source code of Away3D, and I know now that by default, all entities in the scene will be put into a single NodeBase object contained by one Partition3D object.

But I still don’t know how the order of the EntityNodes in the NodeBase object comes to be.

The order in which the objects are added to the scene or any containers doesn’t seem to make any difference. Can anyone give me some insight on this?

Not sure if it would work, but maybe try creating two views using stage3Dproxy.
Like here:
http://away3d.com/tutorials/Away3D_and_Starling_Interoperation

But instead of creating Starling layers, make a second Away3D layer.

Then, place the ‘front’ 3d object on the top layer and the rest on the bottom.

Haven’t tried it, but I think it’s worth a try.

Thanks, that did help!

I tried doing something similar, but I hadn’t seen this tutorial before.

It’s working now, though having more control over the drawing order in Away3D would still be nice.

They have added a zOffset property to the Entity object (it’s not finalized yet, you have to download the dev branch) which can be used to manually control rendering order of transparent objects.

So if you enable alphaBlending in your object and set a large positive number to zOffset you can force it to be rendered last (appear in front).