DroneForge Nimbus App v0.0.1 continues the early Linux GPU path for Nimbus. The first release proved out the connection layer; this one starts moving closer to an actual development workflow for AI drones, model deployment, and autonomous drone experiments.
The biggest change is that Nimbus is no longer just about connecting to the drone and sending basic commands. v0.0.1 adds the first pieces of a programming workflow, with UI changes for deploying models and a new way to create scripts that can be sent to the drone.
Built for GPU Linux machines
Nimbus App v0.0.1 is still focused on GPU-enabled Linux machines. That keeps the development environment close to where most robotics, computer vision, and AI drone tooling already runs.
For developers building with ONNX Runtime GPU, OpenCV, CUDA Toolkit, or custom autonomy stacks, this release gives Nimbus a cleaner base for testing ideas against real drone hardware.
What changed
- New UI changes to make model deployment easier.
- A new programming feature for creating scripts that can be deployed to drones.
- The first version of Nimbus Map, a node-based configurator for building drone script flows.
- Bug fixes for early crash cases and rough edges found in the first release.
Nimbus Map
Nimbus Map is the start of a more visual way to configure drone behavior. Instead of treating every workflow as a single block of code, the node-based interface gives developers a place to shape how scripts connect, run, and get deployed.
That matters for development drones because the stack gets messy quickly: video input, model output, control logic, safety checks, and command dispatch all need to fit together. Nimbus Map is an early step toward making that process easier to inspect and easier to change.
Model deployment
The UI updates in v0.0.1 are aimed at reducing friction around model deployment. If you are experimenting with perception models, autonomy logic, or early AI drone behaviors, the Nimbus App now gives you a cleaner path from local development to running something against Nimbus.
This is still an early release, but the direction is important. Nimbus is becoming more than a connection utility; it is starting to become a development environment for autonomous drones.
Fixes
Several crash edge cases were cleaned up in this version. The release should feel more stable than v0.0.0, especially around the early UI and deployment flows.
Release context
This changelog entry is part of the DroneForge release archive for Nimbus and DF1. The archive helps builders understand how the autonomy stack has changed over time, including updates to setup, Nimbus App behavior, Python Library workflows, documentation, hardware notes, flight workflows, and community-facing product polish.
Older releases are still useful when comparing versions, debugging a local installation, or following the path from early drone connectivity work to current autonomous flight tooling. Use these notes as historical context alongside the current documentation, Nimbus App releases, and Python Library updates.
For current projects, compare these archived notes with the latest release before making setup decisions. DroneForge continues to refine how developers connect hardware, stream telemetry, inspect video, run agents, and build repeatable autonomy workflows.
Community archive
Continue exploring DroneForge changelogs, research notes, and Nimbus examples through the community archive. These internal links help connect related releases, technical notes, and builder resources.
- Version 2.1.4 - Changelog
- Version 2.0.0 - Changelog
- Version 1.0.10 - Changelog
- Version 1.0.9 - Changelog
- Version 1.0.8 - Changelog
- Version 1.0.7 - Changelog
- Version 1.0.6 - Changelog
- Version 1.0.4 - Changelog
- Version 1.0.3 - Changelog
- Version 1.0.2 - Changelog
- Version 1.0.1 - Changelog
- Version 1.0.0 - Changelog
- Version 0.2.0 - Changelog
- Version 0.1.0 - Changelog
- Version 0.0.0 - Changelog
- FLIP - Research
- Nimbus App and Python Library Examples - Examples