06aa031980
sylpheed-port confirmed "nothing declared predicts the gap" from their export independently, and deliberately declined to search combinations: four pairs against many candidate two-screen functions fits by construction. Right call, and it applies to me unchanged. So this iteration adds a PAIR rather than a fit. menu -> a second screen outside GP_TITLE, reached by stepping the cursor two items before arming. The button is not controlled -- there is no focus readout -- so the destination is identified afterwards by its draw signature: incoming primitive [255] at 7-9 draws/frame, against the first run's [127] at 12-13. Different screens. Outgoing quad rises 25, 51, 102, 229, 255 across frames 37-42, then at frame 44 the new screen is already drawing. NO empty frame anywhere. GAP = 0. So the menu as origin gives four values across four destinations: title 0, EXTRAS 1, other-1 1, other-2 0. The same origin yields both 0 and 1 depending on where it goes, while the two repeated pairs stay internally identical (3,3,3 and 2,2). Further evidence for the ordered pair over the origin. Recorded as an observation with its counter-example rather than fitted: the incoming screen's own full-screen primitive is [255] where the gap is 0 and [127] where it is 1, which suggests a screen beginning from opaque black needs no blank frame. That FAILS on menu -> EXTRAS, which declares a black backdrop and still gives 1. Nine transitions against many candidate functions is the construction the port declined to search, and I am not searching it either. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Wuu56cE8vJGTBtn1ppsk8v
215 lines
11 KiB
Bash
Executable File
215 lines
11 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# Decompose a screen transition's ~0.4 s fade-out into RAMP + HOLD, at the
|
|
# emulator's own frame granularity.
|
|
#
|
|
# docs/re/screen-transitions.md measures the fade-out as ~0.4 s (~24 units) while
|
|
# `pteff00.prm`'s final declared ramp is 70->80 = 10 units. The remainder is
|
|
# currently ARITHMETIC THAT FITS -- "the other 14 units must be the black hold"
|
|
# -- and that page says so itself. This measures it instead.
|
|
#
|
|
# The design point: arm the UI draw capture ON THE MAIN MENU, then press (B).
|
|
# One capture window then contains
|
|
# * the menu's fade-OUT -- the unknown, and
|
|
# * the title's fade-IN -- whose ramp IS decoded from the file (build 4's
|
|
# pteff00.prm, t=16 a=255 -> t=261 a=0, 245 units),
|
|
# so the run carries its own control: an instrument that cannot reproduce the
|
|
# known fade-in cannot be trusted on the unknown fade-out.
|
|
#
|
|
# Traps inherited from menu_draw_capture.sh, both already paid for:
|
|
# * F10 arms the capture AND opens the emulator menu bar; any Xenia UI makes
|
|
# IsUIActive() true and every later guest keystroke is swallowed. Click the
|
|
# game surface to dismiss before touching the pad.
|
|
# * a 0.12 s tap gets missed; hold (B) 0.5 s and confirm [RE-INPUT] delivery.
|
|
#
|
|
# WHERE=menu (default) arms on the main menu and presses (B) -> menu -> title.
|
|
# WHERE=title arms on the boot title and presses (A) -> title -> menu.
|
|
# WHERE=extras navigates to EXTRAS, arms there, presses (B) -> menu.
|
|
# WHERE=menu2extras navigates to EXTRAS, (B)s back to the menu with focus
|
|
# restored, arms there and presses (A) -> EXTRAS. The
|
|
# REVERSE pair, to test whether the black gap is a property
|
|
# of the screen pair or of the direction.
|
|
# Tests whether "(B) has no black interval" is a rule or
|
|
# one screen pair -- sylpheed-port's BLOCKED.md ask #1.
|
|
# The two transitions have DIFFERENT declared fade-ins for the incoming screen --
|
|
# build 4 is 0->16 (16 units, 8 frames), build 5 is 0->12 (12 units, 6 frames) --
|
|
# which is what makes the pair a discriminator rather than a fit.
|
|
#
|
|
# Usage: WHERE=title fade_decompose.sh [out_dir]
|
|
set -u
|
|
export HOME=/sylph-home/re SDL_AUDIODRIVER=dummy DISPLAY=:98
|
|
SD="$(cd "$(dirname "$0")" && pwd)"
|
|
OUT="${1:-/sylph-home/re/fadecap}"
|
|
mkdir -p "$OUT"; rm -f "$OUT"/xenia_re_ui_draws_*.log
|
|
alive(){ ps -o pid=,stat= -C xenia_canary 2>/dev/null | awk '$2 !~ /^Z/ {print $1}'; }
|
|
shot(){ screenshot "$1" >/dev/null 2>&1; }
|
|
screen(){ shot /tmp/fdc.png; python3 "$SD/screen_id.py" /tmp/fdc.png | awk '{print $1}'; }
|
|
|
|
( cd "$OUT" && nohup run-canary --mem_watch=false --log_ui_draws=true \
|
|
--ui_draw_capture_frames="${FRAMES:-260}" \
|
|
--ui_draw_capture_max="${MAXDRAWS:-400000}" \
|
|
--logged_profile_slot_0_xuid=B13EBABEBABEBABE \
|
|
>"$OUT/canary.stdout" 2>"$OUT/canary.stderr" & )
|
|
sleep 8
|
|
until xdotool search --name "Xenia-canary" >/dev/null 2>&1; do
|
|
[ -n "$(alive)" ] || { echo "EMULATOR GONE"; exit 4; }; sleep 1
|
|
done
|
|
win="$(xdotool search --name "Xenia-canary" | tail -1)"
|
|
|
|
# 1. wait for the boot title; do not tap through the intro (a run that tapped
|
|
# every 4 s delivered 88 presses and ended on a black screen).
|
|
deadline=$(( SECONDS + ${TITLE_WAIT:-420} )); s=""
|
|
while [ $SECONDS -lt $deadline ]; do
|
|
s="$(screen)"; echo "t=${SECONDS}s $s"
|
|
[ "$s" = "title" ] && break
|
|
sleep 4
|
|
done
|
|
[ "$s" = "title" ] || { echo "NEVER REACHED THE TITLE"; exit 1; }
|
|
|
|
WHERE="${WHERE:-menu}"
|
|
if [ "$WHERE" = "menu" ]; then
|
|
BRANCH="menu: (A) on the boot title -> arm on the MENU -> press (B)"
|
|
# 2. one (A) on the boot title -> main menu; we arm THERE and press (B).
|
|
python3 "$SD/pad.py" tap A 0.5
|
|
for _ in 1 2 3 4 5 6; do
|
|
sleep 4; s="$(screen)"; echo " after A: $s"
|
|
[ "$s" = "menu" ] && break
|
|
done
|
|
[ "$s" = "menu" ] || { echo "NO MENU (screen=$s)"; exit 2; }
|
|
BTN=B
|
|
elif [ "$WHERE" = "menu2other" ]; then
|
|
# A THIRD value for the menu as outgoing screen. The menu is the only screen in
|
|
# GP_TITLE with more than one exit, so it is the only place the port's ask -- a
|
|
# second value on one outgoing screen -- can be tested at all. Here we take an
|
|
# exit that LEAVES the archive (NEW GAME / LOAD / TUTORIAL / OPTIONS), which the
|
|
# discriminator reports as "neither" with a collapsed margin.
|
|
BRANCH="menu2other: arm on the MENU with focus on a non-EXTRAS item -> press (A)"
|
|
python3 "$SD/pad.py" tap A 0.5
|
|
for _ in 1 2 3 4 5 6; do
|
|
sleep 4; s="$(screen)"; echo " after A: $s"
|
|
[ "$s" = "menu" ] && break
|
|
done
|
|
[ "$s" = "menu" ] || { echo "NO MENU (screen=$s)"; exit 2; }
|
|
# Confirm the focused item is NOT extras: press (A), check, (B) back. If it WAS
|
|
# extras, step the cursor once so the armed press goes somewhere else.
|
|
python3 "$SD/pad.py" tap A 0.5; sleep 5
|
|
shot "$OUT/probe.png"
|
|
w="$(python3 "$SD/which_title_screen.py" "$OUT/probe.png")"
|
|
echo " probe: $w"
|
|
python3 "$SD/pad.py" tap B 0.5; sleep 6
|
|
case "$w" in extras*) echo " focus was EXTRAS — stepping once"
|
|
python3 "$SD/pad.py" dpad UP 0.3; sleep 2;; esac
|
|
# STEPS=n moves the cursor n further items before arming, so a second run can
|
|
# leave the menu by a DIFFERENT button. The menu has four non-EXTRAS exits, and
|
|
# a second distinct destination from the same origin is what separates
|
|
# "the gap is per ordered pair" from "the gap is per origin plus destination
|
|
# class". ⚠️ There is no focus readout, so which button this lands on is not
|
|
# controlled -- it is IDENTIFIED afterwards by the destination's draw
|
|
# signature, and if the signature matches the previous run it is the same pair
|
|
# and the run says nothing new.
|
|
for _ in $(seq 1 "${STEPS:-0}"); do
|
|
echo " STEPS: moving the cursor one item"
|
|
python3 "$SD/pad.py" dpad DOWN 0.3; sleep 2
|
|
done
|
|
shot "$OUT/armed-on-menu.png"
|
|
echo " arming on: $(python3 "$SD/which_title_screen.py" "$OUT/armed-on-menu.png")"
|
|
BTN=A
|
|
elif [ "$WHERE" = "extras" ] || [ "$WHERE" = "menu2extras" ] || [ "$WHERE" = "extras2other" ]; then
|
|
BRANCH="extras-family: navigate to EXTRAS"
|
|
python3 "$SD/pad.py" tap A 0.5
|
|
for _ in 1 2 3 4 5 6; do
|
|
sleep 4; s="$(screen)"; echo " after A: $s"
|
|
[ "$s" = "menu" ] && break
|
|
done
|
|
[ "$s" = "menu" ] || { echo "NO MENU (screen=$s)"; exit 2; }
|
|
# EXTRAS is the only main-menu button that stays inside GP_TITLE, and initial
|
|
# focus varies boot to boot, so search: press (A), ask which screen we got, and
|
|
# if it is not EXTRAS come back with (B) and step the cursor. screen_id.py
|
|
# cannot tell EXTRAS from the main menu -- both are dark blue GP_TITLE screens
|
|
# -- so the check is which_title_screen.py, whose control separates them by
|
|
# ~11 RMSE against ~18 within-class.
|
|
found=""
|
|
for try in 1 2 3 4 5 6; do
|
|
python3 "$SD/pad.py" tap A 0.5; sleep 5
|
|
shot "$OUT/try$try.png"
|
|
w="$(python3 "$SD/which_title_screen.py" "$OUT/try$try.png")"
|
|
echo " try $try: $w"
|
|
# ⚠️ REQUIRE A MARGIN. The first version accepted any line starting
|
|
# "extras", but which_title_screen.py returns a nearest-match even for a
|
|
# screen outside GP_TITLE entirely -- where the margin collapses to ~0.1.
|
|
# A bare prefix test would then accept a wrong screen on a coin flip. The
|
|
# control puts a true match at ~10-11; require > 5.
|
|
m=$(echo "$w" | sed -n 's/.*margin \([0-9.]*\).*/\1/p')
|
|
ok=$(awk -v m="${m:-0}" 'BEGIN{print (m>5)?1:0}')
|
|
case "$w" in extras*) [ "$ok" = 1 ] && { found=1; break; }
|
|
echo " (rejected: margin ${m:-?} <= 5)";; esac
|
|
python3 "$SD/pad.py" tap B 0.5; sleep 5
|
|
python3 "$SD/pad.py" dpad UP 0.3; sleep 2
|
|
done
|
|
[ -n "$found" ] || { echo "NEVER REACHED EXTRAS"; exit 3; }
|
|
if [ "$WHERE" = "menu2extras" ]; then
|
|
# We are ON extras. (B) returns to the menu with focus RESTORED on EXTRAS
|
|
# (measured 4/4, menu-navigation-semantics.md), so arming there and pressing
|
|
# (A) gives the menu -> EXTRAS transition: the exact reverse of the pair
|
|
# already measured at a 2-frame gap.
|
|
python3 "$SD/pad.py" tap B 0.5; sleep 6
|
|
shot "$OUT/back-on-menu.png"
|
|
echo " back on menu: $(python3 "$SD/which_title_screen.py" "$OUT/back-on-menu.png")"
|
|
BTN=A
|
|
BRANCH="menu2extras: back on the MENU with focus restored -> press (A)"
|
|
elif [ "$WHERE" = "extras2other" ]; then
|
|
# A SECOND value for EXTRAS as the outgoing screen. I had recorded EXTRAS as
|
|
# having a sole exit -- (B) to the menu -- and called its n=1 STRUCTURAL. The
|
|
# disc refutes that: build 6 declares three buttons, ptbtn11/12/13, all kind
|
|
# 0x3002. So (A) on EXTRAS leaves it by a different route and the cap was an
|
|
# unverified assertion, not a property of the archive.
|
|
BTN=A
|
|
BRANCH="extras2other: arm on EXTRAS -> press (A), leaving by a button"
|
|
else
|
|
BTN=B
|
|
BRANCH="extras: arm on EXTRAS -> press (B)"
|
|
fi
|
|
else
|
|
BRANCH="title: arm on the BOOT TITLE -> press (A)"
|
|
# arm on the title itself and press (A): the incoming screen is then build 5,
|
|
# whose declared fade-in is 12 units where build 4's is 16.
|
|
BTN=A
|
|
fi
|
|
shot "$OUT/armed-on-$WHERE.png"
|
|
|
|
# 3. arm the capture, dismiss the menu bar F10 opened, then press (B).
|
|
# Everything between F10 and (B) is spent inside the capture window, so keep
|
|
# it short: the window is FRAMES submitted frames, not seconds.
|
|
# ── EFFECTIVE CONFIGURATION ──────────────────────────────────────────────────
|
|
# Printed from the variables actually in force, NOT from $WHERE. A three-part
|
|
# patch once left a branch condition unapplied, so WHERE=menu2extras silently ran
|
|
# the `title` branch and produced a well-formed capture of a different transition.
|
|
# The data looked fine; only the ABSENCE of this branch's log lines gave it away.
|
|
# So: every run states what it is really about to do.
|
|
echo "── EFFECTIVE CONFIG ──────────────────────────────"
|
|
echo " requested WHERE = ${WHERE}"
|
|
echo " branch taken = ${BRANCH:-<none — no branch set itself, this is a BUG>}"
|
|
echo " button to press = ${BTN}"
|
|
# ⚠️ `screen` is screen_id.py, which CANNOT tell the main menu from EXTRAS --
|
|
# both are dark blue GP_TITLE screens. Reporting it alone announced "menu" while
|
|
# the run was armed on EXTRAS, i.e. a field the guard could not resolve for
|
|
# exactly the two screens in question. An announcement that cannot distinguish
|
|
# the cases it announces is only half a guard. Print both, and the discriminator
|
|
# with its margin, so the ambiguity is visible rather than hidden.
|
|
shot "$OUT/arming.png"
|
|
echo " arming on = $(screen) [screen_id: cannot separate menu/EXTRAS]"
|
|
echo " discriminator = $(python3 "$SD/which_title_screen.py" "$OUT/arming.png" 2>/dev/null || echo 'n/a — not a GP_TITLE screen')"
|
|
echo "──────────────────────────────────────────────────"
|
|
[ -n "${BRANCH:-}" ] || { echo "REFUSING: no branch announced itself"; exit 5; }
|
|
xdotool windowactivate --sync "$win"; sleep 1
|
|
xdotool key F10; sleep 0.6
|
|
xdotool mousemove 900 400 click 1; sleep 0.6
|
|
echo "-- ($BTN) at $(date +%S.%N) --"
|
|
python3 "$SD/pad.py" tap $BTN 0.5
|
|
sleep 12
|
|
shot "$OUT/after-press.png"; echo "screen after $BTN: $(screen)"
|
|
|
|
grep -c "RE-INPUT" "$OUT/canary.stdout" 2>/dev/null | sed 's/^/[RE-INPUT] lines: /'
|
|
ls -l "$OUT"/xenia_re_ui_draws_*.log 2>/dev/null || echo "NO CAPTURE LOG"
|
|
grep -i "UI-CAP" "$OUT/canary.stdout" | tail -3
|
|
echo "FADE CAPTURE DONE (emulator left running)"
|