Your system is set to reduce motion, so the swarm is paused. This screen has thousands of moving drones, and a jamming storm with red flickering and glitch bands every 34 to 41 minutes.
This page is the command screen of an imaginary fleet of 2,048 autonomous drones, flying over a green wireframe landscape of ridges and valleys. The swarm holds one shape after another: a sphere, a halo ring, a double helix, a lattice, an arrowhead, a torus knot, a starburst, and a rippling wavefront. Between shapes it cruises as a loose flock. Now and then it lines up into a wall and sweeps a sector of ground, tagging what it finds, or splits into four squads that fly off to circle waypoints. About every 35 to 40 minutes a signal-jamming storm rolls through: the drones lose their link and scatter, then re-link one by one and regroup into a rally sphere. Click ⛶ FULLSCREEN and it fills the screen.
No. It is an animation, and the bar under it says SIMULATION. The fleet, the terrain, the four squadrons, the contacts, the grid references, the batteries, and every line of the ops log are invented and drawn in your browser. The page tracks nothing, controls nothing, and makes no connections while it runs. "Theater 04" is not a real place.
It is a film-style picture, not a real ground control station. Real drone operators see far plainer screens, and no real system flies two thousand drones into a torus knot over a mountain range for ten hours. The section on how real drone swarms work below explains what the real thing is like.
Moments worth seeing in the first part of the cycle (seek with the bar or use ?t=):
| Time | Seconds | What happens |
|---|---|---|
| 00:00:00 | 0 | Fleet launch: the drones rise from the ground into a sphere |
| 00:00:52 | 52 | Double helix |
| 00:01:47 | 107 | First scan, sector H7; three contacts tagged at 2:19 and 2:35 |
| 00:02:59 | 179 | Torus knot |
| 00:03:54 | 234 | First squad operation: four squads fly to their waypoints |
| 00:12:00 | 720 | First jamming storm; the mesh link is lost at 12:09 |
| 00:12:34 | 754 | Jamming field fades and the drones start to re-link |
| 00:12:46 | 766 | Rally sphere; swarm restored at 12:50 |
| 00:45:41 | 2741 | Second jamming storm |
Over the full ten-hour cycle there are 281 formation changes plus 16 rally spheres, 90 flock cruises, 74 sector scans that tag 231 contacts, 89 squad operations, and 16 jamming storms, spaced 34 to 41 minutes apart.
?t= and the number of seconds to the address, for example /drone-swarm?t=720 for the first jamming storm. Minutes and hours also work: ?t=12m or ?t=1h25m.The page draws at the full resolution of your screen, up to 4K. On a slow computer it lowers the resolution by itself to keep the motion smooth.
Background screens for science-fiction and techno-thriller films, series, and music videos with a command centre in the story; ambient visuals for electronic music streams; a mission-control screen for escape rooms, tabletop role-playing sessions, airsoft and live-action games; and a moving display for a tech event, a drone club, or a classroom talk about swarms and flocking. The formations are calm enough to leave running for hours, and the jamming storms give a scene a moment of trouble. For OBS setup as a browser source, see the streaming toolkit.
A drone swarm is a group of drones that act together as one system. There are two very different ways to make that happen, and this screen borrows the look of both.
In 1987 the computer graphics researcher Craig Reynolds showed that a convincing flock of birds does not need a leader or a plan. He called his simulated birds boids and gave each one three simple rules about its nearby neighbours:
Each boid only looks at the few others near it, yet the group as a whole swirls, splits around obstacles, and rejoins like a real flock of starlings or a school of fish. The same idea, behaviour that emerges from local rules, sits behind much research on robot and drone swarms. Its appeal is that there is no single point of failure: lose a few drones, or the link to the ground, and the rest carry on.
The drone light shows that draw logos and animals in the night sky work the other way round. Designers build the animation in software, which plans a timed path for every drone and checks that no two paths come too close. The drones fly their own paths using satellite positioning, often with a correction service that brings the error down to a few centimetres, while a ground station monitors them and can stop the show. The drones are not reacting to each other at all. Shows with several thousand drones have been flown. The sphere, helix, and torus knot on this screen are much closer to a light show than to a flock: every drone has a set place in each shape.
Drones need two things from outside: a radio link to their operators, and a way to know where they are. Many swarms pass messages from drone to drone in a mesh network, so a drone out of range of the ground can still be reached through its neighbours; the "mesh hop latency" lines in the log refer to this. Position usually comes from GNSS, the family of satellite navigation systems that includes GPS, backed up by inertial sensors and, on some drones, cameras.
Satellite navigation signals are very weak by the time they reach the ground, so radio noise on the same frequencies can drown them out. That is jamming. Spoofing is subtler: it broadcasts fake signals so that a receiver calculates the wrong position. Control links can be disrupted in the same way. Interference with satellite navigation has been widely reported by airline pilots near some conflict zones in recent years. Operating a jammer is illegal for the public in most countries, because it also disrupts aircraft, emergency services, and phones.
Real drones are built to expect a lost link. Typical failsafes are to hover, to fly back to the take-off point, or to land, and some can carry on with a task using their own sensors. This screen's drones scatter in a wobbling cloud and then snap back together, which looks dramatic but is not how a real fleet would behave.
Nothing on this screen runs the boids rules. The whole ten-hour mission is planned in advance from a fixed random seed, as a list of segments: which formation, flock cruise, scan, or squad operation comes next and how long it lasts, where the scans and waypoints fall, and when the jamming storms arrive. Each drone's place in each formation is a formula: the sphere spreads drones evenly on a spiral, the torus knot is a trefoil curve, and the lattice is a grid 13 drones on a side. During a flock cruise each drone follows its own loop inside a flattened cloud, and during a storm a wobble is added to its position. Between segments every drone glides from its old place to its new one with a small personal delay. The terrain is a sum of sine waves, sampled on a 61 × 61 grid and drawn as ridgelines from back to front so the near hills hide the far ones. Because every frame is a function of the time alone, the page can jump anywhere in the cycle at once, and the same moment always looks the same.
No. It is an animation drawn in your browser. The fleet, the terrain, the squads, the contacts, the grid references, and every line in the ops log are invented. Nothing is tracked or controlled, and the page connects to nothing.
Two ways. Drone light shows are choreographed in advance: software plans a timed path for every drone, and each one flies its own path using satellite positioning, so the drones are not reacting to each other. Research swarms instead give each drone simple local rules, such as keeping its distance from neighbours, matching their heading, and staying with the group, so that coordinated movement emerges without a central pilot. These are the boids rules Craig Reynolds described in 1987.
It depends on how the drone is set up. Most are programmed with a failsafe for a lost control link or a lost satellite position: hover in place, fly back to where they took off, or land. Some can keep flying for a while on their own sensors. A real drone does not scatter in a cloud the way the swarm does on this screen. Using a jammer is illegal for the public in most countries.
Ten hours. The cycle holds 281 formation changes, 74 sector scans that tag 231 contacts, 89 squad operations, and 16 jamming storms. After ten hours it starts again from the beginning. The screen is calculated frame by frame rather than played from a recording, so it needs no download and never buffers.
Yes. Press N for the next event (a sector scan, a squad operation, or a jamming storm) and B for the previous one, or drag the seek bar. To open the page at a given moment, add ?t= to the address with the number of seconds, for example ?t=720 for the first jamming storm.
Yes. It is free to use for videos, films, streams, music visuals, presentations, and events. Click FULLSCREEN, or add the page as an OBS browser source at 1920 × 1080 or 3840 × 2160; the scene is drawn at the full resolution of the source.
There is no full-screen flash. During a jamming storm, every 34 to 41 minutes, for about half a minute: drones that have lost their link flicker between red and white several times a second, faint horizontal glitch bands flicker across the middle of the screen, a red glow pulses at the screen edges about once a second, the camera shakes slightly, and the warning banner blinks. When each drone re-links it shows a brief green flash. If your system is set to reduce motion, the page opens paused. See accessibility and visual effects for more.
Once the page and its fonts have loaded, the simulation makes no further network requests, so it keeps running if the connection drops. The optional VIDEO view streams from YouTube and needs a connection.
For more command-centre screens, pair it with the radar and sonar screen, the satellite tracking screen, or the rocket launch simulator. The tech dashboard is a busy wall of charts, and the Neon Grid city is another large scene full of moving lights.