Capcom used its own stage to say something no major Japanese publisher has said out loud before: its flagship game engine is being rebuilt around artificial intelligence. At the Capcom Open Conference RE: 2026, held on October 2, 2026, the company laid out plans to evolve its in-house RE Engine into what it calls an “AI-generation game engine,” a phrase that is already circulating across outlets including PC Gamer.

The announcement did not come with a shipping date or a product name on a box. It came from a programmer standing in front of a slide deck, describing a six-part internal initiative called REX. But for an industry that has spent two years arguing about where AI fits in game development, a studio behind Resident Evil, Monster Hunter, and Street Fighter just drew a public line in the sand, and the line is more nuanced than the headline suggests.

What Capcom Actually Announced on October 2

The news broke out of a single conference session. Satoshi Ishida, a Capcom programmer, presented a talk titled “The Outlook and Future of the REX Project, Further Evolving the RE Engine for the Next Generation.” The session covered Capcom’s roadmap for RE Engine, the proprietary tool the studio has used since 2017 to build nearly every major release in its catalog.

Ishida’s framing was deliberately incremental. Capcom is not scrapping RE Engine and starting over. According to the company’s own 2025 integrated report, “rather than completely replacing RE ENGINE, we plan to evolve it step by step, integrating new technologies in line with trends in IT,” a line that predates the October reveal but sets up exactly what Ishida described on stage (source: Capcom IR).

That evolution has a name. Capcom’s annual report describes it directly: “This is why we are currently developing the next generation of our engine, REX (RE neXt Engine)” (Capcom annual report, 2025). REX is not a separate engine replacing RE Engine on a shelf somewhere. It is the next layer built on top of it, and October’s conference was the first time Capcom walked a public audience through what that layer is supposed to do.

Inside REX: Six Programs, One Engine

Reports from the conference describe REX as six distinct programs, each targeting a different weak point in modern game production. Capcom has not published a full breakdown of what each of the six covers individually, but the stated development areas span development efficiency, game performance, tooling, and quality assurance, according to the presentation.

Ishida put the motivation in blunt production terms. “REX was launched to overcome modern challenges that make triple-A games take so long to develop, including improving performance, tools, development efficiency, QA, and other aspects,” he said, in comments reported by Video Games Chronicle (archived VGC coverage). That is the quiet part of the announcement that matters more than the AI label: Capcom is treating ballooning development timelines as the actual problem, and AI tooling as one lever among several for pulling them back down.

No completion date was given for REX. No price tag, no hardware target, no performance benchmark. Capcom described direction, not delivery, and that distinction should frame everything else in this story.

The Programming-Language Pivot Nobody Expected

The most concrete technical detail to come out of the conference was not about AI at all. It was about syntax. Capcom plans to unify RE Engine’s systems under what the company describes as the “world’s most common programming language.” Capcom did not name the language on stage, and no outlet covering the event has confirmed which one it is, so treat any specific guess as speculation rather than fact.

The reasoning, though, is explicit and tied directly to the AI angle. Ishida connected the language change to machine comprehension: “Because the REX project will use a more common programming language, it will make development easier for AI to understand, allowing it to automatically create programs and run test plays to check for bugs in the future,” he told the conference, per VGC’s report (source).

Read that sentence carefully and the strategy clicks into place. Large language models write far better code in widely used, well-documented languages than in a studio’s bespoke proprietary dialect, simply because there is more training data to draw from. If RE Engine’s internals currently run on something niche or heavily customized, swapping toward a mainstream language is less a creative choice and more a prerequisite for every AI-assisted workflow Capcom wants to build next.

What “AI-Generation Game Engine” Does Not Mean

The phrase Ishida used to summarize the project, an “AI-generation game engine,” is doing a lot of work in headlines right now, and it is worth separating what Capcom confirmed from what readers might assume. The reported future capabilities are about AI understanding and writing programs, running test plays automatically, and checking for bugs. Nothing in the conference coverage establishes that REX will generate complete games or automatically produce finished art, character models, or other game assets.

Capcom has in fact gone the opposite direction on that specific point, and recently. Referencing the company’s March 2026 shareholders meeting, a statement attributed to Capcom read: “We will not implement assets generated by AI into our games,” as reported by IGN Nordic (IGN Nordic). That is a company trying to have it both ways in a defensible way: embrace AI as a production and QA accelerant internally, while keeping a hard line against AI-generated art, animation, or writing showing up in a finished Resident Evil or Monster Hunter release.

Whether that line holds for years is an open question. But as of October 2026, Capcom’s own public position draws a sharp boundary between tooling and output, and that boundary is the single most important nuance missing from most headline treatments of this story.

RE Engine’s Track Record Explains Why This Matters

RE Engine is not a side project. Since its debut, it has become one of the most consistently used proprietary engines in the industry, powering Capcom’s biggest franchises across nearly a decade of releases, from survival horror to open-world action to fighting games. A studio retooling an engine with that footprint is a different story than a mid-size developer bolting AI features onto a one-off title.

That history also explains Capcom’s “evolve, don’t replace” posture. Rewriting a battle-tested engine from scratch risks years of regressions across a release slate that spans multiple genres and platforms. Layering REX on top, with a staged language migration and six discrete improvement tracks, is a hedge against breaking what already works while still chasing the AI tooling wave the rest of the industry is riding.

RE Engine’s AI Pivot, Milestone by Milestone

Milestone Detail Source
RE Engine debut era Capcom’s in-house engine becomes the standard tool across its major franchises Capcom IR
Oct. 2, 2026 Capcom Open Conference RE: 2026 held; REX project publicly detailed for the first time Conference reports
REX scope confirmed Six programs targeting dev efficiency, performance, tools, and QA Conference reports
Language unification (planned) RE Engine systems to move to a single, widely used programming language Ishida presentation
AI-assisted QA (future goal) Automatic test plays and bug checks described as a future capability, not a shipped feature Ishida presentation
Public tooling (planned) Capcom plans to release some technologies publicly online to support AI training Conference reports
AI assets (company policy) Capcom states it will not put AI-generated assets into its games Shareholders meeting, March 2026

How Capcom’s AI Bet Compares to Unity and Unreal

Capcom is not the first engine maker to talk about AI, but it may be the first major Japanese publisher to frame its own proprietary engine explicitly around AI-assisted code generation and QA. The comparison to the two engines that dominate the rest of the industry, Unity and Epic’s Unreal Engine, is instructive mostly for how differently each company is positioned.

Shattered.io has previously covered Epic’s market lead over Unity in engine adoption, reporting Epic holding roughly 42% share against Unity’s 30% following the Unreal Engine 6 rollout. Both of those engines serve thousands of third-party studios and have to build AI tooling that works across wildly different codebases and art pipelines. RE Engine answers to exactly one customer: Capcom’s own internal teams. That narrower scope is Capcom’s advantage. It can tie AI tooling directly to its own production pain points, like QA cycles and performance tuning on specific titles, without needing to generalize for an external developer base.

Engine Maker AI development focus (as publicly stated) Primary user base
RE Engine / REX Capcom AI-assisted code generation, automated test plays, bug checking; no AI-generated game assets Internal Capcom studios only
Unreal Engine Epic Games Broader engine AI and rendering tooling, evolving across major version releases Thousands of third-party studios
Unity Unity Technologies Engine-wide tooling updates positioned against Unreal’s roadmap Thousands of third-party studios, including mobile-first developers

For deeper specs on how the two market leaders stack up against each other, Shattered.io’s Unreal Engine vs. Unity vs. Godot comparison and the Unity 7 roadmap coverage go into engine-level detail that sits outside Capcom’s announcement. What Capcom’s REX reveal adds to that picture is a third model entirely: a closed, single-publisher engine using AI to compress its own production timeline rather than to sell tooling to outside studios.

Why Now: The Triple-A Development Time Problem

Ishida’s own framing puts the REX project squarely inside a problem the whole industry has been complaining about for years: triple-A games take too long to make. Development cycles for big-budget titles have stretched from roughly two to three years a decade ago toward four, five, or more years for some flagship releases, driven by growing asset counts, larger open worlds, and QA matrices that have to cover more hardware configurations than ever.

Capcom’s own release cadence shows the tension. The studio has managed to ship across multiple franchises on RE Engine at a pace that is fast by industry standards, but every additional platform, every added performance mode, and every new engine feature multiplies QA load. Automated test plays and AI-assisted bug checking, even in an early or limited form, directly attack that specific bottleneck rather than the flashier, more controversial problem of AI-generated art or writing.

That is also why Capcom’s decision to keep AI out of final game assets reads as pragmatic rather than purely ethical. Automating QA and internal tooling has a much smaller blast radius than automating the creative output players actually see and judge. It is the lower-risk half of the AI adoption curve, and Capcom chose to announce that half first, publicly, with a named engineer standing behind it.

REX’s Architecture, in Plain Terms

Based on the conference reporting, REX can be thought of as a layered rework sitting on top of the existing RE Engine runtime rather than a ground-up rebuild. A simplified view of how the pieces reportedly relate looks like this:

RE Engine (existing runtime, since 2017)
  └── REX layer (next-generation evolution, announced Oct. 2, 2026)
        ├── Program 1-6: efficiency, performance, tools, QA (exact split undisclosed)
        ├── Language unification: move to a widely used programming language
        ├── AI-assisted authoring: future goal, not yet shipped
        └── AI-assisted QA: automated test plays and bug checks, future goal

That structure explains why Capcom is comfortable calling this an evolution rather than a relaunch. Studios keep shipping on the current RE Engine while REX’s six programs mature individually, and the language migration can roll out incrementally across systems rather than all at once.

Public Tooling: Capcom’s Unusual Offer to the Industry

One of the more unexpected details from the conference is that Capcom plans to make some of REX’s underlying technologies publicly available online specifically to support AI training. Capcom has not detailed which tools, in what format, or on what timeline. But the intent alone is notable for a company that has historically kept RE Engine entirely proprietary and in-house.

If Capcom follows through, it would put the publisher in an unusual middle ground between studios that keep every engine detail locked down and engine makers like Epic and Unity that build businesses around external developer access. Capcom is not opening RE Engine itself to outside studios. It is floating the idea of opening specific pieces, likely code samples or documentation, so that AI models (its own or third-party) have better material to train on when assisting with RE Engine-style development patterns.

Market and Industry Reaction

Reaction across outlets covering the conference has focused heavily on the “AI-generation game engine” phrase itself, with PC Gamer flagging it as one of the most discussed gaming stories coming out of the announcement. That framing has produced some predictable friction: parts of the gaming community read any AI-and-game-development headline as a signal of incoming AI-generated content, and Capcom’s no-AI-assets statement is doing real work to contain that reaction.

Investors and industry trackers, by contrast, are likely to read the announcement through the development-cost lens rather than the creative-ethics one. A publisher the size of Capcom publicly tying an engine overhaul to reduced QA and tooling overhead is the kind of efficiency story that tends to matter more to a balance sheet than to a message board, even when the message boards get louder.

Risks and Open Questions

Plenty can still go wrong or simply take longer than hoped. Migrating a mature, decade-old engine to a new core programming language is a multi-year undertaking even without an AI component layered on top, and Capcom has not given any completion date for REX as a whole. Large internal engine migrations have a long history of slipping, at Capcom and everywhere else.

There is also a credibility gap between “AI can run automated test plays” as a stated goal and AI actually doing that reliably across Capcom’s full catalog of genres, from horror to fighting games to open-world action, each with different test coverage needs. Nothing in the October reporting confirms REX has shipped a working version of that capability yet. Capcom describes it as a future outcome, not a current feature.

Finally, Capcom’s promise to keep AI out of finished game assets is a policy, not a technical constraint. Policies can change, especially over a multi-year rollout, and the company has given itself room to redefine “assets” narrowly if AI-assisted tooling starts producing content that blurs the line between a QA aid and a shipped game element.

Predictions: Where REX Goes From Here

  • Capcom will likely confirm the target programming language for REX within the next one to two major financial reporting cycles, given how central that detail is to the rest of the plan.
  • Expect Capcom to showcase REX progress incrementally at future Capcom Open Conference events rather than in one big reveal, mirroring the “evolve step by step” language from its 2025 integrated report.
  • Automated QA and test-play tooling will almost certainly ship before any AI-assisted authoring tools reach developer hands internally, since QA carries far less creative and legal risk.
  • Competing Japanese publishers with large internal engines are likely to face pressure to clarify their own AI tooling stance, now that Capcom has set a public reference point.
  • If Capcom does release REX-related technology publicly, expect it to be narrow, such as documentation or limited code samples, rather than an open-source release of RE Engine itself.

What This Means for Players

For players, the most important takeaway is the one Capcom stated directly: nothing about REX changes what ends up in a Resident Evil, Monster Hunter, or Street Fighter release in terms of AI-generated art or writing, at least under the company’s current policy. The visible effect, if REX delivers on its stated goals, would show up indirectly, in shorter development cycles, fewer post-launch patches for QA-catchable bugs, and potentially faster cross-platform ports as tooling improves.

None of that is guaranteed on any specific timeline. Capcom gave a direction at Capcom Open Conference RE: 2026, not a release date, and the gap between the two is exactly where this story will keep developing over the next year.

Frequently Asked Questions

What is Capcom’s REX project?
REX, short for RE neXt Engine, is Capcom’s internal initiative to evolve its RE Engine with six programs aimed at improving development efficiency, performance, tooling, and quality assurance, as detailed at Capcom Open Conference RE: 2026 on October 2, 2026.

Is Capcom replacing RE Engine entirely?
No. Capcom has stated it plans to evolve RE Engine step by step rather than replace it outright, with REX layered on top of the existing engine.

Will Capcom use AI to generate game assets like characters or art?
Capcom has stated it will not implement AI-generated assets into its games, a position reiterated around its March 2026 shareholders meeting.

What programming language will REX use?
Capcom has described it only as the “world’s most common programming language” without naming it publicly. No outlet covering the conference has confirmed the specific language.

When will REX be finished?
Capcom has not given a completion date, launch date, or version number for REX. The project was described in terms of direction and ongoing evolution, not a fixed release schedule.

Who presented the REX project at Capcom’s conference?
Satoshi Ishida, a Capcom programmer, presented the session “The Outlook and Future of the REX Project, Further Evolving the RE Engine for the Next Generation” at Capcom Open Conference RE: 2026.

Will Capcom release any REX technology publicly?
Capcom has said it plans to make some technologies publicly available online to support AI training, though no specifics on format or timing have been announced.

How does REX compare to what Unity and Unreal are doing with AI?
Unity and Unreal Engine build AI tooling for thousands of third-party studios across varied codebases. REX is scoped narrowly to Capcom’s own internal production needs, which lets Capcom target its specific QA and tooling bottlenecks directly.