What Is the REX Project? Capcom’s Six RE: Subsystems Explained

The short version: what REX is

Capcom builds its own engine, does not licence it, and has shipped it across Resident Evil, Monster Hunter, Devil May Cry, Street Fighter and Dragon’s Dogma. The REX Project is the company’s internal programme for changing how that engine is used to make games.

The distinction between making and running matters throughout this page. RE Engine’s rendering behaviour, the way it handles light, materials and performance, was not what Capcom announced a change to. What it announced was work on the systems that surround the renderer: how designs are written down, how the editor behaves, what telemetry the studio collects, how builds and tests are orchestrated, and how engineers get at the underlying C++.

That is a less dramatic claim than “Capcom’s engine is now AI”, and it is the claim the company actually made.

The six subsystems, one at a time

Each of the headings below is our reading of a name Capcom has published but not documented. Where we are inferring, we say so.

Every row in the middle column is inference from a name, and that is the difference between what Capcom said and what most writing about it claims. Trade coverage from 3 October 2026 describes the programme as a whole and adds no per-subsystem detail, so no row here carries a Reported label.

RE:Dox, living design documents

“Dox” reads as documents, and “living” is the operative word. Game design documentation in a large studio is a pile of files that goes stale the moment the game changes, and the gap between what a document says and what the build does is a persistent source of waste.

A system that keeps specification and implementation in step is the kind of unglamorous infrastructure that pays for itself quietly. It is also a natural place to apply generation: turning a structured design intent into a scaffold, or diffing a design document against what is actually in the build. That is inference from the name.

RE:UI, the editor and tooling surface

Every engine has an editor, and the editor is where most of a studio’s day is spent. RE:UI reads as the surface where those tools live. If a generation capability is going to reach artists and designers rather than only engineers, this is the door it walks through.

Expect this to be the subsystem where any visible generation features appear first, because it is where humans and the pipeline meet.

RE:Log, structured telemetry

Studios generate enormous amounts of diagnostic data from builds and playtests, and most of it is read by nobody because reading it is a full-time job. “Log” plus “structured” implies data captured in a shape that can be queried rather than grepped.

This is the least glamorous name on the list and, for anyone who has worked in production, one of the most plausible. It is also a precondition for automating testing: you cannot judge a build automatically if you cannot measure it automatically.

RE:Flows, automated test and build paths

“Flows” suggests orchestration: the sequence of steps from a change to a validated build. Automating that is the difference between testing a level twice a week and testing it twenty times a day.

If REX has an economically measurable payoff, this is where it lives. Iteration count is the variable that most directly converts engineering investment into a better game.

RE:Runtime, what executes on target hardware

This is the first of the two names that reaches the shipped product, and it is deliberately vague. It could describe how the engine schedules work, how content streams, how AI-driven systems behave in a live scene, or how generated content is resolved at load time rather than baked.

Capcom has said nothing specific. Treat any confident account of RE:Runtime as invented until the company publishes something.

RE:C++, engine source access

Source access is an internal question first: how engineers outside the core engine team can extend the engine without forking it. It reads as a modularisation or interface story rather than a public SDK.

To be explicit, because this is a common hope: nothing in the announcement suggests that RE Engine will be licensed or distributed. The engine has never been publicly available and there is no indication that changes. See is RE Engine free?

Why this reads as a toolchain rebuild

Line the six names up against the stages of making a game and the pattern is hard to miss.

Four rows are squarely upstream. One is indirect. One is potentially player-facing. A project shaped like that is a pipeline project, and pipeline projects are judged on throughput rather than on demos, which is precisely why there is nothing to show yet.

What REX is not

Three clarifications that resolve most of the confusion in circulation:

• Not a new engine. RE Engine continues. Every subsystem is named RE: something. A successor engine would not keep the prefix.
• Not a licensing change. Nothing indicates RE Engine becomes available to third parties. It remains internal, undocumented publicly and unavailable.
• Not a graphics overhaul. Nothing in the six names concerns rendering. Capcom’s existing visual signature, photogrammetry-led realism, strong performance on modest hardware. is not what is being changed.

What is still unknown

The gaps are large enough to be worth listing rather than glossing:

• Whether any subsystem is in active use, in prototype, or still on a slide.
• What “generation” produces, and whether its output is ever shipped unreviewed. (Our strong expectation, stated as an expectation: no.)
• How the work is staffed, and whether it changes hiring in Capcom’s engine teams.
• Whether REX touches only Capcom’s internal studios or also external partners.
• What happens to the project if the games it supports do not benefit measurably.

We will keep this page as the reference for the subsystem names themselves, and update it when any of the above stops being unknown. For the sequence of announcements rather than the definitions, see

the AI plans page.

What changed on this page

• added4 Oct 2026Added the subsystem comparison table, with a labelled row for what Capcom published, what we read into each name, and what is still unknown.
• added4 Oct 2026Each subsystem now has its own anchor, so the map on the home page and the links in the table land on the right section.

Sources

1. Capcom Open Conference RE:2026 materialsCapcom · accessed 2026-10-04
2. Capcom investor relationsCapcom · accessed 2026-10-04
3. RE:2026 keynote discussion threadResetEra · published 2026-10-02 · accessed 2026-10-04
4. Capcom’s RE Engine is getting an AI overhaulEngadget · published 2026-10-03 · accessed 2026-10-04