20,741
edits
CompositeViewer support: Difference between revisions
Jump to navigation
Jump to search
→Status: https://sourceforge.net/p/flightgear/mailman/message/37076818/
m (→Open Questions) |
(→Status: https://sourceforge.net/p/flightgear/mailman/message/37076818/) |
||
| Line 54: | Line 54: | ||
== Status == | == Status == | ||
{{Note|while it's certainly possible to have a look at the changes and understand how things are working, the code isn't really ready for review and push yet - there's still loads of debug diagnostics and a few dead-ends in there. Jules is hoping to be able to address some of these over the next few days.<ref>https://sourceforge.net/p/flightgear/mailman/message/37077148/</ref>}} | {{Note|while it's certainly possible to have a look at the changes and understand how things are working, the code isn't really ready for review and push yet - there's still loads of debug diagnostics and a few dead-ends in there. Jules is hoping to be able to address some of these over the next few days.<ref>https://sourceforge.net/p/flightgear/mailman/message/37077148/</ref> | ||
In other words: No one is claiming CompositeViewer support is anywhere near being ready to be enabled by default - there are lots of issues to sort out, at the moment chiefly how to get scenery to show up in cloned views and interact with scenery caching properly etc. <ref>https://sourceforge.net/p/flightgear/mailman/message/37076818/</ref>}} | |||
In 07/2020, Julian Smith reported some success by 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. | In 07/2020, Julian Smith reported some success by 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. | ||