Some game developers are drawn towards projects because they represent a challenge, or the chance to work on fresh hardware. Others may feel attracted to contributing to the development of a particular game because of its subject matter or the concept upon which it is based. Doug Lanford has experienced all of these factors, and furthermore he found them all in a single project.
"I completed my Electrical Engineering degree in 1991, and then moved to the San Francisco Bay Area where I ended up getting a job as a game tester for Sega of America," Lanford explains. "A few months later Sega was building their first internal development studio — the Sega Multimedia Studio — and discovered me already working there. I spent four years at Sega, working on two Sega CD games: Jurassic Park and Wild Woody. As I was finishing Wild Woody, several of my co-workers left Sega and joined GameTek to start working on Robotech. Six months later, they offered me a job at GameTek, since they needed another programmer, as well as a dedicated fan of Robotech to help steer the design...how could I refuse?"
Lanford's love of the classic anime series — which is in fact a mash-up of Japanese shows Super Dimension Fortress Macross, Super Dimension Cavalry Southern Cross and Genesis Climber MOSPEADA — led him to assume a role on the project which went way beyond just programming. "Primarily I was the junior of two software engineers on the project," he explains. "However, we all wore multiple hats on the project, so I also served as one of the story writers and game designers. When I arrived at GameTek, they had been working on the title for about a year, but very little work had been done on the game itself. Most of the work up to that point had been on getting the beginnings of a game engine working that could display things on screen and so on. There was no 'gameplay' at that point. Robotech Academy — which is what the game was known as when I came on board — consisted of a three or four page high-level design document that GameTek had thrown together a year before to help get the Robotech license. The idea of it was that the entire game would take place before the events of the cartoon, and all of the action would be in simulators as you train at the Robotech Academy as a cadet. It didn't have much story or excitement to it. When they asked my opinion, I threw it out and started from scratch."
GameTek was happy for Lanford to steer the project, but the company did place some restrictions in his path. "It had to be based on the Macross-era ships, as GameTek wanted to market the game in Japan as well, and had to have the Zentraedi as the main enemy," he says. "The game would include a new enemy in the form of a bunch of easy-to-render crystals. The crystals were there because at the time we did not know if the final N64 hardware would be powerful enough to display a bunch of more complex ships on screen at the same time, but we could show dozens of crystals. They had already been named 'Ebolians', which stuck." The name of this new enemy would also be reflected in the game's proposed title: Robotech: Crystal Dreams.
Lanford's knowledge of the original TV series stood him in good stead, as he was able to skilfully position the game so it made sense within the canon of the show. "I came up with the idea of a new war between the end of the Macross portion of the show and the beginning of the Robotech II: The Sentinels movie, against a lost fleet of Zentraedi allied with this new crystal intelligence. From there Ian Harac and I fleshed out and wrote the game story and dialogue."
While Lanford and the team at GameTek wanted to make sure the game would stay true to the original Robotech storyline, they had high aspirations for the gameplay as well. "We were building a space combat simulator similar in style to PC-based games like X-Wing, Tie-Fighter and Wing Commander," he explains. "Another interesting thing about the game was we were building it with a totally open world — what is often now called a 'sandbox' game. The player would have been able to fly anywhere he wanted, and his actions through the game would affect his reputation with the various characters he interacted with. For example, if you joined a convoy but then abandoned it in the middle of an attack, your reputation with the defence forces would take a hit."
However, Lanford is keen to stress that there was some kind of structure in place, as well. "The game did have a number of pre-built missions that drove the game story," he states. "We also planned a robust random mission generator as well. As the player completed missions they would gain credit at various shops which they could use to purchase fuel, ammo, and upgrades for their Veritech fighter." From a technical perspective, the sights were set high. "Everything in the game was to scale," Lanford says. "The Earth and Moon were their correct size and distance from each other, and you could fly right up next to Zentraedi capital ships which were four miles in length."
When Lanford joined the project, it was already being hyped as a key release for Nintendo's N64 system, which had at this point still not seen release. GameTek was recruited as one of Nintendo's decidedly-uninspiring "Dream Team" members, lending the project even more importance. As Lanford reveals, GameTek did a good job of inflating expectations prior to his arrival at the company. "Before I joined, GameTek had cobbled together some pre-rendered example shots that a lot of people believed were from the actual game, but actually were not," he reveals. "After I joined, most of the screenshots were from the actual game — including the pilot's reflection in the cockpit window. I had a fun time building that into the game, along with the character facial animation to lip-sync the recorded vocals."
It is these lush screens which fuelled a second wave of anticipation for the title; shots appeared in magazines all over the world and Robotech: Crystal Dreams slowly crept up the list of "must have" titles for the N64. However, even though consumer and press interest was growing, Lanford admits that there was a feeling within GameTek that the company had bitten off more than it could chew. "We definitely had our rough patches," he says. "One big problem was that GameTek was a small company that up to that point had mostly been a publisher of small-scale games. We were its first internal development group, and we were attempting to build a very ambitious game with a crew less than half the size it should have been. We also got caught in the trap of building a great game engine rather than working on a game. There always seemed to be some new fun feature someone would come up with — like the aforementioned pilot reflection, which was nifty but not required to play the game — and we never seemed to be putting it all together into a game."
Things took a turn for the worse in 1997, as GameTek filed for Chapter 11 bankruptcy. The troubled company managed to remain active, thanks largely to a publishing deal with Take 2 Interactive which brought in some much-needed cash, but for Robotech: Crystal Dreams the writing was on the wall. The game was a costly venture for the firm and there were serious doubts about whether or not it had the funds to continue development. An unlikely saviour came in the form of Capcom, which stated that it intended to publish the finished game. A similar deal was already in place for the Japanese market, but with Tomy handling distribution. "I believe the plan was for Tomy to distribute the game in Japan — as a Macross title with a few dialogue and story changes — and for Capcom to distribute it everywhere else," recalls Lanford. "However, neither seemed interested in pulling GameTek out of the fire or helping to complete the game." Because Tomy and Capcom wouldn't commit themselves to bankrolling development, the project was left in a decidedly grim position.
Despite GameTek's dire situation, Lanford admits that he was so focused on getting Robotech: Crystal Dreams finished that he was largely unaware of the problems facing the firm. "I didn't realize GameTek was in trouble until the day I showed up at work and was told people would be leading us individually to our desks to collect our belongings," he recalls. "I had an idea things were a little rough for a month or so before that, but didn't think GameTek was on the edge of closing its doors. The sad thing was that we had just finally got to a point that we were starting to see what the actual gameplay might be like. I had cobbled together some preliminary gameplay functionality so we could demo the game in the Capcom booth at the 1998 E3 Trade Show, and it was fun to fly around, target enemy ships and blast them to pieces. At a guess, we probably had another nine months or so of development to complete the game." Lanford and his team would sadly never get the chance.
Following GameTek's collapse, Take 2 Interactive acquired the company's assets but Robotech: Crystal Dreams was effectively abandoned. Lanford still has no idea why such a promising and high-profile title — with less than a year's development remaining — wasn't finished or at least offered to another publisher. "I've never gotten a good answer to that question," he says. "Over the next five or six months after GameTek died, I personally visited several companies to demo the game, but nobody ever bought the rights to finish it." Despite this, Robotech: Crystal Dreams still attracts a lot of attention, even today — and not just from hardcore fans of the anime series. "It is fun to know that it still lives a bit out there," Lanford says. "We really hoped to add our own little chapter to the Robotech saga with the game, so knowing people are still interested is gratifying."