- Home
- Guides
- Halo: Campaign Evolved
- Halo: Campaign Evolved: crashes, stuttering, and best PC settings, all the official fixes
Halo: Campaign Evolved: crashes, stuttering, and best PC settings, all the official fixes
In brief
Halo: Campaign Evolved suffers from crashes and stuttering well documented by Halo Studios, but the official documentation remains in English. This article translates the essential fixes, from recommended graphics drivers to PC settings that actually make a difference, to turn a chaotic experience into a stable game.
Halo: Campaign Evolved has been available since July 28, 2026, and has received only a single patch, the one from July 29 (build 2026.07.25.1112544). Thirteen days later, the official known issues page hasn't changed a single line: GeForce RTX 50 crashes on Keyes, stuttering cutscenes, and the The Two Betrayals blocker are all still current, and it's up to players to apply the workarounds.
Halo Studios does document nearly everything, with rare precision — but in English, across five support pages that nobody opens. Here's the summary in French, from the graphics driver to the choice between Quality and Performance on console.
Note: this documentation only exists in English. The setting names below are given as they appear there, with their function explained in French; the French client translates the menus, but the exact wording could not be verified against an official source.
Start with the graphics driver, the leading cause of crashes
The list of recommended drivers from Halo Studios isn't just for show: two of the most reported crashes since launch come from specific versions.
- NVIDIA: 610.88. GeForce RTX 50 cards can crash on the Keyes mission with drivers 610.47, 610.62, and 610.74. After installing 610.88, NVIDIA also recommends clearing the shader cache.
- AMD: 26.6.1. The July 29 patch stabilized the intro of The Maw when FSR is active on an AMD card running 26.6.2 or 26.6.4, but the version recommended by the studio remains 26.6.1.
- Intel: 32.0.101.8861 for Arc cards.
Since July 29, PC versions display a warning at launch when they detect an AMD or NVIDIA driver flagged as problematic: don't dismiss it out of habit, it's very likely the cause of your crash. To check your version, press the Windows key, type dxdiag, then go to the Display tab.
Known crashes and their official workarounds
| Symptom | Affected configuration | Workaround |
|---|---|---|
| Game closes before the startup screen | Certain 13th and 14th gen Intel processors (microcode issue predating the game) | Update the motherboard BIOS |
| Crash on the Keyes mission | GeForce RTX 50 on driver 610.47, 610.62, or 610.74 | Update to 610.88 and clear the shader cache |
| Crash on high-refresh-rate displays | AMD card, VSync enabled, and frame rate cap below a quarter of the refresh rate | Raise the frame rate cap or disable VSync |
| Image nearly frozen, only a few frames per second | XeSS + frame generation + active frame rate cap | Generate frames with DLSS or FSR, turn off frame generation under XeSS, or remove the frame rate cap |
| Unable to progress in The Two Betrayals | The Banshee was destroyed after the first generator | Reload an earlier checkpoint and leave the vehicle intact |
| Unable to connect, catastrophic performance, game freezes | Launching HaloCampaignEvolved.exe directly from the Steam folder | Launch from the Steam library instead |
The AMD case deserves a mention, because the official rule and the interface don't quite line up. The studio asks for a frame rate cap of at least a quarter of the refresh rate: 45 frames on a 180Hz display, 60 on a 240Hz display, 90 on a 360Hz display. But the built-in limiter only offers multiples of 30: on a 180Hz display, you'd need to aim for 60. If in doubt, disabling VSync fixes the issue right away.
Stuttering cutscenes: a matter of multiples of 30 Hz
This is the game's most visible flaw, and it affects PC as much as consoles. Cutscenes are locked to 30 frames per second: if the display's refresh rate isn't an even multiple of 30 Hz, they stutter. Three steps, in this order: set the screen to 60, 120, or 240 Hz, enable the TV's Game mode if it has one, then disable variable refresh rate (VRR), which makes the phenomenon worse on some setups.
Two more habits to adopt. Don't pause the game during a cutscene: when you come back, the picture and sound will be out of sync. On Xbox, putting the console to sleep during a cutscene is worse: the last frame stays burned onto every subsequent cutscene, and only a full console restart fixes it.

PC: the two settings that decide everything
The options are found under Video, in the Graphics section: press F1 on keyboard, the Menu button on Xbox, or the Options button on PlayStation 5. You can control everything with the quality preset, or adjust eight settings manually across four levels (Low, Medium, High, Ultra):
- Effects — density of explosions and particles; the lower settings strip out non-essential effects.
- Geometric — fidelity of shapes: characters, trees, rocks.
- Global Illumination — light bounces and indirect lighting.
- Lighting — quality, range, and quantity of shadows.
- Texture — texture resolution.
- Reflections — quality of surface reflections.
- Atmospheric — sky, clouds, fog.
- Post-processing — visor effects, lens flares, and other screen effects.
The studio states it plainly: Global Illumination and Lighting control the most demanding systems, and adjusting just these two is enough to gain a lot of frames. This is no accident: according to PCGamingWiki's findings, the game relies on Unreal Engine 5's hardware Lumen for global illumination, direct lighting, and reflections. These two sliders therefore control ray tracing. Textures and geometry, by contrast, cost little as long as video memory keeps up.
On Steam Deck and ROG Xbox Ally, an additional Very Low level appears, and the game then hides High and Ultra to preserve stability. Two secondary settings are worth a look: asynchronous compute, worth testing in both positions (it helps when the graphics card is the limiting factor, and costs a little when it's the processor), and field of view, adjustable from 65 to 125° according to PCGamingWiki, which comes at the cost of frames per second.

DLSS, FSR, XeSS, or TSR: which one to choose
Four scaling systems are available, each adjustable across five levels for which the studio provides the exact internal definition: Low renders at 33% of display resolution, Medium at 50%, High at 59%, Ultra at 67%, and Native at 100%.
| Technique | Compatible hardware | Good to know |
|---|---|---|
| DLSS (4th generation) | GeForce RTX 20 series and newer | The best rendering on NVIDIA; on Low with Low graphics settings, watch out for grain and oversized halos |
| FSR | All cards via FSR 3; FSR 4 automatically enabled on Radeon RX 9000 (RDNA 4) | The default choice outside of recent NVIDIA hardware |
| XeSS | All cards, optimized for Arc | Missing from the Microsoft Store and Xbox PC app versions: only available on Steam. Limited gains outside of Intel hardware |
| TSR | Universal | Ignores the quality setting: it uses a rendering resolution slider and a frame rate floor |
TSR is the useful special case. Its rendering resolution slider allows exceeding 100%, which amounts to supersampling when the machine has headroom, and its frame rate floor enables dynamic resolution: the engine lowers the internal resolution in demanding scenes, then raises it back up. The best safety net for a modest setup, provided you don't aim for an out-of-reach floor.
Frame generation and latency: who can enable what
Frame generation inserts a computed frame between two rendered frames. It smooths motion but adds latency and artifacts: it only makes sense if the game already runs well without it. Availability depends on the card / scaling technique pairing: DLSS from RTX 40 series onward, FSR from RTX 20 series, Radeon RX 5000 (RDNA 1) and Arc Alchemist onward, XeSS on the same generations. TSR does not support it at all, and the XeSS + frame generation combination officially causes glitches during cutscenes.
On the responsiveness side, the game offers NVIDIA Reflex, AMD Anti-Lag, and Intel Xe Low Latency. Enabling the one matching your card is especially recommended when frame generation is active, since that's what increases latency.
On console: Quality or Performance
Xbox Series X|S, PlayStation 5, and PlayStation 5 Pro offer two modes in the same Video menu: Quality targets 30 frames per second while prioritizing resolution, Performance targets 60 frames per second. All consoles also use dynamic resolution that adjusts in real time based on load. Image reconstruction goes through TSR, except on PlayStation 5 Pro, which uses PSSR2, Sony's in-house implementation.
For a shooter, Performance remains the default choice.
Two pitfalls unrelated to performance
Custom key bindings don't survive closing the game. The bug is acknowledged, and the workaround is counterintuitive: never overwrite a key that's already assigned. To put melee on the space bar, first move jump to a free key, then assign the space bar. Reassigning over an occupied key, and everything reverts to default settings on next launch.
Your saves are not on the Steam cloud. According to PCGamingWiki, Steam Cloud syncing is not enabled: saves are written locally to %LOCALAPPDATA%\Meteorite\Saved\SaveGames. It's the Microsoft account, via cross-platform progression, that acts as the online backup. Reminder: the July 29 patch wiped in-progress mission saves, while keeping unlocked missions and checkpoints intact. The next one could do the same.
What order to go about it
Four steps, if you only do four: the recommended driver for your card, the display set to a multiple of 30 Hz, Global Illumination and Lighting lowered by one or two notches before touching anything else, and scaling suited to your hardware.
No new patch has been announced and the list of known issues hasn't changed since July 29. If your problem isn't on it, the support team's report form is the only channel that actually feeds into the patch notes: those from July 29 cite community tickets as the source of several fixes, including the plasma pistol's charged shot, which no longer kills a player at full shield and full health.
Share this article
What's your main issue with Halo: Campaign Evolved on PC?
Frequently asked questions
My game crashes at the Keyes mission with an RTX 50, what should I do?
Cutscenes stutter a lot, is that normal?
Should I use DLSS, FSR, or XeSS?
Which graphics settings actually impact performance?
I can't connect to the game, why?
Key takeaways
- Updating your graphics driver is the first line of defense: NVIDIA 610.88, AMD 26.6.1, Intel 32.0.101.8861.
- Cutscenes stutter because they run at 30 frames per second, set your display to 60, 120, or 240 Hz to smooth them out.
- Global Illumination and Lighting are the two graphics settings that consume the most power, lowering these two sliders alone is enough to gain a huge amount of frames.
- Never launch the game by double-clicking HaloCampaignEvolved.exe: always go through the Steam library to avoid connection failures and catastrophic performance.
- DLSS excels on recent GeForce cards, FSR on AMD, TSR offers the best safety net for modest setups with its dynamic resolution.
Comments
No comments yet. Be the first to react!
Leave a comment
Similar guides
Latest articles
Rate Halo: Campaign Evolved
Click a star to rate
Android
iOS
Mac
Meta Quest 3
Nintendo Switch
Nintendo Switch 2
PC
PlayStation 4
PlayStation 5
PS VR2
Steam Deck
SteamVR
Xbox One
Xbox Series