Module export 

Writing a design back out as an OpenRocket .ork file.

Guide: OpenRocket .ork design files says what is written and what is not.

The file is written from the Design alone: its rocket, its motors, when its recovery opens and its stages separate, and the simulations OpenRocket last ran, each written as the tags super::design reads them from. Everything the design keeps but hpr does not model (its super::Extensions, such as a pod set, a part’s color or a simulation’s extension) is put back where it was. So a .ork read and written again reads back as the same design, which is how cargo xtask ork checks this on every file in the reference library (ADR-109).

What is written is schema 1.10, the version OpenRocket 24.12 writes, in a zip archive with the design as rocket.ork, as OpenRocket packs one.

Constants

DESIGN_ENTRY

The archive entry the design is written to, where OpenRocket looks for it first.

SCHEMA

The schema version written: OpenRocket 24.12’s.

Functions

creator

The creator written on the document: the program’s name, version and designation in the FusionSpace product system, as hpr_core::tool::stamp writes them (hpr-sim 0.1.0 · FS · SW · TOOL 005). OpenRocket keeps the attribute as text and does not parse it.

document

The design document for design, with a warning for anything kept from the file it came from that has no place in it any more.

write

A .ork file for design: a zip archive holding its document as rocket.ork, and then attachments, such as the thrust curves and preview image of the file it was read from (super::OrkFile::attachments). An attachment called rocket.ork is left out, with a warning: the design is that entry.