v0.7.0
FlightLens 0.7.0
FlightLens adds comparison of VTX activation slots on matching official Betaflight
4.5.0–4.5.5 versions, and adjustment-range declarations on matching official
4.5.0–4.5.5 and 2025.12.1–2025.12.5 versions. These comparisons account for command
ordering, normalized ranges, invalidated declarations, and source lines.
Seven additional global parameter mappings bring certified cross-version coverage
to eleven settings across those releases: battery capacity, forced cell count,
voltage divider and multiplier, ADC current offset, and virtual-current scale and
offset join motor poles and the three battery cell-voltage thresholds. Bounds and
exact firmware identities gate comparisons; missing values remain unknown.
Bundled evidence and developer verification scripts document the supported scope.
The feedback form now states that submitting an issue requires a GitHub account
and labels its browser hand-off “Continue to GitHub”.
Phase 2 item 3 is complete within its documented comparison coverage boundary.
Broader equivalence research is deferred; three-backup comparison is next.
Phase 2 as a whole remains in progress.
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.
Bundled schemas continue to cover Betaflight 4.2, 4.3, 4.4, 4.5 and 2025.12.
New equivalence mappings require exact verified official releases and compatible
packs; vendor builds and other versions do not inherit certification. Existing
export formats and validation requirements are preserved. Collection comparison
does not add collection export.
Known limitations
- Equal declarations do not certify equal flight behavior, measured current,
consumption estimates, RF output, or build/runtime activation. - VTX activation comparison for 2025.12 requires additional build evidence.
Cross-version collection equivalence and broader parameter mappings are deferred. - Three-backup comparison, workspace indexing, portable sessions and native file
associations remain outstanding. - Twelve 2025.12 settings have unresolved bounds; hardware-specific schemas,
arrays and full unsigned 32-bit values still need additional coverage. - Packaged Windows/macOS native integration and feedback hand-off require manual
verification. Installers remain unsigned and macOS notarization is absent.
Release checks cover Rust and frontend tests, parser-to-renderer behavior, the
local backup corpus, and README screenshots. GitHub workflows build and publish
Windows and macOS installers.