Jump to content

id Tech 4

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Freemanukem (talk | contribs) at 19:08, 10 September 2016 (→MegaTexture rendering technology). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

id Tech 4
Developer(s)id Software
Initial releaseAugust 3, 2004; 20 years ago (2004-08-03)
Repository
Written inC++[1]
PlatformMicrosoft Windows, OS X, Linux, PlayStation 3, Xbox, Xbox 360[2]
TypeGame engine
LicenseGNU General Public License[3]
Websitegithub.com/id-Software/DOOM-3-BFG Edit this on Wikidata

id Tech 4, popularly known as the Doom 3 engine, is a game engine developed by id Software and first used in the video game Doom 3. The engine was designed by John Carmack. Carmack also created previous game engines, such as those for Doom and Quake, which are widely recognized as significant advances in the field. This OpenGL-based game engine has also been used in Quake 4, Prey, Enemy Territory: Quake Wars, Wolfenstein, and Brink.

History

id Tech 4 began as an enhancement to id Tech 3. During development, it was initially just a complete rewrite of the engine's renderer, while still retaining other subsystems, such as file access, and memory management. The decision to switch from C to the C++ programming language necessitated a restructuring and rewrite of the rest of the engine; today, while id Tech 4 contains code from id Tech 3, much of it has been rewritten.[4]

At the QuakeCon 2007, John Carmack, the lead graphics engine developer at id, said to LinuxGames: "I mean, I won't commit to a date, but the Doom 3 stuff will be open source". And like its predecessors, John Carmack has said that id Tech 4 will be released as open source.[5]

At the QuakeCon 2009, Carmack said that he planned to petition ZeniMax Media to release the id Tech 4 source upon the release of Rage.[6] As part of his keynote for QuakeCon 2011 he confirmed that the source code to Doom 3 will be out by the end of the year, after the release of Rage.[7]

On November 16, 2011, Carmack announced on Twitter that he's writing new code for Doom 3's open source release, because "lawyers are still skittish about the patent issue around 'Carmack's reverse'".[8] This refers to an implementation of stencil buffered shadow volume algorithms.

On November 22, 2011, Carmack released the Doom 3 source code on GitHub.[9] The source does not include any of the 'Carmack's Reverse' code. According to Carmack, minor tweaks were made to the code to avoid any infringement.[10]

Hardware

The original requirement of id Tech 4 was that it needed a high-end graphics processing unit (GPU) with fully programmable vertex and pixel shaders, such as the Nvidia GeForce 3 or ATI Radeon 8500, with at least 64 MB of VRAM. By E3 2002, the recommended GPU was "100% DirectX 9.0b compatible", such as the Radeon 9700 with 128 MB of VRAM. While the Radeon 9700's DirectX 9.0 features are not necessary to render the game, its advanced architecture, 256-bit memory bus, and efficiency were needed to run Doom 3 at high detail and playable speed.[11] The "Ultra" graphics mode included in Doom 3 would not even run on the current popular graphics cards available in 2004, requiring at least 512 MB of video memory to display properly and at playable speeds, meaning that it was basically unusable at the time of release.[12]

id Tech 4 resulted in the obsolescence of DirectX 7 graphics chips such as the widespread GeForce 2 and Radeon 7200, as well as older chipsets such as RIVA TNT2 and Rage 128, and software rendering (with an integrated Intel GMA). Until the advent of id Tech 4, a powerful CPU was able to somewhat compensate for an older video card. While John Carmack initially warned gamers not to purchase the GeForce 4 MX[13] (which casual consumers often confused with the DirectX 8 capable GeForce 4 Ti, though it was at best an improved GeForce 2)[citation needed], its somewhat widespread adoption compelled id Software to add it to the list of supported cards. There have been cases of enthusiasts forcing Doom 3 to run on unsupported graphics chips, such as the long obsolete Voodoo 2, but these are unable to render the per-pixel lighting and bump mapping.[14]

Features

The shadowing effects of the unified lighting and shadowing engine are shown on the face and body of the zombies in this screenshot of Doom 3

Graphics

Id Tech 4 added several new graphical features absent in its predecessor, id Tech 3. These included bump mapping, normal mapping, and specular highlighting. More features were added in the development of successive games, and in yet unreleased games using id Tech 4, new features have been added or are planned to be added soon.

The primary innovation of id Tech 4 was its use of entirely dynamic per-pixel lighting, whereas previously, 3D engines had relied primarily on pre-calculated per-vertex lighting or lightmaps and Gouraud shading. While dynamic effects had been available before (such as dynamic moving lights), this effect merely changed the brightness of the vertices of the polygon, with the pixel's colors simply being interpolated between the three vertex colors of its polygon.

This fully realtime approach used in Doom 3, combined with the use of shadow volumes permitted more realistic lighting and shadows[15] than in the previous generation of id's engines. The method used to create the shadow volumes is the subject of a patent by Creative, which Creative granted id permission to use in the Doom 3 engine, in exchange for supporting Creative's EAX advanced sound technologies.[16]

The models used in id Tech 4 engine games are animated using skeletal animation. The engine can blend multiple animations together, to produce a skin that moves correctly for those animations. Because this is CPU intensive, id did some work optimising this by using Intel's Streaming SIMD Extensions (SSE).[17]

MegaTexture rendering technology

The original version of the id Tech 4 engine was designed for somewhat dark environments so it was criticized for its perceived inability to handle extremely large day time outdoor areas. The MegaTexture technology not only removed this issue by introducing a means to create expansive outdoor scenes, but also made the new version as the best game engine to handle the outdoor areas, as well[citation needed]. By painting a single massive texture (32,768×32,768 pixels, though it has been extended to larger dimensions in recent versions of the MegaTexture technology) covering the entire polygon map and highly detailed terrain, the desired effects can be achieved. The MegaTexture can also store physical information about the terrain such as the amount of traction in certain areas or indicate what sound effect should be played when walking over specific parts of the map. i.e. walking on rock will sound different from walking on grass.[18] It is expected that this will result in a considerably more detailed scene than the majority of existing technologies, using tiled textures, allow. The first game utilizing MegaTexture is Enemy Territory: Quake Wars, based on the Tech 4 engine. All id Tech 5 and id Tech 6 games use MegaTexture, with the exception of The Evil Within which uses a new renderer.[19][20] Brink, which uses a heavily modified version of id Tech 4 also uses virtual texturing.[21][22] While the implementation is different from MegaTexture, it was inspired by it.[23][24]

Rendering techniques used in id Tech 4

Scripting

id Tech 4 has a comprehensive scripting language which can be used when creating mods, and is used in Doom 3 to control monsters, weapons, and map events. This scripting language is similar to C++.[25]

In addition to the main scripting language, idTech 4 also has another scripting language that is used for GUIs—both the menus and HUD, and also for GUIs embedded into the game world.[26] These in-game GUIs are sufficiently powerful that you can, for example, run another game such as Doom 1 within the game-world.[27]

Despite this additional level of scripting, it is also possible to create mods using C++ to build native code.[28]

Sound

As a result of the agreement with Creative regarding the patent on shadow volumes, the id Tech 4 engine supports OpenAL, including the Creative Technology specific EAX extensions. The work to include OpenAL support was done by Creative Technology, not by id themselves.[29]

Networking

The engine uses a traditional client–server model. Initially it was planned to have a peer-to-peer networking model.[30] This part of the engine works in a fundamentally similar way to the id Tech 3 equivalent, however id Tech 4 exposes a lot more of the network protocol to mod developers.[31]

Although Doom 3 only supports 4 players, the id Tech 4 engine can be used with more players than this, with Quake 4 and Enemy Territory: Quake Wars both supporting significantly more players.

Forks

iodoom3

iodoom3 is a game engine project which intends to take advantage of building on id Software's id tech 4 source code release. A follow-up to ioquake3, the project was started shortly after the source code release with the goal of creating a bug-free, enhanced open-source id tech 4 source code distribution upon which new games and projects can be based.[32] However, the project never took off and it only has very little changes compared to the original Doom 3 source code.

dhewm3

"dhewm3" redirects here. Not to be confused with Dhoom 3 or Doom 3.

dhewm3 is another game engine project of the id Tech 4 GPL source code. The goal of this engine is bring id Tech 4 with the help of SDL to all suitable platforms, and fix the bugs existing without altering the original gameplay.[33]

The main changes of dhewm3 compared with the original id Tech 4 engine are 64-bit port, SDL for low-level OS support, OpenAL for audio output including OpenAL EFX for EAX reverb effects and a portable build system based on CMake.[33]

fhDOOM

fhDOOM is another fork of the id Tech 4 GPL source code. The goal of fhDOOM is to modernize the Doom 3 game and the id Tech 4 engine and keep everything from the original game working. This includes the game itself, the expansion pack Resurrection of Evil and all the built-in tools.[34] The main changes of fhDOOM compared with the original engine are a full port to modern OpenGL and GLSL, soft shadows (using shadow mapping), soft particles, CMake based build system and experimental support for Qt based tools.

RBDOOM-3-BFG

RBDOOM-3-BFG is a game engine project based upon the source code release of the Doom 3 BFG Edition in 2012. Additional features include Linux and Windows 32/64-bit support, OS X support, Bink video support through FFmpeg, Soft shadows using PCF hardware shadow mapping and modified shaders for lighting interaction to use Half-Lambert lighting like in Half-Life 2.[35]

Storm Engine 2

Storm Engine 2 is a game engine project based on earlier version of RBDoom-3-BFG. Includes various performance improvements, 32/64-bit tools, rudimentary multiplayer support, various gameplay improvements and enhancements. It also comes with SWF files for full screen GUIs and basic set of assets. This fork is incompatible with original Doom 3 BFG assets and is aimed at game developers, who want to make standalone games without relying on Doom 3 content.[36]

Games using id Tech 4

Prey utilized a modified version of id Tech 4 that allowed for effects such as portals, variable gravity, and wall walking

Compared to the preceding and widely used id Tech 3 (Quake III Arena engine) and id Tech 2 (Quake II engine), id Tech 4 has had less success in licensing to third parties.[37] This is especially apparent in comparison to its closest contemporaries, Unreal Engine 2 (2002) and Unreal Engine 3 (2006) from Epic Games.[38] id Software was unwilling to license their newest engine before its "parent game" Doom 3 was completed. However the unexpected long development time going into Doom 3 from 2002-04 meant that they could not put up competition to Epic Games's Unreal Engine 2 during that period. Many who licensed Unreal Engine 2 were thus able to make the switch to Unreal Engine 3 more easily.

While id Tech 4 had taken a new direction with its dynamic per-pixel lighting, this unconventional feature had steeper hardware requirements and was initially only useful in "spooky games" (until the MegaTexture addition), whereas an increasing number of developers preferred conventional engines that could render large outdoor areas. Also notable was id Tech 4's relative lack of downward scalability compared to competing FPS engines; id Tech 4 generally required a DirectX 8.0 compliant GPU such as a GeForce 3; the rival Source engine (which was developed from the previous GoldSrc engine) could still run on the older widespread DirectX 7 GPUs (albeit without shaders being used).

Games using a proprietary license

Games using an open source license

See also

References

  1. ^ "id Tech 4 Source Code".
  2. ^ "3D Engine: id Tech 4". Retrieved September 24, 2008.
  3. ^ "Doom 3 Source Code Released To Public". Retrieved September 25, 2012.
  4. ^ Q&A with John Carmack, E3 2002 Archived 2009-09-29 at the Wayback Machine
  5. ^ Carmack, John (August 7, 2007). "I mean I won't commit to a date, but theDoom 3 stuff will be open source". LinuxGames.com.
  6. ^ "The John Carmack Keynote: Liveblogging QuakeCon".
  7. ^ "Id Software will release the Doom 3 source code". The Inquirer. August 5, 2011. Retrieved August 23, 2015.
  8. ^ "John Carmack's Twitter status update". November 16, 2011. Retrieved November 18, 2011.
  9. ^ "Doom 3 Source on GitHub". November 22, 2011. Retrieved November 22, 2011.
  10. ^ "John Carmack tweets about code infringement work around". November 17, 2011. Retrieved November 22, 2011.
  11. ^ "ATI's Radeon 9700 Takes Performance Lead". Retrieved September 25, 2012.
  12. ^ Doom is a boon Game Industry News, article by Todd Hargosh. Retrieved June 11, 2011
  13. ^ ".plan File for John Carmack - Blue's News". bluesnews.com. Retrieved May 25, 2016.
  14. ^ "Doom3 + Voodoo2_Patch_v1_0". Retrieved September 25, 2012.
  15. ^ iXBT Labs. "Doom 3". iXBT Labs. Retrieved May 25, 2016.
  16. ^ "John Carmack: "This sucks."". Ars Technica. Retrieved May 25, 2016.
  17. ^ "Optimizing the Rendering Pipeline of Animated Models Using the Intel Streaming SIMD Extensions". intel.com. Retrieved May 25, 2016.
  18. ^ "GameSpy: Enemy Territory: Quake Wars - Page 1". gamespy.com. Retrieved May 25, 2016.
  19. ^ "John Carmack on Twitter". Twitter. Retrieved May 25, 2016.
  20. ^ "John Carmack on Twitter". Twitter. Retrieved May 25, 2016.
  21. ^ http://www.pcgameshardware.com/aid,691212/Brink-Multi-core-support-and-better-scaling-on-the-PC/News/
  22. ^ http://www.splashdamage.com/downloads/pubs/brink_preferred_rendering_with_opengl.pdf
  23. ^ "Sparse Virtual Textures". silverspaceship.com. Retrieved May 25, 2016.
  24. ^ "Brink technical analysis". hollemeersch.net. Retrieved May 25, 2016.
  25. ^ "id.sdk [Scripts]". iddevnet.com. Retrieved May 25, 2016.
  26. ^ "id.sdk [GUIs]". iddevnet.com. Retrieved May 25, 2016.
  27. ^ "Fully Interactive Surfaces". battleteam.net. Retrieved May 25, 2016.
  28. ^ "id.sdk [The Code]". iddevnet.com. Retrieved May 25, 2016.
  29. ^ "How the latest Sound Blaster X-Fi technology was utilized in QUAKE 4". Retrieved September 25, 2012.
  30. ^ Doom 3 multiplayer networking info
  31. ^ "id.sdk [The Code]". iddevnet.com. Retrieved May 25, 2016.
  32. ^ "iodoom3 official site". Retrieved August 30, 2012.
  33. ^ a b "dhewm/dhewm3 GitHub". Retrieved February 10, 2014.
  34. ^ "eXistence/fhDOOM GitHub". Retrieved July 26, 2016.
  35. ^ "RobertBeckebans/RBDOOM-3-BFG GitHub". Retrieved January 6, 2015.
  36. ^ "motorsep/StormEngine2 GitHub". Retrieved April 18, 2016.
  37. ^ "id Tech 4 (Concept) - Giant Bomb".
  38. ^ "id Tech 5". Retrieved September 25, 2012.
  39. ^ "Outta Dunwall: Thief Remake The Dark Mod Updates".
  40. ^ "The Dark Mod".
  41. ^ Campbell, Colin (February 4, 2013). "What the Hell is Quadrilateral Cowboy?". IGN. Retrieved February 7, 2013.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Id_Tech_4&oldid=738735013"