How to run the demonstration and read the C2 console.
The demo is a real software-in-the-loop (SITL) simulation of the Visentrix autonomous drone swarm, flying under GPS and RF denial — the conditions the system is built for. You launch a scenario, and a high-fidelity simulation with live camera-based perception runs on our GPU server. You follow the flying drones in real time in the C2 console (the operator's common operating picture). Nothing here touches a real aircraft; it is the same software stack that runs on the drones.
Each scenario highlights one capability. Every one is a real Software-in-the-Loop flight of the actual Visentrix stack — the same code that runs on the aircraft, driven by the same automated regression tests. Here is what each does and what to watch for.
More on request. The stack does considerably more than these four — GNSS-denied road following, EW/APNT failover, target pursuit, comms-out rendezvous, natural-language tasking. Those run on the same substrate but are not in the self-service menu: we only offer scenarios whose automated pass criteria are green right now. Ask us for a guided session on any of them.
The entire swarm is waiting for you on the ground — this one is a sandbox, not a script, and it starts where a real sortie starts. You define the swarm (participants, formation, spacing) and you give the launch order; the fleet then takes off and stays up for the rest of the session. From there you drive it: draw a recon area on the map, load or build a mission, plan a road-following route, or type an order in plain language. The fleet carries out whatever you ask, as long as you want to keep exploring.
Watch for: the fleet sitting on the ground at the start — that is deliberate. Set the formation, then send the launch order and watch every drone arm, climb and take up its slot. After that, use the tasking panel (draw area / load mission / plan route / formation) or the command bar (plain language) and watch the swarm execute your orders live against the contacts on the map.
The drone works out where it is without any satellite navigation, by matching what its camera sees against known map features.
Watch for: the position estimate tracking the true flight path on the map — a live fix produced from imagery alone, with GNSS switched off.
The swarm is given an area and covers it autonomously in an efficient search pattern, detecting and tracking what it finds.
Watch for: the coverage sweep across the assigned sector and detected objects appearing as tracks on the map.
The elected master drone is lost mid-mission (its coordinator is killed outright). The swarm re-elects a new leader and the deputy resumes command — the mission never stops and never needs you to intervene.
Watch for: the COMMAND indicator in the header switching to the new master drone, while the fleet keeps flying.
The console follows one idea: one picture. The map is the single operating picture, and everything else annotates it.
| Element | What it shows |
|---|---|
| Map | The live operating picture. Drones and detected objects are drawn as standard military symbols (APP-6 / milsymbol), so the scene reads at a glance. |
| Roster | The fleet: each drone, its role and its status. One drone is the elected MASTER (the swarm's single gateway to you); another stands by as DEPUTY and takes over if the master drops out. |
| Tracks / entities | Objects the swarm has detected and is following, shown as symbols on the map with a heading/vector. |
| SITREP | The AI-generated situation summary (most prominent in the SITREP scenario). |
| Jammers & comms-loss zones | In the GNSS-denied / EW scenario, detected jammers are magenta markers and their estimated interference (comms-loss) areas are shaded magenta rings — the electronic-warfare picture on the map. |
| APNT banner | An amber “APNT ACTIVE — GNSS denied” banner appears when a drone has failed over from satellite navigation to vision/UWB, and names the source it is now navigating on. |
| Assignment / pursuit links | A cyan dashed line from a drone to a target shows which drone is covering or pursuing it (multi-target and pursuit scenarios). |
| Rendezvous overlay | In the comms-out rendezvous scenario: per-drone recon-area rings (amber while comms-independent, green once delivered), convergence lines to the rendezvous point, and a banner that flips to “shared blackboard MERGED” at reconvene. |
| COMMAND (header) | Which drone is the elected master right now. In the master-loss scenario you see it switch to the new leader live. |
| Autonomy & attention | The current autonomy level and anything the system wants you to look at — so you supervise by exception rather than micro-manage. |
Depending on the scenario, some panels are more active than others — e.g. the SITREP panel in the SITREP scenario, the jammer/APNT overlays in the GNSS-denied scenario, the assignment links in the multi-target scenario, or the command indicator in the master-loss / C2-loss scenarios.