Hi Peter, The update traversal is currently only applied to the View's SceneData, not the individual Camera's subgraphs. This is typically desirable as you wouldn't want to run the update traversal multiple times on the same scene graph on each frame as it would be both inefficient and could lead to objects be moved multiple times.
I presume in your case your slave Camera is not share the same scene graph as the View's SceneData, is it a hud? special effect? One possible way to handle this type of usage model would be to have a flag on the slaves that enables/disables the update and event traversals on the Camera's subgraph. It would of be off by default. Another possible scheme might be to collect all the unique scene graphs attached to all Camera's and then traverse all these. Both of these would require mods to the core OSG. If you wish to modify the core OSG then just manually running an update traversal on these subgraphs would do the trick. Robert. On Fri, Nov 21, 2008 at 1:53 PM, Peter Wraae Marino <[EMAIL PROTECTED]> wrote: > Hi Users, > > We have a strange error (perhaps bug).. > > when we have a geode that has a setUpdateCallback and that geode > is a child of a slave camera then the callback is never called. > This is also valid for drawables update callbacks > > anyone? > > -- > Regards, > Peter Wraae Marino > > www.osghelp.com - OpenSceneGraph support site > > _______________________________________________ > 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
