The port raised a real caveat: my earlier scans filtered on height (>1.2
NDC) and sample count (>=20), so a population of many small lights would
have been invisible to both by construction. Dropping both filters, over
the whole title era: 59 distinct shapes, 2 moving, 57 static, and ZERO
small moving shapes. The two moving keys are the rounding-split halves of
one element, pteff03.
So there is exactly one moving quad on the title, 883x1134 px.
That answers the human's actual uncertainty -- whether the game renders one
light per line or one light covering several close lines. It is the second:
the multiple lights are painted INTO the texture of a single large sweeping
sprite, not drawn as separate moving objects. A port reproducing "several
lights" as several elements would be modelling the wrong thing.
The port's caveat was right to raise and the check excludes the population
it warned about -- third time in this exchange that asking was worth it
even when the specific worry did not apply.
What I have NOT done, and it was the literal ask: the human asked for
screenshots and I have taken none. I answered the counting question from
the draw stream because it is the stronger instrument for how-many and
how-big -- it reads the guest's vertex buffer rather than pixels and cannot
miss a faint light. But "what do the lights look like" is a question about
an image and the draw stream cannot answer it. That remains open.
Reach: one boot, one window, every quad in the stream. Static elements are
not counted as lights -- 57 exist and some may pulse in place; this unit
counts motion, not brightness.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jc4pciRArGHfxGGhEbwp5t
ffde5abd94