Game Engines: The Engine as a Platform
Zusammenfassung
A game engine is the reusable machinery underneath a video game — the renderer, physics, audio, scripting, and tools — separated from the specific game built on top. The idea was born when programmers realized the hardest parts of a game could be written once and reused, sold, or licensed. Over thirty years the engine grew from John Carmack’s hand-tuned Doom renderer into Unity and Unreal: platforms so dominant that “making a game” now usually means “using someone else’s engine.” The engine turned games from bespoke software into an industry with shared infrastructure — and reshaped who gets to make games at all.
What an Engine Is — and Why It Exists
Early games had no engines. Each title was written from scratch, its rendering and logic tangled together for one machine. The engine emerged from a simple economic insight: the expensive, reusable parts — drawing the world, simulating physics, playing sound, loading assets, scripting behavior — are largely the same from game to game. Separate them from the game-specific content and you can ship the next game faster, or license the machinery to others.
The term “game engine” itself dates to the early 1990s and is bound up with one studio: id Software.
id Software and the Birth of the Licensable Engine
John Carmack at id Software built the rendering technology that made the engine a recognized, separable thing. Wolfenstein 3D (1992) and especially Doom (1993) ran on Carmack’s custom renderers, which used clever shortcuts (Doom was not true 3D but a 2.5D system) to achieve fast first-person graphics on ordinary PCs. Crucially, id licensed the Doom engine to other studios, and then the Quake engine (1996) — id’s first true 3D engine with hardware acceleration support. This established the business model: build an engine, license it.
This lineage became id Tech. Carmack’s engines also drove the adoption of hardware-accelerated graphics — Quake’s OpenGL port (GLQuake, 1997) was a landmark showcase for the new 3D accelerator cards.
Unreal Engine: From a Shooter to a Universal Platform
In 1995, Tim Sweeney of Epic Games began writing what became the Unreal Engine, first shipped in the 1998 first-person shooter Unreal. It debuted with dynamic colored lighting, volumetric fog, and an integrated visual level editor — and, decisively, a clean separation between engine and game plus a scripting language (UnrealScript) for designers.
Unreal grew into the high-end standard. Unreal Engine 3 (2006) defined a console generation; Unreal Engine 4 (2014) switched to C++ and a node-based visual scripting system (Blueprints) and moved to a royalty model; Unreal Engine 5 (2022) introduced Nanite (virtualized micro-polygon geometry) and Lumen (real-time global illumination). By UE5, Epic was positioning the engine far beyond games — into film virtual production, architecture, and automotive visualization.
Unity: Democratizing Game Development
Unity Technologies was founded in Copenhagen on August 2, 2004 (originally Over the Edge Entertainment) by David Helgason, Nicholas Francis, and Joachim Ante. Their game GooBall (2005) flopped, but the tools they built to make it were the real product. Unity 1.0 launched at Apple’s WWDC in 2005, targeting macOS first.
Unity’s strategy was the opposite of Unreal’s high-end positioning: make game development accessible and cheap, with a free tier and broad platform export. That bet won the explosion it helped create — the mobile and indie booms. For years a large majority of mobile games shipped on Unity. Its accessibility, asset store, and one-click multi-platform export made it the default engine for small studios, students, and hobbyists, vastly widening who could make a game.
The Two-Engine Duopoly
By the 2020s the commercial engine market had effectively consolidated around two players with opposite philosophies: Unreal (high-fidelity, AAA and film, source-available, royalty on revenue) and Unity (accessible, mobile and indie, subscription/seat-based). Most other general-purpose commercial engines faded or became in-house tools.
In-House Engines and the Open Alternative
Not everyone licenses. Major studios maintain proprietary in-house engines tuned to their games: EA’s Frostbite, Rockstar’s RAGE (Grand Theft Auto), Crytek’s CryEngine, and Valve’s Source. These trade reusability for control and a competitive edge.
On the free/open side, Godot (first released 2014, MIT-licensed) rose as a genuinely open-source alternative, gaining momentum especially after controversial commercial pricing changes elsewhere pushed developers to look for engines they fully control.
Why It Matters
The engine turned game development from craft into platform industry. It separated content from technology, created a licensing economy, and — through Unity and Godot especially — collapsed the barrier to entry so that individuals could ship games that once required a funded studio. It also spread out of games: Unreal and Unity now render films, simulate factories, train robots, and power virtual production stages. The engine became one of the most general-purpose pieces of real-time software ever built.
⚠️ Dead End: Unity’s 2023 Runtime Fee
Engine dominance carries a hostage problem: when thousands of studios build on your platform, your pricing decisions are existential for them. In September 2023, Unity announced a Runtime Fee that would charge developers per game install above certain thresholds — retroactively applying to already-shipped games built on prior license terms.
The reaction was furious and immediate: developers felt betrayed by a charge they could not predict or control, some threatened to abandon the engine, and many migrated to Godot, whose adoption surged. Unity walked the policy back and then fully canceled the Runtime Fee in 2024, but the damage to trust was lasting. The episode is a cautionary tale about platform power: an engine’s value is its ubiquity, and that ubiquity evaporates the moment developers stop trusting the terms beneath their work.