Marvel Rivals Stuttering Fix (Season 11): Stop FPS Drops in Team Fights
By Tier1Settings Updated Published
On this page
Marvel Rivals stutters mainly because of Unreal Engine 5 shader compilation, VRAM pressure and CPU-bound frame-time spikes in team fights, so the fixes that work are letting shaders cache, keeping VRAM headroom, a clean GPU driver, a stable frame cap and, since Season 11, NetEase’s experimental CPU-optimized client. This guide was updated on 15 November 2026 for Version 20261113 (Season 11 “Doomsday”) and walks through the fastest fixes to stabilize your 1% lows and make fights feel consistent.

Use this as a checklist before you start changing random settings.
What Marvel Rivals stutter usually looks like
If your average FPS is fine but the game still feels bad, you’re dealing with frame-time spikes, not low FPS. Common symptoms:
- brief freezes the first time you see a new hero or ability
- hitching when ultimates and effects go off
- traversal stutter moving across the map
- inconsistent aim feel even at high FPS
- worse performance right after a patch or driver update
That’s a different problem than a general best settings guide solves.
New in Season 11: try the experimental CPU-optimized client
Version 20261113 (Season 11, 13 November 2026) added an Experimental Feature: Client CPU Performance Optimization. According to NetEase’s patch notes, the client was rebuilt with a new Intel compiler and PGO (Profile-Guided Optimization), and enabling it “is expected to boost CPU performance by approximately 10%, further improving frame rate stability in complex combat scenarios.”
That targets exactly the team-fight frame drops most players report, because those are usually CPU-bound: many heroes, abilities and ultimates at once.
- Open the Marvel Rivals PC launcher and switch the experimental CPU optimization on.
- Let the launcher download and apply the optimized client.
- Play a few matches with the same settings you used before, so you’re comparing like with like.
- If you get crashes or anything odd, switch it back off. NetEase labels it experimental and asks players to report stability issues to Customer Support.
The same patch also fixed an occasional stutter during Blade’s Daywalker Dash. That was a hero animation bug, not a performance problem, so it won’t change your frame rate.
Change these in-game settings first
| Setting | Recommended value |
|---|---|
| Display Mode | Fullscreen |
| V-Sync | Off |
| Frame Rate Limit | Cap at or just below refresh |
| Global Illumination | Low |
| Reflection Quality | Low |
| Shadow Detail | Low |
| Texture Quality | Medium if VRAM is limited |
| Upscaling | DLSS/FSR Quality |
| Frame Generation | Off while troubleshooting |
UE5 games hitch badly under VRAM pressure. If your GPU has 8 GB or less, don’t max textures just because average FPS looks fine — that’s a top cause of ugly hitching.
Let shader compilation finish
A lot of early-match hitching in UE5 games is shader-related.
- After a game or driver update, launch and let the initial shader process settle.
- Play one full match before judging performance — first-time effects compile as you see them.
- If stutter spikes after every patch, update your GPU driver and test again.
Update or clean-install your GPU driver
Driver issues are a top cause of new stutter after an update.
- Install the latest stable driver for your GPU.
- If stutter started right after a driver update, roll back to the previous stable version.
- Reset driver settings to default before layering custom tweaks.
- Turn off extra overlays and recording while troubleshooting.
Check VRAM, RAM, and background apps
Marvel Rivals gets choppy when your system runs out of headroom.
Watch for
- GPU memory near full
- high system RAM use before the match starts
- Discord, browser, capture tools, and overlays all running together
Fast fixes
- Close browsers, launchers, and monitors you don’t need.
- Disable Steam/Discord overlays.
- Lower Texture Quality one step.
- Reboot before long sessions if memory use is messy.
Install Marvel Rivals on an SSD
UE5 streams a lot of data, so slow storage causes traversal hitching. Use an NVMe SSD if possible, keep 15–20% free space, and don’t download or copy large files while playing.
Windows fixes worth trying
- Enable Game Mode.
- Disable unnecessary startup apps.
- Set Windows power plan to High Performance.
- On laptops, force the correct discrete GPU.
- Consider disabling VBS for extra CPU headroom.
For smoother input and frame consistency, also read The Ultimate Guide to Timer Resolution for Gaming (and grab Tier1Suite) and How to Minimize Input Delay for Competitive Gaming.
When to lower your frame cap
Uncapped isn’t always smoothest. If FPS swings wildly in team fights, a stable cap reduces frame-time spikes:
141 FPSfor 144 Hz237 FPSfor 240 Hz117 FPSfor 120 Hz
Pick the cap that feels steadiest in real fights, not the biggest benchmark number.
If stutter started after an update
- If you turned on the experimental CPU-optimized client, switch it off and test again.
- Verify game files.
- Let shaders rebuild.
- Reset aggressive driver overrides.
- Lower textures and effects one step.
- Wait for hotfixes if many players report the same issue.
Related guides
- Best Marvel Rivals Settings for FPS and Performance
- Marvel Rivals DLSS, FSR, and Frame Generation Best Settings
- How to Minimize Input Delay for Competitive Gaming
- The Ultimate Guide to Timer Resolution for Gaming + Tier1Suite
If Marvel Rivals is stuttering, fix shader behavior, VRAM pressure, and background conflicts before chasing obscure tweaks. Most players get the biggest gain from lower Lumen settings, clean drivers, a stable frame cap and, if your CPU is the limit in team fights, the Season 11 experimental client.
Frequently asked questions
What is the Client CPU Performance Optimization in Marvel Rivals Season 11?
It is an experimental client added in Version 20261113 (Season 11, 13 November 2026). NetEase rebuilt the game client with a new Intel compiler and Profile-Guided Optimization, and says enabling it is expected to boost CPU performance by about 10% and improve frame-rate stability in complex fights. You turn it on in the PC launcher, which then downloads the optimized client. It is experimental, so NetEase asks players to report any stability issues to Customer Support.
Why does Marvel Rivals stutter when I see a new hero or ultimate for the first time?
Marvel Rivals runs on Unreal Engine 5 and compiles shaders the first time new effects appear on screen. That one-frame freeze when a hero ults for the first time is traversal shader compilation, not a hardware problem. It mostly goes away after you have played enough matches for those shaders to be cached.
How do I fix Marvel Rivals FPS drops during team fights?
Lower Global Illumination to Low, turn Reflection Quality to Low, and use DLSS or FSR at Quality preset. These are the settings that cause the biggest frame-time spikes during multi-hero ultimate exchanges. If your GPU has 8 GB or less of VRAM, also drop Texture Quality to Medium to prevent VRAM pressure from turning into hitching.
Does Marvel Rivals stutter on a good PC?
Yes. UE5 traversal stutter and shader compilation can affect even high-end systems because the issue is engine behavior, not raw GPU power. Strong hardware reduces the duration and frequency of spikes but does not eliminate them entirely. Using a frame cap slightly below your refresh rate and keeping VRAM headroom free produces the most consistent feel.
Is Marvel Rivals stutter a VRAM problem?
It often is, especially on GPUs with 8 GB or less. Unreal Engine 5 hitches badly when it exceeds available VRAM rather than dropping FPS cleanly. If you notice spikes during team fights on maps with heavy effects, lower Texture Quality by one step and watch GPU memory use with an overlay — if it was near full, that was the cause.
Will reinstalling Marvel Rivals fix the stuttering?
Rarely. Reinstalling does not rebuild shaders faster or fix driver conflicts. Instead, verify game files through the launcher after a patch, let shaders rebuild over one full match, and reset any aggressive driver overrides to default. If stutter started after a specific patch, waiting for a hotfix is often more effective than reinstalling.