Rescue on Fractalus: The Fractals and the Jump Scare

Lucasfilm Games opened its account in 1985 with two titles, and the one that mattered was the one with mathematics in the engine room. Rescue on Fractalus! shipped for the Atari 8-bit family and the Commodore 64, published by Epyx in the United States and Activision in Europe, out of the group Peter Langston had assembled at Lucasfilm’s computer division. David Fox led the design. The fractal terrain algorithms came from the same building that was inventing modern computer graphics — Loren Carpenter’s fractal work was already famous inside the industry for the Genesis sequence in Star Trek II. Charlie Kellner handled the Commodore 64 version.

The internal codename was Behind Jaggi Lines!, which is a joke about the aliens you’re up against and a joke about aliasing at the same time, and it tells you exactly what kind of room this was built in.

What the fractals actually bought

The claim on the box was a planet. The reality is more interesting than the claim. Fractalus does not store a landscape. It generates one, mountain by mountain, using recursive subdivision — take a line, displace its midpoint by a random amount scaled to its length, repeat — which produces ridgelines with the statistical roughness of real mountains at every zoom level. The technique costs almost no memory and a great deal of arithmetic, and in 1985 the arithmetic budget on a 6502 running at roughly one megahertz was the entire problem.

So Fractalus is slow. Let me say that plainly, because forty years of reverence has sanded it down. The frame rate is bad. The terrain lurches toward you in visible steps and the horizon redraws in bands. What it is doing while it lurches is computing an infinite, coherent, three-dimensional world in which you can fly in any direction and find a real valley, and no cartridge on the shelf next to it could do that at any speed.

This is the same argument Elite was making on the same hardware in the same eighteen months, from the other side. Braben and Bell used a seeded generator to produce eight galaxies of planets that were never stored anywhere, spending arithmetic to buy content. Fox’s team spent arithmetic to buy space — the sense that the ground continues past the frame because it is genuinely being derived rather than scrolled. Both games are early proofs of the same proposition: on a machine with 64 kilobytes, an algorithm is worth more than an asset. Every open world since has been settling that bill.

The loop, and why it works

The mission is small and repeats. You fly a Valkyrie fighter over a hostile planet looking for the wreckage of downed pilots. Your long-range scanner points you at one. You fly there, you land near the wreck, and then you do something almost no action game asks: you cut your engines.

That single instruction carries the whole design. With the engines running the pilot will not approach. So you power down, and you sit in the dark on an alien mountainside with your only defence switched off, and you wait, and you watch a small figure walk across the terrain toward your ship. The wait is maybe ten seconds. The game has removed your verbs and given you a window and a noise. When the pilot reaches you there’s a knock, you open the airlock, and you have them.

Then you take off, and the fear evaporates into flying again — gun emplacements below, saucers above, a fuel gauge, a shield. The rhythm is tension, release, tension, release. The night levels take the release away by taking the horizon away: your searchlights carve a little cone out of the black and the mountains are where they always were, unseen. Fifteen levels of escalating difficulty stack up behind that loop, and the loop is strong enough to carry them.

The knock

Here is the thing everybody knows, and it is worth understanding as design rather than as anecdote.

Sometimes the figure walking toward your ship is not a pilot. It is one of the Jaggi. It reaches your ship, and instead of knocking, it smashes through the canopy at your face, accompanied by a shriek — and on the Atari version the screen flashes and the game is over. The sequence appears without warning, and its placement is exquisite: at the precise moment the game has instructed you to disarm yourself and stare at the glass.

I have to be honest about what makes this land, because “1985 game has jump scare” undersells the craft. Three things are doing the work. First, the game trained you: by the time it happens you have executed the land-and-wait ritual a dozen times and it has always been safe, so the ritual has become boring, and boredom is the raw material of a scare. Second, you cannot act. The engines are off. The scare arrives inside a state the game itself told you to enter. Third — and this is the bit that gets forgotten — it is diegetic. The alien is at the window because the window is where a rescued pilot would be. Nothing about the framing cheats.

The story of the team’s own reaction is part of the public record of the era: the sequence was tested on the people who made it and it got them, and it survived into the shipped game specifically because it worked on an audience who knew the code. That’s a rare thing. A scare that lands on its own authors is a scare with real structure underneath it.

Modern horror has spent forty years relearning this. The most durable version of the trick is the one where the game makes safety into a routine and then charges you for the routine — the reason a piece like Signalis can still frighten people who have seen everything is that it understands the same grammar: the fear lives in the interval before anything happens, and the interval has to be one the player chose to enter.

The engine had a second life

The fractal work was not a one-off stunt, which is the strongest evidence that Lucasfilm knew what it had built. Ballblazer shipped alongside Fractalus in 1985 — a split-screen future-sport played on a flat, infinite grid at a frame rate that still astonishes people who check what hardware it was running on. Then came Koronis Rift and The Eidolon later the same year, both leaning on the same terrain-and-perspective technology, both handed to different designers to see what else it could hold. Koronis Rift put you in a rover on fractal hills, scavenging technology off derelict hulks and slotting it into your own vehicle. The Eidolon took the renderer underground into caves full of fireball-throwing creatures.

Four games, one engine, one year, four genuinely different design questions asked of it. That is a company treating its technology as an instrument rather than a demo. The obvious comparison is what Andrew Braybrook did in the same period on the C64 — build a system, then find out what it means — and the reason Paradroid and Fractalus sit on the same shelf in my head is that both came from people who could not stop interrogating their own code.

It is also the moment Lucasfilm Games stopped being a corporate curiosity. The division existed because George Lucas wanted the computer graphics group to pay for itself and had no interest in licensing Star Wars to it — which is why the first four games have nothing to do with the films, and why they are as strange as they are. That constraint, which looked like a handicap, is the entire reason Fractalus exists. A studio told to make Star Wars games in 1984 does not spend its first year proving out midpoint displacement on a 6502.

The verdict, argued

Fractalus is a game I admire more than I return to, and I’d rather say that than pretend otherwise. The flight model is functional. The combat is thin. The mission structure is a checklist and the difficulty scaling is mostly “more of the same, faster and darker”. Played for an hour today, with no memory of 1985 attached to it, it is a slow, brown, repetitive thing.

What survives is the argument. Fox and his team took the most expensive graphics research in the world at that moment and got it running on a home computer with less memory than a modern email signature, then had the sense to build one small, perfect piece of theatre on top of it. The fractals are why it’s in the history books. The knock is why it’s in people’s heads. Those are two different achievements and the second one is the harder of the two, because the second one required someone to notice that the interesting part of a rescue is the waiting.

Both C64 and Atari 8-bit versions are readily emulated and the Atari original runs noticeably better. Play the C64 one if the C64 is your machine and you want the version that had to fight for it; play the Atari one if you want to see what the team actually intended. Either way, fly the first few missions at night with the sound up. The landing ritual is the whole game, and it does its best work on a player who is bored by it.