Capcom Wants to Turn RE Engine Into an 'AI-Generation Game Engine', and Its REX Project Lays Out How

By CriticalPixel · 2026-10-03

Capcom has been on a heater for years, and now it wants its in-house engine to start thinking about AI. On October 2, at its own tech conference called Capcom Open Conference RE: 2026, programmer Satoshi Ishida laid out the future of RE Engine and used a phrase that is going to set comment sections on fire: an "AI-generation game engine." PC Gamer broke the headline to its audience, IGN followed with a longer writeup, and the details come from a Japanese report by GameBiz covering the actual talk. Before anyone grabs a pitchfork, the details are more boring and more interesting than the headline suggests.

Official Steam screenshot of Resident Evil Requiem, a Capcom game built on RE Engine

What Capcom actually announced

The talk was titled "The Outlook and Future of the REX Project, Further Evolving the RE Engine for the Next Generation," and REX is the umbrella name for a pile of upgrades Capcom is bolting onto the engine over time. Capcom is not scrapping RE Engine and starting from zero. The plan is to add new technologies named "RE:something" step by step until the engine reaches what the company calls a next-generation level. PC Gamer counts six separate programs under the REX banner, while GameBiz walks through five of them by name in its writeup of the talk.

RE:Dox is a data handling system that translates all kinds of data into one common set of rules so it loads and edits faster. RE:UI rebuilds the interface layer of the development tools so they stop freezing when a screen has thousands of widgets, and Capcom says the tools can now be tested automatically in the background. RE:Log swaps text logging for tiny ID numbers, ships every log to a central server and lets the text be translated later for overseas staff. RE:Flows lets designers build gameplay logic visually while it quietly converts everything into a standard programming language behind the scenes. RE:Runtime handles huge crowds of characters and objects in batches instead of one by one, and it translates easy-to-write code into a Capcom-specific language called RE:C++ that the machine runs very fast.

Why Capcom says it needs this

Ishida listed three problems after more than eight years with the engine. Games have grown so large that even small tweaks make developers wait. More than 2,000 people at Capcom now use RE Engine, including overseas staff and veterans from other studios, so it has to be easy and multilingual. And the third one is the line that made headlines: successfully integrating AI into development workflows has become, in Capcom's words, an essential condition for streamlining future development. For context, RE Engine started development in 2014, debuted in Resident Evil 7 in 2017, and has powered more than 27 Capcom titles since.

The glue here is a language decision. REX puts the whole system on the most widely used programming language in the world, which Capcom says is easier for humans and also easier for AI to read. Once that base is unified, the company expects AI to eventually understand the code, write some of it and even play-test builds to hunt for bugs. Capcom is also putting parts of the stack, including RE:Dox and RE:Log, out in the open as open-source, partly so the technology can help with AI learning. IGN reports it as at least some of the improvements going open-source for the purpose of training AI, which is the detail I would watch closest.

Second official Steam screenshot of Resident Evil Requiem running on Capcom RE Engine

Capcom's earlier AI promise still stands

This is not a reversal of Capcom's public line on generative AI. At a March 2026 shareholders meeting the company said it will not implement assets generated by AI into its games, while planning to use it proactively as a contributing technology to improve the efficiency and productivity of development, and it named graphics, sound and programming as areas it is exploring. Nothing in the REX talk, as reported, describes AI painting textures, writing dialogue or producing character models. The tools described are about data handling, tooling speed, code conversion, logging and testing. That is closer to the dull infrastructure work that studios have done for decades than to the chatbot-writes-your-game fantasy.

PC Gamer is blunt about the gap between the label and the reality: what Capcom appears to mean is an engine for the AI generation of workflows rather than a generative AI engine. The outlet calls RE:Flows "vibe coding-adjacent" and says it is hard to judge without seeing it in action, and it is unconvinced by the claim that AI is essential for streamlining development. I land in the same place. The branding is the problem. Calling your engine an "AI-generation game engine" in 2026, with players already exhausted by AI slop in storefronts and trailers, reads like a communications own goal even if the engineering behind it is sensible.

The track record Capcom is betting against

The timing is awkward in a different way. Capcom has shipped Resident Evil Requiem, Pragmata and Onimusha: Way of the Sword this year, all to strong reviews and sales, and the engine under them is one of the most trusted pieces of tech in the industry. Requiem alone is a showcase for how well RE Engine scales on PC. When a pipeline is delivering hit after hit, tearing at it for efficiency gains invites the old "if it ain't broke" argument that PC Gamer raises. Efficiency is a fair goal, since a 2,000 person team waiting on slow tools is expensive, but Capcom has not shown any evidence yet that the AI part will make games better rather than just cheaper.

Third official Steam screenshot of Resident Evil Requiem from Capcom

How people are reacting

Reaction so far is limited and split, and it is only a few hours old. PC Gamer's post on X drew a reply telling Capcom "DON'T YOU DARE," while other replies I read pushed back on the knee-jerk assumption that anything AI means failure. One user said they only accept it as long as Capcom keeps AI away from the creative process, and worried that putting it inside the in-house engine could be the first step toward generative AI showing up in the games themselves. With only a handful of independent reactions in hand I would not call that a consensus either way.

The CriticalPixel take

Here is where I come down. The REX material reads like genuine engineering: faster tools, cleaner data, fewer freezes, better logging, easier onboarding for a global team. If AI helps a programmer find a bug or lets a designer prototype a mechanic in an afternoon, that is a defensible use. What worries me is the direction of travel. Open-sourcing code specifically so it can feed AI training, unifying everything so machines can write it, and letting AI run play-tests are all steps that make the next step easy: more automation in places players care about. Capcom has drawn a line at AI-generated assets, and the company deserves credit for saying so in public. A line only means something if it is still there at the next shareholders meeting.

For now the sensible reading is also the least dramatic one. Capcom is modernizing a 12-year-old engine, tying the pitch to AI because every executive has to, and promising it will not touch the art. If that holds, REX is a plumbing story. If it does not, Capcom will have spent years of goodwill on a slogan. Either way, keep an eye on what gets open-sourced and what the studio says about AI in its next earnings call, because that is where the real answers will come from.