Detailed Structural Mapping of Video Content

Metadata

Field	Value
source	../Video_Breakdown_and_Concepts.md
document	Technical Architecture and Systems Deconstruction of Inkbox’s “It Took Every SNES Hardware Trick To Make My Game”
kind	section-lead
parent
lines	49-64
video	https://www.youtube.com/watch?v=j_2bo7ng65E
findings	D14-C1 D14-C2 D14-C3 D14-C4 D14-C5 D14-C6 D14-M2 D14-M3 D14-M4 D14-M9 D14-M10 D14-m2 D14-m8

Source video: It Took Every SNES Hardware Trick To Make My Game (Inkbox, 51:14). The video does not give a stage table. The subsystems exist in the video, but the challenge and solution cells repeat the errors of parts 04 to 11.

The following table summarizes the video presentation, linking narrative segments to their underlying hardware subsystems, primary technical challenges, and software implementations:

Segment Title	Target Hardware Subsystem	Primary Technical Challenge	Core Software Implementation
1. Architecture Baseline & Constraints [cite: 1, 2]	Ricoh 5A22 CPU & System Bus1	Strict 3.58 MHz processing budget, lack of OS, non-uniform memory architecture1.	Bare-metal 65c816 assembly implementation; zero external coprocessor dependence1.
2. WRAM Banking & Procedural Maps [cite: 1]	128 kB Work RAM (Banks $7E/$7F)1	Generating large dynamic playfields without memory fragmentation1.	Bank $7F dedicated to a 63 kB procedural tile buffer; Bank $7E isolated for stack and system state1.
3. PPU Configuration & BCD HUD [cite: 1]	Dual PPUs & Background Mode 11	High cycle cost of runtime integer division for five-digit base-10 HUD tallies1.	Mode 1 layer allocation; Packed BCD arithmetic with hardware decimal flag (SED)1.
4. HDMA Scanline Modulation [cite: 1]	DMA Controller & PPU Registers1	Generating convincing environmental depth without CPU frame cycle consumption1.	Per-scanline horizontal offset table updates targeting register $2111 during H-Blank1.
5. OAM Management & Sprite Limits [cite: 1]	Object Attribute Memory (OAM)1	Hardware dropout and flickering caused by the 32 sprites-per-scanline threshold1.	Viewport culling; dynamic OAM cycling; redirecting inactive sprites to transparent dummy tile 01.
6. Spatial Hashing & Collision [cite: 1]	65c816 Math & WRAM Data Access1	Quadratic scaling (![][image1]) of traditional pairwise bounding box collision algorithms1.	Direct ![][image2] memory address hashing from coordinates; viewport-bounded enemy updates1.
7. Hardware Color Arithmetic [cite: 1]	PPU Color Math Engine1	High bus-bandwidth cost of modifying CGRAM palettes during active frame cycles1.	Sub-screen color subtraction for hit-stop black flashes; real-time blending for spells1.
8. SPC700 Subsystem & Audio Engine [cite: 1, 3]	Sony SPC700, DSP, 64 kB ARAM1	Asynchronous communication and lack of flexible open-source audio drivers1.	Custom SPC700 driver; BRR compression; dynamic 5-voice music and 3-voice SFX allocation1.
9. Physical Synthesis & Testing [cite: 1, 3]	PCB Bus & Physical Mask ROM1	Silicon behavioral divergences from emulator timing, bus floats, and uninitialized RAM1.	Mouse Bite Labs open hardware; EEPROM verification; open-source driver release1.

Review findings for this part

The findings come from ../../findings/ (pass 1). The script matches them to this part by source line.

ID	Severity	Evidence	Status	Location	Problem
D14-C1	critical	VIDEO KNOW DOC	open	L27, L58, L84, L111, L117-133, L179	Claim: HDMA writes register $2111 (BG3HOFS) for mountain parallax in the game, with bands at scanlines 60, 120, 160 and 210 and rates dx0.25 and dx0.50. Problem: The video puts the parallax on the title screen, not in the game (34:08). The far mountains sit on layer 3, and the clouds that scroll sit on layer 2 (34:28). At 35:31 Inkbox says that he writes “the background two horizontal scroll register”. That register is $210F, not $2111. The table has three bytes per entry: a line count and a two-byte value (35:51). The scanline numbers and the rates in the diagram are not in the video. In the game, the only HDMA scroll effect moves the inventory selection on layer 2 (33:47, 36:31).
D14-C2	critical	VIDEO	open	L31, L59, L138, L180, L200	Claim: The engine sorts entities vertically, maps culled actors to transparent “tile zero”, and cycles sprite priority across alternating frames. Problem: The video says the opposite. At 28:34 the five unused sprites of each coin already point to transparent tile zero. The PPU “still counts those transparent sprites” toward the 32 per line, so tile zero is the problem. The fix moves a tile-zero sprite “down to an offscreen value” (28:55). At 30:08 Inkbox says that registers exist to rotate sprites in OAM, but he decides to “leave it as is for now”. At 30:55 he says that the objects are “not organized by X or Y”. The value “Y = 224” in image 3 is not in the video.
D14-C3	critical	VIDEO DOC KNOW	open	L35, L60, L142-147, L181	Claim: Pairwise collision is O(n^2) or O(nm). The map in bank $7F is a “spatial hash grid”. Address = Base + (Y192) OR X, and Y192 = (Y<<7) OR (Y<<6). Off-screen enemies run on “lightweight timer routines”. Problem: The video gives the idea only: from the X and Y of the player, with the scroll, find the tile under the player (05:50). Inkbox says this is “faster” than a loop over a wall list (06:11). He gives no formula, no complexity class and no cycle counts. The formula in image 9 is also wrong. Shift results must be added, not combined with OR: for Y = 3, (3<<7) OR (3<<6) = 448, but 3192 = 576. The OR between Y*192 and X also fails, for example Y = 1, X = 65 gives 193, not 257. The formula also assumes one byte per tile. The video says that 192 x 168 tiles fill 63 K (06:53), so each tile takes two bytes. The video does not describe timer routines for off-screen enemies. Object collision uses generic hitbox functions against the player (38:55) and against on-screen chickens (42:19).
D14-C4	critical	VIDEO	open	L43, L62, L94, L162, L183	Claim: Three “preemptive” sound-effect voices. The driver “preempts lower-priority musical voices and restores them cleanly”. Problem: The video says that voices 0 to 4 play music and that the last three voices wait on standby for the CPU (18:18 to 18:38). The CPU tells the APU “which voice channel to run the effect on”. At 39:35 object sounds play on a channel “reserved for object sounds”, so they do not disturb the player sounds or the music. No voice is taken from the music.
D14-C5	critical	VIDEO VERIFY	verify	L45-47, L63, L164-168, L184	Claim: Inkbox flashed ROM chips, tested cartridges on retail consoles, found divergences between Mesen, bsnes and real hardware, and added “boot-clearing loops”. Problem: The video has none of this. The cartridge work is a solder mask and transparent shells from the sponsor (07:36 to 08:40), the arrival of the parts (45:36 to 46:18), and solder paste (46:18). At 46:55 Inkbox says that the cartridge is good to go “as soon as I finish the game”. The itch.io page tells players to use Mesen or bsnes and says nothing about cartridges (checked by WebFetch). The emulator divergence, the uninitialized RAM problem and the boot-clearing loops are inventions.
D14-C6	critical	DOC VERIFY	verify	L5-203 (all citations)	Claim: Each sentence cites “1”, and the text names the video as the subject. Problem: Source 1 is the techeblog news article, not the video. The video is source 3, and the text cites it only three times together with 1 (L62, L63, L184). The reviewer fetched source 1. It is a short summary that mentions HDMA, mode 1, 128 sprites and five plus three voices. It says nothing about spatial hashing, color math, priority cycling, emulator divergence or compilers. So most citations point to a source that does not hold the claim. A “video breakdown” that cites a news article for the video is not a breakdown of the video.
D14-M10	major	VIDEO VERIFY	verify	L43, L62, L162	Claim: Inkbox wrote the driver “due to the lack of modern, modular sound drivers”. Problem: The video says that “there are lots of SNES sound engines” that he could use (14:08 to 14:29). He writes his own because the Nintendo driver is copyrighted and because he wants to learn. The repository SimpleSNESSoundEngine exists on GitHub with an MIT license and uses SPCASM (checked by WebFetch).
D14-M2	major	VIDEO	open	L19, L56, L99-100, L177	Claim: Bank $7F holds the world and bank $7E holds the stack and entity arrays, which “prevents stack overflows” and “heap fragmentation”. Tunnels are “single-tile pathways” from “deterministic Manhattan vectors” that “avoid loops”. Problem: The video says that the world fills 63 K of the second RAM bank (06:31 to 06:53). The objects were first planned for $7F0000, but Inkbox moved them to the first bank to avoid data bank register swaps (21:18 to 21:59). There is no heap, so there is no fragmentation. Rooms come from the random number routine with rejection (25:08). Tunnels are rooms “with either a small width or height” (25:50), not single tiles. The first method made islands (26:12). The fix tunnels to the closest connected room. Inkbox calls it “not perfect” and says that it can give very long tunnels (26:32). Nothing is deterministic.
D14-M3	major	KNOW VIDEO VERIFY	verify	L23, L57, L105, L176	Claim: The CPU lacks “hardware division instructions”, and decimal output “relies on integer division and modulo operations, both of which are expensive”. Problem: The 5A22 has a hardware unit: $4202 and $4203 start an 8 x 8 unsigned multiply, $4204 to $4206 start a 16 / 8 unsigned divide, and $4214 to $4217 give the quotient, product and remainder (snes.nesdev.org MMIO registers, checked by WebFetch). The video does not give division cost as the reason. Inkbox uses BCD because “it makes the math so much easier” (32:05). The document also omits the trap of the video: INC and DEC ignore the decimal flag, so he must use ADC (32:05 to 32:26). The “LSR and AND” nibble split at L106 is not in the video.
D14-M4	major	VIDEO	open	L39, L61, L86, L152-157, L182	Claim: Hit stop is a “single-frame black flash”. The engine writes $2132 and enables subtraction in $2131, “inverting the display”. The talismans use color math: fire trails, ice “shifts color palettes”, gold and peach give “screen-wide color flashes”. Problem: The video describes one trick: layer 3 holds black tiles, layer 1 leaves the subscreen, and “add and divide by two” halves the brightness (37:13 to 37:34). That is addition, not subtraction, and no inversion. The same trick darkens the background during hit stop, which pauses the game “for a few frames” (40:37). The four talisman effects are four palette colors of the same cloud animation (42:39). Three talismans spawn new objects (42:59). The video never says that the ice talisman freezes anything or that a screen flashes.
D14-M9	major	VIDEO KNOW	open	L31, L59, L137, L180	Claim: The PPU renders “a maximum of 32 sprite tiles” per scanline, and “lower-priority sprites are dropped”. Problem: The limit is 32 sprites per line and also 34 slivers of 8 pixels per line (29:38 to 29:59). With 16 x 16 sprites, 24 objects plus the player give 48 slivers, so only 17 objects drew. The document omits the sliver rule, which was the real cause of the lost player sprite.
D14-m2	minor	VIDEO KNOW	open	L6, L15, L23, L55	Claim: “Ricoh 5A22”, “3.58 MHz”, “dual PPUs (PPU1 and PPU2)”, “absence of an integrated memory management unit”. Problem: The video names none of these. The values are correct hardware facts, but they are not from the video.
D14-m8	minor	DOC	open	L35, L60, L138, L142-146, L181	Claim: Formulas shown as images. Problem: All nine formulas are images. A screen reader cannot read them. A reader cannot search or copy them. The decoded content is: O(n^2), O(1), Y = 224, n, m, O(n * m), (x, y), the address formula and the shift formula.

Review worksheet

1. Goal of this part

What does this part try to show, or help the reader decide?

2. Key claims to test

#	Claim	Evidence given (citation / data)	Verifiable?
1

3. Adversarial review

Strongest counter-argument:
Unsupported, overstated, or outdated claims:
Source quality (primary vs. blog/forum/marketing):
Omissions / what a skeptic would ask:
Internal consistency with other segments:

4. Evaluation

Does the segment achieve its goal? (Yes / Partly / No)
Confidence: (High / Medium / Low)
Required fixes: