Jedi (game engine)

Jedi
Original author(s) Ray Gresko
Developer(s) LucasArts
Written in C
Operating system MS-DOS, Microsoft Windows
Type Game engine
License Proprietary

Jedi is a game engine developed primarily by Ray Gresko for LucasArts. It is extremely similar to the Build engine used in Duke Nukem 3D. While not a true 3D engine, it supported a three-dimensional environment with no limitations in the 3rd dimension (Z). In Doom, environments or levels were limited to existing in the X-Y plane only  levels were laid out two-dimensionally: while floor and ceiling heights could differ, areas could not overlap vertically. The Jedi Engine had support for areas or rooms (called "sectors") on top of one another, a trait that it shared with the Build engine. In the Dark Forces revision of the engine, the renderer could not display two rooms situated on top of each other at the same time. This capability was added for Outlaws.

The Jedi Engine also included the ability to jump and crouch, the ability to look up and down, and atmospheric effects (achieved by careful manipulation of 256-color palette files). The engine is limited in its rendering capabilities, however, and used two-dimensional sprites (pre-rendered in different angles) for most of its object graphics.

The Jedi Engine's lifetime was short lived, being used in two titles, Star Wars: Dark Forces and Outlaws.[1] The sequel to Dark Forces, Jedi Knight, used the Sith engine.

It was sometimes rumored[1][2] that Jedi was a product of reverse-engineering the Doom engine to find out how to build their own. The large differences in the internal structure of the maps and the way elements such as textures are used make the claims somewhat suspect.

References

  1. 1 2 Paul Lilly (2009-07-21). "Doom to Dunia: A Visual History of 3D Game Engines". maximumpc.com. Maximum PC. Retrieved 2016-01-16.
  2. Benjamin Turner (2003-12-08). "Bringin' in the DOOM Clones". gamespy.com. GameSpy. Retrieved 2012-05-06.


This article is issued from Wikipedia - version of the 11/14/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.