Antique Code Show Back in the early- to mid-1990s, the Mac wasn't considered much cop as a games platform. Sure, it had a sexier GUI than Windows boxes, but they could drop out into DOS and dedicate their CPUs' few tens of megahertz to games. Not so the Mac.
But that didn't stop coders from trying to make the most out the Mac. Early groundbreakers like Spectre and the original Prince of Persia showed the Mac could be a good games machine. But it was Bungie Software, the company that would go on to achieve world fame for the Halo series, to put Mac gaming on the map with the platform's first fast first-person shooter, the sci-fi epic, Marathon.
Marathon 1: too few CPU cycles for a bigger screen, unless you were willing to play HUD-less
Just as iD's Doom evolved out of the more basic Wolfenstein, Marathon built on Bungie's slower, more adventure-like FPS Pathways into Darkness. Running on the Motorola 680x0, Pathways could never deliver a Doom-like experience, but with the arrival of the PowerPC chip, Marathon could and did.
And it contained some impressive tech. iD's pioneering shooter didn't let you look up or down, but Heretic, a sword-and-sorcery shooter based on the Doom engine did. But it looked wrong.
Marathon 2:Durandal looked rather better
Marathon got the angles right by implementing perspective correction, though it took the game's sequel, Marathon 2: Durandal to fill the screen sufficiently to make this feature stand out. But the realistic physics model could be appreciated in the original, especially in the low-gravity environment of alien starships.
Marathon's sequels got realistic, literally immersive liquids at a time when the best rival titles could offer is a splash sound effect. Water, lava and slime rose and fell rhythmically, controlled by the same sine wave generator that powered the Marathon's dynamic, per-surface lighting.
The Marathon 2 engine added oscillating liquids
The trouble was, the Mac OS imposed a performance penalty that didn't hinder DOS-running PCs. That's why Marathon debuted with more HUD than viewscreen, leaving the player peering into a window. You could play full-screen, but it was slow and you were left HUD-less. Fortunately, Marathon 2, with an engine tuned specifically for the then-new PowerPC processors, was able to open this out into a full-screen vista the following year.
Still, even peering into a 320 x 240 window within the bigger HUD meant that objects didn't blur into a pixellated mess the way they often did in Doom, and while Marathon's gameplay was nominally of the same 'open door, kill monsters, find key, open next door' element, Bungie spruced it up with a proper storyline that evolved as you played the game.
Pfhor what we are about to receive...
Don't get me wrong: the events weren't shaped by your actions. The story didn't veer off in a different direction because you took too long to complete a certain level. But in an era when a typical game's storyline amounted to a couple of lines on the back of the box or the manual, Marathon was a tale that became more convoluted - and not the one you through it was at the start - as you played.
Marathon's mechanism for conveying events beyond the player's immediate vicinity were the ship's computer terminals. Tapping into the half-dozen or so in each level revealed not only mission details, but engendered a real sense that you were not necessarily at the centre of the action.
Terminal madness: Durandal's bid for freedom revealed
The rape of the colony ship was taking place at many, many locations. Worse, it was being orchestrated by one of the vessel's own on-board AIs.
Poor Durandal. With an IQ in advance of any organic entity on the ship, he was left… operating the ship's doors and airlocks. No wonder he rebelled.