Hello all,
> I was wondering if someone could give me some sample use cases for both
> osgViewer::Viewer and osgViewer::CompositeViewer, at a high level.
Let me ask the question differently.
We have an application which needs to be able to work on multiple screens, and
also eventually on a hemispherical projector setup (3 projectors). It will only
need to be able to view a single scene graph, but we need to be able to
customize each screen's point of view. Also, we need to be able to see some
text and overlays on one screen and not the other(s).
>From what I can see, osgViewer::Viewer with multiple slave cameras can do this.
The other option would be osgViewer::CompositeViewer with multiple views onto
the same scene graph. What are the pros and cons of each scenario?
I find the convenience of osgViewer::View::setUpViewAcrossAllScrens() is hard to
beat for simplicity of setup, and that uses one view with multiple slave
cameras.
I imagine that CompositeViewer is more flexible, but if we don't need this
flexibility and it adds unnecessary complexity, maybe it isn't worth it.
To sum it up, I just need some info about the tradeoffs involved to be able to
choose the most appropriate for the situation. In the past, I've never needed
anything other than the stock osgViewer::Viewer with the default settings and
call viewer.run(), but for these projects we have more complicated
requirements...
Thanks in advance,
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
