CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
(→‎Status: https://sourceforge.net/p/flightgear/mailman/message/37076818/)
Line 55: Line 55:
== 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 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.
Also, the potential benefits we get with an improved viewing system will be really significant. (For example easy creation at runtime of multiple arbitrary top-level
windows showing Tower View / Helicopter View etc on one's own or multiplayer aircraft, new dynamic views such as the view from one aircraft to another, etc etc.)
 
With free software one has to rely on developer enthusiasm for getting things done, and this doesn't always last forever and doesn't always match up with roadmaps.<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.

Navigation menu