Flight Reader 1.7.40 released

Flight Reader
1

A new version of Flight Reader is available. Release 1.7.40 includes the following changes:

  • New Event CSV and Video CSV options are available under the Export menu. The Export menu will only appear in the context menu when selecting multiple flights and right-clicking in the main Flight Reader window.

  • A flight polygon KML is generated during flight log processing to visualize the flight area. Access this new KML by right-clicking a flight in the main Flight Reader window and selecting KML → Flight Polygon KML.

  • Added a new CAMERA.mode field to indicate when the camera is shooting in Single Shot, Multi Shot, Pano, or Video mode.

  • Added a new CAMERA.photosTaken field to show how many photos were captured. This value will be greater than 1 during rapid-fire photo modes like AEB or Burst.

  • Added a new CAMERA.panoPhotoSequence field to indicate the sequence number of each photo in a pano sequence. This can be used to group photos from the same pano sequence.

  • Rows are now highlighted in green wherever a new video recording begins in the Video Log.

  • The CAMERA.isPhoto field now logs a single photo entry at the moment each rapid-fire photo (e.g. AEB or Burst) is taken. The new CAMERA.photosTaken field shows how many photos were captured at that moment.

  • AM/PM designators are now automatically added to 12-hour time fields when using a Windows region that does not have them defined. In previous versions of Flight Reader, missing AM/PM designators made it unclear whether times were in the morning or afternoon.

  • The Measurement Units setting in the General section of the Flight Reader Options window now defaults to the user’s Windows region settings when this setting has not been set.

  • Resolved an issue that caused an extra photo to be incorrectly documented at the end of each pano photo sequence.

  • Resolved a crash that could occur when loading a malformed CSV file. Instead of crashing, Flight Reader will now display the malformed data. Reprocessing the flight log may fix the issue.

  • Resolved an issue where an incorrect flight start time could be shown when a second flight begins without powering off the drone between flights.

  • Fixed an issue that sometimes prevented flight logs from being processed when importing via File → Import Flight Log… in the main Flight Reader window.

See the release notes for a complete list of changes.

1 Like