Contents

Pitstop II: The Split Screen and the Pit Crew

Epyx's 1984 racer made tyre wear part of the race and gave two players a screen each to prove it

Contents

Most racing games on the Commodore 64 in 1984 were about one thing: staying on the road. Epyx’s Pitstop II was about that too, but it also asked a question none of its contemporaries bothered with — what happens to your tyres while you’re doing it — and then had the nerve to split the screen in half so a second player could be asking the same question at the same time, on the same track, in real time.

Two full race tracks, simultaneously, on a 1MHz machine

Advertisement

The split-screen mode is the thing to understand first, because it’s the part that shouldn’t have been possible on the hardware. Two players race the same course side by side, each getting a genuine scrolling first-person racing view rather than a scaled-down afterthought, with both simulations running in lockstep on a machine clocked at roughly one megahertz. Getting two independent, smoothly-scrolling road perspectives out of a Commodore 64 without either view chugging or the two races drifting out of sync was a serious technical achievement for 1984, and it’s the reason Pitstop II became a fixture of split-screen multiplayer on the format rather than a novelty that got tried once and abandoned.

What that technical feat buys, in play, is something simpler than the engineering behind it: an actual race, rather than a leaderboard comparison. Trading position with a friend who’s visibly two car-lengths behind on the other half of the screen, watching them pit at the same moment you do, reading their tyre choice off their lap times — none of that works if the two races are staggered turns or asynchronous scores. Pitstop II’s split screen made head-to-head racing a shared, simultaneous experience on a home computer years before that was a given.

The pit stop is a decision, not a cutscene

The feature the sequel is actually named for is the pit lane, and it’s built as a genuine risk-reward decision rather than an automatic checkpoint. Tyres wear down over the course of a race, visibly affecting how the car handles on corners — a worn tyre loses grip and makes cornering markedly less forgiving, which punishes a player who ignores the mechanic long before it becomes catastrophic. Pit too early and you lose time you didn’t need to lose; pit too late and a blown tyre or a spin costs you far more than the stop would have. The pit lane itself asks you to steer the car into a garage bay and stop within a marked box, and a poorly-judged entry costs additional seconds before the crew can start working — so even the pit stop, the ostensibly safe part of the lap, has a small skill test attached to it rather than being a menu you open and wait through.

That’s a meaningfully different idea from the arcade racers Pitstop II was competing with, most of which treated a race as a pure reflex test against the road and nothing else. Epyx’s insight was that a race has a resource underneath it — the car’s own condition — and that managing that resource under time pressure is just as legitimate a source of tension as the steering itself. It’s the same principle behind Epyx’s other Games-branded titles’ insistence on a real skill underneath a sports theme, discussed in the piece on Winter Games and the ski jump and in California Games’ treatment of sport as attitude rather than pure scorekeeping — a genuine mechanical decision standing in for what a lesser sports game would have left as pure timing or luck.

Reading tyre wear without a number on screen

Advertisement

Pitstop II doesn’t hand you a tyre percentage readout ticking down in the corner of the screen. Wear is communicated through handling — a car that drifts wider on a corner it took cleanly two laps earlier, a rear end that steps out under braking it didn’t step out under before — which forces the player to build an internal model of the car’s condition from feel rather than reading it off a UI element. That’s a harder design problem to get right than a numeric gauge, because it depends on the handling model being consistent and legible enough that a human can actually track a gradual change against their own memory of how the car used to feel. When it works, as it does here, it produces a much stronger sense that the car is a real object degrading in real time, rather than a bar quietly draining in a corner you’re not looking at.

The fuel gauge that turns strategy into arithmetic

Fuel adds a second resource on top of tyre wear, and the two interact: a driver managing both has to weigh whether a pit stop is worth taking for fuel alone when the tyres still have life left, or whether to push the tyres a little further because the tank can’t be topped up again before the laps run out. That interaction is what elevates Pitstop II above a game that merely bolted a single management mechanic onto a racer — the pit-stop decision isn’t “when do I need new tyres,” it’s a small piece of race strategy that has to account for two depleting resources on independent timers, worked out under the actual pressure of a car in front of you pulling away.

What the first Pitstop didn’t have

Epyx’s original Pitstop, released the year before, established the basic shape: a first-person scrolling road, a car that could be steered into a garage for fresh tyres, a sense that the pit lane existed at all rather than racing being pure point-to-point driving. What it didn’t have was the split-screen simultaneous multiplayer, and its resource management was shallower — a single, cruder read on tyre condition rather than the two interacting gauges of tyres and fuel that the sequel builds its late-race decisions around. Pitstop II is a sequel in the useful sense: it kept the part of the original that worked and rebuilt the parts that didn’t, rather than just adding a number to the title and reselling the same track set. That’s a rarer discipline in early-80s sequels than it sounds — a lot of Year Two follow-ups on 8-bit hardware were content to ship new levels on an unchanged engine, and Epyx instead used the second attempt to fix the actual structural gap in the first game’s central idea.

The split screen’s afterlife

It’s worth tracing where the split-screen idea went from here, because Pitstop II’s simultaneous two-player racing view predates the feature becoming an expected default in console racing and kart games. The core technical problem — rendering two independent, correctly-scaled, smoothly moving perspective views on the same hardware pass without either one stealing so much of the machine’s attention that the other stutters — is the same problem every subsequent split-screen racer has had to solve, just with more cycles and more memory to throw at it. Pitstop II didn’t invent the concept of two people racing on one screen, but it’s a rare and early case of a home-computer racing game treating that as worth the very real engineering cost on hardware that had almost nothing to spare, rather than settling for the cheaper option of alternating single-player turns and comparing times afterward.

Why the pit lane became a genre fixture

It’s easy to take pit stops for granted now — they’re a standard feature of virtually every serious racing simulation released since — but Pitstop II is doing this in 1984, on 8-bit hardware, years before racing games generally modelled tyre degradation as anything more than a cosmetic detail. The decision to make the pit lane an active, skill-tested part of the race rather than a passive checkpoint is the part of the design that proved durable; strip away the sprite graphics and the specific handling model and what’s left is a structure — race, manage a depleting resource, choose your moment, execute a small skill check to cash it in — that every modern racing sim with tyre wear and fuel strategy is still running, whether or not its designers ever played the Epyx original.

Racing the computer instead of a friend

Pitstop II is still a functioning single-player game if there’s no second racer available, with computer-controlled cars filling out the field against the clock and the road. The tyre and fuel management doesn’t relax in this mode — a solo racer has to run the same resource calculations a two-player match demands, just without a rival’s split-screen car to read tells off. If anything, the single-player game is where the resource management is easiest to appreciate in isolation, because there’s no temptation to let a good corner against a friend distract from the fact that the rear tyres have quietly lost half their grip since the last pit window. It’s a weaker experience than the split-screen mode Epyx clearly built the game around, but it’s not a lesser version of the same design — the mechanical decisions are identical either way.

Where to play it

Pitstop II runs well in any C64 emulator today, and it’s worth trying specifically in its intended two-player split-screen mode if you can find a second controller and a friend willing to sit close enough to a CRT — or an emulator front-end that supports split keyboard input — because the solo game, while a perfectly sound tyre-management racer on its own, is only telling you half of what made this one stand out from its 1984 field.

Spoilers below

There’s no story to spoil in a racing game, but one structural note worth flagging for anyone planning to learn the track blind: later courses in Pitstop II introduce tighter corner sequences back-to-back with minimal straight recovery time between them, which punishes a tyre-wear strategy that worked fine on the earlier, more open tracks. A pit strategy tuned to lap one won’t necessarily survive to the final course unchanged, and part of the game’s later challenge is realising that and adjusting rather than assuming the opening tracks taught you the whole system.

Advertisement
Advertisement
Jay
Written by Jay

vo.rs's games critic. Jay covers the medium as a system rather than a spectacle — this month's release, the indie nobody bought, and the Amiga game it's quietly descended from — asking what a mechanic makes you feel and why the loop holds. Learned to wait through a C64 tape load, never stopped playing since, and still finishes the odd 60-hour RPG out of spite. Expect argued verdicts, no score ever, spoilers below the line, and a running list of older games worth your weekend.