Hi Karl, On Wed, Jul 22, 2009 at 2:14 PM, Karl Wurzel<[email protected]> wrote: > - osgterrain sets the threading model to SingleThreaded. Is there a specific > reason for this?
I don't recall a reason. It's primarly an example I've used for testing rather than 3rd party education. > - What about setDataVariance(DYNAMIC)? Is this generally necessary for all > nodes of the scene graph that are updated dynamically? Setting dynamic geometry and state to DYNAMIC is required to avoid crashes when you use the DrawThreadPerContext or CullThreadPerCameraDrawThreadPerContext threading models. > (all information I have found about this setting is somehow related to > osgText and freetype not being thread-safe) There is actually a ton of discussion and DataVariance and theading on osg-users over the years, I won't repeat it, please just do more extensive searches. > Code: > // enable the use of compile contexts and associated threads. > osg::DisplaySettings::instance()->setCompileContextsHint(true); It's a hint to the viewer to create a background pbuffer that is used to compile GL objects rather than compile them in the main thread. > - What is the difference between update operations and update callbacks? update callbacks get attached to nodes, the update operations get attached to the viewer. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
