Capcom's REX Project Will Turn RE Engine Into an AI-Assisted Game Engine

CapcomAIGame DevelopmentIndustry

RE Engine has quietly become one of the most important pieces of technology in modern gaming, running everything from Resident Evil Village to Monster Hunter Wilds. Now Capcom wants to rebuild it from the inside out. At its Capcom Open Conference RE:2026 event in Tokyo on October 2, programmer Satoshi Ishida detailed REX — short for RE neXt Engine — a multi-year plan to turn RE Engine into what Capcom is calling an “AI-generation game engine.” It’s a rare, detailed look at how a major Japanese publisher plans to fold AI into its core technology, and Capcom was just as specific about where it intends to stop.

Five programs, one engine

REX isn’t a single feature but a cluster of interconnected tools, each targeting a different pain point in modern AAA development. Capcom has named five of them so far: RE:Dox, a data-handling library that converts formats like JSON, XML, CSV, and TOML into a common internal structure so different tools can read and edit the same data without constant reformatting; RE:UI, which lightens the engine’s development tools by separating how they look from the state they track, cutting memory overhead; RE:Log, which centralizes logging and telemetry into a single searchable store instead of scattered output files; RE:Flows, a visual scripting tool that lets designers build gameplay logic and have it automatically converted into standard code; and RE:Runtime, aimed at efficiently animating and managing large numbers of characters and objects at once.

The common thread is automation aimed at the tools developers use to make games, not the games themselves. Capcom’s pitch is that data management and debugging have become a genuine bottleneck on projects as large as Monster Hunter Wilds or the upcoming Resident Evil Requiem, and that AI and machine-learning techniques can speed up those unglamorous but time-consuming parts of production.

Open-sourcing the first piece

Capcom didn’t just describe REX in a slide deck — it backed up the announcement by publishing RE:Dox’s source code on GitHub under the Apache 2.0 license, in a new CAPCOM-TD-OSS organization. The library already supports reading, editing, and converting between nine structured-data formats, including JSON5, CBOR, and MessagePack, with Capcom citing internal benchmarks showing faster processing and lower memory use than the tools it replaces. Capcom has flagged that RE:Dox is still under active development, with its APIs and supported formats likely to change before a first stable release — but making any of its proprietary engine tooling public at all is a notable step for a publisher that has historically kept RE Engine entirely in-house.

The line Capcom says it won’t cross

The REX announcement arrives alongside a restatement of a position Capcom first laid out at its March 2026 shareholders meeting: “We will not implement assets generated by AI into our games.” That distinction matters, because it draws a sharp line between the two very different things “AI in game development” can mean. REX is explicitly about the first kind — AI accelerating the plumbing of development, like data conversion, tool performance, and debugging — rather than the second, AI generating the art, animation, or writing that players actually see and hear in a finished Capcom game.

It’s a distinction the rest of the industry has struggled to communicate clearly, and Capcom’s framing of REX as an engine that assists developers rather than replaces their output gives it a cleaner answer than most publishers have offered when asked how AI fits into their pipelines.

Why it matters beyond Capcom

RE Engine isn’t a niche tool — it’s the foundation under nearly every major Capcom release of the past several years, from Resident Evil 2’s remake onward, and its performance and tooling choices ripple across dozens of development teams working on it simultaneously. A multi-year, publicly documented plan to re-architect that engine around AI-assisted tooling, backed by an actual open-source release rather than just an announcement, gives the rest of the industry a concrete example to react to — and sets a benchmark other engine teams weighing similar bets will likely be measured against.

Capcom says REX will keep rolling out in stages rather than arriving all at once, with more of its six total planned programs expected to be detailed as development continues through the Open Conference’s Osaka leg on October 17 and 18.


For more on how the rest of the industry is approaching this same question, see our earlier look at AI adoption across game development, where just over half of studios reported using generative AI in production. Capcom’s own hardware ambitions tie into broader industry pressure, too — see our coverage of the memory shortage reshaping game hardware pricing this year.