From 2a11838d746791a6e7a71be0bf2e74bf23af2500 Mon Sep 17 00:00:00 2001 From: Cyd Date: Fri, 17 Jul 2026 12:57:25 -0500 Subject: [PATCH] Stream-verify the demo scenes: warp field + Klingon = DRAM-resident assets MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit trek's live-written DMA stream contains ZERO non-standard SENDs (624 pairs, all four standard payloads) -- the captured demo frames, like the bench, draw only the SMPTE test card. The warp starfield and Klingon vessel geometry are the demos' scene ASSETS resident in render memory (compiled coefficient blocks never referenced by the captured frames' chains). §07 relabeled accordingly: "Recovered assets -- the Star Trek material". Every image in the readout is now attributed by stream evidence, not memory scanning. Co-Authored-By: Claude Opus 4.8 --- emulator/firmware-decomp/render-readout.html | 32 ++++++++++---------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/emulator/firmware-decomp/render-readout.html b/emulator/firmware-decomp/render-readout.html index 26c3f40..feb5f79 100644 --- a/emulator/firmware-decomp/render-readout.html +++ b/emulator/firmware-decomp/render-readout.html @@ -388,29 +388,29 @@
-

07 The warp field — a Star Trek scene, recovered

-

The archive's trek capture — unreleased Star Trek - material — replays and draws after the dual-instruction-mode fix. Walking the - per-region DMA chains in the bin pages enumerated 898 compiled payload programs for - the frame: four are the standard end-of-frame pipeline (fog, texture, RGB — byte-identical - in every capture), and ~860 are the scene itself, per-primitive coefficient blocks - with their geometry sitting in plain screen-space floats. Plotted below: - 433 star positions and 389 streaks, radiating from a convergence point — the - warp-speed starfield, reconstructed from micro-code compiled by the board's own - firmware running on the emulated i860.

+

07 Recovered assets — the Star Trek material

+

The archive's trek and klngvid + captures — unreleased Star Trek material — replay after the dual-instruction-mode fix, and + their render memory holds ~860 compiled per-primitive payload blocks beyond the + standard program. Stream-verification shows the captured frames themselves draw only the + test card (§06) — these blocks are the demos' scene assets, resident in DRAM: + compiled geometry awaiting draws that this recording never reached. Recovered below: + 433 star positions and 389 streaks radiating from a convergence point — a + warp-speed starfield — and a vessel scene, both read from coefficient blocks compiled + by the board's own firmware on the emulated i860.

recovered from the frame's compiled payload programs -
trek at warp — every point and streak is one primitive's - position read from its compiled coefficient block (fields +0x14/+0x18 and +0x24/+0x28, - plain IEEE floats in screen space).
+
the warp starfield asset — every point and streak read from one + compiled coefficient block (plain IEEE floats). Resident in trek's render memory; + not referenced by the captured frames' chains.
same recovery · the Klingon capture -
the Klingon scene — 96 positions and 62 edge segments: a sparse - starfield with a dense tangle of intersecting edges right-of-center — a vessel, - recovered by the identical chain-walk from the klngvid capture.
+
the Klingon scene asset — 96 positions and 62 edge segments: a sparse + starfield with a dense edge tangle right-of-center — a vessel, recovered from the + klngvid capture's render memory (same resident-asset status).