robert.osfield at gmail.com
Wed Sep 17 05:06:47 PDT 2008
In all the OSG 2.x series the DataVariance is used during the draw
traversal to monitor when all DYNAMIC StateSet and Drawables have been
dispatched, as once they have been the next frame can be started in a
parallel with the remaining STATIC objects are rendered (in
DrawThreadPerContex, CullThreadPerCameraDrawThreadPerContext threading
On Wed, Sep 17, 2008 at 12:54 PM, <paul1492 at yahoo.com> wrote:
> In OSG 2.6, is the DataVariance value only used by the Optimizer or is it also used during the frame processing?
> I've had some problems in the past with the StaticObjectDetectionVisitor and the Optimizer (assume "sharing" part of the Optimizer) doing some things to my scene graph which cause it to render incorrectly when I don't specify my DataVariance as being DYNAMIC.
> Is there a reason why there is a StaticObjectDetectionVisitor being done when setSceneData() is performed independent of the Optimizer settings? Is the DataVariance value used by something other than the Optimizer?
> Paul P.
> osg-users mailing list
> osg-users at lists.openscenegraph.org
More information about the osg-users