re: challenge LOD tables are _test + set dressing; orphan count corrected 8 -> 6

Diffed the field sets, the same move that cracked EnumWeapon_EX5.

The five bespoke challenge tables are EXACT SUPERSETS of _test - 10 of 10 (five
stages x the EnumLODSet and EnumGameModel families) with zero removals. Extras
run +2 to +9 and name the stage's own scenery: stg24_01..04, stg26_01..03,
stg27_01..02, stg29_01..02, plus rot_n001_break shared by S24, S26, S27, S28 and
Tutorial.

S28's nine extras independently confirm the player-craft result:
LOD_Frame_rou_f004, four rou_f004_mnv*/turn180 poses and three eff_j004_*
effects - the LOD table for the one stage that flies rou_f004. Two unrelated
tables agreeing on S28's oddity is a real cross-check.

This does NOT revive "rot_n001 is on the disc": that refutation concerned the
bare name, which still occurs 0 times exactly; only the _break form is real,
exactly as recorded.

Self-correction: 6 orphan tables, not 8. name_hash is case-INSENSITIVE, so _test
and _Test are the same pak entry - EnumLODSet hashes to 3485720498 and
EnumGameModel to 4020329537 for both spellings. The family therefore has 10
distinct keys, not 11 tags, and the unreferenced set is S01, S02, S16 x 2 = 6.

And the six are not stale copies of _test. They are far smaller (120, 129 and
178 EnumLODSet fields against _test's 676) yet each carries 4-5 entries _test
does NOT have: LOD_Effect_eff_e0033, _e0058, _e0059, _e0060, _n0071, and S16
adds five rou_e106_* boss parts matching stage16-boss. So the live table is not
a superset of the abandoned ones. Tutorial has the same shape: 66 fields, 3
unique.

All fifteen artefacts byte-identical.
This commit is contained in:
Sylpheed RE agent
2026-08-28 07:15:28 +00:00
parent 0536e287b5
commit d08e464897
2 changed files with 77 additions and 0 deletions

View File

@@ -6499,3 +6499,34 @@ sets, abandoned for the shared `test` table" is a reading, not a measurement.
116 of 130 referenced values are bare `Equip_EnumGameModel_wep_NN.tbl` names from
`PlayerLOD`/`WingmanLOD`/`PlayerMotion`/`WingmanMotion` (58 distinct each); only
the 14 stage-tagged values use the `+` form.
---
## ✅❌ 2026-08-28 — challenge LOD tables are `_test` + set dressing; orphan count corrected to 6
Item (a).
✅ **The five bespoke challenge tables are exact supersets of `_test`** — 10 of 10
(5 stages × 2 families) with **zero removals**; extras are +2 to +9 and name the
stage's own scenery (`stg24_01…04`, `stg26_01…03`, `stg27_01…02`, `stg29_01…02`)
plus `rot_n001_break`.
🔑 **S28's nine extras independently confirm the player-craft result**:
`LOD_Frame_rou_f004`, four `rou_f004_mnv*`/`turn180` poses and three `eff_j004_*`
effects — the LOD table for the one stage that flies `rou_f004`.
⚠️ This does **not** revive "`rot_n001` is on the disc": that refutation concerned
the **bare** name (still 0 exact); only the `_break` form occurs, as recorded.
❌ **Self-correction — 6 orphan tables, not 8.** `name_hash` is case-**insensitive**,
so `_test` and `_Test` are the *same pak entry*
(`EnumLODSet` → 3485720498, `EnumGameModel` → 4020329537 for both spellings). The
family has **10 distinct keys**, and the unreferenced set is **S01, S02, S16 × 2
= 6**.
🟡 **The six are not stale copies.** They are far smaller (120/129/178 vs 676
`EnumLODSet` fields) yet each holds **4–5 entries `_test` lacks** —
`LOD_Effect_eff_e0033/_e0058/_e0059/_e0060/_n0071`, and S16 adds five
`rou_e106_*` boss parts (cf. `stage16-boss`). The live table is **not** a
superset of the abandoned ones. `Tutorial` has the same shape: 66 fields, 3
unique.