Difference between revisions of "Post FlightGear 2020.2 LTS changes"

From FlightGear wiki
Jump to: navigation, search
m (2D Panels: https://sourceforge.net/p/flightgear/flightgear/merge-requests/217/#a8d5)
m (Possible additional items: done: cleanup)
Line 84: Line 84:
== Possible additional items ==
== Possible additional items ==
Once the hackathon is done, we should merge compositor, and then once the build is stabilised, merge composite viewer: i,e during ‘the rest’ of November 2020.<ref>https://sourceforge.net/p/flightgear/mailman/message/37147622/</ref><ref>https://sourceforge.net/p/flightgear/mailman/message/37148460/</ref>
=== osgText ===
=== osgText ===

Revision as of 11:54, 5 December 2020

Current status

It has been suggested that this article or section be merged into Building using CMake.


James has pushed some configuration changes to next (SG+FG) to raise various required versions of things.

If you’re developing on ‘something fairly recent’, you shouldn’t see any difference except it would be a wise time to wipe your build dirs and re-CMake from clean. If you’re on a ‘somewhat older’ Linux, the baselines being Ubuntu 18.04 (their previous LTS) and CentOS 7 (which our Jenkins runs), you should also be fine except for GCC, where you will need a version supporting C++14: in practice this means GCC 5.x or higher. (Or use Clang…) For both of these distros there are officially supported ways to get newer GCCs (we’re actually using GCC 9 on Jenkins now..), so I don’t expect this to be a problem.

As part of this we now require CMake 3.10[1], Qt 5.9 and OSG 3.4.1, and James started removing various legacy pieces from next around this. There are plenty more cleanups that can be done based on this : especially on the CMake and C++ sides. Things like Boost -> Std stuff, Cmake targets-as-objects support (eg, target_compile_features can be used now).

Windows and macOS should be unaffected BTW - because on those platforms you're always running something you downloaded which is fairly up to date. If you choose to go and download an ancient version of CMake or Qt, on either platform that’s your problem to fix - but you’ll get a configuration error at least.

The idea of doing this /now/ is that the build deps won’t change again during the next two years, barring any surprises.

None of this affects the release branches of course: they continue to work with OSG 3.2, GCC 4.x, Qt 5.4 and CMake 3.0. And you shouldn’t see any behavioural changes because of this either.

Let’s see if reality corresponds to all the theory above :)[2]

08/2020: James pushed a large overhaul of the Cmake build files for FlightGear:

  • we now use modern Cmake style nearly everywhere, i.e targets-as-objects for an OOP-style build system
  • transitive dependencies are handled automatically (or at least, that’s the idea…), which simplifies things in many places (eg, audio library handling)
  • system vs built-in dependencies is handled vis ALIAS targets, so most other code doesn’t care. We link to a target which is an alias for either our built-in version or the system one (via an IMPORTED target)
  • we should have better isolation from system headers / versions of things. [3]

Changes that are already on next

It has been suggested that this article or section be merged into Changelog 2020.1#Replay_.2F_Flight_Recorder.


  • Include multiplayer aircraft in recordings.
  • Continuous recording to file without any loss of detail.
  • Periodic generation of a recovery snapshot, allowing resumption after a flightgear crash.

See new File - Flight Recorder Control dialogue.


  • Continuous recording to file is uncompressed to simplify replay; e.g. 100MB for an hour's recording near EDDF.
  • A recovery snapshot is actually a single-frame continuous recording, and will be called <aircraft-type>-recovery.fgtape. Load in the usual way using the Flight Recorder Control dialogue or on the command line with --load-tape=<aircraft-type>-recovery. Then do Ctrl-R to see replay dialogue and click on My Controls. I think that some aircraft may have no or limited support for My Controls though?

Code clean-ups and changes

Collecting what's going to change : this will also be used to work out what manual or automatic migrations are required to keep aircraft working. It's expected that for the first few months of 'next', there will be higher than usual breakage, i.e regular might not be possible.

As a general guideline, the minimum system to develop / build the code on will be Ubuntu 18.04 LTS (Bionic) : the versions below correspond to what is available in a stock Bionic install.

  1. Make C++14 (possibly C++17 to facilitate VSG migration? [4] [5]) the minimum required version (will make it easier to continue replacing Boost items with std:: ones) [6] [7]
  2. Make CMake 3.6 the minimum required version: this will allow simplifying a bunch of compatibility logic in the build files [8] 70}% completed [9]
  3.  Use CMake OBJECT_LIBRARY to improve how we collect sources together when building each sub-dir 10}% completed [10]
  4. Make Qt 5.9 the minimum for the launcher Done Done [11]
  5. Drop 32-bit windows support [12]
  6. Drop the pre-2017.x MultiPlayer message format - this will fix warnings from some aircraft about MP packet overflows [13]
  7. Drop the KLN-89 code, since it's unused and not maintained for a long time: Canvas and the regular GPS code can easily implement a working KLN-89 or similar equipment now [14]
  8. Switch to Compositor mode as the only rendering option 90}% completed [15][16][17][18]
  9. Drop Rembrandt support from C++ (really part of the above) [19]
  10. Drop the C++ NavDisplay: the Canvas version replaces it [20]

Carriers and AI

Richard has been working on carriers since April 2020; originally the intention was to release as part of the 2020.2 LTS however the changes have grown into a set of new features rather than bugfixes and are therefore more suited to a longer development and review process.[21]

  • Done Done Improved view support - so that the nearest tower will include carriers
  • Done Done Changes to core code to support moving towers.
  • 50}% completed Multiple (tower) views - permit selection of LSO, PLAT and Tower as part of the "Tower view"; selection mechanism TDB. Consider revisions to the existing view system to better support this.
  • Done Done Extend XML to include definitions for FLOLS touchdown position, LSO view position, Tower View position, deck angle.
  • 50}% completed Improve 3d models for IFLOLS to ensure that a ball call can be made.
  • 80}% completed Improve logic for IFLOLS lights; not quite an LSO simulation more of an approximation of the definitive cases (e.g. waveoff)
  • Pending Pending Animate the lineup lights on the stern (of Nimitz class).
  • 90}% completed Improved support for Precision Approach Landing System (PALS) (AN/SPN-46); to support lineup deviation as well as glideslope (ball) deviation.
  • 70}% completed Change approach deviations to use new aircraft reference point rather than eyepoint; it is probably more correct to use the eyepoint when in the cockpit view - but for external views this can be slightly inaccurate when outside the aircraft to completely wrong when in tower/LSO view. The reference point is taken as the aircraft position with an optional model defined x,y,z offset. This allows ball tuning on a per aircraft basis.
  • Pending Pending Improved support for AI logic to permit XML definition of e.g. LSO logic. Possibly a version of the autopilot / state machine that can be included as "logic blocks"
  • Pending Pending Review 3d model usage for all Nimitz class and either add LOD selection (low, medium, high)
  • Pending Pending Possible extra visual aids for Case 1 and Case 2 recovery training (e.g. a set of markers to fly through)
  • Pending Pending Better integration of carriers with JSBSim to permit catapult hookup
  • Pending Pending Simulate carrier operations Flight Deck Personnel, e.g. yellow shirts.
  • Pending Pending Animation of arrestor wires
  • Pending Pending Add some sort of trap grading (approach/touchdown plot)

see https://www.cnatra.navy.mil/local/docs/pat-pubs/P-816.pdf for T-45 carrier operations

Possible additional items


1rightarrow.png See OSGText Issues for the main article about this subject.

2D Panels

The idea is to remove all 'raw' OpenGL or OpenSceneGraph code from the panel code, it should be 100% done with Canvas elements. Eg use the Canvas Transform to compute the matrices[22]


fgdata clean-ups


2do: list outdated / deprecated functions for removal (I remember one comment saying: remove after FG 3.0 or something)

  • Clean up the GPS code with respect to FG_210_COMPAT :

property tree clean-up

remove /yasim/* "new" path is /fdm/yasim (since version 201x.?)


  1. https://sourceforge.net/p/flightgear/mailman/message/37094732/
  2. https://sourceforge.net/p/flightgear/mailman/message/37041064/
  3. https://sourceforge.net/p/flightgear/mailman/message/37091728/
  4. https://sourceforge.net/p/flightgear/mailman/message/37041706/
  5. https://sourceforge.net/p/flightgear/mailman/message/37042499/
  6. https://sourceforge.net/p/flightgear/mailman/message/36988831/
  7. https://sourceforge.net/p/flightgear/mailman/message/36984349/
  8. https://sourceforge.net/p/flightgear/mailman/message/37020794/
  9. https://sourceforge.net/p/flightgear/mailman/message/37091728/
  10. https://sourceforge.net/p/flightgear/mailman/message/37042800/
  11. https://sourceforge.net/p/flightgear/mailman/message/37041064/
  12. https://sourceforge.net/p/flightgear/mailman/message/34899704/
  13. https://sourceforge.net/p/flightgear/mailman/message/36300829/
  14. https://sourceforge.net/p/flightgear/mailman/message/36327950/
  15. https://sourceforge.net/p/flightgear/mailman/message/36606242/
  16. https://sourceforge.net/p/flightgear/mailman/message/37039397/
  17. https://sourceforge.net/p/flightgear/mailman/message/37040359/
  18. https://sourceforge.net/p/flightgear/mailman/message/37148477/
  19. https://sourceforge.net/p/flightgear/mailman/message/36340736/
  20. https://sourceforge.net/p/flightgear/mailman/message/36975265/
  21. https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/aaa9a3ee-ca18-e3af-1538-0cd59ae7a752%40zaretto.com/#msg37038519
  22. https://sourceforge.net/p/flightgear/flightgear/merge-requests/217/#a8d5
  23. https://sourceforge.net/p/flightgear/mailman/message/36973988/
  24. https://sourceforge.net/p/flightgear/mailman/message/37042351/
  25. https://sourceforge.net/u/gallaert/flightgear/ci/789f5bdbce10637222ffa25206938947fec4bc64/
  26. https://sourceforge.net/p/flightgear/mailman/message/36973988/
  27. https://sourceforge.net/p/flightgear/mailman/message/36659646/
  28. https://sourceforge.net/p/flightgear/mailman/message/36352621/
  29. https://sourceforge.net/p/flightgear/mailman/message/37042457/
  30. https://sourceforge.net/p/flightgear/mailman/message/36355833/
  31. https://sourceforge.net/p/flightgear/mailman/message/29563353/
  32. https://sourceforge.net/p/flightgear/mailman/message/19718354/
  33. https://sourceforge.net/p/flightgear/mailman/message/37058207/