Hi Gert, Glad to hear that you have your app back up and running.
I do wonder if it would be worth use adding a setDataVariance(DYNAMIC) any time a user applies an update callback to a Drawable of StateSet, its perhaps a little overprotective but as this problem seems to biting a number of developers perhaps its reasonable. Robert. On 9/14/07, Gert van Maren <[EMAIL PROTECTED]> wrote: > Hi Robert, > > > Is this in your own application or one of the OSG examples? > > It is our own app. > > > Are you creating text and then updating per frame? > > We're creating text and using UpdateCallback to add. > > > Are you running osgViewer multi-threaded? If so which threading model? > > Well when I run dual core the OSG automatically picks the > DrawThreadPerContext model -> crash. If I turn dual core off -> > SingleThread no crash. > > > One possibility is that the new DrawThreadPerContext threaded model is > > overlapping the drawing of the text with any updating of the text. > > The way to prevent problems like this is to explictly set the data > > variance on the text to DYNAMIC so that the draw traversal knows to > > hold back the next frame till all the dynamic objects have been > > dispatched. You can ensure this via: > > myText->setDataVariance(osg::Object::DYNAMIC); > > Great, that did the trick > > Thanks Robert. > > > > > -- > Gert van Maren > > Head of Research & Development > K2Vi Virtual Reality Software > Data Interface Technologies Ltd > > Phone: +64 21 2855581 > Email: [EMAIL PROTECTED] > Web: http://www.k2vi.com > > _______________________________________________ > 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
