Hi Roni, The CompositeViewer is written specifically to address your usage model. In 2.2 there is no performance and feature penalty in use CompositeViewer instead of Viewer as they both now use the same ViewerBase class that provides all the threading and rendering setup.
The key difference between the two class is conceptual and functional associated with high level view management - CompositeViewer "has" one or more Views, Viewer "is a" View. While a single View can have multiple slaves these slaves aren't meant to support the rendering of a single view - for instance a single view out of car through multiple windows uses multiple slave cameras that all relative to the master camera's projection and view matrix - what they aren't intended to do are have provide multiple views from multiple cars. As soon as you start mixing multiple views within a single View you are in really tangled mess both conceptually and functionally, and with such a mess will come confusion and bugs. Robert. On Jan 1, 2008 8:21 AM, Roni Rosenzweig <[EMAIL PROTECTED]> wrote: > Hello > I'm writing an application which needs multiple cameras. Some will look at > the same scenedata, some won't. Some will move together, and some will need > their own seperate position update. > > I have 2 options I'm considering: > 1: composite viewer with multiple viewers > 2: 1 simple viewer with slave cameras > > I don't know for sure which option to choose. > If I choose #2, can I set a different camera manipulator for each slave > cameras? > On the other hand, if I choose #1 will it run slower? (I could have as many > as 100 cameras/viewers) > > Any tips will be appreciated > _______________________________________________ > 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
