re: correct a mislabelled blocker -- the world unit needs a run, not a waiver
I wrote "blocked on the oracle" for the unit-to-metre conversion. That was a mislabel: red is for what the container cannot do, and run-canary works here. What the km-name sweep actually established is narrower -- no STATIC test can settle it, because the disc has exactly one size-bearing asset name. The run is well-supported by tooling that already exists: findplayer.py recovers the player position triple from motion, the HUD prints the distance to the selected target in the game own units, and the same separation read both ways is the conversion. Recorded as amber with the experiment written out.
This commit is contained in:
@@ -456,10 +456,14 @@ search cannot find a *schedule*.
|
||||
**108/112** ship/mob stems are prefixed by one of the 480 resource ids, against
|
||||
a **0/112** shuffled-character control, and correctly **0/46** on asteroids. A
|
||||
`CollisionSet` entry is `<GameResourceID>[_<part>]_cmesh`.
|
||||
🔴 **The world unit is BLOCKED on the oracle.** Sweeping every pak for a
|
||||
km-bearing name returns `mapmesh_box_500km` and **nothing else** (162 refs, all
|
||||
that one pair) — the convention has no second instance, so no static test can
|
||||
settle it. Needs a measured in-game traversal against the flight model.
|
||||
🟡 **The world unit needs a run — it is NOT blocked** (label corrected
|
||||
2026-08-26). Sweeping every pak for a km-bearing name returns
|
||||
`mapmesh_box_500km` and **nothing else** (162 refs, all that one pair), so no
|
||||
*static* test can settle it; that is not the same as blocked, and 🔴 is for
|
||||
what the container cannot do. The experiment: `findplayer.py` gives the player
|
||||
and target position triples in world units, the HUD prints the distance between
|
||||
them in the game's own units, and the ratio is the conversion. All of
|
||||
`run-canary` / `pad.py` / `screenshot` / `findplayer.py` already exist.
|
||||
`tools/re-capture/collisionset.py verify|list|obj`
|
||||
([`data/collisionset.txt`](data/collisionset.txt)).
|
||||
❔ Still open: no material/surface-type field exists in the record, and the
|
||||
|
||||
Reference in New Issue
Block a user