Why a Neo Geo Port of Doom Is Functionally Impossible: A Technical Deep Dive

## The Question

Ars Technica published an article explaining why porting Doom to the Neo Geo is "functionally impossible." The question is irresistible to retro computing enthusiasts because Doom has been ported to everything — calculators, pregnancy tests, oscilloscopes. Why not the Neo Geo?

## The Neo Geo Architecture

The Neo Geo AES (1990) was the most powerful console of its generation. But it was designed for one thing: 2D sprite-based games. Its architecture makes first-person 3D rendering fundamentally incompatible:

| Component | Neo Geo | What Doom Needs |
|-----------|---------|----------------|
| Graphics | Sprite-based tilemap | Framebuffer (pixel-based) |
| CPU | Motorola 68000 @ 12MHz | Fast enough (barely) |
| RAM | 64KB work RAM | At minimum 4MB for level data + rendering |
| VRAM | Tile-based (sprites only) | Framebuffer for per-pixel rendering |

## The Framebuffer Problem

The Neo Geo has no framebuffer. Every visual element is a sprite — a 2D tile rendered at a fixed position. Doom renders the world pixel by pixel, building a frame in a buffer and then displaying it. The Neo Geo literally cannot do the one thing Doom requires.

## Why Other Ports Work

| Platform | Why Doom Runs |
|----------|-------------|
| Pregnancy test | Has a small MCU with a framebuffer LCD controller |
| Oscilloscope | External display with vector graphics — bypass rendering entirely |
| TI-83 Calculator | Has a bitmapped display (framebuffer) |
| Neo Geo | Sprite-only display, NO framebuffer |

The pregnancy test has more Doom-compatible graphics architecture than the Neo Geo. Let that sink in.

## The Theoretical Workaround

If someone were masochistic enough to attempt it, the only approach would be:
1. Render Doom on the 68000 as normal
2. Convert each frame into sprite tiles dynamically
3. Place dozens of 16x16 sprites on screen to simulate a framebuffer

The Neo Geo can display 380 sprites simultaneously. At 320x200 resolution, you would need 250 sprites just to cover the screen — leaving only 130 for enemies, weapons, and UI. The CPU would spend all its time converting frame data to sprite positions instead of running the game logic.

## The Verdict

Not impossible in the strict mathematical sense. But practically impossible: it would run at under 1 frame per second and require more sprites than the hardware can display. The Neo Geo is a magnificent machine — for what it was designed to do. 3D rendering is not that.

Why a Neo Geo Port of Doom Is Functionally Impossible: A Technical Deep Dive

// COMMENTS

ON THIS PAGE