Hi Paul,
The osgdepthpartion example would be best rewritten as a Viewer with slave Cameras, rather than a CompositeViewer with multiple Views. The reason for this is that depth partition cameras are conceptually work on the same view, and are locked in sync with the view and projection matrix of the master camera. Robert. On Fri, Apr 18, 2008 at 12:28 AM, Paul Martz <[EMAIL PROTECTED]> wrote: > > Hi all -- Another one of the examples that forces SingleThreaded is > osgdepthpartition. I keep intending to rewrite it using CompositeViewer with > ordered view processing, but haven't gotten around to it yet. > > In a nutshell, if any code executed by the cull or draw threads (such as > your own callbacks or custom nodes) isn't thread safe, then you must use > SingleThreaded. > -Paul > > > > ________________________________ > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jason > Beverage > Sent: Thursday, April 17, 2008 11:40 AM > To: osg users > Subject: [osg-users] When must you use SingleThreaded threading > model > > > > > Hi Robert, > > I was looking through the examples and noticed that osgphotoalbum, > osgdistortion and a few of the other examples are explicitly setting the > viewer to SingleThreaded threading model. Is there anything inherit in > those examples where you *must* use the SingleThreaded viewer model rather > than the others? Just curious as I'm trying to get my head around the new > OSG threading models. > > Thanks, > > jason > > > > > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
