Overview

The Skybrush Suite has several proprietary drone show file formats, each optimized for the different stages of the complete process from design to execution of drone shows.

Below is the brief desctiption of all used formats organized according to the phases of the drone show process, while detailed format specifications can be found at the sidebar for the main file formats.

Formats for drone show design and verification

Drone show design is supported in two strategic ways to accomodate to the different habits of different designers:

  1. We provide exporter plugins for several animation software for those who would like to use their own design framework

  2. We provide Skybrush Studio as a standalone solution for drone show design

The file formats used by each option are described below.

Drone show animation snipped format (.csv)

We provide python plugins/add-ons for all major animation software (3DSMax, Blender, Cinema4D, Houdini, Maya) to export static or animated formations into a very simple linear baked drone trajectory and light show format stored in regular .csv files, one for each drone, all zipped together, with the following line format (colors are optional): Time_msec, x_m, y_m, z_m, Red, Green, Blue.

You can use our online converter to convert an entire .csv show into Skybrush Compiled Format (.skyc).

Alternatively, you can use Skybrush Studio for Blender to import animated formations into the storyboard modularly.

Drone show design plugin formats (.json)

We provide an API for Skybrush Studio Server to use the following core functionalities in any major animation software (3DSMax, Blender, Cinema4D, Houdini, Maya), if embedded in custom designer-specific extentions:

  • automated takeoff, smart return to home and landing procedures

  • automated and optimized morphing between different scenes

  • verification of drone show content

  • export of drone shows to Skybrush-compatible formats

  • etc.

For all these functionalities we use the Skybrush Studio backend with inputs in a simple .json format that is well known, easy to produce in all script languages, human-readable and can be compressed easily.

The documentation of the input and output formats of these services is described at https://studio.skybrush.io/api/v1/docs, while the corresponding code source can be found in the skybrush-studio-backend repo.

As part of the Skybrush Studio API definitions, namely, in the input/data section of render and multi-render operations one can find an entire JSON-based drone show format specification, parsed by the json importer of the skybrush-studio repo. This is actually our most general drone show format. The Skybrush Compiled Format (.skyc) (after being decompressed into a .json file) is also a subset of this format and uses the same json importer. Read more below:

Skybrush Studio format (.sky)

Skybrush Studio is a standalone drone show designer framework. The output of Skybrush Studio is a plain-text, Python-like show description file (.sky) that can be rendered into other Skybrush formats or into actual visualizations for animation softwares.

Skybrush Studio and the documentation of the '.sky' API is currently not public. If you wish to cooperate with using this design framework, please contact us.

Formats for drone show visualization and execution

Skybrush Compiled Format (.skyc)

The Skybrush Compiled Format (.skyc) is a single-file drone show descriptor of entire drone shows for aiding the whole process of drone shows through show design, visualization, verification, sharing and execution.

  • The .skyc format is the output of all animation software export plugins

  • The .skyc format can be used in Skybrush Viewer to pre-visualize drone shows

  • The .skyc format can be used in Skybrush Live to execute drone shows

Formats for individual drone mission control

Skybrush Binary Format (.skyb)

The Skybrush Binary Format (.skyb) is a heavily compressed and optimized binary drone mission format that is uploaded to drones individually by Skybrush Live, after the proper mapping between the show trajectories and the individual drones is determined. It contains the mission trajectory to be followed and a light show to be executed by the given drone. It might also contain geofencing information on specific hardwares.