7 ms·
Game Engine Black Book: Doom [pdf]
- pestaa 4y ago77 cents profit per copy sold? Is this normal for authors? I understand this book has high production costs, but that doesn't mean the author shouldn't get paid...
- foota 4y agoGiven they released it for free too, maybe the author wanted to make it readily available so they reduced their fee?
- pjmlp 4y agoIt is a sad well know fact that one cannot live alone from selling books, in technical domains they mostly serve as means to sell one's credentials in a specific domain, for conferences, freelancing, ....
- bombcar 4y agoThe author stated somewhere he wasn’t out to make money on the books on Amazon or such, and if you sell via print on demand with Amazon it is really hard to get a price that works worldwide and doesn’t give you at least “some” profit somewhere.
- pluijzer 4y agoI love these kinds of historical deep dives. Specifically related to graphics or games. Thank you for sharing.
- kevinh 4y agoNote that this particular PDF is PWYW, so keep that in mind if you enjoyed it: https://fabiensanglard.net/gebbdoom/ https://fabiensanglard.net/gebbdoom/ There's also a book for Wolf3D: https://fabiensanglard.net/gebb/ https://fabiensanglard.net/gebb/ and the CP-System: https://fabiensanglard.net/cpsb/ https://fabiensanglard.net/cpsb/
- prvc 4y agoPerhaps the submission URL can be changed to the first link above?
- ant6n 4y agoA good addition with more story and less technicals is the book „masters of doom“
- djmips 4y ago$20 sent thanks. Yes I imagine he will appreciate not direct linking the PDF. Too late maybe.
- fabiensanglard 4y agoIt helps to share my passion with more people which was the #1 goal of this project. Besides, the PDF is now optimized and weights only 15miB instead of the 300 original MiB. So it does not kill my bandwidth budget :)! I don't mind.
- 0cf8612b2e1e 4y agoWell that’s a nifty update. I just checked the copy I purchased and it weighs in at 174 mbs.
- metiscus 4y agoYou are a good human. Thank you for this wonderful resource!
- dtien 4y agoThank you for posting this, sent $$ and a thank you! Love finding stuff like this.
- 5- 4y agosee also a tutorial on writing a doom-compatible engine from scratch: https://github.com/amroibrahim/DIYDoom https://github.com/amroibrahim/DIYDoom they also have a community forum, diyidtech, at https://discord.gg/a8n4Y2z https://discord.gg/a8n4Y2z
- smcl 4y agoThanks, added to my long list of "TODO projects"
- jbverschoor 4y agoI can recommend the black art of 3d game programming, don’t remember by who, it’s this muscle guy :) and the series called “code on the cob”, by Chris Hargrove, while he was working at 3d realms
- djmips 4y agoAndré LaMothe?
- jbverschoor 4y agoYes :)
- pizza234 4y agoIt's by Andre LaMothe. He has written several popular books in the 90s. His first (major, I believe) book was "Tricks of the Game-Programming Gurus", which revolved around Wolfenstein 3D (ray casting). In reality, it was an overrated and ultimately terrible book (amonth the other things, the book project was not an actual game, and his approach to optimization was to use assembly instead of better algorithms). "Black Art of 3D game programming" is a good book instead, and also relatively relevant today, for those who want to understand the basics of 3d. It also goes in detail in explaining BSP trees, whose implementation is considerably more complex than one would imagine by reading "Game Engine Black Book - Doom" (nothing wrong with that, it's just a matter of page budget).
- nomilk 4y agoA few years ago I wrote to the author to express gratitude for them writing this book (I also purchased a hard copy to express an additional $0.77 worth of gratitude). One thing I notice hasn't been mentioned yet which is cool is that the entire source code for the book is on GitHub: https://github.com/fabiensanglard/gebbdoom https://github.com/fabiensanglard/gebbdoom
- djmips 4y agoNice. The title should have a (2017)?
- boppo1 4y agofrom reading the first couple chapters, it looks like it was completed last month. The age of the github might be from when he started.
- fabiensanglard 4y agoThis is revision 1.2 which was completed last month. The original version (1.0) was released in 2018.
- kqr 4y agoI sometimes play Doom when I have five minutes to kill to the next (remote) meeting. I'm still incredibly impressed by what these people accomplished. It was pretty much the first fast-paced, full 3D world you could immerse yourself in. Sometimes I feel like it's a shame they wasted the potential on a monster shooter, when they could have made an open world adventure (with monster shooter elements) or something seriously ambitious. But then again, I guess that became the ambition but it turned out to be too ambitious, so they probably hit the sweetspot with semi-open level design and smashing gameplay instead of slow story.
- bombcar 4y agoThe timeline for Doom was insane - and other companies came afterwards and used the engine to make more story-based games.
- delta_p_delta_x 4y agoI've always said: in terms of software complexity, video games are second only to OSs. This book describes Doom (1993), and already goes from low-level hardware descriptions (caching, pipelining) to describing 2D and 3D computer graphics (even including a discussion on perspective-correct texture mapping), collision detection, audio and I/O architecture, to the enemy AI. Little wonder that people like John Carmack and Chris Sawyer are absolute legends. Modern video games ramp this complexity up to a wholly new level: at 144 Hz, games have to accurately output frames in 7 milliseconds or less; a single stutter to 30+ ms is noticeable. Add in the complexity of managing CPU-GPU data transfers, audio and networking, and now hardware ray-tracing. Open-world games have to seamlessly stream data to keep the illusion going (Skyrim is already considered antiquated because of loading screens between even outdoors areas—famously, the gate to Whiterun—not to mention loading screens between indoors and outdoors). They also manage gigantic state machines of NPCs movements and reactions, enemy actions, player data and quest progression, and other miscellanea like day/night time cycles. Players also now expect non-linear, branching storylines, and straightforward moddability. Multiplayer games have to seamlessly send and synchronise user input and responses between dozens of players networked across the world, within tens to hundreds of milliseconds—a 100 ms ping is unacceptable in competitive CS:GO. A website is allowed to take several seconds to load, but that I fired a headshot at that other player's character and that it registered on that player's computer within a hundred milliseconds is stupefying. In graphics we now have ML-based upscaling techniques like DLSS and FSR that are barely distinguishable from full-resolution rendering. Just 5 years ago we had to make do with painfully intensive Sinc/Lanczos algorithms, or blurry bi/trilerp. We have temporal anti-aliasing techniques, and rasterisation hacks that are so impressive that they look photorealistic (see Red Dead Redemption 2. Find a bright light source at night when it's raining, and look at the droplets: they refract the light from the light). I've already mentioned hardware ray-tracing that now allows real-time effects we could only have dreamed of just half a decade ago. I would unabashedly say video games are the zenith of what modern computers and modern software development are capable of. Given this, it is a travesty that game developers are frequently the lowest-paid programmers.
- djmips 4y agoI think you are mostly correct but there are other fields that would give video games a run for their money in being the zenith. I'm thinking fast trading, machine learning for example. But thanks for the shout out!
- nicoboo 4y agoFabien's articles are always really detailed and interesting. Truly appreciated. 'Continue comme ça Fabien'!
- fabiensanglard 4y agoMerci :) ! Joyeuse fin d'annee a tout le monde.