Game engine

Short description: Game development and framework for computer science research platform

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages)

| | This software needs to be updated. Please update this software to reflect recent events or newly available information. (February 2018)

|

This article possibly contains original research. Please improve it by verifying the claims made and adding inline citations. Statements consisting only of original research should be removed. (August 2019) (Learn how and when to remove this template message)

|

You can help expand this article with text translated from the corresponding article in português.  (February 2026) Click [show] for important translation instructions.

* Do not translate text that appears unreliable or low-quality. If possible, verify the text with references provided in the foreign-language article.
* You must provide copyright attribution in the edit summary accompanying your translation by providing an interlanguage link to the source of your translation. A model attribution edit summary is `Content in this edit is translated from the existing português Wikipedia article at [[:Pt:Motor de jogo]]; see its history for attribution.`
* You may also add the template `{{Translated|Pt|Motor de jogo}}` to the talk page.
* For more guidance, see Wikipedia:Translation.

|

(Learn how and when to remove this template message)

Part of a series on the:
Video game industry

Activities/jobs

* Video game design
* Game art design
* Game development / Game developer
* Game modification
* Game producer
* Game publisher
* Game journalism
* Level design

Development

* Interaction design
* Game programming
* Level design
* Video game design

Types

* Casual game
* Indie game
* Interactive art
* Interactive movie
* Serious game

Topics

* Digital rights management (DRM)
* Outsourcing
* Software license
* End-user license agreement (EULA)
* Video game preservation

Lists

* List of indie game developers
* List of video game developers
* List of video game industry people

* v
* t
* e

A game engine is a software framework primarily designed for video game development, which may include specialized software libraries and packages, such as level editors.[1] The term "engine" is a direct analogue of "software engine", having it employed across sectors of the software industry.

Furthermore, game engine may also refer to the integrated development environment as an interface behind the given framework, typically a suite of visual development tools and features for developing video games.[2][3]

Game developers can use game engines to create and publish video games across platforms, such as desktops, mobile devices, video game consoles, and other types of computers. The core functionalities commonly covered by a game engine are a 2D or 3D renderer, physics engine, audio engine, scripting, animation, artificial intelligence, networking, streaming, memory management, threads, localization support, scene graph, and cinematics. Game engine developers often economize game development through reuse or adaptation of abstractions built into game engines for production of various games,[4] or through porting of videogames from a single to other target platforms.

## Contents

* 1 Purpose
* 2 History
* 3 Game engines as an industry
* 4 Game middleware
* 5 See also
* 6 References
* 7 External links

## Purpose

Creating a platform game in Godot

In many cases, game engines provide a suite of visual development tools in addition to reusable software components. These tools are generally provided in an integrated development environment to enable simplified, rapid development of games in a data-driven manner. Game-engine developers often attempt to preempt implementer needs by developing robust software suites, which include many elements a game developer may need to build a game. Most game-engine suites provide facilities that ease development, such as graphics, sound, physics and artificial intelligence (AI) functions. These game engines are sometimes called "middleware" because, as with the business sense of the term, they provide a flexible and reusable software platform which provides all the core functionality needed, right out of the box, to develop a game application while reducing costs, complexities, and time-to-market—all critical factors in the highly competitive video game industry.[5]

Like other types of middleware, game engines usually provide platform abstraction, allowing the same game to run on various platforms (including game consoles and personal computers) with few, if any, changes made to the game source code. Often, programmers design game engines with a component-based architecture that allows specific systems in the engine to be replaced or extended with more specialized (and often more expensive) game-middleware components. Some game engines comprise a series of loosely-connected game middleware components that can be selectively combined to create a custom engine, instead of the more common approach of extending or customizing a flexible integrated product. However achieved, extensibility remains a high priority for game engines due to the wide variety of uses for which they are applied. Despite the specificity of the name "game engine", end users often re-purpose game engines for other kinds of interactive applications with real-time graphical requirements—such as marketing demos, architectural visualizations, training simulations, and modeling environments.[6]

Some game engines only provide real-time 3D rendering capabilities instead of the wide range of functionality needed by games. These engines rely upon the game developer to implement the rest of this functionality or to assemble it from other game-middleware components. These types of engines are generally referred to as a "graphics engine", "rendering engine", or "3D engine" instead of the all-encompassing term "game engine". This terminology is inconsistently used, as many full-featured 3D game engines are simply referred to as "3D engines". Examples of graphics engines include: Crystal Space, Genesis3D, Irrlicht, OGRE, RealmForge, Truevision3D, and Vision Engine. Modern game- or graphics-engines generally provide a scene graph—an object-oriented representation of the 3D game-world which often simplifies game design and can be used for more efficient rendering of vast virtual worlds.[7] Most game engines or graphics engines use a Graphics API, which eases communication with the GPU. But older games did not have hardware acceleration or GPUs and had to build their own software renderer.

As technology ages, the components of an engine may become obsolete or insufficient for the requirements of a given project. Since the complexity of programming an entirely new engine may result in unwanted delays (or necessitate that a project restart from the beginning), an engine-development team may elect to update their existing engine with newer functionality or components.

Game engines are not limited to use in the video game field, and have found uses in other scientific fields. Part of this is due to game engines being optimized for consumer-grade computing equipment rather than high-performance computing, allowing researchers to develop programs for their use on lower cost machines. Game engines also simplify many of the computing operations needed for scientific software, including graphics, networking, and interactivity, reducing the need to develop these features themselves.[8]

## History

Some game engines experience an evolution over time and develop a family tree, like for instance id's Quake engine which resulted in the id Tech family.

Before game engines, games were typically written as singular entities: a game for the Atari 2600, for example, had to be designed from the bottom up to make optimal use of the display hardware—this core display routine is today called the kernel by developers of games for older systems. Other platforms had more leeway, but even when the display was not a concern, memory constraints usually sabotaged attempts to create the data-heavy design that an engine needs. Even on more accommodating platforms, very little could be reused between games. The rapid advance of arcade hardware—which was the leading edge of the market at the time—meant that most of the code would have to be thrown out afterwards anyway, as later generations of games would use completely different game designs that took advantage of extra resources. Thus, most game designs through the 1980s were designed through a hard-coded rule set with a small number of levels and graphics data. Since the golden age of arcade video games, it became common for video game companies to develop in-house game engines for use with first-party software.

A notable example of an in-house game engine on home consoles in the mid-1980s was the smooth side-scrolling engine developed by Shigeru Miyamoto's team at Nintendo for the Nintendo Entertainment System (NES). The engine they had developed for the side-scrolling racing game Excitebike (1984) was later employed for the scrolling platformer Super Mario Bros. (1985). This allowed Mario to smoothly accelerate from a walk to a run, rather than move at a constant speed like in earlier platformers.[9]

While third-party game engines were not common until the rise of 3D computer graphics in the 1990s, several 2D game creation systems were produced in the 1980s for independent video game development. These include Pinball Construction Set (1983), ASCII's War Game Construction Kit (1983),[10] Thunder Force Construction (1984),[11] Adventure Construction Set (1984), Garry Kitchen's GameMaker (1985), Wargame Construction Set (1986), Shoot-'Em-Up Construction Kit (1987), Arcade Game Construction Kit (1988), and, most popularly, ASCII's RPG Maker engines from 1998 onward. Klik & Play (1994) is another legacy offering that is still available.[12]

The term game engine emerged in the mid-1990s, particularly with the rise of 3D games like first-person shooters, which often featured a dedicated first-person shooter engine. For instance, Epic Games, founded by Tim Sweeney, debuted its Unreal Engine in 1998.[13]

Such was the popularity of Id Software's Doom and Quake games: rather than building from scratch, its developers licensed the core portions of the software and designed their own graphics, characters, weapons, and levels—they were the "game content" or "game assets." Separation of game-specific rules and data from basic concepts like collision detection and game entity meant that teams could grow and specialize.[12]

Later games, such as id Software's Quake III Arena and Epic Games' Unreal (1998), were designed with this approach in mind, with the engine and content developed separately. The practice of licensing such technology has proved to be a useful auxiliary revenue stream for some game developers, as a single license for a high-end commercial game engine can range from $10,000 to millions of dollars, and the number of licensees can reach several dozen companies, as seen with the Unreal Engine. At the very least, reusable engines make developing game sequels faster and easier, which is a valuable advantage in the competitive video game industry. While a strong rivalry existed between Epic Games and id Software around 2000, Epic Game's Unreal Engine has since become far more popular than id Tech 4 and its successor, id Tech 5.[14]

Modern game engines are some of the most complex applications written, often featuring dozens of finely-tuned systems interacting to ensure a precisely-controlled user experience. The continued evolution of game engines has created a strong separation between rendering, scripting, artwork, and level design. As such, it is now common, for example, for a typical game development team to have several times as many artists as actual programmers.[15]

While third-party game engines are predominantly used in the development of first-person shooter games, they are also being used across other genres. For example, Gamebryo is used in Software:The Elder Scrolls III: Morrowind and Dark Age of Camelot, whereas Unreal Engine 2 is used in Lineage II. Game engines are also used for games originally developed for home consoles, with RenderWare for the Grand Theft Auto and Burnout franchises as an example.

Due to modern multi-core systems and growing demands in realism, exploiting threads has become more important. Separate threads of execution within a game engine manage intensive operations, including rendering, asset streaming, audio playback, and physics simulation. Racing games have typically been at the forefront of threading with the physics engine running in a separate thread long before other core subsystems were moved, partly because rendering and related tasks need updating at only 30–60 Hz. For example, on PlayStation 3, physics ran in Need For Speed at 100 Hz, versus Forza Motorsport 2 at 360 Hz.

Although the term was first used in the 1990s, few earlier systems in 1980s are considered as game engines, such as Sierra's Adventure Game Interpreter (AGI) and SCI systems, LucasArts' SCUMM system and Incentive Software's Freescape engine (in 1986[16]). Unlike most modern game engines, these game engines were never used in any third-party products (except for the SCUMM system, which was licensed to and used by Humongous Entertainment).

As game engine technology matures and becomes more user friendly, the application of game engines has widened in scope. They are now used for serious games: visualization, training, medical, and military simulation applications, with the CryEngine being one example.[17] To improve accessibility, new hardware platforms are also now targeted by game engines, including mobile phones (e.g. Android, iPhone) and web browsers. (e.g. WebGL, Shockwave, Flash, Trinigy's WebVision, Silverlight, Unity Web Player, O3D and pure DHTML.)[18]

Additionally, more game engines are being built upon higher-level languages, such as Java, C# and .NET (e.g., TorqueX, and Visual3D.NET), Python (Panda3D), or Lua Script (Leadwerks). As most 3D-rich games are now mostly limited by the power of a graphics card, the potential slowdown due to translation overheads of higher-level languages becomes negligible, while productivity gains offered by these languages serve the game engine developers' benefit.[19] These recent trends are being propelled by companies such as Microsoft to support indie game development. Microsoft developed XNA as the primary Software Development Kit (SDK) for all video games released on Xbox and their related products. This includes the Xbox Live Indie Games[20] channel designed specifically for smaller developers who do not have the extensive resources necessary to box games for sale on retail shelves. It is becoming easier and cheaper than ever to develop game engines for platforms that support managed frameworks.[21]

## Game engines as an industry

Producers of game engines decide how they allow users to use their products. Just as gaming is an industry, so are the engines they are built off. The major game engines come at varying prices, whether it be in the form of subscription fees or license payments.[22] Unity and Unreal Engine are currently the two most popular choices for game developers.[23] Although the differences among the different game engines blur as they build their own tools on top of them, different game developers may be too used to a system to change, or attracted by the huge benefits of such engines regardless of pay-walls.

Free and open-source engines such as Godot, have seen a rise in popularity, particularly following the 2023 Unity pricing controversy which drove game developers and studios to seek engines with a permissive license.[24]

## Game middleware

Applied more broadly, game engines themselves can be described as middleware. In video games, however, middleware is often used to refer to subsystems of functionality within a game engine. Some game middleware does only one thing, yet does it more convincingly or more efficiently than general purpose middleware.

The four most-widely used middleware packages[25] that provide subsystems of functionality include RAD Game Tools' Bink, Firelight FMOD, Havok, and Scaleform GFx. RAD Game Tools develops Bink for basic video rendering, along with Miles audio, and Granny 3D rendering. Firelight FMOD is a low cost robust audio library and toolset. Havok provides a robust physics simulation system, along with a suite of animation and behavior applications. Scaleform provides GFx for high performance Flash UI and high-quality video playback, and an Input Method Editor (IME) addon for in-game Asian chat support.

Other middleware is used for performance optimization—for example Simplygon helps to optimize and generate level of detail meshes, and Umbra adds occlusion culling optimizations to 3D graphics.

Some middleware contains full source code,[6] or is provided an API reference for a compiled binary library. Some middleware programs can be licensed either way, usually for a higher fee for full source code.

## See also

* 3D computer graphics
* Authoring system
* Game physics
* List of first-person shooter engines
* List of game engines
* List of game middleware
* Virtual studio

## References

1. ↑ Valencia-Garcia, Rafael (2016). Technologies and Innovation: Second International Conference, CITI 2016, Guayaquil, Ecuador, November 23-25, 2016, Proceedings. Springer. ISBN 9783319480244. https://books.google.com/books?id=bZZyDQAAQBAJ&pg=PA146. Retrieved 2021-07-22.
2. ↑ "Common game development terms and definitions | Game design vocabulary | Unity". Unity. https://unity.com/how-to/beginner/game-development-terms.
3. ↑ Tan, James. "Introduction - Unreal Engine (Canterbury Software Summit 2013 slides)". https://cdn2.unrealengine.com/Resources/files/Build_1.x_Not_1.0_JamesTan-1535398852.pdf.
4. ↑ "What is a Game Engine?". GameCareerGuide.com. http://www.gamecareerguide.com/features/529/what_is_a_game_.php.
5. ↑ O'Neill, John (January 15, 2008). "My Turn: The Real Cost of Middleware". Gamedaily.com. http://www.gamedaily.com/articles/features/my-turn-the-real-cost-of-middleware/71334/?biz=1.
6. ↑ 6.0 6.1 Report on Use of Middleware in Games[Usurped!]
7. ↑ "Scene Graph in Unreal Editor for Fortnite | Fortnite Documentation | Epic Developer Community" (in en-us). https://dev.epicgames.com/documentation/en-us/fortnite/scene-graph-in-unreal-editor-for-fortnite.
8. ↑ Lewis, Michael; Jacobson, Jeffrey (January 2002). "Game Engines in Scientific Research". Communications of the ACM 45 (1). doi:10.1145/502269.502288. https://cacm.acm.org/research/introduction-64/.
9. ↑ Williams, Andrew (16 March 2017). History of Digital Games: Developments in Art, Design and Interaction. CRC Press. pp. 152–4. ISBN 978-1-317-50381-1.
10. ↑ "War Game Construction Kit". Oh!FM. http://retropc.net/fm-7/museum/softhouse/ascii/000701300.html. Alt URL
11. ↑ "Thunder Force Construction". Oh!FM. http://retropc.net/fm-7/museum/softhouse/tecnosoft/330602301.html. Alt URL
12. ↑ 12.0 12.1 Fiadotau, Mikhail (2019). "Dezaemon, RPG Maker, NScripter: Exploring and classifying game 'produsage' in 1990s Japan". Journal of Gaming & Virtual Worlds 11 (3): 215–230. doi:10.1386/jgvw.11.3.215_1.
13. ↑ Weinberger, Matt. "The CEO behind 'Fortnite' says it's 'evolving beyond being a game' and explains the company's ambitious vision" (in en-US). https://www.businessinsider.com/epic-games-ceo-tim-sweeney-fortnite-unreal-engine-2019-3.
14. ↑ Bramwell, Tom (2007-08-09). "id Tech 5 Interview • Page 1 • Interviews •". Eurogamer.net. http://www.eurogamer.net/articles/id-tech-5-interview.
15. ↑ "Game Development Team Composition Study - Changes over time.". http://web.cs.wpi.edu/~id111x/c05/slides/intro.ppt.
16. ↑ "Freescape Engine". Universal Videogame List. https://www.uvlist.net/groups/info/freescapeengine.
17. ↑ "Video Games Starting to Get Serious". Gazette.net. 2007-08-31. http://www.gazette.net/stories/083107/businew11739_32356.shtml.
18. ↑ "Gaming: Mobile and Wireless Trends for 2008". M-trends.org. http://www.m-trends.org/2008/01/mobile-and-wireless-trends-for-2008.html.
19. ↑ Zerbst, Stefan; Düvel, Oliver (2004). 3D Game Engine Programming (book). Premier Press. ISBN 9781592003518. https://books.google.com/books?id=-vifhqAi0SEC&q=gpu-limited+games&pg=PA338. Retrieved 2011-01-17.
20. ↑ "xboxlivecommunitygames.org". xboxlivecommunitygames.org. http://www.xboxlivecommunitygames.org/.
21. ↑ "Microsoft to Enable User-Created XBox 360 Games". http://www.gamasutra.com/php-bin/news_index.php?story=10458.
22. ↑ "The 10 Best Video Game Engines | 2018 Edition" (in en-US). 2017-03-11. https://www.gamedesigning.org/career/video-game-engines/.
23. ↑ "The Two Engines Driving the $120B Gaming Industry Forward" (in en-US). 2018-09-20. https://www.cbinsights.com/research/game-engines-growth-expert-intelligence/.
24. ↑ Forbes-Calvin, Alex (2025-07-17). "Two years after the Unity controversy, how are things going with Godot?" (in en). https://www.gamesindustry.biz/two-years-after-the-unity-controversy-how-are-things-going-with-godot.
25. ↑ "Gamasutra Engine and Middleware Technology Survey". Gamasutra.com. 2009-05-08. https://www.gamedeveloper.com/programming/the-engine-survey-technology-results.

## External links

* v
* t
* e

Game engines (list)

* Source port
* First-person shooter engine
* list
* Game engine recreation
* list
* Game creation system
* List of visual novel engines

Free and
open-source|

| 2D|

* Adventure Game Studio
* Beats of Rage
* Cocos2d
* Corona
* Moai
* OHRRPGCE
* OpenFL
* ORX
* Pygame
* Ren'Py
* Stencyl
* Stratagus

|

2.5D|

* Build
* Doom ports
* ORX

3D|

* Away3D/AwayJS
* Cafu
* GamePlay
* GLScene
* Horde3D
* Irrlicht
* JMonkey
* OGRE
* Panda3D
* Platinum Arts Sandbox
* PlayCanvas
* Torque
* Xenko

Mix|

* Allegro
* Godot
* libGDX
* Lightweight Java Game Library
* Spring

Proprietary|

| 2D|

* Clickteam Fusion
* Construct
* Felgo (V-Play Engine)
* GameMaker Studio
* GameSalad
* RPG Maker
* UbiArt Framework
* Vicious
* Zillions of Games

|

3D|

* 4A
* Amazon Lumberyard
* AnvilNext
* Chrome
* Creation
* CryEngine
* Crystal Tools
* Decima
* Diesel
* Disrupt Engine
* Dunia Engine
* Ego
* Essence
* Fox
* Frostbite
* HeroEngine
* id Tech
* 5
* 6
* 7
* Ignite
* IW
* LithTech
* Luminous Studio
* MT Framework
* PhyreEngine
* REDengine
* RAGE
* Shark 3D
* ShiVa
* Snowdrop
* Source
* Unigine
* Unreal

Mix|

* Gamebryo
* Unity

Historical
(Free and
open-source)|

| 2D|

* Thousand Parsec
* Vassal
* Xconq

|

2.5D|

* Doom engine

3D|

* Blender Game
* Bork3D
* Crystal Space
* CyanWorlds.com Engine
* Delta3D
* Dim3
* Genesis3D
* id Tech
* Quake
* Quake II
* 3
* 4
* Open Wonderland
* Papervision3D
* PLIB

Mix|

* Wintermute Engine

Historical
(Proprietary)|

| 2D|

* Game-Maker
* GameMaker
* Garry Kitchen's GameMaker
* Genie
* MADE
* M.U.G.E.N
* SCUMM
* Southpaw
* Virtual Theatre

|

3D|

* Bitsquid
* C4
* Dark
* Enigma
* Flare3D
* GoldSrc
* Filmation
* Freescape
* INSANE
* Jade
* Jedi
* LyN
* Marmalade
* Panta Rhei
* Pie in the Sky
* Q
* Reality Lab
* RenderWare
* SAGE
* Silent Storm
* Sim RPG Maker
* Sith
* Titan
* Truevision3D
* Vision
* Visual3D
* Voxel Space
* XnGine
* Zero

Proprietary
middleware|

* Euphoria
* Gameware
* GameWorks
* Havok
* iMUSE
* Kynapse
* SpeedTree
* FaceGen

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Game engine. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Software:Game_engine&oldid=4289646"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template