Skip to content

0.65.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 08:41
· 122 commits to main since this release

Altnautica Command v0.65.0

This release covers fourteen commits over 2026-11-13 and 2026-11-14, since
0.64.0. Two threads run through it.

The first is the cockpit telling the pilot what the drone will and will not
do. The flight-state chip shows the speed cap the drone applies without
GNSS, reads stale or missing obstacle data in the warning colour,
and keeps a blocked go-to on the map and in AR. Resume and Take control are
refused while the flight controller flies its own failsafe, and Copter
BRAKE reads as the flight controller's mode rather than a landing.

The second is a configuration fix: optical flow yaw is edited and checked in
the units ArduPilot uses, on every path that writes it.

Added

  • Planned path on the local-frame map. While a go-to or a skill flies and
    the pilot's frame is fresh, the local-frame minimap draws the pilot's
    planned path as a dashed line and a ring on its goal, in the go-to colour,
    or in the blocked colour while the pilot reports the way blocked. It
    matches the drone's own cockpit and the Android app.
  • GNSS-denied speed cap on the flight-state chip. When the drone caps its
    horizontal speed because it flies without GNSS, the chip's second line reads
    "GNSS-denied: 2.5 m/s max", rounded to one decimal, in the avoiding colour.
    The demo pilot can show it.
  • Stale or missing obstacle data. When avoidance is on and the drone's
    lidar stops reporting, the pilot holds position and refuses motion until
    fresh scans arrive, and reports the stale avoid state with the hold reason
    obstacle-data-stale: the flight-state chip reads "Holding: no fresh
    obstacle data · Obstacle data stale" in the warning colour and the AR path
    draws amber. A drone with no lidar reports unavailable, read as "No
    obstacle sensor" in the warning colour; its sticks fly, Fly Here is refused
    with its own reason, and the readiness list warns "Lidar".

Changed

  • macOS desktop builds are optional. The desktop release workflow builds
    the macOS app only when the repository variable MC_MACOS is true, and
    publishes the Windows and Linux builds without it. When a release ships
    without macOS, its notes say so.

  • Resume and Take control during a flight-controller failsafe. While the
    flight controller flies its own failsafe return or landing, Resume and Take
    control are disabled with the failsafe text, as Pause already was: in the
    skill list, on the flight-state chip button and in the Mode sheet. Until the
    flight controller's mode has been heard, the chip shows it as unknown.

  • Copter return and brake modes on the chip. Copter AUTO_RTL reads as the
    flight controller's return. Copter BRAKE, which holds position, reads as the
    flight controller's mode with a Take control button instead of as a landing.

Fixed

  • Optical flow yaw in centidegrees. Configure > Sensors edits
    FLOW_ORIENT_YAW in centidegrees (-17999..18000 in steps of 10, presets 0,
    ±9000 and 18000) and names the centidegree value an old 1..7 setting meant.
    The Sensors panel (its Save button and Ctrl+S), the Parameters grid and
    parameter file import all refuse a value off the 10 step or out of range,
    with or without the vehicle's parameter documentation. The field used to
    offer 0..7 in 45° steps, which ArduPilot reads as 0.01..0.07°.

  • The demo pilot refuses Take Control during an FC failsafe. As on the
    agent, Take Control, Resume, Takeoff and Launch return failsafe while the
    flight controller flies its own failsafe return or landing; handing the
    drone to an FC mode ends the failsafe, and Take Control works again.

  • A blocked go-to stays on the map and in AR. With agent 0.109.134 and
    later, a go-to the drone holds because a wall blocks the way keeps its goal
    and the straight way to it on the pilot frame, so the local-frame map draws
    both in the blocked colour instead of dropping them. The AR goal ring now
    takes the blocked colour too, as the path already did.

All 15 commits since v0.64.0
  • Desktop release: build macOS only when MC_MACOS is true, and publish without it (ed989c4)
  • local minimap: planned path and goal (300b87f)
  • Changelog: planned path on the local-frame map (8a70319)
  • Docs: note that macOS desktop builds are optional in releases (4f0ca88)
  • AR goal ring and local map keep a blocked go-to in the blocked colour (b1343d3)
  • Changelog: spacing (edd51ec)
  • cockpit: show the GNSS-denied speed cap on the flight-state chip (06a2cad)
  • Refuse take control, resume and launch in the demo pilot during an FC failsafe (e26a5bc)
  • cockpit: round the speed cap to one decimal on the flight-state chip (879b185)
  • cockpit: show stale and missing obstacle data on the chip, the AR path and readiness (4cb5f13)
  • cockpit: Resume and Take control are disabled during a flight-controller failsafe; an unheard FC mode shows as unknown (a34a0a9)
  • cockpit spec: Copter AUTO_RTL and BRAKE chip as the flight controller's return and landing (af76d7f)
  • cockpit spec: Copter BRAKE chips as the flight controller's mode, not a landing (31906f8)
  • sensors: optical flow yaw in centidegrees with validation before save (dc58264)
  • Record unreleased changes in the changelog (40be2e8)

Full diff: v0.64.0...v0.65.0


Downloads

  • Windows: .exe installer, unsigned
  • Linux: .AppImage

These installers are not code-signed. Check a download against
SHA256SUMS in this release (sha256sum -c SHA256SUMS --ignore-missing).

For the latest web version, visit command.altnautica.com.