Repository navigation
Altnautica Command v0.66.0
This release covers 106 commits from 2026-11-14 to 2026-11-20, since 0.65.0.
Three threads run through it.
The first is the cockpit working with the agent's onboard pilot. A take-off
goes through the pilot's launch and shows the steady take-off on the launch
strip, the flight-state chip names the speed profile, a late stick and the
limit that cut the commanded speed, a position the drone cannot vouch for
reads red, a mission that stops making progress gets a stall card, and a
confined place class keeps a wall margin from the planner to the send dialog.
Controller-free flight has its groundwork: a No controller chip, a per-tab
pilot stream that ends in the link-loss action when the tab freezes, and
controller rumble and light bar driven by one shared rule table.
The second is the extension split. Capture, Reconstruct and Navigation are
separate extensions, the new Map tab draws Navigation's live map in 2D and 3D
and joins the Reconstruct compute node's live stream, and Follow Me gains its
recovery phases, quick settings on the rail and the standoff and height floors
of follow-me 0.5.
The third is the ground station: a ground station agent on the operator's
own computer is reachable from the hosted page, and the Radio tab shows which
ground holds the uplink and takes it back from a phone.
Added
- Map tab: while the map's placement is
stream, Mission Control reads the drone's live stream on its Reconstruct compute node (/api/plugins/com.altnautica.reconstruct/x/ws/live/<drone>, the node the drone's Capture readiness names): the node's occupancy tiles join the live map and its sweep points draw over the 3D view, and the status card names the compute node and whether its stream is live, connecting or not reachable from this browser. A closed stream is dialled again every 2 s. Demo: the demo drone streams to the demo workstation. New dependency@msgpack/msgpackfor the stream's framing. - Flight-state chip: while a skill, a goto or the sticks fly, the secondary line says which limit cut the commanded speed, from the pilot's
command.limits("Slowed: obstacle", "Slowed: sensor range", "Stopped: obstacle", ...), as the agent's cockpit does. - Map tab: shown while the drone's Navigation extension publishes a live map, with a 2D and a 3D view. 2D is the local-frame map with the
map.overlayslot over it, so an extension layer (Capture's coverage) renders in the map's frame; 3D is Navigation's live sweep cloud (/navigation/sweep), coloured by height, with the drone's pose. The status card reads Navigation's map status: placement, memory, voxel size, sweep points, area, the pose provider and the FC IMU feed. Demo: the demo drone's room cloud. - Demo: the Capture, Reconstruct and Navigation extensions are installed from their manifests, with demo stand-ins for their pages (the Capture surface shows the capture monitor, Navigation's Agent page the navigation panel).
- Demo follow-me: a follow distance set below 5 m, the least on a camera's range alone, is flown at 5 m and read back as standoff_min_m, standoff_raised and standoff_reason; the distance setpoint reads "at least 5.0 m with camera-only range", as in follow-me 0.5.0.
- Demo follow-me: a follow height set below 3.4 m (a 2 m subject, 0.4 m of rotor and 1 m between them) is flown at 3.4 m, and the height setpoint reads "kept above head height for safety". The height setting's least value is 3.4 m, in 0.1 m steps, as in follow-me 0.5.0.
- Controller-free flight groundwork. The aircraft setup wizard's "Meet ADOS Pilot" step offers "Use ADOS Pilot with no controller" with a line on what stops the drone without one; it leads when the agent saw no RC receiver. While the drone is declared to fly with no RC transmitter, a "No controller" chip sits beside the Confined chip on the top bar, and the new readiness items and refusals read their words from the shared spec. Demo: the demo pilot and setup wizard answer the declaration and its refusals.
- Cockpit: a take-off goes through the pilot's launch. While the drone's steady take-off runs, the launch strip shows its status line and detail, and the status pill lists the Balance check and Steady take-off rows from the drone, with "I rebalanced it" on a failing Balance check of a disarmed drone. The steady take-off ships switched off on the agent.
- Plugins:
command.sendtakeoffis refused ("Not armed") until the drone is known to be armed, before the confirm prompt, on every route: the operator arms first. - Pilot stream: every frame names this tab with an instance id that stays the same across reconnects, so the drone keeps one link-loss timer per tab, and the tab says goodbye before a deliberate close (switching the drone, closing or leaving the page). The heartbeat is timed by a Web Worker, so a hidden tab's throttled timers no longer look like a lost link. While the tab holds the sticks it beats only while the page itself is responsive, so a frozen operator tab ends in the link-loss action. With no RC declared and the drone armed, closing the tab or switching the drone first warns "Leaving ends in in
s", and switching can be cancelled. - Controller feedback: the pad rumbles from pilot-state changes by the shared rule table in the cockpit spec, the same rules every surface runs. A profile, owner, skill, control-mode change or a takeover plays the mode-change pattern; avoiding or blocked, a new hold reason, a speed cap coming on or a new readiness warning plays the warning; a lost controller, the link-loss or low-battery countdown, a failsafe, a new blocking item while armed, or the pilot state going stale is critical. One update plays only its strongest class, once.
- Controller light bar: while the operator's sticks fly, the bar shows the speed profile (Cine soft green-cyan, Normal blue, Sport orange); failsafe, low battery, RTH, mission and skill keep priority, and goto, swarm and tuning show the plain pilot blue.
- Cockpit: the flight-state chip names the profile with its horizontal limit ("Normal · 7 m/s"), shows a stick input older than 100 ms, and shows the nearest obstacle in amber when it is under twice the margin and in red inside it. Where the bottom row has no room for the speed readouts, the chip carries the horizontal and vertical speed while the sticks fly. Warning and critical facts on the chip keep their colour.
- Cockpit: the on-screen sticks follow the operator's deadzone and stick mode (Mode 1 flies forward on the left pad and climbs on the right), draw the deadzone as a ring on each pad above the knob, and are checked against the shared stick golden vectors.
- Cockpit: the proximity radar reads "No returns" in the warning tone when a fresh lidar scan has no return in any bin and nothing else reports a distance, where it read Clear: a lidar that sees nothing is not the same as open space. A return is a finite range above 5 cm, the pilot's own rule, so a scan of only near-zero bins no longer reads as an obstacle at 0.0 m. The shared spec carries the new words ("No returns", "Lidar no returns").
- Cockpit: a position the drone cannot vouch for reads red. The flight-state chip shows "Position unverified · " (after the flight controller's RTH, Landing and Transition chips, with Take control while the flight controller flies its own mode), the reason read in words from the shared spec, a lost heading or IMU feed included. The hold reads "Holding · position unverified", and the nav-source chip turns crit with FLOW DISAGREES, CORRIDOR or UNVERIFIED. Fly here is not offered while the position is unverified, through the pilot or as a reposition in GUIDED, and the pilot's refusal and readiness item read "Position unverified (nav); fly manually or land" and "Position check (nav)". A stale pilot frame never keeps the nav chip crit. Demo:
__adosDemoPilot.pinreaches the state. - Cockpit: a mission or return that stops making progress shows a stall card next to the countdowns, with Skip waypoint, Return and Land here (a blocked return offers Land here only) and the time left before the pilot acts on its own. The status pill lists the stall, the voice prompts speak it, and the Flight map marks the waypoints the drone skipped. Demo:
__adosDemoPilotpins a stall, counts it down and answers the three actions. - Cockpit and planner: a confined-space place class. The Launch sheet and the planner pick Open or Confined space and show the margin each keeps (a confined place keeps the propeller-tip radius plus 0.1 m). A plan saves its class, in the plan library, the native file, a
.planand a share link; a plan with an unknown class loads as Open. The Launch sheet launches only once the pilot flies with the chosen class. A Confined chip on the top bar opens the route check: whether the route keeps the margin, the tight leg with its clearance and the clearance needed, a mission the agent has not downloaded yet, the waypoints the check could not place, and the speed cap near walls. The send dialog shows the same report before a mission is flown. Demo:__adosDemoPilot.confinedPins("feasible" | "unverified" | "infeasible"). - Follow-me recovery phases. When follow-me loses its subject, the range
readout under the top bar follows the recovery: Predicting, Moving to look
and Searching, each with the seconds left of the search budget, then
"Waiting for you" in the critical colour once the drone holds for the
operator. The lock chip reads "Waiting for you" too. The re-acquired notice
names what hid the subject when the drone reported it. A follow report
older than 2 s blanks the values and reads Stale. - Waiting prompt. While follow-me holds for the operator, a prompt drops
from the follow strip and says why: the search found nothing, the lock was
lost, predictive search is off, no prediction is left, or the follow camera
stopped sending frames. It offers Search again (R), Pick a target (P),
Return home (H), Land (L) and Stop following (X). Search again is left out
in strict re-acquire, with no prediction left, and while the camera sends
nothing. Return home and Land run the same checks as the left column. The
prompt never takes focus: its keys answer only once focus is inside it, and
a tapped button hands focus straight back, so a key meant for another
binding never presses a prompt action. Critical alerts stack below the
prompt instead of covering its title. - Follow quick settings on the rail. The follow strip carries STRICT |
SMART re-acquire, FOLLOW | HOLD for when the tracker is unsure, and the
predictive search switch, which shows only in smart re-acquire. A change
shows a dashed outline until the drone confirms it. If no confirmation
arrives within 3 s, the control goes back to the drone's value and a
warning names the setting that was not applied. On a narrow strip, such as
a phone held upright, the settings move behind a More button, and the
buttons show icons only, so REC and the range readout stay on the row. - Recovery on the maps. While the subject is sought, the local-frame
minimap and the geographic map draw the search area, the predicted path and
the point the drone moves to for a clear look, under the follow target. - Recovery in the demo. The demo follow loses its subject, predicts,
moves to look, searches, finds it again under a new track, and on the next
loss holds and waits for the operator. Search again resumes the search, and
the quick settings take effect in the demo. - Steady boxes while following. While a target is designated, the
agent's vision engine detects most frames only in a window around the
subject. The video overlay keeps the boxes from the last whole frame that
sit outside that window until the next whole frame, or for one second, so
other people and objects no longer blink at the whole-frame rate; over a
ground station's relay the agent's reply carries that whole frame. Plugins
and the pipeline counts see only what each frame detected. A batch from an
older agent, without the window, draws as before. The demo follow sends the
same windowed batches. - Uplink card on the ground station's Radio tab. It shows whether the
station transmits, or stands by while a named phone holds the uplink (since
when, with that phone's last presence beacon), or is unknown while the radio
service is not reporting. Take back asks first. The phone receivers card now
says an approved phone receives and may take the uplink. Demo: the station
stands by while a phone holds it. - Use this computer as ground station. The Add node form offers a ground
station agent running on this computer, reached over loopback from the
hosted page once the browser allows it; without an agent it shows the
install command. A This computer settings page chooses whether the node
answers this computer only or the local network, and states that Wi-Fi,
display, power settings and system updates stay the operator's. - Plugins reach a companion extension.
host.agentFor(plugin)and
host.nodes.agent(deviceId, { plugin })call another extension's routes
when the module holds theplugin.http.<plugin>grant; without it every
call rejects withplugin_not_granted. The grant is read per call, and the
install dialog labels it. A frame or inline module also learns which
contribution it was mounted as (#slot=andpanel=in the frame URL,
ctx.mountinline), so one bundle can serve a cockpit panel and an Agent
page. - A 320x320 person detector. The YOLOX-Tiny person model lists a
cpu_fp32_320variant for Follow Me's crop pass; the whole-frame pick stays
640.
Changed
- The capture session list, the navigation topics and the plugin ids follow the extension split: sessions come from
com.altnautica.capture(/x/capture/sessions), the pose, scan, map status and the sharedplugin.navigation.statetopic fromcom.altnautica.navigation, and the reconstruction node fromcom.altnautica.reconstruct. The Map tab's launcher for the old 3D viewer page is gone. - Cockpit: the sticks' flight-state chip drops its "Pilot · " prefix and reads the profile first ("Cine · 3 m/s", "Normal" without a limit); the control mode line below still names ADOS Pilot.
- The pilot stream keeps only the newest stick frame while its WebSocket still has unsent bytes, so a slow link flies the latest stick rather than a queue of old ones; a release drops a waiting stick frame.
- Settings › Input: the expo slider reads "Stick expo (direct flight controller only)" and says the onboard pilot uses the speed profile's own curve.
- Internal only: the cockpit frame helpers are split into smaller modules under the size limit (no behaviour change).
- Cockpit: the shared sensor-health spec carries the agent's new lidar map heading readiness item, "Lidar map heading not confirmed". The cockpit shows it as the drone sends it, with no other change.
- Internal only: the cockpit mission parsers and the node command lanes move into their own modules under the size limit (no behaviour change).
- The plugin contract catalogue mirrors the agent's
pilot.v14: a goal may
ask for a commanded velocity instead of a feed-forward. - The plugin contract catalogue mirrors the agent's
pilot.v15: a goal may
carry the error of its subject's range, which widens the distance the pilot
keeps from the subject, and a pilot command limit may name the subject. - Return all and a relayed drone's Return send the drone's own agent its return, which the pilot flies back along the flown path in ADOS control, instead of the flight controller's straight-home RTL. A drone seen only through a ground station's relay gets it through that ground station. When the relay does not answer (the ground station unreachable, its radio lane down, a timeout), the flight controller's RTL goes out over the live MAVLink session and the result says so; a refusal from the pilot is shown as it is.
- The planner's built-in camera presets are named by sensor format, resolution and focal length. A plan saved under a retired preset name loads with the renamed preset.
- The cockpit status pill steps its flash twice a second instead of fading at 60 frames a second.
- Links and references point at the repository's new name,
altnautica/ADOSMissionControlGCS.
Fixed
-
The compact and portrait cockpits show the sticks' facts in the flight-state chip. The compact chip face dropped every secondary part, so the horizontal and vertical speed, a late stick input and the obstacle clearance showed nowhere where the on-screen sticks fly. The compact face now keeps those four parts and still drops the rest.
-
The pad's pilot route is checked against the shared stick vectors. The radial deadzone and the stick-mode swap the gamepad poller applies now live in one pure function, and every shared golden case runs through it in both stick modes.
-
A low-battery landing countdown says it will land. When the pilot's low-battery action is to land, the countdown card read "Returning along the flown path". It now reads "Low battery: landing in N s", as the agent's own cockpit and TUI do.
-
A return or landing the pilot accepted no longer reads as failed. In ADOS control the agent answers a flight command with the pilot's verdict, which the GCS read as "no acknowledgement". An accepted verdict now reads as accepted, and a refusal shows the pilot's reason.
-
Opening a node's Flight tab no longer stalls the whole app while the
cockpit loads. Node tab bodies load on first open, and none of them had a
loading boundary of its own. Opening Flight on a cold load suspended the
entire page until the cockpit arrived, and on a slow load React could throw
"Maximum update depth exceeded". The tab body now shows a "Loading panel…"
status while it loads, and the rest of the page keeps updating. The
cockpit's quick settings, command palette and skill-bar editor load the same
way on first open, so opening one never blanks the video and HUD. -
The production build works again. The cockpit's on-demand sheets passed
their loading option tonext/dynamicthrough a shared constant, which the
production build rejects ("next/dynamic options must be an object literal").
Each sheet now passes it inline, with the same behaviour. -
A vantage-goal hold reads "No clear view". When the pilot holds a skill's
vantage goal because no reachable point sees the subject's predicted area, it
reports the hold reasonno-vantage. The cockpit spec now gives that reason a
label, so the flight-state chip reads "No clear view" instead of the raw key.
A hold on stale scans still reads "Holding: no fresh obstacle data". -
Plan 3D and Simulate show waypoint and rally numbers. A label created
on a ground-clamped marker kept a stale position underground after the
marker was rebuilt at an absolute height. Labels are now made only for a
marker with an absolute position.
All 106 commits since v0.65.0
- cockpit: the vantage-goal hold reads No clear view; regenerate the agent contract mirror (e99e57c)
- cockpit: the status pill says why the setup air run aborted; sync the shared spec (8e7b684)
- node panel: catch a loading tab body in its own Suspense boundary (b4dd9d7)
- cockpit: give on-demand sheets their own loading boundary; status fallback for tab bodies (c65d9a4)
- cockpit: an unverified position reads red on the flight-state and nav-source chips (bac223f)
- cockpit: an unverified position keeps the RTH and Landing chips, offers no Fly here, and words its refusal (fa7bbc1)
- hud: split the cockpit frame grids under the size ratchet (500c938)
- cockpit: pass the sheets' next/dynamic options as object literals (585ebfe)
- cockpit: sync the sensor-health spec for the lidar map heading item (9873625)
- cockpit: mission stall overlay, skipped waypoints on the route, return over the pilot (4c83b22)
- cockpit: spec sync, the held mission stall banner and the safety profile text (c066f21)
- cockpit, planner: confined-place profile; the stall overlay hides its own banners (04191f1)
- hud: sync the shared HUD files and cockpit spec; mission parsers move to cockpit-mission.ts (e659b09)
- nodes: move the command lanes and the relayed-node reach out of command-sink.ts (f0b2979)
- nodes: a relayed drone's return falls back to the flight controller's RTL when the relay does not answer (54561f5)
- agent client: read the pilot's verdict as a command's answer (b3100e2)
- planner: a plan with an unknown place class loads as open (b8de864)
- demo: the confined pilot checks the route only for a launch into the mission; open drops its route check (fdf179d)
- fleet: Return all reaches a relayed drone through its ground station (cbf0cc7)
- changelog: mission stall card, confined place class, relayed return, pilot verdict (db37f1b)
- cockpit: the low-battery countdown reads landing when the pilot will land (f105a35)
- cockpit: sync the spec: the confined profile asks for the vehicle's outer radius; an unchecked route may be one not downloaded yet (6a46d5b)
- cockpit: the route check says when the mission is not downloaded yet (3e6a038)
- cockpit: sync the spec: the lidar no_returns state and the radar's No returns (d0a9ae1)
- cockpit: the proximity radar reads No returns for a fresh scan that saw nothing (bc781e4)
- cockpit spec: the unverified route line says the route is checked in flight at each leg's height (8e6b89a)
- cockpit: a confined operator wait counts down to the return home (ec13626)
- cockpit spec: sync the setup strings: the no RC chip, leave warning, readiness items, refusals and setup action (0261cda)
- cockpit: read the no RC declaration from the pilot state and show a No RC chip beside the Confined chip (7c29086)
- pilot stream: name the tab with an sid on every frame, say bye before a deliberate close, time hb from a Worker gated on the operator tab's liveness, and warn before leaving armed with no RC (e07294a)
- aircraft setup: the ADOS Pilot intro offers use_ados_no_rc with its no RC line; the demo wizard mirrors it (9a2f966)
- demo pilot: the no RC declaration, its refusals and readiness rows, and the bye op (13ccb07)
- changelog: controller-free groundwork and the pilot stream instance id (7d731d3)
- cockpit: the banner for a stall that lands in place when no operator answers (5602297)
- cockpit: golden vectors pin the on-screen sticks' signs: a pad dragged up flies forward or climbs (beb868c)
- planner: name the built-in cameras by sensor format, keep saved plans loading (adfd0ca)
- cockpit spec: the readiness item for a launch waiting on external navigation to settle (ba21d76)
- cockpit: follow recovery phases, the waiting prompt with its actions, and the search area, vantage and predicted path on the maps (b21ebee)
- cockpit: follow quick settings on the rail, a waiting prompt that never takes focus, and demo recovery fixes (647a7ea)
- cockpit: a follow quick setting that is not applied names the setting, never a bare Failed (bdd5d24)
- cockpit: the follow rail fits a portrait strip, and predictive search shows only in smart re-acquire (6f545d1)
- cockpit: a tapped prompt button keeps no focus, and critical alerts stack below the waiting prompt (f36edc9)
- changelog: follow recovery, the waiting prompt and the rail quick settings (7802684)
- cockpit: the follow setting toggles are private to the quick settings group (3747bf8)
- test: the demo detection cycle re-acquires with its search fields and ends holding for the operator (95eb6f4)
- cockpit: the skill bar badges an older follow's coasting as predicting and its lost as holding (c7bb654)
- mock, hud: one pin drop helper, and the follow pin and nav narrowing helpers split out under the size limit (d8d44f1)
- plugins: the contract catalogue mirrors the agent's pilot.v1 4 (a goal's vel_mode) (aebf2a5)
- vision overlay: a crop-only detection batch keeps the last whole frame's boxes outside its window for up to a second; the demo follow sends windowed batches (f2918f3)
- vision overlay: a polled crop-only reply's full_frame seeds the held boxes; plugins and pipeline counts leave held boxes out (7eefb3e)
- models: the YOLOX-Tiny person detector gets a 320x320 ONNX variant (3b3f3a4)
- cockpit spec: the battery failsafe readiness item's warning for an unset pack capacity (3b896d4)
- cockpit spec: per-profile light bar, the shared feedback rule table, stick golden vectors and the stick chip parts (15e4974)
- controller: the light bar shows the speed profile and the pad rumbles from the shared pilot-state feedback rules (460820f)
- cockpit: the flight-state chip names the profile limit, a late stick input, the obstacle clearance and the speeds (c7c6fc2)
- cockpit: the on-screen sticks follow the operator's deadzone and stick mode, with a deadzone ring (37a1ac6)
- pilot stream: keep only the newest stick frame while the socket has unsent bytes (c71382f)
- settings: the expo slider says it applies to the direct flight-controller route only (e69ee8b)
- cockpit spec: the profile limit reads without "max" (ed6088f)
- controller: a stale pilot frame delivered again does not re-fire the lost-state rumble (b1d5b2b)
- cockpit: the on-screen deadzone ring draws above the knob (0c0b8ab)
- controller: a takeover rumbles only when another source or session replaces the one flying (f12cc67)
- cockpit spec: the sticks' chip reads the profile first, without the Pilot prefix (3091af7)
- demo follow-me: the follow height floor and its read-back (d51f8ab)
- cockpit spec: the words for the pilot's subject command limit (87c2a4b)
- plugins: the contract catalogue mirrors the agent's pilot.v1 5 (a goal's subject_sigma_m) (d3bbaa8)
- cockpit: compact chip keeps the sticks' parts; pad route runs the stick golden vectors (a86369f)
- cockpit spec: the subject limit reads keeping clear of the person (9f9989d)
- cockpit: compact and portrait grids no longer hide the chip's kept parts (881124f)
- cockpit: on a compact bar the chip's stick facts shrink before its state text (c334536)
- cockpit: take-off goes to the pilot's launch, and the lift-off shows on the launch strip (b0084a6)
- cockpit: steady take-off status line and detail, balance check labels and stop texts (7f1a770)
- cockpit: a plugin take-off waits for the operator to arm; I rebalanced it only while disarmed; take-off strings from the agent spec (5765342)
- demo follow-me: the minimum standoff and its read-back (c018f4a)
- cockpit: a plugin take-off is refused until the drone is known armed (622b938)
- no-RC: the setup intro test and the mock pilot read the no-RC declaration (5a7076b)
- cockpit tests: the steady take-off steps and the plugin take-off outcome (2cc7407)
- release 0.118: test frames carry the pilot stream instance id; plugin take-off tests arm first; unfinished steady take-off test drafts left out (77c54fc)
- changelog: the no-controller words as the spec reads them; the steady take-off surfaces and the armed plugin take-off (e6edf34)
- ground station on this computer: reach a loopback agent from the hosted page, This computer settings, Use this computer as ground station (e2ee248)
- cockpit: the status pill steps its flash twice a second instead of fading at 60 fps (c5bd95d)
- Point Mission Control references at the renamed ADOSMissionControlGCS repository (4d35aee)
- Plugins: a frame learns which contribution it was mounted as (617f728)
- Let an inline module reach a companion extension's server (1cd527d)
- Map tab in 2D and 3D from Navigation; Capture, Reconstruct and Navigation in the demo (0130e9d)
- Strip and sidebar order of the Capture, Reconstruct and Navigation pages (d572e01)
- Radio tab: which ground holds the uplink, and take it back from a phone (aec12c2)
- Phone receivers card: an approved phone may take the uplink (91f7e95)
- Locales: the missing loopback, this-computer and add-node strings in every language (b9cf025)
- Map tab keeps polling the live sweep while it is unavailable; plugin.http grants read as extension-scoped (862835f)
- Navigation state reads from plugin.navigation.state (d3f1d21)
- Navigation manifest mirrors carry the Livox UDP ports; capability descriptions regenerated (3d0d31e)
- Demo pilot: stick limits per profile, the stick block, steady take-off phases and airframe reset (95436af)
- Live sweep hook publishes the cloud through state instead of reading its ref during render (33fc34d)
- Fleet status drops the never-set WHEP and MAVLink port hints (7fba0aa)
- nav-stream test follows the map status without the retired upload and stream rows (783e5d4)
- Tests drop the removed WHEP and MAVLink port hints (3e2bed6)
- Planner 3D and Simulate draw waypoint and rally numbers once their marker has an absolute position (942dc3b)
- Flight-state chip shows the pilot's command limit (f7e430a)
- Checklist test expects the demo pilot's balance readiness row (d00975a)
- Navigation manifest mirrors list the Livox discovery and debug ports (4369d5b)
- Map tab reads the Reconstruct compute node's live stream (d5b5ca2)
- German map tab: the compute node reads 'verbunden' when live (a130e6a)
- Record unreleased changes in the changelog (e87bdfa)
- Pilot stream: the coalescing sender and the session ids move out under the size ratchet (4451f36)
- Demo catalog mirrors the newest first-party releases, generated by a sync script (9d5b1be)
Full diff: v0.65.0...v0.66.0
Downloads
- Windows:
.exeinstaller, 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.