← Technical publications

White paper

Inside CoCoMan on the Color Computer 3

Replacing a PPU with Generated Code, Banked Bitmaps, and a Decoupled 6809 Render Pipeline

Abstract

I built CoCoMan as an eight-world, 32-course action platformer for a stock-speed 512 KB Color Computer 3. The Color Computer and the Nintendo Entertainment System ran nominally similar 1.79 MHz 8-bit processors, but they did not divide graphical work the same way. The NES Picture Processing Unit fetched tiles, applied scrolling, composed sprites, resolved priority and generated the raster while the CPU supplied game rules and small updates. The CoCo 3's GIME scanned a bitmap, supplied a palette and supported display offsets. It did not supply a sprite list, tile fetcher, collision hardware or the same fixed pipeline. I therefore had to replace that work with a software renderer running on the same 6809 that simulated the game. [1, 2]

I built the game around that problem. I separated field-rate input and rules from variable-rate presentation, gave each drawing page its own sprite backups and terrain history, compiled repeated drawing work into 6809 routines, and paged the campaign across four disks. The game does not reproduce the NES PPU in software, nor does it reproduce NES frame rates everywhere. It replaces the PPU's division of labor with a different one. Input and rules advance every vertical field; pictures are committed only when a complete drawing page is ready. The simulation can therefore stay ordered while the renderer falls behind. In three measured passages, Release Build #3 presented 11, 11 and 21 pictures per second, with longest complete holds of 183, 117 and 50 ms. A joystick press became a visible lift after nine NTSC fields, or 150 ms. Those measurements show a playable schedule under named loads, not a game-wide frame rate.

The result I set out to achieve is narrower and more useful than saying the CoCo 3 matched a console built around a dedicated video processor. I built an original campaign with suits, swimming, assisted flight, moving machinery, projectiles, backtracking and side rooms by making presentation a scheduled software subsystem. The difficult part for me was keeping that subsystem inside the 6809 cycle budget and the Color Computer's banked-memory budget while preserving the timing and visible consequences of play.

Attribution and rights · Designed by Brian Holman · Sponsored by Dezota LLC

A closer look

Open original