Marvel Rivals Best PC Settings: Max FPS & UE5 Optimization

Executive Overview: Competitive Performance Tuning

Marvel Rivals on PC exposes a modern, fully customizable graphics pipeline: hardware-accelerated upscaling (DLSS, TSR), screen-space global illumination, screen-space reflections, a low-latency toggle and a frame-generation switch. The default presets are tuned for showcase visuals, not for frame pacing, so on mid-range hardware you will usually get smoother tracking and more readable silhouettes by rebuilding the profile yourself.

Quick Answer: Switch display mode to Fullscreen, set Global Illumination to SSGI - Low Quality and Reflections to Screen Space, keep Model / Post-Processing / Texture / Effects / Foliage on Low with Shadow on Medium, enable DLSS (NVIDIA) or Epic TSR (AMD) Super Resolution, leave Frame Generation OFF, turn Low Latency On and VSync Off.

In a high-speed hero shooter where tracking a swinging Spider-Man or landing hitscan headshots with Hela matters more than looking at bloom, low-percentile frame time beats peak average FPS. This guide provides a calibration matrix across Windows system settings, GPU driver configurations and in-game graphic parameters.

Verification note: Marvel Rivals is commonly described as an Unreal Engine 5 title, and its settings menu (Super Resolution options, "SSGI", Nanite-style mesh scaling) is consistent with a current-gen UE pipeline, but NetEase has not documented the engine build or the exact cost of each slider in our captured sources. Where a percentage improvement would normally be quoted here, we instead state the direction of the change and mark the magnitude as unpublished. Measure your own deltas with the in-game Show FPS and Network Stats toggles before trusting any third-party number.

System-Level Windows & Driver Tuning

Before touching in-game sliders, the underlying operating system and GPU driver should be tuned to remove background overhead and latency buffers.

┌────────────────────────────────────────────────────────────────────────┐
│                   SYSTEM-LEVEL PERFORMANCE CALIBRATION                 │
├────────────────────────────────────────────────────────────────────────┤
│ 1. HARDWARE-ACCELERATED GPU SCHEDULING (HAGS)                          │
│ • Path: Windows Settings > System > Display > Graphics Settings        │
│ • State: ON (test after reboot; some systems regress)                  │
├────────────────────────────────────────────────────────────────────────┤
│ 2. RESIZABLE BAR (ReBAR / Smart Access Memory)                         │
│ • Path: BIOS > Above 4G Decoding & ReBAR Support, or GPU control panel │
│ • State: ENABLED (CPU accesses the full GPU VRAM pool)                 │
├────────────────────────────────────────────────────────────────────────┤
│ 3. GPU SHADER CACHE                                                      │
│ • Path: NVIDIA Control Panel > Manage 3D Settings > Shader Cache Size   │
│ • State: raise it only if you actually see first-cast hitches          │
├────────────────────────────────────────────────────────────────────────┤
│ 4. WINDOWS GAME MODE                                                   │
│ • Path: Windows Settings > Gaming > Game Mode                          │
│ • State: ON, then A/B test - some systems prefer it off                │
└────────────────────────────────────────────────────────────────────────┘

The first, second and fourth items are taken directly from a captured PC-settings guide: Resizable BAR lets the CPU reach GPU memory directly, HAGS moves GPU scheduling onto the card itself, and Game Mode prioritises resources for the active game - with the explicit caveat that a minority of systems do better with HAGS or Game Mode off, so re-test after each change.

Shader Cache and First-Cast Hitches: What We Actually Know

The most frequently reported PC complaint in games of this generation is a freeze when an ability, character or destruction effect is rendered for the first time in a session. The usual cause is real-time shader compilation: the driver compiles a variant on demand, and if the on-disk shader cache is too small to keep previously compiled variants, the work repeats.

NVIDIA and AMD both expose a shader/driver cache size setting, and community guides for UE-based titles routinely recommend raising it above the driver default. We have not verified any specific Marvel Rivals cache size (the widely circulated "set it to 10GB" figure included) against an official or reproducible source, so we are not publishing one. The honest procedure is:

Play a few matches and note whether hitches happen only on first use of a hero or effect, or on every use.
If only first use, a cache-size or pre-warm fix is plausible; leave the driver at its default first, then raise one step and retest.
If it hitches every time, the cause is elsewhere (VRAM pressure, thermals, background capture) - expanding the cache will not help.

Definitive In-Game Graphics Settings Matrix

The table below is the competitive profile we recommend, assembled from the community settings guides we based this page on. The "Direction" column is qualitative on purpose: NetEase does not publish per-slider performance costs.

In-Game Setting	Competitive Recommendation	Direction (magnitude unpublished)	Visual & Tactical Impact
Display Mode	Fullscreen	Cheapest	Reduces input lag versus windowed modes
Resolution	Native monitor resolution	Variable	Maximum pixel clarity for long-range crosshair work
Aspect Ratio	Your panel's native aspect ratio	Neutral	Avoids stretched or letterboxed sightlines
Frame Rate Limit	Off, or clamped just under your refresh rate if using G-Sync/FreeSync	Neutral	Stops V-Sync-style latency while avoiding flicker at the ceiling
Anti-Aliasing & Super Resolution	NVIDIA: DLSS. AMD: Epic TSR with Anti-Aliasing on Ultra	Large uplift	Framerate headroom while keeping edges readable
Frame Generation Mode	OFF	Costs latency	Interpolated frames inflate the counter but do not shorten input latency
Low Latency Mode	On (NVIDIA)	Reduces latency	Tightens the render queue during engagements
VSync	Off	Reduces latency	Prevents the input lag VSync introduces
Global Illumination	SSGI - Low Quality	Meaningful saving	Screen-space lighting instead of heavier GI passes
Reflection Quality	Screen Space Reflections	Meaningful saving	Removes costly mirrored geometry on wet floors
Model Detail	Low	Moderate	Keeps hero silhouettes readable
Post-Processing	Low	Moderate	Strips bloom and lens effects that smear fights
Shadow Detail	Medium	Moderate	Keeps positional shadow cues without the highest cost
Texture Detail	Low	VRAM-dependent	Frees video memory on smaller cards
Effects Detail	Low	Meaningful in teamfights	Reduces ultimate-heavy frame collapse
Foliage Quality	Low	Minor-to-moderate	Clears ground clutter in outdoor lanes
Brightness	Your display's stock default, then tune to your panel	Neutral	Lets you read dark corners without washing out enemies
Show FPS / Network Stats	On	None	Required to measure any of the above yourself
Motion Blur	Off	Neutral	Removes rotational smearing while tracking

Deep-Dive Analysis of Performance-Critical Settings

1. Global Illumination and Reflections

The captured guide's recommendation is explicit: Global Illumination: SSGI - Low Quality and Reflections: Screen Space Reflections. Screen-space GI derives indirect light from what the camera already sees instead of tracing it, which is why it is the cheaper option in a game where ultimates fill the screen with overlapping light sources. Set the two together and re-check your frame pacing in a full teamfight rather than an empty spawn area.

How much either slider is worth is not published by NetEase, and we are not going to invent a percentage. The reliable method: set both to their lowest values, note your FPS and low-percentile timings with Show FPS on, then raise one at a time until the visual loss bothers you more than the frame gain pleases you.

2. Anti-Aliasing, Upscaling & Super Resolution

Marvel Rivals exposes upscalers from more than one vendor, and the captured guide splits the recommendation by hardware:

┌────────────────────────────────────────────────────────────────────────┐
│                   UPSCALING SELECTION DECISION TREE                    │
└──────────────────────────────────┬─────────────────────────────────────┘
                                   │ Detect GPU Vendor
                                   ▼
          ┌────────────────────────┴────────────────────────┐
          │ NVIDIA GPUs                                     │ AMD GPUs
          ▼                                                 ▼
  ┌───────────────────────────────┐                 ┌───────────────────────────────┐
  │ DLSS                        │                 │ Epic TSR                      │
  │ • Super Resolution:         │                 │ • Super Resolution:           │
  │   Performance or Balanced   │                 │   Performance                 │
  │ • Frame Generation: Off     │                 │ • Anti-Aliasing: Ultra        │
  └───────────────────────────────┘                 └───────────────────────────────┘

NVIDIA Hardware: run DLSS with Super Resolution on Performance or Balanced, exactly as the captured guide states. If you are at a high native resolution you have more internal-render slack than a 1080p player, so start conservative and step down only if your frametimes still miss the target.
AMD / Intel Hardware: the captured guide pairs Epic TSR on Performance with Anti-Aliasing on Ultra. TSR is the engine's own temporal path, which tends to hold detail on thin, fast-moving geometry - a real concern when you are tracking a projectile across the screen.
Why Frame Generation stays off: it inserts interpolated frames between real engine frames. That inflates the average FPS number while the input path still runs at the engine's true rate, so aim feels mushier than the counter suggests. Competitive play wants latency, not a bigger number.
FOV: the field-of-view slider trades peripheral awareness against how large enemies render. The exact maximum value differs by client version, so read it off your own menu instead of copying a number from the internet, and raise it in small steps if you get distorted at the edges.

3. Low Latency / NVIDIA Reflex: Why It Is Mandatory

The captured guide's line is simply "Low Latency Mode: On (for NVIDIA GPUs)". Where your driver exposes the "On + Boost" variant, the Boost half additionally pins GPU memory and core clocks so they do not idle down between fights; that means when an enemy rounds a corner the card is already at operating frequency and your frame reaches the monitor sooner.

Audio & Spatial Sound Settings

Audio cues in Marvel Rivals are as vital as visual information: flankers like Spider-Man, Black Panther and Magik announce themselves with movement audio and voice lines before they commit. The captured guide's audio recommendations are directional, so treat the values below as priorities rather than exact percentages:

3D Enhancement: On (improved spatial awareness)
HRTF: On (sharper directional audio)
Sound Effects (SFX) Volume: keep at or near maximum - footsteps, barrier breaks and ability cues are the information you are paying for
Dialogue / Voice Lines: keep audible; ultimates announce themselves through voice shouts, so silencing dialogue can hide a cooldown you needed to know about
Music Volume: lower or off (the captured guide's explicit advice - orchestral swell drowns out quiet footstep audio)

Mouse Sensitivity, Crosshairs & Input Calibration

Consistent aim across first-person camera states requires removing Windows pointer acceleration and settling on a repeatable effective Dots Per Inch (eDPI).

The eDPI Calculation Standard

$$\text{eDPI} = \text{Hardware Mouse DPI} \times \text{In-Game Sensitivity}$$

The most reliable calibration method captured from high-rank community testing is a single baseline sensitivity multiplied per role, measured at a fixed 600 DPI hardware setting. Start from the verified tracking baseline, then scale up for close-quarters roles and down for precision snipers:

Playstyle / Role Class	Hardware DPI	In-Game Sensitivity	Calibration Formula	Tactical Justification
Precision Hitscan / DPS Tracking (Hela, Punisher)	600 DPI	1.18	Baseline reference	Middle-ground sens for precise tracking, flicks, and general aim control
Sniper (long-range holds)	600 DPI	0.59	Baseline ÷ 2	Pixel-perfect flicks with no jitter or overcorrection on long sightlines
Support Strategist (Luna, Mantis)	600 DPI	2.36	Baseline × 2	React fast under pressure, survive dives, and track heals smoothly
Melee / Vanguard / Divers (Spider-Man, Strange)	600 DPI	3.54	Baseline × 3	Quick turns, brawling responsiveness, and high-tempo movement

This ladder is one player's verified personal calibration, not a mandated setting. Use it as a starting grid: the same source's method is to find the lowest sensitivity at which close-range tracking stays clean and jitter-free, then derive the other roles from that baseline.

Crosshair Configuration Best Practices

For complete per-hero reticle codes, neon green setups, and hitscan settings, see our dedicated Marvel Rivals Crosshair Codes & Reticle Guide.

Color Selection: choose a high-contrast static colour that never blends into the neon map palettes; cyan and bright green are the usual picks.
Dynamic Crosshair Spread: set to OFF. Expanding reticles during movement add visual noise and hide the target's head while tracking.
Center Dot: enable a small static centre dot so projectile centre-points stay unambiguous.

Benchmarking & Troubleshooting Common Stutters

If performance still dips after applying this profile, run the three-step diagnostic:

Checklist Item 1: GPU Temperature & Thermal Throttling

A heavily loaded GPU eventually stops increasing clocks and then reduces them to stay inside its thermal target; the audible/visible symptom is frame drops that arrive after several minutes of play rather than immediately. Watch your own card's hot-spot and memory temperature with your vendor overlay, and treat "it started throttling" as the real threshold - the exact number is a property of your cooler, not of Marvel Rivals.

Checklist Item 2: RAM Dual-Channel Operation & XMP / EXPO

Modern UE pipelines stream large asset quantities through system memory. Confirm your DDR4/DDR5 kit is running in dual-channel mode with XMP (Intel) or EXPO (AMD) enabled in BIOS. Single-channel operation, or leaving RAM at its default JEDEC clock, bottlenecks low-end framerates badly enough that no in-game slider will rescue it.

Checklist Item 3: Background Application Overlays

Disable the Discord in-game overlay, Steam overlay hardware acceleration and background capture (Xbox Game Bar, recorder buffers). Each one injects a hook into the render thread, and stacked hooks are a common source of micro-stutter that looks exactly like a game-side problem.

Strategic Summary & Next Steps

Optimizing Marvel Rivals for competitive performance is mostly about removing guesswork:

Lock display mode to Fullscreen with VSync off and Low Latency on.
Take Global Illumination to SSGI - Low Quality and Reflections to Screen Space, then measure the delta yourself with Show FPS.
Use DLSS on NVIDIA or Epic TSR (with Anti-Aliasing on Ultra) on AMD, and keep Frame Generation off.
Only chase shader-cache or driver tweaks if your hitches happen on first cast - otherwise the bottleneck is thermals, memory or background hooks.

To pair your optimized hardware performance with superior gameplay execution, review our Marvel Rivals Beginner Guide for combat fundamentals, study map layouts and demolition strategies in the Marvel Rivals Destructible Maps Guide, explore frontline positioning in the Marvel Rivals Vanguard Tank Guide, and discover optimal team setups in our Marvel Rivals Best Team Comps Guide.