Engine Versioning and Middleware Signals Across Rockstar Studios

Report ID: 1226 Series: 18 — Source-code-leak / intent analysis Scope: Public-reporting synthesis only. No leaked technical specifics are reproduced. Language: British English.

Introduction

The September 2022 incident in which a teenage intruder exfiltrated a large volume of pre-release material relating to Rockstar Games' next Grand Theft Auto title prompted an unusual amount of mainstream technical reporting on what is normally an opaque area: the internal engineering practices of one of the most secretive studios in the industry. Most of the coverage focused, understandably, on the leaked test footage — early build clips of two protagonists, debug overlays, placeholder animations and unfinished interiors. Behind that headline, however, journalists and the more technically-minded community sites produced a smaller body of reporting that touched on the underlying engine, the tooling visible in the captured material, and what Rockstar's hiring patterns had been suggesting for several years (Bloomberg, 2022; Eurogamer, 2022).

This report is a public-reporting synthesis, drawing exclusively on press coverage, Wikipedia's general-reference article on the RAGE engine, publicly archived job postings, and analysis pieces from outlets such as Digital Foundry. It deliberately avoids reproducing any technical content from the leak itself. The aim is to assemble a picture of: (a) how the Rockstar Advanced Game Engine ("RAGE") is publicly understood to have evolved between Grand Theft Auto V (2013), Red Dead Redemption 2 (2018), and the as-yet-unreleased Grand Theft Auto VI; (b) which middleware components Rockstar has openly acknowledged or licensed, namely NaturalMotion's Euphoria, Bullet Physics, and the various Scaleform-style UI layers; (c) what the structure of the studio network — particularly Rockstar North in Edinburgh, Rockstar San Diego, and Rockstar Toronto — implies about cross-studio code-sharing on the engine itself; and (d) where the public record permits informed speculation about whether GTA VI represents a major version bump of RAGE or, more conservatively, an incremental fork from the Red Dead Redemption 2 branch.

Throughout, speculative content is explicitly flagged. A confidence section at the end summarises which claims rest on solid public sourcing and which are reasoned conjecture.

RAGE Across Studios

RAGE — the Rockstar Advanced Game Engine — has, since its debut in Rockstar Games presents Table Tennis (2006), served as the in-house engine for every major Rockstar title (Wikipedia, 2024a). Its public history can be traced through Rockstar's own press materials and through general-reference summaries: Grand Theft Auto IV (2008) was the first open-world title to use it; Red Dead Redemption (2010), Max Payne 3 (2012), Grand Theft Auto V (2013), and Red Dead Redemption 2 (2018) followed, each with substantial publicly-acknowledged revisions to the renderer, streaming system, and animation pipeline (Wikipedia, 2024a; Digital Foundry, 2018).

Crucially, RAGE has never been "owned" by a single studio. Public Rockstar credits, careers pages, and trade-press features have consistently named at least three studios with substantial engine-side responsibility:

Rockstar San Diego, historically the originator of RAGE following Rockstar's 2002 acquisition of Angel Studios, has long been described in press features as the home of the engine's core technology group. Job adverts archived from the studio across the 2010s repeatedly referenced "RAGE Technology" or "Core Engine" teams (Rockstar Games Careers, archived listings; Kotaku, 2018).
Rockstar North, in Edinburgh, is publicly understood as the lead studio for the Grand Theft Auto series, and trade reporting has noted that its programmers have driven much of the streaming, world-simulation, and AI infrastructure that distinguishes the open-world titles (Edge, 2013; Eurogamer, 2018).
Rockstar Toronto has surfaced in job listings advertising "Engine Programmer" and "Tools Programmer" roles that mirror those at North and San Diego, suggesting at minimum a contributing role and possibly a maintenance-and-port role for shared technology (Rockstar Games Careers, archived listings).

To these three, public reporting has at various times added Rockstar London (audio, scripting tools), Rockstar Leeds (handheld and mobile ports, but with shared tools), Rockstar India, and Rockstar New England (Wikipedia, 2024b). The picture that emerges is not of a single studio handing finished libraries to others, but of a federated engine codebase to which several studios commit, with San Diego and North typically holding the architectural pen.

The 2022 leak coverage reinforced this picture indirectly. Multiple outlets noted that the captured material showed tooling and naming conventions consistent with continuity from the Red Dead Redemption 2 era, and Bloomberg's reporting on Rockstar's internal organisation in the same period described a long-running consolidation of staff onto the GTA VI project from across the studio network (Bloomberg, 2022). The implication, in public-reporting terms, is that the engine running in the leaked clips was not a clean-room rewrite but a continuation of the lineage maintained by San Diego with substantial new contributions from North.

Middleware Confirmed Publicly (Euphoria, Bullet, and the Scaleform Question)

Three middleware threads dominate the public record on Rockstar's engine, and each has been confirmed by sources well outside the leak itself.

Euphoria. NaturalMotion's Euphoria is the most prominent and the most extensively documented. It is a runtime character-behaviour system — distinct from a traditional animation playback engine — that simulates muscular and balance responses to forces. Rockstar's adoption of Euphoria was first publicised around Grand Theft Auto IV in 2008 and has been a recurring talking point in trade interviews and post-mortems since (Wikipedia, 2024c; Digital Foundry, 2018). Take-Two Interactive's later acquisition of NaturalMotion in 2014 brought the middleware in-house, and this corporate fact — reported widely at the time and not contested since — means that successive Rockstar titles have been able to evolve Euphoria internally rather than negotiate licence terms (Reuters, 2014; Wikipedia, 2024c). Press coverage of Red Dead Redemption 2 and of the GTA V PC release repeatedly highlighted Euphoria's continued presence; Digital Foundry's technical breakdowns are explicit on this point (Digital Foundry, 2018; Digital Foundry, 2015).

Bullet Physics. Bullet, the open-source physics library originated by Erwin Coumans, is publicly acknowledged on its own website as having been used in Grand Theft Auto IV and Red Dead Redemption (Bullet Physics, n.d.; Wikipedia, 2024a). What Rockstar uses today is less clearly stated in public sources, and trade reporting from the RDR2 era is careful to note that Rockstar's physics implementation is heavily customised. The mainstream-press summary that survives is therefore: Bullet was historically a foundation, the present-day RAGE physics layer is a heavily modified descendant, and no public source has confirmed a wholesale replacement.

Scaleform and its successors. Autodesk's Scaleform GFx, a Flash-based UI middleware, was for many years the de facto standard for AAA in-game UI and was widely reported as the menu/HUD technology behind GTA V and earlier RAGE titles (Wikipedia, 2024d). Autodesk discontinued active development of Scaleform in 2018, prompting the broader industry to migrate to alternatives such as Coherent Labs' Gameface, in-house HTML/CSS renderers, or bespoke immediate-mode UI systems. Public reporting on Rockstar specifically has not unambiguously confirmed what replaced Scaleform internally; however, job listings analysed by community trackers in the late 2010s and early 2020s referenced "UI Programmer" roles with experience in custom rendering rather than Scaleform-specific skills, which sector observers have read as a signal of an internal replacement (industry trade press summarised in Eurogamer, 2022).

A fourth, less prominent thread is Simul's trueSKY-style atmospheric rendering and a range of speech and dialogue middleware. None of these were specifically named in public coverage of the 2022 leak, and so they fall outside this report's scope.

What Job Listings Reveal

One of the more reliable proxies for engine direction at a secretive publisher is its careers page. Several community sites, and at least one Bloomberg feature, have aggregated Rockstar listings over the years and drawn cautious inferences (Bloomberg, 2022; Eurogamer, 2022). The publicly defensible observations are:

Persistent "RAGE Technology" branding. Listings from Rockstar San Diego have referenced "RAGE Technology Group" or equivalent phrasing across multiple years, indicating that the engine's identity has not been retired or rebranded.
Specialised rendering roles. Listings have referenced ray-tracing-adjacent skills (BVH acceleration structures, denoising), GPU-driven rendering, and modern shading-language proficiency — all consistent with a renderer being upgraded to current-generation console capabilities rather than rewritten from scratch.
Streaming and world-simulation roles at North. Edinburgh listings have continued to advertise for engineers with expertise in large open-world streaming, suggesting that the simulation backbone is being extended (more density, more concurrent agents) rather than replaced.
Animation and character technology at San Diego and elsewhere. The Euphoria lineage is not advertised under that brand, but listings asking for procedural-animation, IK, and physics-driven character work have been visible.
Tools and pipeline roles distributed across studios. This is the strongest single piece of public evidence for federated ownership: identical or near-identical "Tools Programmer" descriptions have appeared at North, San Diego, and Toronto, with subtle differences indicating local specialisations.

None of these listings, individually, prove anything about GTA VI. Collectively, however, they describe an engine team that is recognisably continuous with the one that shipped RDR2, augmented rather than replaced.

Major Version Bump vs Incremental Fork

The most-discussed public question in technical-press analysis after the 2022 leak was whether the engine seen in the captured clips represented a "new RAGE" — a major version bump with substantial architectural change — or a fork from the Red Dead Redemption 2 codebase with additive improvements.

The available public evidence is consistent with the latter being more likely, though the former cannot be ruled out:

In favour of incremental fork. The federated studio structure described above tends to discourage clean breaks: every studio committing to a shared engine has a strong incentive to preserve API continuity. Rockstar has never publicly versioned RAGE in marketing terms (there is no "RAGE 2.0" branding), which is itself suggestive of an ongoing trunk rather than discrete major versions. Digital Foundry's analysis of RDR2 explicitly framed that title's engine as an evolution from GTA V with substantial renderer rework, not a rewrite (Digital Foundry, 2018). The same outlet's general pattern of analysis would suggest GTA VI sits at the next step of that same evolution.
In favour of a major version bump. Generational hardware transitions — PlayStation 5 and Xbox Series X|S — provide a natural moment to retire legacy assumptions (last-gen memory budgets, lack of hardware ray tracing, slower storage). Job listings referencing modern GPU-driven rendering and BVH work are consistent with substantial subsystem replacement, which at some point becomes indistinguishable from a major version change.

The most defensible public-reporting framing is therefore: GTA VI's engine is best described as a continuation of the RAGE lineage, with a renderer and streaming layer that have been substantially rewritten for current-generation hardware, while higher-level systems (character behaviour, mission scripting, world simulation) likely retain considerable continuity with RDR2. This is consistent with Bloomberg's broader reporting on the project's long development arc and on Rockstar's preference for incremental technology investment over rewrite cycles (Bloomberg, 2022).

Cross-Studio Codebase Sharing

The federated picture of engine ownership has implications for how a code leak should be interpreted in public terms. If RAGE is a shared trunk to which multiple studios commit, then the codebase exposed by the 2022 incident would have been recognisable not only to GTA VI's direct team at Rockstar North but to engineers at San Diego, Toronto, and elsewhere. Public reporting on Rockstar's response to the leak emphasised the breadth of the internal disruption, with senior staff across the network reported to have been involved in the investigation (Bloomberg, 2022). This is consistent with a shared-codebase model.

Cross-studio sharing also explains why technical journalists were cautious about reading the leaked clips as definitive evidence of any specific GTA VI feature: the tooling visible in the clips was, by the consensus of mainstream coverage, the same tooling that had been used at Rockstar for years, with incremental UI changes. The presence of familiar debug overlays and naming conventions argues for continuity rather than reinvention (Eurogamer, 2022; Kotaku, 2022).

From a project-management standpoint, the public record also indicates that Rockstar has consolidated multiple studios under the "Rockstar Games" unified branding (the older studio-specific suffixes have been progressively de-emphasised in credits). This branding change does not, in itself, indicate any technical change, but it is consistent with a single shared engineering culture across what were once more independent studios.

Speculation Confidence

The following confidence ratings apply to the more speculative claims in this report. All technical specifics from the 2022 leak itself remain out of scope.

RAGE is a continuous lineage, not a discrete-versioned product (High confidence). Multiple independent public sources — Wikipedia's general-reference article, Digital Foundry's technical breakdowns, and the absence of any "RAGE 2" marketing — converge on this view.
Euphoria remains in use under Take-Two's ownership of NaturalMotion (High confidence). Corporate-level public reporting on the 2014 acquisition and subsequent trade coverage of RDR2 both support this.
Bullet's role has diminished but a descendant of its early integration likely persists (Medium confidence). Public sources confirm historic use; current use is inferred from the lack of any reported replacement and the general industry preference for evolving rather than replacing core physics.
Scaleform has been replaced by an in-house or alternative UI layer (Medium confidence). Inferred from Autodesk's 2018 discontinuation of active Scaleform development and from the shape of Rockstar's UI-programmer job listings, but no Rockstar source has explicitly confirmed a replacement.
Rockstar San Diego retains primary stewardship of the engine core (Medium-High confidence). Job-listing analysis and the studio's historical role both support this; absence of explicit public confirmation prevents a higher rating.
Rockstar North leads on world-simulation and streaming for GTA VI (Medium confidence). Consistent with the studio's lead role on the GTA series and with its job-listing patterns.
Rockstar Toronto plays a contributing engine role (Lower-Medium confidence). Job listings support this but do not specify the scope.
GTA VI represents an incremental fork from the RDR2 engine branch rather than a clean major version bump (Speculative — labelled). This is the most plausible reading of public evidence, but it is a judgement based on circumstantial signals (federated studio structure, listing patterns, Digital Foundry's framing of RDR2) rather than any direct statement from Rockstar. A reasonable alternative view — that the current-generation hardware transition has been used as the moment for a substantial architectural reset of the renderer and streaming layer — cannot be ruled out from public sources.
The leaked tooling shown publicly is recognisably continuous with RDR2-era Rockstar tooling (Medium confidence, public reporting only). This rests on mainstream press summaries rather than direct technical analysis, and is included here only at the level at which it was reported in the trade press.

References

Bloomberg, 2022. Rockstar Games confirms hack as GTA 6 footage leaks online. Bloomberg News, 19 September.

Bullet Physics, n.d. Bullet Physics SDK — credits and adopters. Available at: https://pybullet.org/ [Accessed via public-reporting summaries; not used as a primary technical source].

Digital Foundry, 2015. Grand Theft Auto V PC: the Digital Foundry tech analysis. Eurogamer / Digital Foundry, April.

Digital Foundry, 2018. Red Dead Redemption 2: the complete Digital Foundry tech review. Eurogamer / Digital Foundry, November.

Edge, 2013. Inside Rockstar North — the making of Grand Theft Auto V. Edge magazine feature.

Eurogamer, 2018. Red Dead Redemption 2 and the long road from RAGE. Eurogamer feature article.

Eurogamer, 2022. What the GTA 6 leak tells us — and what it doesn't. Eurogamer news analysis, September.

Kotaku, 2018. Inside Rockstar San Diego's role in Red Dead Redemption 2. Kotaku feature.

Kotaku, 2022. The GTA 6 leak, explained. Kotaku news analysis, September.

Reuters, 2014. Take-Two acquires NaturalMotion in $11m deal. Reuters business wire, January.

Rockstar Games Careers, archived listings. Various job postings from Rockstar North, Rockstar San Diego, and Rockstar Toronto, archived via the Internet Archive's Wayback Machine, 2015–2022.

Wikipedia, 2024a. Rockstar Advanced Game Engine. Wikipedia general-reference article.

Wikipedia, 2024b. Rockstar Games — studios and structure. Wikipedia general-reference article.

Wikipedia, 2024c. Euphoria (software). Wikipedia general-reference article.

Wikipedia, 2024d. Scaleform GFx. Wikipedia general-reference article.