Hi Robert -- The bin mode parameter of setRenderBinDetails doesn't appear to
be clearly documented. Looking into it, it's somewhat confusing. I'm hoping
you can tell me what affect one should expect when setting one of
INHERIT_RENDERBIN_DETAILS (default), USE_RENDERBIN_DETAILS, or
OVERRIDE_RENDERBIN_DETAILS.
As near as I can tell, these only have an effect on the state graph
constructed by the CullVisitor. Perhaps it'd be useful if you could
elaborate on the state graph and how these values control it?
In my own tinkering, I've found that INHERIT_RENDERBIN_DETAILS produces a
nested processing order, as we've discussed previously on this list. Three
nodes with bin numbers 1, 2, and 3, with the Node using bin 2 having two
children, and the two children use bin number 0 and 5 (or, graphically:)
Root (bin details unspecified) Group with 3 children
NodeA (bin# 1)
NodeB (bin# 2) Group with 2 children
NodeBsub0 (bin# 0)
NodeBsub1 (bin# 4)
NodeC (bin# 3)
With INHERIT, I get the following render order: NodeA, NodeBsub0, NodeBsub1,
NodeC. NodeBsub0 and NodeBsub1 inherit their parent's bin number for
processing relative to the parent's siblings. This makes sense, and I can
document it.
If I set all nodes to USE, the render order is the same as INHERIT.
However, I do get interesting results if I set all nodes to USE _except_ for
NodeB, which I leave as INHERIT. In this scenario, render bin numbers appear
to specify absolutely rendering order: NodeBsub0, NodeA, NodeC, NodeBsub1.
I've yet to find a use for OVERRIDE.
Any light you can shed would be appreciated. The code is not clear.
Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com <http://www.skew-matrix.com/>
303 859 9466
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
