Capcom really loves its RE Engine, will keep using it beyond Resident Evil and Devil May Cry 5

This article is over 5 years old and may contain outdated information

I’ll keep playing it

Recommended Videos

Capcom might be making some weird decisions with Switch port pricing, but when it comes to brand new games (or brand new remakes), they are killing it. Resident Evil 2 and Devil May Cry 5 are enjoying some of the most celebrated critical and financial successes of this generation, and they have one thing in common: the RE Engine, developed for Resident Evil 7.

It looks like the publisher really struck gold here, and it seems as if it’s here to stay. Speaking at a Q&A for their recent financial results briefing at the end of this fiscal year (March 31, 2019), Capcom doubled down on it: “The games we developed using the RE Engine during this current hardware generation have received critical acclaim, and from the early stages of building this engine, we kept the ability to augment it for next-generation development in mind; as such, we view the RE Engine as one of our strengths that will contribute to next-generation game creation.”

That’s a pretty huge answer with long-lasting implications. I mean the next generation? Will we see the Resident Evil 3 remake and Devil May Cry 6 on the PS5? You can probably bet money on it. Further into the Q&A, Capcom notes that while they decline to grant specifics, “there are numerous titles currently being developed internally with the RE Engine.”

“Numerous” eh? We’ll probably see at least one more current generation project then.

Financial Results Briefing for the Fiscal Year ended March 31, 2019: Q&A Summary [Capcom] Thanks John!


Destructoid is supported by our audience. When you purchase through links on our site, we may earn a small affiliate commission. Learn more about our Affiliate Policy
Author
Image of Chris Carter
Chris Carter
Managing Editor/Reviews Director
Managing Editor - Chris has been enjoying Destructoid avidly since 2008. He finally decided to take the next step in January of 2009 blogging on the site. Now, he's staff!