> Well, the problem is that physics don't run at the same rate as > display. For instance, we should run a "physics update traversal" > at 100Hz, and the "normal" update traversal the fastest possible > (well, limited by the VSYNC).
Then the physics update would run in a separate thread, and you'd need some mechanism to "pull" the physics state into OSG during the update traversal. I guess I don't understand why this "pull" couldn't be done in the existing update traversal. > > You can always fire off custom traversals from the existing traversals. > > Hum... do we need to modify the viewer source? I guess so... I think what Robert is talking about is something like launching a physics simulation step from a root node update callback (for example). This doesn't require modifying osgViewer. But I don't think this would satisfies your requirement to run the physics simulation at a different rate from the display. Paul Martz Skew Matrix Software LLC http://www.skew-matrix.com +1 303 859 9466 _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
