fabi/Syplheed-Reborn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re(route-b): full field map verified 154/154, and 101 defaulted fields read out

Browse Source 
Anchoring each key string to the first store AFTER the accessor call makes the
extraction exact: 159 fields, 125 of them floats, and verify_fieldmap now checks
every one against the live objects -- 154 agree with the disc, 0 disagree.

The last ten mismatches taught the rule: angle fields are degrees on disc and
RADIANS at runtime (AV_PitchPlus_Max 3.6 -> 0.0628319; MaximumBank_Normal 60 ->
1.0472), an exact conversion across every angle field and unit.

101 defaulted fields now have runtime values: angle limits default to 3.6 degrees,
afterburner/turn-attack fields to 0, FiringRange to 0 (matching the loader's miss
value), Size_Y to that unit's Size_X, and the ratio family is per-unit rather than
constant (HQRatio 0.2 or 1, DefencePoint 0.1 or 0.25, ...).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude (auto-RE)
2026-08-12 23:44:57 +00:00
parent 0434afa6a6
commit d674cddad4
3 changed files with 155 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

39
docs/re/live-unit-definitions.md
View File

@@ -387,3 +387,42 @@ matches the loader's own miss value.
off-by-one column in the dump reader — `f[3]` is the u32, `f[4]` the float — and
decoding one by hand (`1128792000` = `0x43480000` = 200.0) showed the map had been
right all along.
## ✅ The whole map verified — 154/154 — and 101 defaulted fields read out
Anchoring the key string to the **first store after the accessor call** (rather
than to the nearest store) makes the extraction exact: **159 fields**, of which
**125 are floats**. `verify_fieldmap.rs` now checks every one of them against the
live objects: **154 field values agree with the disc record, 0 disagree** across
five capital ships.
Getting there needed one rule, and the ten last "mismatches" are what taught it:
```
AV_PitchPlus_Max disc 3.6 live +176 = 0.0628319 ( = 3.6° in radians)
MaximumBank_Normal disc 60 live +256 = 1.0472 ( = 60° in radians)
```
**Angle fields are degrees on disc and radians at runtime** — the incidental
observation from the previous pass, now confirmed as an exact conversion across
every angle field and every unit.
With the map verified, the dump answers the brief's question for **101 fields**
that these records leave defaulted
([`captures/stage02-defaulted-field-runtime-values.txt`](captures/stage02-defaulted-field-runtime-values.txt)).
The shape of the answer:
- **Angle limits default to 3.6°** (`0.0628319` rad) — every `AA_*`/`AV_*`
`Pitch/Roll/Yaw` `Min`/`Max`, identical across all five units.
- **Afterburner and turn-attack fields default to 0** (`AB_*`, `TurnAttack_*`,
`AA_AxisMode_*`, `AV_AxisMode_*`).
- **`FiringRange` defaults to 0**, matching the loader's own miss value exactly.
- **The ratio family is per-unit, not constant**: `HQRatio` 0.2 or 1,
`ThrusterRatio` 0.2 or 1, `AttackCraftPoint` 0.1 or 0.5, `DefencePoint` 0.1 or
0.25, `DelayAdjustment` 0 or 2 — so these are *runtime values for units that do
not set the field*, not a single global default.
- **`Size_Y` takes that unit's own `Size_X`** (200/300/400/600/700).
That is the `…Ratio` / `…Count` family the mission brief named, answered from the
running game, with the field identities read out of the title's own code rather
than guessed.