Skip to content

v0.8.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Sep 01:11
· 11 commits to main since this release
v0.8.0
e06c45d

FlightLens 0.8.0

The Rates tab now includes a read-only Throttle Curve Preview alongside angular
velocity. It shows the selected profile's imported MID, EXPO and throttle limit
settings with source-line links, and plots normalized throttle input against
throttle command in percent.

The calculation follows verified legacy Betaflight integer lookup behavior and
applies the configured OFF, SCALE or CLIP limit afterward. Differential tests
compare 28,512 vectors against compiled, pinned upstream C code.

Phase 2.5 implementation is complete. The next roadmap unit is Phase 2 item 4:
three-backup comparison with an explicit baseline.

Upgrade and compatibility

No breaking changes are known. No migration or other user action is required.
Saved paths and settings retain their existing format; portable .flightlens
sessions are not yet supported. Source backups remain read-only, and inspection
and comparison remain offline. Existing exports and their validation are preserved.

Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
The new throttle preview requires exact official releases 4.2.0, 4.3.0, 4.4.0 or
4.5.0–4.5.5, a matching schema pack, and four explicit valid settings in the
selected rate profile. Missing values are not filled from defaults. Existing
angular-velocity default recovery is unchanged.

Known limitations

  • Vendor builds, other releases and the separate 2025.12 hover-dependent model
    report the throttle preview as unavailable.
  • MID=100 remains a valid CLI setting but is unavailable in the preview because
    the upstream extra lookup knot has a zero divisor.
  • The chart represents the static configured curve and ordinary limit path,
    excluding smoothing, boost, RPM-limit bypass and other runtime effects. It
    does not predict motor output or thrust.
  • Packaged Windows/macOS native integration and feedback hand-off still require
    manual validation. Installers remain unsigned; macOS notarization is absent.
  • Three-backup comparison, workspace indexing, portable sessions and native file
    associations remain outstanding.

Release validation covers Rust and frontend tests, parser-to-renderer browser
behavior, the local backup corpus and README screenshots. GitHub workflows build
and publish Windows and macOS installers.

Assets 5
Loading