Filed under: Gaming, Retail, Software, Developer, iPhone, App Store
Russell Clarke of Ideaworks Game Studio hosted a post-mortem report near the end of the first day of GDC 2010 about
Call of Duty: World at War Zombies for the iPhone. The game was one of the first big brand hits on the App Store -- it successfully brought a game mode from one of Activision's Call of Duty console games (originally developed by Treyarch) to Apple's handheld device. After a quick joke about how a "post-mortem" was an appropriate exercise for a game about zombies, Clarke got into the nuts and bolts of how Ideaworks went about adapting the game for the iPhone.
The most major feature of the game's development, he said, was the decision last year around this time to sit down and work on prototyping for about six weeks. Nowadays, there are a few successful first person shooters around the App Store, but last year, FPSes were still a new genre for the iPhone, so the team decided to really brainstorm how one would work on a touchscreen.
They started by looking at the original game developed by Activision and Treyarch. Zombies is a extra mode of Call of Duty: World at War that was developed as a "lunchtime project" -- a few developers threw it together on a whim, and enjoyed it so much that they released it as DLC, outside of the original game. So Ideaworks wanted to run with that vibe -- create a game that you could play on your lunch break, or squeeze into a few minutes. They did find that the App Store tended towards more casual and family games, but they didn't feel that the mature game could be successfully translated to a family-friendly format. Instead, they decided to stick with the blood and gore: "Activision," Clarke joked, "said we would have to learn to love our 17+ rating, and live with not releasing in every country in the world."
And they also wanted to create a game with "relaunchability," a term that a developer at Treyarch coined. "What keeps you relaunching the game," said Clarke, "is that, like most zombie games, you don't really win. You're just postponing your inevitable death." He also said that learning became a big function of the gameplay -- the game allows you to defend the same environment against zombies every time, so eventually you learn the best spots to make a stand, and so on.
Before development even started, they created a set of benchmarks in terms of performance and gameplay that they wanted to hit: Twenty zombies felt right for gameplay (you'd only be fighting 10 at any given time, but 10 more would be hanging around in the background), 20 FPS seemed like a good target for speed, 2000 triangles for graphics, and of course two thumbs ("the amount that most people have") for control.
The controls were probably the most interesting part of prototyping -- Clarke says his team really tried to brainstorm an interesting way to control an FPS on the iPhone. The problem, however, was that in an FPS game, you're doing three things (running, looking, and shooting), but you only have two thumbs to do them with. One prototype they created had you tilting the accelerometer around to move (while looking and shooting with two onscreen controls), but for some reason, that made everyone who tested it rather dizzy. In the end, they went with a compromise, including a few different choices: a dual stick standard, an aiming assist system, and even a mode that only slightly uses the accelerometer to look around.
Authenticity was another question -- obviously the iPhone doesn't have the processing power of the latest and greatest consoles, so Ideaworks had to work hard to walk the line between keeping the game running smoothly and keeping it detailed enough to compare to the bigger title. They did a lot of pruning on the original model work, turning geometry into straight textures, and cutting off 3D modeling that couldn't actually be seen by the player (the original team had even modeled tree roots underground, rendered on the Xbox 360 and Playstation 3, but never actually seen). They did things like not animating enemies when they weren't in the player's line of sight, and just using a sphere for the grenade hit model rather than actually modeling the shape, since it worked just as well. In the end, the iPhone had only about 1/7th of the geometry of the original game, but Ideaworks tried to make it at least look as similar as they could.
Multiplayer was a challenge, but fortunately, Activision had already created an online backend, so when Ideaworks hooked into that system, they were able to put together all of the multiplayer ideas they had (2-player, 4-player, and even a full online system) and then some (host migration was a project one of their engineers threw together in his spare time, and Bluetooth multiplayer was also added in on a whim).
Finally, Clarke shared a few lessons from the game's development. In terms of the controls, they learned that offering a choice to the player is sometimes the right move, and when there is a choice, you usually need to force it at some point (if you hide a different control scheme in the options, most players will never find it). Piracy was something else they learned -- while Clarke was hesitant to speak much about his opinions on piracy, he did say that it was
easier to pirate the game than anyone on his team believed, and that in the first days of the release, they saw a significant number of extra users playing than had actually bought the game.
Still, Clarke said that the game had done very well -- they've been high on the App Store's Top Paid list ever since release, and while he didn't mention sales for the main game, he said that the lite version has seen over three million downloads. Clarke's panel offered up an interesting look behind one of the App Store's big name hits.
TUAWGDC 2010: Call of Duty: World at War Zombies postmortem originally appeared on The Unofficial Apple Weblog (TUAW) on Wed, 10 Mar 2010 17:00:00 EST. Please see our terms for use of feeds.
Read |
Permalink |
Email this |
Comments
iPhone -
AppStore -
Activision -
Call-of-Duty-World-at-War -
Apple
Read the rest of the story from source
Think we'd all be better off if HTML5 could somehow instantly replace Flash overnight? Not necessarily, according to a set of comparisons from Jan Ozer of the Streaming Learning Center website, which found that while HTML5 did come out ahead in many respects, it wasn't exactly a clear winner. The tests weren't completely scientific, but they did find that HTML5 clearly performed better than Flash 10 or 10.1 in Safari on a Mac, although the differences were less clear cut in Google Chrome or Firefox. On the other hand, Flash more than held its own on Windows, and Flash Player 10.1 was actually 58% more efficient than HTML5 in Google Chrome on the Windows system tested. As you may have deduced, one of the big factors accounting for that discrepancy is that Flash is able to take advantage of GPU hardware acceleration in Windows, while Adobe is effectively cut out of the loop on Mac -- something it has complained about quite publicly. According to Ozer, the differences between HTML5 and Flash playback on a Mac could be virtually eliminated if Flash could make use of GPU acceleration. Hit up the link below for all the numbers.
ReadWriteWeb | 
Streaming Learning Center | Email this | Comments
Recently I've been preparing to move home and finally did last weekend. Naturally I had to pack up all my musical gear, equipment and of course, my Mac. In the week leading up to the move, I've had my iPhone and nothing else. With no creative outlet and the pressure of looming project deadlines, I found myself scouting the app store for a fix to help me start fleshing out a few creative ideas. 
Flourish is something a bit more immersive. While having a steeper learning curve, there's loads more to explore here. The user interface is really fresh and unique (especially for the iPhone), and presents a creative challenge in focusing your composition whilst giving you the space to try different approaches to what you are creating. 
Unit testing refers to a software validation methodology that allows programmers to test individual program units for correctness. It's been an ongoing question in the iPhone developer community as to whether the iPhone's view controller class is testable or not.
Recent Comments