Re: [osg-users] getOrCreateStateSet called from outside the main thread

Hi, I've been away for two weeks, and now returning to this issue. Just wanted to update in case my findings are useful to others. On further investigation, I realised that calling getOrCreateStateSet on a newly created text node will return a pointer to a 'singleton' instance of a stateset. I

[osg-users] getOrCreateStateSet called from outside the main thread

Hi, I'm hoping someone can shed some light on an issue we are having, running OSG 2.8.2 (redhat 5.3) in single threaded mode and creating scenegraph components on a background thread. Basically, we are using a background thread to build up scenegraph components and then adding them to our

Re: [osg-users] getOrCreateStateSet called from outside the main thread

Hi Paul, Node/Drawable::getOrCreateStateSet() isn't thread safe so should only be called from a single thread, or called from threads that serialize access to it. If you are calling getOrCreateStateSet() on objects managed by your background thread then this should be fine, but if you are

Re: [osg-users] getOrCreateStateSet called from outside the main thread

Hi, Thanks for the reply Robert - just to confirm, we are indeed calling getOrCreateStateSet on nodes created in the same thread and not back in the main thread, so as you say, it should work fine. I shall run our app against a debug version of osg and try and get some more details of the