{"id":67669,"date":"2026-06-04T22:00:00","date_gmt":"2026-06-04T13:00:00","guid":{"rendered":"https:\/\/automaton-media.com\/en\/?p=67669"},"modified":"2026-06-04T16:26:25","modified_gmt":"2026-06-04T07:26:25","slug":"final-fantasy-vii-rebirths-switch-2-port-was-built-around-what-to-preserve-not-what-to-cut-director-naoki-hamaguchi-on-optimizing-a-massive-ope","status":"publish","type":"post","link":"https:\/\/automaton-media.com\/en\/interviews\/final-fantasy-vii-rebirths-switch-2-port-was-built-around-what-to-preserve-not-what-to-cut-director-naoki-hamaguchi-on-optimizing-a-massive-ope\/","title":{"rendered":"Final Fantasy VII Rebirth\u2019s Switch 2 port was built around \u201cwhat to preserve,\u201d not \u201cwhat to cut.\u201d Director Naoki Hamaguchi on\u00a0optimizing\u00a0a massive open world with a heavily customized UE4\u00a0"},"content":{"rendered":"\n

Final Fantasy VII Rebirth<\/strong>, the second installment in Square Enix\u2019s FFVII remake trilogy,\u00a0came to\u00a0Nintendo Switch 2, Xbox Series X|S, and Microsoft Store on Windows on June 3.\u00a0While\u00a0the Switch\u00a02\u00a0represents\u00a0a big leap in hardware capability compared to its predecessor, optimization\u00a0remains\u00a0a concern when it comes to\u00a0massive\u00a0tiles\u00a0like\u00a0FFVII\u00a0Rebirth.\u00a0To learn more about how the game was ported to the Switch 2,\u00a0AUTOMATON\u00a0recently sat down with Square Enix\u2019s Naoki Hamaguchi\u00a0\u2013 director of the FFVII Remake trilogy \u2013 who talked\u00a0to us\u00a0at length about the technical challenges and solutions involved.\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

\u2014I assume FFVII Rebirth\u2019s assets were created with PS5-, gaming PC-, and Xbox Series-level hardware in mind. What kind of optimization work was required to make it run on Nintendo Switch 2?<\/strong> <\/p>\n\n\n\n

Naoki Hamaguchi (hereafter Hamaguchi):<\/strong>\u00a0
Since FFVII Rebirth was developed with a future PC release in mind from the\u00a0start, we had already designed it with a certain degree of scalability\u00a0when it comes to\u00a0processing load. However,\u00a0the\u00a0Nintendo Switch 2, especially in handheld mode,\u00a0operates\u00a0under stricter power consumption constraints, which further limits the resources available, so we\u00a0couldn\u2019t\u00a0simply\u00a0port the game over as-is.\u00a0<\/p>\n\n\n\n

Compared to FFVII Remake, FFVII Rebirth saw a dramatic increase in the number of meshes, materials, and background streaming data visible on-screen due to its open-world design. As a result, we needed to perform comprehensive optimization that encompassed not only GPU, but also CPU usage and memory bandwidth. Therefore, our approach wasn’t “What can we cut?” but rather, “What should we redesign in order to preserve what has to stay?” <\/p>\n\n\n\n

For environmental models, we redesigned the LOD (Level of Detail) system specifically for Nintendo Switch 2. Rather than simply reducing polygon counts, we re-evaluated information density at different viewing distances and even revisited material composition. We also built Switch 2-specific versions of levels using those dedicated assets so each scene could be configured optimally. <\/p>\n\n\n\n

The same goes for lighting. We adjusted shadow draw distances and the number of spotlights while searching for a balance that would preserve not only performance, but also the atmosphere and sense of immersion characteristic of FFVII Rebirth. <\/p>\n\n\n\n

Frankly speaking, there are no shortcuts in this kind of work. People sometimes call it a “miracle port,” but in reality, it’s the result of a painstaking process of measuring load, identifying bottlenecks, and eliminating them one by one. Ultimately, I believe this accumulation of effort is what allowed us to successfully bring the FFVII Rebirth experience to Switch 2. <\/p>\n\n\n\n

\"\"
Image from the <\/em>Final Fantasy VII Rebirth Launch Trailer for\u00a0the\u00a0Nintendo Switch 2 and Xbox Series X|S<\/em><\/a><\/em><\/figcaption><\/figure>\n\n\n\n

\u2014The FFVII remake series has attracted attention for continuing to use Unreal Engine 4 (<\/strong>related article<\/strong><\/a>). Given the massive scale of FFVII Rebirth, I imagine that, rather than just tailoring in-game assets, you needed to customize Unreal Engine itself as well. Could you tell us more about that?<\/strong> <\/p>\n\n\n\n

Hamaguchi:<\/strong>\u00a0
Yes, at the scale of FFVII Rebirth, simply using Unreal Engine 4 as-is\u00a0wouldn’t\u00a0have\u00a0been\u00a0feasible.\u00a0In particular, the transition to an open-world\u00a0design\u00a0significantly increased rendering and streaming demands compared to FFVII Remake. Because of that, we\u00a0don’t\u00a0rely entirely on Unreal Engine’s standard systems\u00a0when it comes to\u00a0rendering\u00a0and lighting. Instead,\u00a0we’ve\u00a0continuously customized them to suit our needs.\u00a0<\/p>\n\n\n\n

More specifically, we’ve rebuilt portions of the lighting system, optimized shaders, and improved rendering data efficiency to suit the characteristics of each platform. In addition, because FFVII Rebirth features an enormous world map, we’ve developed and now utilize a proprietary large-scale geometry system called Massive Environment. While it shares some similarities with Unreal Engine 5’s Nanite conceptually, it’s something we’ve developed to specifically meet the needs of the FFVII remake series. <\/p>\n\n\n\n

Since we handle a vast amount of environmental data spanning distant scenery to close-up views, this also led us to revisit our streaming methods and caching strategies for the Nintendo Switch 2 version. For this port, rather than simply lowering the rendering quality, we needed to redesign where to allocate our limited resources. Therefore, instead of optimizing rendering, lighting, and streaming individually, we adjusted things while viewing the entire system as an integrated whole. <\/p>\n\n\n\n

People often ask us why we’re still using Unreal Engine 4, but for us, what’s important isn’t the engine version, but whether it can deliver the game experience we’re aiming for. We’re also continuing to use Unreal Engine 4 for the final installment of the remake trilogy currently in development, and considering the technical assets and expertise we’ve accumulated over more than a decade, I think that was a very rational decision. I would say we aren’t simply \u201cusing\u201d Unreal Engine 4; we’ve continuously expanded and evolved it to meet the needs of the FFVII remake project. That accumulated work also played a role in developing FFVII Rebirth\u2019s Nintendo Switch 2 version. <\/p>\n\n\n\n

\"\"
Image from the <\/em>Final Fantasy VII Rebirth Launch Trailer for\u00a0the\u00a0Nintendo Switch 2 and Xbox Series X|S<\/em><\/a><\/figcaption><\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

\u2014Nintendo Switch 2 has both less RAM and slower memory than the PS5 and Xbox Series X|S (12GB as opposed to 16GB), and there’s a significant gap in CPU performance too. How did you address hardware limitations that can’t simply be resolved by lowering asset quality?<\/strong> <\/p>\n\n\n\n

Hamaguchi:<\/strong>\u00a0
This might surprise you, but compared to the GPU,\u00a0the\u00a0CPU and memory constraints\u00a0didn’t\u00a0feel\u00a0significantly more limiting to me\u00a0in practice.\u00a0That\u2019s\u00a0because\u00a0the primary limitation in Nintendo Switch 2’s handheld mode is the GPU. Of course,\u00a0there\u00a0are<\/em>\u00a0differences in CPU performance and memory capacity, but many console games are originally designed around a 60fps\u00a0target when it comes to\u00a0CPU load. If\u00a0you’re\u00a0targeting 30fps,\u00a0then\u00a0there’s\u00a0plenty\u00a0of room to work with\u00a0in theory.\u00a0<\/p>\n\n\n\n

That’s purely theoretical, however, and during actual development, many other issues arise. FFVII Rebirth constantly runs numerous systems simultaneously, including NPC behavior, background streaming, animation updates, and gameplay logic, so simply lowering texture or model quality isn’t enough. On the memory side, we reduced the memory footprint of environmental models and mesh data, and we also revisited streaming methods and caching strategies across the entire open world to ensure that available memory was used more efficiently. <\/p>\n\n\n\n

When it comes to CPU load, we focused on NPC and animation optimization. For example, we controlled animation update frequency based on distance from the player and managed how many characters could be updated simultaneously, thus reducing load in areas players are unlikely to notice. <\/p>\n\n\n\n

Additionally, at the engine level, we strengthened SIMD support and introduced compiler optimizations, including two-pass PGO (Profile-guided optimization). Individually, these changes may seem modest, but their cumulative effect is rather significant. <\/p>\n\n\n\n

In open-world environments, momentary spikes in load are generally a bigger concern than average load. We repeatedly measured and recreated situations where such load spikes occurred, then eliminated each bottleneck one by one. <\/p>\n\n\n\n

To summarize, rather than merely adjusting asset quality, we made FFVII Rebirth feasible on the Switch 2 through comprehensive optimization of the entire system, including CPU usage, memory management, streaming, and animation processing. <\/p>\n\n\n\n

\u2014The sheer volume of assets in the game’s urban areas is especially impressive. Could you tell us what specific optimizations were carried out there?<\/strong> <\/p>\n\n\n\n

Hamaguchi:<\/strong>\u00a0
Cities were among the\u00a0highest-load\u00a0areas in FFVII Rebirth.\u00a0Since environmental models, NPCs, and lighting are\u00a0densely\u00a0packed together,\u00a0urban areas require\u00a0a\u00a0different optimization approach than the world map.\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

First, when it comes to environmental assets, we redesigned the LOD structure specifically for the Switch 2. We also adjusted shadow draw distances and the number of spotlights to optimize overall rendering load. Additionally, we revisited NPC counts and placement of small objects on an area-by-area basis, reducing system load while maintaining the sense of density players are supposed to experience. <\/p>\n\n\n\n

I’d also like to note that our goal was not simply to reduce load. The bustle and atmosphere of the cities are core parts of the FFVII Rebirth experience, so we started from first determining what absolutely needed to remain, and only then proceeded with optimization. As a result, I believe we\u2019ve managed to achieve a balance that works on the Nintendo Switch 2 without significantly compromising the sense of density and immersion unique to FFVII Rebirth\u2019s urban areas. <\/p>\n\n\n\n

\u2014Nintendo Switch 2’s inclusion of NVIDIA’s DLSS upscaling technology (which uses AI calculations to make lower-resolution images appear higher-resolution) has drawn a lot of attention, but what specific DLSS settings were used in FFVII Rebirth?<\/strong> <\/p>\n\n\n\n

Hamaguchi:<\/strong>\u00a0
We do utilize DLSS in the Nintendo Switch 2 version of FFVII Rebirth.\u00a0The game is designed\u00a0with\u00a0Dynamic\u00a0Resolution scaling\u00a0in mind\u00a0rather than a fixed resolution, meaning the internal rendering resolution changes in real time depending on\u00a0load. In handheld mode, the internal resolution ranges from 1344\u00d7756 to 672\u00d7380, while in TV mode,\u00a0it ranges from 1920\u00d71080 down to 960\u00d7540, with\u00a0DLSS used to enhance the final image quality.\u00a0<\/p>\n\n\n\n

This follows the same general approach we adopted for the Nintendo Switch 2 version of FFVII Remake. However, we don’t view DLSS simply as a technology for increasing resolution. In an open-world title like FFVII Rebirth, many different factors \u2013 like draw distance, lighting and streaming \u2013 affect performance simultaneously, which makes deciding how to allocate limited GPU resources crucial. DLSS is one of the tools we use to achieve this, by flexibly controlling the internal resolution, thus balancing frame rate stability with immersive gameplay. <\/p>\n\n\n\n

Another topic that\u00a0came up with\u00a0the Nintendo Switch 2 version of FFVII Remake was the interaction between DLSS and fine\u00a0forms\u00a0such as hair\u00a0(related\u00a0article<\/a>), and we\u00a0continued refining that aspect for Rebirth as well.\u00a0We\u2019ve\u00a0optimized\u00a0the visuals to look as natural as possible\u00a0by, for example,\u00a0applying\u00a0subtle blur wherever\u00a0necessary\u00a0depending on the density and flow of the hair.\u00a0Our goal\u00a0wasn\u2019t\u00a0to make players\u00a0aware\u00a0of\u00a0DLSS\u00a0itself;\u00a0we prioritized making sure the\u00a0same world feels natural whether\u00a0you’re\u00a0playing in handheld\u00a0or docked mode.\u00a0<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

\u2014What scenes in the Nintendo Switch 2 version of FFVII Rebirth would you say particularly demonstrate how you\u2019ve leveraged the hardware’s capabilities?<\/strong> <\/p>\n\n\n\n

Hamaguchi:<\/strong>\u00a0
Personally, I think traversing the map at high speed on a\u00a0Chocobo\u00a0is one of the clearest examples.\u00a0Since\u00a0FFVII Rebirth\u00a0is an\u00a0open-world\u00a0game, the amount of environmental data being processed within a single frame is enormous. Mountains in the distance, nearby vegetation, terrain, and lighting are all being streamed and\u00a0rendered\u00a0continuously, making these scenes technically very demanding.\u00a0<\/p>\n\n\n\n

So, when the player is moving at high speed, the amount of data that needs to be loaded increases dramatically. To handle that, we combined background LOD switching, streaming controls, Dynamic Resolution scaling, and DLSS, all with the goal of preventing players from noticing any loading or heaviness. <\/p>\n\n\n\n

Another good example would be urban areas such as <\/strong>Kalm and Junon. These areas present a different kind of challenge from the world map because they house large numbers of NPCs, environmental objects, and lighting elements simultaneously. <\/p>\n\n\n\n

In fact, there were instances where we had to make trade-offs to manage load \u2013 like adjusting small environmental props \u2013 which led to people noticing missing food on tables and the like. However, our priority was to ensure the player\u2019s experience is consistent, not to recreate the exact same number of objects. <\/p>\n\n\n\n

In scenes where reproducing everything one-to-one isn’t feasible, we focus on determining what should be preserved. As a result, we chose to prioritize maintaining the liveliness of the cities, their unique atmosphere, and the player’s sense of immersion in the world. <\/p>\n\n\n\n

Throughout development of the Nintendo Switch 2 version, what we were most conscious of wasn’t showcasing differences in hardware specifications, but ensuring all players could experience the same journey. Whether in handheld mode or TV mode, we didn’t want anyone to feel like they were playing a different game. I believe our cumulative efforts of optimization aimed at achieving this goal are evident in scenes like these. <\/p>\n\n\n\n

\u2014Thank you very much.<\/strong> <\/p>\n\n\n\n

\n