Skip to main content

Module value

Module value 

Source
Expand description

Reading the values a .ork writes inside its elements.

Every later step walks the document tree and asks it for numbers, counts, flags and dimensions. Three things make that less simple than it sounds, and all three are mistakes Loft made:

  • A dimension may be automatic. <outerradius>auto 0.0125</outerradius> means “OpenRocket works this out from the neighbours, and 0.0125 m is what it last worked out”. Keeping only the number turns an automatic dimension into a hand-typed one the next time the design is saved (Loft lesson L58). Dimension keeps both.
  • A tag may have two names. OpenRocket renamed several, and writes both for older readers. The reader takes the first name it finds, newest first (Loft lesson L62).
  • A stated zero is a value. <overridecd>0.0</overridecd> means no drag at all, not “no override”. Loft read it as missing and charged the part full drag (Loft lesson L63).

Structs§

Overrides
What a component says its own mass, center of gravity and drag coefficient are, instead of what its geometry and material would give.
Values
Reads a .ork element’s child values, collecting a warning for anything it cannot.

Enums§

Dimension
A number a .ork writes, which OpenRocket may be working out for itself.

Constants§

AXIAL_OFFSET
The two names OpenRocket writes a component’s distance along its parent under.
INSTANCE_COUNT
The two names for how many of an instanced component there are (fins, rail buttons, pods).