Build (Game Engine)

Build Engine

Screenshot showing Build in 2D mode
Developer(s)	Ken Silverman
Initial release	September 30, 1995; 28 years ago (1995-09-30)
Repository	advsys.net/ken/buildsrc/
Successor	Build 2
License	Source-available[1]
Website	advsys.net/ken/build.htm

The Build Engine is a first-person shooter engine created by Ken Silverman, author of Ken's Labyrinth, for 3D Realms. Like the Doom engine, the Build Engine represents its world on a two-dimensional grid using closed 2D shapes called sectors, and uses simple flat objects called sprites to populate the world geometry with objects.

The Build Engine is generally considered to be a 2.5D engine, as the basic world geometry is two-dimensional with an added height component, allowing each sector to have a different ceiling height and floor height. Some floors can be lower and some can be higher; the same is true with ceilings (in relation to each other). Floors and ceilings can hinge along one of the sector's walls, resulting in a slope. With this information, the Build Engine renders the world in a way that looks three-dimensional, unlike modern game engines that create actual 3D environments.

Though the Build Engine achieved most of its fame from powering the 1996 first-person shooter Duke Nukem 3D, it was also used for many other games.

Technical features

Sectors

Sectors are the building blocks of a level's layout, consisting of a two-dimensional polygonal outline when viewed from above, with the top and bottom faces of the sector given separate altitudes to create a three-dimensional space.^[2] Hence, all walls are perfectly vertical—anything appearing otherwise is technically a sloped floor or ceiling. The word room can be used as a loose substitute to aid understanding, though one room in the game world can consist of many sectors, and parallaxed skies can give the illusion of being outdoors. Sectors can be manipulated in real-time; all of their attributes such as shape, height, and slope could be modified "on-the-fly" by games, unlike the earlier Doom engine. This allowed games to have destructible environments, such as those seen in Blood.^[2] This technique is similar to the use of push walls in the earlier Apogee Software title Rise of the Triad which featured similar dynamic environments.

Developers of games based on the engine used special reserved "sprites" (game objects), often called "sector effectors [sic]", that, when given special tags (numbers with defined meanings), would allow the level designer to construct a dynamic world; 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 players fall through the floor if they walk over it and teleport them to 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 an 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 hall of mirrors effect resulted).^[3] 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 for designers due to the 2D viewpoint used for much of the editing process). This allowed the designers to create worlds that would be physically impossible (e.g. a doorway of a small building could lead into a network of rooms larger than the building itself). While all these made the games using the engine appear to be 3D, it wouldn't be until later first-person shooters, such as Quake, which used the Quake engine, that the engine actually stored the world geometry as true 3D information, making the creation of one area stacked atop another area in a single map very feasible.

Voxels

Later versions of Ken Silverman'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 some of the later Build Engine games. Blood uses voxels for weapon and ammo pickups, power-ups, and eye-candy (such as the tombstones in the "Cradle to Grave" level, some chairs, and a crystal ball in "Dark Carnival"). Shadow Warrior makes even more advanced use of the technology, with voxels that can be placed on walls (all of the game's switches and buttons are voxels).

For several years, Ken worked on a modern engine based entirely on voxels, known as Voxlap.

Room over room

One limitation of the Build Engine is that its level geometry is only capable of representing one connection between sectors for any given wall. Due to this, a structure as simple as a shelf with space both above and below it is impossible, though sometimes sprites or voxels can be substituted. Buildings with several floors are technically possible, but it is not possible for such a building to contain an external window directly above or below another window. In addition, some liberties will need to be taken with the staircases, elevators, and other methods of access for each floor.

Several Build Engine games (namely Shadow Warrior, Blood, and Redneck Rampage) worked around this by displaying a "viewport" to another sector through an additional rendering pass. This technique, called room-over-room (ROR), appears seamless to the player. In addition to an expanded range of vertical construction, ROR was often used to give bodies of water translucent surfaces. ROR was never a feature of the Build Engine itself, but rather a "trick" that was created by game developers. A trick used in Duke Nukem 3D to get around this, as in the case of its opaque underwater sections, was to simply transport the player quickly to another region of the map made to mimic it, similar to the elevators from Rise of the Triad.

In 2011, a feature was added to EDuke32 called true room over room (TROR), which allows multiple sectors to be stacked vertically so that each sector's wall has its own connection, enabling vertically-unrestricted structures. The difference between ROR and TROR is that TROR sectors physically overlap in the map data and editor (allowing for easy creation and visualization), rather than being drawn from separate locations using view portals, hence true room over room. TROR is a feature of the EDuke32 source port, not a game feature or trick.

List of Build Engine games

Games that are built directly on the Build Engine

Year	Title	Developer	Notes
1994	Rock'n Shaolin: Legend of Seven Paladins 3D	Accend Inc.	Illegally used an earlier version of the engine, only released in Taiwan and South Korea.[4][5]
1995	Witchaven[2]	Capstone Software
	William Shatner's TekWar[2]
1996	Duke Nukem 3D[6]	3D Realms	Also Plutonium PAK, Atomic Edition, Duke!ZONE II, Xtreme, Duke it Out in D.C., Life's a Beach and Nuclear Winter expansions.
	PowerSlave	Lobotomy Software
	Witchaven II	Capstone Software
1997	Blood[6]	Monolith Productions	Also Plasma Pak and Cryptic Passage expansions.
	Shadow Warrior[6]	3D Realms	Also Twin Dragon and Wanton Destruction expansions.

Games that are based on the Duke Nukem 3D code

Year	Title	Developer	Notes
1997	Redneck Rampage	Xatrix Entertainment	Also Suckin' Grits on Route 66 expansion.
1998	Redneck Rampage Rides Again
	Redneck Deer Huntin'
	Extreme PaintBrawl	Creative Carnage
	NAM	TNT Team
	Liquidator[7]	Akella	Illegally used the engine, only released in Russia.
1999	WWII GI	TNT Team	Also WWII GI: Platoon Leader expansion.
2019	Ion Fury	Voidpoint	via EDuke32.
2022	A.W.O.L.[8]	Shotspark Studios

Unreleased Build Engine games

• Fate (unfinished, only a demo exists)
• Corridor 8: Galactic Wars (unfinished, source code is available)
• Shadow Warrior: Deadly Kiss (unreleased, screenshots were released in January 1998)

Development

The Build Engine was essentially a one-man project for Ken Silverman, though he consulted John Carmack for guidance early in the project.^[3] Silverman was hired by 3D Realms on the basis of his demo for Build. Though he continued to refine the engine after becoming employed at 3D Realms, according to Silverman he never teamed with any other 3D Realms employees on the project and was never directed to tailor the engine towards any particular game.^[2]

Source release and further developments

On June 20, 2000 (according to his website) Ken Silverman released the Build Engine source code under a proprietary non-commercial license.^[9][1] Silverman explained that after id Software set a precedent by releasing the source code for the Doom engine, fans had been pressuring him to release the source code for the Build Engine.^[2]

Early days

Version 2.0 of Matt Saettler's EDuke, a project to improve Duke Nukem 3D for modders, was sent to 3D Realms for packaging shortly after the release of the Build source, leaving Duke Nukem 3D the pre-built libraries that 3D Realms had used with the original Duke. (Both Duke Nukem 3D and EDuke were still closed-source at this point.)

With the 2.1 private betas, Saettler worked towards integrating Silverman's build source into the Duke source code, but the project fizzled out before producing anything more than some very buggy private betas. A few total conversion teams for Build games decided to work from Silverman's Build code directly, and an enhanced version of the Build editor known as Mapster was also developed.

It was claimed at the time by many on the 3D Realms 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 available in a multitasking environment. This statement did not hold up to scrutiny, as all modern operating systems use virtual memory which allows apps to get contiguous logical memory without using contiguous physical memory, but conventional wisdom of the time was that porting Build to such an OS was unfeasible.

Duke Nukem 3D source release

On April 1, 2003, after several years of claims to the contrary, 3D Realms released the source code to Duke Nukem 3D under the GPL-2.0-or-later license. Not long afterwards, both Ryan C. Gordon and Jonathon Fowler created and released source ports of the game, including the Build Engine. It was possible to play Duke Nukem 3D well on the NT line of Windows (including Windows 2000/XP) and on Linux and other Unix operating systems, and interest in the source ports soared.

icculus.org port

Ryan C. Gordon (icculus), with the help of others, 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 (despite being compiled with Watcom C++, Build is plain C.) There was some talk of Matt Saettler using this to port EDuke to Windows, but nothing came of it.

JonoF port

A second source port was made to Windows, and later to Linux and Mac OS X, by Jonathon Fowler (JonoF). This port, JFDuke3D, initially did not have network game support, though this was added later in development.

Polymost

The task of updating the Build Engine to a true 3D renderer was taken on by Silverman himself. In the release notes for Polymost, he wrote: "When 3D Realms released the Duke Nukem 3D source code, I thought somebody would do a OpenGL or Direct3D port. Well, after a few months passed, I saw no sign of somebody working on a true hardware-accelerated port of Build, just people saying it wasn't possible. Eventually, I realized the only way this was going to happen was for me to do it myself."^[10]

The Polymost renderer allowed for 3D hardware-accelerated graphics using OpenGL. It also introduced "hightile", a feature that made it possible to replace the game's original textures with high-resolution replacements in a variety of formats. Polymost has been utilized in Jonathon Fowler's JFBuild, JFDuke3D, JFShadowWarrior, and source ports derived from their code bases.

EDuke32

The source for EDuke 2.0 was later^[when?] released, followed by the source for the last private beta of EDuke 2.1 (which never made it to a release version). Richard Gobeille (TerminX) merged the EDuke 2.0 source with JFDuke3D to make EDuke32. Another port, Wineduke, based on the icculus code, has since died off, leaving EDuke32 the only EDuke port still in development.

EDuke32 also supports the games NAM and WWII GI, as EDuke was based on the code to those games.

Polymer

On April 1, 2009, an OpenGL shader model 3.0 renderer was revealed to have been developed for EDuke32, named Polymer to distinguish from Ken Silverman's Polymost. At first it was thought to be an April Fools' joke, but the renderer was later made public. It allows for more modern effects such as real-time dynamic colored lighting and shadow mapping, specular and normal mapping, and other shader-based features in addition to most of the features added to Polymost over the years. Although Polymer is completely usable, it is technically incomplete and unoptimised, and is still in development. The developers of EDuke32 have stated that once Polymer has been rewritten for speed, it will supplant Polymost completely, as it is a superior renderer, and can be made to look identical to Polymost.

Other game ports

BuildGDX

Developer(s)	Alexander "[M210]" Makarov
Initial release	January 12, 2018; 6 years ago (2018-01-12)
Stable release	1.04 / September 13, 2019; 4 years ago (2019-09-13)
Repository	gitlab.com/m210/BuildEngine
Platform	Java
Type	Game engine
License	Source-available
Website	m210.duke4.net

The Shadow Warrior source code was released on April 1, 2005 under the GPL-2.0-or-later license, and JonoF released a source port of it, JFShadowWarrior, on April 2, 2005.^[11] However, he admitted that he had access to the Shadow Warrior source code about a week before its release.^[12] This port was later forked by ProASM for the SWP port.^[13] A VoidSW port by the Ion Fury and EDuke32 developers entered public beta on May 21, 2020.^[14]

The Transfusion project aimed to re-create Blood in the DarkPlaces engine,^[15] but as of 2007, this project was far from complete, though it has playable deathmatch multiplayer; a similar project is BloodCM which recreates all of the Monolith made single player levels for Blood on top of EDuke32,^[16] as well as ZBlood which ports some Blood assets and levels onto ZDoom.^[17] The eRampage project attempted to create a total conversion of Redneck Rampage for EDuke32.^[18]

The source code of Witchaven, Witchaven II, William Shatner's TekWar, and Corridor 8: Galactic Wars have also surfaced. The legal status of these, however, is unclear. The full source code for alpha versions of Blood have also leaked,^[19] and was used as a reference for an otherwise reverse engineered port to Java using LibGDX called BloodGDX in May 2017 by the previous author of BloodCM.^[20]

This followed from the author's previous port of TekWar released in January 2016,^[21] and has been followed up by ports for Witchaven,^[22] Redneck Rampage,^[23] Duke Nukem 3D, PowerSlave, Legends of the Seven Paladins and Shadow Warrior, now all collectively called BuildGDX.^[24] DukeGDX also supports the files from the 20th Anniversary World Tour edition of Duke Nukem 3D.^[25]

A further port of Blood, called NBlood, was released in January 2019 based on EDuke32,^[26] and the creator's previous Rednukem port for Redneck Rampage (which also supports Duke Nukem 3D and Duke Nukem 64).^[27][28] An EDuke32 port for PowerSlave, called PCExhumed, was released on November 21, 2019.^[29]

The source port Raze forks various Build engine ports, including JFDuke3D, SWP, NBlood, Rednukem, and PCExhumed, and ties it to a new underlying backend based on GZDoom.^[30]

Successor

After multiple attempts to design a successor to Build, Silverman again began experimenting with such an idea in 2006. He used this work - now called Build 2 - while teaching 3D game programming to children at a summer camp from 2007 until 2009, and work continued until 2011 when he lost interest in the project. It features a more advanced lighting system, voxel rendering for entities and true room-over-room 3D spaces, and at least in part retained backwards compatibility with the original Build. Silverman released his drafts to the public on March 7, 2018.^[31][32] The source code was published under a proprietary non-commercial license on June 8, 2019.^[33]

References

External links

• Ken Silverman's Build Engine Page
• BUILD2 Demo and Tools
• Build Engine basic tutorial using mapster32
• Build (game engine) at Curlie

0.00 (0 votes) Original source: https://en.wikipedia.org/wiki/Build (game engine). Read more