August 27, 2004. Originally at Bungie.net.
Bungie Weekly Update, August 27th 2004
Although there's more than a month of actual mind crushing work left, this week is a real milestone in my mind, and so we bring you a special, extended update, because Halo 2's campaign mode is not only playable, it's fun. Actually, fun is the wrong word – since some of the levels left me sweating, awed and terrified by turns. Caveat: As well as an employee, I'm still part fanboy, so read this with that in mind.
BUS STOP
I've been getting up very early, coming in and playing the latest test build. It's always full of surprises. One bizarre way to tell how advanced it is is to look at the buses. They started as large oblong crates, completely flat but with the candy-cane default texture that's used for unfinished objects. One morning I loaded it up and the candy cane texture was gone. Replaced with a sort of vaguely instructional "Large Dias" emblazoned across it. A few weeks later, it kinda looked like a crate with wheels. Then, a passable bus. This morning, it wheels, glass, and does something very cool if you lob enough grenades at it. It's a bus. Keanu Reeves would drive it. But like, you can't really drive it. Before you ask.
Surrounding the bus, which I admit is kind of a boring thing to watch over a period of months, is some dramatically detailed city environment and architecture. You've already got some idea of what the landscape of Earth City looks like, thanks to the year and a half old E3 demo, but there are varied elements to the city environment, and there are plenty of graphical and environmental surprises in store for you. You'd be surprised what a difference a few power cables make.
BUILD QUALITY
The system kind of works like this: We have a general resource at Bungie where the latest builds of the game are located. One is recommended as stable by the test department, while others may have been built to test or debug a specific problem. The testers get the stable build and rampage through it, looking for any problems, "bugging" them (that is, saving their exact position in the game, noting what the problem was, and entering it into a database.) and then play on, looking for problems.
Parsons has asked Brian and me to get stuck into that process as well. He thinks I'm basically stupid though, so while Brian has been asked to look for "clipping errors, instance geometry problems and physics anomalies," Parsons told me to "watch out for colors that aren't pretty," or "scary things that make you want to go wee."
Speaking of Brian, he's getting married today. So congrats to Brian from everyone on the team, except the hardcore dudes who're all like, "Dude, you're gonna be so whipped man," and "this is the end of the party, brah!"
Harold the test manager, who's as evil as Carrot Top's Y-Fronts , explained that he's basically been staying until 3am and then arriving again about four hours later. He's opening and closing bugs at a ferocious rate. One horrible thing he did this week to the test team was open 478 bugs at once, using an automated process. That far outstripped the entire output of the rest of the test team. You could hear the wailing and gnashing of teeth. Still, they were minor fixes. Hundreds more will be opened and fixed between now and the game's ship.