Post FlightGear 2020.2 LTS changes: Difference between revisions

Jump to navigation Jump to search
m
→‎Possible additional items: use canvas pre-render camera outside the scene graph, as per Tim's comments: https://sourceforge.net/p/flightgear/mailman/message/36352621/
m (→‎Possible additional items: use canvas pre-render camera outside the scene graph, as per Tim's comments: https://sourceforge.net/p/flightgear/mailman/message/36352621/)
Line 43: Line 43:
* Remove the 2D panel code in favour of Canvas (this requires completing some work to load 2D panel elements as Canvas, from XML) <ref>https://sourceforge.net/p/flightgear/mailman/message/36973988/</ref>
* Remove the 2D panel code in favour of Canvas (this requires completing some work to load 2D panel elements as Canvas, from XML) <ref>https://sourceforge.net/p/flightgear/mailman/message/36973988/</ref>
* Remove the C++ HUD in favour of Canvas-based version : this requires some kind of migration script or framework, so we have at least the default UFO HUD available
* Remove the C++ HUD in favour of Canvas-based version : this requires some kind of migration script or framework, so we have at least the default UFO HUD available
* Review Tim's original suggestion: Another [Canvas] optimization is to use a pre-render camera that isn't in the scene graph to do the Canvas rendering. '''Otherwise the Canvas textures are rendered at least twice, in the near and far cameras'''. <ref>https://sourceforge.net/p/flightgear/mailman/message/36352621/</ref>
** https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Canvas/FGCanvasSystemAdapter.cxx#l70
** https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Viewer/renderer_compositor.cxx#l927 (compositor renderer)
** https://sourceforge.net/p/flightgear/flightgear/ci/next/tree/src/Viewer/renderer_legacy.cxx#l1842 (legacy renderer)


== fgdata clean-ups ==
== fgdata clean-ups ==

Navigation menu