Encounter: The Wireframe Arena and the Fear of Open Ground

Encounter! arrived simultaneously on the Atari 8-bit computers and the C64 in 1983, programmed by Paul Woakes, who co-founded Novagen Software specifically to publish it in the UK and Europe (Synapse Software handled North America). It’s usually filed under the shadow of Atari’s 1980 arcade coin-op Battlezone, and the comparison is fair as far as the premise goes — a lone armoured vehicle, a flat battlefield, enemies that appear one at a time and have to be picked off before the next wave arrives. Where the two games actually differ is the detail that gets flattened every time someone reaches for the word “wireframe” to describe either of them, and that detail is the whole reason Encounter still reads as a small technical marvel rather than a curiosity.

Not actually a wireframe

Battlezone rendered its tanks and obstacles as glowing vector line-drawings, an approach Encounter pointedly does not copy. Woakes built the game around large, sometimes screen-filling, scaled solid-colour bitmaps instead of line-drawn models, which meant the C64 and Atari 8-bit hardware could push objects toward the player at a pace vector-line rendering of the era simply couldn’t sustain. Contemporary write-ups have since described it as Battlezone running at what feels like several times the original’s speed, and that’s the more accurate way to hear the title of this piece: the arena reads as stripped-back and schematic, a bare plain with a scatter of solid shapes on it, but the starkness comes from a tight colour count and the absence of scenery, not from actual wireframe lines. The visual effect earns the word “wireframe” as a description of mood. It doesn’t earn it as a description of the rendering technique, and getting that distinction right matters for understanding what Woakes actually built.

Novagen’s own later games make the contrast sharper. Mercenary: the wireframe city you were allowed to leave — Woakes’ 1985 open-world game — did commit fully to genuine vector wireframe graphics for its city and landscape, arriving two years after Encounter had already proven that a first-person 3D battlefield could run convincingly on the same hardware using an entirely different graphical approach. The lineage runs from Battlezone’s wireframe original, through Encounter’s solid-colour reinterpretation at speed, to Mercenary’s eventual return to true wireframe for an open world rather than a single arena — three different solutions to the same underlying problem of rendering a 3D space on an 8-bit machine, from the same programmer’s hand across five years.

Why the open ground is the threat

The design brief of Encounter is close to the purest expression of a single idea in the whole early-eighties first-person shooter lineage: you are exposed, on a flat plain, and the enemies — saucers and kamikaze drones, tracked on a radar display beneath the main view, with a counter showing how many remain before the level clears — can approach from any direction at once. Scattered pillars offer the only cover on the map, and using them well means constantly re-evaluating where the next threat is likely to come from rather than committing to a single defensive position and holding it.

That’s a genuinely different tension from a corridor shooter, where the direction of danger is dictated by the level geometry and the player’s job is essentially reactive — face forward, deal with what the corridor sends. Encounter removes the corridor and leaves you accountable for the entire compass, which turns the empty plain itself into the source of dread rather than any single enemy on it. An empty horizon in a game with walls means safety. An empty horizon in Encounter means you don’t yet know where the next saucer is coming from, and the radar becomes the object you’re actually watching more than the horizon itself, because the radar is the only part of the interface that tells you where “open” stops being safe.

Speed as the actual innovation

What made Encounter land as a technical marvel on release, rather than a slower reinterpretation of an already-existing idea, is the sheer velocity Woakes extracted from 8-bit hardware for scaling and moving large solid shapes across the screen in real time. Battlezone’s arcade cabinet had dedicated vector-display hardware built specifically for the job of drawing lines fast. Woakes was working with general-purpose home-computer silicon and no dedicated graphics coprocessor to lean on, and the game’s reputation — a four-out-of-five score from Your Commodore, praise for both the difficulty and the sound design — rests substantially on how fast the whole apparatus moved compared to anything else attempting first-person 3D on the same class of machine that year.

Three difficulty settings meant the speed and aggression of the encounters could be tuned, which is a small detail worth noting because it suggests the design team understood exactly how demanding the core loop was and built in a release valve for players who wanted the atmosphere without the reflexes to match the hardest setting. That’s a more considered piece of difficulty design than plenty of contemporaries bothered with, at a time when “insert more coins” was still the default assumption most home-computer conversions inherited from their arcade sources without adjustment.

Two platforms, two audiences

The Atari 8-bit version charted higher and stayed on sales charts longer than the C64 release, while the C64 version reportedly did especially well in the German market specifically — a reminder that a single game’s reputation can diverge sharply by territory and platform, shaped as much by each region’s existing hardware installed base and distribution deals as by anything different in the software itself. Both versions were also picked up by Atlantis Software for a later reissue as a budget cassette title, which extended the game’s shelf life to an audience who’d missed the original full-price release. A 1991 Amiga and Atari ST conversion arrived years later, long after the design’s novelty had been absorbed into a decade of first-person shooters that took the fast, corridor-free arena for granted; contemporary coverage of that later port was notably cooler than the original’s reception had been, which tracks — the trick had already been done, and done first, on hardware with far less to spare.

The dedicated board problem

Arcade cabinets of Battlezone’s generation could afford to build a display around the specific job of drawing vector lines quickly, because the economics of a coin-op let a manufacturer design bespoke hardware for one game and recoup the cost a coin at a time over years in arcades. Home computers never had that luxury. A C64 or Atari 8-bit machine sold to run any software a publisher cared to write for it, which meant Woakes had to find a way to fake the impression of the arcade experience using general-purpose sprite and colour hardware never designed with a first-person 3D battlefield in mind. The arcade conversion problem: eight bits against a dedicated board covers this asymmetry in more depth, and Encounter is an unusually clean case study inside it — not a conversion of Battlezone at all, technically, but an original game solving the same design problem the arcade cabinet had already solved with purpose-built silicon, using considerably humbler tools and arriving at a faster, more aggressive result rather than a diminished one.

That’s a rarer outcome than the conversion history of the era generally offers. Most home-computer takes on an arcade idea in 1983 came out slower, sparser and less confident than their coin-op inspiration, constrained by exactly the hardware gap described above. Encounter inverted the usual outcome by refusing to attempt a literal conversion in the first place, choosing instead to solve the same design brief with a different graphical technique better suited to the silicon actually available. The result is a game whose relationship to its inspiration is closer to a rival answer than a tribute act.

Sound as more than atmosphere

The audio design deserves more credit than it usually gets in retrospectives that focus purely on the visual speed. Your Commodore’s four-out-of-five review singled the sound out specifically alongside the difficulty, rather than treating it as a footnote to the graphics, and on a machine where the visual field is otherwise a mostly empty plain with a handful of solid shapes on it, audio carries more of the tension than it would in a busier-looking game. An empty screen with a threatening soundscape underneath it reads as far more dangerous than an empty screen alone, and that’s a genuinely period-appropriate piece of design thinking for a machine whose sound chip was, in the C64’s case specifically, considerably more capable than its graphics hardware.

What actually plays now

Emulated Atari 8-bit and C64 versions both run cleanly, and either is worth trying to get a sense of how the same core design landed differently depending on the underlying hardware’s sprite-handling quirks. Go in expecting a single-arena survival test rather than anything resembling a campaign with distinct stages — the whole design is one idea, executed at a velocity that was genuinely startling for 1983, and it’s worth playing with that historical context in mind rather than judging it against decades of first-person shooters that inherited the same open-arena tension and built entire genres on top of it.

What Woakes took forward

Novagen was a small operation — Woakes founded it with Bruce Jordan specifically as a vehicle for turning his own programming projects into something publishable, rather than as a studio built to commission work from outside teams. That structure meant Encounter’s lessons about scaling large solid objects at speed travelled directly into Woakes’ next major project rather than being handed off to a different team who’d have to relearn them from scratch. Mercenary’s open, explorable landscape two years later owes a debt to the confidence Encounter built up in a single programmer’s ability to push 8-bit hardware past what the rest of the market assumed was possible, even though the later game gambled on wireframe rendering instead of solid shapes to achieve a different kind of scale — a whole city and a wider world, rather than one dense, fast arena. Two different technical answers, from the same hand, aimed at two different design problems.

Spoilers below

The hardest stretch on the higher difficulty settings comes from kamikaze drones arriving from a bearing the radar has just cleared, punishing a player who’s stopped scanning because the previous wave seemed handled — the game’s real cruelty is teaching you to trust a moment of quiet on the radar and then breaking that trust the instant you relax into it. Using the scattered pillars purely as static cover rather than as a route to reposition toward whichever quadrant the radar is lighting up tends to end a run quickly, because a fixed position eventually gets surrounded from an angle no single piece of cover protects against.