20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
→Cameras
m (from proposal to project, first stab at de-quoting) |
|||
| Line 30: | Line 30: | ||
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> | 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> | ||
== Status == | |||
In 07/2020, Julian Smith reported mixed success by crudely changing flightgear's FGRenderer's osgViewer::Viewer to an osgViewer::CompositeViewer with a single osgViewer::View, and patching up all the calling code so it compiles. | |||
It all builds ok, but at runtime it appears to stop making progress at 'loading scenery' - the splash screen stays in place with the scrolling blue line at the bottom. | |||
Presumably there's some messaging or synchronisation broken? Or maybe something more fundamental. | |||
All threads are blocked apart from the main thread which appears to be running the loop in fgOSMainLoop().<ref>https://sourceforge.net/p/flightgear/mailman/message/37057525/</ref> | |||
== Cameras == | == Cameras == | ||