CompositeViewer support: Difference between revisions

Jump to navigation Jump to search
m
too much fluctuation to point to any single commit/branch
m (too much fluctuation to point to any single commit/branch)
Line 10: Line 10:
|description = Support for multiple independent scene views
|description = Support for multiple independent scene views
|status      = experimental (building, mostly working in single-view mode, buildings missing, supports cloning independent views into distinct windows <ref>http://wiki.flightgear.org/CompositeViewer_Support#cite_note-22</ref>) <br/>{{Progressbar|30}} <ref>https://sourceforge.net/p/flightgear/mailman/message/37070203/</ref>
|status      = experimental (building, mostly working in single-view mode, buildings missing, supports cloning independent views into distinct windows <ref>http://wiki.flightgear.org/CompositeViewer_Support#cite_note-22</ref>) <br/>{{Progressbar|30}} <ref>https://sourceforge.net/p/flightgear/mailman/message/37070203/</ref>
|developers  = Julian Smith<ref>https://sourceforge.net/p/flightgear/mailman/message/37062319/</ref>
|developers  = Julian Smith<ref>https://sourceforge.net/p/flightgear/mailman/message/37062319/</ref> <ref>https://sourceforge.net/p/flightgear/mailman/message/37077854/</ref>
|changelog = https://sourceforge.net/u/cgdae/profile/feed.rss
|changelog = https://sourceforge.net/u/cgdae/profile/feed.rss, https://sourceforge.net/u/cgdae/flightgear/ci/fc3a62e291fc5948811c43e1647905c9a50a726e/
<!--
|topic-fg= https://sourceforge.net/u/cgdae/flightgear/ci/CompositeViewer
|topic-fg= https://sourceforge.net/u/cgdae/flightgear/ci/CompositeViewer
|topic-sg= https://sourceforge.net/u/cgdae/simgear/ci/CompositeViewer
|topic-sg= https://sourceforge.net/u/cgdae/simgear/ci/CompositeViewer
-->
<!--
<!--
|folders =  
|folders =  
Line 54: Line 56:


== 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 <ref>https://sourceforge.net/p/flightgear/mailman/message/37077854/</ref> 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.  
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
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

Navigation menu