BRENNEN

Industries / Media, arts and recreation / Media and entertainment / Video games

Engines and programming

Programmers build or license an engine, the shared software that draws each frame, plays sound, runs physics and reads the controls, and then write the game's own code on top of it.

7

Milestones achieved, from 1996 to 2026.

2

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 1996

    3D cards reach home PCs

    On 7 October 1996 Orchid released the Righteous 3D, the first card built on 3dfx Interactive's Voodoo Graphics chips. It drew only 3D scenes and worked alongside the PC's ordinary 2D graphics card. 3dfx gave programmers its own interface, Glide, which also worked under DOS, and a patch called GLQuake let id Software's Quake use the card from early 1997; cofounder Ross Smith told Club386 that "we probably sold millions of boards because of that game."

    LessonLeading one generation of graphics hardware did not last; by the Computer History Museum's account 3dfx went "from industry leader to bankruptcy in just a few years," and NVIDIA took most of its assets.

    club386.comcomputerhistory.org

    Credit

    3dfx Interactive cofounders Gordon Campbell, Scott Sellers, Ross Smith and Gary Tarolli

  2. 1997

    Doom's code given away

    On 23 December 1997 John Carmack of id Software released the source code of Doom, the 1993 game, "for your non-profit use." Players still needed the original game's data files. The DOS version was held back because it used a copyrighted sound library, so the released code ran only on Linux. The copy now kept on id Software's GitHub page carries the GNU General Public License, which lets anyone change and share the code.

    github.com

    Credit

    John Carmack, id Software

  3. 2005

    An engine for small teams

    Nicholas Francis, Joachim Ante and David Helgason founded Unity in a Copenhagen apartment in 2004 and launched their engine to Mac developers at Apple's developer conference in June 2005. At first only developers working on Macs could use it, and Ante recalled that at launch "we had like one customer. That's $200." The founders' stated aim was to "democratize game development," and in 2019 TechCrunch wrote that "nearly half of the world's games" were built with Unity.

    techcrunch.com

    Credit

    Nicholas Francis, Joachim Ante and David Helgason, Unity

  4. 2015

    Engines free to start

    In March 2015 Epic Games made Unreal Engine 4 free to download and dropped the US$19-a-month subscription it had charged for about a year. Instead it takes a 5% royalty on gross revenue after the first US$3,000 per product per quarter; Tim Sweeney, Epic's founder, said the engine's user base had grown about tenfold after the subscription began. Godot, an engine whose code Juan Linietsky and Ariel Manzur wrote from 2007, had been released as open source early in 2014 under the MIT license, which lets anyone use, change and share it, even commercially.

    fortune.comgodotengine.orggodotengine.org

    Credit

    Epic Games; Juan Linietsky, Ariel Manzur and the Godot contributors

  5. 2018

    Ray tracing in real time

    Ray tracing draws a scene by following rays of light through a 3D model of it, which gives true reflections and shadows. Games had instead used rasterization, which paints triangles onto the flat plane of the screen. On 19 March 2018 Microsoft announced DirectX Raytracing (DXR) for DirectX 12, noting that "no games currently use real-time raytracing," with EA's SEED group, Epic, Unity and Futuremark named as early users. Sony's PlayStation 5, detailed in March 2020, lists "Ray Tracing Acceleration" in its AMD graphics chip.

    devblogs.microsoft.comblog.playstation.com

    Credit

    Microsoft's Direct3D team; Sony Interactive Entertainment and AMD

  6. 2022

    A studio drops its engine

    On 21 March 2022 CD Projekt Red, maker of The Witcher games and Cyberpunk 2077, said its next Witcher game would be made in Epic's Unreal Engine 5 instead of its own REDengine, under a multi-year partnership that also covers technical work on Unreal Engine 5 itself.

    LessonKeeping an in-house engine current is costly; the studio's chief technology officer, Paweł Zawodny, said it had "spent a lot of resources and energy to evolve and adapt REDengine with every subsequent game release.".

    gamedeveloper.com

    Credit

    CD Projekt Red; Epic Games

  7. 2026

    Agents scored on engine work

    AI coding agents are programs that write, run and fix code with little human help. In GameDevBench, published in February 2026 and revised in June, Wayne Chi, Chris Donahue and colleagues gave agents 333 game-making tasks drawn from web and video tutorials; the best agent solved 53.8%, and showing it screenshots or video of the running game raised GPT-5.4 from 41.1% to 52.0%. In GameEngineBench, from July 2026, the best of 12 agent setups passed 55.5% of 110 C++ tasks from nine Unreal Engine 5 game projects on the first try, and 31 tasks were solved by none.

    arxiv.orgarxiv.org

    Credit

    Wayne Chi, Chris Donahue and colleagues; Brian La, Kanav Goyal and colleagues

Watch for

  1. An assistant inside the engine

    Epic Games released Unreal Engine 5.7 in November 2025 with an AI assistant built into the editor, where developers can ask technical questions, request C++ code and follow step-by-step instructions without leaving the program. Digital Production noted that the assistant is "not intended to replace documentation or verified workflows," that its "long-term reliability in multi-user pipelines remains untested," and that Epic had not detailed how it handles data.

    Achieved whenAn outside party measures how often its code and instructions are correct on a published set of Unreal tasks, or a studio reports measured results from using it on a released game.

    digitalproduction.com

    Claimed by

    Epic Games, November 2025

  2. Shaders compiled before download

    A shader is a small program that tells the graphics card how to draw a surface or effect; PC games often compile theirs on the player's machine, which causes stutter. Microsoft's Advanced Shader Delivery has developers record a game's shader data, compiles it in the cloud with the graphics makers' compilers, and sends ready-made shaders to Windows. Microsoft first offered it on the ROG Xbox Ally handhelds in 2025; NVIDIA added support in October 2026, starting with Call of Duty: Modern Warfare 4 and Gears of War: E-Day, and claims a shader-cache hit rate of "nearly 100 percent" in supported games. It does not address traversal stutter.

    Achieved whenAn outside test counts hitches in supported games with and without it, on more than one make of graphics card.

    pcworld.com

    Claimed by

    Microsoft, 2025; NVIDIA, October 2026

Open

  1. 01

    Fix real engine bugs

    A test of AI coding agents on the bug reports of an open-source engine, in the style of SWE-bench, the benchmark built from real GitHub issues. Collect closed bug reports for the Godot engine whose fix was merged together with a new unit test. Set the code back to just before the fix, give an agent the bug report, and count the fix as good only if the new test passes and no old test breaks.

    The brief
    Credit · unclaimed
  2. 02

    Count stutter across games

    A repeatable public count of stutter, the short freezes that interrupt play, in recent PC games. On fixed hardware, play the same 10-minute route in each game three times with an empty shader cache and three times with a full one, record the time of every frame, and count hitches (frames over 50 ms) per minute. Hitches that vanish on the second pass point to shader compilation, the step in which the graphics driver turns a game's effects into code for the card; those that stay point to traversal stutter, pauses while new parts of the world are loaded.

    The brief
    Credit · unclaimed

Open 01 · the brief

Fix real engine bugs

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A test of AI coding agents on the bug reports of an open-source engine, in the style of SWE-bench, the benchmark built from real GitHub issues. Collect closed bug reports for the Godot engine whose fix was merged together with a new unit test. Set the code back to just before the fix, give an agent the bug report, and count the fix as good only if the new test passes and no old test breaks.

Why it is still open

Published game-coding tests measure making games, not maintaining an engine. GameDevBench's 333 tasks come from tutorials; SWE-Game's 247 Godot tasks include repairing 83 bugs that its authors planted in 41 reference games, and porting games from Godot to Unity; GameEngineBench's 110 C++ tasks come from nine Unreal Engine 5 game projects. SWE-bench Multilingual, whose 300 tasks come from real issues in open-source projects in nine programming languages, includes the three.js 3D graphics library but no game engine. This research found no test built from a game engine's own bug tracker.

arxiv.orgarxiv.orgarxiv.orgdatasets-server.huggingface.co

Built with what exists

Godot's public GitHub repository, its unit tests and its SCons build; the open-source SWE-bench harness and Docker to rebuild each task; agents such as Claude Code running Claude Fable 5.2 (see the Note "Three working devices"), GitHub Copilot Fusion (see the Note "Effort, not model") and OpenHands; the GitHub API to collect issues and pull requests.

  1. First step

    Use the GitHub API to list Godot pull requests merged in 2025 that close a bug report and add a unit test, then rebuild five of them at the commit before the fix.

  2. Done looks like

    300 tasks from Godot bugs closed in 2024 to 2026, each confirmed to fail before and pass after the human fix; for each agent, the share solved; 50 agent fixes read by two experienced C++ developers for whether they fix the cause, not just the test; tasks and harness published under Godot's MIT license.

Open 02 · the brief

Count stutter across games

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A repeatable public count of stutter, the short freezes that interrupt play, in recent PC games. On fixed hardware, play the same 10-minute route in each game three times with an empty shader cache and three times with a full one, record the time of every frame, and count hitches (frames over 50 ms) per minute. Hitches that vanish on the second pass point to shader compilation, the step in which the graphics driver turns a game's effects into code for the card; those that stay point to traversal stutter, pauses while new parts of the world are loaded.

Why it is still open

TechSpot's October 2026 test of SCSKiller, an open-source tool that compiles a game's shaders before it is launched, covered seven games, and noted that traversal stutter, "one of the biggest issues, particularly with Unreal Engine 5 games," is beyond the tool's reach. This research found no published count across many games and engines.

techspot.com

Built with what exists

Intel's PresentMon, an open-source tool that logs the time of every frame; SCSKiller, to separate shader stutter from the rest; recorded controller input replayed by a script, or an AI agent that walks the route; Python with pandas for the counts.

  1. First step

    Record three first runs and three repeat runs of one route in two owned Unreal Engine 5 games with PresentMon, and check how much the hitch counts vary between runs.

  2. Done looks like

    50 games released from 2024 to 2026, grouped by engine, each with hitches per minute on first and repeat runs; run-to-run spread under 10% across three repeats; routes, raw frame logs and counts published.