Editing Tricks of the Game-Programming Gurus

From DoomWiki.org

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 72: Line 72:
 
Though Doom is prominently mentioned as a point of reference throughout the book, several key deficiencies exist in its content which place it well behind what was then the state of the art represented by Doom:
 
Though Doom is prominently mentioned as a point of reference throughout the book, several key deficiencies exist in its content which place it well behind what was then the state of the art represented by Doom:
 
* The book focuses exclusively on real mode 16-bit addressing with access to 640 KB of segmented RAM, whereas Doom ran in 32-bit {{wp|protected mode}} with linear access to 4 MB or more of memory.
 
* The book focuses exclusively on real mode 16-bit addressing with access to 640 KB of segmented RAM, whereas Doom ran in 32-bit {{wp|protected mode}} with linear access to 4 MB or more of memory.
* Approaches suggested for lighting and [[light diminishing]] suggest per-pixel calculation of color values instead of something similar to Doom's pre-computed [[COLORMAP]].
+
* Approaches suggested for lighting and light diminishing suggest per-pixel calculation of color values instead of something similar to Doom's pre-computed [[COLORMAP]].
 
* Hidden surface removal is limited to the {{wp|ray casting}} algorithm as used by ''Wolfenstein 3D''. [[Node|BSP trees]] are not suggested or detailed to any extent.
 
* Hidden surface removal is limited to the {{wp|ray casting}} algorithm as used by ''Wolfenstein 3D''. [[Node|BSP trees]] are not suggested or detailed to any extent.
 
* Only VGA graphics {{wp|Mode 13h}} is detailed. {{wp|VGA}} tweaking approaches similar to those expounded by [[Michael Abrash]] and used extensively by [[John Carmack]] are neglected. This precludes any discussion of hardware page flipping or scrolling. Deficiencies in the implementation due to this factor are only given the suggested solution of extensively rewriting the C code as assembly, whereas Doom itself used very little assembly language.
 
* Only VGA graphics {{wp|Mode 13h}} is detailed. {{wp|VGA}} tweaking approaches similar to those expounded by [[Michael Abrash]] and used extensively by [[John Carmack]] are neglected. This precludes any discussion of hardware page flipping or scrolling. Deficiencies in the implementation due to this factor are only given the suggested solution of extensively rewriting the C code as assembly, whereas Doom itself used very little assembly language.

All contributions to DoomWiki.org are considered to be released under the CC BY-SA 4.0 International (see Doom Wiki:Copyrights for details). By contributing, you agree to be bound by the Terms of Use.
Your changes will be visible immediately. Please enter a summary of your changes above.

Do not submit copyrighted images or text without permission! This includes text taken from in-game codices or logbooks, or from official instruction manuals, strategy guides, and other such books.

This project is not affiliated with id Software, Raven Software, ZeniMax Media, Bethesda SoftWorks, or any other commercial software developer or publisher. Use of trademarked logos and other protected intellectual property is solely for the purpose of analysis and critical commentary on the identified products and associated fan community activity, and does not imply any endorsement by any of these organizations or their employees, past or present.

Cancel | Editing help (opens in new window)