Wolfenstein3DforiOS源码发布_C_Objective-C_下载.zip

iPhone development*

By John Carmack, Technical Director, Id Software

I had been frustrated for over a year with the fact that we didn't have any iPhone development projects

going internally at Id. I love my iPhone, and I think the App Store is an extremely important model for

the software business. Unfortunately, things have conspired against us being out early on the platform.

Robert Duffy and I spent a week early on starting to bring up the Orcs & Elves DS codebase on the

iPhone, which would have been a nice project for a launch title, but it wasn't going to be a slam dunk.

The iPhone graphics hardware is a more capable superset of the DS hardware (the driver overhead is far,

far worse, though), but the codebase was fairly DS specific, with lots of Nintendo API calls all over the

project for conventional Java and BREW mobile phones, and Anna didn't want to slip a scheduled

milestone on the established, successful development directions there for a speculative iPhone project.

After thinking about the platform's capabilities a bit more, I had a plan for an aggressive, iPhone specific

project that we actually started putting some internal resources on, but the programmer tasked with it

didn't work out and was let go. In an odd coincidence, an outside development team came to us with a

proposal for a similar project on the Wii, and we decided to have them work on the iPhone project with

us instead. We should be announcing this project soon, and it is cool. It is also late, but that's software

development...

Late last year, the mobile team had finished up all the planned versions of Wolfenstein RPG, but EA had

suggested that in addition to the hundreds of customized versions they normally produce for all the

the level for a view that would confirm my suspicion, and when I found a clear enough view of some

angled geometry I saw the tell-tale mid-polygon affine swim in the texture as I rotated. They were using

the software rasterizer on the iPhone. I patted myself on the back a bit for the fact that the

combination of my updated mobile renderer, the intelligent level design / restricted movement, and the

hi-res artwork made the software renderer almost visually indistinguishable from a hardware renderer,

but I was very unhappy about the implementation.

I told EA that we were NOT going to ship that as the first Id Software product on the iPhone. Using the

iPhone's hardware 3D acceleration was a requirement, and it should be easy -- when I did the second

generation mobile renderer (written originally in java) it was layered on top of a class I named TinyGL

that did the transform / clip / rasterize operations fairly close to OpenGL semantics, but in fixed point

Rather than having a big confrontation over the issue, I told them to just send the project to me and I

And I had fun doing it.

Since we now were doing something resembling "real work" on the iPhone at the office, we kept it going

at a low priority. One of the projects Cass was tinkering around with at home was a port of Quake 3,

and we talked about different interface strategies every now and then.

Unfortunately, when we sat down to try a few things out, we found that

Q3 wasn't really running fast enough to make good judgments on iPhone control systems. The

I was just starting to set up a framework to significantly revise Q3 when I considered the possibility of

just going to an earlier codebase to experiment with initially. If we wanted to factor performance out of

the equation, we could go all the way back to Wolfenstein 3D, the grandfather of FPS games. It had the

basic run and gun play that has been built on for fifteen years, but it originally ran on 286 computers, so

it should be pretty trivial to hold a good framerate on the iPhone.

playing on a PC at high resolution. Things weren't as smooth as they should be at first, but two little

changes made a huge difference -- going at VBL synced update rates with one tic per cycle instead of

counting milliseconds to match 70 hz game tics, and fixing a bug with premature integralization in the

angle update code that caused mouse movement to be notchier than it should be. The game was still

fun to play after all these years, and I began to think that it might be worthwhile to actually make a

product out of Wolfenstein on the iPhone, rather than just using it as a testbed, assuming the controls

worked out as fun to play. The simple episodic nature of the game would make it easy to split up into a

$0.99 version with just the first episode, a more expensive version with all sixty levels, and we could

release Spear of Destiny if there was additional demand. I was getting a little ahead of myself without a

fun-to-play demonstration of feasibility on the iPhone, but the idea of moving the entire line of classic Id

titles over -- Wolf, Doom, Quake, Quake 2, and Quake Arena, was starting to sound like a real good idea.

away from Rage to work on the iPhone exclusively. Cass continued to help with iPhone system issues, I

drafted Eric Will to create the few new art assets, and Christian Antkow did the audio work, but this was

the first time I had taken full responsibility for an entire product in a very long time.

*Design notes*

The big question was how "classic" should we leave the game? I have bought various incarnations of

Super Mario Bros on at least four Nintendo platforms, so I think there is something to be said for the

classics, but there were so many options for improvement. The walls and sprites in the game were

originally all 64 x 64 x 8 bit color, and the sound effects were either 8khz / 8 bit mono or (sometimes

truly awful) FM synth sounds. Changing these would be trivial from a coding standpoint. In the end, I

decided to leave the game media pretty much unchanged, but tweak the game play a little bit, and build

a new user framework around the core play experience. This decision was made a lot easier by the fact

The original in-game status bar display had to go, because the user's thumbs were expected to cover

much of that area. We could have gone with just floating stats, but I thought that BJ's face added a lot

of personality to the game, so I wanted to leave that in the middle of the screen. Unfortunately, the

way the weapon graphics were drawn, especially the knife, caused issues if they were just drawn above

the existing face graphics. I had a wider background created for the face, and used the extra space for

directional damage indicators, which was a nice improvement in the gameplay. It was a tough decision

to stop there on damage feedback, because a lot of little things with view roll kicks, shaped screen

blends, and even double vision or blurring effects, are all pretty easy to add and quite effective, but

with automatic-use, and some secret push walls are trivially found when you pick up an item in front of

them now, but this was definitely the right decision.

You could switch weapons in Wolf, but almost nobody actually did, except for occasionally conserving

ammo with the chain gun, or challenges like "beat the game with only the knife". That functionality

didn't justify the interface clutter.

The concept of "lives" was still in wolf, with 1-ups and extras at certain scores. We ditched that in

Doom, which was actually sort of innovative at the time, since action games on computers and consoles

were still very much take-the-quarter arcade oriented. I miss the concept of "score" in a lot of games

today, but I think the finite and granular nature of the enemies, tasks, and items in Wolf is better suited

to end-of-level stats, so I removed both lives and score, but added persistent awards for par time, 100%

kills, 100% secrets, and 100% treasures. The award alone wasn't enough incentive to make treasures

relevant, so I turned them into uncapped +1 health crumbs, which makes you always happy to find