RSS

Tag Archives: interplay

Realms of the Haunting

I like to imagine that Realms of the Haunting, Gremlin Interactive’s bizarre 1996 mélange of first-person shooter, point-and-click adventure, and interactive movie, was the brainchild of Ian and Nigel, students at Thomas Hughes Secondary School in Stow-on-the-Water.

Ian was sitting in a sheltered nook after school one day, sketching notes for a Call of Cthulhu scenario, when Nigel, the local football star, came barreling down the lane on his bicycle. Spotting his nerdy classmate, he dismounted in his customary way, by leaping off the still-moving bike, whose forward progress would have been arrested by Ian’s legs if he hadn’t swung them hastily aside. Nigel then joined his mode of transportation in marching up to see what Ian was up to, not without provoking some consternation from the latter, who wasn’t at all sure how this exchange was going to go. “What’cha up to, dude?”

Ian pushed his spectacles further up his nose. Even under the best of circumstances, he never quite knew how to respond to Nigel’s mix of Americanisms and Cockney, which he found almost incomprehensible at times. But he rallied. “Well, it’s sort of a scenario for a game…”

“A game? What kind of game?”

Call of Cthulhu. It’s sort of a horror game. You get together with some mates, and one of you is sort of the referee. The others are all investigators who learn about this creepy old mystery. First they find this old bunch of letters — letters between some sort of cultist and his girlfriend…” Ian trailed off. He could sense that this was already going horribly wrong.

But it appeared that Nigel had heard only the words “horror” and “girlfriend.” “Dude, I know what you mean!” he cried. “Like Duke Nukem! You know that one? You can shoot blokes in the head with a shotgun, and the blood goes everywhere! And you meet strippers! You can pay’em to get out their titties for you.”

Ian did not know Duke Nukem. His father, a line engineer for British Telecom, was possessed of a streak of patriotism that precluded the purchase of any American personal computer. He insisted the family could get by perfectly well with their homegrown Acorn Archimedes, which advertised its stolid Britishness by means of its incompatibility with everything else. Still, Ian dearly wanted this conversation not to get onto the wrong track, so he nodded, whilst pushing his glasses up once again. “Yes… sort of…”

Any sign of hesitation was lost on Nigel. “Dude, we could work together on it!”

“Um, okay…”

“So, maybe you start in a haunted house — you’ve got to start somewhere, right? — but then it just keeps getting bigger and bigger! You find, like, one of those snakehole thingies and go to other dimensions and stuff, with wickeder and wickeder monsters to fight. And there’ll be a bunch of bosses to fight too. A bloke who’s dressed up like a doctor, like he wants to do human experimentation on you and all, and a creepy evil priest in sunglasses –”

“Wait… why sunglasses?”

“Why not?” shrugged Nigel. He was in the habit of dwelling on the abstract cool in life, not on the details.

Ian felt his blood stirring despite himself. Maybe he should think bigger for once. “Maybe you could sort of go to ancient Egypt,” he piped up cautiously. He’d always loved those ancient-archaelogy picture books his dad collected, so much so that he’d been begging for a trip to Egypt for years. “Just imagine the sort of interesting puzzles we could have around the pyramids…”

“Sure, sure, dude,” said Nigel. All things were possible in his world. “But it’s got to be bigger than that even, you know? I know… maybe in the end you’ve got to go right down into Hell and kill Satan! That would be awesome! I’m sure no one’s ever made a game where you’ve got to kill Satan.”

Again, his words set Ian thinking. They were reading Paradise Lost in his honors literature course this semester, and The Divine Comedy was waiting in the wings. And then he’d read this less respectable thing called The Holy Blood and the Holy Grail last summer. “We could sort of pull a lot of the story right out of the Bible and Milton and Dante,” he said. “Sort of build on them. Even have the Garden of Eden in there. And Knights Templar. You’ve always got to have Knights Templar.”

Nigel looked unusually pensive for a moment, so much so that Ian almost thought he was giving serious consideration to the advantages and pitfalls of building a new mythology on the scaffolding of older ones. But he was soon disabused of that notion. “We’re going to need a chick,” said Nigel contemplatively.

“Sure, alright,” said Ian. “She can be sort of your companion, who’ll know a lot more than you do about all the mythology, and can sort of help to explain…”

But again, Nigel had only caught a word or two. “Companion, what?” he leered. “I like the sound of that.”

“Say,” said Ian suddenly, “have you been in the computer lab lately?” When Nigel unsurprisingly shook his head no, he rushed on. “They’ve got this computer version of Connections there. Have you seen that one on the telly?” Another shake of the head. “It’s a show about how everything in history is interrelated –”

“Inter- what? Dude, what are you on about?”

Ian decided to elide further details. “Anyway, the point is that they put the host of the show right in the computer game. I mean, the real host. We could do the same — have real actors in the game.”

Nigel looked dubious. “How will that make it cooler?”

“Well, it would make it seem more real… sort of more believable with real people.” Nigel still looked doubtful. So Ian tried another tack. “Just think how cool all those bosses would look as real people, sort of like they’re in a real horror movie. And then to play your companion we can get a real chick,” he said, pronouncing the word as naturally as he could, like an earnest foreigner trying out his French on the natives.

Nigel was sold. “Right, then, we gotta have that too,” he said. “We’ll look like wankers if we don’t.”

And so it went. Through the sylvan afternoon, Ian and Nigel raised their castle in the air to ever loftier heights, adding battlements and wings and dungeons until the whole edifice teetered in the merest hint of a breeze. When they were finally winding down, Nigel got unexpectedly thoughtful again. “Maybe it’s a bit much,” he mused, expressing a sense of moderation which neither Ian nor any of the adults in his life had ever suspected might lurk within him. “Maybe you shouldn’t actually kill Satan after all…”

Ian nodded. They had gotten rather carried away, hadn’t they? Obviously they would have to rein things in a little. Or a lot.

“We’re gonna need some material for the sequel, right, mate?” Nigel grinned. “And anyway, we got to leave Marilyn Manson a Satan to sing about. Am I right, what?” he queried with a friendly fist jab.

Ian wasn’t sure whether he was right or not, but he could always see the wisdom in restraint; his whole life to date had been a study in it. “Okay, we have enough already without Satan. Maybe too much. But if it does get to be too much, we could always just sort of say it was all in someone’s imagination at the end, like in the last episode of St. Elsewhere.” That last reference spoke to how comfortable he was beginning to feel with his rambunctious design partner. His mother had an eccentric fondness for soapy American television which she’d imparted to her son, but normally he would die before sharing this passion with any of his peers.

Nigel was unfazed, if also uninterested. “Sure, dude. Truth.” He held out his hand for a fist bump, which Ian navigated with only a little awkwardness. It seemed they were now fast friends, but it was also time for Ian to get home for dinner; his mother did scold so when he was late. Nigel nodded his acquiescence, digging his bicycle out of the bushes where it had landed a couple of hours before. “Check you later, mate,” he said as he swung one leg over the saddle.

“Yes… mate” said Ian. “Our game’s going to be… awesome.” He smiled to himself as Nigel rode off into the sunset. He rather liked the feel of the word on his tongue.

One week later, the boys sent their design document to Gremlin Interactive.


Fair warning: this article spoils the “shocking” denouement of Realms of the Haunting as well as some other plot details.

Alas, the real origin story of Realms of the Haunting is somewhat more prosaic. The game’s individual pieces mark it as a thoroughgoing product of its time; it’s only their amalgamation in one place that makes it so bat-guano insane.

The project began when Gremlin Interactive joined three-quarters of the other games studios on the planet in beating the bushes for a DOOM-like 2.5D engine in the wake of that game’s extraordinary success. They wound up sourcing the “True3D” engine — which was actually no more true 3D than DOOM had been — from Tony Crowther, a legendary British games programmer whose career’s beginning predated Gremlin’s own 1984 founding. Crowther also offered Gremlin two ideas for a game to make with his engine. One was a “generic monster game,” as he puts it, while the other had a “devil theme.” Gremlin chose the latter. So far, so DOOM-like, in theme as well as technology.

But here’s where it starts to get weird. Gremlin, virtually alone among the many studios working with engines like this one, thought that theirs could be twisted to suit the needs of a puzzle-based adventure game instead of being strictly a vehicle for first-person carnage. And the odd thing is, they were kind of right. After production had already started on Realms of the Haunting, another team at Gremlin used the True3D engine to create a non-violent comedy adventure in the LucasArts tradition, to surprisingly good effect. Normality‘s ramshackle 2.5D visual aesthetic proved a good fit with its cock-eyed protagonist’s stoner-dude perspective on the world, while its puzzle design was as buttoned down as the rest of the affair was comfortably casual. Despite being started after Realms of the Haunting, it came out months before it in 1996. Unfortunately, it garnered few sales. One senses that, in addition to being confused by the look of the thing, gamers just didn’t quite get its jokes. Nor did it help that the market was flooded with bigger, more expensive adventures from American studios that year, the last in which the adventure genre was still widely perceived as one of the industry’s AAA standard bearers.

Through it all, the Realms project trundled on, determined to be both a kick-ass first-person shooter and a brain-tickling adventure game. Writer Paul Green wanted the story to be “epic.” And indeed, it just kept growing and growing. Then someone got the bright idea to jump on yet another indelibly mid-1990s trend: the “full-motion-video” game, incorporating clips of real actors filmed in front of green screens, which backgrounds were filled in after the fact with conventional computer graphics. Gremlin hired Bright Light Studios, an outside video-production house, to cast and carry out the shoots, then spent much time and money massaging the end results into their Frankenstein’s monster of a game. By the time it came out in Britain, about a week before the Christmas of 1996, Realms of the Haunting had spent a good two and a half years in development — one year longer than had been intended — and had become by far the most expensive game Gremlin had ever made.

Programmer Greg Staples, engine architect Tony Crowther, and writer and designer Paul Green.

And what did they get for their money? Oh, my… where to begin? With the beginning, I suppose…

The very first impression Realms of the Haunting gives is of reaches exceeding grasps, establishing a leitmotif that will persist throughout. It opens with an epigraph that’s attributed only to “anonymous”: “Goodness reflects the light and evil bears the seed of all darkness. These are mirrors of the soul, reflections of the mind. Choose well.” This reads like pieces of other, better epigraphs cut and pasted together into a meaningless word salad. Yet it actually serves its purpose of being a harbinger of what is to come in two separate ways. Realms of the Haunting itself will play like chunks of other, better games cut and pasted together. And everyone you meet in the game will talk just like that epigraph is written.

Next we have the bravura eight-minute opening movie, in which we meet our protagonist Adam Randall, in the back of a taxi on his way to answer a mysterious summons to a deserted house out in the middle of nowhere — a visit he’s decided to make in the middle of a dark and stormy night, of course, as you do in these situations. When I first heard Adam speak, I thought it strange that Gremlin had opted to cast an American actor in the role, given that the actual text of the script shows every indication he ought to be British; the summons to the haunted house came from a self-purported colleague of his recently deceased father, who we’re told was “the pastor in a Cornish village.” But then I started noticing oddities in Adam’s vowels and in his “Ts” that didn’t fit with an American accent either. In the end, I decided he must be Canadian. (Hey, at least that puts him inside the Commonwealth!) But then, after I was finished with the game, I watched Gremlin’s short “making of” video, and all became clear: the actor was a Brit putting on an American accent. But… why, especially when it doesn’t make any sense in the context of the plot? I can only conclude that Gremlin believed they’d have a better chance of cracking the all-important American market with an American-sounding protagonist — plot fidelity be damned. Anyway, not much else about the plot will wind up making much sense. Why should this?

The actor in question is one David Tuomi, who has managed the neat trick of leaving no digital footprint whatsoever in all the years since. It’s as if he was immaculately created just to play Adam Randall, then returned to the dust from which he had been made as soon as shooting wrapped. To this day, his profile on The Internet Movie Database has exactly one entry: Realms of the Haunting. He doesn’t even enjoy the cult celebrity of someone like Dean Erickson, whose acting résumé is almost as scanty and similar long-abandoned, but who still pops up to give an interview from time to time about that one time he got to play Gabriel Knight. No, David Tuomi is just… gone. It seems he took his right to be forgotten seriously.

This is made still weirder by the fact that he really isn’t that bad here. He may not be Laurence Olivier, but he’s a good-looking, likable young man who doesn’t palpitate with nervousness when he speaks his lines, which puts him well ahead of Dean Erickson and many of his other peers in the full-motion-video field. The problems with this game’s storytelling aren’t down to him.

In fact, for all of its haunted-house clichés, the opening movie as a whole strikes a pensive note that raises the hopes of a writerly type like me. The Adam we meet in the back of that taxi is haunted by metaphorical rather than literal demons; he’s filled with regrets about all of the things he never said to his father, all of the times he could have picked up the phone to call him but didn’t. This sense of guilt is joined by other, bitterer sentiments: “He was well-liked. Had time for everyone. Except his son.” (Those might just be the most cogent lines in a script with very few of them.) You can almost begin to believe that, like all the best classic horror, this story will really be about the fears and worries and secret shames that are part and parcel of being a human being, those occasional dark nights of the soul that keep even those of us who don’t believe in ghosts wide awake from time to time. But never fear, would-be demon blasters: the game will never strike a note like this one again, and Adam will never again betray any sign of having an inner life that goes beyond the exigencies of the moment.

Adam pays the taxi driver and enters the house. As he does so, the doors shut behind him with a crash, like the sealing of a tomb. He doesn’t so much as twitch in response to this event. On the one hand, this is a typical discordance of these sorts of productions: the David Tuomi acting in front of a green screen had no slamming doors to react to, because both the sight and the sound of them were painted in later. But it also establishes a precedent in another way. Adam will stumble through everything to come comically unfazed by it all. Even now, at the outset, he just shrugs as he wanders the corridors of a house with glowing pentagrams splashed over the walls and doors, portraits that blink at him with livid red eyes, a fly-encrusted suit of armor that appears to contain a human corpse, decapitated animal bodies strewn randomly about the place, and a typewriter that’s typing “We live!” over and over again of its own accord. Unflappable doesn’t begin to describe this guy. “A rat. No head,” he mutters to himself, and moves on. In the case of the typewriter, he confines his observations to, “Ink ribbon’s missing.” Right. Better buy a new one in the morning, once I’m through with all this tedious business of demon blasting. Which Adam will soon be doing with laconic aplomb, mowing through his enemies like Duke Nukem — until it’s time for a cut scene, at which point he reverts to being the slim, harmless-looking guy we met in the taxi.

Could this library look any more Lovecraftian?

The aforementioned demons show up only after you’ve solved a puzzle or two and found your way into the house’s library, that natural repository of secrets. In the best tradition of a Call of Cthulhu scenario, you find a clutch of 70-year-old letters between a cultist and his paramour, talking about some ominous ritual they’re attempting to enact. And, even more disconcertingly, you meet Adam’s father’s ghost, entwined in chains that make him look like a parody of Jacob Marley in A Christmas Carol.

Then you open the inevitable secret door that’s hidden behind the bookcase, and the first demon comes running at you. With head-snapping speed, we’ve gone from pensive psychological horror to Gothic horror to a vaguely Lovecraftian story to a B-grade zombie flick.

And so it will go for the next couple of dozen hours. The designers’ response to any and all suggestions seems to have been, “Sure! Put it in there!” Realms of the Haunting is a study in excess, a game that wants so very badly to be all things to all people, evincing all of the sweaty desperation in pursuit of that goal that Adam so noticeably fails to display. It just goes on and on and on and on. Most games that tell pre-scripted, set-piece stories have around four or five chapters; this one has twenty.

Sometimes, however, less is more. Perhaps more so than any other game I’ve played, Realms of the Haunting descends linearly in quality — in all measures of quality, from writing to production values to gameplay — as it unspools from beginning to end.

That said, the descent doesn’t happen at the same pace along these different vectors. It’s the story that goes off the rails first. The central problem here is all too typical in videogames: stakes inflation. It’s not enough for this to be a tale of a father and son’s sins and redemption, not even enough for the fate of a family or a town or even a nation to hinge on Adam’s actions. No, the fate of the entire world — no, make that the fate of the entire universe! — has to be borne on the fashionably padded shoulders of Adam Randall.

The flames of Hell are so bright, Florentine’s got to wear shades.

It soon becomes clear that Paul Green has no idea how storytelling works at the most fundamental level. Instead of giving us one central villain to hate, he dilutes the impact with a whole rogue’s gallery of weirdos whose relationships to one another are almost impossible to keep track of: the creepy priest who seems to have been modeled on Rasputin, the guy who runs around in a doctor’s outfit, the guy dressed up like he’s auditioning for a Sam Spade flick who’s always flipping through a deck of cards and giggling like a low-rent Joker. If this was a Nintendo-style level-based videogame, these folks might work as a series of bosses. But as an interactive story told primarily through about 90 minutes of live-action video, it never gives anybody enough screen time to make you care. It’s not a problem of the acting; like David Tuomi, all of the actors perform what’s being asked of them serviceably enough, intoning their lines like the Shakespearean creatures of the British theater scene they probably were. It’s a problem of the writing.

This fellow looks like an evil Tex Murphy.

Your allies are no better. Again, there’s just too many angels and archangels and God knows what else running around, all talking in symbolic gibberish that brings to mind the game’s horrid opening “quotation” and never telling you what you actually want to know. At one point, one of them apologizes for “speaking in metaphors” — which is hilarious because absolutely everybody in this game speaks in nothing but metaphors, and terrible mixed ones at that, until you want to pull out your big old shotgun, point it at their foreheads, and demand a straight fricking answer, for once. The would-be drama has a way of shooting its gravitas in the foot at every turn. Your guardian angel Hawk, for example, runs around in an artfully crumpled tee-shirt that makes him look like a model in a Gap circular. Another character, one who has something or other to do with the Knights Templar, is named “Aelf” — pronounced as far as I can tell just like “Alf,” which always sets me giggling to myself about cat-loving anthropomorphic aliens.

The character you spend the most time with is Rebecca, a fetching lass in a chic pantsuit more appropriate for a day behind a desk in the City than a night in a haunted house. (She’s played by one Emma Powell, who unlike David Tuomi went on to a long and fruitful career as a supporting and voice actress in movies, television, and videogames.) Our avatar of indifference Adam comes across her in the library at the end of Chapter 2, inexplicably just sitting there, and, true to form, never bothers to ask her how she ended up there. For the bulk of the game thereafter, she serves as his sounding board and advisor as he wanders about, offering hints and commentary on the environment and adding a little spark of life to what would otherwise be a decidedly lonely experience. In that sense, she’s not a bad addition at all.

Emma Powell and David Tuomi

Indeed, the gameplay generally declines less precipitously than the writing — with one caveat. That comes in form of the interface, which will first flabbergast you with its inscrutability and then annoy you like a dull foot ache for all the hours to come. Some of this game’s confusions for the modern player exist in many first-person shooters that came out between 1993 and 1998, including to some extent even (un-modded) DOOM itself. These were the years before the control schemes that have been the standard for the last quarter-century had quite stabilized.

Still, Realms of the Haunting‘s problems in this department extend well beyond the lack of mouse-look or the unfamiliar default key mappings. The adventuring interface is fiddly almost beyond belief; everything you try to do is ten times harder than it would be if you were doing it in real life. Using or examining an object entails pressing “I” to bring up the inventory screen, then finding its stamp-sized icon among the four separately sorted categories of junk you’re carrying: “general items,” “weapons,” “mysterious or magical items,” or “documents.” (No, it isn’t always immediately obvious what the game considers to belong in what category.) For some reason, all of this is allowed to fill no more than a quarter of the screen. So, if it’s a document you’re interested in reading, you get to do so by dragging it around inside a small window; it’s like reading a book through a telescope. If you want to try to use an object on something in the world, you first have to place it in Adam’s left hand — his left hand, mind you; the right is reserved for weapons — then exit the inventory system completely before you can click on the target. This is so annoyingly convoluted a process that I’m going to tarnish my cred as a hardcore adventurer by strongly suggesting that you play this game, if you choose to do so, in “easy” adventuring mode, where it automatically uses the correct object in the correct place, as long as you have it in your inventory. What’s truly bizarre about all this is that Normality, the other Gremlin game that was built with the True3D engine, has a fast, elegant popup radial menu for examining and using objects. What on earth were these developers thinking?

You can almost always tell whether the makers of any given game have given it to anyone to actually play before they released it. These ones most definitively did not, as evidenced by the constant unnecessary niggles. When you find a new key, for example, you never know where it will appear among the twenty others you’re already carrying around with you. Why not dispose of the ones that have already served their purpose?

Still, if you can get past the torturous interface, the first chapters, when you’re still exploring the house itself, acquit themselves fairly well. The shooting parts serve their purpose well enough, while the puzzling parts can be surprisingly satisfying, revolving mostly around finding keys that let you open up more and more of the house for exploration. Realms of the Haunting is at its best at this stage, just about making you believe that its chocolate-and-peanut-butter combination of genres has something to recommend it after all. And, while I would by no means call it scary in a “I don’t want to play this alone” kind of way, its aesthetic does qualify as enjoyably creepy.

It’s only after you leave the house to start dimension-hopping about seven chapters in that things begin to fall apart on the gameplay front as well. An engine that can portray shadowy hallways to fairly good effect is less suited to conveying the splendor of ancient Egypt, the beauty of the Garden of Eden (yes, you really do travel there), or the horrors of Hell (yes, you really do travel there as well). All of these environments are much bigger, sprawling places than the house, with unfortunately less inside of them to see and do, a sure sign that constraints of budget and time were catching up with the designers’ ambitions. Even the normal spaces become hard to find your way around in; you are provided with helpful maps of most of them, but consulting them involves scrolling them around in that absurd little inventory window, a process so excruciating that you won’t want to bother until you’re truly at wit’s end. And then there are the deliberate mazes… oh, Lord, save us from the mazes in this game, which are scarier than any of its demons. There are three of them, extended, hair-pulling monstrosities all.

The game gives you maps of most of the larger areas, which is very kind and progressive of it. But then it makes you peer at them through a pointlessly tiny window. And every time you bring a map up again, it resets the view to the top left. The cruel irony here is that the full document seems very close to the size of your monitor screen. This is not rocket science, Gremlin.

As the game wears on, the puzzles become increasingly surreal, to say the least. For example, you run through one of the mazes collecting little brains to shove into a giant brain machine, apropos of nothing that comes before or after. And you’ll spend an inordinate amount of time constructing a bong so one of the angelic beings you meet can toke up properly. (I assume that all of the obvious jokes about what the folks at Gremlin were doing when they made this game have already been told, so I won’t bother.) If you’ve made it this far without ragequitting, you must long since have adopted Adam’s attitude. Just shrug your shoulders and go with it.

It gradually becomes clear that significant chunks of the story are simply missing in action, presumably due to budget shortfalls or space limitations; Realms of the Haunting shipped on four CDs as it was. At one point, Adam and Rebecca stand on the verge of a dramatic showdown with one of the ceaselessly rotating lazy Susan of villains. After everyone has engaged in the usual speechifying that precedes such things, the screen fades to black, a scream sounds, and you flex your mouse hand and get ready for battle… and suddenly Adam is in a prison cell, while Rebecca has somehow escaped and is trying to rescue him from outside the door. The game never explains how any of this happened. Just go with it.

At long last, you get to the very end and save the universe/multiverse/whatever. And then… you join a straitjacketed Adam in a mental hospital, as he finishes telling his tale to a skeptical doctor and a nurse with a syringe at the ready. Oh, my. You can almost hear the writers slapping one another on the back for being so clever. At least now we know why one of the villains was dressed up like a doctor. And perhaps, come to think of it, why we’ve never heard another peep from David Tuomi…

The dominant impression Realms of the Haunting leaves you with is that of bits that don’t fit together. This applies as much at the most granular levels of detail — as in the way that Adam’s reactions never quite seem to be in line with what is actually happening to him — as it is in the big picture. Rebecca, for instance, shows up in the movie bits, and is on-hand to offer commentary in the adventure-game bits, but simply doesn’t exist in the shooter bits. Likewise, we never see the veritable Fort Knox of weaponry Adam is carrying around with him when we see David Tuomi portraying him in the movie bits. Of course, Realms of the Haunting is hardly the first or the last game to hand-wave away inconvenient details like these. If it succeeded on at least one of its three levels — whether as a shooter, a puzzle-driven adventure game, or a well-scripted interactive movie — I’d be more inclined to overlook such inconsistencies. As it is, though, it’s failing everywhere by the time you make it halfway through: the shooter bits have become samey and janky, the adventure bits samey and illogical, the story samey and flat-out incomprehensible. This game is the inversion of the reviewer’s cliché about the creation under review being “more than the sum of its parts.” As bad as these parts are, the whole manages to be less than their sum. Every part of the game actively diminishes every other part.

And yet as hot messes go, this one is as intriguing as they come. Whatever else you can say about Realms of the Haunting, there’s never been another game like it. It’s amazing to think that a purportedly responsible management team ever approved such an outlandish monstrosity as this one. In fact, there’s a melancholy aspect to that: long shot that it was to get made even in 1996, it’s even harder to imagine this game appearing any later in the decade. For as gaming moved into the last third of the 1990s, genres were calcifying into fixed categories with inviolate sets of expectations. Soon absolutely no one would be taking fliers on crazy cross-genre experiments like this one anymore.

To know why, we need only look to Realms of the Haunting‘s commercial performance. Its British release date was not ideal, coming too late to reap the proper benefit of the Christmas buying season. And the circumstances of its American release, in the dog days of March of 1997 under the imprint of an unenthusiastic Interplay Entertainment, were no more auspicious. Yet a game with true mass appeal can overcome such factors — as, for example, Diablo did when it was shipped to American stores between the Christmas and New Years of 1996. Unfortunately, Realms of the Haunting was the antithesis of Diablo, being as clunky, fiddly, and scattered as Blizzard’s juggernaut was frictionless, polished, and laser-targeted. As Computer Gaming World put it in an (overly) generous 4.5 star review, Gremlin’s game had natural appeal to “action gamers looking for some adventure” and “adventure gamers looking for some action.” But just how many people meeting these descriptions were there? Not very many at all, it would appear. Realms of the Haunting was dead on arrival, selling less than 500 units in its first week on the market in Britain. Its high cost combined with its abject commercial failure had much to do with Gremlin’s subsequent collapse, which resulted in the company being bought out by the burgeoning French giant Infogrames in 1999.

Even today, however, some of the delusions of grandeur that allowed this game to be made still persist. Steve McKevitt, Gremlin’s former communications chief, blames its failure on “a backlash against full-motion video.” He claims that the developers “got just about everything right: the script, subject matter, story line, pacing. It was years ahead of its time. More The Last of Us than Quake.” Uh, no, Steve. Just no.

Yet, easy though it is to make fun of, Realms of the Haunting is a hard game to totally hate. It’s just so earnest in pursuit of its lofty ambitions, so fixated on being epic, man. How can you hate something that’s trying this hard to be the best game ever? Chalk it up as a last artifact of an older games industry that frequently had more vision than competence, of a time when budgets were small enough to take a chance on something crazy and just see what happened. In the years to come, both of those equations would be reversed. The result would be tighter, more polished experiences, but very few games that dared to throw out all the rules, whether wisely or unwisely. Instead of logical shorthands to bracket discussions, genres would begin to look like the straitjacket Adam Randall is wearing when we catch our last glimpse of him.

And it’s for that reason really that I’ve chosen to write about this game, even though I’m not at all in the habit of writing about bad games that didn’t sell well and didn’t have much influence on the field. There’s something kind of beautiful about Realms of the Haunting‘s passionate incompetence. I’m not usually an adherent of the “so bad it’s good” school of criticism, but I can almost make an exception in the case of this game. Many critics before me have argued that it would have been a far better game if it had been content to stay inside the haunted mansion and leave off with the apocalyptic fever dreams. They’re almost certainly right, but at the same time I’m not sure I would be talking about it today had anyone involved with it understood the virtues of restraint. Realms of the Haunting is a final holdover from a messier, more freewheeling time, when everyone was still making it all up as they went along. And so, having paid our last respects to the old ways, we can now march onward, into a future that could never give us anything as amateurish, ill-considered, excessive, and lovable as this.



Did you enjoy this article? If so, please think about pitching in to help me make many more like it. You can pledge any amount you like.


(Sources: the book A Gremlin in the Works by Mark James Hardisty; Retro Gamer 24 and 108; Computer Gaming World of January 1997 and May 1997; Edge of July 1996; PC Format of December 1996; PC Power of December 1996. Online sources include Sascha Kimmel’s Realms of the Haunting fan site, Jdanddiet’s interview with the aforementioned Sascha Kimmel, Retro Video Gamer‘s interview with Tony Crowther, and a retrospective of the game at The Genesis Temple.

Realms of the Haunting is available as a digital download from GOG.com.)

 
 

Tags: , ,

Normality

Sometimes these articles come from the strangest places. When I was writing a little while back about The Pandora Directive, the second of the Tex Murphy interactive movies, I lavished with praise its use of a free-roaming first-person 3D perspective, claiming in the process that “first-person 3D otherwise existed only in the form of action-oriented shooters and static, node-based, pre-rendered Myst clones.” Such a blanket statement is just begging to be contradicted, and you folks didn’t disappoint. Our tireless fact-checker Aula rightly noted that I’d forgotten a whole family of action-CRPGs which followed in the wake of Ultima Underworld (another game I’d earlier lavished with praise, as it happened). And, more pertinently for our subject of today, Sarah Walker informed me that “Gremlin’s Normality was an early 1996 point-and-clicker using a DOOM-style engine.”

I must confess that I’d never even heard of Normality at that point, but Sarah’s description of it made me very interested in checking it out. What I found upon doing so was an amiable little game that feels somehow less earthshaking than its innovative technical approach might lead one to expect, but that I nevertheless enjoyed very much. So, I decided to write about it today, as both an example of a road largely not taken in traditional adventure games and as one of those hidden gems that can still surprise even me, a man who dares to don the mantle of an expert in the niche field of interactive narratives of the past.



The story of Normality‘s creation is only a tiny part of the larger story of Gremlin Interactive, the British company responsible for it, which was founded under the name of Gremlin Graphics in 1984 by Ian Stewart and Kevin Norburn, the proprietors of a Sheffield software shop. Impressed by the coding talents of the teenagers who flocked around their store’s demo machines every afternoon and weekend, one-upping one another with ever more audacious feats of programming derring-do, Stewart and Norburn conceived Gremlin as a vehicle for bringing these lads’ inventions to the world. The company’s name became iconic among European owners of Sinclair Spectrums and Commodore 64s, thanks to colorfully cartoony and deviously clever platformers and other types of action games: the Monty Mole series, Thing on a Spring, Bounder, Switchblade, just to name few. When the 1980s came to an end and the 8-bit machines gave way to the Commodore Amiga, MS-DOS, and the new 16-bit consoles, Gremlin navigated the transition reasonably well, keeping their old aesthetic alive through games like Zool whilst also branching out in new directions, such as a groundbreaking line of 3D sports simulations that began with Actua Soccer. Through it all, Gremlin was an institution unto itself in British game development, a rite of passage for countless artists, designers, and programmers, some of whom went on to found companies of their own. (The most famous of Gremlin’s spinoffs is Core Design, which struck international gold in 1996 with Tomb Raider.)

The more specific story of Normality begins with a fellow named Tony Crowther. While still a teenager in the 1980s, he was one of the elite upper echelon of early British game programmers, who were feted in the gaming magazines like rock stars. A Sheffield lad himself, Crowther’s fame actually predated the founding of Gremlin, but his path converged with its on a number of occasions afterward. Unlike many of his rock-star peers, he was able to sustain his career if not his personal name recognition into the 1990s, when lone-wolf programmers were replaced by teams and project budgets and timelines increased exponentially. He remembers his first sight of id Software’s DOOM as a watershed moment in his professional life: “This was the first game I had seen with 3D graphics, and with what appeared to be a free-roaming camera in the world.” It was, in short, the game that would change everything. Crowther immediately started working on a DOOM-style 3D engine of his own.

He brought the engine, which he called True3D, with him to Gremlin Interactive when he accepted the title of Technical Consultant there in early 1994. “I proposed two game scenarios” for using it, he says. “Gremlin went with the devil theme; the other was a generic monster game.”

The “devil theme” would become Realms of the Haunting, a crazily ambitious and expensive project that would take well over two years to bring to fruition, that would wind up filling four CDs with DOOM-style carnage, adventure-style dialogs and puzzle solving, a complicated storyline involving a globe-spanning occult conspiracy of evil (yes, yet another one), and 90 minutes of video footage of human actors (this was the mid-1990s, after all). We’ll have a closer look at this shaggy beast in a later article.

Today’s more modest subject of inquiry was born in the head of one Adrian Carless, a long-serving designer, artist, writer, and general jack-of-all-trades at Gremlin. He simply “thought it would be cool to make an adventure game in a DOOM-style engine. Realms of the Haunting was already underway, so why not make two games with the same engine?” And so NormalityRealms of the Haunting‘s irreverent little brother, was born. A small team of about half a dozen made it their labor of love for some eighteen months, shepherding it to a European release in the spring of 1996. It saw a North American release, under the auspices of the publisher Interplay, several months later.



To the extent that it’s remembered at all, Normality is known first and foremost today for its free-roaming first-person 3D engine — an approach that had long since become ubiquitous in the realm of action games, where “DOOM clones” were a dime a dozen by 1996, but was known to adventure gamers only thanks to Access Software’s Tex Murphy games. Given this, it might be wise for us to review the general state of adventure-game visuals circa 1996.

By this point, graphical adventures had bifurcated into two distinct groups whose Venn diagram of fans overlapped somewhat, but perhaps not as much as one might expect. The older approach was the third-person point-and-click game, which had evolved out of the 1980s efforts of Sierra and LucasArts. Each location in one of these games was built from a background of hand-drawn pixel art, with the player character, non-player characters, and other interactive objects superimposed upon it as sprites. Because drawing each bespoke location was so intensive in terms of human labor, there tended to be relatively few of them to visit in any given game. But by way of compensation, these games usually offered fairly rich storylines and a fair degree of dynamism in terms of their worlds and the characters that inhabited them. Puzzles tended to be of the object-oriented sort — i.e., a matter of using this thing from your inventory on this other thing.

The alternative approach was pioneered and eternally defined by Myst, a game from the tiny studio Cyan Productions that first appeared on the Macintosh in late 1993 and went on to sell over 6 million copies across a range of platforms. Like DOOM and its ilk, Myst and its many imitators presented a virtual world to their players from a first-person perspective, and relied on 3D graphics rendered by a computer using mathematical algorithms rather than hand-drawn pixel art. In all other ways, however, they were DOOM‘s polar opposite. Rather than corridors teeming with monsters to shoot, they offered up deserted, often deliberately surreal — some would say “sterile” — worlds for their players to explore. And rather than letting players roam freely through said worlds, they presented them as a set of discrete nodes that they could hop between.

Why did they choose this slightly awkward approach? As happens so often in game development, the answer has everything to do with technological tradeoffs. Both DOOM and Myst were 3D-rendered; their differences came down to where and when that rendering took place. DOOM created its visuals on the fly, which meant that the player could go anywhere in the world but which limited the environment’s visual fidelity to what an ordinary consumer-grade computer of the time could render at a decent frame rate. Myst, on the other hand, was built from pre-rendered scenes: scenes that had been rendered beforehand on a high-end computer, then saved to disk as ordinary graphics files — effectively converted into pixel art. This work stream let studios turn out far more images far more quickly than even an army of human pixel-artists could have managed, but forced them to construct their worlds as a network of arbitrarily fixed nodes and views which many players — myself among them — can find confusing to navigate. Further, these views were not easy to alter in any sort of way after they had been rendered, which sharply limited the dynamism of Myst clones in comparison to traditional third-person adventure games. Thus the deserted quality that became for good or ill one of their trademarks, and their tendency to rely on set-piece puzzles such as slider and button combinations rather than more flexible styles of gameplay. (Myst itself didn’t have a player inventory of any sort — a far cry from the veritable pawn shop’s worth of seemingly random junk one could expect to be toting around by the middle stages of the typical Sierra or LucasArts game.)

By no means did Normality lift the set of technical constraints I’ve just described. Yet it did serve as a test bed for a different set of tradeoffs from the ones that adventure developers had been accepting before this point. It asked the question of whether you could make an otherwise completely conventional adventure game — unlike its big brother Realms of the Haunting, Normality has no action elements whatsoever — using a Doom-style engine, accepting that the end result would not be as beautiful as Myst but hoping that the world would feel a lot more natural to move around in. And the answer turned out to be — in this critic’s opinion, at any rate — a pretty emphatic yes.

Tony Crowther may have chosen to call his engine True3D, but it is in reality no such thing. Like the DOOM engine which inspired it, it uses an array of tricks and shortcuts to minimize rendering times whilst creating a reasonably convincing subjective experience of inhabiting a 3D space. That said, it does boast some improvements over DOOM: most notably, it lets you look up and down, an essential capability for an old-school adventure game in which the player is expected to scour every inch of her environment for useful thingamabobs. It thus proved in the context of adventure games a thesis that DOOM had already proved for action games: that gains in interactivity can often more than offset losses in visual fidelity. Just being able to, say, look down from a trapdoor above a piece of furniture and see a crucial detail that had been hidden from floor level was something of a revelation for adventure gamers.

You move freely around Normality‘s world using the arrow keys, just as you do in DOOM. (The “WASD” key combination, much less mouse-look, hadn’t yet become commonplace in 1996.) You interact with the things you see on the screen by clicking on them with the mouse. It feels perfectly natural in no time — more natural, I must say, than any Myst clone has ever felt for me. And you won’t feel bored or lonely in Normality, as so many tend to do in that other style of game; its environment changes constantly and it has plenty of characters to talk to. In this respect as in many others, it’s more Sierra and LucasArts than Myst.

The main character of Normality is a fellow named Kent Knutson, who, some people who worked at Gremlin have strongly implied, was rather a chip off the old block of Adrian Carless himself. He’s an unrepentant slacker who just wants to rock out to his tunes, chow down on pizza, and, one has to suspect based on the rest of his persona, toke up until he’s baked to the perfection of a Toll House cookie. Unfortunately, he’s living in a dictatorial dystopia of the near future, in which conformity to the lowest common denominator — the titular Normality — has been elevated to the highest social value, to be ruthlessly enforced by any and all means necessary. When we first meet Kent, he’s just been released from a stint in jail, his punishment for walking down the street humming a non-sanctioned song. Now he’s to spend some more time in house arrest inside his grotty apartment, with a robot guard just outside the door making sure he keeps his television on 24 hours per day, thereby to properly absorb the propaganda of the Dear Leader, a thoroughly unpleasant fellow named Paul Mystalux. With your help, Kent will find a way to bust out of his confinement. Then he’ll meet the most ineffectual group of resistance fighters in history, prove himself worthy to join their dubious ranks, and finally find a way to bring back to his aptly named city of Neutropolis the freedom to let your freak flag fly.

Adrian Carless. It seems that the apple named Kent didn’t fall far from the tree named Adrian…

There’s a core of something serious here, as I know all too well; I’ve been researching and writing of late about Chairman Mao Zedong’s Cultural Revolution in China, whose own excesses in the name of groupthink were every bit as absurd in their way as the ones that take place in Neutropolis. In practice, though, the game is content to play its premise for laughs. As the creators of Normality put it, “It’s possible to draw parallels between Paul [Mystalux] and many of the truly evil dictators in history — Hitler, Mussolini, Stalin — but we won’t do that now because this is supposed to be light-hearted and fun.” It’s far from the worst way in the world to neutralize tyranny; few things are as deflating to the dictators and would-be dictators among us than being laughed at for the pathetic personal insecurities that make them want to commit such terrible crimes against humanity.

This game is the very definition of laddish humor, as unsubtle as a jab in the noggin, as rarefied as a molehill, as erudite as that sports fan who always seems to be sitting next to you at the bar of a Saturday night. And yet it never fails to be likeable. It always has its heart in the right place, always punches up rather than down. What can I say? I’m a simple man, and this game makes me laugh. My favorite line comes when, true adventure gamer that you are, you try to get Kent to sift through a public trashcan for valuable items: “I have enough trash in my apartment already!”

Normality‘s visual aesthetic is in keeping with its humor aesthetic (not to mention Kent’s taste in music): loud, a little crude, even a trifle obnoxious, but hard to hate for all that. The animations were created by motion-capturing real people, but budget and time constraints meant that it didn’t quite work out. “Feet would float and swim, hands wouldn’t meet, and overall things could look rather strange,” admits artist Ricki Martin. “For sure the end results would have been better if it had been hand-animated.” I must respectfully disagree. To my mind, the shambolic animation only adds to the delightfully low-rent feel of the whole — like an old 1980s Dinosaur Jr. record where the tape hiss and distortion are an essential part of the final impression. (In fact, the whole vibe of the game strikes me as more in line with 1980s underground music than the 1990s grunge that was promised in some of its advertising, much less the Britpop that was sweeping its home country at the time.)

But for all its tossed-off-seeming qualities, Normality has its head screwed on tight where it’s important: it proves to be a meticulously designed adventure game, something neither its overall vibe not its creators’ lack of experience with the genre would lead one to expect. Thankfully, they learned from the best; all of the principals recall the heavy influence that LucasArts had on them — so much so that they even tried to duplicate the onscreen font found in classics like The Secret of Monkey Island, Day of the Tentacle, and Sam and Max Hit the Road. The puzzles are often bizarre — they do take place in a bizarre setting, after all — but they always have an identifiable cartoon logic to them, and there are absolutely no dead ends to ruin your day. As a piece of design, Normality thus acquits itself much better than many another game from more established adventure developers. You can solve this one on your own, folks; its worst design sin is an inordinate number of red herrings, which I’m not sure really constitutes a sin at all. It’s wonderful to discover an adventure game that defies the skepticism with which I always approach obscure titles in the genre from unseasoned studios.


The game begins in Kent’s hovel of a flat.

The game’s verb menu is capable of frightening small children — or, my wife, who declared it the single ugliest thing I’ve ever subjected her to when I play these weird old games in our living room.

Sometimes Normality‘s humor is sly. These rooms with painted-on furniture are a riff on the tendency of some early 3D engines to appear, shall we say, less than full-bodied.

Other times the humor is just dumb — but it still makes me laugh.

The game ends in a noisy concert that’s absolutely off the hook, which is absolutely perfect.



Normality was released with considerable fanfare in Europe, including a fifteen-page promotional spread in the popular British magazine PC Zone, engineered to look like a creation of the magazine’s editorial staff rather than an advertisement. (Journalistic ethics? Schmethics!) Here and elsewhere, Gremlin plugged the game as a well-nigh revolutionary adventure, thanks to its 3D engine. But the public was less than impressed; the game never caught fire.

In the United States, Interplay tried to inject a bit of star power into the equation by hiring the former teen idol Corey Feldman to re-record all of Kent’s lines; mileages will vary here, but personally I prefer original actor Tom Hill’s more laconic approach to Feldman’s trademark amped-up surfer-dude diction. Regardless, the change in casting did nothing to help Normality‘s fortunes in the United States, where it sank without a trace — as is amply testified by the fact that this lifelong adventure fan never even knew it existed until recently. Few of the magazines bothered to review it at all, and those that did took strangely scant notice of its formal and technical innovations. Scorpia, Computer Gaming World‘s influential adventure columnist, utterly buried the lede, mentioning the 3D interface only in nonchalant passing halfway into her review. Her conclusion? “Normality isn’t bad.” Another reviewer pronounced it “mildly fun and entertaining.” With faint praise like that, who needs criticism?

Those who made Normality have since mused that Gremlin and Interplay’s marketing folks might have leaned a bit too heavily on the game’s innovative presentation at the expense of its humorous premise and characters, and there’s probably something to this. Then again, its idiosyncratic vibe resisted easy encapsulation, and was perhaps of only niche appeal anyway — a mistake, if mistake it be, that LucasArts generally didn’t make. Normality was “‘out there,’ making it hard to put a genre on it,” says Graeme Ing, another artist who worked on the game — “unlike Monkey Island being ‘pirates’ and [Day of the] Tentacle being ‘time travel.'” Yet he admits that “I loved the game for the same reasons. Totally unique, not just a copy of another hit.”

I concur. Despite its innovations, Normality is not a major game in any sense of the word, but sometimes being “major” is overrated. To paraphrase Neil Young, traveling in the middle of the road all the time can become a bore. Therefore this site will always have time for gaming’s ditches — more time than ever, I suspect, as we move deeper into the latter half of the 1990s, an era when gaming’s mainstream was becoming ever more homogenized. My thanks go to Sarah Walker for turning me onto this scruffy outsider, which I’m happy to induct into my own intensely idiosyncratic Hall of Fame.

(Sources: the book A Gremlin in the Works by Mark James Hardisty, which with its digital supplement included gives you some 800 pages on the history of Gremlin Interactive, thus nicely remedying this site’s complete silence on that subject prior to now. It comes highly recommended! Also Computer Gaming World of November 1996, Next Generation of November 1996, PC Zone of May 1996, PC World of September 1996, Retro Gamer 11, 61, and 75.

Normality is available for digital purchase at GOG.com, in a version with the original voice acting. Two tips: remember that you can look up and down using the Page Up and Page Down, and know that you can access the map view to move around the city at any time by pressing “M.” Don’t do what I did: spend more than an hour searching in vain for the exit to a trash silo you thought you were trapped inside — even if that does seem a very Kent thing to do…)

 
 

Tags: , ,

Buzz Aldrin’s Race into Space (and Space-Program Games in General)

“Demography is destiny,” said the French sociologist Auguste Comte apocryphally in the nineteenth century. That truism has been taken to heart by many in the time since — not least by our political classes. Yet it applies equally in the world of the arts and entertainment. For in any free market, the nature of production is dictated as much by the consumers as by the producers.

Certainly this is true of computer games. Throughout the 1980s and 1990s, they were largely the province of a rather specific demographic indeed: single white males between the ages of ten and thirty from relatively privileged socioeconomic circumstances, with a bent toward intellectual rather than active pursuits — i.e., the stereotypical “nerds” of pop culture. Computer games reflected the tastes of these boys and young men in other kinds of entertainment and leisure-time hobbies: Dungeons & Dragons, Star Wars, jet fighters, World War II, action movies, heavy-metal music, fast cars, and, when they could get a glimpse of them, fast women. Although I too have liked all of these things to a greater or lesser degree at some point in my life — I did, after all, grow up as a member of exactly the demographic in question — their extreme prevalence in the cultural ghetto about which I write has often left me searching, sometimes in vain, for games with a different set of values and antecedents.

But this article is not about one or more of those interesting cultural outliers. It’s rather about an interestingly scanty subgenre of games which seems like it ought to have been perfect for the demographic I’ve just described, but that for some reason just never quite took off. Specifically, I speak of games based on the realities of space exploration in a contemporary context, as opposed to the outer-space fantasias of Star Wars and the like. After all, just about every nerdy teenage boy goes through a race-for-the-Moon phase at some point. (And why not? Has humanity ever embarked on a grander collective adventure?) Further, games on this subject would seemingly have fit in well with the broader craze for realistic simulation, as manifested by everything from F-15 Strike Eagle to SimCity, which had taken a firm grip on the industry by the end of the 1980s.

And yet there just weren’t many simulations of this particular type, and even fewer of them that did very well. It strikes me that it’s worth asking why this is so. Was there something about this subject that just didn’t work as a game, or are we dealing with a mere historical accident here? Let’s begin with a brief survey of the field of earlier games that did venture out into this territory before we turn to the one that will be our main focus for today. To help in doing so, we’ll further divide the field into two categories: vehicular simulations of spaceflight and games of space-program management.

The earliest game of the former type actually predates the personal computer. Created on a big DEC PDP-8 by a Massachusetts high-school student named Jim Storer, inspired by the real Neil Armstrong’s nerve-wracking manual landing on the Moon in 1969, the very year it was first programmed, Lunar demanded that you set your own landing craft down gently before your fuel ran out. Implemented entirely in text — you simply entered the number of fuel units you wished to burn each turn in response to a changing textual status display — it inspired dozens of clones and variants, most going under the more accurately descriptive name of Lunar Lander. By the dawn of the personal-computing age in 1978, David Ahl was able to write in his landmark book BASIC Computer Games that Lunar Lander in all its incarnations was “far and away the most popular computer game” of them all. It was even converted into a graphical standup-arcade game by Atari in 1979, in which form its quiet, cerebral tension made it an incongruous outlier indeed in an arcade full of shoot-em-ups.

Other programmers got inevitably more expansive in their ambitions for spaceflight simulation after Lunar Lander. By 1986, with the release of Spectrum HoloByte’s Orbiter, they had graduated to offering up a complete Space Shuttle flight simulator, covering all the stages of a mission from liftoff to landing. (Sadly, it arrived just in time for the Challenger disaster…) In 1992, Virgin Software published an even more complex and complete iteration on the concept, entitled simply Shuttle.

Yet neither of these later simulations came close to matching their simplistic predecessor in popularity. Their subject matter, it seemed, just didn’t quite work as a hardcore simulation. A simulation of a jet fighter flying into a war zone — such as the popular and long-lived Falcon series which Spectrum HoloByte produced after Orbiter — offered an intriguing range of tactical possibilities which a simulation of a Space Shuttle did not. A fighter pilot flying into combat is lord of his domain, in complete control of his airplane; the outcomes of his battles are entirely up to him. An astronaut flying into space, on the other hand, is merely the tip of a long spear of cooperative hierarchy; situations like those last few minutes before the Eagle landed, when Neil Armstrong was making all of the decisions and executing them all alone, have been vanishingly rare in the history of space flight. If, as Sid Meier likes to say, a good game is “a series of interesting decisions,” this fact makes spaceflight as it has existed so far in our historical reality problematic as the subject of a compelling simulation. Too often, Orbiter and Shuttle felt like exercises in rote button-mashing — button-mashing which you were expected to do exactly when and how ground control told you. Perhaps you weren’t quite the spam in a can the test-pilot peers of the earliest astronauts had so mocked them for being, but it sure felt that way at times. “As strange as it may seem,” wrote Computer Gaming World magazine of Orbiter, “a lot of flying the Shuttle is boring — a lot of pushing buttons, running computer programs, and the like — and it shows.”

In light of this, it’s telling that arguably the most entertaining of these spaceflight simulators opted for a less hardcore, more impressionistic approach. Apollo 18, developed by the Canadian studio Artech and published by Accolade in 1987, posited an alternative history where at least one of NASA’s final trio of cancelled Moon missions actually did take place. In keeping with Artech designer and theoretician-in-chief Michael Bate’s concept of “aesthetic simulation,” Apollo 18 portrayed a mission to the Moon not as a holistic vehicular simulation but as a series of mini-games, jumping from the perspective of ground control to that of the astronauts in space whenever it felt the need. This more free-wheeling, almost cinematic approach, combined perhaps with the fact that going to the Moon is inherently more exciting than releasing yet another whatsit from the Shuttle’s cargo bay in low Earth orbit, made the game a more riveting experience than its Shuttle-centric peers. Still, even it ran out of legs fairly quickly; once you’d worked through the steps of getting to the Moon and back once or twice, there just wasn’t much motivation to do so again.

So much for simulation. In the category of strategic space-program managers, we have an equally mixed bag.

Just as with the venerable Lunar Lander, one of the very first attempts to portray the contemporary conquest of space in this way was also the most successful of its era, in both financial and artistic terms. I wrote at some length long ago about 1984’s Project: Space Station, an earnest effort, masterminded by a fellow named Lawrence Holland who would go on to become LucasArts’s flight-simulator guru, to portray the construction and operation of a commercial space station in Earth orbit. Both space stations and private enterprise in space were much in vogue at the time, thanks respectively to President Ronald Reagan’s announcement of plans to build a station called Freedom in his 1984 State of the Union address and the realities of a terminally underfunded NASA whose priorities shifted with the political winds — realities which would ensure that Freedom itself never got off the drawing board, although it would gradually morph into the joint project known as the International Space Station. As I wrote in that older article, Project: Space Station, which blended an overarching strategy game with light vehicular simulation, came heartbreakingly close to greatness. But in the end, it was somewhat undone by a lack of feedback mechanisms and poor command and control — weaknesses which, it should be said, feel more like a result of the limited 8-bit hardware on which it ran than a failure of design in the abstract. But whatever its failings, it was by all indications reasonably successful in its day, enough so that, when its original publisher HESware went bankrupt within a year of its release, it was picked up at auction by Accolade and re-released by them in the same year they published Apollo 18.

Alas, Project: Space Station‘s immediate successors would prove markedly less rewarding as games to play or products to sell. Space MAX, created and self-published by a former Jet Propulsion Laboratories engineer named Tom Keller in 1986, poured on the detail at the expense of playability, until it came to resemble one of NASA’s long-range planning tools more than a computer game. And Karl Buiter’s Earth Orbit Stations of 1987 buried a very appealing premise, focusing more on the mechanical details of building a modular space station than had either of the earlier games of its type, under an atrocious presentation layer which Computer Gaming World described as “a textbook case of how not to design a [graphical user] interface.” And after those two less-than-compelling efforts, the strategic space-program-management subgenre pretty much dried up.

This, then, was the underwhelming state of contemporary-spaceflight games in general in 1993, when Interplay published a new take on the subject matter bearing the name of one of the most famous astronauts of all — in fact, the one who had actually been sitting there beside Neil Armstrong when he was making that hair-raising landing on the Moon. Like Apollo 18, Buzz Aldrin’s Race into Space chose to turn back the clock to those glory days of the Moon race rather than focusing on present-day space stations engaged in the comparatively plebeian labor of developing new industrial-chemical compounds and new medical treatments, important though such things undoubtedly are. The managerial perspective it adopted, however, had more to do with Project: Space Station than Apollo 18. A noble effort in its way, as indeed were all those games I’ve just written about, its own points of failure have perhaps even more to tell us about game design than theirs do.


Fritz Bronner

The driving force behind Buzz Aldrin’s Race into Space wasn’t its astronaut mascot — no surprise there, right? — but rather one Fritz Bronner, a less famous American whose name would have fit perfectly to one of the German rocket scientists who helped Wernher von Braun build the Saturn V rocket that sent men to the Moon. In the early 1980s, as a young man with dreams of becoming an actor, Bronner spent many an evening playing a variety of tabletop wargames and RPGs with his buddies in his home state of Florida. On one of those evenings, he had just finished an RPG session when he turned on the television to see a rocket launch on the news — an event he always watched with interest, being a self-described “space fanatic.” The thought process he went through then, with his mind still addled by game systems and dice rolls, will waken immediate recognition in anyone who has ever played Race into Space. For the most fundamental mechanic in that game has its origin right here:

The game player in me suddenly wondered what the odds were for a successful launch. The next thought I had was the chance of failure. I formulated in my mind a guess on the total number of [successful] launches versus failures. I quickly concluded that out of ten previous launches, nine of them were successful. Just before liftoff, I rolled the percentile dice and rolled below the range, which indicated to me that the launch would be successful. A few minutes later, another satellite reached orbit. I was elated that I had come up with a pseudo-model for launch success.

Immediately I wondered how a manned launch would work. I started to play with some rough mathematical figures. I selected a one-stage rocket and a two-stage rocket and then realized that I would have to devise a safety factor for a capsule. I think I came up with around 85 percent for the capsule. Then I plunged into what mission steps would occur in spaceflight. I rolled the dice on a three-step suborbital flight and to my excitement it worked! Suddenly each step of the mission was monumentally important. I became tense as I rolled the dice. It reminded me of the flavor of the early spaceflights.

I called [my friend] Steve [Stipp] over and told him of my successful suborbital flight. After his own successful flight, we both gleefully started scribbling notes on possible payload weights and additional mission steps. Soon we had scraps of paper filled with my horribly drawn stick figures of capsules that were lofting astronauts into space.

At this point, it was success or total failure on a mission step. We both realized that it was too crude and unrealistic for a rocket to always blow up on the pad. There were cancelled launches and aborts that should be considered. We laughed and played and scribbled more notes and sketched drawings for several hours, and then folded it up and forgot about it for several years.

In 1985, Bronner’s acting dream took him from Florida to New York City. His wife was working as a long-haul flight attendant, leaving him with plenty of solitude for contemplation in between auditions there in the big city. A television documentary called Spaceflight refreshed his memories of playing that improvised dice-throwing game of space launches. Just as importantly, it shifted his thinking toward an historical perspective. What if he made a game about the space race of the 1950s and 1960s, with one player in the role of the Americans and the other of the Soviets, each trying to be the first to reach the Moon? Each player would have to research the technology necessary for each stage of the endeavor, then test it with a live launch. The tension that would make for interesting choices was clear: that between researching everything exhaustively to achieve the best possible safety rating and pushing the timetable to beat out your opponent. At bottom, then, it would be a “press your luck” game — an evergreen in tabletop game design, but implemented here in the service of a thoroughly unique theme. For the next couple of years, Bronner continued to develop and refine the concept, even sending samples to many board-game publishers, albeit without managing to stir up much interest.

In 1987, Bronner’s acting dream took him from New York City to Hollywood. While he would never become the movie star he might have imagined back in Florida, he would carve out a solid career for himself as one of the film industry’s unglamorous but indispensable utility players; he would take bit parts in dozens of movies and television shows alongside starring roles in hundreds of commercials, and eventually also take on small-time writing, directing, and producing gigs. A year after arriving in Hollywood, he wrangled a meeting with the Los Angeles-based Task Force Games, best known for their Star Fleet Battles tactical space-combat games which took place in the Star Trek universe. He finally got a positive response from this publisher, and soon signed a contract with them to publish the board game Liftoff!.

Liftoff! made its public bow in the summer of 1989 at the Origins International Game Expo, one of the tabletop hobby’s two biggest American events, which happened to be held that year right there in Los Angeles. The reaction to Bronner’s game at Origins was cautiously favorable, but it never translated into much in the way of sales in the months that followed. Task Force Games had been bought by the computer-game publisher New World Computing the year before they signed the contract with Bronner; it was for this reason that they were in the Los Angeles area at all, having been moved there from Amarillo, Texas, to join their new parent. Yet the relationship wasn’t living up to either partner’s expectations. Profits, which tended to be scant at the best of times in the tabletop industry, had become nonexistent, as the expected synergies between the computer and the tabletop business failed to materialize. In 1990, Task Force’s head John Olsen scraped together enough funding to buy the company back from New World and moved with it back to Amarillo. Necessity forced the downsized entity to focus its resources on Star Fleet Battles, its most well-known and marketable franchise. Liftoff! died on the vine.

But Fritz Bronner wasn’t willing to let his game go so gently into that good night. Although he had never owned a computer in the past, his arrival in Hollywood had coincided with the beginnings of a buzz from the more forward-thinking members of the media elite about the future of interactive video and multimedia computing. It certainly hadn’t been lost on Bronner when signing the contract with Task Force Games that the company’s parent was a publisher of computer games. In fact, he had tried to interest New World in a digital version of Liftoff! repeatedly, but could never really get their attention. Fortunately, his attorney had assured that the contract he signed with Task Force/New World gave them just one year to develop a computerized version, if they wished to do so; afterward, those rights reverted to Bronner himself. He soon bought his first computer, a used Commodore Amiga 500, to consider the possibilities. In the summer of 1990, he started talking with a young programmer named Michael K. McCarty. At year’s end, the two of them formed a company which they named Strategic Visions, and began working on a demo to show to publishers.

It perhaps says something about the zeitgeist of gaming on the cusp of the multimedia age that Bronner and McCarty elected to make their demo a non-interactive video rather than an interactive game. From the start, Bronner’s vision for the project had been to move the mechanics of the board game onto the computer essentially intact, then spice them up with lots of video footage from the archives of NASA and the Soviet space program. His timing in this respect was perfect: the fall of the Iron Curtain helped immensely in getting access to the latter’s videos. Meanwhile the fact that all of the footage was the product of government agencies, and thus released into the public domain, helped in another way. Less positively, this overweening focus on the multimedia aspects of the project, which would continue throughout its duration, would rather distract from some worrisome flaws in the foundation of the actual rules set — an issue we’ll return to a bit later.

In the short term, though, the non-interactive demo served its purpose. In contrast to the relative lack of interest the tabletop design had garnered, the proposed digital version attracted lots of publishers when Bronner and McCarty brought their demo to the Summer Consumer Electronics Show for private screenings in June of 1991. The videos Bronner showed of rockets soaring and exploding were well-nigh irresistible to an industry all abuzz with talk of interactive movies incorporating just this type of real-world footage. Over thirty potential partners viewed the demo reel in the course of the show, and several of them came forward with serious offers.

Bronner settled on Interplay Productions for several reasons: they were also Los Angeles-based, always a nice advantage; he got on well with Interplay’s head Brian Fargo; and Fargo had immediately run with an idea Bronner had mentioned in passing, that of signing up Edwin “Buzz” Aldrin — by far the most gregarious and ambitious of the Apollo 11 astronauts in terms of media and marketing — to lend his endorsement to the game. Indeed, Fargo already had Aldrin on board when the contract was signed in August of 1991. Thus did Liftoff! become Buzz Aldrin’s Race into Space.

Aldrin’s direct participation encompassed nothing more than marketing — he regaled a long string of trade-show attendees and magazine editors with his well-worn tales of landing on the Moon, while saying next to nothing about the game itself — but it did lead to the computer game’s most significant substantive addition to the board game. Bronner added a roster of astronauts to be recruited and trained, who manifested differing strengths and weaknesses and even differing personalities which could cause them to be more or less effective when combined into crews. The idea and approach are so similar to the astronaut management found in Project: Space Station that one suspects they must have been inspired by that earlier game. That said, I have no proof that this was so.

Otherwise, though, Race into Space is a fairly straightforward re-implementation of Liftoff! rather than a major expansion upon it. In fact, some parts of the board game are actually trimmed away, such as the ability to play as the head of a fictional European or Asian space agency, which Bronner had included in order to allow up to four players to gather around the tabletop. Race into Space, on the other hand, is limited to two players, each of them controlled either by a human or the computer.

Pitched to Interplay with an absurdly optimistic six-month development timeline, Race into Space ran over that estimate by a factor of three. Indeed, it became the first game in history to get two feature-length previews in Computer Gaming World, one in January of 1992 and one in December of the same year. An early decision to switch development from the fading Amiga to MS-DOS didn’t help matters; nor did Strategic Visions’s need to rely on Interplay’s art team for most of the non-digitized graphics, work that got done only as time allowed betwixt and between other in-house projects. Most of all, though, the project began just a little bit too early, before the typical consumer computer was quite able to live up to Bronner’s multimedia ambitions. Even the version of the game that finally did ship on floppy disk in March of 1993 was heavily compromised by the limitations of its storage medium, with digitized still photographs standing in for most of the videos the original demo had promised. Players would have to wait for the CD-ROM version, which didn’t arrive until fourteen months later, to truly see the game as its designer had imagined it.



Race into Space is played in turns lasting six months each, beginning in 1957 and stretching until either 1977 arrives or someone manages to land on the Moon. Economics will play a big role in your success or lack thereof; you’re provided with a semiannual budget which increases only gradually, with the completion of major milestones according it a more substantial boost — especially if you manage them before your opponent — and catastrophic failures having the opposite effect. This approach is rather ahistorical on the face of it — in a classic example of throwing money at a problem until it bears fruit, the budget of NASA in particular was dictated more by the achievements of the Soviets than by the agency’s own accomplishments — but is probably necessary for Race into Space to work as a game.

As the game goes on, you build up your program’s facilities — adding things like additional launch pads to let you carry out more launches per turn.

Still, the core of the experience remains what it was when a young Fritz Bronner first started experimenting with the idea of a space-program-management game in the early 1980s: watching with bated breath from mission control as your rockets go up, hoping each successive step will go off without a hitch to get you your next mission milestone. Said milestones encompass everything from launching the first unmanned satellite — the game begins in the year of Sputnik — to the Moon landing itself. Yet, beyond the first few milestones at any rate, they don’t break down into a mere linear progression of steps to be mindlessly walked through. You can combine milestones into one mission; for example, you might make your first flight of eight days or more duration the same one where your astronauts first execute a space walk. And you can also skip some of them entirely, if you’re pressed for time and are willing to forgo the budget boosts with which they tempt you; the aforementioned space walk, for example, isn’t even strictly necessary for a Moon landing.

Most importantly, Race into Space lets you implement not only the historical method of getting to the Moon — that of employing a space capsule which orbits the Moon and a separate landing craft to take part of the crew down to the surface — but also a number of other approaches that were discussed at the time, such as an all-in-one-spacecraft approach (this requires developing a monster rocket that makes a Saturn V look like a kid’s toy) or even a reusable space shuttle (this requires both an enormous investment of time and money and a really slow opponent). The variety of alternate histories the game allows is not infinite — more on that momentarily — but is enough to provide for at least a few interesting and even educational playthroughs. If nothing else, you’ll walk away from your failed attempts to rewrite history with a better understanding of why NASA chose the approach they did.

Achieving firsts is extremely important because it increases your program’s prestige — which in turn leads to an increase in its budget. If things go too disastrously wrong, you can even be fired from your post as program director.

But alas, Race into Space soon begins to show those cracks in its foundation which I alluded to earlier, which are partly born from the lack of a clear sense of its own goals as a game. One can imagine at least three abstract approaches fitting into the general framework of “a managerial game about the race to the Moon.” One would be a heavily experiential game, in the spirit of Michael Bate’s aesthetic simulations, de-emphasizing the competitive aspects in favor of taking the player on a journey through those heady early days of the space age. Another would be a replayable game of hardcore strategy, in which the fiction of the Moon race functions as a mere thematic skin for the mechanical underpinnings which quickly become the player’s real focus. And still another would be an open-ended sandbox, a learning tool that lets the player experiment with many different approaches to landing on the Moon and to spaceflight in general.

Race into Space never firmly commits to any one of these approaches, but rather feints toward all of them in various places. The end result is a confusing mishmash of elements that are constantly cutting against one another. The heavy reliance on photographs, video, and sound clips from the period in question seem to push it into the experiential camp, but its board-game-derived mechanics and relatively short play time — a full game usually takes no more than two or three hours to play — pull it in the second direction I outlined. And so the cognitive dissonances start to add up. The video clips lose their appeal when you’re forced to click through the same ones over and over, every time you play, even as it remains debatable whether the mechanics are really compelling enough to make it a game you want to return to again and again under any circumstances; there are really only one or two best paths to follow to get to the Moon, and once you’ve found them there’s little reason to keep playing. Meanwhile the game’s educational sandbox potential, while by no means nonexistent, is also sharply limited. True to its board-game roots, Race into Space doesn’t simulate spaceflight at all beyond rolling dice against an arbitrary set of success-or-failure percentiles. In terms of spaceflight hardware, it lets you mix and match a set of pieces it provides for you, and pour money into each piece’s research to push its reliability percentage up, but it’s nowhere near sophisticated enough to let you develop your own components from scratch. Here too, then, it feints in a promising direction without going far enough to truly satisfy over the long term.

Yet this sense of confusion about what Race into Space actually wants to be constitutes only its second biggest problem. Its biggest problem of all doesn’t require as much design philosophy to explain: the darn thing is just too darn hard. Something is badly off with the math behind this game — something you sense more than you can know. Playing it quickly begins to feel like that memorable montage of exploding and misguided rockets from the film The Right Stuff. You can recover in fairly short order from failed launches in the early phases, when you’re mostly launching unmanned craft, but they turn devastating when they start chewing through your astronaut corps like a wolf in a chicken coop. Failed missions not only destroy the morale of your surviving astronauts, causing them to perform worse, but knock the reliability of the failed component almost all the way back to zero, forcing you to research it up again from scratch. This of course makes no sense in strictly logical terms; in the absence of any new inputs, a defective component should be defective to exactly the same extent on the next flight. Rather than conveying the rounds of investigation and soul-searching that always accompanied a real loss of life in the space program, as it was doubtless intended to do, this mechanic just furthers the impression that the game is out to get you at any cost. The fact that the computer player mysteriously seems to be able to cut more corners than you without killing astronauts by the dozens contributes strongly to the same impression.

Screens like this one appear distressingly frequently, almost regardless of how thoroughly you research and develop your components. Either the real NASA was incredibly lucky, or something is off inside this game’s numbers. Perhaps a bit of both?

Unkind though it may sound to say, I can’t help but suspect that Race into Space‘s issues in this area reflect a fundamental misunderstanding of statistics on the part of a younger Fritz Bronner — a misunderstanding that somehow never got corrected through all his years of working on his game. A mission does not, as one might initially imagine, have a chance of success equal to the reliability percentage of its dodgiest hardware component. On the contrary: the various components actually undergo reliability checks at various times — often at multiple times — during a mission. Therefore even a stack of components which have all been researched up to a reliability of 95 percent still has a substantial chance of failing in some more or less disastrous way on a more complex mission. And yet you simply don’t have time to laboriously research every component up to its maximum reliability, which for many of them is substantially below 95 percent anyway. You’re in a Moon race, after all. You have to roll the dice. Small wonder that so many players over the years have advocated save-scumming — that dastardly practice of saving and reloading until the dice roll your way — as the only practical way to play. That, or play a two-human-player game, but just click through your “opponent’s” turns without doing anything. Playing that way, you might just be able to get to the Moon before 1977.

So, despite the historical verisimilitude it works so hard to inculcate via its video clips and all the other period-specific touches, Race into Space‘s mechanics lead to a simple game of luck at bottom, and one where the odds are stacked against you at that. There is no opportunity to jump in and make decisions when a mission starts to go wrong — no chance, in other words, to improvise your way through a drama like the Apollo 13 mission. You’re a mere helpless bystander from the moment a mission begins until it ends.

The game’s delight in making its players’ rockets go boom provoked such howls of protests from early purchasers of the original floppy-based release that Interplay soon released a patch to tweak the numbers somewhat — although still nowhere near enough in the opinion of most. The very fact that Bronner felt able to manipulate the numbers in this way, of course, demolished any remaining belief players might have harbored that the numbers had any real historical basis at all. Clearly they were strictly arbitrary. Bronner never did achieve a balance that felt both playable and true to history. And that failure makes it difficult to consider Race into Space as a whole as anything but another interestingly failed attempt at making a game out of real-world space exploration.

Race into Space sold in reasonable numbers for Interplay, but never huge ones, especially after word of just how frustrating it could be got around on the street. Thus none of Bronner’s plans for sequels, which he had publicly discussed at some length in the run-up to release, ever got off the metaphorical launching pad. Strategic Visions soon folded up shop, and Bronner continued his career in Hollywood. He’s never designed another game.

Ironically, the sequels Bronner discussed may actually have made for better games than this one. One idea, for example, would have focused on a manned mission to Mars. Removed from the context of real history, not being surrounded by all those grainy old video clips reminding players of what once was, such a game would have been able to exist entirely on its own terms, and may have wound up feeling more satisfying because of it even if its mechanics had been left largely unchanged.

As it is, though, Race into Space displays that most telling sign of an ingenious game idea with questionable execution: players lining up with ways to fix it. Their efforts were confined to the realms of speculation and hex editors until 2005, when, the rights having reverted to Fritz Bronner, he generously released the game and all of its source code under the General Public License. In the time since, a small community of enthusiasts has continued to port and refine the game on a sporadic basis, but it’s never managed to garner a critical mass of developers or players. Ditto an attempt at a full-fledged commercial revival of the concept by the wargame publisher Slitherine, which arrived complete with the original game’s astronaut mascot in 2014 under the name Buzz Aldrin’s Space Program Manager.


While Race into Space‘s most specific, practical design mistakes aren’t too hard to identify, the more generalized failings of it and its peers in the scanty tradition of contemporary-space-program games do rather prompt one to ask another question: is there something about the subject matter itself that causes it not to work as a satisfying game? I believe I’ve actually done a reasonable job of answering that question already for the case of spaceborne vehicular simulations: as I noted near the beginning of this article, an astronaut in space just doesn’t have enough independent agency in most situations to make for a reasonably realistic simulation that’s also engaging as a game. But what of the other broad category of games I’ve addressed today, the one to which Race into Space belongs: that of space-program managerial games?

For a long, long time after Race into Space, one might have been forgiven for assuming that space-program managers as well were indeed nonstarters as satisfying games. But then, in 2015, a game called Kerbal Space Program came along to prove such naysayers wrong. I don’t usually write about modern games here, but I will briefly outline the premise of this one.

The titular Kerbals are a species of furry green aliens who run a space program of their own on their planet of Kerbin. Despite their cartoony cuteness, said space program itself is simulated with meticulous attention to detail, including all of the particulars of physics and aeronautics which Race into Space so conspicuously lacks. Players with an interest in rocketry or aeronautical engineering can and do lose years of leisure time to it. It may or may not be a game for you, but it is, by any objective definition, an impressive piece of work, far more intrinsically fascinating than any other that I’ve written about today.

And how does it accomplish this feat? One obvious answer is that it knows what it wants to be first and foremost: a sandbox for exploring the practical possibilities and limitations of space travel using the technology of our own recent past, present, and near future. A dedicated modding community has helped the designers to graft on additional layers of competitive strategy and economics for those who want them. Nevertheless, the game’s central delight remains that of creation and discovery. Kerbal Space Program is, in other words, one of the preeminent sandbox games of our time. And it’s completely comfortable with itself in that role, being free of the cognitive dissonances of Race into Space.

This stronger sense of itself is certainly one of the secrets to Kerbal Space Program‘s success. And here’s another: having noted earlier that the proposed non-historical sequels to Race into Space may have led to more compelling games, I’ll now submit Kerbal Space Program as Exhibit One in evidence for that argument. Freed from the weight of all that real human history, existing as it does in a world of cartoon aliens, it can just be a game.

Games can be great tools for exploring other lives and other times, but sometimes you just want to play. History, after all, doesn’t occur for our ludic amusement. Every wargamer knows that the number of unaltered historical battles that lead to good games is very small indeed; most real battles have their outcomes foreordained before they even begin. Perhaps the Apollo program and the Space Shuttle and the International Space Station and all the rest just don’t have the right stuff to make a worthy game. But that’s okay — because it means that, instead of recreating the storied past, we can imagine an exciting future. That goal is at least equally worthy — and, as Kerbal Space Program so thoroughly illustrates, it’s something that a game about space exploration can most definitely do, and do well at that.

When you play Race into Space as the Americans, each turn begins with a newscast from “Carter Walcrite” — a nod to Walter Cronkite, the television anchorman whose dulcet tones were the voice of the space race for many Americans, whom a number of surveys revealed to be the most trusted person in the United States during the turbulent 1960s. (I’ll leave the comparisons with contemporary attitudes toward journalism as an exercise for the reader…) Although the inclusion of all this loving period detail is wonderful on one level, on another it can be oddly stultifying to your attempts to write your own history.

(Sources: the books The Buzz Aldrin’s Race into Space Companion by Fritz Bronner, Designers & Dragons, Volume 2 by Shannon Appelcline, and BASIC Computer Games by David Ahl; Computer Gaming World of August 1986, March 1987, October 1987, February 1988, January 1992, May 1992, December 1992, and August 1993; Strategy & Tactics 212. Online sources include Leon Baradat’s comprehensive Race into Space site, the article “The Buzz is Gone” at The Escapist, and Steve Stipp’s homepage.

You can download the current open-source edition of Race into Space for free, or purchase its spiritual successor Buzz Aldrin’s Space Program Manager.)

 
 

Tags: ,

Alone in the Dark

Most videogame stories are power fantasies. You spend your time getting ever stronger, ever tougher, ever more formidable as you accumulate experience points, gold, and equipment. Obstacles aren’t things to go around; they’re things you go through. If you can’t get past any given monster, the solution is to go kill some other monsters, then come back when you’re yet more powerful and slay the big beast at last. Life, these games tell us, is or ought to be one unadulterated ride up the escalator of success; a setback just means you haven’t yet risen high enough.

That dynamic held true in 1992 just as much as it usually does today. But during that year there came a well-nigh revolutionary game out of France that upended all of these traditional notions about what the medium of videogames can do and be. It cast you as a painfully ordinary, near-powerless individual adrift in a scary world, with no surefire panaceas in the form of experience points, gold, or portable rocket launchers to look forward to. It was just you and your wits, trapped in a haunted house full of creatures that were stronger than you and badly wanted to kill you. Despite its supernatural elements, this game’s scenario felt more disconcertingly close to real life than that of any of those other games. Here, you truly were alone in the dark. Aren’t we all from time to time?


Any story of how this shockingly innovative game came to be must begin with that of Frédérick Raynal, its mastermind. Born in the south-central French town of Brive-la-Gaillarde in 1966, Raynal was part of the first generation of European youths to have access to personal computers. In fact, right from the time his father first came home with a Sinclair ZX81, he was obsessed with them. He was also lucky: in a dream scenario for any budding hacker, his almost equally obsessed father soon added computers to the product line of the little videocassette-rental shop he owned, thus giving his son access to a wide variety of hardware. Raynal worked at the store during the day, renting out movies and watching them to kill the time — he was a particular fan of horror movies, a fact which would soon have a direct impact on his career — and helping customers with their computer problems. Then, with a nerdy young man’s total obliviousness to proportion, he hacked away most of the night on one or another of the machines he brought home with him. He programmed his very first released game, a platformer called Robix, in 1986 on an obscure home-grown French computer called the Exelvision which his father sold at the store. His father agreed to sell his son’s Exelvision game there as well, managing to shift about 80 units to customers desperate for software for the short-lived machine.

Raynal’s lifestyle was becoming so unbalanced that his family was beginning to worry about him. One day, he ran out of his room in a panic, telling them that all of the color had bled out of his vision. His mother bustled him off to an ophthalmologist, who told him he appeared to have disrupted the photoreceptors in his eyes by staring so long at a monitor screen. Thankfully, the condition persisted only a few hours. But then there came a day when he suddenly couldn’t understand anything that was said to him; he had apparently become so attuned to the language of computer code that he could no longer communicate with humans. That worrisome condition lasted several weeks.

Thus just about everyone around him took it as a good thing on the whole when he was called up for military service in 1988. Just before leaving, Raynal released his second game, this time for MS-DOS machines. Not knowing what else to do with it, he simply posted it online for free. Popcorn was a Breakout clone with many added bells and whistles, the latest entry in a sub-genre which was enjoying new popularity following the recent success of the Taito arcade game Arkanoid and its many ports to home computers and consoles. Raynal’s game could hold its head high in a crowded field, especially given its non-existent price tag. One magazine pronounced it one of the five best arcade games available for MS-DOS, whether commercial or free, and awarded it 21 points on a scale of 20.

Raynal was soon receiving letters at his military posting from all over the world. “Popcorn has made my life hell!” complained one player good-naturedly. Another wrote that “I caught acute Popcornitus. And, it being contagious, now my wife has it as well.” When Raynal completed his service in the summer of 1989, his reputation as the creator of Popcorn preceded him. Most of the companies in the French games industry were eager to offer him a job. His days working at his father’s computer store, it seemed, were behind him. The Lyon-based Infogrames, the most prominent French publisher of all, won the Raynal sweepstakes largely by virtue of its proximity to his hometown.

Yet Raynal quickly realized that the company he had elected to join was in a rather perilous state. An ambitious expansion into many European markets hadn’t paid off; in fact, it had very nearly bankrupted them. Bruno Bonnell, Infogrames’s co-founder and current chief executive, had almost sold the company to the American publisher Epyx, but that deal had fallen through as soon as the latter had gotten their first good look at the state of his books. It seemed that Infogrames would have to dig themselves out of the hole they’d made. Thus Bonnell had slashed costs and shed subsidiaries ruthlessly just to stay alive. Now, having staunched the worst of the bleeding, he knew that he needed as many talented programmers as he could get in order to rebuild his company — especially programmers like Raynal, who weren’t terribly assertive and were naive enough to work cheap. So, Raynal was hired as a programmer of ports, an unglamorous job but an absolutely essential one in a European market that had not yet consolidated around a single computer platform.

Bonnell, for his part, was the polar opposite of the shy computer obsessive he had just hired; he had a huge personality which put its stamp on every aspect of life at Infogrames. He believed his creativity to be the equal of anyone who worked for him, and wasn’t shy about tossing his staff ideas for games. He called one of them, which he first proposed when Raynal had been on the job for about a year, In the Dark. A typically high-concept French idea, its title was meant to be taken literally. The player would wander through a pitch-dark environment, striking the occasional match from her limited supply, but otherwise relying entirely on sound cues for navigation. Bonnell and Raynal were far from bosom buddies, then or ever, but this idea struck a chord with the young programmer.

As Raynal saw it, the question that would make or break the idea was that of how to represent a contiguous environment with enough verisimilitude to give the player an embodied sense of really being there in the dark. Clearly, a conventional adventure-game presentation, with its pixel graphics and static views, wouldn’t do. Only one approach could get the job done: 3D polygonal graphics. Not coincidentally, 3D was much on Raynal’s mind when he took up Bonnell’s idea; he’d been spending his days of late porting an abstract 3D puzzle game known as Alpha Waves from the Atari ST to MS-DOS.

I’ve had occasion to discuss the advantages and disadvantages of this burgeoning new approach to game-making in previous articles, so I won’t rehash that material here. Suffice to say that the interest so many European programmers had in 3D reflected not least a disparity in the computing resources available to them in comparison to their American counterparts. American companies in this period were employing larger and larger teams, who were filling handfuls of floppy disks — and soon CD-ROMs — with beautiful hand-drawn art and even digitized snippets of real-world video. European companies had nothing like the resources to compete with the Americans on those terms. But procedurally-generated 3D graphics offered a viable alternative. At this stage in the evolution of computer technology, they couldn’t possibly be as impressively photorealistic as hand-drawn pixel art or full-motion video, but they could offer far more flexible, interactive, immersive environments, with — especially when paired with a French eye for aesthetics — a certain more abstracted allure of their own.

This, then, was the road Raynal now started down. It was a tall order for a single programmer. Not only was he trying to create a functional 3D engine from scratch, but the realities of the European market demanded that he make it run on an 80286-class machine, hardware the Americans by now saw as outdated. Even Bonnell seemed to have no confidence in Raynal’s ability to bring his brainstorm to fruition. He allowed Raynal to work on it only on nights and weekends, demanding that he spend his days porting SimCity to the Commodore CDTV.

An artist named Didier Chanfray was the closest thing to a partner and confidante which Raynal had at Infogrames during his first year of working on the engine. It was Chanfray who provided the rudimentary graphics used to test it. And it was also Chanfray who, in September of 1991, saw the full engine in action for the first time. A character roamed freely around a room under the control of Raynal, able to turn about and bend his body and limbs at least semi-realistically. The scene could be viewed from several angles, and it could be lit — or not — by whatever light sources Raynal elected to place in the room. Even shadows appeared; that of the character rippled eerily over the furniture in the room as he moved from place to place. Chanfray had never seen anything like it. He fairly danced around Raynal’s desk, pronouncing it a miracle, magic, alchemy.

In the meantime, Bruno Bonnell had negotiated and signed a new licensing deal — not exactly a blockbuster, but something commensurate with a rebuilding Infogrames’s circumstances.


Something tentacled and other-worldly, it seems, got into the water at Infogrames from the start: Didier Chanfray provided this very Lovecraftian concept drawing for Raynal’s game long before the conscious decision was made to turn it into a Lovecraft pastiche. Raynal kept the sketch tacked on the wall beside his desk throughout the project as a reminder of the atmosphere he was going for.

The American horror writer H.P. Lovecraft, who died well before the advent of the computer age in 1937, was nowhere near as well-known in 1991 as he is today, but his so-called “Cthulhu Mythos” of extra-dimensional alien beings, terrifying by virtue of their sheer indifference to humanity and its petty morality, had already made appearances in games. The very first work of ludic Lovecraftia would appear to be the 1979 computer game Kadath, an odd sort of parser-less text adventure. Two years later, at the height of the American tabletop-RPG craze, a small company called Chaosium published Call of Cthulhu, a game which subverted the power fantasy of tabletop Dungeons & Dragons in much the same way that Raynal’s project would soon be subverting that of so many computer games. Still, although Call of Cthulhu was well-supported by Chaosium and remained reasonably popular by the standards of its niche industry throughout the 1980s and beyond, its success didn’t lead to any Lovecraftian onslaught in the realm of digital games. The most notable early example of the breed is Infocom’s very effective 1987 interactive fiction The Lurking Horror. But, being all text at a time when text adventures were becoming hard sells, it didn’t make much commercial impact.

Now, though, Bonnell believed the time had come for a more up-to-date Lovecraftian computer game; he believed such a thing could do well, both in France and elsewhere.

Lovecraft had long had a strong following in France. From the moment his books were first translated into the language in 1954, they had sold in considerable numbers. Indeed, in 1991 H.P. Lovecraft was about as popular in France as he was anywhere — arguably more popular on a per-capita basis than in his native land. The game of Call of Cthulhu too had long since been translated into French, giving a potential digital implementation of it as much natural appeal there as in its homeland. So, Bonnell approached Chaosium about licensing their Call of Cthulhu rules for computers, and the American company agreed.

When viewed retrospectively, it seems a confusing deal to have made, one that really wasn’t necessary for what Infogrames would ultimately choose to do with Lovecraft. When Lovecraft died in obscurity and poverty, he left his literary estate in such a shambles that no one has ever definitively sorted out its confusing tangle of copyright claimants; his writing has been for all intents and purposes in the public domain ever since his death, despite numerous parties making claims to the contrary. Prior to publishing their Lovecraft tabletop RPG, Chaosium had nevertheless negotiated a deal with Arkham House, the publisher that has long been the most strident of Lovecraft’s copyright claimants. With that deal secured, Chaosium had promptly trademarked certain catchphrases, including “Call of Cthulhu” itself, in the context of games. Yet as it turned out Infogrames would use none of them; nor would they draw any plots directly from any of Lovecraft’s published stories. Like the countless makers of Lovecraftian games and stories that would follow them, they would instead draw from the author’s spirit and style of horror, whilst including just a few of his more indelible props, such as the forbidden book of occult lore known as the Necronomicon.

The first Lovecraftian game Infogrames would make would, of course, be the very game that Frédérick Raynal had now spent the last year or so prototyping during his free time. By the time news of his work reached Bonnell, most of Infogrames’s staff were already talking about it like the second coming. While the idea that had inspired it had been wonderfully innovative, it seemed absurd even to the original source of said idea to devote the best 3D engine anyone had ever seen to a game that literally wouldn’t let you see what it could do most of the time. It made perfect sense, on the other hand, to apply its creepy visual aesthetic to the Lovecraft license. The sense of dread and near-powerlessness that was so consciously designed into the tabletop RPG seemed a natural space for the computer game as well to occupy. It was true that it would have to be Call of Cthulhu in concept only: the kinetic, embodied, real-time engine Raynal had created wasn’t suitable for the turn-based rules of the tabletop RPG. For that matter, Raynal didn’t even like the Chaosium game all that much; he considered it too complicated to be fun.

Still, Bonnell, who couldn’t fail to recognize the potential of Raynal’s project, put whatever resources he could spare from his still-rebuilding company at the mild-mannered programmer’s disposal: four more artists to join Chanfray, a sound designer, a second programmer and project manager. When the team’s first attempts at writing an authentic-feeling Lovecraftian scenario proved hopelessly inadequate, Bonnell hired for the task Hubert Chardot, a screenwriter from 20th Century Fox’s French division, a fellow who loved Lovecraft so much that he had turned his first trip to the United States into a tour of his dead hero’s New England haunts. One of Chardot’s first suggestions was to add the word “alone” to the title of the game. He pointed out, correctly, that it would convey the sense of existential loneliness that was such an integral part of Lovecraftian horror — even, one might say, the very thing that sets it apart from more conventional takes on horror.

You can choose to enter the mansion as either of two characters.

The game takes place in the 1920s, the era of Lovecraft himself and of most of his stories (and thus the default era as well for Chaosium’s Call of Cthulhu game). It begins as you arrive in the deserted Louisiana mansion known as Derceto, whose owner Jeremy Hartwood has recently hanged himself. You play either as Edward Carnby, a relic hunter on the trail of a valuable piano owned by the deceased, or as Emily Hartwood, the deceased’s niece, eager to clear up the strange rumors that have dogged her uncle’s reputation and to figure out what really went down on his final night of life. The direction in which the investigation leads you will surprise no one familiar with Lovecraft’s oeuvre or Chaosium’s RPG: occult practices, forbidden books, “things man was never meant to know,” etc. But, even as Chardot’s script treads over this ground that was well-worn already in the early 1990s, it does so with considerable flair, slowly revealing its horrifying backstory via the books and journals you find hidden about the mansion as you explore. (There is no in-game dialog and no real foreground story whatsoever, only monsters and traps to defeat or avoid.) Like most ludic adaptations of Lovecraft, the game differs markedly from its source material only in that there is a victory state; the protagonist isn’t absolutely guaranteed to die or become a gibbering lunatic at the end.

One of the in-game journals, which nails the spirit and style of Lovecraft perfectly. As I noted in an earlier article about the writer, the emotion he does better than any other is disgust.

Yet Chaosium wasn’t at all pleased when Infogrames sent them an early build of the game for their stamp of approval. It seems that the American company had believed they were licensing not just their trademarks to their French colleagues, nor even the idea of a Lovecraft game in the abstract, but rather the actual Call of Cthulhu rules, which they had expected to see faithfully implemented. And, indeed, this may have been Bonnell’s intention when he was making the deal — until Raynal’s 3D engine had changed everything. Chaosium, who had evidently been looking forward to an equivalent of sorts to the Gold Box line of licensed Dungeons & Dragons CRPGs, felt betrayed. After some tense negotiation, they agreed to let Alone in the Dark continue without the Call of Cthulhu name on the box; some editions would include a note saying the game had been “inspired by the works of H.P. Lovecraft,” while others wouldn’t even go that far. In return for Chaosium’s largess on this front, Infogrames agreed to make a more conventional adventure game that would make explicit use of the Call of Cthulhu trademarks.

Call of Cthulhu: Shadow of the Comet, the fruit of that negotiation, would prove a serviceable game, albeit one that still didn’t make much direct use of the tabletop rules. But, whatever its merits, it would come and go without leaving much of a mark on an industry filled to bursting with graphical adventures much like it in terms of implementation. Alone in the Dark, on the other hand, would soon be taking the world by storm — and Chaosium could have had their name on it, a form of advertisement which could hardly have failed to increase their commercial profile dramatically. Chalk it up as just one more poor decision in the life of a company that had a strange talent for surviving — Chaosium is still around to this day — without ever quite managing to become really successful.

Infogrames got their first preview of just what an impact Alone in the Dark was poised to make in the spring of 1992, when Dany Boolauck, a journalist from the French videogame magazine Tilt, arrived to write a rather typical industry puff piece, a set of capsule previews of some of the company’s current works-in-progress. He never got any further than Alone in the Dark. After just a few minutes with it, he declared it “the best game of the last five years!” and asked for permission to turn the capsule blurb about it into a feature-length article, complete with a fawning interview with Raynal. (He described him in thoroughly overwrought terms: as a reincarnation of The Little Prince from Antoine de Saint-Exupéry’s beloved novella of the same name.) In a “review” published in the summer of 1992, still a couple of months before Infogrames anticipated releasing the game, he gave it 19 of 20 stars, gushing over its “exceptional staging” and “almost perfect character movement,” calling it “a revolution in the field of play” that “people must buy!”

Bruno Bonnell was pleased with the positive press coverage, but less thrilled by Boolauck’s portrayal of Raynal as the game’s genius auteur. He called in his introverted young programmer, who seemed a bit befuddled by all the attention, and told him to scrub the words “a Frédérick Raynal creation” from the end credits. Alone in the Dark, he said, was an Infogrames creation, full stop. Raynal agreed, but a grievance began to fester in his heart.

Thanks to Bonnell’s policy of not advertising the individuals behind Infogrames’s games, Raynal’s name didn’t spread quite so far and wide as that of such other celebrated gaming auteurs as Éric Chahi, the mastermind of Another World, France’s standout game from the previous year. Nevertheless, upon its European release in September of 1992, Raynal’s game stood out on its own terms as something special — as an artistic creation that was not just fun or scary but important to its medium. As one would expect, the buzz started in France. “We review many games,” wrote one magazine there. “Some are terrible, some mediocre, some excellent. And occasionally there comes along the game that will revolutionize the world of microcomputers, one that causes sleepless nights, one that you cannot tear yourself away from, can only marvel at. We bid welcome now to the latest member of this exclusive club: Alone in the Dark.” By the end of 1992, the game was a hit not only in France but across most of Europe. Now for America.

Bonnell closed a deal with the American publisher Interplay for distribution of the game there. Interplay had also published Another World, which had turned into a big success Stateside, and the company’s head Brian Fargo was sure he saw similar potential in Alone in the Dark. He thus put the game through his company’s internal testing wringer, just as he had Another World; the French studios had their strengths, but such detail work didn’t tend to be among them. Raynal’s game became a much cleaner, much more polished experience thanks to Interplay’s QA team. Yet Bonnell still had big international ambitions for Infogrames, and he wasn’t willing to let such a remarkable game as this one share with Another World the fate of becoming known to American players simply as an Interplay title. Instead he convinced Fargo to accept a unique arrangement. Interplay and Infogrames each took a stake in a new shared American subsidiary known as I-Motion, under which imprint they published Alone in the Dark.

The game took North America by storm in early 1993, just as it had Europe a few months earlier. It was that rarest of things in games, a genuine paradigm shift; no one had ever seen one that played quite like this. Worldwide, it sold at least 400,000 copies, putting Infogrames on the map in the United States and other non-European countries in the process. Indeed, amidst the international avalanche of praise and punditry, perhaps the most gratifying press notice of all reached Frédérick Raynal’s ears from all the way off in Japan. Shigeru Miyamoto, the designer of Super Mario Bros. and many other iconic Nintendo classics, proclaimed Alone in the Dark to be, more so than any other game, the one he wished he could have come up with.


Arguably the creepiest visual in the game is the weird mannequin’s head of your own character. Its crudely painted expression rather smacks of Chucky the doll from the Child’s Play horror films.

Seen from the perspective of a modern player, however, the verdict on Alone in the Dark must be more mixed. Some historically important games transcend that status to remain vital experiences even today, still every bit as fun and playable as the day they were made. But others — and please forgive me the hoary old reviewer’s cliché! — haven’t aged as well. This game, alas, belongs to the latter category.

Today, in an era when 3D graphics have long since ceased to impress us simply for existing at all, those of Alone in the Dark are pretty painful to look at, all jagged pixels sticking out everywhere from grotesquely octagonal creatures. Textures simply don’t exist, leaving everything to be rendered out of broad swatches of single colors. And the engine isn’t even holistically 3D: the 3D characters move across pasted-on pre-rendered backgrounds, which looks decidedly awkward in many situations. (On the other hand, it could have been worse: Raynal first tried to build the backgrounds out of digitized photographs of a real spooky mansion, a truly unholy union that he finally had to give up on.) Needless to say, a comparison with the lovingly hand-drawn pixel art in the adventure games being put out by companies like LucasArts and Sierra during this period does the crude graphics found here no favors whatsoever. Some of the visuals verge on the unintentionally comical; one of the first monsters you meet was evidently meant to be a fierce dragon-like creature, but actually looks more like a sort of carnivorous chicken. (Shades of the dragon ducks from the original Atari Adventure…)

Dead again! Killed by… Prince during his Purple Rain period?

Then, too, the keyboard-only controls are clunky and unintuitive, and they aren’t made any less awkward by a fixed camera that’s constantly shifting about to new arbitrary locations as you move through the environment; some individual rooms have as many as nine separate camera angles. This is confusing as all get-out when you’re just trying to get a sense of the space, and quickly becomes infuriating when you’re being chased by a monster and really, really don’t have time to stop and adjust your thinking to a new perspective.

The more abstract design choices also leave something to be desired. Sudden deaths abound. The very first room of the game kills you when you step on a certain floorboard, and every book is either a source of backstory and clues or an instant game-ender; the only way to know which it is is to save your game and open it. Some of the puzzles are clever, some less so, but even those that are otherwise worthy too often depend on you standing in just the right position; if you aren’t, you get no feedback whatsoever on what you’re doing wrong, and are thus likely to go off on some other track entirely, never realizing how close you were to the solution. This fiddliness and lack of attention to the else in the “if, then, else” dynamic of puzzle design is a clear sign of a game that never got sufficiently tested for playability and solubility. At times, the game’s uncommunicativeness verges on the passive-aggressive. You’ll quickly grow to loathe the weirdly stilted message, “There is a mechanism which can be triggered here,” which the game is constantly spitting out at you as you gaze upon the latest pixelated whatsit. Is it a button? A knob? A keyhole? Who knows… in the end, the only viable course of action is to try every object in your inventory on it, then go back and start trying all the other objects you had to leave lying around the house thanks to your character’s rather brutal inventory limit.

Fighting is a strange, bloodless pantomime.

Yes, one might be able to write some of the game’s issues off as an aesthetic choice — as merely more ways to make the environment feel unsettling. Franck de Girolami, the second programmer on the development team as well as its project leader, has acknowledged using the disorienting camera consciously for just that purpose: “We realized that the camera angles in which the player was the most helpless were the best to bring in a monster. Players would instantly run for a view in which they felt comfortable.” While one does have to admire the team’s absolute commitment to the core concept of the game, the line between aesthetic choice and poor implementation is, at best, blurred in cases like this one.

And yet the fact remains that it was almost entirely thanks to that same commitment to its core concept that Alone in the Dark became one of the most important games of its era. Not a patch on a contemporary like Ultima Underworld as a demonstration of the full power and flexibility of 3D graphics — to be fair, it ran on an 80286 processor with just 640 K of memory while its texture-mapped, fully 3D rival demanded at least an 80386 with 2 MB — it remained conceptually unlike anything that had come before in daring to cast you as an ordinary mortal, weak and scared and alone, for whom any aspirations toward glory quickly turn into nothing more than a desperate desire to just escape the mansion. For all that it threw the Call of Cthulhu rules completely overboard, it retained this most fundamental aspect of its inspiration, bringing Chaosium’s greatest innovation to a digital medium for the first time. It’s not always impossible to kill the monsters in Alone in the Dark — often it’s even necessary to do so — but, with weapons and ammunition scarce and your health bar all too short, doing so never fails to feel like the literal death struggle it ought to. When you do win a fight, you feel more relieved than triumphant. And you’re always left with that nagging doubt in the back of the mind as you count your depleted ammo and drag your battered self toward the next room: was it worth it?


The legacy of this brave and important game is as rich as that of any that was released in its year, running along at least three separate tracks. We’ll begin with the subsequent career of Frédérick Raynal, its original mastermind.

The seeds of that career were actually planted a couple of weeks before the release of Alone in the Dark, when Raynal and others from Infogrames brought a late build of it to the European Computer Trade Show in London. There he met the journalist Dany Boolauck once again, learning in the process that Boolauck had switched gigs: he had left his magazine and now worked for Delphine Software, one of Infogrames’s French competitors. Delphine had recently lost the services of their biggest star: Éric Chahi, the auteur behind the international hit Another World. As his first assignment in his own new job, Boolauck had been given the task of replacing Chahi with a similarly towering talent. Raynal struck him as the perfect choice; he rather resembled Chahi in many respects, what with his very French aesthetic sensibility, his undeniable technical gifts, and his obsessive commitment to his work. Boolauck called in Paul de Senneville, the well-known composer who had launched Delphine Software as a spinoff from his record label of the same name, to add his dulcet voice to the mix. “We wish to place you in a setting where you will be able to create, where you will not be bullied, where we can make you a star,” said the distinguished older gentleman. “We want to give free rein to the fabulous talent you showed in Alone in the Dark.” When Raynal returned to Lyon to a reprimand from Bruno Bonnell for letting his game’s planned release date slip by a week, the contrast between his old boss and the possible new one who was courting him was painted all too clearly.

Much to Raynal’s dismay, Bonnell was already pushing him and the rest of the team that had made the first Alone in the Dark to make a sequel as quickly as possible using the exact same engine. One Friday just before the new year, Bonnell threw his charges a party to celebrate what he now believed would go down in history as the year when his struggling company turned the corner, thanks not least to Raynal’s game. On the following Monday morning, Raynal knocked on Bonnell’s office door along with three other members of the newly christened Alone in the Dark 2 team, including his most longstanding partner Didier Chanfray. They were all quitting, going to work for Delphine, Raynal said quietly. Much to their surprise, Bonnell offered to match Delphine’s offer, the first overt sign he’d ever given that he understood how talented and valuable they really were. But his counteroffer only prompted Delphine to raise the stakes again. Just after New Years Day, Bonnell bowed out of the bidding in a huff: “You want to leave? Goodbye!”

A couple of weeks later, the videogame magazine Génération 4 held an awards ceremony for the previous year’s top titles at Disneyland Paris. Everyone who had been involved with Alone in the Dark, both those who still worked at Infogrames and those who didn’t, was invited. When, as expected, it took the prize for top adventure game, Bruno Bonnell walked onto the stage to accept the award on behalf of his company. The departure of Raynal and crew being the talk of the industry, the room held its collective breath to see what would happen next. “My name is Bruno Bonnell,” he said from behind the rostrum. “I’d like to thank God, my dog, my grandmother, and of course the whole team at Infogrames for a beautiful project.” And with that he stumped offstage again.

It hadn’t been a particularly gracious acceptance speech, but Raynal and his colleagues nonetheless had much to feel good about. Dany Boolauck and Paul de Senneville were true to their word: they set Raynal up with a little auteur’s studio all his own, known as Adeline Software. They even allowed him to run it from Lyon rather than joining the rest of Delphine in Paris.

Naturally, all of the Alone in the Dark technology, along with the name itself and the Chaosium license (whatever that was worth), stayed with Infogrames. Raynal and his colleagues were thus forced to develop a new engine in the style of the old and to devise a fresh game idea for it to execute. Instead of going dark again, they went light. Released in 1994, Little Big Adventure (known as Relentless: Twinsen’s Adventure in North America) was a poetic action-adventure set in a whimsical world of cartoon Impressionism, consciously conceived by Raynal as an antidote to the ultra-violent Doom mania that was sweeping the culture of gaming at the time. He followed it up in 1997 with Little Big Adventure 2 (known as Twinsen’s Odyssey in North America). Although both games were and remain lovely to look at, Raynal still struggled to find the right balance between the art and the science of game design; both games are as absurdly punishing to play as they are charming to watch, with a paucity of save points between the countless places where they demand pin-point maneuvering and split-second timing. This sort of thing was, alas, something of a theme with the French games industry for far too many years.

This, then, is one legacy of Alone in the Dark. Another followed on even more directly, taking the form of the two sequels which Infogrames published in 1993 and 1994. Both used the same engine, as Bruno Bonnell had demanded in the name of efficiency, and both continued the story of the first game, with Edward Carnby still in the role of protagonist. (Poor Emily Hartwood got tossed by the wayside.) But, although Hubert Chardot once again provided their scripts, much of the spirit of the first game got lost, as the development team began letting the player get away with much more head-to-head combat. Neither sequel garnered as many positive reviews or sales as the original game, and Infogrames left the property alone for quite some time thereafter. A few post-millennial attempts to revive the old magic, still without the involvement of Raynal, have likewise yielded mixed results at best.

But it’s with Alone in the Dark‘s third legacy, its most important by far, that we should close. For several years, few games — not even its own sequels — did much to build upon the nerve-wracking style of play it had pioneered. But then, in 1996, the Japanese company Capcom published a zombie nightmare known as Resident Evil for the Sony Playstation console. “When I first played Resident Evil,” remembers Infogrames programmer Franck de Girolami, “I honestly thought it was plagiarism. I could recognize entire rooms from Alone in the Dark.” Nevertheless, Resident Evil sold in huge numbers on the consoles, reaching a mass market the likes of which Alone in the Dark, being available only on computers and the 3DO multimedia appliance, could never have dreamed. In doing so, it well and truly cemented the new genre that became known as survival-horror, which had gradually filtered its way up from the obscure works of a poverty-stricken writer to a niche tabletop RPG to a very successful computer game to a mainstream ludic blockbuster. Culture does move in mysterious ways sometimes, doesn’t it?

(Sources: the books La Saga des Jeux Vidéo by Daniel Ichbiah, Designers & Dragons: A History of the Roleplaying Game Industry, Volume 1 by Shannon Appelcline, and Alone in the Dark: The Official Strategy Guide by Johan Robson; Todd David Spaulding’s PhD thesis H.P. Lovecraft & The French Connection: Translations, Pulps, and Literary History”; Computer Gaming World of February 1993; Amiga Format of June 1991; Edge of November 1994; Retro Gamer 98. Online sources include Adventure Europe‘s interview with Frédérick Raynal, Just Adventure‘s interview with Hubert Chardot, and the video of Frédérick Raynal’s Alone in the Dark postmortem at the 2012 Game Developers Conference. Note that many of the direct quotations in this article were translated by me into English from their French originals.

The original Alone in the Dark trilogy is available as a package download at GOG.com.)

 
 

Tags: , , ,

Interplay Takes on Trek

Original-series Star Trek is the only version I’ve ever been able to bring myself to care about. Yet this Star Trek I once cared about a great deal.

Doubtless like many of you of a similar age, I grew up with this 1960s incarnation of the show — the incarnation which its creator Gene Roddenberry so famously pitched to the CBS television network as Wagon Train to the Stars, the one which during my childhood was the only Star Trek extant. Three or four Saturdays per year, a local UHF television station would run a Star Trek marathon, featuring nine or ten episodes back to back, interspersed with interviews and other behind-the-scenes segments. Strange as it now sounds even to me in this era when vintage media far more obscure than Star Trek is instantly accessible at any time, these marathons were major events in my young life. I particularly loved the give and take on the bridge of the starship Enterprise during episodes such as “Balance of Terror,” which were heavily inspired by the naval battles of World War II. Upon realizing this, I became quite the little war monger for a while there, devouring every book and movie I could find on the subject. Even after it had slowly dawned on me that in the final reckoning the death and suffering brought on by war far outweigh any courage or glory it might engender, the fascination with history which had been thus awakened never died.

I loved the Star Trek movies of the 1980s as well. Young though I was, I recognized the poignancy inherent in watching the now middle-aged cast cram their increasingly substantial frames back into the confines of their Starfleet uniforms every couple of years. Yes, this made effortless fodder for the late-night comedians, but there was also a wry wisdom to these movies that one doesn’t usually find in such blockbuster fare, as the actors’ aging off-screen selves merged with their onscreen personas in a way we don’t often see in mainstream mass media. Think, for example, of the scene in Star Trek II: The Wrath of Khan where McCoy comes to visit Kirk and present him with his first pair of reading glasses. Decades before I fully understood what that moment — not to mention an expanding middle-aged waistline! — means in real life, I could sense the gravitas of the scene. I credit this side of Star Trek with showing me that there is as much drama and interest in ordinary life as there is in fantastic adventures in outer space. It primed me for the evening I begrudgingly opened Ethan Frome for my English class, and proceeded to devour it over the course of the next several rapt, tear-streaked hours. My English teacher was right, I realized; books without any spaceships or dragons in them really could be pretty darn great. Some years later, I took my bachelor’s degree in literature.

It must have been about the time I was discovering Ethan Frome that Star Trek: The Next Generation debuted on television. Like most of my peers, I was hugely excited by the prospect, and tuned in eagerly to the first episode. Yet I was disappointed by what I saw. The new incarnation of the Enterprise seemed cold and antiseptic in comparison to the old ship’s trusty physicality. Nor did I care for the new crew, who struck me as equally bland and bloodless. Being smart enough even at this tender age to recognize that fictional personalities, like real ones, need time to ripen and deepen, I gave the show another chance — repeatedly, over the course of years. But it continued to do nothing for me. Instead of Wagon Train to the Stars, this version struck me as Bureaucrats in Space.

All of this, I’ll freely admit, may have more to do with the fact that The Next Generation came along after I had passed science fiction’s golden age of twelve than anything else. Nevertheless, it does much to explain why I’m the perfect audience for our subject of today: the two Star Trek adventure games which Interplay made in the early 1990s. Throwbacks to the distant past of the franchise even when they were brand new, they continue to stand out from the pack today for their retro sensibilities. Fortunately, these are sensibilities which I unabashedly share.



Star Trek hadn’t been well-served by commercial computer games prior to the 1990s. Corporate nepotism had placed its digital-game rights in the slightly clueless hands of the book publisher Simon & Schuster, which was owned, like the show’s parent studio Paramount Pictures, by the media conglomerate known as Gulf and Western. The result had been a series of games that occasionally flirted with mediocrity but more typically fell short of even that standard. Even as each new Star Trek film topped the box-office charts, and even after Star Trek: The Next Generation became the most successful first-run series in the history of syndicated television, Simon & Schuster’s games somehow managed not to become hits. At decade’s end, Paramount granted the rights to a game based on the film Star Trek V: The Final Frontier to the dedicated computer-game publisher Mindscape, but the end product proved little better than what had come before in terms of quality or commercial success. Still, the switch to Mindscape did show that an inkling of awareness of the money all these half-assed Star Trek games were leaving on the table was dawning at last upon Paramount.

As the new decade began, the silver anniversary of the original series’s first broadcast on September 8, 1966, was beginning to loom large. Paramount decided to celebrate the occasion with something of a media blitz, anchored by a two-hour television special that would air in 1991 as close as possible to the show’s exact 25th anniversary. For the first time on this occasion, Paramount decided to make digital games into a concerted part of their media strategy rather than an afterthought. They signed a contract with the Japanese company Konami to make a game, entitled simply Star Trek: 25th Anniversary, for the Nintendo Entertainment System, the heart of the videogame mass market, and for the Nintendo Gameboy, the hot new handheld videogame system. Rather than the Next Generation crew or even the original Enterprise crew in their most recent, most rotund incarnations, these games were to wind the clock all the way back to those heady early days of 1966, when Captain Kirk was still happy to appear on camera with his shirt off.

That deal still left a space for an anniversary title in the computer-game market. Said market was, it was true, much smaller than the one for Nintendo games, but it was notable for its older, more well-heeled buyers willing to pay more money for more ambitious games. Yet computer-game publishers proved more reluctant to sign on for the project than the broad popularity of the Star Trek brand in general might lead one to believe.

It didn’t require the benefit of hindsight to see that the Star Trek franchise, although it was indeed more popular than ever before, was going through a period of transition in 1990. The Next Generation had been on the air for three seasons now and was heading into a fourth; it was thus about to exceed the on-air longevity of the series that had inspired it. Meanwhile the cast of that older series were bowing to the realities of age at last; it had been announced that Star Trek VI: The Undiscovered Country, due for release in late 1991, was to be the last feature film in which they would star. A time when the Next Generation crew would become the default face of Star Trek, the original crew creaky anachronisms, was no longer impossible to imagine.

Given this passing of the torch that seemed to be in progress, most computer-game publishers were skeptical of Paramount’s plans for games featuring the original Enterprise and its crew in their youngest incarnations. They felt that this version of Star Trek was already all but dead in commercial terms, what with the success of all of the franchise’s more recent productions.

Brian Fargo of Interplay Entertainment was among the few who didn’t agree with this point of view. He pitched a computer game to Paramount that would share a name with Konami’s efforts, but would otherwise be a completely separate experience. Aided by his natural charm and the relative disinterest of most of Interplay’s competitors, he made the deal.

Disinterested competitors or no, it was quite a coup for his company, nowhere close to the largest or most prominent in its industry, to secure a license to make Star Trek games — especially given that the deal was made just months after Interplay had acquired the rights to another holy totem of nerd culture, The Lord of the Rings. While the Tolkien games would prove rather a disappointment, the Star Trek license would work out better all the way around.

Interplay signed an open-ended contract with Paramount which allowed them to make Star Trek games all the way until the year 2000, with some significant restrictions: they would be subject to the studio’s veto power over any and all of their aspects, and they could be set only in the time of Captain Kirk and company’s first five-year mission. With these restrictions in mind, Interplay set out to make a game that would be slavishly faithful to the original television series’s format. Instead of a single epic adventure, the game would consist of eight independent “episodes,” each roughly equivalent in plot complexity and geographic scope to those that had aired on television back in the day.

The structure of each episode would be the same: the Enterprise would be called upon by Starfleet to handle some new crisis at the episode’s beginning, whereupon the player would have to warp to the correct star system and engage in some action-oriented space combat, before beaming down to the real heart of the problem and sorting it all out in the guise of an adventure game. Interplay noted that the episodic format could make for a refreshing change from the norm in adventure games, being amenable to a more casual approach. Each episode would be designed to be completable in an evening; after finishing one of them, you could start on the episode that followed the next day, the next week, or the next month, without having to worry about all of the plot and puzzle threads you left dangling last time you played. From Fargo’s perspective, the episodic structure also had the advantage that each part of the game could be designed without much reference to or dependence on any of the others; this made things vastly easier from the standpoint of project management.

Fargo turned to a familiar source for the episodes’ scripts: Michael Stackpole, a member of the Arizona Flying Buffalo fraternity who had played a leading role on Interplay’s Wasteland CRPG and contributed to such other titles as Neuromancer. Stackpole had been busying himself recently with writing tie-in novels set in the universe of the BattleTech tabletop-game franchise. He thus thought that he knew what to expect from working with a licensed property, but he was unprepared for the degree of micromanagement that a bureaucratic giant like Paramount, stewarding one of the most valuable media properties of the age, was willing to engage in. He submitted scripts for fifteen episodes for a game that was anticipated to contain only eight, assuming that should surely cover all his bases; Interplay and Paramount could decide between themselves which eight they actually wanted to include.

To everyone’s shock, Paramount outright rejected all but a handful of them weeks later, usually for the most persnickety of reasons. Interplay’s frustration was still evident in a preview of the game published much later in Computer Gaming World magazine, which noted that “the film studio decided against plot elements derived from episodes which were already part of the Star Trek legend.” With Stackpole having returned to writing his novels, Fargo brought in Elizabeth Danforth, another Flying Buffalo alumnus who had worked with Interplay before, to write more episodes and shepherd them through the labyrinthine approval process.

All of this was happening during one of the most chaotic periods in Interplay’s history. Their distributor Mediagenic had just collapsed, defaulting on hundreds of thousands of dollars they had owed to Interplay and destroying the company’s precious pipeline to retail. The Lord of the Rings game, which was supposed to have been their savior, missed the Christmas 1990 buying season and, when it did finally ship early the following year, met with lukewarm reviews and disappointing sales. Only the strategy game Castles, an out-of-left-field hit from a third-party developer, kept them alive.

Amidst it all, the team making Star Trek: 25th Anniversary kept plugging away — but, inevitably, the game fell behind schedule. September of 1991 arrived, bringing with it the big television special and the Nintendo Entertainment System game, but Interplay’s own tie-in product remained far from complete. It didn’t ship until March of 1992, by which time all of the anniversary hoopla was in the past. Interplay’s game had all the trappings of an anticlimax; it really should have been known as Star Trek: 26th Anniversary, noted more than one commentator pointedly. For those inside the company, the story of the game was taking on some worrisome parallels to that of their Lord of the Rings title: a seeming surefire hit of a high-profile licensed game that arrived late and wound up underwhelming everyone.

They needn’t have worried. Star Trek: 25th Anniversary was a much more polished, more fully realized evocation of its source material than The Lord of the Rings had been, and it came at one of the Star Trek franchise’s high-water marks in popularity. Star Trek VI, which had hit theaters just three months before Interplay’s game, had become everything one could have hoped for from the original crew’s valedictory lap, garnering generally stellar reviews and impressive box-office receipts. Meanwhile The Next Generation was now in its fifth season on television and more popular than ever. The only shadow over proceedings was the death of Gene Roddenberry, the creator of Star Trek, on October 24, 1991. Yet even that event was more help than hindrance to the Interplay game’s commercial prospects, in that it created an appetite among wistful fans to look back to the franchise’s beginnings.

Interplay dedicated Star Trek: 25th Anniversary to Gene Roddenberry.

Indeed, Star Trek: 25th Anniversary thrived in this febrile atmosphere of contemporary success tinged with nostalgia. It became the biggest Interplay hit since Battle Chess, selling over 250,000 copies in all and doing much to set the company’s feet back on firm financial ground after the chaos of the previous couple of years.



The game continues to stand up fairly well today, with a few caveats. Undoubtedly its least satisfying aspect is the space-combat sequence that must be endured at the beginning of each episode. Perhaps not coincidentally, this is one of the few places where the game isn’t faithful to the spirit of Star Trek.

Science fiction’s two most successful media franchises take very different approaches to battles in outer space: while Star Trek portrays its combatants as lumbering naval vessels, jockeying for position in a slow-paced tactical game of cat and mouse, Star Wars looks to the skies of World War II for inspiration, opting for frenetic dog fights in space. But 25th Anniversary goes all-in for Star Wars instead of Star Trek in this respect; the Enterprise turns into Luke Skywalker’s X-Wing fighter, dodging and weaving and spinning on a dime in response to the joystick. The reason for the switch can be summed up in two words: Wing Commander. Origin Systems’s cinematic action game of outer-space dog-fighting was taking the market by storm as Interplay was starting work on their own science-fiction game, and the company wanted to capitalize on their rival’s success. They described their game as “Sierra meets Wing Commander” at early trade-show presentations, and even made it possible to engage in randomized fights just for fun by visiting star systems other than those to which you’ve been directed, just in case the fighting you get to do in the episodes proper isn’t enough for you.

That was quite the stretch; the combat in 25th Anniversary really isn’t much fun as anything more than an occasional palate cleanser, and it’s hard to imagine anyone voluntarily deciding to look for more of it. Not only does this part of the game clash with its faithfulness to Star Trek in just about every other respect, but it doesn’t work even on its own terms. The controls are awkward, it’s hard to understand where your enemies are in relation to you, and it’s simply too hard — a point I’ll be returning to later. For now, suffice to say that Star Trek: 25th Anniversary ain’t no Wing Commander.

The worst part by far of Star Trek: 25th Anniversary.

Thankfully, the rest of the game — the “Sierra” in Interplay’s pithy formulation — is both more engaging and more faithful to the Star Trek of old. When you leave the Enterprise‘s bridge, the game turns into a point-and-click graphic adventure, marking the first time Interplay had dabbled in the format since Tass Times in Tonetown back in 1986. You control Kirk directly, but Spock, McCoy, and some poor expendable redshirt also come along, ready to offer their advice and use their special talents when needed — or, in the case of the redshirt, to take one for the team, dying so that none of the regulars have to do so.

The interface can be a little confusing at first; it’s not always clear when you should be “using” Spock or McCoy themselves on something and when you should be using their tricorders. But you start to get a feel for things after just a few minutes, and soon the interface fades into the background of what could stand on its own as a solid little graphic adventure — or, rather, eight solid little mini-adventures. Some of the puzzles can get a bit fiddly, but there are no outrageously unfair ones. The episodic nature of the game does much to make it manageable by limiting the possibility space you need to explore in order to solve any given puzzle; most of the episodes play out over just half a dozen or so locations.

Still, what elevates a fairly workmanlike adventure game to something far more memorable is the Star Trek connection. This is clearly a game made by and for fans of the source material. If you count yourself among them, you almost can’t help but be delighted. The writers do a great job of evoking the characters we know and love; McCoy lays into Spock like the old racist country doctor he is, Spock plays such a perfect straight man that one can’t help but suspect that he’s laughing up his sleeve behind his facade of “logic,” and Kirk still loves to egg them both on and enjoy the fireworks.

Star Trek: 25th Anniversary apes the look of its source material down to the title card that opens each episode.

The interactive episodes are true to the rhythms of their non-interactive antecedents; each one begins with a title card superimposed over a stately Enterprise soaring toward its latest adventure, and ends with some humorous banter on the bridge and a final command from Kirk of “Warp factor 4!” to send it on its way to the next. Even the visuals, presented in slightly pixelated low-res VGA, conjure up the low-rent sets of the show; more photo-realistic graphics, one suspects, would only ruin the effect. For the music, George “The Fat Man” Sanger and Dave Govett, whose work was everywhere during this period — they scored Wing Commander and Ultima Underworld as well, among many others — mix the familiar Star Trek theme with their own period-perfect motifs. The only things missing from their score in comparison to that of the original show are those oh-so-sixties orchestral stabs at dramatic moments. (There does come a point, Sanger and Govett must have decided, when nostalgia descends into outright cheese.)

It’s true that the episodes work more on the level of pastiche than that of earnest attempts at storytelling — another reason that enjoying this game probably does require you be a fan of vintage Star Trek. Most of the scripts read like a Mad Libs take on the original series, mixing and matching its most familiar tropes. The crew has to shut down another misguided computer (a la “A Taste of Armageddon”), engage in some gunboat diplomacy with the Romulans (“The Enterprise Incident”), and negotiate an earthly religious mythos transplanted to another planet (“Who Mourns for Adonais?”). Harry Mudd, the intergalactic con man whose antics featured in two episodes of the original series, makes a third appearance here. Even Carol Marcus, scientist and Kirk paramour, shows up to foreshadow the major role she’ll later play in the movie Star Trek II.

Star Trek: 25th Anniversary in its graphic-adventure mode. The gang’s all here, including the poor terrified red shirt hiding behind a pillar.

If none of the interactive episodes can challenge the likes of “The City on the Edge of Forever” for the crown of Best of Trek, they’re certainly far less embarrassing than most of what the series produced during its painfully bad third season. They encompass the full tonal palette of the show, from screwball comedy to philosophical profundity. The graphic-adventure format does force a shift in emphasis away from dialog and action to more cerebral activities — the Kirk on television never had to slow down to solve set-piece logic puzzles like some of the ones we see here — but that shift is entirely understandable.

Unfortunately, all of the good will the game engenders is undermined to a considerable extent by one resoundingly terrible design decision — a decision that’s ironically built upon a foundation of very good design choices. Each episode permits multiple solutions to most of the problems it places before you; this is, of course, a good thing. At the end of each episode, assuming you don’t get yourself killed, you receive an evaluation from Starfleet Command in the form of a percentile grade. You’re rewarded with a better grade if you’ve managed to keep the poor redshirt who beamed down with you alive — this game’s writers show far more compassion for the expendable crew members than the original series’s writers ever did! — and if you’ve accomplished things with a minimum of violence — i.e., if you’ve kept your metaphorical and sometimes literal phasers on “stun” rather than “kill.” All of this too is a good thing, seeming evidence of a progressive design sensibility that’s become ubiquitous today, when countless games let you finish each scenario with a bronze, silver, or gold star, allowing you to be exactly as completionist and perfectionist as you choose to be.

But now the bad part comes in. The final grades you receive on the episodes affect the performance of your crew during the remaining space-combat sequences, which themselves become steadily more difficult as you progress through the game. In fact, the final battle is so hard that you virtually have to have scored 100 percent on all of the preceding episodes to even have a chance in it. It turns out that the seeming easygoing attitude of the game, encouraging you to do better but letting you slide if you just want to move on through the episodes, has been a colossal lie, an ugly trap to get you 90 percent of the way to the finish line and then stop you cold. This is like a caricature of awful, retrograde game design — something even Sierra at their absolute nadir would have thought twice about. Either tell the player at the end of the episode that she just hasn’t done well enough and make her do it again, or honor your promise to let her continue with a less than stellar score. Don’t lie to her about it and then cackle about how you got her in the end.

Pro tip: this is not good enough to get you through the game.

Not only is this design decision terrible on its own terms, but it clashes with all of the implications of Interplay’s own characterization of Star Trek: 25th Anniversary as a more casual sort of adventure game than the norm, one that will let you play through a satisfying episode in a single relaxing evening. Interplay heard about this cognitive dissonance from their fans — heard so much about it that they begrudgingly issued an optional patch that let players skip past the combat sequences altogether by triggering a hot key. It wasn’t the most elegant solution, but it was better than nothing.

This discordant note aside, the worst complaint you could make about Star Trek: 25th Anniversary in 1992 is one that doesn’t apply anymore today: that it was just a bit short in light of its $40 street price. And yet, worthy effort though Interplay’s first Star Trek game is on the whole, they would comprehensively top it with their second.



Given 25th Anniversary‘s commercial success and the open-ended license Interplay had acquired from Paramount, a sequel was rather inevitable. There wasn’t much point in making bold changes to a formula that had worked so well. Indeed, when they made the sequel they elected to change nothing whatsoever on the surface, retaining the same engine, the same episodic structure, and even the same little-loved combat sequences. Yet when we peer beneath the surface we see the product of a development team willing to learn from their mistakes. As sometimes happens in game development, the fact that the necessary enabling technology was already in place in the form of an existing engine allowed design in the abstract to come even more to the fore in the sequel. The end result is a game that, while hardly a transformative leap over its predecessor, is less frustrating, more narratively ambitious, and even more fun to play.

Although Star Trek: Judgment Rites continues with the episodic structure of its predecessor, it adapts it to a format more typical of television shows of the 1990s than those of the 1960s. An overarching “season-long” story arc is woven through the otherwise discrete episodes, to come to a head in a big finale episode. This gives the game a feeling of unity that its predecessor lacks.

Even more welcome, however, is a new willingness within the individual episodes to move beyond pastiche and into some narratively intriguing spaces of their own. Virtually all of Judgment Rites‘s episodes, written this time by the in-house Interplay employees Scott Bennie and Mark O’Green in addition to the returning contractors Michael Stackpole and Elizabeth Danforth, mix things up rather than stick with the unbending 25th Anniversary formula of a space combat followed by Kirk, Spock, McCoy, and a semi-anonymous redshirt beaming down somewhere. Combat this time around is neither as frequent nor as predictably placed in the episodes, and the teams that beam down now vary considerably; Scotty, Uhura, and Sulu all get at least one chance of their own to come along and use their special talents.

My favorite episode in Judgment Rites also happens to be the longest and most complex in either of the games. In Bennie’s “No Man’s Land,” a team from the Enterprise beams down to a planet which is being forced to reenact a simulacrum of Earth’s World War I by Trelane, the childish but almost infinitely powerful demigod who was introduced in the original-series episode “The Squire of Gothos.” As his inclusion would indicate, “No Man’s Land” is very aware of Star Trek lore. It’s plainly meant partially as an homage to the original show’s occasional “time-travel” episodes, like “Tomorrow is Yesterday,” “A Piece of the Action,” or “Patterns of Force.” These were beloved by fans for giving the familiar crew the chance to act out a bit in an entirely different milieu. (They were beloved by the show’s perpetually cash-strapped producers for another reason: they let them raid their studio’s stash of stock sets, props, and costumes).

Yet “No Man’s Land” transcends homage to become a surprisingly moving meditation on the tragedy of a pointless war.

Another standout is Stackpole’s “Light and Darkness,” a pointed allegory about the folly of eugenics.

In addition to showing far more confidence in its storytelling, Judgment Rites also addresses the extreme difficulty of the space-combat sequences in its predecessor and the false promise that is letting you continue after completing an episode with a less-than-perfect score. You now have a choice between no combat at all, easy combat, and hard combat. The middle setting is calibrated just about right. Combat at this level, while still a long way from the likes of Wing Commander, becomes an occasional amusing diversion that doesn’t overstay its welcome instead of an infuriating brick wall that kills the rhythm of the game. And, at this level, moving on from any given episode with a score of less than 100 percent is no longer a fool’s gambit.

Although a better game than its predecessor in almost every respect, Judgment Rites couldn’t muster the same sales. It didn’t ship until December of 1993 — i.e., almost two full years after 25th Anniversary — and by that time the engine was beginning to show its age. Nor did it help that Interplay themselves undercut its launch by releasing a “talkie” version of the first game on CD-ROM just a month later.

That said, it’s not hard to understand Interplay’s eagerness to get the talkie version onto the market. In what can only be described as another major coup, Interplay, working through Paramount, brought in the entirety of the original cast to voice their iconic roles. At a time when many CD-ROM-based games were still being voiced by their programmers, it promised to be quite a thrill indeed to listen to the likes of William Shatner, Leonard Nimoy, and Deforest Kelley in the roles that had made them famous.

The reality was perhaps a little less compelling than the promise. While no one would ever accuse any member of the show’s cast of being a master thespian in the abstract, they had been playing these roles for so long that doing so once more for a computer game ought to have presented little problem on the face of it. Yet they plainly struggled with this unfamiliar medium. Their voice acting runs the gamut from bored to confused, but almost always sounds like exactly what it is: actors in front of microphones reading lines on a page. It seems that none of them knew anything about the stories to which the lines related, which can only be construed as a failure on Interplay’s part — albeit one perhaps precipitated by the sharply limited amount of time during which they had the actors at their disposal. Over the course of a scant few days, the cast was asked to voice all of the dialog not for one but for two complete games; the voices for a CD-ROM version of Judgment Rites were recorded at the same time. And they had to do it all bereft of any dramatic context whatsoever.

Somewhat disapointing though the final result is, these sessions represent a melancholy milestone of their own in Trek history, marking the last time the entire cast to the original show was assembled for a new creative project. As such, the talkie versions of these games are the last gasps of an era.

Personally, though, I prefer the games without voices — not only because of the disappointing voice work but because Interplay chose to implement it in a really annoying way, with Kirk/Shatner saying each choice in every dialog menu before you choose one. Interplay, like most of their peers, was still scrambling to figure out what did and didn’t work in this new age of multimedia computing.

Despite holding a license to the original series for the balance of the decade, Interplay would never release another game set in this era of Star Trek after the talkie version of Judgment Rites shipped in March of 1994. The company did work intermittently on an ambitious 3D action-adventure featuring Kirk and the rest of the classic crew, tentatively entitled Secret of Vulcan Fury, near the end of the decade, but never came close to finishing it. Gamers and Trekkies were moving on, and the newer incarnations of the show were becoming, just as some had predicted they would, the default face of the franchise. Indeed, no standalone Star Trek game since the two Interplay titles discussed in this article has revisited the original show. This fact only makes 25th Anniversary and especially Judgment Rites all the more special today.



That would make for a good conclusion to this article, but we do have one more thing to cover — for no article about Interplay’s takes on classic Trek could be complete without the media meme they spawned.

Like a fair number of other memes, this one involves William Shatner, for more than half a century now one of the odder — and more oddly endearing — characters on the media landscape. Back when he was a struggling young actor trying to make it in Hollywood, it was apparently drilled into him by his agents that he should never, ever turn down paying work of any kind. He has continued to live by this maxim to this day. Shatner will do absolutely anything if you pay him enough: pitch any product, sing-talk his way through fascinatingly terrible albums, “write” a new memoir every couple of years along with some of the worst science-fiction novels in history. He’s the ultimate cultural leveler, seeing no distinction between a featured role in a prestigious legal drama and one in a lowest-common-denominator sitcom based on someone’s Twitter feed.

And yet he manages to stay in the public’s good graces by doing it all with a wink and a nod that lets us know he’s in on the joke; when he goes on a talk show to plug his latest book, he can’t even be bothered to seriously pretend that he actually wrote it. He’s elevated crass commercialism to a sort of postmodern performance art. When the stars align, the kitschy becomes profound, and the terrible becomes wonderful. (“Why is this good?” writes a YouTube commenter in response to his even-better-than-the-original version of “Common People.” “It has no right to be this good.”) For this reason, as well as because he’s really, truly funny — one might say that he’s a far better comedian than he ever was an actor — he gets a pass on everything. At age 88 as of this writing, he remains the hippest octogenarian this side of Willie Nelson.

In keeping with his anything-for-a-buck career philosophy, Shatner is seldom eager to spend much time second-guessing — much less redoing — any of his performances. His reputation among media insiders as a prickly character with a taste for humiliation has long preceded him. It’s especially dangerous for anyone he perceives as below him on the totem pole to dare to correct him, challenge him, or just voice an opinion to him. Like a dog, he can smell insecurity, and, his eagerness to move on to the next gig notwithstanding, he’s taken a malicious delight in tormenting many a young assistant director. Craig Duman, the Interplay sound engineer who was given the task of recording Shatner’s lines for the CD-ROM versions of 25th Anniversary and Judgment Rites, can testify to this firsthand.

The problem began when Shatner was voicing the script for the first episode of Judgment Rites. Coming to the line, “Spock, sabotage the system,” he pronounced the word “sabotage” rather, shall we say, idiosyncratically: pronouncing the vowel of the last syllable like “bad” rather than “bod.” A timid-sounding Duman, all too obviously overawed to be in the same room as Captain Kirk, piped up to ask him to say the line again with the correct pronunciation — whereupon Shatner went off. “I don’t say sabotahge! You say sabotahge! I say sabotage!” (You say “potato,” I say “potahto?”) His concluding remark was deliciously divaish: “Please don’t tell me how to act. It sickens me.”


This incident would have remained an in-joke around Interplay’s offices had not an unknown employee from the sound studio they used leaked it to the worst possible person: morning-radio shock jock Howard Stern. Driving to work one morning, Brian Fargo was horrified to hear the outtake being broadcast across the country by this self-proclaimed “King of All Media.” Absent the “it sickens me,” the clip wouldn’t have had much going for it, but with it it was absolutely hilarious; Stern played it over and over again. Fargo was certain he had just witnessed the death of one of Interplay’s most important current projects.

He was lucky; it seems that Shatner wasn’t a regular Howard Stern listener, and didn’t hear about the leak until after both of the talkies had shipped. But the clip, being short enough to encapsulate in a sound file manageable even over a dial-up connection, became one of the most popular memes on the young World Wide Web. It also found a receptive audience within Hollywood, where plenty of people had had similar run-ins with Shatner’s prickly off-camera personality. It finally made its way into the 1999 comedy film Mystery Men, where Ben Stiller parrots, “Please don’t tell me how to act. It sickens me,” on one occasion, and Janeane Garofalo later inserts a pointed, “You say sabotahge! I say sabotage!”

Thanks to Howard Stern, Mystery Men, and the mimetic magic of the Internet, this William Shatner outtake has reached a couple of orders of magnitude more people than ever played the game which spawned it; most of those who have engaged with the meme have no idea of its source. If it seems unfair that this of all things should be the most enduring legacy of Interplay’s loving re-creations of the Star Trek of yore, well, such is life in a world of postmodern media. As Shatner himself would attest, just reaching people, no matter how you have to do it, is an achievement of its own. And if you can make them laugh while you’re about it, so much the better.

(Sources: Computer Gaming World of December 1991, May 1992, March 1994, and May 1994; Questbusters of April 1992; Origin Systems’s internal newsletter Point of Origin of December 9 1991; the special video features included with the Star Trek: Judgment Rites Collector’s Edition. Online sources include Matt Barton’s interview with Brian Fargo and Fargo’s appearance on Angry Centaur Gaming’s International Podcast. Finally, some of this article is drawn from the collection of documents that Brian Fargo donated to the Strong Museum of Play.

Star Trek: 25th Anniversary and Judgment Rites are both available for purchase from GOG.com.)

 

Tags: , , ,