Key takeaways
- Short, one-time hitches: often caused by shader compilation, asset streaming, or a new effect being loaded.
- Regular pauses every few seconds: commonly related to background applications, overlays, storage activity, thermal throttling, or memory pressure.
- Constantly uneven movement: usually a frame-time problem caused by settings that are too demanding, a CPU limit, a driver issue, or an inconsistent frame-rate cap.
- Rubber-banding or delayed actions: more likely to be network latency than graphical stutter. Check your connection and ping separately.
To learn how to fix stuttering in Marvel Rivals, first determine whether the hitching comes from shader compilation, unstable frame times, graphics settings, drivers, or another program competing for CPU, GPU, memory, or storage access.
Our top picks
As an Amazon Associate we earn from qualifying purchases at no extra cost to you. Ratings are shown as listed on Amazon.
1. Identify what kind of stutter you have
Play one repeatable situation for five to ten minutes, such as entering a busy objective area or using several abilities in a team fight. Notice whether the problem is:
- Short, one-time hitches: often caused by shader compilation, asset streaming, or a new effect being loaded.
- Regular pauses every few seconds: commonly related to background applications, overlays, storage activity, thermal throttling, or memory pressure.
- Constantly uneven movement: usually a frame-time problem caused by settings that are too demanding, a CPU limit, a driver issue, or an inconsistent frame-rate cap.
- Rubber-banding or delayed actions: more likely to be network latency than graphical stutter. Check your connection and ping separately.
Use a frame-time graph in a tool such as MSI Afterburner with RivaTuner Statistics Server, or another trusted monitoring utility. A smooth 60 FPS frame rate requires roughly 16.7 milliseconds per frame; 120 FPS requires 8.3 ms. A game that reports 100 FPS can still feel poor if individual frames occasionally take 30–50 ms.
| Target | Average frame time | Useful starting cap | What a bad spike looks like |
|---|---|---|---|
| 60 FPS | 16.7 ms | 58–60 FPS | 25 ms or higher |
| 90 FPS | 11.1 ms | 87–90 FPS | 18 ms or higher |
| 120 FPS | 8.3 ms | 117–120 FPS | 14 ms or higher |
| 144 FPS | 6.9 ms | 140–144 FPS | 12 ms or higher |
These are timing targets, not guarantees. Your best cap depends on your monitor, hardware, and whether the game can hold that rate during the busiest fights.
2. Allow shader compilation to finish
Modern Unreal Engine games can compile shaders when new maps, characters, visual effects, or driver versions are introduced. During this process, the game may hitch even when your average FPS appears adequate.
- Launch Marvel Rivals and leave it at the main menu for several minutes.
- Enter the practice or training area and load several characters and abilities.
- Play a few normal matches without repeatedly restarting the game.
- After a graphics-driver update, repeat this warm-up process because the driver may rebuild its shader cache.
Do not repeatedly clear the shader cache as a first response. Deleting it can make the next launch stutter more while shaders are rebuilt. If the cache is clearly corrupted, close the game, use your GPU driver’s cache-reset option or Windows Disk Cleanup, then allow the game to compile again from scratch.
3. Apply a stable graphics baseline
Begin with a stable configuration rather than changing every option at once. Set the game to your monitor’s native resolution, use fullscreen or borderless fullscreen according to which mode produces steadier frame times, and choose a frame cap your system can sustain during combat.
Recommended first-pass settings
- Resolution: native resolution. If the GPU is overloaded, reduce internal resolution or use the game’s supported upscaling option before lowering every setting.
- Frame rate: cap 2–4 FPS below the refresh rate when using variable refresh rate. For example, try 141 FPS on a 144 Hz display or 117 FPS on a 120 Hz display.
- Textures: High if your graphics card has enough VRAM; use Medium if VRAM is nearly full or texture streaming causes spikes.
- Shadows: Medium or Low. Shadow quality can create significant GPU and CPU work in crowded scenes.
- Effects and post-processing: Medium initially, then reduce them if team fights cause spikes.
- View distance: High or Medium. Lower it if the CPU is near full utilization while the GPU is not.
- Motion blur, film grain, and depth of field: disable them while troubleshooting. They rarely solve stutter, but removing them makes motion easier to judge.
- Upscaling: test the Quality mode first. If the GPU remains at 95–100% usage, try Balanced; avoid lowering resolution so far that image clarity becomes a new problem.
VRAM pressure is worth checking separately. A 1920×1080 frame contains about 2.1 million pixels, while 2560×1440 contains about 3.7 million—approximately 1.78 times as many pixels. At 3840×2160, the count rises to about 8.3 million, nearly four times 1080p. Higher resolution increases render workload, while high textures mainly increase memory usage. If GPU memory is full, lower textures first; if GPU utilization is maxed but VRAM is not, lower resolution, effects, shadows, or upscaling quality.
4. Match the fix to your hardware symptom
| Observed monitor result | Likely limit | Next change |
|---|---|---|
| GPU 95–100%, VRAM below capacity | Rendering workload | Lower upscaling quality, effects, shadows, or resolution |
| GPU below 85%, one or more CPU cores near 100% | CPU or game-thread limit | Lower view distance, close background tasks, use a sensible FPS cap |
| VRAM nearly full, sudden texture-related hitch | Memory pressure or streaming | Lower textures and close GPU-using applications |
| System RAM above roughly 90% | Paging or memory pressure | Close browsers and launchers; reduce applications running behind the game |
| Temperatures rise, clocks repeatedly fall | Thermal or power throttling | Improve cooling, clean filters, use a balanced power mode |
5. Update or roll back the graphics driver
Install the current driver for your graphics card from NVIDIA, AMD, or Intel, depending on your hardware. Choose a clean installation when the installer provides that option, particularly after switching GPU brands or experiencing problems immediately after an update.
If stuttering began directly after a driver update, test the previous stable driver instead of assuming the newest version is best. Remove unnecessary driver extras, but keep the components required for the game and display. After changing drivers, expect shader compilation to occur again.
Also install pending Windows updates and restart the computer. Avoid updating Windows, the GPU driver, the game, and several monitoring utilities simultaneously if you are trying to identify a cause; changing one major variable at a time makes the result clearer.
6. Stop background interference
Close browsers with many tabs, video encoders, file synchronization tools, RGB utilities, hardware monitoring programs you do not need, and other games or launchers. Disable overlays temporarily, including those from Discord, Steam, Xbox Game Bar, NVIDIA, AMD, and recording software.
Recording and instant-replay features can create intermittent disk and CPU activity. Turn them off for one test session. If the stutter disappears, re-enable features one at a time and reduce recording resolution, bitrate, or capture frame rate.
Check Task Manager while Marvel Rivals is running. Sort by CPU, Memory, GPU, and Disk usage. A short disk-usage spike that matches each hitch points toward streaming, antivirus scanning, updates, or a nearly full drive. Keep meaningful free space on the game drive and avoid running intensive downloads during matches.
7. Use a frame cap instead of chasing maximum FPS
An uncapped frame rate can keep the GPU and CPU fluctuating between full load and idle, especially when the game moves between quiet areas and crowded fights. A cap slightly below the rate your system can maintain often produces better frame pacing than a higher but unstable average.
For example, if your system varies between 105 and 145 FPS on a 144 Hz display, try a 100 or 110 FPS cap and compare the frame-time graph. If it stays close to the cap with fewer spikes, the lower number is the smoother choice. If you use a variable-refresh monitor, enable its adaptive-sync feature and avoid running beyond the display’s reliable range.
8. Verify files and test configuration changes
Use your game launcher’s file-verification function if crashes, missing assets, or unusual stuttering appeared after an interrupted update. Do not modify configuration files from random sources while troubleshooting; unsupported tweaks can introduce new instability or be reset by patches.
After each change, test the same map or type of match for several minutes. Record the resolution, preset, FPS cap, GPU utilization, VRAM use, CPU utilization, and the largest frame-time spikes. This turns “it feels smoother” into a repeatable comparison.
When the problem is probably not your graphics settings
If frame times are stable but characters teleport, attacks register late, or the network indicator reports loss, investigate connection quality rather than lowering graphics. Use wired Ethernet where possible, stop large downloads, and test another network. If only one map or patch causes severe hitches after shader warm-up, the issue may be game-side and may require a later update rather than a hardware change.
The most reliable troubleshooting order is: warm up shaders, establish a moderate graphics baseline, cap the frame rate, inspect GPU/CPU/VRAM/RAM usage, disable overlays and recording, update or roll back the driver, and verify files. Recheck the frame-time graph after every major step; smooth, consistent frame delivery matters more than the highest number shown by the FPS counter.
