Hi Pail, The default setting of DataVariance is UNSPECIFIED. There has been lots written on this topic, please go look at the archives.
Robert, On Wed, Oct 8, 2008 at 7:17 PM, Paul Melis <[EMAIL PROTECTED]> wrote: > Robert Osfield wrote: >> >> On Wed, Oct 8, 2008 at 6:21 PM, Paul Melis <[EMAIL PROTECTED]> wrote: >> >>> >>> Hmmm, if setting it to STATIC causes a crash like this, might that be a >>> design flaw? >>> >> >> Is a design constraint for when running in DrawThreadPerContext or >> CullThreadPerCameraDrawThreadPerContext threading models as these >> threading models use the DataVariance of StateSet and Drawable to >> decide when it's safe to let the next frame advance. Lots has been >> written on this topic on the mailing list over the past year and half. >> >> If it you think it's a "flaw" then you just just stick to >> SingleThreaded or CullDrawThreadPerContext threading models and forgo >> the performance benefit that this "flaw" provides. >> > > Please don't get sarcastic, I did not mean to offend you. > > I'm merely looking at this from a user perspective, in which an object > member can take on two values where one value (DYNAMIC) provides an > optimization that might not be of immediate interest to the average OSG > user, while the default setting (STATIC) causes OSG to exit with cerain (ok, > non-standard) threading models. And updating text values during rendering > does seem like a fairly straightforward operation that should not result in > too many surprises. > > Would it be a solution to set the data variance to DYNAMIC as soon as the > text's value is set the second time? > > Regards, > Paul > _______________________________________________ > 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
