Following the exciting Ōkami sequel announcement at The Game Awards, fan speculation immediately centered on Capcom's RE Engine powering the game. IGN can exclusively confirm this, based on interviews with key project leads.
In an extensive interview, Machine Head Works producer Kiyohiko Sakata confirmed the use of RE Engine. Regarding Machine Head Works' role, Sakata explained their function as a bridge between Capcom (IP holder and director of the game's overall vision) and Clover (lead developer). Machine Head Works' prior experience with Capcom and Hideki Kamiya, along with their familiarity with RE Engine, provides crucial support to Clover, who lacked prior experience with the engine. Additionally, Machine Head Works includes personnel with experience on the original Ōkami, further aiding development.
Capcom producer Yoshiaki Hirabayashi succinctly stated the appeal of RE Engine: "Yes," elaborating that Capcom believes Kamiya's artistic vision wouldn't be achievable without it. Kamiya himself added that RE Engine's renowned visual capabilities align perfectly with fan expectations for the sequel's quality.
The interview further highlighted RE Engine's potential, with Sakata suggesting it allows the team to realize elements envisioned for the original Ōkami but unattainable at the time. Modern technology, coupled with RE Engine, enables them to surpass those original ambitions.
RE Engine, Capcom's proprietary engine (originally developed for Resident Evil 7), has powered many major titles, including the Resident Evil series, Monster Hunter, Street Fighter, and Dragon's Dogma. While most RE Engine games utilize a realistic art style, the prospect of its application to Ōkami's distinctive aesthetic is highly intriguing. Capcom's development of the successor engine, REX, and its gradual integration into RE Engine, suggests the Ōkami sequel may incorporate some of REX's technology as well.
For a complete account of the interview with the Ōkami sequel's leads, including further details on the game's development, please refer to the full Q&A.
