Halo 2's Development Was a Gigantic Mess
As the plug is pulled on the original Xbox Live - and Halo 3 [http://www.amazon.com/Halo-2-Xbox/dp/B00008J7NZ/ref=sr_1_1?ie=UTF8&s=videogames&qid=1278536101&sr=1-1] originally one game, but the famous Halo 2 E3 demo was "all smoke and mirrors."
This week, Microsoft will be pulling the plug on its Xbox Live service for the original Xbox - on April 15th, to be specific [http://www.escapistmagazine.com/news/view/98069-Microsoft-Dropping-Online-Support-for-Original-Xbox-Games] - and with it dies the multiplayer for Halo 2, still played by thousands. It may be difficult to remember in a post-Modern Warfare 2 world, where millions play online on their Xbox 360s and PS3s (and the occasional Wii), but console online multiplayer used to be a pipe dream at best - until the massive success of Halo 2 cemented it as the way of the future.
There's a really fascinating (if long) read awestruck by the E3 2003 demo [http://www.eurogamer.net/articles/better-than-halo-the-making-of-halo-2-article], the game's engineering lead Chris Butcher said that said demo was all "smoke and mirrors."
"The graphics engine that we showed at E3 2003, driving around the Earth city... That entire graphics engine had to be thrown away, because you could never ship a game on the Xbox with it," said Butcher. "Through putting ourselves through hell, we were able to do a five-minute demo of it, but after we came back from E3 we had to admit that this graphics engine was never going to work - it was never going to support the kind of environments that are really important for a Halo game. So we literally scrapped the entire graphics engine and started from scratch."
The level with the Flood in the quarantine was a mere 20% of a "gargantuan, sprawling level that was meticulously built and hand-constructed, but that could never, ever have shipped in any engine," said Butcher - and those sorts of cutbacks were endemic of a troubled, disorganized, chaotic development cycle in which entire features and levels had to be tossed out in order to desperately make the ship date.
In fact, the game that actually hit shelves was only half of what Bungie had dreamed up. The other half? Well, they took a bit more time on it with a much more organized approach this time around, and eventually released it as Halo 3. That's right - the annoying cliffhanger ending to Halo 2? It wasn't supposed to be like that, in Bungie's original plan.
If you have the time, the whole interview is a really interesting read - detailing the game's "brutal" crunch [http://www.eurogamer.net/articles/better-than-halo-the-making-of-halo-2-article], among others.
Honestly, it's a testament to Bungie's skill as a developer that Halo 2 turned out as good as it did, despite the many, many troubles during the game's development. Flawed, yes, but also good.
Permalink
As the plug is pulled on the original Xbox Live - and Halo 3 [http://www.amazon.com/Halo-2-Xbox/dp/B00008J7NZ/ref=sr_1_1?ie=UTF8&s=videogames&qid=1278536101&sr=1-1] originally one game, but the famous Halo 2 E3 demo was "all smoke and mirrors."
This week, Microsoft will be pulling the plug on its Xbox Live service for the original Xbox - on April 15th, to be specific [http://www.escapistmagazine.com/news/view/98069-Microsoft-Dropping-Online-Support-for-Original-Xbox-Games] - and with it dies the multiplayer for Halo 2, still played by thousands. It may be difficult to remember in a post-Modern Warfare 2 world, where millions play online on their Xbox 360s and PS3s (and the occasional Wii), but console online multiplayer used to be a pipe dream at best - until the massive success of Halo 2 cemented it as the way of the future.
There's a really fascinating (if long) read awestruck by the E3 2003 demo [http://www.eurogamer.net/articles/better-than-halo-the-making-of-halo-2-article], the game's engineering lead Chris Butcher said that said demo was all "smoke and mirrors."
"The graphics engine that we showed at E3 2003, driving around the Earth city... That entire graphics engine had to be thrown away, because you could never ship a game on the Xbox with it," said Butcher. "Through putting ourselves through hell, we were able to do a five-minute demo of it, but after we came back from E3 we had to admit that this graphics engine was never going to work - it was never going to support the kind of environments that are really important for a Halo game. So we literally scrapped the entire graphics engine and started from scratch."
The level with the Flood in the quarantine was a mere 20% of a "gargantuan, sprawling level that was meticulously built and hand-constructed, but that could never, ever have shipped in any engine," said Butcher - and those sorts of cutbacks were endemic of a troubled, disorganized, chaotic development cycle in which entire features and levels had to be tossed out in order to desperately make the ship date.
In fact, the game that actually hit shelves was only half of what Bungie had dreamed up. The other half? Well, they took a bit more time on it with a much more organized approach this time around, and eventually released it as Halo 3. That's right - the annoying cliffhanger ending to Halo 2? It wasn't supposed to be like that, in Bungie's original plan.
If you have the time, the whole interview is a really interesting read - detailing the game's "brutal" crunch [http://www.eurogamer.net/articles/better-than-halo-the-making-of-halo-2-article], among others.
Honestly, it's a testament to Bungie's skill as a developer that Halo 2 turned out as good as it did, despite the many, many troubles during the game's development. Flawed, yes, but also good.
Permalink
oes this mean that Halo fans got ripped off by haveing two games, originally one
