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

re: H3 answered -- 2 units per guest frame, and the settle anchor is t~160

Browse Source 
The Port asked which of two of my measurements to believe, 55 units/s vs
~150, a factor of 2.7 off one game. Measured on the plate's own declared
ramp, against a pre-registration committed first.

PREDICTED 11 frames at 2 units/frame, 4.4 at the Port's inferred 5, +/-1.
MEASURED 10 labels, and three consecutive gap-free steps of EXACTLY 23,
which is 255*2/22 on the nose. 5 units/frame is excluded by >2x.

Why the splash read as 5: an alpha step is not a clock rate. For a linear
segment d(alpha)/frame = 255*(units/frame)/T. Splash B's quads step 34 with
a declared T=15; the plate steps 23 with a declared T=22; ONE clock, two
steps 1.5x apart. And the Port's intervals start at each quad's first
submission, which on splash A is already alpha=85 -- not the element's t
where alpha=0, and biased by a different amount per element because T
differs. My own splash-quad-timeline.txt published alpha against frame with
no T beside it, which is the column that makes the conversion possible; it
now carries the warning.

The other half: the 'title settled' anchor is ptcopyright reaching full
alpha -- the last build-in element and the ONLY glyph one, which is what a
glyph counter settling means. Calibrated on the plate's own ramp it lands at
t~168 (t~176 at a flat 2.0/label). The Port's candidates are 118 and 160, 42
units apart: this is 8-16 units from 160 and 50-58 from 118. It is 160.

Instrument fact that bounds all of it: labels with zero draws exist, ~1 in 5,
and the clock does NOT advance a fixed amount across them -- across label
5376 the plate moved +82 where three adjacent labels each moved +23. So an
empty label is a real advance, not a logger artefact, and spans that cross
one are approximate. The conclusion rests on the gap-free steps.

Also recorded: the sweep leaves never settle. They translate monotonically
through every label examined and are still moving when the plate arrives, so
'settled' can only mean the build-in elements are done.

NOT answered, and it is what the port actually needs: units per SECOND.
units/s = (units/frame) x (guest fps); this pins the first at 2 and says
nothing about the second, and 2x30 vs 2x60 differ by exactly the ~2 s the
human reported. My own title-plate-delay-measured.md's 2.13 s does not
reconcile with this capture's 20 labels for the same two anchors -- a real
~2.9x disagreement, now localised to frames->seconds rather than
units->frames. Settling it needs the guest's own frame counter, which
neither capture read.
This commit is contained in:
sylph-decoder
2026-09-01 16:49:08 +00:00
parent 19aa1a89a3
commit 6aab30253a
3 changed files with 282 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/re/data/splash-quad-timeline.txt
View File

@@ -11,6 +11,20 @@
# Q6 x[-0.320,+0.310] y[-0.650,-0.220] submitted in 21 draws
# Q7 x[-0.530,+0.540] y[-0.130,+0.120] submitted in 8 draws
#
#
# WARNING added 2026-09-01, after this file was read as a clock rate and was not.
# The alpha column is NOT a clock rate and cannot be converted into one without
# each element's DECLARED ramp length T, which this file does not carry:
# d(alpha)/frame = 255 * (units per frame) / T
# Splash B's six quads step 34/frame with T=15; the title's plate steps 23/frame
# with T=22; both are the SAME clock at 2 units/frame. Reading a step as a rate
# gave a factor of 2.7 between two captures of one game -- see
# ../h3-units-per-frame-measured.md.
# Also: a quad's FIRST appearance here is its first submission, not its t where
# alpha=0. Q7 and Q0 are both already at alpha=85 when first submitted, so an
# interval between two first-appearances is not an interval between two declared
# times, and the bias differs per element.
#
frame slot quad x0 y0 x1 y1 alpha rgb uniform_colour
4 0 Q7 -0.53 -0.13 0.54 0.12 85 FFFFFF True
6 0 Q7 -0.53 -0.13 0.54 0.12 204 FFFFFF True

91
docs/re/data/title-plate-ramp.txt Normal file
View File

@@ -0,0 +1,91 @@
# The title's build-in and the PRESS (A) plate, off the guest's vertex stream.
# Capture 2026-09-01: ui_draw_capture.sh GRACE=1 NOTAP=1 ARM=early FRAMES=20000
# MAXDRAWS=400000, augmented draw logger (canary sylpheed-re d90d14e02).
# 30466 draws over 6565 frame labels; the title occupies labels ~5250..6456.
# 'label' is the logger's swap counter: one VdSwap = one label. Labels with NO
# draw at all exist and are listed; the animation clock does NOT advance a fixed
# amount across them, which is why counts across a gap are approximate.
## empty labels (zero draws) in 5340..5390
[5346, 5351, 5360, 5367, 5371, 5376, 5379, 5383, 5388]
## ptbtn00 -- the PRESS (A) plate NDC x+-0.40 y -0.67..-0.53 = 513x50 px at (383,550). Declared t=214 a=0 -> t=236 a=255.
label alpha step
5372 46
5373 69 23
5374 92 23
5375 115 23
5377 197 82
5378 220 23
5380 255 35
5381 255 0
5382 255 0
5384 255 0
5385 255 0
5386 255 0
5387 255 0
5389 255 0
5390 255 0
5392 255 0
5393 255 0
5394 255 0
5395 255 0
5396 255 0
5397 255 0
5398 255 0
5399 255 0
5400 255 0
## ptcopyright -- the last build-in element, and the only glyph one NDC x+-0.54 y -0.87..-0.82 = 691x36 px at the screen foot.
label alpha step
5341 23
5342 57 34
5343 81 24
5344 104 23
5345 139 35
5347 208 69
5348 231 23
5349 243 12
5350 255 12
5352 255 0
5353 255 0
5354 255 0
5355 255 0
5356 255 0
5357 255 0
5358 255 0
5359 255 0
5361 255 0
5362 255 0
5363 255 0
5364 255 0
5365 255 0
5366 255 0
5368 255 0
5369 255 0
5370 255 0
5372 255 0
5373 255 0
5374 255 0
5375 255 0
5377 255 0
5378 255 0
5380 255 0
5381 255 0
5382 255 0
5384 255 0
5385 255 0
5386 255 0
5387 255 0
5389 255 0
5390 255 0
5392 255 0
5393 255 0
5394 255 0
5395 255 0
5396 255 0
5397 255 0
5398 255 0
5399 255 0
5400 255 0