Capcom has gone public with a direct answer to one of the loudest AI controversies to hit Japanese game development this year. On October 9, 2026, iXBT.games reported that Capcom had responded to mounting criticism over its planned use of artificial intelligence in Resident Evil development, following a wave of fan and developer backlash that began earlier in the week. The statement traces back to a conference presentation about the next generation of Capcom’s RE Engine, and it lands at a moment when the studio behind Resident Evil Requiem, Monster Hunter Wilds, and Street Fighter 6 is trying to walk a narrow line between embracing AI tooling and avoiding the stigma now attached to generative AI art in big-budget games.
The short version: Capcom says it will not put AI-generated assets into its finished games, but it does plan to lean on AI to speed up the grind of building them. That distinction, drawn in a clarification to IGN and echoed across outlets covering the Japanese developer, is now the center of a fight over what “AI in game development” actually means in 2026 — and whether players, artists, and engineers are even arguing about the same thing.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What sparked the Resident Evil AI backlash
The controversy did not start with a single leak. It built over roughly a week, stacking two separate stories on top of each other until they blurred into one narrative: “Capcom is putting AI into Resident Evil.” The first thread traces to Capcom’s annual recruitment and technology event, Capcom Open Conference RE:2026, held on October 2, 2026. There, company programmer Satoshi Ishida presented a roadmap session titled “The Outlook and Future of the REX Project, Further Evolving the RE Engine for the Next Generation.” REX stands for RE neXt Engine, and it is not a ground-up replacement for the RE Engine that has powered Capcom’s biggest titles since Resident Evil 7. It is described as a gradual evolution of the same engine, built to handle larger scenes, more characters on screen, faster data handling, lighter development tooling, and — critically — a development environment meant to let AI systems and human programmers work side by side.
That framing, once it filtered through secondary coverage and social media, got compressed into shorthand like “AI-generation game engine,” which is a much more alarming phrase than “we are modernizing our internal tools.” The second thread involves Resident Evil Requiem directly. Nvidia used the game, and specifically protagonist Grace Ashcroft, in hands-on demonstrations of DLSS 5’s neural rendering technology. Coverage of those demos, including a hands-on report from Inven Global, noted that Ashcroft’s face appeared visibly altered under the new upscaling and frame-generation pipeline — smoother skin, stronger highlights, a different read on her expression than players remembered from trailers. That reporting stopped well short of claiming Capcom used generative AI to create Ashcroft’s character model, but the optics merged with the REX story anyway. By the time both threads reached a general gaming audience, the takeaway many people walked away with was that Resident Evil’s next engine, and possibly Requiem itself, would involve AI-generated character art.
That is the backdrop for the Resident Evil Requiem story line heading into its post-launch content push, and it is also tangled up with broader anxiety about Nvidia’s AI-driven rendering tools, which tech-insider.org has tracked extensively as DLSS 5 rolled out across other titles.
Capcom’s exact clarification, word for word
Capcom’s response did not come as a splashy press release. It arrived as a clarification issued after IGN asked the company directly to explain what Ishida’s REX presentation actually meant. The resulting statement, reported by IGN and reproduced by iXBT.games, reads: “We will not implement assets generated by AI into our games. However, we plan to proactively use it as a contributing technology to improve the efficiency and productivity of the game development process. To this end, we are currently exploring ways to implement it in various areas, including graphics, sound and programming,” according to Capcom’s company statement published by IGN.
That is a deliberately narrow promise. IGN reported that Capcom says REX would improve development efficiency rather than generate in-game assets, and that the company plans to test AI across three areas: graphics, sound, and programming. Capcom is not ruling out AI touching Resident Evil at any point in the pipeline, it is ruling out AI-generated output appearing in the shipped product. Debugging tools, code analysis, automated playtesting, and performance optimization are all fair game under this framing, because none of those produce an “asset” in the traditional sense. A texture painted by a generative model would violate the pledge; an AI system that flags a memory leak during a Resident Evil Requiem build would not.
Capcom has made a version of this argument before. Kotaku’s reporting on the company’s generative-AI philosophy quotes Capcom directly: “The company will not be implementing any AI-generated assets into our video game content,” according to a Game Developer report on the same briefing. Capcom’s March 23, 2026 shareholder Q&A reportedly took the same position, pairing the pledge not to implement AI-generated assets with plans to use AI as a contributing technology for development efficiency, which is why the policy is better read as a limit on shipped assets than as a ban on all AI use. The company has also said, in material reported by Kotaku, that “AI is not a replacement for humans,” according to Kotaku’s coverage. The consistency across outlets suggests this is a rehearsed company line, not an improvised walk-back.
Who is Shinichi Inoue and why his title matters
The person doing most of the public explaining is not Ishida, the engine programmer who triggered the controversy, but Shinichi Inoue, Capcom’s vice president of game development platform and AI solutions. His job title alone tells you something about how seriously Capcom is treating this: the company created a VP-level role explicitly pairing development platforms with AI solutions, which signals that AI tooling is now considered core infrastructure rather than an experimental side project.
Inoue’s public comments draw a sharper philosophical line than the brief corporate statement. “What we in the entertainment industry consider extremely important in contrast to artificial intelligence is human sensibility. Even top-tier AI still cannot match our creators when it comes to sensibility. That’s the current reality,” Inoue said, according to AI and Games. He has also been quoted more bluntly: “AI is not for Creating Art,” per the same AI and Games interview. That is a notably stronger stance than many Western and Chinese publishers have taken in 2026, several of which have shipped generative AI texture and voice tools without drawing a public line around “art.”
Whether that philosophy survives contact with production deadlines is the open question. Capcom is not a small studio insulated from market pressure — it is a publicly traded company whose Steam revenue has reportedly overtaken its PlayStation revenue, and investors increasingly expect every major studio to show an AI efficiency story in earnings calls. Saying “AI is not for creating art” in an interview is one thing; holding that line when a competitor ships a Resident Evil-scale game in half the development time using generative tooling is another.
REX explained: what actually changes in RE Engine
Strip away the controversy and REX is, on paper, a fairly conventional engine-modernization project with an AI-tooling layer bolted on. According to reporting on Ishida’s October 2 presentation, in which he described REX, short for “RE neXt Engine,” as a program to incrementally improve RE Engine, the stated goals include faster data handling, lighter and more accessible development tools, reworked logging and networking systems, easier gameplay prototyping, and support for scenes containing substantially more characters than the current RE Engine can comfortably render. Capcom has framed the push behind three pressures: games are getting larger and iteration cycles are slowing down as a result, the development workforce itself has grown larger and more internationally distributed, and AI needs to be integrated into the workflow somehow if Capcom wants to keep pace with both of those trends.
The AI-specific pieces of REX, as described in coverage of the presentation, center on AI-assisted code generation and automated playtesting, plus a programming environment designed to be legible to both human developers and AI systems working in tandem. None of that, taken at face value, describes generative art tools. It describes something closer to GitHub Copilot for a AAA game engine: a system that helps engineers write boilerplate code faster and catches bugs during automated test passes, freeing human time for design and art work rather than replacing it.
That is a meaningfully different pitch than “AI-generation game engine,” and it is the gap between those two framings that produced most of the backlash. REX also matters beyond Resident Evil, because RE Engine already powers Monster Hunter and Street Fighter. Capcom separately addressed Street Fighter 6 directly, telling press around October 3, 2026, that it has no plans to use generative AI for in-game animations, visuals, or other assets in that title either — the same pledge, applied to a second franchise, within roughly 24 hours of the original statement.
Data table: the two AI controversies, side by side
Because the REX engine story and the DLSS 5 Grace Ashcroft story merged in public conversation, it helps to separate what is actually confirmed about each one.
| Detail | REX / RE Engine AI tooling | DLSS 5 / Grace Ashcroft rendering |
|---|---|---|
| What triggered it | Satoshi Ishida’s Oct. 2, 2026 roadmap talk at Capcom Open Conference RE:2026 | Nvidia hands-on demo of DLSS 5 using Resident Evil Requiem, reported by Inven Global |
| Who is responsible | Capcom’s internal engine and AI-solutions team | Nvidia’s neural rendering pipeline, applied to Capcom’s existing character model |
| What Capcom confirmed | AI-assisted code generation, automated playtesting, faster data handling — no AI-generated assets in shipped games | No confirmation that generative AI created or altered Ashcroft’s base character model |
| Games affected | Future RE Engine titles across Resident Evil, Monster Hunter, Street Fighter | Resident Evil Requiem specifically, as a DLSS 5 showcase title |
| Status as of Oct. 10, 2026 | Capcom issued a public clarification via IGN distinguishing dev-tool AI from generative content AI | Unresolved; criticism of the visual change predates the REX statement by about two weeks |
Why the distinction between “AI tooling” and “AI-generated art” matters
Game developers have spent much of 2026 discovering that “AI in games” means wildly different things depending on who is saying it. A studio using AI to automate QA regression testing is doing something almost nobody objects to. A studio using a generative model to paint final character textures or compose music tracks that ship in the retail product is doing something that triggers union concern, ethical-sourcing questions about training data, and straightforward fear about job security for artists and composers. Capcom’s statement is an attempt to plant its flag firmly on the first side of that line while acknowledging that AI, in some form, is already part of how modern engines get built.
The timing matters too. Capcom’s clarification lands against a backdrop where Japanese game development, as an industry, has already moved much further toward generative AI adoption than the public conversation around this story suggests. According to a 2026 CESA (Computer Entertainment Supplier’s Association) survey previewed at Tokyo Game Show, 85.8% of surveyed Japanese game developers reported using generative AI in their work in some capacity, up from roughly 51% the previous year, according to Automaton’s reporting on the survey. That figure covers everything from concept art brainstorming to code assistance, and it is a useful reminder that the Capcom backlash is not really a story about whether AI touches Japanese game studios — it clearly already does, broadly — but about where the line gets drawn between assistive use and generative content in the final product.
That adoption curve is also why Capcom’s framing reads as calculated rather than reactive. A company watching 85.8% of its peers already use generative AI tools internally cannot credibly pretend it will avoid AI entirely. What it can do is draw a visible, quotable line — no AI-generated assets in finished games — that protects it from the artist-replacement narrative while still capturing the productivity upside everyone else is already banking.
Historical context: Capcom’s RE Engine and its track record
RE Engine has been one of the more quietly successful proprietary game engines of the last decade. Built originally for Resident Evil 7: Biohazard, it has since powered Resident Evil Village, Resident Evil 4’s remake, Monster Hunter Rise, Monster Hunter Wilds, Street Fighter 6, Devil May Cry 5, and Dragon’s Dogma 2, among others. Part of Capcom’s commercial turnaround over the past several years — including the kind of Steam-first sales shift tech-insider.org covered in 2026 — has been credited to RE Engine’s efficiency relative to licensed engines like Unreal, letting Capcom ship visually dense games with relatively lean teams.
REX is explicitly framed as the next chapter of that same engine lineage rather than a clean break, which is itself notable. Capcom did not, for example, announce a wholesale migration to Unreal Engine 5 or a brand-new proprietary system the way some rivals have pursued. It chose evolution over revolution, and the AI tooling layer is being bolted onto an engine with an established reputation rather than introduced alongside a risky engine transition. That continuity is one reason Capcom’s pledge carries some weight: the studio has a multi-year history of using RE Engine upgrades to solve real production bottlenecks (lighting, character counts, load times) rather than to chase buzzwords, and REX’s stated goals — faster data handling, better tooling, larger scenes — fit that pattern.
The engagement stakes around Resident Evil specifically are also higher than usual right now. Resident Evil games saw a reported 50% jump in engagement following the franchise’s recent movie release, and the series’ voice cast remains a draw in its own right — Maggie Robertson, who voices Lady Dimitrescu, has publicly confirmed she would return for future Capcom projects. Any perception that AI is creeping into character performance or likeness work lands on a franchise that is currently riding a wave of renewed mainstream attention, which raises the reputational cost of getting the AI message wrong.
Competitive comparison: how other major publishers have handled generative AI
Capcom is not operating in a vacuum. Other major publishers have staked out their own, sometimes contradictory, positions on generative AI in game production over the past year, and the contrast helps explain why Capcom’s specific wording — “no AI-generated assets,” paired with open-ended AI tooling — is being read as a middle path rather than either extreme.
| Publisher | Public stance on generative AI assets | Engine / tooling approach |
|---|---|---|
| Capcom | No AI-generated assets in shipped games; AI permitted for code, testing, efficiency tools | RE Engine evolving into REX, built around human-plus-AI programming workflows |
| Electronic Arts | Has discussed AI-assisted production tools publicly, with less explicit no-assets pledge | Proprietary engines (Frostbite) plus third-party middleware |
| Square Enix | Has acknowledged generative AI use in some internal pipelines | Luminous and other proprietary engines, alongside Unreal Engine adoption |
| Independent/indie studios | Highly varied; many explicitly market “no AI” as a selling point | Mostly Unreal Engine or Unity rather than proprietary tech |
The table above reflects general industry positioning rather than a single verified comparative study; exact policies vary by title and have continued shifting through 2026. The throughline, though, is that Capcom’s pledge is more explicit and more publicly quotable than most of its direct competitors, which is likely why it became the flashpoint story rather than, say, a similar internal memo at a rival publisher that never got pressed on the record.
What this means for Resident Evil Requiem specifically
Resident Evil Requiem sits at the intersection of both controversies, which makes it the title to watch. It is a flagship showcase for Nvidia’s DLSS 5 technology — the same technology implicated in the Grace Ashcroft facial-rendering criticism — and the ninth mainline Resident Evil entry, the most recent mainline game that will eventually be shaped by whatever REX tooling Capcom rolls out. Capcom’s clarification does not retroactively change anything about Requiem’s already-shipped content; the game, released on February 27, 2026, is already out, built under the existing RE Engine pipeline, not REX.
What the DLSS 5 criticism actually targets is a rendering-time effect — the way neural upscaling and frame generation reconstruct a face in real time on a player’s screen — not the underlying art asset Capcom’s artists created. That distinction got lost in a lot of social media commentary. Nvidia’s rendering pipeline sits downstream of Capcom’s actual character models, and the “AI-altered face” players noticed in hands-on demos reads more like an aggressive photo filter than AI-generated concept art. That does not make the criticism baseless, but it is a different problem than the one Capcom’s REX statement addressed, and conflating the two makes it harder to hold either company accountable for what it actually controls.
Developer and industry reaction
Public reaction split along fairly predictable lines once the story circulated. A segment of players and critics reacted negatively to the phrase “AI-generation game engine” specifically, reading it as confirmation that future Resident Evil content would include AI-generated art, models, or audio. That reaction sits inside a broader, well-documented current of opposition to generative AI in game production tied to concerns about artistic labor, training-data consent, and job displacement — concerns that have shaped coverage of AI in gaming across most of 2026, independent of any single studio’s actual policy.
Capcom’s clarification appears designed specifically to defuse that reaction by drawing a bright line between development-assistance AI (testing, debugging, automation) and generative AI used to create final assets. Whether that distinction lands with skeptical players remains to be seen; corporate clarifications issued after backlash tend to get read with more suspicion than statements made proactively, regardless of their content. The fact that Capcom felt it needed to respond at all — rather than letting the REX presentation stand on its own — suggests the company registered the backlash as reputationally significant, not just online noise.
Market and business impact for Capcom
Capcom’s business case for REX is straightforward even if the AI framing is contentious: engine efficiency has been directly tied to the company’s financial performance for years. A studio that can ship visually ambitious games with smaller teams and shorter cycles protects its margins better than one locked into a slower, more labor-intensive pipeline. Resident Evil, Monster Hunter, and Street Fighter are Capcom’s three most commercially important franchises, and all three run on RE Engine, which means any efficiency gain from REX compounds across the publisher’s entire release slate rather than benefiting a single game.
That is also exactly why the “no AI-generated assets” pledge is a calculated business decision as much as a creative one. A reputational hit to Resident Evil’s brand — a franchise Capcom has spent years rebuilding into one of its most reliable sellers — would cost far more than whatever efficiency Capcom might gain from loosening its stance on generative content. Drawing the line at “AI helps us build faster, it doesn’t replace what our artists make” lets Capcom pursue the cost savings tied to AI tooling while insulating its highest-value franchises from the backlash that has hit other companies accused of using generative AI in finished creative work.
What Capcom has not addressed
There are real gaps in what Capcom has said publicly. The company has not detailed a timeline for when REX tooling reaches production, nor named which upcoming Resident Evil, Monster Hunter, or Street Fighter titles will be first built with REX rather than the current RE Engine. It also has not addressed, in any verified statement, job impact — whether AI-assisted testing and code tools are meant to reduce headcount, or simply let existing teams work faster. No union statement tied specifically to this controversy has been confirmed as of this writing. Capcom also has not directly addressed the DLSS 5 Grace Ashcroft criticism in the same statement that covered REX, leaving the two controversies formally unlinked even though public conversation has treated them as one story.
Predictions: where this goes next
- Expect Capcom to repeat versions of the “no AI-generated assets” pledge at future events, including likely restatements around Monster Hunter and Street Fighter 6 content drops, as the company tries to get ahead of the story rather than respond to it.
- REX is unlikely to ship as a distinct, marketed feature in any single Resident Evil title; it will more likely surface gradually as background engine updates that Capcom discusses primarily in developer-facing contexts rather than consumer marketing.
- Scrutiny of AI-assisted rendering technologies like DLSS 5 will keep getting folded into “is this game using AI” conversations even when the underlying art assets are untouched, because most players cannot distinguish rendering-time AI from asset-generation AI without it being explained.
- Other Japanese publishers with CESA-reported generative AI adoption will likely face similar pressure to issue their own public “no AI assets” clarifications over the next two to three months, following Capcom’s playbook.
- Watch for Capcom to eventually quantify REX’s productivity gains in an earnings call once a REX-built title ships, since the company has a track record of tying engine investments to concrete financial narratives for investors.
The bigger picture for game engines in 2026
REX is Capcom’s version of a broader shift already underway across the industry, where engine teams are being asked to build AI-collaboration directly into their tooling rather than treating AI as an optional plugin layered on top. That mirrors conversations happening around engines like Unreal and Godot, both of which tech-insider.org has covered as developers weigh proprietary versus open engine tradeoffs and which engines best support smaller teams under rising development costs. Capcom’s position — proprietary engine, AI as an internal productivity layer, explicit no-generative-assets pledge — is a middle-ground answer that larger studios with existing engine investments can realistically copy, which is part of why it is being watched closely outside of Resident Evil fandom specifically.
It also sits alongside a wider conversation about AI-driven rendering technology that tech-insider.org has tracked since DLSS 5’s debut, where the gap between marketed frame-rate claims and real-world performance has repeatedly become its own controversy independent of any specific game’s art pipeline. The Grace Ashcroft criticism is very much part of that same pattern: a rendering technology doing something visible and debatable to an existing asset, rather than a generative model creating a new one from scratch.
Frequently Asked Questions
Is Capcom using AI to create Resident Evil characters or art?
No. Capcom has stated it will not implement AI-generated assets into its games. The company says AI will be used for development efficiency — things like code analysis, automated testing, and workflow tools — not for generating final art, character models, or audio that ships in a game.
What is REX, Capcom’s RE Next Engine?
REX stands for RE neXt Engine. It is a planned evolution of Capcom’s existing RE Engine, not a replacement built from scratch, aimed at faster data handling, lighter development tools, and support for scenes with more characters, including AI-assisted code generation and automated playtesting.
Did Resident Evil Requiem use AI to change Grace Ashcroft’s face?
What drew criticism was Nvidia’s DLSS 5 neural rendering technology, demonstrated using Resident Evil Requiem, which some hands-on reports said visibly altered Grace Ashcroft’s appearance during gameplay. There is no confirmation that Capcom used generative AI to create the underlying character model itself.
Which Capcom games run on RE Engine?
RE Engine powers Resident Evil titles since Resident Evil 7, along with Monster Hunter Rise, Monster Hunter Wilds, Street Fighter 6, Devil May Cry 5, and Dragon’s Dogma 2, among other Capcom releases.
Has Capcom made similar AI statements about other franchises?
Yes. Capcom separately addressed Street Fighter 6, saying it has no plans to use generative AI for in-game animations, visuals, or other assets in that title, applying the same stance it took on Resident Evil.
Who is Shinichi Inoue?
Shinichi Inoue is Capcom’s vice president of game development platform and AI solutions. He has publicly emphasized that human creative sensibility cannot currently be matched by AI, and has stated that AI is not meant for creating art at Capcom.
How widely do Japanese game developers already use generative AI?
According to a 2026 CESA survey previewed at Tokyo Game Show, 85.8% of surveyed Japanese game developers reported using generative AI in some capacity, up from roughly 51% a year earlier, though that figure spans a wide range of uses beyond art generation.
When will REX actually be used in a shipped Resident Evil game?
Capcom has not announced a timeline or named a specific upcoming title that will be the first built using REX tooling rather than the current RE Engine.
