Files
Sylpheed/docs/re/data/f1-repeat-cursor-transitions.tsv
sylph-decoder ed9a7d702d re: F1 answered -- 12 frames initial delay, 4 frames interval, by patching in the repeat the driver lacked
Direct follow-through on this session's own named next step. The prior
result (f1-held-down-measured-no-repeat-via-file-driver.md) concluded the
file driver cannot show menu repeat because its GetKeystroke() never emits
a REPEAT-flagged event, and that the menu's repeat is very likely driven by
that flag rather than raw polled state. Testable, so tested: patched
/canary/src/xenia/hid/file/file_input_driver.h to add opt-in repeat behind
a new --pad_file_repeat cvar (off by default, every other scripted script
unaffected), using the SDL driver's own constants verbatim
(HID_SDL_REPEAT_DELAY/_RATE = 400/100, guest-time ms via
Clock::QueryGuestUptimeMillis) rather than re-deriving them. Incremental
rebuild, ~1 minute (only xenia_main.cc needed recompiling).

Control: the driver's own log confirms repeated keystroke events fire as
designed, zero crashes.

Result: re-ran the identical held-DOWN capture. The cursor that moved once
and stopped in the null result now cycles continuously through the whole
5-item menu, wrapping, for as long as the button is held -- the null result
was real for that driver path, and giving the driver the one thing it
lacked reverses it completely.

Measured at this run's achieved 29.87 fps guest rate: 12 frames (~402ms)
initial delay from the press-triggered step to the first repeat step; 4
frames (~133ms) steady-state interval for 13 of 15 gaps, 3 frames (~100ms)
for the other 2 -- slower than the raw 100ms constant driving it, which
this page flags but does not trace further (most likely the game batches
drained keystrokes per its own frame tick rather than reacting to each one
instantly). The 4-frame figure is what matters for the port: it's what the
cursor visibly does.

Honestly scoped: this measures what the game does when FED repeat events
shaped like the SDL driver's, not a capture through an actual physical
controller (none exists in this container) -- classified measured, not
decoded, for exactly that reason. One run only; the corpus's two-run
minimum isn't met, flagged rather than overclaimed.

f1_hold_capture.py gains an optional `repeat` argument. The Canary source
patch itself lives in /canary, outside this repo (Canary source, not
sylpheed-formats) -- fully described inline in the finding doc so it can be
reapplied if that tree doesn't persist across a container reset.

Reference data: docs/re/data/f1-repeat-cursor-transitions.tsv -- every
transition's frame, guest tick and Y position, not the raw draw log.
2026-09-12 12:31:05 +00:00

24 lines
956 B
Plaintext

# frame gtick gfreq_hz cursor_quad_y_ndc frames_since_prev_transition
# source: xenia_re_ui_draws_01.log, 2026-09-12, f1_hold_capture.py OUTDIR 2.5 repeat (run f1h)
# --pad_file_repeat=true: file_input_driver.h emits Keystroke REPEAT at SDL-driver constants (400ms delay/100ms interval, guest time)
# quad: page B5B1C73032BA3FA3, ~0.09x0.16 NDC (focus highlight)
1 8088762299 50000000 0.05 0
3 8092093499 50000000 -0.16 2
15 8112191520 50000000 -0.385 12
19 8118864353 50000000 0.5025 4
23 8125673641 50000000 0.28 4
27 8132277847 50000000 0.055 4
31 8138935070 50000000 -0.1625 4
35 8145620699 50000000 -0.385 4
39 8152349650 50000000 0.505 4
43 8159014126 50000000 0.285 4
46 8164059013 50000000 0.05 3
50 8170775552 50000000 -0.1675 4
54 8177444513 50000000 -0.3875 4
58 8184235878 50000000 0.5025 4
62 8190930524 50000000 0.28 4
66 8197605724 50000000 0.05 4
70 8204312489 50000000 -0.1675 4
73 8209322148 50000000 -0.39 3
77 8216032739 50000000 0.5 4