Duke Nukem 3D Code Review

alancronin writes "Similar to Fabien Sanglard's previous code reviews of other games such as the Quake and Doom line of games comes a review of the code base of Duke Nukem 3D (split out over 4 pages). This will be a very good read for anyone interested in understanding the mechanics of a highly addictive game or anyone that wants to learn more about game design."

Comments

duke nuken

[Anonymous Coward]

duke nuken

Re:duke nuken

[Sockatume]

"I'm here to use my bubble-gun and kick some asps. And I'm all out of bubbles."

Re:duke nuken

[isorox]

Duke 3D was waaay more sophisticated than Wolfenstein. While it did employ similar dated rendering techniques and the need for sprites, it did offer full range of motion along all three dimensions, actual floors and ceilings, interactive environments, the ability to look around using a mouse, and the ability to have passages that could overlap one another. Doom couldn't even do that.

The Quakes were technologically superior, by far. Three dimensional rendering in the truest sense, greater lighting effects, antialiasing (I think that came about with Quake 2, but correct me if I'm wrong). Network play out the wazoo. Even the audio capabilities were incredible. (I used to love putting different CD's in the drive to change up the soundtrack. Megadeth's "Rust in Peace" goes very well with Quake.)

But despite all that, I always had more fun with Duke 3D than I did with Quake. It just had a more colorful personality and it had more creative levels. Quake was always so... brown and gray.

The amount of weekends I spent with a friend, 2 computers, and a null modem cable, so much fun. We even built a map of our school with build. And we showed it off during open evenings. Probably get arrested nowadays.

Laser trip mines.Oh yes.

Duke Nuken

[digitalmonkey2k1]

Cone get sone!

Re:Nuken... Really?

[Hatta]

For shane.

Re:Fuck, it's a 5 word title

[stepdown]

Don't be so hard on tinothy, he got 60% of the words right!

Re:Fuck, it's a 5 word title

[damn_registrars]

Find a job more suited to your lack of ability already (though I admit it's going to be hard to find a job that requires less).

Timothy has been with slashdot for so long that he is no longer qualified to do anything else.

Re:Duke Nukem Forever

[Anonymous Coward]

When it's done!

Sequel

[Nick]

When I first created my account on /. I remember getting excited about the sequel that was going to be released soon.

Re:Yeah

[telchine]

Piece of cake!

That's a lie!

Re:Oh, you're going to get an F on that one for su

[MrSteveSD]

At my old job I was once writing a while loop and decided to use "i" as the name of a counter variable I was incrementing. After a while I noticed that I had not declared the i and was perplexed as to why there was no compile error. Then to my horror I discovered that someone was using a global variable named "i".

Re:Oh, you're going to get an F on that one for su

[Namarrgon]

Had a similar problem; couldn't figure out why I kept getting surprising compiler errors in some of my perfectly legal loops. Even more surprisingly, I got similar errors in some basic expressions, despite identical expressions using different variables compiling just fine.

Surprise was no longer adequate, and I had to resort to astonishment when I found a colleague had #defined the letter "r" to a constant.