Capcom Wants to Build AI Into the RE Engine. What 'AI Game Engine' Means Is Contested

Capcom used its own developer event on October 2, 2026 to set out how it wants to change the engine behind most of its biggest games. At the Capcom Open Conference RE: 2026, the programmer Satoshi Ishida gave a talk titled "The Outlook and Future of the REX Project, Further Evolving the RE Engine for the Next Generation." VGC reported that Capcom wants to evolve RE Engine into what it described as an AI game engine. IGN carried the goal in Capcom's words: "Our goal is a future where we create games together with AI." What the talk set out in practice was narrower than that sentence.

Related reading: Google Launches Playground, an AI Platform That Builds Playable Games From Prompts · Meta Wants You to Build a Playable Game From a Prompt on Your Phone.

RE Engine is the thing Capcom owns

RE Engine is Capcom's in-house game engine, the software layer its teams build games on. It powers Resident Evil, Monster Hunter, Street Fighter, Devil May Cry and Dragon's Dogma, and Capcom has used it across more than two dozen games. Owning the engine matters because it sets the terms on which those teams work. A studio licensing Unreal Engine or Unity absorbs the vendor's design decisions and pricing. Capcom absorbs its own. When the company changes RE Engine, its own franchises are the first test case, and there is no third party at the table.

The engine's reach also sets the stakes of a change. Every team working on those franchises depends on the same foundation, so a shift in how the engine is built reaches all of them at once. There is no partial migration for a studio that owns its own tools.

That is why an engineer's conference talk counts as news. The tooling layer is where a large publisher's costs and schedules live, even though players never see it. A change to how the engine is built can reshape how long a Resident Evil takes to make.

What REX is, per Capcom

REX is a multi-step program to improve the engine. PC Gamer reported that it involves six programs, each aimed at integrating AI and machine-learning technology into the engine. The stated goals are production goals rather than gameplay features. Capcom says REX should improve development tools, quality assurance and efficiency, and shorten the long production cycles that define big-budget games.

None of that is a product yet. A conference talk about six internal programs is a roadmap, and Capcom has not published ship dates or named a game that uses any of it. The claims worth weighing are the ones about mechanism, which describe what the technology would do.

The mechanism: code that AI can read

The clearest technical claim from the presentation is about language. Because REX would adopt a more common programming language, Capcom says the code becomes easier for AI to read and understand. That would let AI automatically create programs and run test plays to identify bugs in the future.

That is a description of engineering automation, in two parts. The first is code generation, aimed at the routine work of writing software. The second is automated playtesting, aimed at the repetitive work of finding out whether software works. Neither is a system that draws a character, writes dialogue or assembles a level. The second part, running test plays to surface bugs, is work Capcom already pays large QA teams to do by hand.

The distinction matters for how the plan gets judged. Automated playtesting is a narrower and more measurable goal than content generation. It sits closer to the existing field of software test automation than to the image and text models that dominate the AI debate. A tool that plays a build thousands of times and logs crashes is unexciting, and it can be evaluated on whether it finds bugs faster than a person does.

Notice the tense. Capcom's mechanism is framed as something that would happen in the future, once the language migration is done. The announcement describes an intention and a precondition, not a result.

The wording fight

The wording matters because the three phrases point in different directions.

"AI-generation game engine" suggests an engine that generates game content, and in 2026 that reading lands on art, voices and levels, the places where the generative-AI argument in games is hottest. "AI-era game engine" only marks a period. "AI game engine," the closest English rendering of Capcom's own phrase, could mean almost anything. Reporting on the announcement noted that the phrase is ambiguous, and that ambiguity is why the same talk produced headlines that do not quite agree with each other.

Eurogamer covered the plan under the "AI-generation" framing. So did VGC, PC Gamer and IGN in their headlines. Nintendo Life chose "AI-era." The talk was delivered in Japanese at a Japanese developer event, so the phrase reached English readers through translation and paraphrase, and different outlets resolved the ambiguity in different directions. Whether the spread is a translation artifact, an editorial choice or simply what the original phrase allows is itself disputed. What is not disputed is the mechanism Capcom described, which is narrower than "generation."

Capcom's own communication does not settle it. Ishida's talk title uses the plain word "evolving," and the phrase attributed to him, "AI game engine," is a label rather than a specification. That leaves the interpretation to whoever writes the headline, which is how one conference talk becomes several different stories.

The phrase in the headline is elastic, the capability in the body is specific, and readers remember the headline.

For Capcom, whose audience is unusually attentive to anything that sounds like generative AI, the gap between the phrase and the capability is a communications risk separate from the engineering.

Open source as a way to train the model

One detail cuts against the idea that this is only internal tooling. Capcom said it has open-sourced some technologies, including tools named RE:Dox and RE:Log, primarily as a way to train its AI. PC Gamer reported that framing.

Open source is usually pitched as giving code away. Here the stated purpose is to train Capcom's AI, which points the flow of value back toward the company that released the tools. How the training works, and what developers agree to by using the software, is not detailed in the announcement. The licensing terms would decide whether this reads as a gift to the community or a pipeline back to Capcom, and the announcement did not include them.

Art is the line Capcom keeps drawing

Capcom has tried to separate its AI plans from generative art. Its VP of game development and AI solutions has previously said the company will not use AI to create art, and that the aim is to "unlock the potential for creators." That line matters because generative art is the flashpoint. When a studio is accused of using AI art, the argument is about authorship and the value of human craft. Capcom is trying to keep REX on the tools-and-testing side of that divide, and the wording fight above is what happens when the messaging blurs the boundary.

The claim is a statement of intent, made before any product exists to test it. It also covers one category. It promises nothing about programmers or QA staff, whose work is what the described mechanism actually touches.

A backlash, and a hiring question

The announcement landed in the middle of a wider backlash to generative AI in games. A recent controversy at Level-5 is one example. Some coverage argued that the "AI-generation" framing mischaracterized a plan mostly about automation, tooling and QA, and that reading fits what Capcom described.

That ambiguity colors how the backlash reads. Readers who met the story as "AI-generation" responded to a claim Capcom did not make. Readers who met it as "AI-era" may have missed that code generation and automated testing are real changes to how games get built.

Headcount cuts the other way. GameSpot reported that Capcom is still ramping up hiring despite its interest in generative AI. That undercuts the simplest version of the story, that the technology is arriving to replace Capcom's staff. It does not answer what the automation is for, how any savings get used, or whether the hiring picture looks the same once REX produces something.

The labour question is concrete. Automated test plays target the work of QA testers. Program generation targets the routine work of junior programmers. Neither is a claim about layoffs, and neither is a promise that the people doing that work will be untouched. Capcom has described both as future capabilities, which leaves the company room to define the terms as the tools arrive. Capcom has not said how it would tell players when a game was built with AI assistance, and that gap is worth watching as closely as the engineering.

What to watch

• Deliverables. REX is six programs described in a conference talk. The test is whether Capcom ships the tools, sets dates, or names a game that uses them.
• The language migration. Adopting a more common programming language is the precondition Capcom names for everything else. Moving a codebase behind more than two dozen games is a long job, and its progress will show whether REX is a working program or an aspiration.
• A shipped title. Whether a Capcom game ships with AI-assisted code, QA or tooling, and how the company discloses it, will matter more than the announcement did.
• Hiring. GameSpot reported Capcom is still ramping up hiring. Job listings and headcount over the next few years will show where the automation ends up.
• The wording. Capcom's English communications have not settled on a phrase. Whether the company standardizes on "AI game engine," "AI-generation" or something else will shape how the plan is understood.

The plan has a name, six programs and a stated mechanism. What it produces is still ahead of it.

Cover: A screenshot from Resident Evil 4 Remake, which runs on Capcom's RE Engine. Image by Capcom France via Wikimedia Commons, CC BY 3.0.