Clair Obscur Expedition 33 Lag Fix: How to Stop Stuttering and FPS Drops on PC

You just started Clair Obscur: Expedition 33, the prologue looks stunning, and then the stuttering hits. Every new area, every cutscene transition, every particle effect triggers a freeze that lasts anywhere from 50 to 200 milliseconds. You are not alone. With over 8 million copies sold and a recent anniversary update bringing new players in, the Clair Obscur Expedition 33 lag fix is one of the most searched performance topics in gaming right now.

The good news: most of the stuttering in Expedition 33 is caused by Unreal Engine 5’s shader compilation pipeline, and there are concrete steps you can take to eliminate it. This guide walks you through every fix in order, from the fastest setting changes to deeper engine tweaks that most guides skip entirely.

Table of Contents

1. Why Expedition 33 Stutters So Much
2. Quick Fixes: Settings That Make an Immediate Difference
3. Fix the Shader Compilation Stutter
4. VRAM Management: The Hidden Culprit
5. Engine.ini Tweaks for Smoother Frametimes
6. Unlock the 30 FPS Cutscene Cap
7. Windows and Driver Optimizations
8. FAQ

Why Expedition 33 Stutters So Much

Clair Obscur: Expedition 33 was built on Unreal Engine 5, using Nanite for geometry and Lumen for global illumination. Both systems look incredible, but they demand shader compilation in real time when you encounter new visual effects for the first time.

Here is what happens under the hood: the game runs a shader precompilation step on first launch (that loading bar you see for 1 to 2 minutes). But it does not compile every shader upfront. Instead, UE5 uses a “pipeline state object” (PSO) cache that grows as you play. When you enter a new area with effects your GPU has not seen yet, the engine compiles those shaders on the fly, causing a 50 to 200ms hitch.

This is why the prologue stutters the most. You are encountering dozens of new materials, particle systems, and lighting setups in rapid succession. By the time you reach the open world sections, most shaders are already cached, and the game stabilizes significantly.

Understanding this mechanism is important because it means not every fix applies equally. If your stuttering is only in the first hour, you need shader cache solutions. If it persists throughout, you likely have a VRAM or streaming bandwidth issue.

Quick Fixes: Settings That Make an Immediate Difference

Before touching any config files, adjust these in-game settings:

Resolution scaling (DLSS/FSR/TSR): Enable your GPU’s upscaler at Quality mode. TSR (built into UE5) works on all GPUs and delivers a 25 to 30% FPS gain with minimal visual loss. DLSS users should select Quality or Balanced.

Shading Quality: Drop from Epic to High. This reduces the number of shader permutations the engine needs to compile, directly reducing stutter frequency.

Shadow Quality: High instead of Epic. Lumen’s software ray tracing for shadows is one of the heaviest workloads.

Texture Quality: Match this to your VRAM capacity. 8 GB VRAM cards should use High at 1080p. Only 12 GB+ cards should attempt Epic at 1440p or above.

Motion Blur: Turn it off. It adds GPU overhead during camera movement (exactly when you need frames most) and masks the visual feedback you need to spot remaining stutter.

Frame Rate Cap: Set this to your monitor’s refresh rate minus 3 (so 57 for a 60Hz display, 141 for 144Hz). Use RTSS (RivaTuner Statistics Server) for the cap rather than the in-game limiter, as RTSS produces tighter frametimes.

These changes alone solve the problem for roughly 40% of affected players, particularly those who were running settings above what their hardware could sustain.

Fix the Shader Compilation Stutter

This is the core issue for most players. Here is how to force a complete shader rebuild:

Step 1: Delete the existing shader cache

1. Close the game completely
2. Navigate to %LOCALAPPDATA%\ClairObscur\Saved\PipelineCaches
3. Delete everything inside this folder
4. Also clear your GPU driver’s shader cache:
   – NVIDIA: Open NVIDIA Control Panel, go to Manage 3D Settings, find Shader Cache Size, set it to Unlimited, then navigate to %LOCALAPPDATA%\NVIDIA\DXCache and delete its contents
   – AMD: Open AMD Software, go to Graphics, find Shader Cache, toggle it off, reboot, toggle it back on

Step 2: Let the game rebuild completely

1. Launch the game and wait at the main menu. Do not skip the “Compiling Shaders” progress bar.
2. After it completes, load your save and stay in the first area for 2 to 3 minutes without moving. This allows background shader compilation to finish.
3. Play through areas you have already visited before entering new zones. This “warms” the cache without triggering new compilations during combat.

Step 3: Prevent cache invalidation

Your shader cache gets wiped every time you update your GPU driver. After a driver update, repeat Steps 1 and 2 before playing. Alternatively, if the new driver does not fix a specific game issue for you, consider staying on your current driver until the next major game patch.

According to Digital Foundry’s PC tech analysis, shader compilation stutter in UE5 titles is the single most common performance complaint across all 2025 and 2026 releases built on the engine.

VRAM Management: The Hidden Culprit

If your stuttering persists beyond the first hour, VRAM saturation is likely the problem. Expedition 33 is extremely VRAM hungry because Nanite meshes and Lumen light probes both consume video memory aggressively.

Here is a quick reference for what your card can handle:

VRAM	Max Resolution	Texture Quality	Expected FPS (High Settings)
6 GB	1080p	Medium	45 to 55
8 GB	1080p	High	55 to 70
10 GB	1440p	High	50 to 65
12 GB+	1440p/4K	Epic	60+ (with upscaling)

When VRAM fills up, the game starts swapping textures between system RAM and VRAM. Each swap causes a micro-stutter. You can monitor this in real time using MSI Afterburner’s VRAM usage overlay. If you are consistently above 90% VRAM utilization, drop Texture Quality one tier.

The most impactful VRAM savings come from:

1. Texture Quality: Epic to High saves roughly 1.5 GB
2. Shadow Quality: Epic to High saves roughly 400 MB
3. Enable texture streaming: Make sure this is ON (it is by default). Disabling it loads all textures at maximum resolution immediately, which can overflow VRAM.

Engine.ini Tweaks for Smoother Frametimes

For players comfortable editing config files, these Engine.ini modifications target the specific systems causing stutter in Expedition 33.

Navigate to %LOCALAPPDATA%\ClairObscur\Saved\Config\Windows\Engine.ini and add the following sections:

[SystemSettings]
r.Streaming.PoolSize=4096
r.Streaming.MaxTempMemoryAllowed=256
r.ShaderPipelineCache.Enabled=1
r.ShaderPipelineCache.ReportPSO=1

[/Script/Engine.StreamingSettings]
s.AsyncLoadingThreadEnabled=True
s.EventDrivenLoaderEnabled=True

[ConsoleVariables]
r.GTSyncType=1
r.FinishCurrentFrame=0

What these do:

• PoolSize=4096: Allocates 4 GB for texture streaming, preventing sudden texture swaps that cause hitches
• MaxTempMemoryAllowed=256: Limits temporary memory spikes during area transitions
• ShaderPipelineCache.Enabled=1: Ensures the PSO cache is active and persistent
• AsyncLoadingThreadEnabled: Moves asset loading to a dedicated thread so it does not block the render thread
• GTSyncType=1: Aligns GPU and CPU frame submission to reduce frametime variance
• FinishCurrentFrame=0: Prevents the CPU from waiting on the GPU to finish each frame, which reduces input latency and smooths frametime delivery

After saving, set Engine.ini to read-only so game updates do not overwrite your tweaks.

Unlock the 30 FPS Cutscene Cap

Expedition 33 locks cutscenes to 30 FPS by default. If you are running at 60+ FPS during gameplay, the sudden drop to 30 during cutscenes feels like severe stuttering (even though it is technically consistent framing).

The community fix uses a mod called ClairObscurFix on Nexus Mods that removes the cutscene cap and also fixes ultrawide aspect ratio issues. Install it by dropping the ASI files into your game’s Binaries folder.

If you prefer not to mod, you can partially work around this by enabling VSync in your GPU driver’s control panel. This smooths the transition between 60 FPS gameplay and 30 FPS cutscenes by preventing screen tearing during the switch.

Windows and Driver Optimizations

These OS-level changes reduce background interference that amplifies UE5’s stutter:

Disable Memory Integrity (VBS): Windows 11 enables Virtualization-Based Security by default. It reduces gaming performance by 5 to 10% in shader-heavy titles. Disable it in Windows Security, then Device Security, then Core Isolation.

Disable MPO (Multi-Plane Overlay): MPO causes frame delivery issues in DX12 titles. Open Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm, create a DWORD called OverlayTestMode and set it to 5.

GPU Driver: Use the latest Game Ready (NVIDIA) or Adrenalin (AMD) driver. After installing, always do a clean installation to reset the shader cache.

Set game priority to High: Open Task Manager while the game is running, find the process, right-click, and set priority to High. This gives the game more CPU scheduling time over background processes.

Disable Xbox Game Bar: Settings, then Gaming, then Xbox Game Bar, toggle off. The overlay’s capture pipeline steals GPU cycles even when you are not recording.

For additional Windows optimizations, see our full Windows 11 gaming optimization guide.

FAQ

Why does Clair Obscur: Expedition 33 stutter so much in the prologue?

The prologue introduces dozens of new materials, particle effects, and lighting setups that your GPU has never compiled shaders for. Unreal Engine 5 compiles these shaders on the fly, causing 50 to 200ms freezes each time. The stuttering naturally decreases as you progress because most shaders get cached after the first encounter.

How much VRAM do I need for Clair Obscur: Expedition 33?

You need at least 8 GB of VRAM for High settings at 1080p without constant texture swapping. For 1440p at High settings, 10 GB is the minimum. Epic quality at 1440p or 4K requires 12 GB or more. Cards with 6 GB should use Medium textures and enable FSR or TSR for acceptable performance.

Does deleting the shader cache fix stuttering in Expedition 33?

Yes, but only if your existing cache is corrupted or was built on a previous driver version. Delete the contents of %LOCALAPPDATA%\ClairObscur\Saved\PipelineCaches, clear your GPU driver shader cache, then relaunch the game and let it fully recompile before loading a save.

Why are cutscenes locked to 30 FPS in Expedition 33?

The developers locked cutscene playback to 30 FPS for cinematic presentation. This feels like stuttering when transitioning from 60+ FPS gameplay. You can remove this cap using the ClairObscurFix mod from Nexus Mods, which unlocks cutscene framerate and fixes ultrawide aspect ratios.

Will the Engine.ini tweaks get me banned or break my save?

No. Expedition 33 is a single-player RPG with no anti-cheat system. Engine.ini modifications only affect rendering and streaming parameters. They cannot corrupt save files. Set the file to read-only after editing so game patches do not overwrite your changes.

What to Do Next

If you have followed every step in this guide and still experience occasional hitches, the remaining stutter is almost certainly from asset streaming during area transitions. This is a known UE5 limitation that Sandfall Interactive is aware of. Installing the game on an NVMe SSD (not a SATA SSD or HDD) gives the streaming system the bandwidth it needs to load assets without blocking the render thread.

For players dealing with high ping or network lag in online co-op sessions, the fixes above will not help because that is a network issue rather than a rendering one. Check our packet loss fix guide if you are seeing disconnections during multiplayer.

The performance gets dramatically better after the prologue. Stick with it, apply the shader cache fix, and you will be running smoothly through Lumiere and beyond.