An NVIDIA RTX 5090, the fastest consumer GPU you can buy, holds a capped 60 FPS at 4K in Halo: Campaign Evolved while its own utilization sits at roughly 50 percent. That single number tells you almost everything about how this remake behaves on PC. The graphics card is idling. Something else is setting the ceiling, and on most rigs that something is your processor.
Early access opened today, July 23, 2026 at 8:00 a.m. PDT for Premium and Collector’s Edition buyers, with the full launch on July 28. If you jumped in this morning and your frame rate is bouncing around despite a card that should crush a 25-year-old shooter, you are not imagining it and you did not break anything. This is a heavy Unreal Engine 5 title wearing a nostalgic skin, and the fixes that help are not the ones people reflexively reach for.
What this remake actually is under the hood
Halo: Campaign Evolved is a full ground-up remake of the original Halo: Combat Evolved campaign, and it drops the Slipspace engine entirely in favor of Unreal Engine 5. That decision brings Lumen for dynamic global illumination, Nanite for virtualized geometry, and hardware ray tracing that the game leans on for lighting and reflections. Art director Chris Matthews has pointed to Lumen and Nanite as the reason the remade environments can be more interactive and detailed than the 2001 original ever allowed.
It is campaign only. There is no PvP multiplayer here. What it does have is four-player online co-op with crossplay and shared progression across Xbox, PlayStation 5, and PC, plus two-player split-screen on consoles. Hold onto that co-op detail, because it changes which of your problems are local and which live on the network.
The published PC requirements set expectations honestly for once. The 1080p/60 minimum asks for an RTX 2060 Super, RX 6600, or Arc A580 paired with a Ryzen 5 3600 or Core i7-10700K and 16GB of RAM. The 1440p/60 tier wants an RTX 3070 or RX 7600 with a Ryzen 7 5700X or Core i5-12600K. The 4K/60 Ultra tier demands an RTX 4080 and 32GB of RAM. Every tier requires 100GB of free space on an SSD, and that SSD requirement is not a suggestion.
The bottleneck is your CPU, and the benchmarks prove it
Here is the part generic “boost your FPS” guides get wrong for this specific game. They tell you to lower resolution and turn down textures to take load off your GPU. In a CPU-bound title, that barely moves the number, because the GPU was never the thing holding you back.
Look at what the preview hardware actually did. An RTX 5090 paired with a Ryzen 9 9950X3D, running native 1440p on the Ultra preset with DLAA and no upscaling, sat around 120 FPS in the opening area, dropped to roughly 100 outdoors, and fell into the 90s during the tank sequence. At 4K it held a capped 60 while the GPU coasted at about 50 percent load. When the most powerful GPU on the market is half asleep, more GPU is not your answer.
Now the mid-range picture. A system with an RTX 4060, a Ryzen 5 5600X, and 16GB of RAM could not hold a consistent 60 FPS at 1440p even with DLSS set to Balanced. The culprit, per the preview, was CPU throttling that showed up hardest when the screen filled with enemies. A firefight with a dozen Covenant on screen is exactly when the simulation load spikes and the processor becomes the wall. For contrast, an Xbox Series X ran the game at around 1080p with dynamic resolution and ray tracing enabled and held 60 FPS with minimal stutter, which means the console produced smoother gameplay than a mid-range PC that costs more than the console does.
I spent twenty years in IT operations, part of it in Saskatchewan telecom, and this is the same trap I watched teams fall into with overloaded servers: they kept throwing more of the resource that was already sitting idle at the problem while the actual constraint went untouched. Match the fix to the bottleneck. In Halo: Campaign Evolved, that means CPU-side and streaming-side moves come first.
Settings that actually move the number
Because the engine is CPU-limited on most systems, the highest-value changes are the ones that either reduce simulation and draw-call overhead or let the GPU carry frames the CPU cannot. Start here.
| Setting | Set to | Why it helps |
|---|---|---|
| Upscaling (DLSS / FSR / XeSS) | Quality at 1440p, Balanced at 4K | Renders internally lower and reconstructs, easing GPU load and freeing headroom |
| Frame Generation | On, if your CPU is the limit | Inserts generated frames the CPU never had to simulate; ideal for CPU-bound scenes |
| Global Illumination (Lumen) | Medium | One of the heaviest UE5 features; medium keeps the mood, cuts the cost |
| Shadow Quality | Medium | Softer edges you will not notice mid-firefight, frames you will |
| GPU Async Compute | Off if CPU-bound | The developer notes async gives little when the GPU is already waiting on the CPU |
| Resolution Scale | Leave to upscaler | Manual downscaling does little in a CPU-limited title |
| Frame Rate Limit | Just under your refresh | Stops the GPU sprinting for frames the CPU can’t feed, smoothing frame times |
| Textures | High if VRAM allows | Cheap on FPS when you have the VRAM budget |
Two of those deserve a note. Frame Generation is the single most effective toggle for a CPU-bound game, because the interpolated frames sidestep the processor entirely. The trade is input latency, since the inserted frames are predicted rather than tied to your stick and trigger, so competitive twitch play suffers more than a single-player campaign does. For a Halo campaign run, most players will happily take the smoothness. The preview build did not expose Frame Generation or DLSS 4, but both are slated for the retail release, so the launch build should give you the lever the preview lacked.
The GPU async compute note comes straight from the official optimization guidance: in a CPU-bound scenario, leaving async compute on can slightly reduce performance because the GPU is already stalled waiting on the CPU and the extra scheduling work buys nothing. If you are GPU-bound instead, which is rare here outside native 4K, leave it on.
If you want the broader framework for telling a CPU bottleneck apart from a GPU one before you start flipping switches, our guide to high CPU usage while gaming walks through reading the load in real time.
Co-op run snapping across regions?
Four-player crossplay means one teammate three time zones away can drag the whole session’s latency. When the route to the host is the weak link, WTFast reroutes your game traffic through optimized servers and cuts ping 30 to 50 percent for most players.
The first-hour stutter is shaders, and an NVMe drive is not optional
If your worst hitches happen on a fresh install or right after a GPU driver update, that is shader compilation, not a broken setting. Modern UE5 games compile shaders the first time you encounter a new effect, weapon, or area, and each first-time compile is a micro-freeze. It fades as the cache fills, so the counterintuitive fix is to play through an area once and let it settle rather than panic-tweaking during the roughest hour.
Storage is where this game is unusually strict. The 100GB SSD requirement exists because Halo: Campaign Evolved streams assets aggressively, and on Windows 11 with a DirectStorage-compatible NVMe drive it can decompress those assets on the GPU without routing them through the CPU. That matters twice over in a CPU-bound title: it shrinks load times and it cuts the traversal stutter you feel when the engine streams in a new chunk of a level. Running the game off a SATA SSD works, but an NVMe drive on Windows 11 is where the streaming hitches genuinely quiet down. A mechanical hard drive is not viable here, full stop.
A few more streaming-side moves that pay off:
- Install on your fastest NVMe drive, not a secondary SATA SSD or an external.
- Update to the launch-day GPU driver before you start. UE5 stability leans heavily on current drivers, and a driver install that wipes your shader cache is worth doing before your first real session so the recompile happens once.
- Keep 16GB as the floor and 32GB as the real target. The Ultra tier lists 32GB for a reason, and a texture-streaming UE5 game punishes a tight memory budget with stutter.
For the full symptom-to-cause map that separates shader hitches from traversal freezes and background-app spikes, our rundown of every cause of in-game lag is the reference I would keep open.
Co-op is the only place the network touches you
Solo, this is a rendering and CPU story. The moment you start a four-player crossplay run, latency enters the picture, and no graphics setting fixes a network problem. If your character rubberbands, warps, or your teammates teleport, that is the connection between players, not your shadow quality.
Crossplay makes this trickier than a same-platform lobby. Shared progression pulls four players together regardless of platform or region, and whoever is farthest from the session host pays a ping tax the whole run. The fixes, in the order I would try them:
- Get every player on a wired connection. Wi-Fi micro-drops are the most common cause of co-op warping, and a single wireless teammate can make the whole squad feel unstable. Here is why Ethernet still beats wireless for low ping if you need to make the case to a friend.
- Rule out packet loss before blaming the game. Even 1 percent loss will make a co-op session feel like it is teleporting you around. Our breakdown of why packet loss breaks games and how to find it has the diagnostic steps.
- Understand who is hosting. In connected co-op, the host’s connection quality sets the ceiling for everyone. If one player has a rough line, how peer connections and hosting shape co-op lag explains why and what to do about it.
Distance is the factor people underestimate. A four-player group spread across regions is asking a lot of the routing between them, and the farther apart you are, the more a cleaner path is worth testing before you assume the game is just broken.
Wired the whole squad and still warping?
When everyone is on Ethernet, packet-loss-free, and the crossplay run still stutters, the leftover problem is the route to the host across regions. A cleaner path is the fastest experiment left before you give up on the session.
What to change tonight
Halo: Campaign Evolved is a gorgeous remake with a heavy engine and a clear bottleneck. If it stutters on a fresh install, that is shader compilation and it fades as the cache fills. If it will not hold your target frame rate despite a strong GPU, that is your CPU carrying the simulation, so turn on Frame Generation, drop Lumen and shadows to Medium, disable async compute, and stop lowering resolution expecting it to help. If a co-op run warps, that is the network, so wire everyone, kill packet loss, and pay attention to who is hosting and where they are.
Do two things before your next session. Move the game to your fastest NVMe drive and install the launch-day driver, then flip Frame Generation on and Lumen to Medium. Those alone clear most of the launch-week complaints for a game whose GPU was never the problem.