Hi Werner, On 23 November 2017 at 11:02, Werner Modenbach <[email protected]> wrote: > many, many thanks. That was exactly the cause of the problem. > I changed the callback to be an update callback and the delay is gone. > Better to say: almost gone. > When I turn my object via camera manipulator there seem to be no update > callbacks. > Is that right? Is there any way to get also this case catched by a callback?
By default OSG doesn't differentiate between frames based on what drives the frame. A viewer.frame() will always call the the update traversal which should in turn call all the update callbacks in the scene graph. I don't know what is happening in your application, I know nothing the application your have, there is no way I can guess what might be going wrong. It's technically possible to override default osgViewer behaviours, whether you do or not is only something you can answer. All I can say is the in a standard osgViewer based application event handlers like camera manipulators don't have any affect on whether update callbacks are called or not on the next frame, as long as the viewer.frame() is called appropriately an update traversal will happen. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
