Hi Sherman, I don't think your code is in error, nor that AutoTransform or small feature culling is in error, rather it's unfortunately chicken and the egg "which came first?" type dependency.
The ways to break the culling of custom node in the first frame would be: To switch off small feature culling or set its value very low. To override the computeBound() of the AutoTransform so that it returns an invalid bounding sphere for the first frame till its been through the cull traversal once, once its been set correct then let the bounding sphere be computed correctly. To override the computeBound() of the AutoTransform so that it returns an large default bounding sphere for the first frame till its been through the cull traversal once, once its been set correct then let the bounding box be computed correctly. The two later solutions could possibly be rolled into AutoTransform itself. Robert. On Mon, Aug 25, 2008 at 2:53 AM, sherman wilcox <[EMAIL PROTECTED]> wrote: > I've attached a small demo app that illustrates an issue I've > discovered (known?) with AutoTransform nodes and small feature > culling. Briefly summarized, if I add a custom AutoTransform node (see > code for trivial example) to the scenegraph just under the root node > everything seems fine, with or without small feature culling enabled. > However, if I add this AutoTransform node as a member of a osg::Group > and then add the group to the scenegraph then this node's accept > function no longer is called after the first traversal if small > feature culling is enabled. However, if I disable small feature > culling all is well. > > Is this a bug or am I doing something wrong? > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
