Current Build (2024-03-31)

• Supports latest version (1.0.19) of fllightlog2kml, which can use a CLI data file to add Safehome and FWApproach to a KML
• The Windows Installer contains refreshed "Gtk" components which, in theory, should:
  • No longer require setting GSK_RENDERER to CAIRO
  • No longer crash when clicking "Output"
• There is no good reason to update a Linux / FreeBSD installation from 1.2.0, however upgrading to the latest fllightlog2kml is recommended.

FW Approach

• Supports latest version (1.0.15) of fllightlog2kml, which can use a CLI data file to add Safehome and FWApproach to a KML

Notes:

(a) The Windows installer was refreshed 2024-02-23 as it may have been missing a (non-essential) DLL
(b) If the installed Windows executable crashes before the main window is displayed (on a VM at least), setting the environment variable GSK_RENDERER to CAIRO should prevent such behaviour.

Drag'n'Drop

• Drag and Drop of logs and mission files onto the output text area is now supported on all platforms (master gtk4 builds)
• Master branch (and published builds) are gtk4
• There is a legacy (gtk3) branch (and Deb installer) for older Linux distros. This is marked version 1.0.3 and is no longer actively maintained.

If you're happy wtih 1.0.2, and aren't bothered about D'n'D, there's no compelling reason to upgrade..

Mission only KML/Z generation

It is now possible to generate a KML/Z for just a mission file (no flight logs defined). Requires flightlog2kml 1.0.3 or later (1.0.3 is included in the Windows installer).

Earth Launcher

Allows direct launching of Google Earth from the user interface, either from the "Earth" button or by pressing Control-L after KML/Z files have been generated.

• Requires flightlog2kml (1.0.1 or later). 1.0.2 is recommended and is included in the Windows installer.
• fl2xui Attempts to detect the presence of Google Earth. Only if this fails is it necessary to add the name of the Google Earth executable in the configuration file:
  • On (non-macOS) POSIX platforms, where Google Earth is customarily on PATH, just the executable name is required, for example:

     "ge-name" : "google-earth-pro"
    

  • On Windows, the full path is required, for example (note back-slashes have to be escaped):

    "ge-name" : "C:\\Program Files\\Google\\Google Earth Pro\\client\\googleearth.exe"
    

  • On macOS, Google Earth is not auto-detected, so needs an entry like:

     "ge-name" :  "/Applications/Google Earth Pro.app/Contents/MacOS/Google Earth"
    

    It is also unlikely that macOS will actually load your files. Advice on how to fix this would be appreciated.

Earth Launcher

Allows direct launching of Google Earth from the user interface, by pressing Control-L after KML/Z files have been generated.

• Requires flightlog2kml (1.0.1-rc1) or later (development branch); 1.0.1-rc2 is recommended and is included in the Windows installer.

• fl2xui Attempts to detect the presence of Google Earth. Only if this fails is it necessary to add the name of the Google Earth executable in the configuration file:

  • On (non-macOS)Allows direct launching of Google Earth from the user interface, by pressing Control-L after KML/Z files have been generated.

• Requires flightlog2kml (1.0.1-rc1) or later (development branch); 1.0.1-rc2 is recommended and is included in the Windows installer.

• fl2xui Attempts to detect the presence of Google Earth. Only if this fails is it necessary to add the name of the Google Earth executable in the configuration file:

  • On (non-macOS) POSIX platforms, where Google Earth is customarily on PATH, just the executable name is required, for example:

     "ge-name" : "google-earth-pro"
    

  • On Windows, the full path is required, for example (note back-slashes have to be escaped):

    "ge-name" : "C:\\Program Files\\Google\\Google Earth Pro\\client\\googleearth.exe"
    

  • On macOS, Google Earth is not auto-detected, so needs an entry like:

     "ge-name" :  "/Applications/Google Earth Pro.app/Contents/MacOS/Google Earth"
    

    It is also unlikely that it will actually load your files, as this would be infra-dig for such an advanced operating system. Advice on how to fix this would be appreciated.

POSIX platforms, where Google Earth is customarily on PATH, just the executable name is required, for example:
"ge-name" : "google-earth-pro"

• On Windows, the full path is required, for example (note back-slashes have to be escaped):

  "ge-name" : "C:\\Program Files\\Google\\Google Earth Pro\\client\\googleearth.exe"
  

• On macOS, Google Earth is not auto-detected, so needs an entry like:

   "ge-name" :  "/Applications/Google Earth Pro.app/Contents/MacOS/Google Earth"
  

  It is also unlikely that it will actually load your files, as this would be infra-dig for such an advanced operating system. Advice on how to fix this would be appreciated.

All version numbers are arbitrary

Changes

• Provides of visual preview of gradients
• Supports new plotting attributes:
  • Speed
  • Altitude
  • Battery (voltage)
• Requires flightlog2kml 1.0.0-rc2 or later (1.0.0 is included in Windows installer); 1.0.0 is also the current flightlog2kml release version.
• Supports command line provision of log files (so you can drag and drop log files onto the Windows shortcut icon).
• Adds "Save Settings" to save the currently set parameters as default.
• Create Windows Start Menu entry
• Behave sanely when no extant configuration file and / or directory
• Save dms setting correctly
• Don't crash on save when no extant directory
• Fix compilation with older compilers (e.g. Debian Buster, vala 0.42)
• Show version in title bar
• Fix tool-tips
• Show output directory path

New settings

The Speed and Altitude plots defaults are currently set as:

• For Speed, red is slow (risk of stalling an aeroplane)
• For Altitude, red is high (check compliance with regulatory requirements).

These may be inverted (high speed is red, low altitude is red), with the following settings in ~/.config/fl2x/config.json / %LOCALAPPDATA%\fl2x\config.json. These attributes can also be edited and saved from the UI.

 "fast-is-red" : true

and

"low-is-red" : true

For example:

{
  "dms" : true,
  "extrude" : true,
  "gradient" : "yor",
  "attributes" : "effic,speed,altitude,battery",
  "rssi" : false,
  "efficiency" : true,
  "outdir" : null,
  "kml" : false,
  "fast-is-red" : true,
  "low-is-red" : true
}

Note standalone efficiency is legacy, the efficiency plot is rendered if either "efficiency" : true or the new attributes field contains effic. This is for backwards compatibility with earlier versions.

Dependencies

Unless you are using the Windows installer, you must ensure you have contemporaneous releases of flightlog2kml and INAV blackbox_decode installed.

Pre-release for 0.0.8 (rc5)

New Features

• Provides of visual preview of gradients
• Supports new plotting attributes:
  • Speed
  • Altitude
  • Battery (voltage)
• Requires flightlog2kml 0.14 (0.14-rc2 is included in Windows installer, otherwise build from development).
• Supports command line provision of log files (so you can drag and drop log files onto the Windows shortcut icon).
• Adds "Save Settings" to save the currently set parameters as default.

Since rc4

• Show output name, fix tooltips

Since rc3

• Windows only; fix another gratuitous incompatibility with ROTW.

Since rc1/rc2

• Create Windows Start Menu entry

• Behave sanely when no extant configuration file

• Save dms setting correctly

• Don't crash on save when no extant directory

• Compile om ancient compilers (Buster, 0.42)

• Show version in title bar

New settings

The Speed and Altitude plots defaults are currently set as:

• For Speed, red is slow (as you might stall an aeroplane)
• For Altitude, red is high (in case one is concerned with regulatory requirements).

These may be inverted (high speed is red, low altitude is red), by adding the following settings
to ~/.config/fl2x/config.json / %LOCALAPPDATA%\fl2x\config.json.

 "fast-is-red" : true

and

"low-is-red" : true

For example:

{
  "dms" : true,
  "extrude" : true,
  "gradient" : "yor",
  "attributes" : "effic,speed,altitude,battery",
  "rssi" : false,
  "efficiency" : true,
  "outdir" : null,
  "kml" : false,
  "fast-is-red" : true,
  "low-is-red" : true
}

Note efficiency is legacy, efficiency plot is rendered if either "efficiency" : true or the new attributes field contains effic. This is for backwards compatibility with earlier versions.

007 revisited

Note

This release has been updated due mainly to some missing Windows icons (apologies, in order to add a couple of trivial icons, there is a large bump in the size of the Windows installer). The re-release also fixes a misplaced tooltip.

Changes

• Adds an interval spin-button (you can also type in an entry) for the sampling interval. Previously the sampling interval was fixed at 1s, which was too small for long duration logs.
• Fixes an erroneous tooltip

Debian archive

• The deb is built on Debian Buster. Should work on most contemporaneous and recent distos (Debian, Ubuntu and derivatives).

Windows Installer (Updated)

Note that the Windows archive / installer is:

• 64 bit only
• Includes recent releases of blackbox_decode (4.0.1) and flightlog2kml (0.13.0).
• Supersedes the earlier issue due to some missing icons.

Another Windows update

Windows only update

• Fix another WIndows resource leak
• Fix Windows case where flightlog2kml was not found
• Default to Windows10 GTK theme
• Honour outdir key from fl2x config.json
• Migrate windows APPDATA to LOCALAPPDATA (as for flightlog2kml 0.12.5)

Non-Windows OS

Although the version is bumped to reflect the Windows-only updates, there are no functional changes for Linux, FreeBSD, MacOS etc.

Debian archive

• The deb is built on Debian Buster. Should work on most contemporaneous and recent distos (Debian, Ubuntu and derivatives).

Note that the Windows archive / installer is:

• 64 bit only
• Includes recent releases of blackbox_decode (4.0.1) and flightlog2kml (0.12.5).