Capcom's REX project, unveiled on October 5 (GamesIndustry.biz), wires AI into code generation, automated playtesting and performance work inside RE Engine, with a long-term goal of an "AI-generation game engine." Capcom also says it will not ship a single AI-generated asset. Those two statements look like a contradiction. They are not. Capcom is moving AI into the parts of production players never see, while locking down the parts they do. If it works, it becomes the template every Japanese publisher copies.
一、REX Changes the Pipeline, Not the Picture
At Capcom's annual technology conference, programmer Satoshi Ishida presented "The Outlook and Future of the REX Project, Further Evolving the RE Engine for the Next Generation." The stated goals are unglamorous: accelerate development, improve QA efficiency, make the toolkit easier for new and international staff, and integrate AI into the production workflow.
Six modules, all plumbing
The announced systems are RE:Dox for standardised data processing, RE:UI for faster toolkit development, RE:Log for ID-based logging, plus the visual scripting tool RE:Flows, a reworked runtime core RE:Runtime, and a refined execution framework RE:C++.
Not one of these names has anything to do with art direction. That is the tell.
What the AI actually does
Ishida listed four jobs: assist development, generate and interpret code, automate playtesting to catch bugs, and optimise performance. His framing was that developers will "create games together with AI." Automated playtesting is the line worth circling. It points directly at QA hours.
二、Two Thousand Developers Share One Engine
Capcom began building RE Engine in 2014 to make Resident Evil 7, which shipped in 2017. GamesIndustry.biz, citing Eurogamer, puts the number of developers using the engine at more than 2,000.
That number explains the strategy. RE Engine is not one game's tech stack; it is the company's production standard. Improvements compound across every team, and so do mistakes. Which is precisely why Capcom is upgrading logging, data and code layers instead of touching character faces.
三、Capcom's Red Line: Generate Code, Never Assets
At its March shareholder meeting, Capcom stated it "will not implement any generative AI assets" into its games, and that the technology is for improving "efficiency and productivity in game development." The company said it was testing uses across graphics, sound and programming departments, as reported by GamesIndustry.biz on March 24.
The DLSS 5 backlash explains the line
Resident Evil Requiem appeared in an Nvidia DLSS 5 tech demo, and the AI-enhanced model of protagonist Grace Ashcroft drew criticism. Players were not angry that AI existed. They were angry that it touched a character's face.
So Capcom drew the border in the least visible place: assets stay human, pipelines get automated.
四、The Same Week, Someone Open-Sourced the Alternative
On October 15, DayZ creator Dean Hall released Brutal, an open-source development framework built in C#. It is free for commercial use with no royalties; developers only keep a copyright line in the credits. Work began in 2022 and the framework is already used across six projects at three studios (GamesIndustry.biz, October 15), including RocketWerkz's Kitten Space Adventure and the Waylith engine powering Ludeon Studios' Rimworld.
Hall's argument is sharper than any analyst note
In a long Reddit post, Hall said Unity and Unreal have "consistently failed to be held accountable to developers." His worry is forward-looking: as agentic workflows erode the competitive advantages that protected established software companies, "the companies involved will increasingly look to extract more revenue from developers who feel they cannot switch. Whether through royalties, subscriptions, or more restrictive licensing."
He added a line aimed at himself: if his own team ever stops being accountable, developers should be able to fork the framework and walk away.
五、The Real Risk Isn't Art. It's Jobs.
Put Capcom and Dean Hall side by side and you get two ends of the same argument. One studio is pulling AI into a proprietary pipeline to cut cost. One veteran is open-sourcing the pipeline so nobody can be held hostage by it.
For working developers, the near-term change is not whether AI draws well. It is the shape of QA and tools roles. Once automated playtesting is reliable, the first headcount to shrink is repetitive test labour, not concept art. Almost nobody in the public debate mentions this.
六、Why This Turn Is Worth Recording
For two years, the industry's AI argument has been almost entirely about whether an asset was generated. Capcom is offering a different sample: automate the invisible, protect the visible.
Whether that holds depends on two testable things. First, whether automated defect detection actually beats human coverage. Second, whether players accept a game that was debugged by machines but drawn by people. If both hold, more Japanese publishers will follow. If not, REX becomes an expensive internal slide deck.
We will keep tracking engine and toolchain news in GameHub's industry feed, with links to the original technical talks.
七、FAQ
Is a Capcom game built with AI now an "AI game"?
A: By Capcom's own definition, no. The company ruled out generative AI assets in March, and REX covers code, logs, automated playtesting and performance optimisation, all inside the tooling layer.
How many developers use RE Engine?
A: GamesIndustry.biz, citing Eurogamer, estimates more than 2,000. At that scale, an engine change lands on nearly every project Capcom has in development at once.
How is Brutal different from Unity or Unreal?
A: Brutal is an open-source framework, not a full engine. It is written in C#, royalty-free, and can be used to ship a game directly or to build your own engine, which is what Ludeon Studios did with Waylith.
The tools changed. The ledger did not: whoever owns the toolchain owns the split. More engine and publisher coverage is on gghubs.com.