F1 — implement held-direction repeat, taking the rate from the Decoder #2

New Issue

fabi · 2026-09-04T15:48:06Z

fabi commented

2026-09-04 15:48:06 +00:00

The mechanism is ours; the number is not.

🔴 Do not ship a placeholder rate. An invented interval is indistinguishable from a measured one a month from now, and this is the exact field where that has already cost this project once.

Pass: holding a direction repeats at the Decoder's measured initial delay and interval, and the citation in the code names the finding that supplied them.
Fail: any literal here that a docs/re/ page does not back.

Blocked until the measurement lands.

The mechanism is ours; **the number is not**. > 🔴 **Do not ship a placeholder rate.** An invented interval is indistinguishable from a measured one a month from now, and this is the exact field where that has already cost this project once. **Pass:** holding a direction repeats at the Decoder's measured initial delay and interval, and the citation in the code names the finding that supplied them. **Fail:** any literal here that a `docs/re/` page does not back. Blocked until the measurement lands.

fabi added this to the Menus milestone 2026-09-04 15:48:06 +00:00

fabi added the agent/port state/proposed kind/item labels 2026-09-04 15:48:06 +00:00

fabi added a new dependency 2026-09-04 15:48:21 +00:00

#1 F1 — measure the held-direction repeat: initial delay and interval, in frames

fabi added state/approved and removed state/proposed labels 2026-09-04 15:59:14 +00:00

sylph-decoder referenced this issue

2026-09-12 12:31:33 +00:00

F1 — measure the held-direction repeat: initial delay and interval, in frames #1

sylph-decoder commented

2026-09-12 12:31:37 +00:00

The Decoder has your numbers now: issue #1 /
docs/re/f1-repeat-measured-via-driver-patch.md
(landing via #23) — 12 frames initial delay, 4 frames steady interval,
measured at 29.87 fps guest rate (so ~402ms / ~133ms if you need wall-time,
but frame counts are the portable number). Measured, not decoded — read the
page's own caveats (one run, and it's what the game does when fed repeat
events shaped like a real controller's, not a capture through a physical
pad, since none exists in this container) before treating it as final.

The Decoder has your numbers now: issue #1 / [`docs/re/f1-repeat-measured-via-driver-patch.md`](../../docs/re/f1-repeat-measured-via-driver-patch.md) (landing via #23) — **12 frames initial delay, 4 frames steady interval**, measured at 29.87 fps guest rate (so ~402ms / ~133ms if you need wall-time, but frame counts are the portable number). Measured, not decoded — read the page's own caveats (one run, and it's what the game does when fed repeat events shaped like a real controller's, not a capture through a physical pad, since none exists in this container) before treating it as final.

sylph-decoder referenced this issue

2026-09-12 12:31:39 +00:00

re: land the F5/F6 title-clock corpus (docs/re, reference data, sylpheed-formats) #23

fabi referenced this issue from a commit

2026-09-13 11:16:20 +00:00

re: ask #2 -- t=357.7 came from a GPU draw capture, and a sweep cannot date a frame

fabi referenced this issue from a commit

2026-09-13 11:16:20 +00:00

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

fabi referenced this issue from a commit

2026-09-13 11:16:20 +00:00

re: PRE-REGISTER the guest frame-rate test -- the movie is the ruler