20,741
edits
No edit summary |
|||
| Line 31: | Line 31: | ||
* Basic Knowledge of FlightGear and XML | * Basic Knowledge of FlightGear and XML | ||
== OSG::CompositeViewer == | |||
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. | |||
Also, it would make sense to implement a moving map as a scene graph in its own right with its own pager. That would require a change in current fg architecture to use a CompositeViewer instead of a single Viewer, but we're contemplating that anyway. | |||
Independent view windows are not 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. | |||
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 CompositeViewer model, which supports several scene graphs, and rely completely on the osg database paging machinery. | |||
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17001.html | |||
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg17263.html | |||
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg27134.html | |||
* http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg28869.html | |||
=Part 1: Rendering a Camera View to Texture= | =Part 1: Rendering a Camera View to Texture= | ||