Troubleshooting
Marvel Rivals Stuttering Fix: Stop Frame Drops
Most Marvel Rivals stuttering traces back to four things: shader compilation, asset streaming, VRAM overflow, and background CPU load. The fastest fixes are to disable the High-Resolution Texture Pack, cap your frame rate a few frames below your average, turn off Motion Blur and V-Sync, and switch on FSR or TSR upscaling. Those four changes clear the large majority of hitches on most systems.
This matters more than raw FPS because a steady 120 frames feels smoother than a jumpy 200. The hitches are what get you killed. If the game freezes for a split second when you turn a corner, when a new hero ults, or when you first load in, your average frame rate is fine and the real problem is frame pacing. The guide below fixes the causes in order of impact, so work top to bottom and stop once your 1% lows flatten out. New to this? Start with our guide to increasing FPS in Marvel Rivals .
Why is Marvel Rivals stuttering?
Marvel Rivals runs on Unreal Engine 5, and almost every stutter you feel falls into one of four buckets. Knowing which one you have saves you from changing settings that were never the problem.
Shader compilation stutter
UE5 compiles shaders the first time an effect appears. You feel short, one-time hitches early in a match or the first time you see a new hero's abilities. It usually smooths out as the game caches those shaders.
Traversal and streaming stutter
The engine loads map assets on the fly as you move. Turning a corner into a new area or watching a wall get destroyed can spike the frame time while textures stream in.
VRAM overflow stutter
When your graphics card runs out of video memory, textures get swapped in and out of system RAM. This is the aggressive, repeating stutter that never really goes away, and it is the most common cause on 6 GB and 8 GB cards.
CPU and background load
Chrome tabs, overlays, and shader-cache builds fight the game for CPU time. These show up as lag spikes that line up with something happening outside the game.
Fix 1: Disable the High-Resolution Texture Pack
This is the single biggest fix for VRAM overflow stutter. Marvel Rivals ships an optional High-Resolution Texture Pack that adds roughly 40 GB of ultra-detailed textures. On a mid-range card it pushes your VRAM over the edge, and that is exactly what causes the repeating corner-turn hitches.
- Right-click Marvel Rivals in your Steam Library and open Properties.
- Go to the DLC tab.
- Uncheck the High-Resolution Texture Pack.
- Let Steam remove the assets, then relaunch the game.
On Steam copies, the RivalsFPS.gg app exposes this same toggle under Settings so you can flip the HD Texture Pack off without digging through the launcher. On Epic and Loading Bay it shows those launchers' own steps instead.
Fix 2: Cap your frame rate
An uncapped frame rate sounds good, but it is a common source of frame drops. When your GPU runs flat out at 100 percent it has no headroom, so the moment a fight gets busy your frame time spikes and you feel it as a stutter. Capping a few frames below what your system can sustain keeps the frame time flat.
Set the cap a little under your typical frame rate. If you usually sit around 240, cap at 237. If you hover near 140, cap at 138. Set it in the game's own video settings, or in your GPU driver's control panel if you want the cap to apply everywhere.
Fix 3: Turn off the frame-eaters
A handful of effects cost frame time and pacing while adding almost nothing in a fast hero shooter. Turn these off first:
- Motion Blur. It smears the screen during exactly the fast flicks where you need clarity.
- Depth of Field. It blurs the background for no competitive benefit.
- V-Sync. It adds input latency, so leave it off and use a frame cap instead.
Then turn on an upscaler. Rendering at a lower internal resolution and letting FSR or TSR reconstruct the image is the biggest single frame-rate win most players can make, and it directly relieves the GPU pressure behind streaming stutter.
Fix 4: Clean up the Windows side
If the stutter lines up with things happening outside the game, the fix is on your system, not in the settings menu.
- Enable Hardware-Accelerated GPU Scheduling under Settings > System > Display > Graphics.
- Set your Windows power plan to High performance.
- Close Chrome, Discord streams, and anything doing heavy background work before you queue.
- Update your GPU drivers. A clean driver install clears a surprising amount of shader-cache stutter.
When settings are not enough
If you have worked through everything above and your 1% lows are still rough, the render load itself is too high for your hardware, and the settings menu has no lower gear left. What you can still change is the textures the engine draws. A graphic pack swaps the map and environment textures for simpler, faster ones, so there is less to shade every frame and less sitting in VRAM while the engine streams the next area in. Both of those sit directly behind traversal and overflow stutter.
The RivalsFPS.gg app builds packs on your own PC from your own game files, so nothing is downloaded, and only one is active at a time. Above the library sit six layer selects, Foliage Style, Foliage Res, Visual Effects, Characters, Decals and Shadows, each set to Default, Competitive, Balanced or Pretty, which lets you take the foliage and decals down without flattening the heroes you need to read. Our graphic pack settings guide covers what each layer costs. Be honest with yourself about the trade: the game looks different afterwards. The signature bypass that lets the game load a pack installs from the same app in one click.
On NVIDIA, the Quality tab
The RivalsFPS.gg app has a Quality tab that trades texture quality for FPS by writing the NVIDIA driver's own per-game profile for Marvel Rivals. It needs an NVIDIA graphics card. On AMD and Intel the tab still opens and says why it cannot work there: AMD's driver has no equivalent for DirectX 12 games, so in-game low settings plus FSR stay the answer on those cards. No game files are touched and nothing else on your PC changes.
Be realistic about the size of it. In our own benchmarks the gain was moderate, around 3 percent more FPS on a high-end card with Ultra Potato. Cards with less VRAM and lower-end GPUs typically gain more, and most of it shows up in the 1% lows, meaning less stutter, rather than in headline FPS. That is the number this page is about, so the average barely moving is not the point.
There are three tiers, biggest gain first: Ultra Potato, Potato and Standard. Ultra Potato can turn some floors invisible on a few maps and Potato leaves a few slightly raised, both cosmetic. Standard keeps every map intact. You arm a tier in the tab, the app writes it when you press its Launch button, and it is put back when the game closes, so starting the game any other way runs stock.
How to tell it worked
Do not trust the average FPS number. Turn on the 1% low reading in an overlay like MSI Afterburner and watch that instead. A good result is your 1% low climbing close to your average, which is the number that actually represents smoothness. Load into the Practice Range, walk past dense geometry and spam a few abilities, and the corner-turn hitches should be gone.
Fix the frame pacing and the game stops fighting you. Every duel comes down to your aim instead of a random freeze at the worst moment.
Frequently asked questions
Why does Marvel Rivals stutter when I turn a corner?
Corner-turn stutter is almost always VRAM overflow. The engine streams in new textures as you enter an area, and if your graphics card is out of video memory it swaps assets to system RAM, which causes the hitch. Disabling the High-Resolution Texture Pack, which adds around 40 GB of textures, is the most reliable fix on 6 GB and 8 GB cards.
Does capping my frame rate reduce stutter?
Yes. An uncapped frame rate runs the GPU at 100 percent with no headroom, so frame times spike the moment a fight gets busy. Cap a few frames below your typical rate, for example 237 if you usually hit 240, to keep frame pacing flat.
Why does Marvel Rivals stutter at the start of a match?
That is shader compilation stutter. Unreal Engine 5 compiles shaders the first time each effect appears, so you get short, one-time hitches early in a match or the first time you see a hero's abilities. It smooths out as the shaders cache, and a clean GPU driver install clears most of it.
How do I tell if my stutter is a VRAM or a CPU problem?
Watch when it happens. VRAM and streaming stutter lines up with movement and new areas, like turning corners or watching walls break. CPU and background stutter lines up with things outside the game, like an overlay or a browser tab doing work. An overlay that shows VRAM usage and 1% lows makes it obvious which one you have.
Will a graphic pack fix stuttering?
It helps when the render load itself is too high for your hardware. A graphic pack replaces the map and environment textures with simpler, lighter ones, which eases both the GPU work per frame and the VRAM pressure behind streaming stutter. In the RivalsFPS.gg app one pack is active at a time and it is built on your own PC from your own game files, so testing one and switching back is quick. It does change how the game looks, so treat it as a trade rather than a free fix.
Does the Quality tab help with 1% lows?
That is where most of its gain lands. The Quality tab in the RivalsFPS.gg app trades texture quality for FPS by writing the NVIDIA driver's own per-game profile for Marvel Rivals, so it needs an NVIDIA graphics card. On AMD and Intel the tab still opens and says why it cannot work there, because AMD's driver has no equivalent for DirectX 12 games, so in-game low settings plus FSR stay the answer on those cards. In our own benchmarks the gain was moderate, around 3 percent more FPS on a high-end card with Ultra Potato. Cards with less VRAM and lower-end GPUs typically gain more, and most of it shows up in the 1% lows, meaning less stutter, rather than in headline FPS. No game files are touched and nothing else on your PC changes. Three tiers ship, biggest gain first: Ultra Potato, Potato and Standard. You arm one in the tab, the app writes it when you press its Launch button, and it is put back when the game closes, so starting the game any other way runs stock.