Build engine
From Freepedia
Image:Rawmeat classic.png
The Build engine is a first-person shooter engine created by Ken Silverman for 3D Realms. Like Doom, the Build engine represents its world on a two-dimensional grid using closed 2D shapes called sectors, and simple flat objects called sprites. It is widely considered a 2.5D engine as the basic world geometry is two-dimensional with an added height component as each sector may have a different ceiling and floor height, and the ceiling and floor may be angled along one line of the sector. The engine renders these sectors from a perspective that initially appears three-dimensional. However the sizing for perspective only depends on the horizontal distance (most noticeable as the fact that wall verticies are always straight vertical lines onscreen). This can cause noticeable distortion when looking up and down and so most build games restrict this to a fairly limited range of angles.
Contents |
Sectors
The Build engine allowed for more complex and flexible worlds than Doom by virtue of its representation of the world information. Sectors could be manipulated in real-time; their shape, heights, and slope angles being completely variable, without requiring recalculation of rendering information.
Developers of games based on the engine used reserved sprites, often called sector effectors, that when given special tags (numbers with defined meanings), would allow the level designer to make a dynamic world that appeared to be 3D. Similar tag information could be given to the sector walls and floor area to give a sector special characteristics. For example, a particular sector effector may let a player fall through the floor if he walked over it and teleport him into another sector. In practice, this could be used to create the effect of falling down a hole to a bigger room or creating a body of water that could be jumped into to explore underwater. A sector could be given a tag that made it behave like a simple elevator or lift. Sectors could overlap one another provided they could not be seen at the same time (if two overlapping sectors were seen at the same time a corrupted display resulted). This allowed the designers to create, for instance, air ducts that appeared to extend across the top of another room (however doing so could be tricky due to the 2D viewpoint used for much of the editing process). More interestingly, this allowed the designer to create worlds that would be physically impossible (e.g. a door way of a small building could lead into a room that was larger than the building itself). While all these things made the game appear to be 3D, it wouldn't be until later first-person shooters, like Quake, that the engine actually stored the world geometry as proper 3D information.
Voxels
Later versions of Ken's Build engine allowed game selected art tiles to be replaced by 3D objects made of voxels. This feature appeared too late to be used in Duke Nukem 3D but was seen in several of the later Build engine games. For several years Ken has been working on a modern engine based entirely on voxels, known as Voxlap.
Build Engine Games
The Build engine was most famous for powering the classic 3D Realms FPS Duke Nukem 3D. But was used in numerous other games.
- Games that were built directly on Ken's code.
- Games whose code was based on duke3D
- Nam
- WW2GI
- The Redneck Rampage series.
- Details unknown
Room over room
Several build engine games used a trick involving rendering multiple times to draw two sectors joined floor to ceiling. The sectors could either be moved at map load time which made calculations during the game simpler or left where they were (building them over the top of each other wasn't really feasiable due to limitations of the editor). The two best known games to do this were Shadow Warrior (which moved the sectors at map load time) and Blood (which didn't). It is important to stress that this is not a feature of the Build engine but a trick discovered by game developers.
Source release and further developments
On the June 20, 2000 (according to his website) Ken released the Build engine source code.
The early days
A few total conversion teams for Build games decided to work from Ken's Build code directly and the Eduke project started moving towards using Ken's released Build code (though there was no publically released version until after the source release of Duke 3D). It was claimed at the time by many on the 3DR forums that it would be impossible to port build to a multitasking OS as it needed a large contiguous block of memory that wouldn't be availible in a multi tasking environment (the people who claimed this obviously didn't realise how virtual memory works). An enhanced version of the Build editor known as mapster was also developed.
The Icculus port
Ryan C. Gordon (Icculus) made the first port of the engine using SDL. The port was first to Linux, then to Cygwin and finally to a native Windows build using the Watcom C++ compiler, which was the compiler used for the original DOS build (Note: Build is plain C despite being compiled with Watcom C++). There was some talk of Matt Saettler using this to port Eduke to Windows but nothing came of this.
The jonof port
A second port was made to Windows and later Linux by Jonothen Fowler (jonof). Unlike the icculus port, this used DirectDraw rather than SDL on Windows and so was generally faster.
The Duke Nukem 3D source release
On the April 1, 2003 3D Realms released the source code to Duke 3D after years of saying it would never happen. Not long afterwards both Icculus and jonof had ports made. It was now possible to play Duke Nukem 3D well on the NT line of Windows (including Windows 2000/XP) and interest in the ports soared.
Polymost
Image:Rawmeat polymost.png After the Windows Build ports it was often claimed by long timers on the 3DR forums that it would not be possible to make build render to polygons. The particular issue that they picked on this time was how to turn the floors into a series of triangles with decent speed. Eventually Ken Silverman got sick of the claims that it was impossible and decided to do it himself based on the jonof port. Soon afterwards support for 3D models was added and eventually support for voxels was added too. The addition of polymost to the jonof port made it far more attractive than the ICCULUS based versions though netcode issues meant that ICCULUS based ports remained the norm for multiplayer until quite recently.
Other ports
Source for the last private beta of eduke 2.1 (which never made it to a release version) was released soon after the Duke Nukem 3D source. There was a port of this based on the ICCULUS code known as wineduke but those working on it became frustrated with bugs introduced by Matt Saettler as a result of inadeqate testing during the eduke 2.1 development process.
Source for eduke 2.0 was also released but this took a lot longer due to issues in making Matt Saettlers archived source for it compile. This was merged with the jonof port of Duke Nukem 3D and many features from 2.1 and various other eduke branches added by terminX to make eduke32 and wineduke has since died off leaving Eduke32 the only eduke port still in development.
Eduke contained the code from nam and ww2gi so theese could probablly be made to work with it without too much effort but thier do not seem to be any projects to do so currently. There has also been the Transfusion project which aimed to re-create Blood but as of 2005 this is far from complete.
Shadow Warrior source was released on April 1, 2005. And jonof released a port of it on April 2, 2005. However he admitted that he had access to the Shadow Warrior source about a week before its release.
External links
- Ken Silverman's Build Engine Page
- Icculus build engine page
- Jonathon Fowler's Build Engine Page
- JonoF's Duke Nukem 3D Port (JFDuke3D)
- Category at ODP
