Marvel Rivals stuttering fix
How to fix Marvel Rivals stuttering and frame-time spikes
Last updated
How do you fix Marvel Rivals stuttering?
Almost all stutter in this game comes from three Unreal Engine 5 sources: shader compilation on first encounter, Lumen global illumination pushing frame times past your refresh interval, and VRAM eviction on cards carrying the high-resolution texture pack. Each has a specific fix, and general settings tuning will not address any of them.
An Unreal Engine 5 title, so its two dominant performance costs are Lumen global illumination and shader compilation -- both of which have specific, known fixes rather than general tuning.
Recommended Marvel Rivals settings
| What you observe | Cause | Fix |
|---|---|---|
| Hitching in the first match after an update, then smooth | Shader compilation | Expected. Play through once to build the cache. If it persists, clear the DirectX shader cache and rebuild. |
| Frame time spikes during busy team fights | Lumen global illumination | Turn Lumen GI off or set SSGI Low. This is the dominant per-frame cost. |
| Stutter that worsens the longer you play, on an 8GB card | VRAM eviction | Uninstall the high-resolution texture pack and drop texture quality one step. |
| Sudden stutter mid-session after weeks of stability | Stale or corrupted shader cache | Clear the DirectX Shader Cache via Disk Cleanup, or the vendor cache in the driver control panel. |
| Rubber-banding, or stutter only in matches | Network | Check packet loss and server region. Not a rendering problem. |
| Setting | Recommended | Why |
|---|---|---|
| Global Illumination | Off or SSGI Low | Removes the largest and most variable per-frame cost in the game. |
| Frame Rate Limit | Your worst-case rate | Converts a swinging frame rate into a steady one, which is what stutter actually is. |
| High-Resolution Texture Pack | Uninstall on 8GB cards | Eviction stutter is very commonly mistaken for a GPU limit. |
| Hardware-accelerated GPU scheduling | Test both ways | Helps on some configurations and hurts on others. Judge on a frame-time graph. |
Shader compilation stutter is expected once, not forever
Unreal Engine 5 compiles shaders the first time it needs them. After a game update, a driver update, or a cache clear, the first session will hitch as that work happens. That is the engine behaving normally.
What is not normal is the same hitching persisting across many sessions. If it does, the cache is not being written or is being invalidated -- clear it explicitly and rebuild, and check that the drive it lives on is not full.
Check VRAM before blaming the GPU
When VRAM fills, the driver starts evicting textures and re-uploading them mid-frame. That produces exactly the symptom people describe as stutter, and it gets worse the longer a session runs as memory fragments.
Any overlay that reports VRAM usage will show this. If you are sitting above about 90% during play, that is your problem, and reducing texture quality or removing the optional texture pack fixes it directly.
What do people get wrong when tuning Marvel Rivals?
- Judging shader compilation stutter on the first session after an update instead of the second.
- Lowering every setting except Lumen global illumination, which is the one actually costing the frame time.
- Running the high-resolution texture pack on an 8GB card and concluding the card is too slow.
- Treating network rubber-banding as a rendering fault and tuning graphics settings to fix it.
- Changing several settings between matches so no single change can be attributed.
What else is worth knowing?
- Watch a frame-time graph rather than the FPS counter. Stutter is a frame-time problem and the counter averages it away.
- Play one full match between changes. Stutter is intermittent and a single quiet minute proves nothing.
- If you clear the shader cache, expect the next session to be worse before it is better.
- Check VRAM usage during a busy fight, not in the menu. The menu is not representative.
Can you apply the Windows-side changes automatically?
Everything above that lives inside Marvel Rivals you set yourself — no tool should be changing your in-game options for you. The Windows-side items are a different matter: power plans, background processes, service start types and network adapter settings are the same work on every machine, and working through them by hand while keeping track of what you altered is the tedious part.
JINSHI Tweaks is a one-time purchase that applies those Windows-side changes in one pass, creates a System Restore Point first, and lets each one be reversed individually. It does not touch game files, read game memory, inject into any process, or install a driver. Our settings reference documents what each change does.
Marvel Rivals performance: frequently asked questions
Why does Marvel Rivals stutter after an update?
Unreal Engine 5 recompiles shaders when the game or driver changes, and that compilation happens on first encounter. The first session after an update will hitch. It should settle from the second.
Does clearing the shader cache fix stuttering?
For stutter that appeared suddenly, or that persists across many sessions, yes. Expect the session immediately after clearing to be worse while the cache rebuilds.
Is Lumen the cause of my stutter?
It is the largest and most variable per-frame cost in the game, so it is the first thing to turn off when frame times spike during busy scenes. Test with it off for a full match.
Why does it get worse the longer I play?
That pattern points to VRAM. As memory fills and fragments, the driver evicts and re-uploads textures mid-frame. Check VRAM usage during a fight and reduce texture quality if it is near capacity.