007 First Light Glacier Engine: Streaming and Switch 2 Explained

007 First Light’s Glacier Refresh Is Built Around One Big Goal: Keep Bond Moving

007 First Light uses a heavily rebuilt version of IO Interactive’s Glacier engine to do something the modern Hitman games were never designed around: move players through rapidly changing locations without stopping for a full mission load. That means airport terminals, mountain facilities, city streets, interiors, crowds, combat spaces, and cinematic transitions can be stitched together through continuous data streaming rather than separated by the familiar “load the level, then play the sandbox” structure.

That technical change matters even more for the Nintendo Switch 2 version. IO Interactive is not making a separate, stripped-down Bond game. Glacier’s new Virtual Platform system lets the studio build one mission content base, then tailor geometry, textures, crowd density, visual effects, and streaming budgets for each machine. The target on Switch 2 is a stable 30fps, while PlayStation 5 and Xbox Series X offer 30fps Quality and 60fps Performance modes.

It is an ambitious plan, and it is smarter than trying to brute-force console-scale visuals onto a lower-power handheld-oriented platform. The compromise is visible in the design: Switch 2 will use tighter streaming bricks, lower-detail asset variants, stricter AI budgets, and more aggressive culling. Those are the trade-offs that keep a spy thriller from turning into a stuttery tour of loading screens.

Platform Targets and the Important Limits

Platform	Frame-Rate Target	Rendering Approach	Key Constraint
PlayStation 5	30fps Quality / 60fps Performance	Frame Graph and up to four asynchronous compute pipelines	Balances dynamic GI, volumetrics, and heavy scenes across GPU workloads
Xbox Series X	30fps Quality / 60fps Performance	Modern Glacier rendering stack with software RT global illumination	Must sustain large environments and crowd simulation at higher settings
Xbox Series S	30fps-focused	Reduced performance target versus Series X	RAM and GPU headroom rule out a 60fps target
PC	Hardware-dependent	DirectX 12 only; DLSS 4.5 Dynamic Multi Frame Generation on RTX GPUs	No DX11 or Vulkan fallback; AMD and Intel lack equivalent frame generation at launch
Nintendo Switch 2	Stable 30fps target	Dedicated Virtual Platform profile with smaller streamed asset bricks	Tighter memory, bandwidth, crowd, and geometry budgets

From Hitman’s Big Sandboxes to Bond’s Faster-Paced Missions

The modern Hitman trilogy used large, dense levels, but each mission began with a substantial blocking load. That approach made sense for social-stealth sandboxes: load Sapienza, Paris, or Dubai once, then let the simulation run. 007 First Light needs a different rhythm. Bond stories move between infiltration, pursuit, combat, conversations, escapes, and setpieces much more aggressively.

Glacier now handles that through dynamic “brick” streaming. A brick is a package of world data containing pieces of geometry, textures, simulation information, AI, animation data, lighting information, and other assets needed for a specific part of the environment. Instead of loading an entire level at once, the engine swaps these packages in and out as Bond moves through a mission.

The practical payoff is less dead time. A mission can move from a broad exterior space into an interior, then through a service corridor into another major area without returning to a menu or forcing a traditional full-screen load. That does not mean every transition becomes invisible on every platform. Lower-bandwidth systems can still lean on elevators, tunnels, narrow passages, slower camera moves, or cinematic beats to give the streaming system breathing room. That is normal engineering, not a failure of the seamless-streaming pitch.

Why the Editor, Runtime, and Resource Server Split Matters

The Glacier refresh is more than a renderer upgrade. IO Interactive has separated the engine into three connected parts: the Editor, the Runtime, and the Resource Server. They communicate through RPC calls, but each has a distinct job.

• The Editor is where teams build levels, missions, gameplay logic, assets, and transitions. It can simulate streaming conditions before a mission reaches a console or PC build.
• The Runtime runs the game itself: rendering, AI, physics, animation, audio, world streaming, and player interaction.
• The Resource Server manages asset packages and platform-specific streaming bricks, delivering the right data to the Runtime when it is needed.

This split is useful because it turns optimization into something developers can test earlier. A level team can inspect brick transitions, identify memory spikes, and adjust platform budgets while authoring the mission rather than finding a nasty streaming hitch after the world is already locked down. It also improves crash resilience by reducing the degree to which development tools and the live runtime are intertwined.

For a multiplatform project, that is a serious upgrade. The old approach of building a high-end scene and spending months cutting it down for weaker machines is expensive and messy. Glacier’s new architecture is designed to let IO build the scene once, then feed every platform a version of that scene appropriate to its memory, GPU, and storage constraints.

Virtual Platforms Are the Real Switch 2 Strategy

Virtual Platforms are IO Interactive’s internal hardware profiles. Think of them as a ruleset for each target machine: high-end PC, PlayStation 5, Xbox Series X, Xbox Series S, and Nintendo Switch 2 each get their own expected memory budget, texture tier, geometry density, streaming behavior, and frame-rate target.

That means the Switch 2 version can use the same mission layout and gameplay logic as the PS5 version while pulling smaller brick variants from the Resource Server. Lower-resolution textures, reduced geometry detail, more forceful level-of-detail transitions, and reduced anisotropic filtering are predictable parts of that profile. The important bit is that these reductions are planned at the asset pipeline level, rather than bolted on after the fact.

IO’s stated game memory budget for Switch 2 is 9,381MB, compared with 10,481MB for the PC version. Those figures are game budgets rather than a declaration of each platform’s total installed memory. The split also reveals where the cuts are expected to land: game logic, animation, physics, and audio retain the same budget, while rendering assets such as textures and geometry take the reduction.

That is the correct priority for a Bond game. A lower-resolution wall texture is far less damaging than broken animation blending, delayed sound cues, missing interaction logic, or AI that loses track of its own suspicion state. The visual downgrade may be noticeable side by side, but keeping the systemic layer intact protects the actual game.

30fps on Switch 2 Depends on More Than Resolution Scaling

The Switch 2 build targets stable 30fps with scaling technology, but resolution is only one part of the workload. Glacier’s most expensive new features are not limited to pixel count. Dynamic global illumination, volumetric smoke, crowd simulation, animation systems, physics, and AI all consume CPU time, GPU time, or memory bandwidth.

Lighting is a good example. Hitman relied heavily on pre-baked bounce lighting. 007 First Light shifts to fully dynamic global illumination implemented through software ray tracing and dense light-probe data. The game does not use hardware ray tracing at launch, but software RT GI still costs real performance. It allows lighting to react when an object changes, cover is damaged, a light breaks, or a scene transitions from bright exterior space to a darker interior.

Then there is Smolder, Glacier’s proprietary smoke and fog system. Burning spaces, dusty interiors, muzzle smoke, underwater scenes, and light shafts all benefit from richer volumetrics, but volumetric rendering can eat a frame budget alarmingly quickly. On Switch 2, the likely pressure points are lower sample counts, reduced volumetric resolution, shorter effect draw distances, and stricter limits on how many expensive effects run at once.

Crowds will also be managed more tightly. Glacier has always been strong at filling an environment with people and letting them react to chaos, but every active civilian, guard, camera, and physics object has a cost. The Switch 2 profile reduces the number of agents active per region and limits simulation complexity as bricks stream in. A busy reception hall may look less populated than the same area on PS5, but that is preferable to frame-time spikes whenever Bond enters a crowd-heavy scene.

The Frame Graph Helps the Bigger Consoles, But It Does Not Create Free Performance

On PlayStation 5, Glacier’s new Frame Graph can schedule up to four asynchronous compute pipelines. That lets the GPU overlap work where possible: global illumination, visibility calculations, post-processing, and other rendering tasks do not always need to queue up one after another like cars at a single toll booth.

It is one reason PS5 and Xbox Series X can support both a 30fps Quality mode and a 60fps Performance mode. But asynchronous compute is not magic. It works when a GPU has spare resources that can be used in parallel. Once the GPU is fully saturated, piling on more parallel work can simply create contention. That is why the lower-spec Xbox Series S is 30fps-focused despite sharing the same core engine technology.

The Switch 2 version faces an even tighter balancing act. Its dedicated Glacier profile is built around reduced rendering demands before the frame begins: smaller bricks, earlier prefetching, lower geometry density, tighter effects budgets, and conservative simulation limits. That is a more reliable route to 30fps than trying to rescue an overloaded scene after the GPU is already struggling.

PC Players Get the Broadest Options, With One Awkward Catch

On PC, 007 First Light uses DirectX 12 only. That matches Glacier’s updated rendering design and its Frame Graph-based workload management, but it also means there is no DX11 or Vulkan fallback for older configurations. The game is built for modern APIs, modern drivers, and modern GPU scheduling.

GeForce RTX owners can use DLSS 4.5 Dynamic Multi Frame Generation, with multipliers up to 6× available on supported hardware. FSR 3.15 is also supported, but the launch build does not offer equivalent frame generation for AMD or Intel hardware. That leaves RTX systems with the widest performance toolkit, particularly at high resolutions.

IO Interactive and NVIDIA have also planned a path-tracing update with DLSS Ray Reconstruction for summer 2026. The launch version has no hardware ray tracing, which is a sensible call for a game already handling real-time GI, streaming, volumetrics, animation, and dense AI. Path tracing will be a PC showcase feature, not the baseline visual experience that defines the console versions.

What the Switch 2 Delay Signals

007 First Light launched for PS5, Xbox Series X|S, and PC on May 27, 2026, before its global launch communication on May 28. The Nintendo Switch 2 version was originally placed in a summer 2026 window, then moved to later in 2026. That shift is understandable given the work involved.

The Switch 2 release needs more than a lower resolution and a 30fps cap. IO has to validate every streamed transition, every mission route, every crowd-heavy encounter, every cinematic sequence, and every memory spike under the platform’s smaller resource envelope. Glacier’s Virtual Platforms make that process more structured, but they do not erase the testing burden.

The upside is that IO is doing this work on an engine refresh that was designed around scale profiles from the start. If the final Switch 2 build maintains frame pacing and avoids visible asset pop-in during Bond’s larger transitions, a stable 30fps version will be a credible result. A portable release does not need PS5-level pixels to preserve the mission flow, stealth systems, animation work, and systemic chaos that make Glacier games compelling.