Workspace

How to use droneshow.store

Upload a show, tune the music, share it with your team. This is the short version - pick a topic below or scroll through the steps. The full manual, with screenshots and the Show Builder, is in the Docs.

contact@droneshow.storeWe answer within 1 business day

Quick start

Three steps from a fresh login to a sharable show.

1
Sign in
Create an account or use an existing one. New here? Sign up.
2
Upload a show
Open a project and drop in a .usd, .path3, .mat or .csv file - or a .zip of any of them.
3
Share the link
Click Copy share link and paste it into chat or email. No account needed to view.

Topics

Uploading shows

Drag any supported file (or archive) onto the upload area inside a project. The status badge walks through queued → converting → ready; you can keep working in another tab while it processes.

Supported formats

The format badge on each show follows the file content, not the extension - a .zip of .path3 files reads as PATH3.

USD.usd.usda.usdc.usdzPixar USD scenes. One file per show. Cameras embedded in the scene can be imported separately.
PATH3.path3One file per drone - multi-select them all at once, or pack into a .zip / .7z / .tar.gz.
MAT.matMATLAB matrix file. Fields must follow our exporter convention - email support a sample before uploading several GB.
CSV.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.
DAMODA.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.
BLEND.blendBlender scenes. Drones are detected automatically as sphere-shaped meshes. Wrap large files (>100 MB) in a .zip to save bandwidth.
archive.zip.7z.tar.tar.gzContainer for PATH3 / CSV bundles. The format badge reflects what's inside.

Multi-file uploads

Multi-select. Pick every per-drone file at once in the file picker. Works great up to a few dozen drones.
Archive. Pack the files into .zip / .7z / .tar.gz and upload that single file - easier for shows with hundreds of drones.
All files in one upload must share the same per-drone extension. Mixing .path3 and .csv in the same batch is rejected up front.

Limits

Per-upload cap
8 GiB
Per-account caps
storage · projects · shows
Need more?

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:

  1. Object → Viewport Display → Color (animatable, simplest to set up)
  2. Material → Emission shader Color input (most common for self-lit LED look)
  3. Material → Principled BSDF Base Color
  4. Vertex colour (averaged across the mesh)
  5. White fallback if none of the above is set
Resampling. Your scene's authored frame rate is respected - the bake interpolates to our standard playback rate. Drivers, constraints, geometry nodes and modifiers are all evaluated, so even complex setups convert correctly (just slower).
Big scenes. Wrap large .blend files in a.zip before uploading - Blender files compress well (often 50 % smaller). The zip is what gets stored; the unpacked .blend lives only during conversion.
Long shows (>10 min or >1000 drones). Blender bakes at roughly 0.5–1 second per 5 seconds of show - fine for short clips, noticeable for full-length productions. For these, export your drones to per-drone CSV directly from Blender (Skybrush Studio plugin, or a small script that dumps each drone's f-curves to a.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 X
  • our 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

Each animation carries one audio track. After the first decode, return visits start instantly - no waiting on the spinner.

Uploading audio

  1. Open the show card.
  2. Click Add audio and pick a file.
  3. 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.

++2.5 s
Delay the music
Music starts 2.5 s after the show begins.
00 s
In sync
Music and show start together. Default.
--1.2 s
Start music early
When the show begins, music is already 1.2 s in.
Granularity is 10 ms; range is ±300 s. Changes preview live in the player as you type - handy for nailing a percussive hit on a specific drone flash. Saved on blur or Enter. Share visitors see whatever value you saved last.

If the audio is silent

On a fresh load, music starts muted - browsers block autoplay until you interact with the page. Look for the "Sound is off - tap to enable" pill in the bottom corner and click anywhere on the page to un-mute.

Cameras

droneshow.store ships built-in preset cameras (top-down, three-quarter, eye-level) plus two ways to add your own.

Import a camera from JSON
On the Cameras panel click Import camera and pick a .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.
Save current view
Frame the angle you want in the viewer (orbit / pan / dolly with the mouse, or pinch on touch). Click Save current view. The shot remembers your orbit pivot, so re-opening it preserves both the framing and the centre of rotation.

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.
Coordinate conventions. The camera looks down the source's negative Z axis with Y pointing up. That matches the default authoring orientation of most DCC tools, so a vanilla export usually loads correctly without re-axis-conversion. If the imported camera points in the wrong direction, double-check that your export used Y-up / -Z-forward.
Default camera per project. Open the gear icon in the viewer → Default camera. Whichever camera you pick is the one the viewer activates on first load - both for you and for visitors who open the share link.

Sharing & comments

Share link
Every project carries a public share link. Hit Copy share link on the project hub. Visitors don't need an account. Renaming the project keeps the original link working. A new project's page has the review tools on - analysis, measurements, drone numbers; Client preview under Share page on the hub leaves camera views, fullscreen and sound.
Hide a show
Each animation has an eye icon. Closed eye → admin-only: visible to you, invisible on the share link. Useful for work-in-progress takes. Open eye → public.
Comments
Once you turn them on (Share page on the hub), visitors can leave time-stamped notes. Click the timeline at the moment you want to anchor a comment to. You see them immediately in the admin view and can resolve or delete.
Revoke a link
Email contact@droneshow.store and we'll rotate the share link - the old URL stops resolving.

Account & data

Change your password
Log out, then use Forgot password on the login screen. We'll email a link that lets you set a new one.
Marketing emails
Off by default. If you opt in on the Account page, every email carries a one-click unsubscribe in the footer.
Delete your account
Email contact@droneshow.store from your registered address. We remove your account, every project, and every uploaded file within 30 days.

Keyboard shortcuts

Inside the 3D viewer:

Space
Play / pause
←→
Skip 1 second
⇧+←→
Skip 5 seconds
Home
Jump to start
End
Jump to end
Shortcuts are off while typing in a text field - Space won't pause playback while you're writing a comment.

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 .path3 files (no .DS_Store droppings, 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.

Short version. Upload a .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, .path3 archive, 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.
Why we tell you this. Studios put real IP into their show files - custom rigs, material libraries, choreography logic. The playback data we keep is what the audience would see if they were standing under your drones; everything about how the show was built leaves the server when the original does.

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.
Need a signed data-processing agreement, custom retention rules, or self-hosting? Email contact@droneshow.store and we'll sort it out.

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.

contact@droneshow.store