CompositeViewer support: Difference between revisions

CompositeViewer support (view source)

Revision as of 12:08, 20 February 2014

4 bytes removed , 20 February 2014

m

→‎Background

Hooray

Administrators

20,741

edits

@@ Line 6: / Line 6: @@
 == Background ==
-{{cquote|<nowiki>What i want to achieve: Multiple views of the same scene . Lets call them
+{{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
-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
-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
+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
-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.
-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
+README.multiscreen in the FlightGear documentation says its possible to create a master camera and a slave camera that is offset from the master
-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
+one of the windows. Is there any way I can make the GUI to appear in all the windows? Actually I want to be able to view the hud and 2D panel in all the
-one of the windows. Is there any way I can make the GUI to appear in all the
-windows? Actually I want to be able to view the hud and 2D panel in all the
 windows.
-Also when I change the view in any one of the windows, the view changes in
+Also when I change the view in any one of the windows, the view changes in the other windows as well. Is it possible to make the windows independent of
-the other windows as well. Is it possible to make the windows independent of
+each other. I want to display the cockpit in one window at all times, in the second window I want to be able to shuttle between helicopter / chase or
-each other. I want to display the cockpit in one window at all times, in the
-second window I want to be able to shuttle between helicopter / chase or
 model views.
-Also I have observed that in the second screen where I'm displaying lets say
+Also I have observed that in the second screen where I'm displaying lets say the Helicopter view the aircraft remains static while the environment moves.
-the Helicopter view the aircraft remains static while the environment moves.
+This is because the cockpit view in my Master screen is defined as 'lookfrom'. Can I define 'lookfrom' for one screen and 'lookat' for the
-This is because the cockpit view in my Master screen is defined as
-'lookfrom'. Can I define 'lookfrom' for one screen and 'lookat' for the
 other screen.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27112.html|title=<nowiki>[Flightgear-devel] Help needed with multi-screen</nowiki>|author=Kavya Meyyappan|date=Fri, 19 Mar 2010 03:31:50 -0700}}</ref>|Kavya Meyyappan}}
-{{cquote|I think you have just summarized all the limitations of the FlightGear
+{{cquote|I think you have just summarized all the limitations of the FlightGear multi-camera/view/display system.  Tim Moore is the person who developed
-multi-camera/view/display system.  Tim Moore is the person who developed
+this feature (nothing existed before his efforts) and maybe he can offer more insight.  I know that in the case of menus, hud, 2d instrument panels,
-this feature (nothing existed before his efforts) and maybe he can offer
+there would need to be some significant code restructuring to allow these to be displayed on other windows.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27114.html|title=<nowiki>Re: [Flightgear-devel] Help needed with multi-screen</nowiki>|author=Curtis Olson|date=Fri, 19 Mar 2010 08:36:22 -0700}}</ref>|Curtis Olson}}
-more insight.  I know that in the case of menus, hud, 2d instrument panels,
-there would need to be some significant code restructuring to allow these to
-be displayed on other windows.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27114.html|title=<nowiki>Re: [Flightgear-devel] Help needed with multi-screen</nowiki>|author=Curtis Olson|date=Fri, 19 Mar 2010 08:36:22 -0700}}</ref>|Curtis Olson}}
-{{cquote|there's a limitation in Plib that forces the GUI to be drawn on one
+{{cquote|there's a limitation in Plib that forces the GUI to be drawn on one window.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27134.html|title=<nowiki>Re: [Flightgear-devel] Help needed with multi-screen</nowiki>|author=Tim Moore|date=Sat, 20 Mar 2010 01:42:31 -0700}}</ref>|Tim Moore}}
-window.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27134.html|title=<nowiki>Re: [Flightgear-devel] Help needed with multi-screen</nowiki>|author=Tim Moore|date=Sat, 20 Mar 2010 01:42:31 -0700}}</ref>|Tim Moore}}
 {{cquote|Neither of these are supported at the present time, but it would be a good project. We would have to start using a different OSG class,
@@ Line 55: / Line 40: @@
 {{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
+{{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
-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}}
-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
@@ Line 64: / Line 47: @@
 models, drones, etc.<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|Good thing to have!!!
+{{cquote|Good thing to have!!! Just still support graphics context on different screens/displays too ...<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17016.html|title=<nowiki>Re: [Flightgear-devel] RFC: changes to views and cameras</nowiki>|author=Mathias Fröhlich|date=Sat, 28 Jun 2008 00:05:19 -0700}}</ref>|Mathias Fröhlich}}
-Just still support graphics context on different screens/displays too ...<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17016.html|title=<nowiki>Re: [Flightgear-devel] RFC: changes to views and cameras</nowiki>|author=Mathias Fröhlich|date=Sat, 28 Jun 2008 00:05:19 -0700}}</ref>|Mathias Fröhlich}}
 {{cquote|FG only supports one view position at a time, right? Multiple view positions (e.g. one screen for the tower view and a second screen for
@@ Line 73: / Line 55: @@
 CompositeViewer model, which supports several scene graphs, and rely completely on the osg database paging machinery.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28869.html|title=<nowiki>Re: [Flightgear-devel] Disappearing scenery</nowiki>|author=Tim Moore|date=Sun, 19 Sep 2010 11:39:32 -0700}}</ref>|Tim Moore}}
-{{cquote|this also raises the question of reproducible clouds. If we have
+{{cquote|this also raises the question of reproducible clouds. If we have multiple independent viewers in the future, we need to draw the same clouds on
-multiple independent viewers in the future, we need to draw the same clouds on
+each with a bare minimum of communication. So, what is needed to generate the exactly same cloud. May be an initial seed for the random number generator, a
-each with a bare minimum of communication. So, what is needed to generate the
+position and a size? We may need to identify such a set of parameters and may be we should have a peudo loader for osg producing this kind of clouds from
-exactly same cloud. May be an initial seed for the random number generator, a
+these parameters. The you would be able to load and use these clouds from fgviewer and see isolated statistics about the draw/cull whatever steps. This
-position and a size? We may need to identify such a set of parameters and may
-be we should have a peudo loader for osg producing this kind of clouds from
-these parameters. The you would be able to load and use these clouds from
-fgviewer and see isolated statistics about the draw/cull whatever steps. This
 might also help in understanding what is going on.<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35147.html|title=<nowiki>Re: [Flightgear-devel] Trying to get more performance out of the 3D	clouds!</nowiki>|author=Mathias Fröhlich|date=Wed, 07 Dec 2011 22:16:45 -0800}}</ref>|Mathias Fröhlich}}

CompositeViewer support: Difference between revisions

CompositeViewer support (view source)

Revision as of 12:08, 20 February 2014

Navigation menu

Search