Stephan,
See Robert's response below in a thread entitled "setUpdateCallback
fails under slave-camera"
Martins
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 4/27/10 4:00 PM, Stephan Huber wrote:
Hi all,
before starting a debugging session I'll ask the community:
(using osg 2.9.x, revision 11314)
I have the suspicion, that update-callbacks are not called for nodes who
are childs of a slave-camera. If the same child with it's update
callback is added to the main camera or via setSceneData, the
update-callback gets called. Adding the same node to a slave camera will
disable the update-callback. (I am adding the slave-camera with
useMastersSceneData=false)
Is this intentional? If not I'll try to debug the scenario and send a
fix if possible,
cheers,
Stephan
_______________________________________________
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
