fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: the black gap between screens is NOT a load -- measured, three legs

Browse Source 
sylpheed-port's BLOCKED ask #2. The gap was the one quantity in the transition
with no rule: measured at 0, 3 and 2 frames across three transitions, and I had
proposed it might be a load, which would make it emulator- and storage-dependent
and unauthorable.

Leg 1, bundle size runs the wrong way. If the gap were the incoming bundle
arriving, the biggest bundle would gap longest. Build 4 is 12 278 666 B and gaps
ZERO frames; build 5 is 6 977 437 B and gaps 3 and 2.

Leg 2, ran title->menu a second time from cold. The outgoing ramp is
byte-identical (63, 127, 191, 255) and the gap is 3 frames in BOTH runs.

Leg 3, and the two runs are not a null comparison -- which is the objection leg 2
invites. The captures refute it themselves: press-to-first-change differs by ~12
frames between them (~25 against ~10). Something in this transition really is
cache-sensitive and moved by 0.4 s, while the gap did not move at all. The
control comes from inside the measurement rather than from an assumption that
conditions differed.

So the gap is deterministic to the frame and not a load. It is also not constant
across transitions (0, 3, 2, 3) and not in the fade group -- the port reports 866
keyframes across 16 screens with 0 untimed. A deterministic game quantity with no
rule found; black_hold_units stays 0, and "not a load" must not become a reason
to author a constant.

The load proposal in screen-transitions.md is marked refuted rather than deleted.

Also fills in docs/game/navigation.md, which the standing brief asks me to keep
and which I had not touched while measuring four transitions: a player-side
section on what a screen change looks like, and three scripting traps -- that
`pkill -f xenia_canary` kills the shell that ran it (cost a launch today, and the
same trap is already in METHOD for pgrep), that screen_id.py reports `menu`
during the attract loop, and that it cannot tell EXTRAS from the main menu.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
This commit is contained in:
sylph-decoder
2026-08-30 14:28:00 +00:00
parent 6afe0c4ab8
commit e803930e88
4 changed files with 192 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

50
docs/re/data/fade-three-transitions.txt → docs/re/data/fade-four-transitions.txt
View File

@@ -1,14 +1,19 @@
# THREE screen changes, per frame, from the running game. 2026-08-30.
# FOUR screen changes, per frame, from the running game. 2026-08-30.
# tools/re-capture/fade_decompose.sh (WHERE=menu | title | extras)
#
# Declared, per build (corrected keyframe association):
# build 4 title pteff00 [0:a255 16:a0 261:a0 269:a255] open 16u=8f close 8u=4f
# build 5 menu pteff00 [0:a255 12:a0 70:a0 80:a255] open 12u=6f close 10u=5f
# build 6 EXTRAS pteff00 [0:a255 12:a0 64:a0 74:a255] open 12u=6f close 10u=5f
# Captures 2 and 4 are the SAME transition, title -> menu via (A), run twice.
# They are the hold-vs-load test: a load varies with cache and contention,
# a deterministic hold does not. The pair carries its own control -- the
# press-to-first-change latency DIFFERS by ~12 frames between the two runs,
# so conditions demonstrably were not identical, while the black gap is
# exactly 3 frames in both.
#
# Capture 3's screen identity was checked, not assumed: which_title_screen.py
# on the armed frame gives extras rmse=18.58 vs main_menu 29.85, margin 11.27,
# inside the 9.9-11.7 band its control establishes on four known captures.
# quantity run 1 (cap 2) run 2 (cap 4)
# outgoing quad rise 67-70: 63,127,191,255 64-67: 63,127,191,255
# frames black ([255] alone) 70,71,72 = 3 67,68,69 = 3
# incoming appears frame 73 frame 70
# incoming decay 255,-,127,84,63 255,169,127,84,42
# press -> first change ~25 frames ~10 frames
############ CAPTURE 1 -- menu -> title, via (B) ############
frame untextured full-screen textured (distinct) draws tex
@@ -32,12 +37,8 @@ frame untextured full-screen textured (distinct) draws tex
49 [64] [32, 96, 255] 8 6
50 [64] [48, 128, 255] 8 6
############ CAPTURE 2 -- title -> menu, via (A) ############
############ CAPTURE 2 -- title -> menu, via (A), run 1 ############
frame untextured full-screen textured (distinct) draws tex
55 [] [204, 221, 255] 10 9
57 [] [204, 221, 255] 10 9
58 [] [84, 135, 147, 254, 255] 10 9
59 [] [42, 118, 128, 212, 254, 255] 10 9
60 [] [42, 50, 55, 84, 255] 9 8
61 [] [16, 18, 255] 8 7
62 [] [235, 255] 7 6
@@ -86,3 +87,26 @@ frame untextured full-screen textured (distinct) draws tex
48 [64] [7, 32, 247, 255] 8 6
49 [64] [8, 96, 246, 255] 8 6
50 [64] [9, 192, 245, 255] 8 6
############ CAPTURE 4 -- title -> menu, via (A), run 2 ############
frame untextured full-screen textured (distinct) draws tex
61 [] [137, 255] 7 6
62 [] [98, 255] 7 6
63 [] [78, 255] 7 6
64 [63] [19, 255] 8 4
65 [127] [255] 6 2
66 [191] [255] 6 2
67 [255] [255] 6 2
68 [255] [255] 6 2
69 [255] [255] 6 2
70 [64, 255] [255] 7 3
71 [64, 169] [1, 253, 255] 7 3
72 [64, 127] [2, 252, 255] 7 3
73 [64, 84] [3, 251, 255] 7 3
74 [64, 42] [4, 250, 255] 7 3
75 [64] [5, 249, 255] 7 3
76 [64] [6, 248, 255] 7 3
77 [64] [7, 32, 247, 255] 8 6
78 [64] [8, 96, 246, 255] 8 6
79 [64] [9, 192, 245, 255] 8 6
80 [64] [10, 244, 255] 8 6