CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
→‎Background: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28647.html
No edit summary
m (→‎Background: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28647.html)
Line 6: Line 6:


== Background ==
== Background ==
{{cquote|<nowiki>What i want to achieve: Multiple views of the same scene . Lets call them
View1 and View2(they may be on 2 separate screens). There should be only one
instance of flightgear running. I should be able to have "View1 = Cockpit
View & View2 = Chase View" or "View1 = Helicopter View & View2 = Cockpit
View" or any other such combination of views. I am using FlightGear 2.0.0
I should be able to switch the view in each viewport without affecting the
view in the other view port. i.e i should be able to double right click and
change the view on each display with the mouse without affecting the view in
the other display.
README.multiscreen in the FlightGear documentation says its possible to
create a master camera and a slave camera that is offset from the master
camera. BUT I want 2 master cameras that can switch to any view at any time.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28647.html|title=<nowiki>Multiple views without slaving to master camera</nowiki>|author=<nowiki></nowiki>|date=<nowiki></nowiki>}}</ref>|<nowiki></nowiki>}}
{{cquote|I have just been trying out the multiple screen feature in FG. I found that
{{cquote|I have just been trying out the multiple screen feature in FG. I found that
the GUI camera (including the menu bar, hud and 2D panel) appears in only
the GUI camera (including the menu bar, hud and 2D panel) appears in only
Line 40: Line 55:
{{cquote|That would require a change in current fg architecture to use a CompositeViewer instead of a single Viewer, but we're contemplating that anyway.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17263.html|title=<nowiki>Re: [Flightgear-devel] Cockpit displays (rendering, modelling)</nowiki>|author=Tim Moore|date=Mon, 04 Aug 2008 02:43:52 -0700}}</ref>|Tim Moore}}
{{cquote|That would require a change in current fg architecture to use a CompositeViewer instead of a single Viewer, but we're contemplating that anyway.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17263.html|title=<nowiki>Re: [Flightgear-devel] Cockpit displays (rendering, modelling)</nowiki>|author=Tim Moore|date=Mon, 04 Aug 2008 02:43:52 -0700}}</ref>|Tim Moore}}


{{cquote|The cameras in a camera group don't need to render directly to the
screen. They can render to a texture which can be used either in the
scene, like in a video screen in the instrument panel, or for distortion
correction in a projected or dome environment.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17001.html|title=<nowiki>[Flightgear-devel] RFC: changes to views and cameras</nowiki>|author=Tim Moore|date=Thu, 26 Jun 2008 03:53:05 -0700}}</ref>|Tim Moore}}
{{cquote|Open Scene Graph supports a CompositeViewer object that supports rendering from several widely separated viewpoints, complete with
{{cquote|Open Scene Graph supports a CompositeViewer object that supports rendering from several widely separated viewpoints, complete with
support for multiple terrain pager threads. We could move to CompositeViewer and support simultaneous views from e.g., the tower, AI
support for multiple terrain pager threads. We could move to CompositeViewer and support simultaneous views from e.g., the tower, AI

Navigation menu