20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
m
→CompositeViewer: https://sourceforge.net/p/flightgear/mailman/message/37325678/
m (→Status updates) |
m (→CompositeViewer: https://sourceforge.net/p/flightgear/mailman/message/37325678/) |
||
| Line 18: | Line 18: | ||
== CompositeViewer == | == CompositeViewer == | ||
CompositeViewer allows multiple independent views of the Flightgear scene, e.g. in independent top-level windows. | CompositeViewer allows multiple independent views of the Flightgear scene, e.g. in independent top-level windows, which allows for multiple independent views from different locations, allowing each view to have separate scenery loaded, using its own scenery pager.<ref>https://sourceforge.net/p/flightgear/mailman/message/37325678/</ref> | ||
This is primarily needed/useful when views may need acccess to scenery (tiles) that are no longer in the cache of the main aircraft, for instance a tower view of the destination airport, or payload-specific views (think missiles) that may be out of range, and thus need their own scenery DB pager. In other words, CompositeViewer (CV) support is needed whenever a view can no longer be easily defined/described as a "child view" of the main aircraft. | |||
=== Status updates === | === Status updates === | ||