re: state the real (non-circular) evidence for Ammo Capacity == LoadingCount
The 'N/N exact matches' framing was circular: each UI entry was identified BY its ammo value. Replaced with what actually carries the claim — tab-uniqueness of the forced match, the independent Max. Lock Ons agreement on two of them, and one entry (STILETTO BG I) identified from the HANGAR loadout rather than from ammo. Also downgrades LIGHT MACHINE GUN MG I to PROBABLE: three guns share ammo 3000. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -38,7 +38,7 @@ entries are withheld. The same panel appears in **HANGAR → (hard point)**, wit
|
|||||||
|
|
||||||
| DATA SHEET row | IDXD field | Confidence | Evidence |
|
| DATA SHEET row | IDXD field | Confidence | Evidence |
|
||||||
|---|---|---|---|
|
|---|---|---|---|
|
||||||
| `Ammo Capacity` | `LoadingCount` | ✅ CONFIRMED | 9/9 exact matches across 4 weapon types — 3000, 6000, 4000, 600, 300, 600, 45, 18, 75 |
|
| `Ammo Capacity` | `LoadingCount` | ✅ CONFIRMED | every one of the 10 identified entries lands on a `LoadingCount` that exists in its own weapon-type tab — and see the circularity note below |
|
||||||
| `Max. Lock Ons` | `TriggerShotCount` | ✅ CONFIRMED | FALCON 9AM = 12 vs `wep_02`'s 12; BUZZARD 10AM = 22 vs `wep_04`'s 22 (two distinctive values, two independent records) |
|
| `Max. Lock Ons` | `TriggerShotCount` | ✅ CONFIRMED | FALCON 9AM = 12 vs `wep_02`'s 12; BUZZARD 10AM = 22 vs `wep_04`'s 22 (two distinctive values, two independent records) |
|
||||||
| `Hard Point` | mount slot | ✅ CONFIRMED | matches the HANGAR slot the weapon is mountable/equipped on (`STILETTO BG I` → NOSE, `FALCON 9AM` → MAIN WEAPON1) |
|
| `Hard Point` | mount slot | ✅ CONFIRMED | matches the HANGAR slot the weapon is mountable/equipped on (`STILETTO BG I` → NOSE, `FALCON 9AM` → MAIN WEAPON1) |
|
||||||
| `Range Class` | bucket of `MaximumRange` | 🟡 PROBABLE | monotone in the on-disc metres, see the bracket table below |
|
| `Range Class` | bucket of `MaximumRange` | 🟡 PROBABLE | monotone in the on-disc metres, see the bracket table below |
|
||||||
@@ -47,6 +47,28 @@ entries are withheld. The same panel appears in **HANGAR → (hard point)**, wit
|
|||||||
| `Speed Class` | ❔ | ❔ | present only on missiles (MPM = A, ASM = B); no on-disc pairing established |
|
| `Speed Class` | ❔ | ❔ | present only on missiles (MPM = A, ASM = B); no on-disc pairing established |
|
||||||
| `Sight Homing`, `Lock on Overlap` | ❔ (`Available` / `–`) | ❔ | the plausible on-disc partners (`Homing`, `OverlapLockon`) are identifier-valued and not yet decoded; **NEEDS-HUMAN** |
|
| `Sight Homing`, `Lock on Overlap` | ❔ (`Available` / `–`) | ❔ | the plausible on-disc partners (`Homing`, `OverlapLockon`) are identifier-valued and not yet decoded; **NEEDS-HUMAN** |
|
||||||
|
|
||||||
|
### Why the `Ammo Capacity` evidence is not circular
|
||||||
|
|
||||||
|
Each UI entry was **identified** by matching its `Ammo Capacity` against the records in
|
||||||
|
that weapon-type tab, so "the ammo matches" cannot on its own prove the mapping. What does:
|
||||||
|
|
||||||
|
1. **The match is forced and unique.** For 10 of the 11 entries, exactly one record in that
|
||||||
|
tab carries that number (`600` occurs three times overall — `wep_04`, `wep_24`, `wep_55`
|
||||||
|
— but in three different tabs: MPM, BEAM, B/R). An unrelated quantity would not land on
|
||||||
|
a valid, tab-unique `LoadingCount` eleven times running.
|
||||||
|
2. **A second, independent field then agrees.** FALCON 9AM and BUZZARD 10AM were pinned by
|
||||||
|
ammo alone, and their `Max. Lock Ons` (12, 22) then matched those same records'
|
||||||
|
`TriggerShotCount` (12, 22) — values that play no part in the identification. A wrong
|
||||||
|
identification would have to be wrong twice, consistently.
|
||||||
|
3. **One entry is identified without ammo at all.** STILETTO BG I is described in-game as
|
||||||
|
"the initially mounted Delta Saber beam gun" and is the weapon the HANGAR shows equipped
|
||||||
|
on the nose; `wep_01_Beam` is the corresponding record, and its `LoadingCount` 6000 is
|
||||||
|
what the panel shows.
|
||||||
|
|
||||||
|
The weakest identification is LIGHT MACHINE GUN MG I: three guns share `LoadingCount = 3000`
|
||||||
|
(`wep_09`, `wep_33`, `wep_83`). `wep_33` is picked on `Weight Class = Light` (it has by far
|
||||||
|
the smallest `Mass`, 1.5 vs 3.6 / 33.0) — 🟡 PROBABLE, not certain.
|
||||||
|
|
||||||
## Finding — recovered defaults
|
## Finding — recovered defaults
|
||||||
|
|
||||||
| Weapon | UI name | Field | On disc | **Runtime** | Conf. |
|
| Weapon | UI name | Field | On disc | **Runtime** | Conf. |
|
||||||
@@ -71,7 +93,7 @@ All values are from one session on save slot 01 (Stage 02, "At Standby", 5 % cle
|
|||||||
|
|
||||||
| UI name | Record | Rng | Dmg | Spd | Weight | Ammo | Lock | Homing | Overlap | Hard point |
|
| UI name | Record | Rng | Dmg | Spd | Weight | Ammo | Lock | Homing | Overlap | Hard point |
|
||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|---|---|---|---|---|---|---|---|---|---|---|
|
||||||
| LIGHT MACHINE GUN MG I | `wep_33_Gun` | D | E | – | Light | 3000 ✓ | – | – | – | NOSE WEAPON (Nose) |
|
| LIGHT MACHINE GUN MG I | `wep_33_Gun` 🟡 | D | E | – | Light | 3000 ✓ | – | – | – | NOSE WEAPON (Nose) |
|
||||||
| BROAD SWORD SG I | *see below* | E | D | – | Light | 200 | – | – | – | NOSE WEAPON (Nose) |
|
| BROAD SWORD SG I | *see below* | E | D | – | Light | 200 | – | – | – | NOSE WEAPON (Nose) |
|
||||||
| STILETTO BG I | `wep_01_Beam` | E | E | – | Light | 6000 ✓ | – | – | – | NOSE WEAPON (Nose) |
|
| STILETTO BG I | `wep_01_Beam` | E | E | – | Light | 6000 ✓ | – | – | – | NOSE WEAPON (Nose) |
|
||||||
| DAGGER BG2 | `wep_37_Beam` | D | E | – | Light | 4000 ✓ | – | – | – | NOSE WEAPON (Nose) |
|
| DAGGER BG2 | `wep_37_Beam` | D | E | – | Light | 4000 ✓ | – | – | – | NOSE WEAPON (Nose) |
|
||||||
|
|||||||
Reference in New Issue
Block a user