CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
more de-quoting
m (→‎Background: remove irrelevant quote)
m (more de-quoting)
Line 23: Line 23:
{{Multicore}}
{{Multicore}}


aircraft can define their own views and so on. But only one view can be active at a time. So no matter how many windows and cameras you define in preferences.xml, they all are relative to the current view in FG (i.e. cockpit, tower...). <ref>http://forum.flightgear.org/viewtopic.php?p=146136#p146136</ref>  
FlightGear only supports one view position at a time. Multiple view positions (e.g. one screen for the tower view and a second screen for the plane) would complicate a "locked to cache" flag quite a lot...<ref>http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28864.html</ref>.
 
 
Aircraft can define their own views and so on. But only one view can be active at a time. So no matter how many windows and cameras you define in preferences.xml, they all are relative to the current view in FG (i.e. cockpit, tower...). <ref>http://forum.flightgear.org/viewtopic.php?p=146136#p146136</ref>  


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>http://sourceforge.net/p/flightgear/mailman/message/19718339/</ref>
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>http://sourceforge.net/p/flightgear/mailman/message/19718339/</ref>
Line 98: Line 101:


{{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}}
{{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}}
{{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
the plane) would complicate a "locked to cache" flag quite a lot...<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28864.html|title=<nowiki>Re: [Flightgear-devel] Disappearing scenery</nowiki>|author=ThorstenB|date=Sun, 19 Sep 2010 07:41:13 -0700}}</ref>|ThorstenB}}


{{cquote|Yes, and that's not really supported by the current architecture, neither by the tile cache nor by osgViewer::Viewer. We would need to move to a
{{cquote|Yes, and that's not really supported by the current architecture, neither by the tile cache nor by osgViewer::Viewer. We would need to move to a

Navigation menu