INAV Configurator 2.0.0

Final 2.0.0 version

INAV Configurator 2.0.0 RC3

Changes since RC2: 2.0.0-rc2...2.0.0-rc3

Please, see the full release notes at https://github.com/iNavFlight/inav/wiki/2.0.0-Release-Notes

INAV Configurator 2.0.0 RC2

Changes since RC1:

• Fixed OSD preview of pitch/roll angles and heading
• Fixed incorrect OSD item IDs (caused some switches to control the visibility of the wrong element)
• Fixed alignment of version number
• Fixed hang on "Loading data" screen when connecting to INAV < 2.0
• Display boards and versions correctly for unstable releases in the firmware upgrades tab
• Make mixer tab work properly on smaller window widths
• Fixed incorrect current and used mAh values in the setup tab
• Fixed issue when the configurator was started minimized
• Added "Clarity" font to the OSD font manager

See the full INAV 2.0 release notes at https://github.com/iNavFlight/inav/wiki/2.0.0-Release-Notes

INAV Configurator 2.0.0 RC1

Merge pull request #487 from shellixyz/add_new_osd_items

Add new OSD items

INAV Configurator 1.9.3

Merge pull request #406 from iNavFlight/dzikuvx-pid-defaults-update

updated defaults for PIDs and presets

INAV Configurator 1.9.2

Merge pull request #375 from shellixyz/fix_acc_calibration_values

Fix calibration tab reported acc{zero,gain}_* values

INAV Configurator 1.9.1

Merge pull request #349 from iNavFlight/de_enable_craft_name

Enable CRAFT_NAME item in OSD

INAV Configurator 1.8.1

Version bump to 1.8.1

INAV Configurator 1.8.0

Bump version to 1.8.0

INAV Configurator 1.7.3

Google is going to end support for Chrome Apps somewhere in 2018. As a countermeasure we are now publishing native binaries for MacOS and Windows. Linux will follow.

Binaries provided are not signed, and the OS will warn you about that. It's only an annoyance and doesn't affect application functionality. We are working on fixing this.