re: the keyframe block s +4 and +8 are angles used almost always as a 180 flip
Narrows a standing unexplained pair without claiming to decode it, and states precisely why it cannot be closed in this container. Census over every UI pak on the disc -- 2859 builds, 90347 keyframes, parents and nested leaves. +4 has 12 distinct values and +8 has 11, against 157 for the decoded rotation at +12. Per sprite-instance across 14241 of them, with +12 as a control because it is known to hold a real angle: +4 takes more than two distinct values on 7 instances, +8 on 99, and +12 on 396. So +4 is in practice a two-state field whose state is 180 -- and for a screen-plane sprite a 180 degree rotation about an in-plane axis is a mirror. But they are not booleans. GP_TITLE entry 7 s ptlogo3a runs +4 = -72, -18, -4, -1 against +12 = -14, -4, -1, 0: the two decay to zero together with +4 roughly four to five times +12 at each keyframe. That is a coupled two-axis settle and the strongest support the disc offers for the three-axis reading. So the readings reconcile -- the field is an angle whose overwhelmingly common use is the 180 degree special case. The reach is the important half. All six non-zero +4/+8 keyframes in GP_TITLE are in entry 7, the Japanese title, which has no oracle capture and which MISSION scopes out as localisation beyond English. The five English screens that do have captures carry +4 = +8 = 0 on every keyframe, so they never exercise the fields. The paks that use them heavily, GP_READY_ROOM at 4686 and GP_DIALOG at 1058, are also out of scope and GP_READY_ROOM is a recorded no-go. So this is untestable against every oracle the project holds rather than merely unfinished. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QsEPXWVaEpyfudtR6re1Pd
This commit is contained in:
sylph-decoder
40
docs/re/data/kf-unknown-4-8-census.txt
Normal file
40
docs/re/data/kf-unknown-4-8-census.txt
Normal file
@@ -0,0 +1,40 @@
|
||||
2859 builds, 90347 keyframes (parents + leaves)
|
||||
|
||||
+4: 12 distinct values, 4289 non-zero keyframes (4.7473%)
|
||||
180 x4200
|
||||
-180 x24
|
||||
22 x24
|
||||
90 x18
|
||||
-45 x8
|
||||
60 x8
|
||||
+8: 11 distinct values, 4064 non-zero keyframes (4.4982%)
|
||||
180 x3288
|
||||
90 x201
|
||||
-180 x156
|
||||
178 x144
|
||||
45 x99
|
||||
23 x95
|
||||
+12 (rotation): 157 distinct values, 12520 non-zero keyframes (13.8577%)
|
||||
90 x1968
|
||||
-90 x1260
|
||||
180 x608
|
||||
120 x540
|
||||
-58 x426
|
||||
53 x408
|
||||
|
||||
keyframes with a non-zero +4 or +8: 6345
|
||||
GP_BUNK.pak e1 pjnet_bg.rat->pjnet_base.t32 +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e1 pjnet_bg.rat->pjnet_loop1.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e1 pjnet_bg.rat->pjnet_loop2.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e1 pjnet_bg.rat->pjnet_loop1.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e3 pjnet_bg.rat->pjnet_base.t32 +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e3 pjnet_bg.rat->pjnet_loop1.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e3 pjnet_bg.rat->pjnet_loop2.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e3 pjnet_bg.rat->pjnet_loop1.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e4 pjeff02.rat->pjeff21.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e4 pjeff02.rat->pjeff21.rat +4=180 +8=0 +12=360
|
||||
GP_BUNK.pak e6 pjeff02.rat->pjeff21.rat +4=180 +8=0 +12=0
|
||||
GP_BUNK.pak e6 pjeff02.rat->pjeff21.rat +4=180 +8=0 +12=360
|
||||
GP_CHALLENGE.pak e71 pjnet_bg.rat->pjnet_base.t32 +4=180 +8=0 +12=0
|
||||
GP_CHALLENGE.pak e71 pjnet_bg.rat->pjnet_loop1.rat +4=180 +8=0 +12=0
|
||||
GP_CHALLENGE.pak e71 pjnet_bg.rat->pjnet_loop2.rat +4=180 +8=0 +12=0
|
||||
86
docs/re/structures/ui-keyframe-unknown-4-8.md
Normal file
86
docs/re/structures/ui-keyframe-unknown-4-8.md
Normal file
@@ -0,0 +1,86 @@
|
||||
# 🟡 The keyframe block's `+4` and `+8` — narrowed, not decoded
|
||||
|
||||
**Status:** 🟡 the space is much narrower than "unexplained", and the reason it
|
||||
cannot be closed here is specific and worth stating. ❔ **Not decoded** — nothing
|
||||
below is confirmed against the oracle.
|
||||
|
||||
`+12` is ✅ decoded as a screen-plane rotation in degrees
|
||||
([`ui-keyframe-rotation.md`](ui-keyframe-rotation.md)). `+4` and `+8` sit
|
||||
immediately before it, are carried rather than dropped, and one standing reading
|
||||
is that the three together are rotations about three axes — *"not tied to an
|
||||
observed rotation"*.
|
||||
|
||||
Census over **every UI pak on the disc**: 2 859 builds, **90 347 keyframes**,
|
||||
parents and nested leaves alike.
|
||||
[`data/kf-unknown-4-8-census.txt`](../data/kf-unknown-4-8-census.txt),
|
||||
`--example kf_unknown_census`.
|
||||
|
||||
## They do not behave like `+12`
|
||||
|
||||
| | `+4` | `+8` | `+12` (decoded rotation) |
|
||||
|---|---|---|---|
|
||||
| distinct values | **12** | **11** | **157** |
|
||||
| non-zero keyframes | 4 289 (4.75 %) | 4 064 (4.50 %) | 12 520 (13.86 %) |
|
||||
| commonest non-zero | **180** ×4 200 | **180** ×3 288 | 90 ×1 968 |
|
||||
|
||||
And per sprite-instance, across 14 241 of them — with `+12` as the **control**,
|
||||
since it is a field known to hold a real angle:
|
||||
|
||||
| | both 0 and ±180 in one build | ±180 with no 0 | **more than 2 distinct values** |
|
||||
|---|---|---|---|
|
||||
| `+4` | 415 | 252 | **7** |
|
||||
| `+8` | 360 | 180 | **99** |
|
||||
| `+12` (control) | 155 | 30 | **396** |
|
||||
|
||||
🔴 **`+4` takes more than two values on 7 instances out of 14 241; `+12` does so
|
||||
on 396 — 57× more.** In practice `+4` is a two-state field, and the state is
|
||||
`180`. For a screen-plane sprite a 180° rotation about an in-plane axis **is a
|
||||
mirror**, so the overwhelmingly common use of these fields is a **flip**.
|
||||
|
||||
## ⚠️ But they are NOT booleans, and one element shows why
|
||||
|
||||
`GP_TITLE` entry 7 has the only interesting case on the disc's title side:
|
||||
|
||||
```
|
||||
ptlogo3a.t32 +4=-72 +12=-14
|
||||
+4=-18 +12=-4
|
||||
+4=-4 +12=-1
|
||||
+4=-1 +12=0
|
||||
```
|
||||
|
||||
**`+4` and `+12` decay to zero together**, `+4` running roughly 4–5× `+12` at
|
||||
each keyframe. That is a coupled two-axis settle, not a flag — and it is the
|
||||
strongest support the disc offers for the three-axis reading. The census's other
|
||||
odd values (`22`, `60`, `−45`, `178`, `23`) say the same thing more weakly.
|
||||
|
||||
✅ **So the two readings reconcile:** the field **is** an angle, and its
|
||||
overwhelmingly common *use* is the 180° special case that mirrors a sprite. A
|
||||
consumer that treats it as a boolean will be right 97 % of the time and wrong on
|
||||
`ptlogo3a`.
|
||||
|
||||
## 🔴 Why it cannot be closed here — the reach
|
||||
|
||||
**All six non-zero `+4`/`+8` keyframes in `GP_TITLE` are in entry 7**, the
|
||||
Japanese title:
|
||||
|
||||
```
|
||||
e7 ptlogo3a.t32 +4=-72/-18/-4/-1
|
||||
e7 ptlogo_eff2.rat->ptlogo_eff2.t32 +4=180 (both keyframes)
|
||||
```
|
||||
|
||||
* `title_jp` has **no oracle capture**, so a mirror or a two-axis settle cannot
|
||||
be confirmed against the running game in this container;
|
||||
* MISSION §7 scopes out *"localisation beyond English"*, so entry 7 is **not a
|
||||
question this port has to answer**;
|
||||
* the five English screens that *do* have captures have `+4 = +8 = 0` on every
|
||||
keyframe — **they never exercise these fields at all**.
|
||||
|
||||
⚠️ So this is not "needs more work"; it is **untestable against every oracle this
|
||||
project holds**, and the only assets that would test it are out of scope. The
|
||||
paks that use the fields heavily — `GP_READY_ROOM` (4 686), `GP_DIALOG` (1 058) —
|
||||
are also outside the menu port's scope, and `GP_READY_ROOM` is separately a
|
||||
recorded no-go.
|
||||
|
||||
**For the port:** the five menu screens are unaffected either way. Carrying the
|
||||
fields rather than dropping them, which `sylpheed-formats` already does, remains
|
||||
the right handling.
|
||||
Reference in New Issue
Block a user