Thanks for the info, Robert. > o OVERRIDE is effectively an instruction to ignore an > attempts of StateSet below it to set RenderBin's.
Understood. Can you give me an example of why someone would want to do this? > o USE says to either use the RenderBinDetails to create a > new RenderBin in the rendering backend for the subgraph' > geometry to be dropped, or to reuse a RenderBin already > created in the parents RenderBin for this purpose. > > The later reuse is important, consider the case of a > transparent bin, you want all transparent geometries to be placed > into the same transparent bin, you don't want every > geometry to have its own transparent bin. The reuse is chosen > simply on whether that bin number is already allocated > in its parent RenderBin/Stage. Right. I was somewhat stumped as to how transparency could work properly, which was what drove my investigation to understand further how the bin mode works. Makes sense now. > If you have multiple RenderStage (such as when doing > RTT) then you'll have multiple transparent bins generated, as > the parent RenderBin in this case would be a different > RenderStage, so the cull traversal will create a fresh RenderBin > for each stage. Ah ha. Glad I'm finally digging in and gaining a deeper understanding of this part of OSG. Thanks. Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com 303 859 9466 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
