What’s in Capcom’s Next-Generation RE Engine?

What Capcom actually said

The announcement is one sentence long. At its Open Conference RE:2026 on 2 October 2026, Capcom said it will evolve RE Engine into an “AI generation engine” as part of the REX Project. “Evolve” is Capcom’s verb. Capcom has not said the engine is being replaced, and no new engine has been named.

The six names are RE:Dox (living design documents), RE:UI (editor and tooling surface), RE:Log (structured telemetry), RE:Flows (automated test and build paths), RE:Runtime (ship-target execution) and RE:C++ (engine source access). That is the published specification. Expected features, performance figures and release timing have come from elsewhere, which is why the announcement as it was worded is worth reading next to the coverage.

Tooling changes are not rendering changes

A renderer rewrite shows up in screenshots. A toolchain rebuild shows up in schedules. The six names read like the second kind of work: documents, an editor surface, telemetry, test paths, a ship target and source access. None of them is a lighting model, a geometry system or a frame budget.

That classification is ours and we flag it as inference. The full subsystem list is worth reading alongside it, because the names are more specific than most coverage implied, and specificity is what makes them checkable later.

Why the distinction matters: players experience rendering directly and tooling indirectly. If the next generation is a toolchain, the first visible change is not a better-looking game. It is a game that shipped on a schedule that would previously have slipped. That is a smaller promise than the headlines carried, and it is the one Capcom actually made.

Test paths and telemetry

RE:Flows covers automated test and build paths. RE:Log covers structured telemetry. Together they describe a loop: build often, test automatically, collect data, feed it back into the next build. Capcom has not said which projects use that loop, how telemetry is collected, what is retained, or who reviews it.

Automation of that kind is where the returns are easiest to argue, because repetition and regression checking are measurable. It is also where claims are easiest to overstate, because no benchmark, technical talk or sample output has been published. We can describe the shape of the loop from the names alone. We cannot tell you how well it works.

The two-year gap before the keynote suggests the work started well before it was described in public. That is inference from silence, not evidence of a start date.

How a tooling change reaches players

Players receive a delta, not an engine. The pipeline documented on this site is the mod path: a source file is referenced into a project pack, compressed into a PAK entry, and only changed blocks ship. Capcom’s own tooling feeds the same kind of pipeline, though the company has not described its internals.

So a better toolchain reaches you indirectly: through what ships, how often it ships and how much of it survives contact with players. It does not arrive as a setting you can turn on, and nobody has described a runtime feature that would. If Capcom later describes content generated while a game is running, that would be a larger claim, and it would need a different standard of proof.

What stays the same

Three things are provable from the public record. The engine is in-house and stays in-house: Capcom does not license, sell or distribute RE Engine, there is no public SDK, no download and no free tier. Existing games are unaffected, because no released title has been promised an update, a patch or a migration. And the name is unchanged, with no version number announced, which is why we keep “next-generation RE Engine” in quotation marks.

For what the engine is today, see what RE Engine is. For what a public licence looks like, how a licensed engine compares sets out the difference: Unreal publishes its terms, Capcom publishes nothing, and that gap is a decision about distribution rather than a comment on quality.

The shipped catalogue is the other constant. Resident Evil 7 arrived on the engine in 2017, followed by the Resident Evil remakes, Village, Monster Hunter Rise, Monster Hunter Wilds, Devil May Cry 5, Street Fighter 6, Dragon’s Dogma 2 and Pragmata. None of that changes because the tooling does.

What we do not know

What would change this page: a technical talk with numbers, a named title, or a public document. Until one of those exists, the tooling reading is the best-supported one available, because it is the only reading built from Capcom’s own words.