RockSim .rse motor files
See how HPR Sim reads and writes RockSim .rse motor files, the XML thrust curves ThrustCurve.org
serves, following real files where the spec disagrees.
A .rse file is a motor database in XML, a text format of nested, named elements, from the RockSim
flight simulator. It holds one or more motors (“engines”). Each has its size, masses and delays
as attributes, and a table of thrust, mass and center of gravity
(CG) over time. ThrustCurve.org serves it beside
RASP .eng.
To fly a motor from a .rse file, see
A motor from a file on the Solid motors page. It reads a
.eng file, and says what changes for a .rse one.
This page is the reference for HPR Sim’s reader and writer. The spec is thin and disagrees with every real file on element and attribute names, so a reader must follow the observed structure. Of the 823 RockSim files ThrustCurve.org held on September 17, 2026: 821 read and write back with every value unchanged. The other two have a time that goes backwards (Checked against real files).
Code: hpr_motor::rse (API reference), written for the
solid-motor milestone (M1.3). The rules below are from the spec unless marked
Observed (seen in real files) or Policy (the simulator’s own choice).
Sources
- [P] “RockSim & EngEdit – Engine File (.rse) Format Guide”, 3 pp., PDF hosted by ThrustCurve.org.
Pinned as
rocksim-rse-spec(sha256c47a04f4…) in the reference lock file. The lock file records each source’s address and checksum. The PDF was fetched torefs/papers/rocksim-rse-spec.pdf, a local folder that is never committed. Cited as [P p.N]. - [S] ThrustCurve.org, “Flight Simulators”, RockSim section,
https://www.thrustcurve.org/info/simulators.html, captured September 17, 2026 and pinned as
thrustcurve-simulators(sha2565bb2bad7…). - [X] W3C, XML 1.0 5th ed., https://www.w3.org/TR/xml/, §2.11 (end of line), §3.3.3 (attributes).
- Observed: 715 engines and 15,149 points in the ThrustCurve manufacturer file sets (9
.rsesets) and 10 single-motor API downloads. They were fetched September 17, 2026 into a local cache,refs/samples/formats/, that is never committed.
What a file holds
The file’s structure, its attributes and its thrust curve, as the spec gives them and as real files write them.
Structure
Spec: the minimal example is a bare <engine …> holding <data> with <point t="…" f="…"/>
children [P p.2]. Observed in 715 of 715 engines:
<engine-database>
<engine-list>
<engine ATTRIBUTES> repeated; one list holds every engine in the file
<comments>free text</comments> optional (415 of 715), before <data>
<data>
<eng-data t="…" f="…" m="…" cg="…"/> one per sample, in file order
</data>
</engine>
</engine-list>
</engine-database> no XML declaration, DTD or namespace
<engine> attributes
“Req” is the spec’s Required column [P p.1]. Units are from [P p.1, p.3] unless noted.
| Attribute | Req | Unit | Meaning |
|---|---|---|---|
mfg | yes | n/a | Manufacturer name |
code | yes | n/a | “Unique engine identifier”, the “primary lookup key” |
Type | yes | n/a | Engine type [P p.1 spells it type; files always use Type]. Seen: reloadable, single-use, hybrid [S], unspecified, Single-Use |
dia | yes | mm | Diameter |
len | yes | mm | Length |
initWt | yes | g (spec: “kg or g”) | Initial (loaded) motor mass |
propWt | yes | g (spec: “kg or g”) | Propellant mass |
delays | yes | s | “Comma-separated delay values” |
Itot | yes | N·s | Total impulse |
avgThrust | yes | N | Average thrust |
peakThrust | yes | N | Peak thrust |
burn-time | yes | s | Burn duration |
auto-calc-mass | no | flag | 1: RockSim computes mass as , with [P p.2] |
auto-calc-cg | no | flag | 1: “CG is fixed at engine center” [P p.2] |
massFrac | n/a | % | Not in spec. Observed: (703 of 710), where is the first point’s m |
Isp | n/a | s | Specific impulse. Not in spec. Observed: , in kg, within ±0.006 in 696 of 710 |
throatDia, exitDia | n/a | mm? | Nozzle throat and exit diameters. Not in spec. Always 0. |
tDiv tStep tFix FDiv FStep FFix mDiv mStep mFix cgDiv cgStep cgFix | no | n/a | “Rendering attributes … control how graphs are drawn” [P p.2]. Always Div 10, Step -1., Fix 1 |
The spec contradicts itself: its summary names initMass and propMass [P p.2], while its
table and example use initWt and propWt [P p.1–2]. Only initWt/propWt occur in real files.
Mass unit (verified). Of 557 .rse engines whose code also appears in the .eng sets,
497 have initWt within 1% of 1,000 × the .eng total mass. None match the kg value; the other 60
are different data (another diameter or mass). massFrac and Isp are consistent with grams.
The smallest initWt is a 1.2 g micro motor.
<eng-data> point attributes
| Attr | Req | Unit | Meaning |
|---|---|---|---|
t | yes | s | Time since ignition [P p.1] |
f | yes | N | Thrust [P p.1] |
m | no | g | “Mass … over time”, needed if auto-calc is off [P p.1]. Observed: propellant mass remaining. = propWt in 696 of 715; last m = 0 in 715 of 715. In 698 of the 700 set engines with , , with the trapezoidal impulse, to 1e-3 relative (median 1.3e-6). That is not the spec’s linear auto-calc formula. |
cg | no | mm | Motor CG over time [P p.1], [S]. Observed: constant = len/2 in 685 of 715. The datum (forward or aft end) is stated nowhere: unverified. |
With every observed file setting both auto-calc flags to 1, RockSim may ignore m and cg
[P p.2]. Policy: the simulator preserves them for round trips but derives mass and CG itself.
Thrust curve
- The spec example lists an explicit
t="0.0" f="0.0"first point and ends withf="0.0"atburn-time[P p.2]. Unlike.eng, the origin is written out. The spec is silent on ordering, duplicates and a nonzero last point. - Observed: the first point is (0, 0) in 715 of 715. The last
fis 0 in 713; 2 put a nonzero point after the zero at the samet. 70 engines have equal consecutivet, and 1 hastdecreasing.burn-timediffers from the lasttin 281 (rounded).Itotmatches the trapezoidal integral within 0.1% in 712, andavgThrust=Itot/(lastt) within 0.1% in 712.peakThrust≠ maxfin 9.
Reading and writing
What else real files do, and what the reader and writer do with each case.
Observed in real files (other)
- Delays: missing in 5. Always comma integers; never
P. Descending lists are common (15,12,10,8,6). Checked against ThrustCurve search metadata,1000means plugged in 126 of 128 single-token cases and0in 24 of 25. Lists can end in1000(10,14,1000). - Strings:
mfghas 20+ spellings, including leading or trailing spaces (Aerotech), commas (Estes Industries, Inc.) and underscores.codecan hold spaces (Micro Maxx II), commas and parentheses. - Numbers: 6 significant digits, like C
%g, with a trailing.on integral values (35.,0.,-0.). One exponent (1.51982e-05); some padded (0.00). - XML text: start tags wrap over several lines; two spaces after the element name. Attribute
order is either RockSim’s (490) or alphabetical (220); XML gives order no meaning. 6 of 19 files
use CRLF, and many lack a final newline.
<comments>spans lines in 197 engines; 2 use CDATA, one holding a raw&. There are no entity references, and everything is ASCII. - Bad values:
propWt10× (a typo), andcg0.1 × len/2. Five engines (four hybrids) have everymandcg= 0, so cannot mean “no propellant”.
Reader policy (lenient, with diagnostics)
- Use a conforming XML parser (
roxmltree): it handles CDATA (raw-text sections), entities (escapes such as&) and end-of-line normalization [X §2.11]. Refuse DTDs and external entities, declarations that can make a parser fetch other files (core crates do no I/O). The reader takes text and strips a BOM. Decoding bytes is the caller’s job, as for.engfiles: planned forhpr-io, which doesn’t do it yet. - Take every
engineelement at any depth, so a bare<engine>root [P p.2] also works, but not one nested inside another engine. An engine with an error is skipped, with the error as a warning, when others in the file read. With repeated<data>or<comments>, the last is read, with a warning.<comments>keeps only text: XML comments and processing instructions inside are not part of it, and nested markup contributes its text. Every warning carries a kind: skipped (an engine left out), dropped (a value left out) or unusual (read as it stands). Points areeng-datachildren ofdata; also acceptpoint[P p.2]. - Match attribute names exactly, then ASCII case-insensitively (
Type/type); acceptinitMass/propMassas aliases [P p.2]. Ignore the rendering attributes silently; warn on and ignore other unknown attributes and elements. - Required:
code,dia,len,initWt,propWt, and at least 2 points withtandf. A missingmfgreads as empty, with a warning. Everything else isOption; a missingdelaysmeans no delay information. If only some points carrym(orcg), treat it as absent for all of them, and warn.auto-calc-*flags read1or0; anything else is left out with a warning. - Numbers: trim XML whitespace, then parse with Rust’s f64 parser. Reject non-finite values:
Rust accepts
inf,infinityandNaN. Warn ifpropWt≥initWt. Keep file units (g, mm) in the file model, in fields named for them (initial_mass_g). Convert to SI only when building the physical motor. The round trip g → kg → g is not bit-exact (4030.comes back as4030.0000000000005). 14 of 1,330 distinct mass and length values in the sets fail. - Keep strings verbatim, including the spaces in
mfg; normalize names in the catalog layer. Delays: keep the raw string; interpret it as in.engfiles (1000/100→ plugged,0ambiguous). - Point checks match
.eng. Error on negative or decreasingt, and on a lastfabove half the curve’s peak, where the file looks cut off. When other engines in the file read, that engine is skipped, with a warning. Warn on a lower lastf≠ 0, on negative thrust, and on anItotorpeakThrustthat disagrees with the curve by more than 1%.burn-timeis not checked: files round it from the last time.
Writer policy (strict, round-trip stable)
Round-trip stable: a file the simulator writes reads back to exactly the values it was written from.
-
Emit
<engine-database>,<engine-list>and one<engine>per motor. Use 2-space indent, LF endings, a final newline, UTF-8, and no XML declaration (none was observed; whether RockSim accepts one is unverified). -
Policy: the first line is an XML comment naming the program that wrote the file, its version and its designation in the FusionSpace product system. Every file the simulator writes has this line:
<!-- FusionSpace HPR 0.1.0 · FS-ACHERNAR · SW · TOOL 001 -->. XML readers skip comments, the simulator’s too, so the file reads back to the same values and writing it again gives the same bytes. Whether RockSim and OpenRocket accept a comment before<engine-database>has not been checked. -
Write attributes in RockSim’s order:
mfg code Type dia len initWt propWt delays auto-calc-mass auto-calc-cg avgThrust peakThrust throatDia exitDia Itot burn-time massFrac Isp tDiv tStep tFix FDiv FStep FFix mDiv mStep mFix cgDiv cgStep cgFix. Write only the ones present in the model. Points are written ast f m cg, verbatim, with no origin added or removed. An engine with fewer than two points, or whose lastfis above half its peak, is refused, as the reader would refuse the curve. -
Numbers use Rust
{}(Display): the shortest digits that round-trip exactly, no exponent, and-0for negative zero. -
Escape attribute values as
& < > ", and tab, LF and CR as	 . A literal one would read back as a space [X §3.3.3]. Escape<comments>text as& < >with CR as , without CDATA, and write it verbatim (no trimming). -
Flags are written
1or0. The rendering attributes are not kept, so they are not written. -
Apart from that comment, the writer adds nothing by itself. Converting from
.engis a separate step,hpr_motor::convertorhpr convert(since M4.2c, the command-line conversion). It fills what.englacks the way the observed files do. The counts are out of the files that give each attribute. Of 715 engines, 710 givemassFracandIsp, and 700 have a propellant mass above zero form’s shape:attribute filled as observed in a (0, 0)first pointadded when the curve’s first point is after ignition 715 of 715 Itotthe trapezoidal integral of the curve within 0.1% in 712 peakThrustthe largest fall but 9 burn-timethe last tthe last t, or in 281 of 715 a rounding of itavgThrustItot/burn-timewithin 0.1% in 712 m, = propWt= propWtin 696 of 715; the shape in 698 of 700cglen/2685 of 715 auto-calc-mass,auto-calc-cg1every file massFrac703 of 710 Isp, in kg 696 of 710 Typeunspecified, as the guide requires one [P p.1]one of the values seen Delays trade
-for,andPfor1000. Masses move from kg to g by moving the decimal point in their shortest digits, not by multiplying. Converting to.engdrops the attributes above, plusthroatDiaandexitDia, each named in a warning. It refuses a hybrid, and a motor with no delays the simulator can read until--delaysgives them. OpenRocket 24.12 opens every file converted from the 32 curves first bundled (motor_files.py); whether RockSim does is unverified. -
Invariant (test it): whenever
write(parse(x))succeeds,parse(write(parse(x))) == parse(x), with f64 compared by bits and strings compared exactly.
Checked against real files
On September 17, 2026, 821 of the 823 RockSim files in ThrustCurve.org’s solid-motor survey read, and
write-parse-write reproduces every value bit for bit. The other two have a time that goes
backwards and are rejected with its line. In the manufacturer sets, 704 engines read; one engine
with a backwards time is skipped with a warning. The files are cached under refs/samples/ and
never committed.