CAPCOM is turning RE Engine into REX Engine, a set of tools that could let AI read code, write software, run tests and find bugs while human teams keep making the games.
CAPCOM is preparing its game development pipeline for an "AI Generation." The company wants artificial intelligence to read engine code, write new code, run test plays and search for bugs. It is not presenting this as an automated content factory. The plan centres on REX Engine, a staged evolution of RE Engine rather than a separate replacement. IGN reported that programmer Satoshi Ishida presented REX at CAPCOM Open Conference RE:2026 on October 2. The project is meant to support AI-assisted development, testing and quality assurance over time.
REX targets development bottlenecks
Ishida outlined the project at CAPCOM Open Conference RE:2026 on October 2. His presentation tied REX to three practical problems inside CAPCOM. Games have grown so large that routine edits and checks can involve long waits. More than 2,000 developers now use the engine. The rapid growth of AI has also made machine-readable tools more useful. Conference materials describe cutting those delays as one of the main reasons for REX.
The answer is a change to the engine's structure. CAPCOM has brought the system together around the rules of the world's most common programming language. That gives developers a more consistent base and makes the code easier for AI systems to read. The planned workflow would let AI generate code from that shared base, run tests and find defects. People would still make the development decisions and approve the finished game. GameBiz reported that the common rules are meant to improve readability for both developers and AI systems.
The presentation did not describe AI-generated art, characters, environments or other game assets. CAPCOM's announced uses are internal tools: code assistance, automated testing, log translation and quality assurance. Ishida described the long-term goal as a future in which teams "create games together with AI." So far, the material is about the production pipeline, not an automated content generator.
The engine's new building blocks
RE:Dox converts different data formats into a common rule set. CAPCOM says this has improved loading speed and made data easier to edit. RE:UI deals with the company's internal tools. Those tools had become slow, prone to freezing and limited to Windows. RE:UI separates an interface element's appearance from its state. One checkbox design can then serve many instances, while the screen redraws only after a change.
That separation gives automated testing a cleaner path through the development tools. RE:Log replaces text-heavy logging with compact identification numbers. The system retrieves the wording when a message appears. Developers can revise messages without changing code, translate them for overseas staff and store them in compressed form on a central server. The wider team can search and analyse them there.
RE:Flows gives designers a visual scripting environment. Behind the scenes, it translates their work into a standard programming language. RE:Runtime handles the game-facing foundation. It turns human-friendly code into RE:C++ for speed and manages objects in fixed-size batches instead of one at a time. Eurogamer's account of the presentation identifies these systems as parts of the wider REX architecture. RE:Dox handles standardised data. RE:UI covers internal tools. RE:Log uses ID-based logging. RE:Flows handles visual scripting. RE:Runtime and RE:C++ deal with runtime processing and batch execution. The changes are meant to help CAPCOM handle large numbers of characters and creatures.
What players may notice
RE:Runtime is the part most likely to affect games on screen. CAPCOM did not tie the technology to a specific title or promise a fix for an existing performance problem. The design could matter in CPU-heavy scenes with dense crowds or large creature populations. That makes the crowded cities in Dragon's Dogma 2 and Monster Hunter Wilds on PC obvious reference points. It does not show that REX will fix either game's known issues.
CAPCOM has not said when the individual REX components will be used across upcoming releases. The company has not provided measured frame-rate results, loading comparisons or platform-specific performance data either. Readers should treat REX as a development plan with possible benefits for players, not as a delivered performance upgrade. As Eurogamer reported in early October 2026, the presentation described a technology roadmap and gradual integration into the existing pipeline. It did not announce a new commercial product.
CAPCOM has open-sourced some REX technologies, including RE:Dox and RE:Log, and published them online. Japanese website GameBiz reported that making those systems useful for AI training is part of the objective. That adds context to CAPCOM's approach. It does not mean the wider REX vision is already a finished production system.
Why RE Engine is changing
CAPCOM began developing RE Engine in 2014. It first used the engine for Resident Evil 7: Biohazard in 2017. More than 27 CAPCOM games released since then have been built with it. A toolset that once served a smaller development operation now supports almost the entire company. It also has to serve more overseas staff and developers who arrive with experience of other engines. The Verge's background on CAPCOM's technology strategy places REX within that longer evolution. It does not present REX as a wholly separate platform.
REX is a gradual rebuild layered onto RE Engine. CAPCOM is adding technologies with the RE prefix step by step. It is not throwing out the existing engine and starting again. That lowers the risk of an abrupt transition. It also means the benefits will arrive unevenly across tools and projects instead of appearing as one finished engine upgrade.
The approach fits CAPCOM's wider technical direction. As our earlier breakdown of AI-assisted image reconstruction showed, machine learning can help without replacing the underlying game or its authored content. REX applies the same idea to the production pipeline instead of the final image.
Resident Evil Veronica is among the RE Engine projects due next year. A recent rumour claimed it will not launch until Fall. CAPCOM has not disclosed the timing of REX's rollout, so there is no confirmed link between that project and the new systems. The announcement is strongest as a statement of direction. CAPCOM wants its game teams to work with tools that can understand the engine, test changes and expose bugs faster.
That is a more grounded use of AI in game development than promises of instant machine-made worlds. REX could cut repetitive engineering and QA work while leaving art, assets and in-game content handcrafted. CAPCOM has not shown the results in a shipped game. The real test will be whether shorter development feedback loops produce more stable games and better CPU performance, rather than simply adding another layer of technical vocabulary.
Here, automated testing means software repeatedly checking a build or tool without a developer performing every step by hand. It can catch code failures quickly. It cannot replace human judgement about whether a game feels good or whether a visual result is artistically right. REX is best understood as infrastructure for faster iteration. Its value will be shown by the games and tools CAPCOM eventually delivers, not by the ambition of the presentation.
