Jump to content

Unreal Engine 1

From Wikipedia, the free encyclopedia
(Redirected from UE1)
Unreal Engine 1
Initial releaseUnreal build 100 / May 1998
Stable release
Unreal Tournament build 436 / November 2000
Written inC++, UnrealScript, Assembly[1]
PlatformMicrosoft Windows, Linux, Mac OS and OS X, Dreamcast, PlayStation 2
LicenseProprietary

Unreal Engine 1 (UE1) is the first version of the Unreal Engine game engine. It was initially developed in 1995 by Epic Games founder Tim Sweeney for Unreal. Epic later began to license the Engine to other game studios. It was succeeded by Unreal Engine 2.

History

[edit]
A screenshot released by Epic of the first version of UnrealEd, displaying a graphical user interface written in Visual Basic[2]

The first-generation of Unreal Engine was developed by Tim Sweeney, the founder of Epic Games.[3] Having created editing tools for his shareware games ZZT (1991) and Jill of the Jungle (1992),[4] Sweeney began writing the engine in 1995 for the production of a game that would later become a first-person shooter known as Unreal.[5][6][7] After years in development, it debuted with the game's release in 1998,[8] although MicroProse and Legend Entertainment had access to the technology much earlier, licensing it in 1996.[2] According to an interview, Sweeney wrote 90 percent of the code in the engine, including the graphics, tools, and networking system.[9]

Licensing

[edit]

Sweeney initially did not plan to license his Engine, but when other studios offered to license it from Epic, he agreed.[10]

We released amazing screenshots of our game, but also screenshots of our editor early on, around 1995. That led those companies to call us. Microprose called us and they said "we're interested in licensing your engine!" and we're like "Engine? What engine? Oh! Right, our engine! It's very expensive."

— Sweeney, Game Developer, 2018[10]

Sweeney attributed part of Epic's success in licensing Unreal Engine to their customer support.[10] By late 1999, The New York Times indicated that there had been sixteen external projects using Epic's technology, including Deus Ex, The Wheel of Time, and Duke Nukem Forever,[11] the latter of which was originally based on the Quake II engine.[12] Unlike id Software, whose engine business only offered the source code, Epic provided support for licensees and would get together with their leads to discuss improvements to its game development system, internally dubbed the Unreal Tech Advisory Group.[2][13] While it cost around $3 million to produce and licenses for up to $350,000,[11] Epic gave players the ability to modify its games with the incorporation of UnrealEd and a scripting language called UnrealScript, sparking a community of enthusiasts around a game engine built to be extensible over multiple generations of games.[14][15][16][17]

The big goal with the Unreal technology all long was to build up a base of code that could be extended and improved through many generations of games. Meeting that goal required keeping the technology quite general-purpose, writing clean code, and designing the engine to be very extensible. The early plans to design an extensible multi-generational engine happened to give us a great advantage in licensing the technology as it reached completion. After we did a couple of licensing deals, we realised it was a legitimate business. Since then, it has become a major component of our strategy.

— Sweeney, Maximum PC, 1998[17]

Features

[edit]

Rendering

[edit]

At first, the engine relied completely on software rendering, meaning the graphics calculations were handled by the central processing unit (CPU).[3] However, over time, it was able to take advantage of the capabilities provided by dedicated graphics cards, focusing on the Glide API, specially designed for 3dfx accelerators.[18][19] While OpenGL and Direct3D were supported, they reported a slower performance compared to Glide due to their deficiency in texture management at the time.[20][21] Sweeney particularly criticized the quality of OpenGL drivers for consumer hardware, describing them as "extremely problematic, buggy, and untested", and labeled the code in the implementation as "scary" as opposed to the simpler and cleaner support for Direct3D.[20] With regard to audio, Epic employed the Galaxy Sound System, a software created in assembly language that integrated both EAX and Aureal technologies, and allowed the use of tracker music, which gave level designers flexibility in how a game soundtrack was played at a specific point in maps.[22][23][24] Steve Polge, the author of the Reaper Bots plugin for Quake, programmed the artificial intelligence system, based on knowledge he had gained at his previous employer IBM designing router protocols.[25][26]

According to Sweeney, the hardest part of the engine to program was the renderer; he had to rewrite its core algorithm several times during development. He found the infrastructure connecting all the subsystems less "glamorous".[27][18] Despite requiring a significant personal effort, he said the engine was his favorite project at Epic, adding: "Writing the first Unreal Engine was a 3.5-year, breadth-first tour of hundreds of unique topics in software and was incredibly enlightening."[28]

Other features

[edit]

Among its features were collision detection, colored lighting, and a limited form of texture filtering.[19] It also integrated a level editor, UnrealEd,[29] that had support for real-time constructive solid geometry operations as early as 1996, allowing mappers to change the level layout on the fly.[30][18] Even though Unreal was designed to compete with id Software (developer of Doom and Quake), co-founder John Carmack complimented the game for the use of 16-bit color and remarked its implementation of visual effects such as volumetric fog. "I doubt any important game will be designed with 8-bit color in mind from now on. Unreal has done an important thing in pushing toward direct color, and this gives the artists a lot more freedom," he said in an article written by Geoff Keighley for GameSpot.[7] "Light blooms [the spheres of light], fog volumes, and composite skies were steps I was planning on taking, but Epic got there first with Unreal," he said, adding: "The Unreal engine has raised the bar on what action gamers expect from future products. The visual effects first seen in the game will become expected from future games."[7]

Harry Potter and the Sorcerer's Stone for PC was developed with the Unreal Tournament version of the engine using assets and environments from the 2001 film.[31]

Unreal was noted for its graphical innovations, but Sweeney acknowledged in a 1999 interview with Eurogamer that many aspects of the game were unpolished, citing complaints from gamers about its high system requirements and online gameplay issues.[26] Epic addressed these points during the development of Unreal Tournament by incorporating several enhancements in the engine intended to optimize performance on low-end machines and improve the networking code, while also refining the artificial intelligence for bots to display coordination in team-based gamemodes such as Capture the Flag.[32] Originally planned as an expansion pack for Unreal,[33] the game also came with increased image quality with the support for the S3TC compression algorithm, allowing for 24-bit high resolution textures without compromising performance.[34]

In addition to being available on Windows, Linux, Mac and Unix,[11] the engine was ported through Unreal Tournament to the PlayStation 2 and, with the help of Secret Level, Inc., to the Dreamcast.[35][36]

See also

[edit]

References

[edit]
  1. ^ Edwards, Benj (25 May 2009). "From The Past To The Future: Tim Sweeney Talks". Gamasutra. UBM plc. Retrieved 8 February 2015.
  2. ^ a b c Lightbown, David (January 9, 2018). "Classic Tools Retrospective: Tim Sweeney on the first version of the Unreal Editor". Game Developer. Archived from the original on August 23, 2018. Retrieved February 22, 2022.
  3. ^ a b Sweeney, Tim (2005). "GPU Gems 2 – Foreword". Nvidia Developer. Archived from the original on October 3, 2017. Retrieved October 3, 2017.
  4. ^ Edwards, Benj (May 25, 2009). "From The Past To The Future: Tim Sweeney Talks". Gamasutra. Archived from the original on August 9, 2017. Retrieved November 18, 2018.
  5. ^ Plante, Chris (October 1, 2012). "Better with age: A history of Epic Games". Polygon. Archived from the original on October 4, 2017. Retrieved August 19, 2020.
  6. ^ Nutt, Christian (March 21, 2014). "Epic's Tim Sweeney lays out the case for Unreal Engine 4". Game Developer. Archived from the original on October 3, 2017. Retrieved February 22, 2022.
  7. ^ a b c Keighley, Geoffrey. "Blinded By Reality: The True Story Behind the Creation of Unreal". GameSpot. Archived from the original on May 19, 2001. Retrieved October 3, 2017.
  8. ^ Horvath, Stu (May 17, 2012). "The Imagination Engine: Why Next-Gen Videogames Will Rock Your World". Wired. Vol. 20, no. 6. Condé Nast. Archived from the original on May 30, 2015. Retrieved February 22, 2022.
  9. ^ Brightman, James (March 13, 2012). "An Epic Interview With Tim Sweeney". GamesIndustry.biz. Archived from the original on July 9, 2019. Retrieved July 9, 2019.
  10. ^ a b c Lightbown, David (January 8, 2018). "Classic Tools Retrospective: Tim Sweeney on the first version of the Unreal Editor". www.gamedeveloper.com.
  11. ^ a b c Herz, J.C. (December 2, 1999). "GAME THEORY; For Game Maker, There's Gold in the Code". The New York Times. Archived from the original on September 19, 2017. Retrieved September 24, 2017.
  12. ^ Thompson, Clive (December 21, 2009). "Learn to Let Go: How Success Killed Duke Nukem". Wired. Vol. 18, no. 1. Archived from the original on May 2, 2020. Retrieved May 2, 2020.
  13. ^ Lightbown, David (October 23, 2018). "Classic Tools Retrospective: The tools that built Deus Ex, with Chris Norden". Game Developer. Archived from the original on June 29, 2019. Retrieved February 22, 2022.
  14. ^ Reinhart, Brandon (June 9, 2000). "Postmortem: Epic Games' Unreal Tournament". Game Developer. Archived from the original on July 29, 2017. Retrieved February 22, 2022.
  15. ^ "History of Unreal - Part 1". Beyond Unreal. May 31, 2005. Archived from the original on July 7, 2011. Retrieved July 5, 2009. Probably the biggest draw to Unreal was the ability to mod it. Tim Sweeney (Founder of Epic) wrote a simple scripting engine into the game called UnrealScript.
  16. ^ Busby, Jason; Parrish, Zak; Wilson, Jeff (July 21, 2009). Introduction to Unreal Technology. InformIT. Archived from the original on September 30, 2012. Retrieved February 22, 2022.
  17. ^ a b McDonald, T. Liam (November 1998). "The 3D Engine Wars". Maximum PC. Vol. 3, no. November 1998. p. 43. ISSN 1522-4279. Archived from the original on October 16, 2019. Retrieved September 17, 2017.
  18. ^ a b c Thomsen, Mike (February 23, 2010). "History of the Unreal Engine". IGN. Archived from the original on July 12, 2017. Retrieved August 13, 2017.
  19. ^ a b Hand, Randall (July 21, 2009). "Doom to Dunia: A Visual History of 3D Game Engines". VizWorld. Archived from the original on July 24, 2009. Retrieved February 22, 2022.
  20. ^ a b Wilson, Billy (October 23, 1998). "Talkin' nasty with Epic's code-p1mp, Tim Sweeney". Voodoo Extreme. Archived from the original on May 1, 1999. Retrieved July 20, 2019.
  21. ^ O'Brien, Chris; Wilson, Billy (March 28, 2000). "Ask Sweeney, part 2". Voodoo Extreme. Archived from the original on August 15, 2000. Retrieved July 20, 2019.
  22. ^ Brandon, Alexander (2004). Audio for Games: Planning, Process, and Production. New Riders. p. 70. ISBN 9780735714137.
  23. ^ "Interview - Carlo Vogelsang on Lightning Quick 3D Audio with OpenAL". Creative Labs. June 30, 2003. Archived from the original on August 10, 2003. Retrieved July 8, 2019.
  24. ^ Brandon, Alexander (March 27, 1998). "Interactive Music: Merging Quality with Effectiveness". Game Developer. Archived from the original on February 20, 2020. Retrieved February 22, 2022.
  25. ^ Sweeney, Tim. "Licensing FAQ". Epic MegaGames. Archived from the original on October 6, 1999. Retrieved September 9, 2021.
  26. ^ a b Gestalt (October 28, 1999). "Tim Sweeney of Epic Games". Eurogamer. Archived from the original on August 9, 2020. Retrieved April 16, 2020.
  27. ^ "Next gen engines". Tolstiy's Place. Archived from the original on November 21, 2001. Retrieved August 7, 2020.
  28. ^ Edwards, Benj (February 19, 2021). "Before Fortnite, There Was ZZT: Meet Epic's First Game". How-To Geek. Archived from the original on December 28, 2021. Retrieved March 23, 2021.
  29. ^ Smith, Tom (July 16, 2013). "Unreal: Epic's would-be Doom... er... Quake killer". The Register. Archived from the original on August 12, 2017. Retrieved August 13, 2017.
  30. ^ Wilson, Billy; O'Brien, Chris; Heir, Manveer; Howarth, Robert (May 25, 2000). "Talkin' nasty with Epic's Tim Sweeney". Voodoo Extreme. Archived from the original on June 20, 2000. Retrieved August 13, 2017.
  31. ^ "Harry Potter and the Sorcerer's Stone". IGN. August 10, 2001. Archived from the original on April 4, 2021. Retrieved August 25, 2020.
  32. ^ Kosak, Dave. "Beyond Unreal". GameSpy. Archived from the original on June 21, 2001. Retrieved April 16, 2020.
  33. ^ Reinhart, Brandon (June 9, 2000). "Postmortem: Epic Games' Unreal Tournament". Gamasutra. UBM plc. Archived from the original on October 17, 2016. Retrieved October 8, 2016.
  34. ^ "This Is Unreal Tournament". Next Generation. April 16, 1999. Archived from the original on November 12, 1999. Retrieved January 24, 2021.
  35. ^ "Unreal Tournament". IGN. October 9, 2000. Archived from the original on July 17, 2016. Retrieved August 10, 2017.
  36. ^ "Interview With Dreamcast Unreal Tournament Team". IGN. December 8, 2000. Archived from the original on October 9, 2019. Retrieved February 22, 2022.
Retrieved from "https://wiki.riteme.site/w/index.php?title=Unreal_Engine_1&oldid=1257063157"