975d77f0b2
EXTRAS whole-screen residual 1.97 -> 0.63; ptframe4 31.90 -> 1.14, pteff21/22/23 from 12-14 to under 0.8. The four elements I reported as in no draw were in a draw all along -- the vertex dump was capped at two quads and the batch holds six, so four were dropped with a well-formed line and no ellipsis. Same failure class as my MIX-default material: the run completed, the output parsed, the answer was wrong. Their pteff10 flag, tested by holding it alpha-over with everything else additive: tone-corrected residual 0.630 additive against 1.704 alpha-over, but raw RMSE 12.91 against 9.98. They disagree because the port already renders +8.50 levels brighter than the capture on this screen before any of this, so raw RMSE punishes added light whether or not the light is right. Adopted on the measurement plus the structural metric; extras raw-rmse went 11.43 -> 12.88 and that is stated, not hidden. The differing region halved, 0.07 % -> 0.03 %. Refuted, mine: "every decoration 0x0 and every button 0x3002" was a two-screen generalisation I called a confirmation, one message after objecting to exactly that move in their page. My own export held the counter-examples -- ptbtn00 is 0x73002 and my exporter calls it unknown rather than button; three title elements are 0x3000, button-shaped and not focusable. kind & 0x2 is the focusable flag. Refuted, mine: the sweeps DO run on the main menu. Their log retains NDC and both strips overlap the screen in every captured frame, stepping in opposite directions with vertex alpha ramping. My phase sweep measured that the PORT'S sweeps make the match worse, which is a statement about my rendering, not about the game. A best-match argument for an absence cannot separate "not there" from "there and drawn wrong", and I had that caveat written down and read past it. Not flipped: the strips are additive with a ramping vertex alpha and the port has neither on the leaf path, so enabling the loop today would be more correct in behaviour and worse on screen. The ramp is asked for. What changed today is the claim -- the port is wrong here and now says so.
Sylpheed
A clean-room reverse engineering and port project for Project Sylpheed: Arc of Deception (Xbox 360, 2007).
Three things live here, in one repository so that a change spanning them lands as one commit:
| The decoders | crates/sylpheed-formats — the disc's formats, read and verified disc-wide |
| The port | port/ — a Godot 4 project, plus crates/sylpheed-export which converts a disc into the open asset tree it reads |
| The corpus | docs/re/ — what has been reverse engineered, with its evidence, its retractions and its dead ends |
You need your own copy of the game. No game content is in this repository and none ever will be. The exporter reads the disc you supply.
The oracle is the real game
sylpheed-cliand the Explorer are tools for verifying our decoding. They are hypotheses under test and they have been wrong. When something must be checked against the truth, the truth is the game running in Xenia Canary, captured — not any renderer of ours.
This is stated first because getting it backwards is the most expensive mistake this project has made.
Layout
crates/
sylpheed-formats/ the decoders. Disc-wide verified; the corpus is its spec
sylpheed-cli/ headless tools -- render a screen, dump a table, probe audio
sylpheed-viewer/ the Explorer: a human's window onto the disc. STATIC data only
sylpheed-export/ disc -> the open, moddable asset tree
port/ the Godot 4 project. Reads open formats ONLY
authored/ decisions that are NOT on the disc, each with its reason
data/
base/ generated by the exporter. Gitignored, never hand-edited
mods/ drop-in overrides. Yours
docs/
re/ the corpus: findings, refutations, method traps
game/ how the game is navigated -- menus, modals, flight
port/ the port's mission, its handoff contract, modding rules
-- and RUNNING.md, which is how you actually start it
agents/ how the agent team works together
tools/ capture harnesses, probes, the share tool
exchange/ transient inter-agent files. NOT in git
docker/ the agent containers
Where to start
docs/re/INDEX.md— what is decodeddocs/re/REFUTED.md— what has been tested and dieddocs/re/METHOD.md— traps this project has already paid fordocs/game/navigation.md— how the game is navigateddocs/port/MODDING.md— why the asset tree looks the way it does
Xenia Canary is a separate repository: it is a fork tracking upstream, and it carries our instrumentation.
Conventions
Confidence is per claim, never per document: ✅ CONFIRMED · 🟡 PROBABLE ·
❔ HYPOTHESIS · ❌ REFUTED. A withdrawn result is kept with its reasoning
rather than deleted — that is why the numbers here can be trusted.