Capcom has revealed how it plans to rebuild the engine behind Resident Evil, Monster Hunter and Street Fighter around AI — and the plan is more concrete, and stranger, than the usual “AI in games” hand-wringing. At the company’s Capcom Open Conference RE: 2026 on 2 October, programmer Satoshi Ishida laid out REX, a project to incrementally evolve the nine-year-old RE Engine for the next generation, with IGN’s translation carrying the headline claim: the goal is to transform RE Engine into an “AI-generation game engine” for “a future where we create games together with AI.”
🔍 THE BOTTOM LINE: Capcom is not putting AI art in Resident Evil — it is rebuilding its engine so that AI coding agents can work inside it, and open-sourcing components specifically so that AI can learn from them. The most consequential gaming-AI story this month is not about generated images; it’s about generated developer hours.
What REX actually is
According to GameBiz’s report from the conference, Ishida framed REX around three mounting problems: games have grown so massive that simple build-and-test cycles eat hours; Capcom’s 2,000+ developers, increasingly international, need an engine everyone can use; and “successfully integrating AI technology into development workflows has become an essential condition for streamlining future development.”
The structure of the answer is deliberately unglamorous. Rather than a new engine, Capcom is bolting incrementally named components — REX unifies data handling under shared rules with a component the company calls RE:Dox, alongside improvements to performance, tools and QA — onto the existing RE Engine that has shipped every Capcom title since 2017’s Resident Evil 7. But two details separate this from routine engine-housekeeping news. First, IGN reports that at least some REX improvements are being made open-source “for the purpose of training AI.” Second, REX unifies the entire system under “the world’s most common programming language” — a design choice the company justifies explicitly as making the engine easier for AI to understand, not just for humans to use.
An engine codebase that is deliberately legible to AI coding agents, with open-source surfaces for those agents to be trained on, is a different object from a game engine. It is closer to the agentic-infrastructure bets that Microsoft has made with Muse than to anything in a publisher’s asset pipeline.
The distinction Capcom keeps drawing: workflow, not assets
Every outlet covering the conference took care over the same boundary. Capcom has said since at least March 2026, in a shareholders meeting, that it “will not implement assets generated by AI into our games,” while planning to “proactively use it as a contributing technology to improve the efficiency and productivity of the game development process,” including in graphics, sound and programming. Polygon’s read is that Ishida’s comments leave the door open to more extensive use while remaining “primarily workflow-driven” — and The Verge notes the irony that the studio’s new game Pragmata is literally about the horrors of AI, even as the company positions the tech as its engine’s next evolutionary step.
That distinction is load-bearing, and it will be tested. Capcom’s audience has already pushed back on AI-adjacent choices this year — the producer of Resident Evil Requiem told Polygon it “meant we got the design right” after fans hated the AI-upscaled version of heroine Grace shown in Nvidia’s DLSS 5 reveal. Players can forgive tooling that speeds up QA; they punish studio-brand contamination of the product itself. Capcom’s framing keeps that line bright for now.
Why an “AI-generation engine” is a bigger claim than it sounds
Consider what “create games together with AI” means as an engineering statement. If RE Engine’s next iteration is a codebase where AI agents can safely modify builds, generate test scripts, triage QA failures and contribute tool code — with the studio maintaining review gates — then Capcom is repositioning its most strategic asset as an AI-native development platform. The open-source move compounds it: training corpora built on a production game engine that has shipped 27+ AAA titles would be, effectively, proprietary knowledge no university dataset can offer. The open-weights wave this site has tracked all year has been about models; Capcom’s move extends it to development environments.
For context on how compressed this timeline is: it was only in 2023 that generative-AI backlash in gaming hardened into policy at most studios. Capcom held that line, and has instead run toward the less visible half of the revolution. The bet is that developer-time leverage compounds invisibly while asset-generation risk is borne loudly elsewhere. Nothing in the conference record suggests their engine will write its own monsters; everything in it suggests their engine is being prepared for colleagues that are not human.
❓ FAQ
Is Capcom putting AI-generated content in its games? No — the company reiterated in March 2026 that it “will not implement assets generated by AI into our games,” and IGN’s translation of the REX presentation confirms the plan is to use AI to streamline development workflow, not to generate in-game art.
What is the REX project? A multi-year effort, unveiled at the Capcom Open Conference RE: 2026 on 2 October, to evolve the nine-year-old RE Engine for the next generation: unified data processing, better tools, faster QA, and — most notably — an architecture designed to be understood and operated by AI, with some components open-sourced specifically for AI training.
What does “AI-generation game engine” actually mean? Capcom’s own term for an engine whose workflows, languages and data formats are arranged so that AI systems can participate in development — writing tool code, running checks, streamlining QA — in a “create games together with AI” model, per The Verge’s coverage.
Why should players care if AI touches the tools and not the assets? Because it changes where development capacity comes from in the next decade. A workflow-AI engine means faster iteration and possibly better-polished games; it also reshapes what junior developer roles look like across the industry — including in New Zealand’s growing games sector, which exports talent to studios exactly like this one.
🔍 THE BOTTOM LINE
Watch the open-source component, not the slogans. If Capcom genuinely ships production-grade REX components as training surfaces for AI agents, it will have quietly made the largest single contribution to game-engine AI tooling anyone has attempted — while every rival studio’s AI debate stays stuck on whether generated art is acceptable. The strategic move is the boring one: agents in the toolchain.
📰 Sources
- GameBiz — “カプコンのゲーム開発を支える「RE ENGINE」はどう進化するのか…新プロジェクト「REX」が目指す未来” (2 October 2026)
- IGN — “Capcom Announces Plans to Transform the RE Engine Into an AI-Generation Game Engine” (3 October 2026)
- Polygon — “Resident Evil Dev Capcom Plans To Embrace AI In Game Development” (3 October 2026)
- The Verge — “Capcom is preparing for a ‘future where we create games together with AI’” (3 October 2026)
