On 8/3/07, Robert Osfield <[EMAIL PROTECTED]> wrote: > Hi Doug, > > There are number of hoops one has to jump through to do safe > multi-threading with the OSG, osgViewer does these all for you, while > SceneView knows nothing of it and requires higher level classes to > handle it. osgViewer itself does use SceneView so does illustrate > that it is possible using SceneView so you could possible use this as > guide. > > Personally I'd recommend that VRJuggler just use osgViewer for > creating the windows and cameras as per the configuration required by > VRJuggler, this way you can take advantage of all the threading models > that osgViewer provides in a way that is known to be thread safe. > > Another key advantage of adopting osgViewer is that problems you see > will be much more reproducible by others who don't use VRJuggler. > For instance you could create a scene that uses a ClearNode and run in > standard OSG examples, and if the problems exists then I and others > can look into it. > > With the current state of play, trying to help diagnose what might be > up would require a massive time investment in getting VR Juggler > installed, learning about it, setting up the case that reproduces the > problem, then stepping through to see where the problem lies.
Actually, all the OSG code for VR Juggler is contained in one header file: http://developer.vrjuggler.org/browser/juggler/branches/2.2/modules/vrjuggler/vrj/Draw/OSG/OsgApp.h Could you give this file the once over and alert us to any problems? If you have any questions I can certainly try to explain what is going on. -- Daniel E. Shipton Software Engineer, Infiscape Corp. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
