20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
m
from proposal to project, first stab at de-quoting
m (update as per: https://sourceforge.net/p/flightgear/mailman/message/37057525/) |
m (from proposal to project, first stab at 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> | |||
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> | |||
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 models, drones, etc.<ref>http://sourceforge.net/p/flightgear/mailman/message/19718339/</ref> | |||
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, CompositeViewer, to support multiple views from independent view points. Our terrain pager would need a complete overhaul to use the [[PagedLOD]] scheme of OSG, and the Flightgear view manager would need to be aware multiple active views.<ref>=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27134.html</ref> | |||
== Cameras == | == Cameras == | ||