The Doom engine, also called id Tech 1,^[1] is the game engine that powers the id Software games Doom and Doom II. It is also used by HeXen, Heretic, Strife and HacX, and other games produced by licensees. It was created by John Carmack, with auxiliary functions written by Mike Abrash, John Romero, Dave Taylor and Paul Radek. Originally developed on NeXT computers, it was ported to DOS for Doom's initial release and was later ported to several game consoles and operating systems. A game engine is the core software component of a computer or video game or other interactive application with real-time graphics. ... id Software (IPA: officially, though originally ) is an American computer game developer based in Mesquite, Texas, a suburb of Dallas. ... “Computer and video games” redirects here. ... Doom (or DOOM)[1] is a 1993 computer game by id Software that is a landmark title in the first-person shooter genre. ... Doom II: Hell on Earth is a first-person shooter video game created by id Software. ... Hexen: Beyond Heretic (or Hexen) is a first-person shooter computer game developed by Raven Software, published by id Software, and distributed by GT Interactive beginning on March 16, 1996. ... Heretic is a fantasy first-person shooter computer game created by Raven Software, published by id Software, and distributed by GT Interactive in 1994. ... Strife, published in 1996, is a computer game developed by Rogue Entertainment and published by Velocity, based on the Doom engine from id Software. ... John D. Carmack II (born August 20, 1970) is a widely recognized figure in the video game industry. ... Michael Abrash, a veteran game programmer, wrote his first commercial game in 1982, Space Strike, for the IBM PC. Though Abrash has contributed immensely to the computer gaming industry, he is best known as one of the top optimization and assembly programmers. ... Alfonso John Romero (born October 28, 1967 in Colorado Springs, Colorado) is a well-known game designer, programmer, and developer in the video game industry. ... Dave D. Taylor Dave D. Taylor is a game programmer, perhaps best known as a former id Software employee and noted for his work promoting Linux gaming. ... For other meanings, see Next. ... In computer science, porting is the process of adapting software so that an executable program can be created for a computing environment that is different from the one for which it was originally designed (e. ... Instructions on how to use the directory command. ... The Nintendo GameCube is an example of a popular video game console. ... // An operating system (OS) is the software that manages the sharing of the resources of a computer. ...

The source code for the Linux version of Doom was released to the public in 1997 under a license that granted rights to non-commercial use, and was re-released under the GNU General Public License in 1999.^[2][3] The dozens of unofficial Doom source ports that have been created since then allow Doom to run on previously unsupported operating systems and sometimes radically expand the engine's functionality with new features. Source code (commonly just source or code) is any series of statements written in some human-readable computer programming language. ... This article is about operating systems that use the Linux kernel. ... The GNU logo The GNU General Public License (GNU GPL or simply GPL) is a widely-used free software license, originally written by Richard Stallman for the GNU project. ... A Doom source port is a source port of the Doom engine, the game engine used by the computer game Doom. ...

It is not a true "3D" engine, as it is not possible to look up and down properly, and two sectors cannot be placed above and under each other, but it is a fairly elegant system that allows pseudo-3D rendering. In its time, Doom was revolutionary in its ability to provide a fast texture-mapped environment that passed for 3D. Texture mapping is a method of adding realism to a computer-generated graphic. ...

Doom level structure

A simple setup demonstrating how Doom represents levels internally

Map view in editor

In-game view

Viewed from the top down, all Doom levels are actually two-dimensional, demonstrating one of the key limitations of the Doom engine: it is not possible to have "rooms above rooms". This limitation, however, has a silver lining: a "map mode" can be easily displayed, which represents the walls and the player's position, much like the first image to the right. File history Legend: (cur) = this is the current file, (del) = delete this old version, (rev) = revert to this old version. ... File history Legend: (cur) = this is the current file, (del) = delete this old version, (rev) = revert to this old version. ... File history Legend: (cur) = this is the current file, (del) = delete this old version, (rev) = revert to this old version. ... File history Legend: (cur) = this is the current file, (del) = delete this old version, (rev) = revert to this old version. ...

Basic objects

The base unit is the vertex, which represents a single 2D point. Vertices (or "vertexes" as they are referred to internally) are then joined to form lines, known as "linedefs". Each linedef can have either one or two sides, these are known as "sidedefs". Sidedefs are then grouped together to form polygons; these are called "sectors". Sectors represent particular areas of the level. In geometry, a vertex (plural vertices) is a special kind of point, usually a corner of a polygon, polyhedron, or higher dimensional polytope. ... “Line” redirects here. ... Look up polygon in Wiktionary, the free dictionary. ...

Sectors

Each sector contains a number of properties: a floor height, ceiling height, light level, a floor texture and a ceiling texture. To have a different light level in a particular area, for example, a new sector must be created for that area with a different light level. One-sided linedefs therefore represent solid "walls", while two-sided linedefs represent "bridge" lines between sectors. Spherical texture mapping Texture mapping is a method, pioneered by Edwin Catmull, of adding detail, surface texture, or colour to a computer-generated graphic or 3D model. ...

Sidedefs

Sidedefs are used to store wall textures; these are totally separate from the floor and ceiling textures. Each sidedef can have three textures; these are called the middle, upper and lower textures. In one-sided linedefs, only the "middle" texture is used for the texture on the wall. In two-sided linedefs, the situation is more complex. The lower and upper textures are used to fill the gaps where adjacent sectors have different floor and ceiling heights: lower textures are used for steps, for example. The sidedefs can have a middle texture as well, although most do not; this is used to make textures "hang" in mid air. For example, when a transparent bar texture is seen forming a cage, this is an example of a middle texture on a two-sided linedef.

Things

Finally, there is a list of objects in the level; objects are known as "things" in Doom. These are used to place players, monsters, powerups, etc. Each thing is given a 2D coordinate, as with the vertices. Things are then automatically placed on the floor or the ceiling depending on their type. Power Up, the Professional Organization of Women in Entertainment Reaching Up is an organization with the stated mission to promote the visibility and integration of gay women in entertainment, the arts, and all forms of media. Power Up provided funding and assistance to the 2003 short film . ... See Cartesian coordinate system or Coordinates (elementary mathematics) for a more elementary introduction to this topic. ...

This is only an overview of the basic structure of Doom levels; most of the data structures here carry extra properties, for example, texture offsets, and special properties for gameplay.

Binary space partitioning

Doom makes use of a system known as binary space partitioning (BSP). A tool is used to generate the BSP data for a level beforehand. Depending on the size of the level, this process can take quite some time. It is because of this that it is not possible to move the walls in Doom; while doors and lifts move up and down, none of them ever move sideways. Binary space partitioning (BSP) is a method for recursively subdividing a space into convex sets by hyperplanes. ...

The level is divided up into a binary tree: each location in the tree is a "node" which represents a particular area of the level (with the root node representing the entire level). At each branch of the tree there is a dividing line which divides the area of the node into two subnodes. At the same time, the dividing line divides linedefs into line segments called "segs". In computer science, a binary tree is a tree data structure in which each node has at most two children. ...

At the leaves of the tree are convex polygons, where it is not useful to divide the level up any further. These convex polygons are referred to as subsectors (or "SSECTORS"), and are bound to a particular sector. Each subsector has a list of segs associated with it. A convex pentagon In geometry, a convex polygon is a simple polygon whose interior is a convex set. ...

The BSP system is really a very clever way of sorting the subsectors into the right order for rendering. The algorithm is fairly simple:

1. Start at the root node.
2. Draw the child nodes of this node recursively. The child node closest to the camera is drawn first. This can be found from looking at which side of the node's dividing line the camera is on.
3. When a subsector is reached, draw it.

The process is done when the whole column of pixels is filled (i.e., there are no more gaps left). This ordering ensures that no time is wasted drawing objects that are not visible and as a result maps can become very large without any speed penalty.

Rendering

Drawing the walls

All walls in Doom are drawn vertically; it is because of this that it is not possible to properly look up and down. It is possible to perform a form of look up/down via "y-shearing", and many modern Doom source ports do this. Essentially this works by increasing the vertical resolution, and then providing a "window" on that space. By moving the window up and down, it is possible to give the illusion of looking up and down. However, this will distort the view the further up and down the player looks.

The Doom engine renders the walls as it traverses the BSP tree, drawing subsectors by order of distance from the camera so that the closest segs are drawn first. As the segs are drawn, they are stored in a linked list. This is used to clip other segs rendered later on, reducing overdraw. This is also used later to clip the edges of sprites.

Once the engine reaches a solid (1-sided) wall at a particular x ordinate, no more lines need to be drawn at that area. For clipping the engine stores a "map" of areas of the screen where solid walls have been reached. This allows far away parts of the level which are invisible to the player to be clipped completely.

The Doom graphic format stores the wall textures as sets of vertical columns; this is useful to the renderer, which essentially renders the walls by drawing lots of vertical columns of texture.

Floor and ceiling

The system for drawing floors and ceilings ("flats") is less elegant than that used for the walls. Flats are drawn with a flood fill-like algorithm. Because of this, it is sometimes possible if a bad BSP builder is used to get "holes" where the floor or ceiling bleeds down to the edges of the screen. This is also the reason that if the player travels outside of the level using the noclip cheat the floors and ceilings will appear to stretch out from the level over the empty space. Flood fill, also called seed fill, is a recursive algorithm that determines connected regions in a multi-dimensional array. ...

The floor and ceiling are drawn as "visplanes". These represent horizontal runs of texture, from a floor or ceiling at a particular height, light level and texture (if two adjacent sectors have the exact same floor, these can get merged into one visplane). Each x position in the visplane has a particular vertical line of texture which is to be drawn.

Because of this limit of drawing one vertical line at each x position, it is sometimes necessary to split visplanes into multiple visplanes. For example, consider viewing a floor with two concentric squares. The inner square will vertically divide the surrounding floor. In that horizontal range where the inner square is drawn, two visplanes are needed for the surrounding floor. Concentric objects share the same center, axis or origin with one inside the other. ...

This leads to one of Doom's classic limitations which frustrated many mappers for a long time. DOOM contained a static limit on the number of visplanes; if exceeded, it would crash back to DOS with the message, "No more visplanes!". The easiest way to invoke the visplane limit is a large checkerboard floor pattern; this creates a large number of visplanes.

As the segs are rendered, visplanes are also added, extending from the edges of the segs towards the vertical edges of the screen. These extend until they reach existing visplanes. Because of the way this works, the system is dependent on the fact that segs are rendered in order by the overall engine; it is necessary to draw close up visplanes first, so that they can "cut off" by the further away ones. If unstopped, the floor or ceiling will "bleed out" to the edges of the screen, as previously described. Eventually, the visplanes form a "map" of particular areas of the screen in which to draw particular textures.

While visplanes are constructed essentially from vertical "strips", the actual low level rendering is performed in the form of horizontal "spans" of texture. After all the visplanes have been constructed, they are converted into spans which are then rendered to the screen. This appears to be a tradeoff: it is easier to construct visplanes as vertical strips, but because of the nature of how the floor and ceiling textures appear it is easier to draw them as horizontal strips. Because of the nature of visplanes, the conversion is fairly trivial, however.

Things (sprites)

Each sector within the level has a linked list of things stored in that sector. As each sector is drawn the sprites are placed into a list of sprites to be drawn. If not within the field of view these are ignored. In computer graphics, a sprite (also known by other names; see Synonyms below) is a two-dimensional image or animation that is integrated into a larger scene. ...

The edges of sprites are clipped by checking the list of segs previously drawn. Sprites in Doom are stored in the same column based format as the walls are, which again is useful for the renderer. The same functions which are used to draw walls are used to draw sprites as well.

While subsectors are guaranteed to be in order, the sprites within them are not. Doom stores a list of sprites to be drawn ("vissprites") and sorts the list before rendering. Far away sprites are drawn before close ones. This causes some overdraw but usually this is negligible.

There is a final issue of middle textures on 2-sided lines, used in transparent bars for example. These are mixed in and drawn with the sprites at the end of the rendering process, rather than with the other walls.

See also

Free software Portal

• Doom 3 engine

Image File history File links Portal. ... The Doom 3 engine is a computer game engine developed by id Software and first used in the PC game Doom 3. ...

References

• BSP Frequently Asked Questions
• GL nodes specification
• Utilities to edit Doom and Doom2