RSS

Tag Archives: holland

The Space Sim’s Last Hurrah


This article tells part of the story of space sims.

Amidst so much else, the 1990s saw the rise and fall of the narrative-driven space sim. The sub-genre was effectively invented in 1990, when Wing Commander dared to add a set-piece story line to the sturdy foundation of the more open-ended British classic Elite. It reached a peak of commercial and critical acceptance in 1994 with Wing Commander III and TIE Fighter, only to fall off the big publishers’ radar completely by shortly after the turn of the millennium. As you regular readers know, I’ve been writing the final installments to a lot of stories recently, a symptom of the period of churn and consolidation in which these histories currently find themselves. Now I’m on the verge of writing my last words on not just a company but a whole category of games as a mainstream commercial force — almost, I’m tempted to say, a whole subculture of gaming, one of the oddest of them of all when you stop to think about it.

Even the phrase “space sim” is kind of strange and misleading. What were these games supposed to be simulating? Definitely not any form of real spaceflight — not when they chose to implement atmospheric drag, meaning that your ship slows down if you let off the throttle in exactly the way that a real vehicle out in the vacuum of space doesn’t. Their developers started with the way space combat was presented in the Star Wars films, which had themselves happily ignored everything we know about the nature of real space travel in favor of dogfights borrowed from old Second World War movies. Then they just piled on whatever seemed fun and interesting to them, which often entailed delving deeper into the same wellspring as George Lucas. (It was no coincidence that Lawrence Holland, one of the foremost practitioners of the space sim, cut his teeth as a game developer on World War II flight simulators.) Space sims were known by that name because of their vibe alone — because they subjectively felt like simulators, no matter how divorced they were from the reality of space travel. (There are lessons to be drawn from this, if we choose to heed them. The fact is that almost every game which is labelled a simulator is less of one than it purports to be. This is worth remembering any time anyone encourages you to take any game too seriously as a reflection of the real world.)

Chris Roberts’s Wing Commander games made the space-sim formula still more uncanny, by interleaving the missions in space with potboiler relationship drama. It may have been weird on the face of it, seemingly more a product of some random butterfly somewhere flapping its wings than anything flown in on the wings of fate, but for the better part of a decade quite a lot of people loved it.

And then they didn’t so much anymore…


Wing Commander III includes a love triangle. Because of course it does…

Being an inveterate hiker when I’m not sitting behind a computer, I can tell you that it’s sometimes harder than you think it ought to be to realize when you’ve reached peak elevation in a landscape. The same is true in the landscape of media. As I noted above, the space sim reached its peak already in 1994, even though it would take a few years for everyone to cotton onto that fact. For this was the year that both the Wing Commander series and LucasArts’s Star Wars space sims, the eternal yin and yang of the sub-genre, released their best-remembered installments.

Wing Commander III: Heart of the Tiger doubled down on creator Chris Roberts’s passion for the cinematic side of the experience by interleaving a fairly workmanlike space-combat game with a semi-interactive movie that featured digitized human actors, among them such established Hollywood talents as Jason Bernard, Malcolm McDowell, John Rhys-Davies, and Tom Wilson. In what was arguably the greatest feat of stunt casting in the history of games, the star of the show was none other than Mark Hamill. Over a decade after he had last portrayed Luke Skywalker on the big screen, he portrayed here another space-fighter jock, the player’s own avatar, Colonel Christopher Blair. The presence of so many recognizable actors garnered Wing Commander III considerable attention in the glossy mainstream press. The “Siliwood” dream of Northern and Southern California joining forces to forge a new form of entertainment was nearing its frenzied peak in tandem with the space sim in 1994. Wing Commander III was widely hailed, notwithstanding its computer-generated sets and general B-movie aesthetics, as a proof of concept for the better, richer interactive movies that were still to come. Hyped inside the industry as the most expensive game yet made, it garnered a rare five-stars-out-of-five review from Computer Gaming World, and sold at least half a million copies in the United States alone, at an average street price of about $70.

If Wing Commander III was trying to capitalize on gamers’ love for Star Wars in some less-than-subtle ways, LucasArts’s TIE Fighter had the advantage of literally being Star Wars, coming out of George Lucas’s very own games studio. It also had the advantage of being a much better, deeper game where it really counted, eschewing digitized actors and soapy relationship drama to focus firmly on the action in the cockpit. It too was given a perfect score by Computer Gaming World, and sold in similar numbers to Wing Commander III, albeit without attracting the same level of attention from the mainstream press.

Alas, it was mostly downhill for the two franchises from there; such is rather the nature of peaks, isn’t it? In early 1996, barely eighteen months after Wing Commander III, Chris Roberts and his employer Origin Systems were ready with Wing Commander IV: The Price of Freedom. Despite the short turnaround time, it represented another dramatic escalation in budget and ambition on the cinematic side of the equation. (The combat engine, with which Roberts by now hardly bothered to concern himself, was largely unchanged.) Mark Hamill and most of the rest of the previous cast were back, for a production that was shot on film this time rather than videotape, on real sets rather than in front of green screens that were filled in with computer-generated backgrounds after the fact. Yet many gamers found the end results to be paradoxically less stunning. The filmed sequences of Wing Commander IV fell into a sort of uncanny valley, being no longer clearly part of a computer game and yet having nowhere near the production values of even the most modest Hollywood features of the standard stripe. Probably more importantly, the Siliwood cultural moment was quickly passing, leaving the game with something of the odor of an anachronism. The mainstream was becoming more interested in the burgeoning World Wide Web than the wonders of multimedia and CD-ROM, even as hardcore gamers were embracing the non-stop action of the first-person-shooter and real-time-strategy genres, having lost patience with the long cutscenes and endless exposition of interactive movies.

For a cost of more than three times that of Wing Commander IIIWing Commander IV sold a third as many copies. Origin’s management told Chris Roberts that any future games in the series would have to scale back the movie angle and try harder to refresh the increasingly stale gameplay. By way of a response, Roberts quit his job at Origin.

From here, the decline was steep for Wing Commander. In September of 1996, the USA television network debuted Wing Commander Academy, a Saturday-morning cartoon featuring the voices of Mark Hamill, Malcolm McDowell, and Tom Wilson among other actors from the last couple of games. All of the parties involved had envisioned the show capitalizing on a hit game. Absent said hit, it disappeared from the airwaves after just thirteen episodes.

The franchise’s last hurrah as a game came with Wing Commander: Prophecy, which appeared at the end of 1997. “Wing Commander III and IV were both great products,” said Prophecy’s producer Adam Foshko, straining hard to be diplomatic toward his predecessor Chris Roberts, “but they are more like unequal halves. This is a much more synergistic product. It’s very team-driven. It’s not one person’s vision, and I think it shows.” At its best, Prophecy really did play better than any Wing Commander in years, evincing the far greater level of attention the team paid to the action in the cockpit. Less positively, the movie sequences were cheesier and more constrained, even as a plan to bring the game fully in line with the hardcore set’s current priorities by adding a multiplayer component ultimately came to naught. When Prophecy didn’t sell well, that was that for Wing Commander as a gaming franchise. The commercial prospects of an expansion pack that the team had been working on — a return to the old “mission disks” that had made Origin a bundle back before the former Luke Skywalker and his Hollywood friends had entered the picture — looked so dire that Origin just dumped the whole thing onto the Internet for free.

Meanwhile Lawrence Holland and his colleagues had been going through some travails of their own. After making a well-received TIE Fighter expansion pack and a “Collector’s CD-ROM” with yet more new missions to fly, Holland left LucasArts on amicable terms to start a studio called Totally Games, taking his technology and most of his team with him. From the average fan’s perspective, this was a distinction without a difference: Totally’s games would still be Star Wars space sims, and they would still be published by LucasArts.

Like their counterparts at Origin, the folks at Totally could totally see the potential in offering a multiplayer mode to keep up with the changing times. But unlike them, they stuck with the program. In fact, the next iteration of their series was designed to be multiplayer first and foremost. Holland and his people spent almost two years finding ways to make multiplayer work reliably despite all of the challenges of the high-latency, dial-up Internet of the era.

The result of those efforts landed with a resounding thud in the spring of 1997, becoming a case study in the dangers of failing to understand your customers. Holland’s X-Wing and TIE Fighter games may not have been interactive movies in the sense of Wing Commander III and IV, but people had nevertheless loved their unfolding campaigns, loved the sense of playing a part in what could easily have been a novel set in the Star Wars Expanded Universe. The ingeniously titled X-Wing vs. TIE Fighter didn’t give them any of that; its single-player mode was little more than a place to practice for multiplayer matches. “The sad part is, I was really looking forward to this game,” wrote Computer Gaming World’s reviewer, echoing the sentiments of thousands upon thousands of deeply disappointed ordinary players. “After the high of TIE Fighter, I wanted another Star Wars experience that would be just as immersive and fun. And while my wish for multiplayer Star Wars action was fulfilled, my hope for an equivalent single-player experience wasn’t.” In a last-ditch attempt to save their baby, Totally put together an expansion pack whose sole purpose was to provide a single-player campaign of the old style. It did so competently enough, but inspired it was not, and it never had much chance of rescuing a base game that was already a fixture of bargain bins by the time the expansion appeared in January of 1998.

In contrast to Wing Commander, however, LucasArts and Totally’s space-sim series was afforded one more kick at the can after 1998. To hear Lawrence Holland talk about it when it was still in development, Star Wars: X-Wing Alliance was the be-all, end-all in space sims. For those who wanted a story-driven campaign, this game’s would be the biggest and best ever. For those who wanted multiplayer action, this game’s multiplayer mode would be more stable and convenient than that of X-Wing vs. TIE Fighter. For those who cared about graphics, this game’s would be the best yet, taking full advantage of the 3D-accelerator cards that were proliferating everywhere. It was an ambitious plan, especially considering that this old-school Star Wars game had to be finished before The Phantom Menace, the first new Star Wars movie in more than a decade and a half, reached theaters in May of 1999, bringing with it an onslaught of next-generation toys and games.

X-Wing Alliance met that goal, being released in March of 1999. The most remarkable thing about it is how many of its other lofty goals it managed to achieve against the strictures of time and budget. The story is almost Wing Commander-like in its elaborateness, presenting for the first time a named, strongly characterized protagonist, a youthful member of a trading family caught between the Rebel Alliance and the Empire. His story is told not only through the usual mission briefings but also through emails and radio chatter full of enough interpersonal drama to warm the cockles of Chris Roberts’s heart. The campaign begins on the ice-planet Hoth, is interwoven with the events of The Empire Strikes Back and Return of the Jedi, and climaxes with you getting to fly the Millennium Falcon at the Battle of Endor. What dedicated Stars Wars fan could resist?


Sadly, further examination of X-Wing Alliance reveals some significant shortcomings. The individual missions are often unpolished, sometimes failing to even convey adequately what their goals are; trying to complete some of them feels like trying to read the designers’ minds. Ironically, this is the same general set of issues that dragged down the original X-Wing, upon which TIE Fighter did such a magnificent job of improving. It’s disheartening to see them making a return at this late date. Like so many flawed games, X-Wing Alliance might have been amazing if it had just been allowed a few more months in the oven.

That said, the biggest obstacle that X-Wing Alliance faced in the marketplace was probably just the tenor of the times. As I already noted, at a time when everyone was excited and optimistic about The Phantom Menace, the new face of Star Wars, this game was old-school. And yet that was only the beginning of the commercial headwinds it faced. Gamers in general were turning away from simulations in droves; real-world flight and combat simulators too, which had in some earlier years accounted for more than 20 percent of the computer-game industry’s total revenues, had now fallen markedly out of favor. Fewer and fewer gamers even owned joysticks anymore. (To what extent this was a cause and to what extent it was a symptom of simulators’ declining fortunes is a matter of debate.) Existing fans and would-be fans of simulations were being tempted away by other action-packed genres that were quicker and easier to pick up and play for the first time, while still offering plenty of long-term rewards for those who stuck with them. It seemed that fewer people had the patience for games that started by asking you to read a thick manual, then required you to go through a veritable digital flight school before you could start playing them for real.

At any rate, by Y2K both Wing Commander and the Star Wars space sims had been consigned by their publishers to the dustbin of history. Other titles in development that had dreamed of competing with the space sim’s dynamic duo head-on suffered the same fate. The most high-profile of the cancellations was a space sim from Sierra that took place in the universe of the recently concluded Babylon 5 television series. Created with heavy input from Christy Marx, a Babylon 5 scriptwriter who had earlier designed a couple of point-and-click adventure games for Sierra, it was supposed to “tart up a tired genre” and “radically change the face of gaming” with “non-linear, non-branching storytelling, a brilliant modular refit job on nearly five hours of [television composer] Christopher Franke’s music, plus an attention to the physics of space travel that will raise the high bar on space-combat games for years to come.” It got to within a few months of completion, got as far as having the box art prepared before falling victim in late 1999 to an uncongenial marketplace and to the chaos inside Sierra that had followed that venerable mom-and-pop company’s purchase by two separate corporate conglomerates in a period of just a few years.

Still, the space-sim diehards did get one last pair of classics from an utterly unexpected source before their favored sub-genre disappeared from the catalogs of the big publishers forever. In fact, many a grizzled joystick jockey will tell you even today that the second of the two Freespace games is the best of its type ever created — yes, better even than the hallowed TIE Fighter.


The first mover without whom Freespace would never have come to be was a native Chicagoan named Mike Kulas, whose early gigs as a game programmer included stints at subLogic of Flight Simulator fame and at Lerner Research, a precursor to the legendary Looking Glass Studios. At the latter workplace, he befriended one Matt Toschlog. “If this is what it means to run a company, we can do it too,” the friends decided after spending two years at the dawn of the 1990s on an ultimately unsatisfying racing game that was sold in the trade dress of Car and Driver magazine. “What’s the worst that could happen? It’ll fail and we’ll have to go back to work for somebody else.” Kulas and Toschlog moved out of the Boston area and back to Champaign, Illinois, also the home of subLogic. Champaign seemed a good place to open a new studio: it had the advantages of fairly cheap rents and a large pool of enthusiastic young tech talent, thanks to the University of Illinois Urbana-Champaign, the source of such innovations as the pioneering PLATO system of the 1970s and the point-and-click Mosaic browser that was popularizing the nascent World Wide Web at that very moment.

Kulas and Toschlog founded Parallax Software in June of 1993, six months before DOOM ignited a craze for immersive 3D action that would remake much of the industry in its image over the next few years. Luckily, Parallax was well-equipped to capitalize on the trend, what with the founders’ experience with 3D graphics and the passionate young sparks they were able to recruit from the nearby university. Descent, their very first game, put you behind the controls of a small flying vehicle and set you loose inside a series of 3D-rendered outer-space mining complexes, filled with robots gone haywire. It was different enough to stand out in a sea of DOOM clones, yet felt very much in step with the times in a broader sense. Upon its release in March of 1995, Descent became a surprise hit for its publisher Interplay, whose marketers were left scrambling to catch up to the buzz on the street with a port to the Sony PlayStation and television campaigns starring mid-tier celebrities. Made for less than half a million dollars, the game was one heck of a debut for Parallax. It and its almost-as-successful 1996 sequel were enough to make them think that winning fame and fortune in the games industry was actually pretty easy.

Matt Toschlog had never been happy in Champaign. Flush with all of that Descent cash, he wanted to move Parallax somewhere else. Mike Kulas, on the other hand, preferred to stay put. Unable to find any other way out of the impasse, the founders agreed to split the company between them. In late 1996, Toschlog moved to Ann Arbor, Michigan, to start Outrage Entertainment. Kulas decided to rename his half of the company Volition — “an intense act of will to accomplish something” — after stumbling across the word in a book. Outrage’s first project was to be the inevitable Descent3; Volition’s was to be Freespace, a space sim that would, as its name implied, take the player out of the asteroid mines and into the limitless inky-black freedom that lay beyond.

Freespace isn’t shy about displaying its influences. Created by a bunch of guys who adored LucasArts’s X-Wing and TIE Fighter sims, it hews unabashedly to their template. After the requisite flight training, you’re tossed into an interstellar war between your Terran Alliance and an alien race known as the Vasudans. Then another group of aliens shows up, a shadowy enigma that comes to be called the Shivans, who are so powerful that the old antipathies are quickly forgotten, and Terrans and Vasudans unite to face the greatest threat either of their races has ever known.

Although neither its core gameplay model nor its fiction is remotely revolutionary, Freespace stands out for how well it executes on this derivative material. The graphics are exceptional for their era, the possibility space behind the controls expansive, the mission design uniformly solid. Inspiration in game design is wonderful, but we should never forget the value of perspiration. The people who made Freespace loved what they were doing enough to sweat every small detail, and it shows. The only place where the game fell down a bit back in the day was a somewhat under-baked multiplayer mode.

Interplay insisted on calling the game Descent: Freespace (“From the creators of Descent!”) in the hope of riding the coattails of the publisher’s biggest hit in recent memory. Whatever else you can say about it, it certainly wasn’t their worst exercise in Descent branding. (That would be Descent to Undermountain, an ill-advised attempt to use the old Parallax engine for, of all things, a Dungeons & Dragons-licensed CRPG.) And who knows? Maybe the branding even did some good. Upon its release in June of 1998, Freespace sold well enough to be modestly profitable for its studio and publisher and convince Interplay to fund an expansion pack and a sequel. The only catches were that Volition had to turn both out quickly, without spending too much money on them.

The expansion pack, which they called Silent Threat, ended up being short and perfunctory, the definition of inessential. The full-fledged sequel, however, was a minor miracle. It defied every cynical expectation raised by its abbreviated development cycle when it shipped on September 30, 1999.

Freespace 2 — Interplay allowed the cleaner name this time, perhaps to avoid confusion with the recently released Descent3 — did everything its predecessor had done well that much better, then added a finishing touch that it had lacked: a real sense of gravitas, provided largely by the one significant addition to the development team. Jason Scott (not to be confused with the archivist and Infocom documentarian of the same name) was Volition’s first dedicated writer. He made his presence felt with a campaign that was sometimes exhilarating, sometimes harrowing, but always riveting. The outer-space kitty-cats of Wing Commander, even Darth Vader and Emperor Palpatine, paled in comparison to the Shivans after Jason Scott got his hands on them. “The universe is very impersonal,” he says. “Your character is referred to only as ‘Pilot’ or ‘Alpha 1,’ and you’re up against countless waves of a seemingly unbeatable, genocidal adversary that never communicates its goals or motives. In the briefings, we tried to convey the sense of a much larger conflict unfolding in multiple systems, while at the same time hinting that your commanders weren’t telling you the whole story.”


Freespace 2 was never going to single-handedly rescue the space-sim sub-genre, but it did ensure that it went out on a high note. It’s a demanding game even by the usual standards of its kind, one that uses every key on the keyboard and then some, one that is guaranteed to leave you wishing you had more buttons on your joystick, no matter how nerdily baroque it might already be. Some of its more counter-intuitive commands, such as “target my target’s target,” have become memes in certain circles. Yet the developers are unapologetic. “We wanted players to feel like pilots in control of a complex, powerful, responsive, and technologically advanced machine,” says Jason Scott. “Complexity was a virtue.”

I’m almost tempted to write here that this was a shame, in that it put such a high barrier to entry in front of what was actually one of the more sophisticated ludic fictions of its era. My experience with the game probably isn’t unique: I struggled with it for a while, reached a point where I couldn’t seem to hit any enemy that I shot at even as said enemies had become all too good at hitting me, and wound up watching the rest on YouTube, as you do these days. On the other hand, though, why shouldn’t unabashedly demanding games that aren’t quite for me have good writing too?

Because you deserve to hear from someone other than a dabbler like me before we move on, I’m going to take the liberty of quoting Lee Hutchinson, who is a good friend of this site, a stalwart voice of reason in these increasingly unreasonable times of ours through his day job as a senior editor at Ars Technica, and, most importantly for our purposes, a hardcore space-sim junkie in all the ways that I am not. He can explain better than I can what Freespace 2 came to mean to its biggest fans, how it melded gameplay and narrative into an unforgettable roller-coaster ride.

If you’ve seen one of those simplified “evolution of man” charts, showing a chimp-like predecessor far at the left and an upright tool-using human all the way at the right, you’ve got a good idea of how Freespace 2 capped off the genre. It was the culmination of everything that had come before it, and every single gameplay element was refined and polished to a razor-sharp gleam.

Freespace 2 lets players experience a tremendous variety of missions in different fighters with a gamut of capabilities. Each mission is connected by an overarching plot: you may be ambushed while escorting some capital ships in one mission, and then in the next mission you might switch to flying a bomber and be assigned to take those capital ships out. You might be temporarily attached to a special-operations wing flying a prototype starship, or have to fly captured Shivan fighters in a deep-cover mission to scope out an enemy staging point, or deal with total mission failure and objective changes right in the middle of doing dozens of other things. Capital ships fire ridiculously large, ridiculously powerful beam weapons at each other, slicing each other to ribbons and providing a fantastic Babylon 5-esque backdrop while the player duels enemy fighters.

The targeting system is complex and rich; the wingman and escort system is complex and rich; the comms system is complex and rich. Everything about Freespace 2 shows care, love, and craftsmanship — from the chatter going back and forth between your wingmen as you blindly scout a nebula looking for a lost frigate, to the amazingly well-acted mission briefings. In practically every way, it is the Platonic ideal of a space-combat sim.

Starting at about the halfway point, Freespace 2 drops the hammer on the player with a series of tightly linked missions that absolutely do not let up. The war against the Shivans isn’t going well. A faction of Quisling-like humans is trying to defect to the Shivans’ side, taking a large chunk of the human military with it. At several points throughout the long campaign, it feels like the game is about to come to a crashing climax — only it doesn’t end. Things just get worse, and it’s an absolute rush to experience — flying your guts out, desperately trying to fight a rear-guard action against an unknowable enemy that seems to be totally unable to feel remorse, pity, or even fatigue.

I’ve never felt quite the combination of awe, fear, and eagerness I felt as I pushed through to Freespace 2’s endgame. There are lots of gaming experiences I wish I could relive for the first time, but playing Freespace 2 tops the list. That’s as good a way as any to judge a game as the best in its genre.

In the short term at least, Volition wasn’t rewarded very well for creating this game that Lee Hutchinson and more than a few others consider simply the best story-driven space sim ever made, the evolutionary end point of Chris Roberts’s original Wing Commander of 1990. Mike Kulas insists that Freespace 2 didn’t actually lose money for its studio or publisher, but it didn’t earn them much of anything either. Plans for a Freespace 3 were quietly shelved. Thus Freespace 2 came to mark the end of an era, not only for Volition but for computer gaming in general: while not quite the last space sim to be put out by a major publisher, it was the last that would go on to be remembered as a classic of its form.

What with there being no newer games that could compete with it, those who still loved the space sim clung all the tighter to Freespace 2 as the months since its release turned into years. They were incredibly lucky that Volition was staffed by genuinely nice, fair-minded people who felt their pain and were willing to “pay it forward,” as the saying goes. In 2002, Volition uploaded the full source code to Freespace 2 to the Internet for non-commercial use.

They couldn’t possibly have envisioned what followed. As of this writing, 23 years after that act of spontaneous generosity, the Freespace 2 engine has been improved and modernized almost beyond recognition, with support for eye-bleedingly high resolutions and all of the latest fancy graphical effects that my humble retro-gaming computers don’t even support. You can use the updated engine to play Freespace 1 and 2 and the Silent Threat expansion pack, in versions that have been polished to an even shinier gleam than the originals by the hands of hundreds of dedicated volunteers. Even more inspiringly, folks have used the technology to create a welter of new campaigns — effectively whole new space sims that run off what remains the best of all engines for this type of game.

The people who made Freespace 1 and 2 all those years ago are themselves awed by what their pair of discrete boxed computer games have been turned into. Freespace proved to be as much a new beginning as an ending. Long may the space sim fly on in the hands of those who love it most.



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: Sierra On-Line’s customer newsletter InterAction of Spring 1999; Origin Systems’s internal newsletter Point of Origin of September 20 1996 and February 14 1997; Computer Gaming World of October 1994, February 1995, July 1997, April 1998, October 1998, November 1998, February 1999, July 1999, and January 2000; Retro Gamer 204.

Online sources include interviews with Jack Nichols and Randy Littlejohn on B5 Scrolls, “Growing Up Gaming: The Five Space Sims That Defined My Youth” by Lee Hutchinson at Ars Technica, an interview with some of the core members of the Freespace 2 team by the Space Game Junkie podcast, and a Game Informer documentary about Volition’s history.

Where to Get Them: Wing Commander I and IIWing Commander III: Heart of the TigerWing Commander IV: The Price of FreedomWing Commander: ProphecyX-WingTIE FighterX-Wing vs. TIE FighterX-Wing AllianceDescent: Freespace, and Freespace 2 are all available as digital purchases on GOG.com.

I strongly recommend that you run the Freespace games through the Freespace Open engine, even if you’re primarily looking for a retro experience. Both on native Windows 10 and running through WINE on Linux, I found the original Freespace to be subtly broken: I was given only a fraction of the time I ought to have been given to complete the last training mission. (This was not good at all, considering I’m rubbish at the game anyway.) Freespace Open is quite painless to install and maintain using a utility called Knossos. It will walk you through the setup process and then deliver a glitch-free game, whilst letting you select as many or as few modern niceties as you prefer.

 
 

Tags: , , , , , , , , , ,

The Second Coming of Star Wars

It’s all but impossible to overstate the influence that Star Wars had on the first generation of microcomputer games. The fact is, Star Wars and early home computers were almost inseparable — in some odd sense part of the same larger cultural movement, if you will.

The first film in George Lucas’s blockbuster trilogy debuted on May 25, 1977, just days before the Apple II, the first pre-assembled personal computer to be marketed to everyday consumers, reached store shelves. If not everyone who loved Star Wars had the money and the desire to buy a computer in the months and years that followed, it did seem that everyone who bought a computer loved Star Wars. And that love in turn fueled many of the games those early adopters made. J.R.R. Tolkien’s Lord of the Rings novels and, perhaps more arguably, the Star Trek television and movie franchise are the only other traditional-media properties whose impact on the fictions and even mechanics of early computer games can be compared to that of Star Wars.

And yet licensed takes on all three properties were much less prominent than one might expect from the degree of passion the home-computer demographic had for them. The British/Australian publisher Melbourne House had a huge worldwide hit with their rather strange 1982 text-adventure adaptation of Tolkien’s The Hobbit, but never scaled similar heights with any of their mediocre follow-ups. Meanwhile Star Trek wound up in the hands of the software arm of the print publisher Simon & Schuster, who released a series of obtuse, largely text-based games that went absolutely nowhere. And as for Star Wars, the hottest property of them all… ah, therein lies a tale.



Like The Lord of the Rings before it, Star Wars was a victim of the times in which its first licensing deals were signed. In the months before the first movie was released, both George Lucas himself and 20th Century Fox, the studio that distributed the film, sought after someone — anyone — who would be willing to make a line of toys to accompany it. They were turned down again and again. Finally, Marc Pevers, Fox’s president of licensing, got a nibble from a small toy maker called Kenner Products.

Kenner was owned at that time by the big corporate conglomerate General Mills, who also happened to own Parker Brothers, the maker of such family-board-game staples as Monopoly, Clue, and Sorry!. Thus when Kenner negotiated with Lucas and Fox, they requested that the license cover “toys and [emphasis mine] games,” with responsibility for the latter to be kicked over to Parker Brothers. For at this early date, before the release of the Atari VCS videogame console, before even the arrival of Space Invaders in American arcades, “games” meant board games in the minds of everyone negotiating the deal. Indeed, Kenner explicitly promised that at a minimum they would produce four action figures and a “family game” to help prime the pump of a film whose commercial prospects struck just about everyone as highly dubious.

There are conflicting reports as to the other terms of the deal, but it seems most likely that Kenner agreed to pay Lucas and Fox either a 5-percent royalty or a flat $100,000 per year, whichever amount was greater. If Kenner ever failed to pay at least $100,000 in any given year, the arrangement would end immediately. Otherwise, it would go on in perpetuity. It was quite a sweet deal for Kenner by any standard, very much a reflection of the position of weakness from which Fox and Lucas were negotiating; one Kenner employee later joked that they had gotten Star Wars for “$50 and a handshake.”

Of course, we all know what happened with that first Star Wars film upon its release a few months after the contract was signed. After a slow start in 1977 while they tooled up to meet the completely unexpected level of demand, Kenner sold 42 million pieces of Star Wars-branded merchandise in 1978 alone; by 1985, the worldwide population of Star Wars action figures was larger than the United States’s population of real human beings. Lucas publicly excoriated Marc Pevers for a deal that had cost him “tens of millions,” and the two wound up in libel court, the former eventually forced to pay the latter an unspecified sum for his overheated remarks by a settlement arrangement.

Lucas’s anger was understandable if not terribly dignified. As if the deal for the toy rights alone wasn’t bad enough, Pevers had blithely sold off the videogame rights for a song as well, simply by not demanding more specific language about what kinds of games the phrase “toys and games” referred to. Kenner’s first attempt at a Star Wars videogame came already in 1978, in the form of a single-purpose handheld gadget subtitled Electronic Laser Battle. When that didn’t do well, the field was abandoned until 1982, when, with the Atari-VCS-fueled first wave of digital gaming at its height, Parker Brothers released three simple action games for the console. Then they sub-contracted a few coin-op arcade games to Atari, who ported them to home consoles and computers as well.

But by the time the last of these appeared, it was 1985, the Great Videogame Crash was two years in the past, and it seemed to the hidebound executives at General Mills that the fad for videogames was over and done with, permanently. Their Star Wars games had done pretty well for themselves, but had come out just a little too late in the day to really clean up. So be it; they saw little reason to continue making them now. It would be six years before another all-new, officially licensed Star Wars videogame would appear in North America, even as the virtual worlds of countless non-licensed games would continue to be filled with ersatz Han Solos and Death Stars.

This state of affairs was made doubly ironic by the fact that Lucasfilm, George Lucas’s production company, had started its own games studio already in 1982. For most of its first ten years, the subsidiary known as Lucasfilm Games was strictly barred from making Star Wars games, even as its employees worked on Skywalker Ranch, surrounded with props and paraphernalia from the films. Said employees have often remarked in the years since that their inability to use their corporate parent’s most famous intellectual property was really a blessing in disguise, in that it forced them to define themselves in other ways, namely by creating one of the most innovative and interesting bodies of work of the entire 1980s gaming scene. “Not being able to make Star Wars games freed us, freed us in a way that I don’t think we understood at the time,” says Ron Gilbert, the designer of the Lucasfilm classics Maniac Mansion and The Secret of Monkey Island. “We always felt we had to be making games that were different and pushed the creative edges. We felt we had to live up to the Lucasfilm name.” For all that, though, having the Lucasfilm name but not the Star Wars license that ought to go with it remained a frustrating position to be in, especially knowing that the situation was all down to a legal accident, all thanks to that single vaguely worded contract.

If the sequence of events which barred Lucasfilm from making games based on their own supreme leader’s universe was a tad bizarre, the way in which the Star Wars rights were finally freed up again was even stranger. By the end of 1980s, sales of Star Wars toys were no longer what they once had been. The Return of the Jedi, the third and presumably last of the Star Wars films, was receding further and further into the rear-view mirror, with nothing new on the horizon to reignite the old excitement for the next generation of children. For the first time, Kenner found themselves paying the guaranteed $100,000 licensing fee to Lucas and Fox instead of the 5-percent royalty.

At the beginning of 1991, Kenner failed to send the aforementioned parties their $100,000 check for the previous year, thereby nullifying the fourteen-year-old contract for Star Wars “toys and games.” Fan folklore would have it that the missing check was the result of an accounting oversight; Kenner was about to be acquired by Hasbro, and there was much chaos about the place. A more likely explanation, however, is that Kenner simply decided that the contract wasn’t worth maintaining anymore. The Star Wars gravy train had been great while it lasted, but it had run its course.

There was jubilation inside Lucasfilm Games when the staff was informed that at long last they were to be allowed to play in the universe of Star Wars. They quickly turned out a few simple action-oriented titles for consoles, but their real allegiance as a studio was to personal computers. Thus they poured the most effort by far into X-Wing, the first Star Wars game ever to be made first, foremost, and exclusively for computers, with all the extra complexity and extra scope for design ambition which that description implied in those days.


Lawrence Holland, circa 1992.

The mastermind of X-Wing was a soft-spoken, unassuming fellow named Lawrence Holland, whose path into the industry had been anything but straightforward. His first passion in life had been archaeology and anthropology; he’d spent much of his early twenties working in the field in remote regions of East Africa and India. In 1981, he came to the University of California, Berkeley to study for a doctorate in anthropology. He had never even seen a personal computer, much less played a computer game, until he became roommates with someone who had one. Holland:

I was working as a chef at a restaurant in Berkeley — and I realized I didn’t particularly want to do that for the next six years while I worked on my doctorate. At the time, my roommate had an Atari 800, and he was into programming. I thought, “Hey, what a cool machine!” So I finally got a Commodore 64 and spent all my spare time teaching myself how to use it. I’d always wanted to build something, but I just hadn’t found the right medium. Computers seemed to me to be the perfect combination of engineering and creativity.

The barriers to entry in the software industry were much lower then than they are today; a bright young mind like Holland with an aptitude and passion for programming could walk into a job with no formal qualifications whatsoever. He eventually dropped out of his PhD track in favor of becoming a staff programmer at HESWare, a darling of the venture capitalists during that brief post-Great Videogame Crash era when home computers were widely expected to become the Next Big Thing after the console flame-out.

While working for HESWare in 1985, Holland was responsible for designing and programming a rather remarkable if not quite fully-realized game called Project: Space Station, a combination of simulation and strategy depicting the construction and operation of its namesake in low Earth orbit. But soon after its release HESWare collapsed, and Holland moved on to Lucasfilm Games. Throughout his many years there, he would work as an independent contractor rather than an employee, by his own choice. This allowed him, as he once joked, to “take classes and keep learning about history and anthropology in my copious spare time.”

In writing about the LucasFilm Games of the late 1980s and early 1990s in previous articles, I’ve focused primarily on the line of graphic adventures which they began in 1987 with Maniac Mansion, stressing how these games’ emphasis on fairness made them a welcome and even visionary alternative to the brutality being inflicted upon players by other adventure developers at the time. But the studio was never content to do or be just one thing. Thus at the same time that Ron Gilbert was working on Maniac Mansion, another designer named Noah Falstein was making a bid for the vehicular-simulation market, one of the most lucrative corners of the industry. Lawrence Holland came to Lucasfilm Games to help out with that — to be the technical guy who made Falstein’s design briefs come to life on the monitor screen. The first fruit of that partnership was 1987’s PHM Pegasus, a simulation of a hydrofoil attack boat; it was followed by a slightly more elaborate real-time naval simulation called Strike Fleet the following year.

With that apprenticeship behind him, Holland was allowed to take sole charge of Battlehawks 1942, a simulation of World War II aerial combat in the Pacific Theater. He designed and programmed the game in barely six months, in time to see it released before the end of 1988, whereupon it was promptly named “action game of the year” by Computer Gaming World magazine. Battlehawks 1942 was followed in 1989 by Their Finest Hour, another winner of the same award, a simulation of the early air war in Europe; it was in turn followed by 1991’s Secret Weapons of the Luftwaffe, a simulation of the later years of war there. Each simulator raised the ante over what had come before in terms of budget, development time, and design ambition.

The Early Works of Lawrence Holland


Project: Space Station (1985) is an amazingly complex simulation and strategy game for the humble Commodore 64. Holland took the project over after an earlier version that was to have been helmed by a literal rocket scientist fell apart, scaling down the grandiose ideas of his predecessor just enough to fit them into 64 K of memory.

PHM Pegasus (1987) was designed by Noah Falstein and implemented by Holland. It simulates a military hydrofoil — sort of the modern equivalent to the famous PT Boats of World War II.

Strike Fleet (1988), Holland’s second and last game working with Falstein as lead designer, expands on the concept of PHM Pegasus to let the player lead multiple ships into fast-paced real-time battles.

Battlehawks 1942 (1988) was Holland’s first flight simulator, his first project for LucasArts on which he served as lead designer as well as programmer, and the first which he coded on MS-DOS machines rather than the Commodore 64. A simulation of carrier-based aviation during the fraught early months of World War II in the Pacific, it was implemented in barely six months from start to finish. Dick Best, the leader of the first dive-bomber attack on the Japanese aircraft carriers at the Battle of Midway — and thus the tip of the spear which changed the course of the war — served as a technical advisor. “I am thinking about buying an IBM just so I can play the game at home,” said the 78-year-old pilot to journalists.

Their Finest Hour (1989) was the second game in what would later become known as Holland’s “air-combat trilogy.” A portrayal of the Battle of Britain, it added a campaign mode, a selection of set-piece historical missions to fly, and even a mission builder for making more scenarios of your own to share with others.

Holland’s ambition ran wild in Secret Weapons of the Luftwaffe (1991). Beginning as a simulation of such oddball latter-war German aircraft as the Messerschmitt Me-163 rocket plane and the Me-262 jet fighter, it wound up encompassing the entire second half of the air war in Europe, including a strategy game about the Allied strategic-bombing campaign that was detailed enough to have been put in a separate box and sold alone. As much a gaming toolbox as a game, it was supported with no fewer than four separate expansion packs. Holland and Edward Kilham, his programming partner for the project, crunched for a solid year to finish it, but nevertheless ended a good twelve months behind schedule. With this object lesson to think back on, Holland would rein in his design ambitions a bit more in the future.



As I described at some length in a recent article, flight simulators in general tend to age more like unpasteurized milk than fine wine, and by no means is Holland’s work in this vein entirely exempt from this rule. Still, in an age when most simulators were emphasizing cutting-edge graphics and ever more complexity over the fundamentals of game design, Holland’s efforts do stand out for their interest in conveying historical texture rather than a painstakingly perfect flight model. They were very much in the spirit of what designer Michael Bate, who used a similar approach at a slightly earlier date in games he made for Accolade Software, liked to call “aesthetic simulations of history.” Holland:

Flight simulators [had] really focused on the planes, rather than the times, the people, and how the battles influenced the course of the war. [The latter is] what I set out to do. It’s become my philosophy for all the sims I’ve done.

We get letters from former pilots, who say, “Wow! This is great! This is just like I remember it.” They’re talking about a gut, sensory impression about the realism of flying and interacting with other planes — not the hardcore mathematical models. I’ve focused on that gut feeling of realism rather than the hardcore mathematical stuff. I’ve emphasized plane-to-plane engagement, seat-of-the-pants flying. I like to keep the controls as simple as possible, so someone can jump in and enjoy the game. Of course, the more technically accurate the flight model, the more difficult it is to fly. Unless they’re really familiar with flight simulators, people tend to be intimidated by having to learn the uses of a bunch of different keys. That makes a game hard to get into. I want them to be able to hop into the cockpit and fly.

In some ways at least, Secret Weapons of the Luftwaffe remains to this day the most ambitious game Lawrence Holland has ever made. At a time when rival flight simulators like Falcon were going micro, attempting to capture a single aircraft with a pedant’s obsession for detail, Secret Weapons provided a macro-level overview of the entire European air war following the entry of the United States into the conflict. Holland called it a “kitchen-sink” game: “It’s fun and challenging to keep thinking of different ways for the player to interact with the product on different levels.” In Secret Weapons, you could pilot any of eight different airplanes, including the experimental German rocket planes and jets that gave the game its misleadingly narrow-sounding name, or even fly as a gunner or bombardier instead of a pilot in a B-17. You could go through flight school, fly a single random mission, a historical mission, or fly a whole tour of duty in career mode. Or you could play Secret Weapons as a strategy game of the Allied bombing campaign against Germany, flying the missions yourself if you liked or letting the computer handle that for you; this part of the game alone was detailed enough that, had it been released as a standalone strategy title by a company like SSI, no one would have batted an eye. And then there were the four (!) expansion packs LucasArts put together, adding yet more airplanes and things to do with them…

Of course, ambition can be a double-edged sword in game design. Although Secret Weapons of the Luftwaffe came together much better in the end than many other kitchen-sink games, it also came in a year late and way over budget. As it happened, its release in late 1991 came right on the heels of the news that Lucasfilm Games was finally going to be allowed to charge into the Star Wars universe. Lawrence Holland’s life was about to take another unexpected twist.



It isn’t hard to figure out why LucasArts — the old Lucasfilm Games adopted the new name in 1992 — might have wished to create a “simulation” of Star Wars space battles. At the time, the biggest franchise in gaming was Origin Systems’s Wing Commander series, which itself owed more than a little to George Lucas’s films. Players loved the action in those games, but they loved at least equally the storytelling which the series had begun to embrace with gusto in 1991’s Wing Commander II. A “real” Star Wars game offered the chance to do both things as well or better, by incorporating both the spacecraft and weapons of the films and the established characters and plot lore of the Star Wars universe.

Meanwhile the creative and technical leap from a simulation of World War II aerial combat to a pseudo-simulation of fictional space combat was shorter than one might initially imagine. The label of space simulator was obviously a misnomer in the strictly literal sense; you cannot simulate something which has never existed and never will. (If at some point wars do move into outer space, they will definitely not be fought anything like this.) Nevertheless, X-Wing would strive to convey that feeling of realism that is the hallmark of a good aesthetic simulation. It wouldn’t, in other words, be an arcade game like the Star Wars games of the previous decade.

In point of fact, George Lucas had aimed to capture the feel of World War II dogfighting in his movies’ action sequences, to the point of basing some shots on vintage gun-camera footage. It was thus quite natural to build X-Wing upon the technology last seen in Secret Weapons of the Luftwaffe. You would have to plan your attacks with a degree of care, would have to practice some of the same tactics that World War II fighter pilots employed, would even have to manage the energy reserves of your craft, deciding how much to allocate to guns, shields, and engines at any given juncture.

Still working with LucasArts as an independent contractor, Holland hired additional programmers Peter Lincroft and Edward Kilham — the former had also worked on Secret Weapons of the Luftwaffe — to help him out with the project. LucasArts’s in-house staff of artists and composers saw to the audiovisual assets, and their in-house designers developed most of the missions. With the struggle that his last game had been still high in his memory, and knowing all too well that LucasArts’s first Star Wars computer game needed to be released in a timely fashion if it was to compete with the Wing Commander juggernaut, Holland abandoned any thoughts of dynamic campaigns or overarching strategic layers in favor of a simple series of set-piece missions linked together by a pre-crafted story line — exactly the approach that had won so much commercial success for Wing Commander. In fact, Holland simplified the Wing Commander approach even further, by abandoning its branching mission tree in favor of a keep-trying-each-mission-until-you-win-it methodology. (To be fair, market research proved that most people played Wing Commander this way anyway…)


Smoke ’em if you got ’em: X-Wing in action.

X-Wing‘s not-so-secret weapon over its great rival franchise was and is, to state it purely and simply, Star Wars. Right from the iconic flattened text crawl that opens the game, accompanied by the first stirring chords of John Williams’s unforgettable theme music, it looks like Star Wars, sounds like Star Wars, feels like Star Wars. The story it tells is interwoven quite deftly with the plot of the first film. It avoids the slightly ham-handed soap-opera story lines which Wing Commander loves to indulge in in favor of a laser focus on the real business at hand: the destruction of the Death Star. Whereas Wing Commander, with its killer alien cats and all the rest, never rises much above the level of earnest fan fiction, X-Wing is… well, it certainly isn’t great literature, any more than the films upon which it’s based are profound drama, but it is solidly crafted pulp fiction for the kid in all of us, and this quality makes it exactly like the aforementioned films. Playing it really does feel like jumping into one of them.

But X-Wing also has an Achilles heel that undoes much of what it does so well, a failing that’s serious enough that I have trouble recommending the game at all: its absolutely absurd level of difficulty. As you advance further in the game, its missions slowly reveal themselves to be static puzzles to be solved rather than dynamic experiences. There’s just one way to succeed in the later missions in particular, just one “correct” sequence of actions which you must carry out perfectly. You can expect to fly each mission over and over while you work out what that sequence is. This rote endeavor is the polar opposite of the fast-paced excitement of a Star Wars film. As you fail again and again, X-Wing gradually becomes the one thing Star Wars should never be: it becomes boring.

There’s a supreme irony here: LucasArts made their name in adventure games by rejecting the idea that the genre must necessarily entail dying over and over and, even worse, stumbling down blind alleys from which you can never return without restoring or restarting. But with X-Wing, the company famous for “no deaths and no dead ends” delivered a game where you could effectively lock yourself out of victory in the first minute of a mission. It’s hard to conceive of why anyone at LucasArts might have thought this a good approach. Yet Computer Gaming World‘s Chris Lombardi was able to confirm in his eventual review of the game that the punishing mission design wasn’t down to some colossal oversight; it was all part of the plan from the beginning.

Through an exchange with LucasArts, I’ve learned from them that the missions were designed as puzzles to be figured out and solved. This is entirely accurate. The tougher missions have a very specific “solution” that must be executed with heroic precision. Fly to point A, knock out fighters with inhuman accuracy, race to point B, knock out bombers with same, race to point C, to nip off a second bomber squadron at the last possible second. While this is extremely challenging and will make for many hours of play, I’m not convinced that it’s the most effective design possible. It yanks [the player] out of the fiction of the game when he has to play a mission five times just to figure out what his true objective is, and then to play the next dozen times trying to execute the path perfectly.

Often, success requires [the player] to anticipate the arrival of enemy units and unrealistically race out into space to meet a “surprise” attack from the Empire. It’s all a matter of balance, young Jedi, and on the sliding scale of Trivially Easy to Joystick-Flinging Frustration, X-Wing often stumbles awkwardly toward the latter. From the reviewer’s high ground of hindsight, it seems a player-controlled difficulty setting might have been a good solution.

Despite this tragic flaw lurking at its mushy center, X-Wing was greeted with overwhelmingly positive reviews and strong sales upon its release in March of 1993. For, if X-Wing left something to be desired as a piece of game design, the timing of its release was simply perfect.

The game hit the scene in tandem with a modest but palpable resurgence of interest in Star Wars as a whole. In 1991 — just as Kenner Products was deciding that the whole Star Wars thing had run its course — Timothy Zahn had published Heir to the Empire, the first of a new trilogy of Star Wars novels. There had been Star Wars books before, of course, but Zahn’s trilogy was unique in that, rather than having to confine himself to side stories so as not to interfere with cinematic canon, its author had been given permission by George Lucas to pick up the main thread of what happened after Return of the Jedi. Everyone who read the trilogy seemed to agree that it represented a very credible continuation indeed, coming complete with an arch-villain, one Imperial Grand Admiral Thrawn, who was almost as compelling as Darth Vader. All three books — the last of them came out in 1993, just after X-Wing — topped genre-fiction bestseller lists. Star Wars was suddenly having a moment again, and X-Wing became a part of that, both as beneficiary and benefactor. Many of the kids who had seen the films multiple times each in theaters and carried Star Wars lunchboxes with them to school were now in their early twenties, the sweet spot of the 1993 computer-game demographic, and were now feeling the first bittersweet breaths of nostalgia to blow through their young lives, even as they were newly awakened to the potential of space simulators in general by the Wing Commander games. How could X-Wing not have become a hit?

The people who had made the game weren’t much different from the people who were now buying it in such gratifying numbers. Zahn’s novels were great favorites of Holland and his colleagues as well, so much so that, when the time came to plan the inevitable sequel to X-Wing, they incorporated Admiral Thrawn into the plot. In the vastly superior game known as TIE Fighter, which takes places concurrently with the second Star Wars film, a younger Thrawn appears in the uneasy role of subordinate to Darth Vader.



Indeed, it’s difficult to imagine TIE Fighter, which dares to place you in the role of a pilot for the “evil” Empire, ever coming to exist at all without the Zahn novels. For it was Zahn’s nuanced, even sympathetic portrayal of Thrawn, and with it his articulation of an ideology for the Empire that went beyond doing evil for the sake of it, that first broadened the moral palette of the Star Wars universe to include shades of gray in addition to black and white. Zahn’s version of the Empire is a rather fussily bureaucratic entity that sees itself as tamping down sectarianism and maintaining law and order in the galaxy in the interest of the greater good, even if the methods it is sometimes forced to employ can be regrettably violent. The game took that interpretation and ran with it. Holland:

Our approach is that the propaganda machines are always running full-blast during warfare. So far, the propaganda we’ve been exposed to has been from the Rebels. But in warfare, neither side is always clean, and both sides can take the moral high ground. So we’re trying to blur the moral line a little bit and give the Empire a soapbox to communicate its mission: the restoration of peace and order.

For instance, there’s a lot of civil war going on. The fighting planets are lost in their hate and don’t have the galactic perspective the Empire can provide. In this regard, the Empire feels it can serve to stop these conflicts. Within the Empire there are a lot of people — like the pilot the player portrays — who have an honorable objective.

At the risk of putting too fine a point on it: I would hardly be the first Internet scribe to note that the established hegemony of developed Western nations in our own world resembles the Empire far more than the Rebel Alliance, nor that the Rebel freedom fighters bear a distinct similarity to some of the real-world folks we generally prefer to call terrorists.

TIE Fighter casts you as a pilot of good faith who earnestly believes in the Empire’s professed objective of an orderly peace and prosperity that will benefit everyone. In order to capture some of the murderous infighting that marks the highest levels of the Imperial bureaucracy in both the movies and Zahn’s novels, as well as to convey some of the moral rot taking cover beneath the Empire’s professed ideology, the game introduces a mysterious agent of the emperor himself who lurks in the shadows during your mission briefings, to pull you aside afterward and give you secret objectives that hint of machinations and conspiracies that are otherwise beyond your ken. In the end, you find yourself spending almost as much time fighting other factions of the Empire as you do Rebels — which does rather put the lie to the Empire’s claim that only it can provide a harmonious, orderly galaxy, but so be it.

What really makes TIE Fighter so much better than its predecessor is not the switch in perspective, brave and interesting though it may be, but rather the fact that it so comprehensively improves on X-Wing at the level of the nuts and bolts of game design. It’s a fine example of a development team actually listening to players and reviewers, and then going out and methodically addressing their complaints. In the broad strokes, TIE Fighter is the same game as X-Wing: the same linear series of missions to work through, the same basic set of flight controls, a different but similarly varied selection of spacecraft to learn how to employ successfully. It just does everything that both games do that much better than its predecessor.

Take, for example, the question of coordinating your tactics with your wingmen and other allies. On the surface, the presence of friends as well as foes in the battles you fight is a hallmark not just of X-Wing but of the Wing Commander games that came before it, being embedded into the very name of the latter series. Yet your helpmates in all of those games are, as Chris Lombardi put it in his review of X-Wing, “about as useful as a rowboat on Tatooine.” Players can expect to rack up a kill tally ten times that of their nearest comrade-in-arms.

TIE Fighter changes all that. It presents space battles that are far more complex than anything seen in a space simulator before it, battles where everyone else flies and fights with independent agency and intelligence. You can’t do everything all by yourself anymore; you have to issue real, substantive orders to the pilots you command, and obey those orders that are issued to you. Many reviewers of TIE Fighter have pointed out how well this ethos fits into that of a hyper-organized, hyper-disciplined Imperial military, as opposed to the ramshackle individual heroism of the Rebel Alliance. And it’s certainly a fair point, even if I suspect that the thematic resonance may be more a happy accident than a conscious design choice. But whatever the reasons behind it, it lends TIE Fighter a different personality. Instead of being the lone hero who has to get everything done for yourself, you feel like a part of a larger whole.

For the developers, the necessary prerequisites to success with this new philosophy were an improved technical implementation and improved mission design in comparison to those of X-Wing. In addition to the audiovisual evolution that was par for the course during this fast-evolving era of computing — the 3D models are now rendered using Gouraud shading — TIE Fighter gives you a whole range of new views and commands to make keeping track of the overall flow of battle, keeping tabs on your allies, and orienting yourself to your enemies much easier than in X-Wing. Best of all, it abandons the old puzzle-style missions in favor of the unfolding, dynamic battlescapes we were missing so keenly last time. It does you the small but vital kindness of telling you which mission objectives have been completed and which still need to be fulfilled, as well as telling you when a mission is irrevocably failed. It also introduces optional objectives, so that casual players can keep the story going while completists try to collect every last point. And it has three difficulty levels to choose from rather than being permanently stuck on “Hard.”

TIE Fighter was released in July of 1994, five months before the long-awaited Wing Commander III, a four-CD extravaganza featuring a slate of established actors onscreen, among them Mark Hamill, Mr. Luke Skywalker himself. LucasArts’s game might have seemed scanty, even old-fashioned by comparison; it didn’t even ship on the wundermedium of CD at first, but rather on just five ordinary floppy disks. Yet it sold very well, and time has been much kinder to it than it has to Origins’s trendier production, which now seems somehow more dated than the likes of Pong. TIE Fighter, on the other hand, remains what it has always been: bright, pulpy, immersive, exciting, Star Warsy fun. It’s still my favorite space simulator of all time.

TIE Fighter


How could it be Star Wars without that iconic opening text crawl? TIE Fighter and its predecessor succeed brilliantly in feeling like these movies that define the adjective “iconic.” This extends to the sound design: the whoosh of passing spacecraft and closing pneumatic doors, the chatter of droids, the various themes of John Williams’s soundtrack… it’s all captured here with remarkable fidelity to the original. Of course, there are some differences: the sequence above is initially jarring because it’s accompanied by Williams’s ominous Imperial theme rather than the heroic main Rebel theme which we’ve been conditioned to expect.

One of the many places where TIE Fighter borrows from Wing Commander is in its commitment to a diegetic interface. You don’t choose what to do from a conventional menu; you decide whether you want to walk to the training simulator, briefing room, film room, etc.

The staff of LucasArts were big fans of Timothy Zahn’s Heir to the Empire trilogy of novels. Thus Grand Admiral Thrawn, the books’ most memorable character, shows up as a younger Imperial officer here.

TIE Fighter‘s in-flight graphics weren’t all that spectacular to look at even by the standards of their day, given that they were implemented in standard VGA rather than higher-resolution SVGA. Wing Commander III, which appeared the same year, did embrace SVGA, and looked much better for it. Luckily, TIE Fighter had other things working in its favor…

Having decided to present the most complex battles yet seen in a space simulator, TIE Fighter needed to provide new ways of keeping track of them if it was to remain playable. Thankfully, the developers were up to the task, devising a whole array of clever command-and-control tools for your use.

You wind up spending almost as much time fighting other Imperial factions as “Rebel scum.” Call it a cop-out if you must…

You fly the climactic final mission side by side with Darth Vader. Unable to secure the services of James Earl Jones to voice the role, LucasArts had to settle for a credible soundalike. (Ironically, Jones did agree to provide voice acting for a game in 1994, but it wasn’t this one: it was Access Software’s adventure game Under a Killing Moon. He reportedly took that gig at a discount because his son was a fan of Access’s games.)



Both X-Wing and TIE Fighter later received a “collector’s edition” on CD-ROM, which added voice acting everywhere and support for higher-resolution Super VGA graphics cards, and also bundled in a lot of additional content, in the form of the two expansions that had already been released for X-Wing, the single TIE Fighter expansion, and some brand new missions. These are the versions you’ll find on the digital storefronts of today.

Time has added a unique strain of nostalgia to these and the other early LucasArts Star Wars games. During their era there was still an innocent purity to Star Wars which would be lost forever when George Lucas decided to revive the franchise on the big screen at decade’s end. Those “prequel” films replaced swashbuckling adventure with parliamentary politics, whilst displaying to painful effect Lucas’s limitations as a director and screenwriter. In so thoroughly failing to recapture the magic of what had come before, they have only made memories of the freer, breezier Star Wars of old burn that much brighter in the souls of old-timers like me. LucasArts’s 1990s Star Wars games were among the last great manifestations of that old spirit. The best few of them at least — a group which most certainly includes TIE Fighter — remain well worth savoring today.

(Sources: the books How Star Wars Conquered the Universe by Chris Taylor, Droidmaker: George Lucas and the Digital Revolution by Michael Rubin, and the X-Wing and TIE Fighter Collector’s Edition strategy guides by Rusel DeMaria, David Wessman, and David Maxwell; Game Developer of February/March 1995 and April/May 1995; Compute! of March 1990; Computer Gaming World of April 1988, November 1988, October 1989, January 1990, September 1990, December 1990, November 1991, February 1992, September 1992, June 1993, October 1993, February 1994, October 1994, and July 1995; PC Zone of April 1993; Retro Gamer 116; LucasArts’s customer newsletter The Adventurer of Fall 1990, Spring 1991, Fall 1991, Spring 1992, Fall 1992, Spring 1993, and Summer 1994; Seattle Times of December 25 2017; Fortune of August 18 1997. Also useful was the Dev Game Club podcast’s interview with Lawrence Holland on January 11, 2017.

X-Wing and TIE Fighter are available as digital purchases on GOG.com.)

 
 

Tags: , , , , ,

Project: Space Station, Part 3: The Game

Project: Space Station

Stan Kent and his company AstroSpace may have exited the stage, but Avant-Garde Publishing, the new owners of HES, weren’t ready to give up on Project: Space Station. They reached out to Larry Holland to finish the game.

Holland shares with Stan Kent some impressive academic credentials, but he’s otherwise his polar opposite: a quiet just-get-the-job-done sort who has always avoided interviews and public exposure as much as possible. After earning a Bachelors in anthropology and archaeology from Cornell in 1979, he spent two years out in the field, working on digs in Africa, Europe, and India, before starting on a PhD at Berkeley. He settled there near Silicon Valley just as home computers were beginning to take off. He bought himself one of the first Commodore 64s, learned to program it, and was hired by HES in early 1983 to port action games like Super Zaxxon to it. He proved himself clever and reliable at the work, enough so that it was decided to dump Project: Space Station in his lap. It was just the chance Holland needed to show what he could really do. He pared down and refined AstroSpace’s shaggy mixture of advocacy and simulation, synthesizing a bunch of disparate pieces that looked more like engineering tools than pieces of a game into something that fit on a single disk side and was actually fun — and all without sacrificing the spirit of the original concept.

Project: Space Station starts you out on July 1, 1985, with two space shuttles, $10 billion(!), and high hopes. You’ll have to plan and build your station module by module, while also, this being the new era of space exploration, earning enough from commercial satellite launches and the results of the experiments you run up there to keep the project going. From the perspective of today especially, Project: Space Station is a simulation of an alternate history in which the American space station not only got funded and built in the 1980s but all of NASA’s manned-space initiatives — most notably the shuttle — lived up to all of their plans and hopes. In this timeline shuttle launches are truly routine. You can assign a couple of astronauts to a shuttle, launch it, bring them down a few days later after having delivered their payload, then launch them again a week later like the space truckers they are. In a small concession to reality, every ten launches or so the shuttle might lose some thermal tiles, thus needing an extra ten days or so for repairs, but the thing blessedly never blows up or burns up. You even have clients asking you to hoist satellites for them for $40 million to $70 million a shot, and the shuttle is cheap enough to operate that you can turn a profit on that; pack several satellites into the cargo bay and send ‘er up before your arch-rival, the European Space Agency with their boring unmanned rockets, steals the job from you.

Project: Space Station Project: Space Station

The first thing you notice when you first start Project: Space Station is how friendly it strains to be. I’ve made it a point to mention in the past how the innovations of the Lisa and Macintosh trickled down to cheaper machines in a way that gave the Apple computers influence far out of proportion to their actual sales numbers. That influence is all over Project: Space Station; this program simply couldn’t have existed a couple of years earlier. Everything is presented via icons and menus, navigable with the trusty joystick, while the space-station design screen has you sketching out your station by pulling modules into place with a “mouse” pointer. There’s even a — get this — context-sensitive help system to guide you through the game along with some canned tutorials to get you started. Hardware limitations inevitably restrict all of this in practice, but Project: Space Station feels like it was looking ahead about ten years into the future of software — or just looking very carefully at what was happening on the Mac, which largely amounted to the same thing.

The other obviously extraordinary thing about Project: Space Station is the fact that it runs entirely in real time. There were plenty of grand strategy games already available for machines like the Commodore 64; SSI alone had published dozens of them by 1985. But, true to that company’s roots in cardboard wargaming, most of these felt like tabletop rulesets that had been translated to the computer. Project: Space Station, however, is undeniably a born-and-bred computer game. There are no turns here. As you navigate through its screens the clock is constantly ticking, sometimes much to your consternation, as when you find yourself with research projects that need to be tweaked, a shuttle costing you money in space that needs to be landed ASAP, a precious satellite contract about to be awarded to those pesky Europeans, and another shuttle on the launch pad about to begin its countdown. Where do you begin? This game does nothing if not teach how to prioritize and how to manage your time. It also does a great job of not making you feel like you’re just tinkering with a dry spreadsheet, a syndrome that afflicted many other contemporary strategy games, a genre not exactly known for its graphics at a time when graphics in general were, shall we say, somewhat limited in comparison to today. Project: Space Station‘s graphics are actually quite nice for the era and the machine. But more importantly, you get to do such a variety of stuff in this game that it stays fresh and interesting for a surprisingly long time. When you’re tired of budgeting, there’s a shuttle to land via a real-time action game; when you’re tired of tweaking research projects, there’s that new laboratory module to move into place via an EVA.

So, let me walk you quickly through the different sections of the game, each of which is represented by and always accessible via its icon at the top of the screen.

Project: Space Station

The Plan section is the expected spreadsheet portion of the game, where you allocate funds to your different departments; buy the actual pieces of the station which you’ll be assembling, erector-set-like, in orbit; hire and fire astronauts; and provision and schedule shuttle launches. The most interesting and surprising part of this section is the astronaut-selection process. Each of the 32 possible astronauts has not only a professional specialty but also a personality. You have to consider whom you put together, because personality clashes can and will result if you put, say, a control freak together with a more laissez-faire kind of fellow. You’ll grow attached to some of these folks, and you’ll feel awful if you kill one or more of them by stranding a shuttle in orbit or botching an EVA.

Project: Space Station

Shuttle launches are affected by the weather; you’ll want to watch it carefully, and delay the launch if conditions are too unfavorable. Occasional mechanical snafus will also cause delays. Once the candle is lit, you take control, guiding the shuttle into orbit via a little action game that doubtless would have horrified the original Project: Space Station team with its lack of realism but is nevertheless a nice, not-too-difficult break from the strategic side of the game. If you stray too far off course, the shuttle will end up parked in orbit far from your station, making any EVA operations to expand or repair it much more time consuming and hazardous.

Project: Space Station

Shuttle landings also involve a simple action game. Rough landings can result in damage to the shuttle and extra repair time before it can fly again.

Project: Space Station

The Station section is there mainly to let you transfer astronauts between a shuttle in orbit, which can hold up to six people, and the station, whose capacity depends on how many crew modules you’ve bought, flown into orbit, and linked up, along with how much additional station infrastructure you’ve built to support the crew: power modules, radiator modules to disperse heat from the power modules, emergency modules to protect the astronauts from the occasional solar flares. And of course there’s not much point in having people at the station without something for them to do — meaning research projects, which require laboratory modules, which require yet more power modules, which… you get the picture.

Project: Space Station

The EVA section is the most fanciful part of the game. You venture outside shuttle and station using worker pods that have everything to do with 2001: A Space Odyssey and nothing to do with anything NASA was likely to come up with in the mid-1980s. You use the pods to construct the station, clear occasional debris that’s made its way into the station’s orbit, and launch commercial satellites; in the screenshot above, I’ve just attached a Payload Assist Module to a satellite to boost it into geosynchronous orbit. It’s very easy to run out of fuel or damage a pod so badly that it’s no longer functional. When that happens, you’d best have a backup pod that you can use to rescue the first before oxygen runs out. Once you’ve experienced a single time the excruciation of waiting for an astronaut to die from oxygen deprivation, unable to do anything about it, you’ll make sure you always do, believe me.

Project: Space Station Project: Space Station

Finally there’s the real heart of the game, the R & D section; after all, it does bill itself on the box as a “science simulation in space.” You can have up to four research projects running at once, assuming you have a station that can support them. While you receive a generous initial budget which you can supplement with satellite launches, your research should eventually become the heart of your revenue stream, as it is the heart of the game’s rhetorical argument for a space station as a fundamentally practical, commercial proposition that will eventually pay for itself and then some. Some projects can also yield practical improvements that will make your station run more efficiently. There are 40 impressively specific projects to choose from, divided into 9 categories: Agriculture, Astronomy, Bio Medical, Earth Watch, Geology, Materials Science, Meteorology, Physics, and Space Technology. It’s a big thrill when one yields a major breakthrough, enough so that you’ll probably be willing to ignore questions like why it’s necessary for people in space to examine the satellite imagery used to make a crop survey.

I don’t want to overstate the case for Project: Space Station. While thoroughly entertaining in its early stages, it does have a litany of little problems that are very likely to turn you off eventually. Many involve research. If you don’t happen to be watching an R & D project when a milestone is completed, it’s very easy to miss it; once replaced by something else, each R & D notification from each project is lost forever whether you’ve actually read it or not. That’s a very bad thing because each project yields exactly three milestones, after which it continues to suck money from your budget but doesn’t earn you much of anything. You’re thus often left uncertain whether a given project has run its course or a big windfall might be just around the corner. Even more infuriating is when a project starts saying a “key scientist” is needed for research to continue, without telling you whom or even what type of scientist you should be looking for. Gameplay then devolves into a tedious — and expensive — ferrying up of shuttleloads of possibilities and swapping them in one at a time, whilst you wonder what the hell sort of a research team would just tell you they feel the need for someone else but not whom or what for.

There are a number of other areas like this where the game’s ambitions outrun the capabilities of an 8-bit 64 K computer with a blocky low-resolution screen, where you feel like the game just isn’t telling you things you really ought to be able to know. Which research projects are expected to yield the most immediate returns for the early days of your station? When can you expect the next injection of financial assistance from Congress, and how much will it be? If a research team is suffering personality clashes, who exactly is having a problem with whom? And then there’s the goal problem, in the sense that there really isn’t one. The whole affair must presumably spin down into entropy at some point, when you’ve done all of the research projects and can no longer sustain your station, although it seems that can take a very long time; on his now-defunct blog dedicated to the game, Geof F. Morris posted screenshots of a station that lasted into 2007 in game years. I would venture to guess that Larry Holland was not so much unaware of these problems as just unable to push the hardware any further to correct them. Project: Space Station‘s sensibility is so modern that it can lead us to expect more from it than a Commodore 64 can deliver even under the control of a great programmer.

The game didn’t have much commercial luck. It was released at last in late 1985, some three years after Stan Kent had first conceived it and just a few months before the Challenger, which features as one of the two shuttles in the game, blew up on its way to orbit and suddenly made Project: Space Station‘s sunny optimism about a future in space feel tragically anachronistic. Avant-Garde Publishing went under shortly thereafter, marking the final end of the HES label. Yet Project: Space Station wasn’t dead yet. It ended up in the hands of Accolade, who rereleased it in 1987 as a member of their Advantage line of budget games, with some small but important changes: the Challenger was replaced by the Discovery, and the starting date was moved up to 1987. It made no great impact then either, and faded away quietly into commercial oblivion at last.

Surprisingly given its (lack of) commercial performance, Project: Space Station spawned a modest, oddly specific sub-genre of space-station-building games that also included Electronic Arts’s Earth Orbit Stations as well as Space MAX from the perfectly named Final Frontier Software and the more fanciful E.S.S. Mega from Coktel Visions, which replaced American with European boosterism. Buzz Aldrin’s Race into Space, a management simulation of the Moon race, might also be considered something of a spiritual heir. All except that last share with the space shuttle itself today a certain melancholia. Thoroughly of their time as they are, they can be a bit disconcerting to us in ours, showing as they do ambitions never fulfilled, grand adventures never quite undertaken.

Project: Space Station is even more fascinating as a piece of history than many of the titles I write about, being a document of our sunniest expectations for a future in space prior to the Challenger explosion that changed everything. But even taken as just a game, it’s impressive and noble enough that I’d recommend you play it for a little while in spite of its issues. You can download the original Commodore 64 version from here if you like, or find its ports to the Apple II and IBM PC on other sites. Most games — even the equally-noble-in-its-own-way Ultima IV — treat life so cheaply, sending you off to slaughter in the name of becoming a hero. It’s nice to play a game that’s all about preserving the precious lives of your astronauts, that shows that a game can be absolutely without violence and still be riveting, that shows that heroism need not come with a body count. Would that ludic history had many more like it.

(Larry Holland — who in later years tended to be billed as Lawrence Holland — has generally managed to avoid talking much about his personal life and background as well as his early career. The best print source is a profile in the spring 1992 issue of LucasArts’s newsletter The Adventurer. While I generally try to avoid wikis or overly fannish sources, his page on Wookiepedia is also very complete and appears to collect just about everything we know about him, scanty though it may be.)

 
 

Tags: , ,

Project: Space Station, Part 2: The Dream

A proposed NASA space station with shuttle docked

As long as there has been a space program, there have been space-program boosters. With budgets dwindling and interest waning after Apollo 11, however, NASA suddenly needed them as never before. Various people started various organizations to educate, to advocate, to lobby, sometimes even to agitate the case for space. Briefly among the more prominent of these folks during the early 1980s was Stan Kent, a precocious English rocket scientist still in his mid-twenties.

Growing up working class in the industrial city of Wolverhampton in the West Midlands, Kent wrote to NASA asking for more information about the Titan rocket used to hoist the Gemini space capsules into orbit. Much to his family’s surprise, they sent it, cementing a passionate love affair with space and with NASA. (NASA was notably wonderful about this sort of thing in their 1960s heyday; many a starry-eyed kid all over the world received a similar thick envelope filled with pictures and articles for no charge but the cost to mail a letter to Houston.) At age 15, he demonstrated for the first time what would prove to be a lifelong knack for self-promotion. Determined to find a way to study rocket science, he entered a contest to design a functioning powered aircraft which won him national attention inside his home country and was enough to recommend him to a wealthy philanthropist in Santa Clara, California, named Austen Warburton. With Warburton’s assistance, he came to the United States to attend university at the age of 17, and graduated from Stanford with a Masters in aerospace engineering in 1978 at the age of 22, winning the prestigious Herman Oberth Gold Medal in the process for his paper on “The Space Shuttle External Tank as a Reentry Module.” He was soon working for Boeing and later Lockheed, and doing consulting jobs for NASA itself.

Kent’s public space advocacy began in 1979, when he got wind of proposals within NASA to stop monitoring the two Viking probes that had landed on Mars three years before simply because they couldn’t afford to continue to pay people to do it. He organized a Viking “charity” which presented NASA administrator Robert A. Frosch with a check for $60,000 to go toward continued monitoring on January 7, 1981. The sum would increase to over $100,000 in the months to come, then increase dramatically again when he organized with former astronaut and Moon-walker Pete Conrad to sell off recovered pieces from the old Skylab space station by way of further fundraising. (By that time Viking 2 had already gone offline due to a failed battery. Viking 1 would continue to transmit — and, yes, to be monitored — until a botched software update took it offline on November 11, 1982.)

Under the aegis of Delta Vee, the nonprofit corporation he set up with the assistance of Warburton and some aerospace colleagues, Kent stumped the country on behalf of space, appearing on television, on radio, in Omni magazine (with whom he did much of his advocacy in partnership), and in countless newspaper articles. He worked to set up a nationwide network of “neighborhood space centers” — “the McDonald’s of space” — and gave speeches to anyone who would have him. Far from your stereotypical rocket scientist, Kent made space cool in what the L.A. Times described as his “new-wave haircut, beige suit, purple shirt, and bright red tie”; he looked like “he might be a member of a rock band.” In September of 1981 he testified before the Congressional Subcommittee on Space Science and Applications at the age of just 25. His pitch emphasized a new, more pragmatic take on space very much in keeping with the dawning hyper-capitalism of the 1980s. The NASA that Kent described was fundamentally a practical enterprise whose work would bring scientific and technological breakthroughs to make life better for ordinary Americans, along with economic benefits to the country; Kent was fond of citing such dubious surveys as the one done in 1972 by Chase Econometrics, which claimed that every $1 spent on the space industry injected $10 to $15 back into the economy within five to seven years.

In that spirit, he and his partners soon set up a second, for-profit corporation they named AstroSpace. Its initial purpose was to research and hopefully to exploit a pet idea Kent called SOLARES: “Space Orbiting Light Augmentation Reflector Energy System,” a way to beam concentrated sunlight down to Earth for use as energy. In the meantime, though, the home-computer boom was happening. Soon Kent hit upon a more earthbound project for his company: to create a computer game that simulated the building and operation of the permanent space station that he and so many others felt represented the next logical steppingstone to Mars and beyond. By 1983 he had sold the idea to Jay Balakrishnan of Human Engineered Software, who loved big, high-concept edutainment titles.

Project: Space Station was certainly that. The game that Kent and Balakrishnan described (separately) to InfoWorld magazine in 1984 — it was quite obviously the HES product that the latter was most excited to discuss — filled nine disk sides. Balakrishnan:

It’s an absolute simulation. First of all, to start you have to go to Congress to requisition a budget. You have to choose your scientific team that will comprise the space mission. There’s a book, almost like a story, with different fictitious characters that you can select your team from. There’s a whole page of biographical data on each person — where they went to school, whom they married, whether they’re stable individuals or not, and so on. Then you must decide on what kind of industry you’re going to develop in space — for example, if you want to make ball bearings or crystals or whatever.

Then you design your space station. Each one is a different module. You might build a plant area, living quarters, etc. Then you run a simulation. Now the plant starts working, giving oxygen and life, and the industry starts working. You see that it’s a viable operation. Finally, after you have overseen everything, you resign your post. You were the director of a successful space industry, so you get your gold watch at the end. Of course, during the game all kinds of random things can occur. Maybe you’ve gone over budget. So you go back to Washington, D.C., and appeal for a higher requisition to keep the business going.

Together Kent and Balakrishnan organized an “advisory” board for the project that consisted of Kent’s colleagues in the aerospace industry along with the high-school students who would be the game’s most obvious target market, all “overseen” by the hapless, computer-illiterate Leonard Nimoy (who must have been wondering by this point why he’d signed on with HES at all).

I find this original conception of Project: Space Station fascinating as an early example of a computer game with an explicit real-world rhetorical goal. One could call it without hyperbole propaganda, a political advertisement for a NASA space station. The justifications it makes for such a project are the same as those Kent was making in his speeches, and, indeed, those that Ronald Reagan more obliquely referred to in his State of the Union address of 1984. In Project: Space Station, players would enjoy success not so much in the form of exploratory firsts or pure scientific breakthroughs but rather that of crop surveys that would make American agriculture more efficient, new semiconductors that would make American computers more powerful, lasers that would revolutionize American manufacturing, even the proverbial cure for cancer. If it wasn’t always entirely clear why some of these research projects had to be done by people in space, well, that was a problem Project: Space Station shared with some of Kent’s speeches.

AstroSpace's original Project: Space Station

AstroSpace's original Project: Space Station AstroSpace's original Project: Space Station

AstroSpace's original Project: Space Station

This huge game being developed by a bunch of aerospace people with no experience in game development was of course all but doomed to failure. Kent and company did manage to get far enough to produce some intriguing screenshots that, as published in the April 16, 1984, issue of InfoWorld, stand today as the only tangible artifacts left to us from this version of Project: Space Station. The whole thing collapsed by the end of that year, with HES going bankrupt and being absorbed by Avant-Garde Publishing and AstroSpace coming to an abrupt end along with Kent’s time as a space advocate. He made an extreme and kind of bizarre change in life direction, opening back in Santa Clara a night club called One Step Beyond that became a regular stop on the college-rock touring circuit for some years. Today he writes erotica, hosts naughty events at a sex shop, and is something of a fixture of the Southern California nightlife scene while apparently still keeping his hand in from time to time as a rocket scientist. In 2012 he consulted on the perfect combination of all his interests: a proposed Playboy space station.

(Stan Kent’s space advocacy is chronicled in the August 3 1980 Washington Post, the January 8 1981 and November 12 1982 New York Times, and the July 22 1982 L.A. Times. The two InfoWorld articles that describe Kent’s original vision for Project: Space Station are in the April 16 1984 and September 3 1984 issues. A transcript of his testimony before Congress is contained in the government publication “Future Space Programs, 1981: Hearings Before the Subcommittee on Space Science and Applications of the Committee on Science and Technology, U.S. House of Representatives, Ninety-seventh Congress, First Session, September, 21, 22, 23, 1981.” The space-advocacy movement of the late 1970s and early 1980s and the place of a space station within are treated at length in Reaching for the High Frontier by Michael A. G. Michaud, available online from The National Space Society.)

 

Tags: , ,

Project: Space Station, Part 1: The Reality

Space Shuttle

It was hard for a space-obsessed kid growing up in the 1980s not to feel just a little bit envious of the previous generation. The late 1960s had marked the climax of one of the most glorious adventures in human history, and the first one that, thanks to the miracle of mass media, everyone could share in in real time. Even the most non-technical and non-scientific among us could understand the clear progression that climaxed in that “giant leap for mankind”: Apollo 7 tested the Apollo capsule in Earth orbit; Apollo 8 voyaged to the Moon and circled it; Apollo 9 tested the lunar lander in Earth orbit; Apollo 10 was the dress rehearsal; Apollo 11 was the big one, July 20, 1969, the day that changed everything forever for humanity. Or so it must have seemed at the time. By the early 1980s it could feel hard to believe the Moon landing had actually happened. In place of Apollo we got the space shuttle, NASA’s glorified space truck. In place of the clear milestones of Apollo we got a space program whose strategy seemed akin to the missions of the shuttles themselves: go up, circle around for a while doing some things people weren’t really too clear about, then come back down. Oh, we dutifully put together our shuttle model kits and dreamed of seeing an actual launch, but something was missing.

The program to make a reusable space plane was first conceived even before that first Moon landing, when 2001: A Space Odyssey was in cinemas showing a vision of the near future in which a flight into Earth orbit was as routine as a flight for the opposite coast. To achieve such a vision, clearly something would have to change. An Apollo Moon rocket weighed slightly over 450,000 pounds without fuel, of which 12,250 pounds — less than 3 percent of the total — would make its way back to Earth at the end of a mission in the form of the non-reusable command module. The rest was cast away at various stages of the mission, making Apollo 11’s trip to the Moon, if one of — perhaps the — most inspiring voyages in human history, also one uniquely wasteful and completely unsustainable as a model for a future of routine space flight. After all, while NASA had been enjoying effectively blank checks from Congress through the Space Race, it didn’t take a Nostradamus to realize that that was likely to change in a hurry as soon as the Moon was achieved and American pride satisfied.

The budget cuts, when they came, were even more draconian than anticipated, costing NASA three of their planned ten Moon landings — another, Apollo 13, never made it there for other reasons — and forcing them to similarly scale back Skylab, the United States’s first (and to date, outside of the International Space Station, only) space station. The space shuttle survived only by making a series of painful compromises and an unholy alliance with the Air Force that would see it used for classified military missions — basically, to launch a new generation of bigger and heavier spy satellites — about 30 percent of the time. It was a partnership that neither NASA nor the Air Force really wanted. Robert Seamans, a former NASA administrator who had become Secretary of the Air Force by the time the deal was made, thought it was “asinine” to try to coordinate with a civilian agency and put astronauts’ lives at risk instead of just building a cheaper, simpler unmanned rocket for the purpose. But his and other practical voices were overwhelmed by those of the bureaucrats and the politicians.

An early space-shuttle concept which used short, straight wings and a different reentry profile to reduce heat buildup.

An early space-shuttle concept which used short, straight wings and a different reentry profile to reduce heat buildup.

The Air Force partnership had tragic consequences for the shuttle. In order to carry the big spy satellites the Air Force anticipated launching, the shuttle’s cargo bay had to be bigger and wider than it might otherwise have been, giving the shuttle its distinctively chunky, less than aerodynamically ideal shape. While occasionally useful, much of that space went empty much of the time. In case the Cold War should ever turn hot, the Air Force also demanded that it be possible to launch the shuttle from Vandenberg Air Force Base in California, deploy a satellite, and land again back in California within one orbit without ever flying over Soviet territory, thus minimizing its exposure to space-borne or terrestrial weaponry. In aeronautics jargon, this necessitated that the shuttle have a considerable “downrange” or “crossrange” capability to glide off its normal orbital path, which in turn necessitated the shuttle’s delta-shaped wings that made it less than a pilot’s delight. John Young, the first man to pilot a shuttle to Earth from space, compared it to trying to fly a brick. Other pilots would call landing the shuttle a “controlled plummet,” while passengers compared it to a “dive-bomber run.” Worse, the final design generated far more heat on reentry than would have NASA’s earlier concepts, heat which engineers could combat only through the use of heavy, cludgy thermal-protection tiles that were a constant worry and labor sink throughout the program’s history. Each of the 35,000 tiles on the shuttle was a one-off piece that had to be custom manufactured, and every single one of them had to be carefully inspected by hand after every single launch in the hopes of averting disaster on the next mission. In spite of NASA’s best efforts, the disaster that was perhaps inevitable finally came on February 1, 2003, when the Columbia burned up on reentry. A more elegant shuttle could have minimized or even eliminated the tiles altogether, and saved the lives of seven astronauts.

Well before the Columbia and even the Challenger disasters, a feeling dogged engineers and astronauts alike that the shuttle just wasn’t as safe as it should be in still other ways. This was largely down to yet more concessions and compromises to budgetary realities. In place of a reusable booster section which would have blasted the shuttle into space and then glided — possibly with the aid of a human pilot — back down to a soft runway landing, the shuttle got a massive external fuel tank that would just be cast away, Apollo-style, and a pair of solid-fuel booster rockets that floated back via parachute to drop into the ocean. Essentially little more than hollow metal cylinders filled with propellant, the boosters could be reused, but were problematic in other ways. The shuttle was the first manned space vehicle ever to use solid rockets as a primary means of propulsion; they had heretofore been considered too dangerous because they can neither be throttled nor shut down entirely if something should go wrong during a burn. And, unlike earlier spacecraft, the shuttle was equipped with no emergency escape mechanism whatsoever for launches. Just as the heat tiles’ failings cost the last crew of the Columbia their lives, this lack may have cost the last crew of the Challenger, who appear to have been alive and conscious for at least some portion of their fatal fall back to Earth.

I don’t mean to say that the space shuttle wasn’t a crazily magnificent feat, nor to cast aspersions on the engineers who made it (usually) work in the face of all the cutbacks and compromises, nor to say that I wouldn’t have jumped at the chance to fly in it, safety questions and all. The shuttle certainly made for a cool sort of spacecraft, and an almost unbelievably comfortable one. If hardly the lap of luxury by earthbound standards, it was ridiculously roomy by comparison with the American spacecraft that preceded it and those (if any) that appear likely to follow it. Certainly the earliest astronauts in their “Spam in a can” capsules, who had to fight just to get a window, would have loved this craft that an astronaut got to actually fly.

Yet it’s hard for even the most generous observer to avoid noting just how massively the space-shuttle program overpromised and underdelivered. Originally projected as capable of launching again just one week after returning to Earth, the timetable was revised by the time of the Columbia‘s maiden flight in 1981 to one month. No shuttle ever came close to meeting even this timeframe. What with all of the repairs and inspections that were needed — not least to those pesky tiles — a shuttle that launched three times in a year was doing very well for itself. Nor did the huge savings supposedly enabled by this reusable spacecraft ever really materialize. The cost of each launch averaged over the life of the program ends up in the $1.3 billion to $1.5 billion range, at least ten times what it costs the Russians to put a three-man crew into space via their trusty old Soyuz space capsule and a conventional expendable rocket — and, while fourteen people died aboard the Challenger and Columbia, the Russians haven’t lost a cosmonaut since 1971. The shuttle lacked the romance of the Apollo program, but that was rather implicit in its purpose all along. More damningly, it failed in its goal of making spaceflight a safe matter of (relatively) inexpensive routine.

For much of the shuttle’s lifetime, NASA had trouble answering a fairly fundamental question: just what was it really good for? In the optimistic early days of the program they floated the idea that the shuttle might be a viable commercial proposition, an actual moneymaker for the agency. Other countries as well as private companies would pay NASA to truck their satellites into space. But this never materialized in any significant way; the shuttle was far, far too expensive to launch, not to mention too prone to unexpected delays and other problems, to compete with cheap, reliable unmanned rockets for commercial satellite launches. Twice West Germany paid NASA to launch the shuttle and give them free use of a Spacelab laboratory module installed in the cargo bay, but that was about as good as it would ever get for the shuttle as a commercial entity.

The shuttle also failed to live up to expectations as a tool for the military. Work on the planned alternative launch site for military missions at Vandenberg fell far behind schedule, and was finally abandoned in the wake of the Challenger disaster after over $4 billion had been spent. Of 27 military personnel recruited and trained to serve as astronauts on the shuttle, only 2 ever made it into space due to disorganization, turf wars, and poor inter-agency communication. Instead the military had to content itself with essentially sub-contracting its payloads out to NASA; the missions launched from the Kennedy Space Center and featured the usual rotating crew of civilian astronauts. These so-called “Department of Defense” missions, which numbered nine between 1985 and 1992, always felt a bit farcical. Their satellite payloads, despite usually being officially considered “classified,” were an open secret at best around the Kennedy Space Center; during the run-up to the second of these launches, to put a Defense Satellite Communications System into orbit in October of 1985, even reporters were walking around in “DSCS” tee-shirts. Never happy about being bound to the shuttle in the first place, the military started working in earnest to find an alternative following the Challenger disaster and the subsequent thirty-month hiatus in launches. That alternative turned out to be, inevitably, a cheaper and simpler unmanned rocket in the form of the Titan IV, latest in a venerable line of military and civilian workhorse launchers.

Lots of good science was done aboard the shuttle betwixt and between all these dashed expectations. Yet it was hard for even a space-loving kid, much less the general public, to get all that excited about experiments in applied plasma physics or materials science. After the novelty of the first few flights which proved the crazy contraption actually worked, it was just hard to get excited about the space shuttle in general. Only one tantalizing prospect seemed like it had a chance of changing all that: a permanent station in space, to be built, supplied, and maintained by the shuttle.

Artist's conception of the shuttle servicing an American space station.

Artist’s conception of the shuttle servicing an American space station.

This idea of a space station had been bound up with that of the shuttle itself right from the beginning. After all, that inspiring 2001 future had featured both, hadn’t it? Without a space station, where was the space shuttle to actually go? (“Nowhere,” some would soon be saying.) In this, NASA’s original vision for the post-Apollo future, the space shuttle was to be just that, the shuttle bus ferrying people, materials, and equipment up to where the real action was happening. The shuttle wasn’t supposed to be exciting in itself. The real excitement would be happening up there, as a permanent settlement in space grew and developed and just maybe started thinking about building its own spacecraft right there in orbit to visit the Moon, Mars, the asteroids, perhaps Halley’s Comet (which was conveniently due for a visit in 1986). NASA anticipated building both parts of the program — the station and the ancillary shuttle to service it — in tandem. It was only when the budget cuts started to bite that they had to make the hard decision to go ahead with the space shuttle alone as a necessary precursor to the station. If the shuttle without the space station felt like a spacecraft without a purpose, that’s because it largely was.

And so NASA continually tried to find a way to get the space-station project out of stasis. During the mid-1970s some planners floated the intriguing idea that it might be possible to reuse the recently abandoned Skylab as the core of a more permanent station. Plans were mooted to send an early shuttle mission to Skylab with a rocket pack that could be used to push it out of its decaying orbit. Later missions would then have refurbished, repaired, and reactivated the station for habitation. Such plans were doomed, however, by delays in the shuttle program and by heavy sunspot activity that caused Skylab’s orbit to decay more quickly than anticipated. On July 11, 1979, Skylab crashed to Earth, raining debris down on Western Australia and causing NASA considerable embarrassment almost two more years before the eventual maiden flight of the Columbia.

The space-station project remained alive after that as a theoretically real thing, but generated little more than sketches and plans for which NASA could never seem to amass more than a fraction of the necessary funding. In his January 1984 State of the Union Address, President Reagan gave the project a badly needed shot in the arm via a would-be Kennedy-esque pronouncement.

Our next frontier [is] space. Nowhere do we so effectively demonstrate our technological leadership and ability to make life better on Earth. The Space Age is barely a quarter of a century old. But already we’ve pushed civilization forward with our advances in science and technology. Opportunities and jobs will multiply as we cross new thresholds of knowledge and reach deeper into the unknown.

Our progress in space — taking giant steps for all mankind — is a tribute to American teamwork and excellence. Our finest minds in government, industry, and academia have all pulled together. And we can be proud to say: We are first; we are the best; and we are so because we’re free.

America has always been greatest when we dared to be great. We can reach for greatness again. We can follow our dreams to distant stars, living and working in space for peaceful economic and scientific gain. Tonight, I am directing NASA to develop a permanently manned space station and to do it within a decade.

A space station will permit quantum leaps in our research in science, in communications, in metals, and in lifesaving medicines which could be manufactured only in space. We want our friends to help us meet these challenges and share in their benefits. NASA will invite other countries to participate so we can strengthen peace, build prosperity, and expand freedom for all who share our goals.

Couched in empty political tautologies as it is (“America has always been greatest when we dared to be great?”), that declaration did lead to some action: an official Space Station Program Office was established at the Johnson Space Center, strategic plans and blueprints were created with more enthusiasm. Any momentum was abruptly dissipated, however, by the Challenger disaster of January 28, 1986, an event which stopped American manned spaceflight in its tracks for two and half years of investigating and soul-searching. The shuttle program would never quite be the same again, while hopes for the space station were all but dashed. Reagan’s successor George Bush gave NASA another apparent boost in a major speech on July 20, 1989, refloating the old idea of the station, now to be named Freedom, as a base for launching future missions to the Moon and Mars. But that speech was just another in an emerging tradition of Presidents making grand pronouncements about space exploration that come to nothing. Just as had happened with the space shuttle, project Freedom was steadily scaled back and compromised in the face of dwindling budgets. In 1993, NASA’s independent Freedom was finally folded into the International Space Station, itself only a shadow of what NASA had originally planned for the station to be.

Even at that, though, the ISS finally provided the space shuttle with a purpose for which it seemed eminently suited. Beginning with the first ISS building block which the Endeavor carried into orbit in 1998, the aging shuttle fleet got from the station a new lease on life and a new sense of purpose; this was what the shuttle had been designed to do all those years ago. But then came the Columbia disaster of 2003, and all the old doubts resurfaced. It was almost with a sense of relief that NASA retired the shuttle at last in 2011, before any more lives were lost, even if doing so left them with no way to get people into space at all for what looks to be, at best, some years to come. It was hard to escape the feeling as the shuttle fleet was parceled out to museums that something had gone horribly wrong in the aftermath of Apollo, that a brilliant beginning had been squandered.

(A very good short summary of the shuttle program and its discontents is found in The Final Countdown by Pat Duggins. For more on the shuttle as a military vehicle, see this article at Smithsonian Air and Space. For more on the drawbacks of the shuttle’s design and the alternative once proposed by Max Faget, see this article at The Space Review.)

 

Tags: , ,