v0.16.1 (New Calibrations & Visualizer Fixes)
View this release on GitHub → Release Date: July 17, 2026
A visualizer bug-fix patch, plus new default background-noise calibrations for three Carbon sensors. There are no API changes.
Interface contract:
carbon-interfacev1.3.3 (unchanged from v0.16.0) Firmware compatibility: unchanged from v0.16.0
New Supported Units
- Background noise calibration: default masks added for
CAR-30-012andCAR-30-014, and updated forCAR-30-013. Required to bring up these sensors through the compiled binaries (visualizer, CLI, Python/C++ bindings).
New Features
- Playback’s “Show invalid points” setting is now a live toggle. A checkbox in the rendering panel (playback only) shows or hides sensor-flagged invalid points at any time, including while paused. The
--keep-invalid-pointsCLI flag still sets its initial state at launch.
Bug Fixes
- The health panel no longer drifts out of sync with a paused live view. Pausing a live stream freezes the point cloud, but the sensor-state readout (calibration and current SDL configuration) kept updating in the background; it now freezes along with the point cloud. Time-sync, comms-health, and heartbeat-liveness readouts still update live, since they reflect present-tense connection health rather than the frozen frame’s calibration.
- Fixed a false latency spike after unpausing a live stream. Any point-cloud regeneration while paused — e.g. changing a filter or color setting — was incorrectly recorded as a new frame’s timing sample, so the latency/FPS stats could show a large, misleading spike right after resuming. Only actual new frames now feed those stats.
- Switching data sources no longer leaves the previous frame on screen. Reconnecting live or switching to playback now clears the display immediately, instead of showing the previous source’s stale point cloud until the new one delivers a frame.
Documentation
For comprehensive documentation, examples, and installation instructions, visit our documentation site.
Feedback
We value your feedback! If you encounter issues or have suggestions for improvements, please see our troubleshooting guide for the best options for getting in touch with us.