Quick start
Three steps from a fresh login to a sharable show.
.usd, .path3, .mat or .csv file - or a .zip of any of them.Topics
Uploading shows
Supported formats
The format badge on each show follows the file content, not the extension - a .zip of .path3 files reads as PATH3.
.usd.usda.usdc.usdzPixar USD scenes. One file per show. Cameras embedded in the scene can be imported separately..path3One file per drone - multi-select them all at once, or pack into a .zip / .7z / .tar.gz..matMATLAB matrix file. Fields must follow our exporter convention - email support a sample before uploading several GB..csvPer-drone files from Skybrush Studio or Crostars (header uavid,lon,lat,alt,r,g,b,land_flag - detected automatically, 25 fps). Same multi-file or archived workflow as PATH3..jsdmOne JSON file holds the whole show: positions (metres, Z up) and RGB per drone, keyed in milliseconds - the frame rate is read from the key step..blendBlender scenes. Drones are detected automatically as sphere-shaped meshes. Wrap large files (>100 MB) in a .zip to save bandwidth..zip.7z.tar.tar.gzContainer for PATH3 / CSV bundles. The format badge reflects what's inside.Multi-file uploads
.zip / .7z / .tar.gz and upload that single file - easier for shows with hundreds of drones..path3 and .csv in the same batch is rejected up front.Limits
If a show fails to process
A failed animation gets a red failed badge with a short error message. Common causes: a non-standard MAT field layout, a malformed PATH3 file, a Skybrush CSV with an unexpected header, or a USD scene with no drone geometry. Click Try again to retry - many transient failures clear on a second attempt without re-uploading.
Preparing a Blender (.blend) scene
Drones are detected automatically - any mesh with a roughly-cube bounding box (i.e. sphere-shaped) and fewer than ~1000 vertices is treated as a drone. No special naming required. Larger meshes in the scene (environment, backdrop, hero models) are ignored.
Colour is read with this priority:
- Object → Viewport Display → Color (animatable, simplest to set up)
- Material → Emission shader Color input (most common for self-lit LED look)
- Material → Principled BSDF Base Color
- Vertex colour (averaged across the mesh)
- White fallback if none of the above is set
.zip before uploading - Blender files compress well (often 50 % smaller). The zip is what gets stored; the unpacked .blend lives only during conversion..csv) and upload the bundle as a .zip. The CSV reader skips the bake step entirely and finishes in seconds even on large shows.Coordinate convention
Blender uses Z-up / +Y-forward; our renderer uses Y-up with -Z-forward. The bake automatically converts:
our X=blend Xour Y=blend Z(Blender's up becomes our up)our Z=-blend Y(Blender's forward becomes our -forward)
No project setting needs flipping - chunks land in our coord space directly.
Audio & sync offset
Uploading audio
- Open the show card.
- Click Add audio and pick a file.
- The track auto-attaches; play to confirm.
Supported: .mp3, .wav, .ogg, .oga, .m4a, .aac, .flac. Max 256 MiB - comfortably more than a 5-minute stereo show needs.
Sync offset
After uploading audio you'll see an offset field next to the audio filename. It shifts the music relative to the show - useful when the upload starts a beat too early or too late.
If the audio is silent
Cameras
droneshow.store ships built-in preset cameras (top-down, three-quarter, eye-level) plus two ways to add your own.
.json file matching the shape below. Field of view is derived from focal + sensor_width + aspect ratio, so you don't need to provide it explicitly.Camera JSON format
Minimal valid file - all fields except name are required.
{
"name": "Hero camera",
"resolution": { "x": 1920, "y": 1080 },
"camera_position": { "tx": 0.0, "ty": 12.0, "tz": 35.0 },
"camera_rotation": { "rx": -15.0, "ry": 0.0, "rz": 0.0 },
"focal": 50.0,
"sensor_width": 41.4214
}namestringoptionalLabel shown in the camera switcher. Falls back to the filename when omitted.resolution{ x, y }requiredOutput frame size in pixels. Used to derive aspect ratio.camera_position{ tx, ty, tz }requiredPosition in source coordinates. Same space your show data is authored in.camera_rotation{ rx, ry, rz }requiredEuler rotation in degrees, applied in XYZ order.focalnumberrequiredFocal length in millimetres.sensor_widthnumberrequiredCamera sensor width in millimetres. With focal + aspect this fully defines the field of view.Account & data
Keyboard shortcuts
Inside the 3D viewer:
Troubleshooting
The setup email never arrived
- Give it a minute or two - delivery isn't instant.
- Check your spam folder.
- Try Forgot password to issue a fresh link.
- If nothing arrives after a few minutes, email contact@droneshow.store and we'll resend manually.
Upload says the file is too large
Your file is larger than the per-upload cap (8 GiB). Either split the show into smaller archives or write to support to request a larger cap on your account.
The show plays but I can't hear anything
- Click anywhere on the page - browsers block autoplay until you interact.
- Confirm an audio file is attached: open the animation card and check the audio row.
- If the timing feels off, see the sync offset section.
My PATH3 archive failed to convert
- Open the archive locally - it should contain only per-drone
.path3files (no.DS_Storedroppings, no other archives nested inside). - Re-export from your show software with a consistent filename pattern.
- Click Try again on the failed card - transient failures often clear without needing a re-upload.
The share link doesn't open
If the link came through chat with a trailing punctuation mark, strip it - that can break the URL. If the project was deleted, the link is dead. If you renamed the project after sharing, the original link still works; you can grab a fresh one from the project hub.
Privacy & file retention
We don't keep your original show files. The moment your upload is converted into a streamable playback, the source is removed from the server.
.blend, .usd, .mat, .path3 or .csv - we read it, bake the show into a compact playback file, and delete the original. Your rigging, materials, drivers, and any non-show data in those files don't sit on our disks.What we keep
- Playback data - quantised positions and colours per frame. This is what the viewer needs to render the show in a browser; it's a tiny fraction of the original file size.
- Audio track (if you attached one) - served back to viewers as-is so the show plays in sync.
- Analytics report - duration, drone count, max speeds and altitudes, the printable PDF. Computed once at upload from the source, then kept alongside the playback data.
- Share preview image - the social-card thumbnail. You can refresh it at any time from the player.
- Project metadata - name, customer, cameras you've imported, your saved views.
What we delete
- Your original upload -
.blend,.usd,.mat,.path3archive, whatever format you sent. Removed automatically after processing finishes. - Anything bundled INSIDE the upload that wasn't part of the show timeline - your rigs, materials, drivers, constraints, scene comments, layer structure.
What it means in practice
- Re-running analytics on the server requires the original file. If you need fresh metrics later, just re-upload the show into the same project - the old animation can stay or be removed as you prefer.
- You can delete a project (and everything inside it) from the project hub at any time. That removes the playback data, audio, analytics, and share link irreversibly.
Still stuck?
Email us - include what you were trying to do, the project or animation ID from the URL (e.g. /workspace/projects/01KRS…), and a screenshot if possible.