CompositeViewer support: Difference between revisions

Jump to navigation Jump to search

CompositeViewer support (view source)

Revision as of 16:39, 2 October 2020

1,993 bytes removed ,  2 October 2020
→‎Status
Line 22: Line 22:
To execute the patched binary with the compositeviewer enabled, use: <code>fgfs  --composite-viewer=1</code> <ref>https://sourceforge.net/u/cgdae/flightgear/ci/059cf073c74d43a57c11f363cae6c9271772d869</ref>
To execute the patched binary with the compositeviewer enabled, use: <code>fgfs  --composite-viewer=1</code> <ref>https://sourceforge.net/u/cgdae/flightgear/ci/059cf073c74d43a57c11f363cae6c9271772d869</ref>


Unfortunately the property system seemed to be not set up early enough to read in FGRenderer's constructor so we do a few calls of fgGetNode("/sim/composite_viewer", true)->getBoolValue() at runtime. Julian suspects they aren't called very frequently, in which case this branch (minus the diagnostics changes probably) might be ok to push to next at
some point, so that it's easier to test/investigate things.<ref>https://sourceforge.net/p/flightgear/mailman/message/37062319/</ref>
For some reason buildings don't appear, but basic ground scenery now loads so fgfs progresses to loading the fdm etc and one can fly the aircraft as normal.


{{Note|According to Richard, when testing the database pager extensively (running with 20 DB pager threads), the main problem is the way that random objects (buildings, vegetation) are inserted into the scene graph doesn't seem  to be compatible with lots of pager threads.<ref>https://sourceforge.net/p/flightgear/mailman/message/36536293/</ref>}}
{{Note|According to Richard, when testing the database pager extensively (running with 20 DB pager threads), the main problem is the way that random objects (buildings, vegetation) are inserted into the scene graph doesn't seem  to be compatible with lots of pager threads.<ref>https://sourceforge.net/p/flightgear/mailman/message/36536293/</ref>}}


In August 2020 Julian reported additional progress: He set things up so that one can 'clone' the current view using a key-press. This creates a new top-level view window with its own copy of the current view's camera projection matrix etc. The view is added to the CompositeViewer so it sees the same scene.
In August 2020 Julian reported additional progress: He set things up so that one can 'clone' the current view using a key-press. This creates a new top-level view window with its own copy of the current view's camera projection matrix etc. The view is added to the CompositeViewer so it sees the same scene.
For now at least, cloned views' projection matrices don't change so the cloned views are completely independent from movement of the aircraft or changes to the main view. Eventually he would like to make them behave more dynamically, e.g. follow the aircraft if cloned from Helicopter View.
At the moment most of the scenery doesn't show up and the background colours are wrong, but this screen shot shows it working: http://op59.net/fg-cv.png
The cloned view on left was cloned from Pilot View when the aircraft was at the end of the runway. Since then the aircraft has been moved up the runway and is hovering. The cloned view on the right was cloned from a Tower AGL view of the hovering aircraft.<ref>https://sourceforge.net/p/flightgear/mailman/message/37075206/</ref>
In 09/2020, Jules reported that he's still unable to get textures to work in cloned views, so he's been playing around with various new viewing features using the CompositeViewer support.
Here's a short and very grainy video showing a 'double view' in a separate window on the left of the main window. The double view keeps two aircraft (a Harrier-GR3 and a SU-37 here) in view at all times, keeping one (the Harrier) at a small constant distance in the foreground <ref>https://sourceforge.net/p/flightgear/mailman/message/37101960/</ref>: http://op59.net/fg-cv-demo3.mpeg




Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/127812"

Navigation menu