Stop copying streamer configs
Every "best Marvel Rivals settings" post on the internet hands you a list of numbers — somebody's eDPI, somebody's FOV, somebody's video preset — and tells you to copy them. Then you copy them, your aim feels worse than it did last week, and you spend another hour fiddling with sliders trying to figure out why.
The problem isn't the numbers. The problem is that settings are a function of you — your hand, your monitor, your desk, the heroes you play, the mode you queue. A pro player's sensitivity is right for their hand, their monitor distance, and the role they play. It is almost never right for yours.
This guide is the version of the post we wish we'd read when we started playing Marvel Rivals seriously. It tells you which settings actually move the needle, how to think about each one, and where the right answer is "test it for yourself" versus where there's a defensible default.
We're not going to tell you to use 800 DPI and 0.5 in-game. We're going to tell you how to find the equivalent number for your hand in about twenty minutes.
The four settings that actually matter
Of the dozens of sliders Marvel Rivals exposes, four meaningfully affect your performance. Everything else is preference or visual taste.
- Mouse sensitivity — eDPI, in-game multiplier, and any acceleration.
- Field of view (FOV) — how much of the world is on your screen at once.
- Crosshair — colour, size, and shape.
- Audio mix — game sound, voice-line volume, and whether you have positional audio dialled in.
Video settings affect frames per second, which affects input latency, which affects aim. But they don't change how you aim — just how responsively the input fires. We'll cover them, but treat them as a follow-up to the four above, not a substitute for getting those four right.
Mouse sensitivity: find your number
This is the single biggest lever you have, and the one most players get wrong. The mistake is thinking there's a "right" sensitivity in the abstract. There isn't — there's a right eDPI for the way your hand moves.
What eDPI is, and why it matters
eDPI = mouse DPI × in-game sensitivity multiplier. It's the combined number that determines how many in-game degrees your aim moves per inch of mouse travel.
Two players running 1600 DPI / 0.5 sens and 800 DPI / 1.0 sens have the same eDPI (800) and will feel identical in-game. The mouse-and-game pair you choose to get to your eDPI matters less than hitting the right eDPI for your style.
How to find your number
Start with this: how do you move the mouse? Do you flick from the wrist (low travel, fast snaps) or sweep from the elbow (long travel, smoother arcs)?
- Wrist aimer — typical eDPI range 600–1200. You want a smaller mousepad travel per 360° turn so flicks stay in comfortable wrist range.
- Arm aimer — typical eDPI range 300–600. You want bigger arcs because you're using your shoulder to track, not your wrist.
- Hybrid — most players land here. Try 600–900 and adjust.
Pick a starting eDPI from your range. In Marvel Rivals practice range, set up a stationary bot and do this: drag your mouse from fully-extended-left to fully-extended-right across the mousepad without lifting. The crosshair should sweep about 180–270° in game.
- If it sweeps a full 360° or more, your eDPI is too high. Lower it by 20% and re-test.
- If it sweeps less than 180°, your eDPI is too low. Raise it by 20% and re-test.
You're aiming for "a comfortable arm-and-wrist motion gets me roughly half a turn." That's the sweet spot for most heroes.
Acceleration and raw input
Two non-negotiables:
- Mouse acceleration: off. Both in-game and in Windows. With acceleration on, the same physical motion produces a different in-game movement depending on speed — which is the opposite of what muscle memory needs.
- Raw input: on. Bypasses Windows pointer ballistics and applies the mouse delta directly. The default in most competitive titles for a reason.
If you've been playing with acceleration on, you'll feel slow for a day after turning it off. Push through. Your tracking will improve.
Field of view: 90 to 105, and what's between
Marvel Rivals' FOV slider runs from a relatively narrow default up to a wider competitive cap. Wider FOV gives you more peripheral awareness (good for flanks, situational reads, and dive heroes). Narrower FOV makes targets appear bigger on screen, which can help with precise aim on hitscan heroes.
The trade is real and well-understood across competitive shooters:
- Lower FOV (~90) — bigger targets, easier hitscan tracking, worse peripheral awareness. Good for snipers and duellists.
- Higher FOV (~105) — smaller targets, harder precision aim, better awareness. Good for divers, supports, and any hero who benefits from seeing flanks early.
There's no objectively correct answer. The competitive shooter consensus is try 103 first, then adjust by ±5 based on whether you feel you're missing reads (raise it) or missing shots (lower it).
If you only play one hero and it's a hitscan duellist, you can defensibly run lower. If you play a roster of heroes, picking a single number and committing to it matters more than picking the "right" one, because your muscle memory calibrates to whatever number you're using.
Crosshair: visible, simple, calibrated
A crosshair has one job: tell you where your shot is going to register. Anything that complicates that is overengineering.
Colour
Cyan, magenta, or bright green. Colours that aren't present in the game's level palette. Marvel Rivals' maps lean warm-orange and saturated-blue, so a cyan crosshair that looks decent in the practice range can disappear against the sky on Yggsgard. Take five minutes to play one of each map and confirm the crosshair stays visible against every background.
If you're colour-blind or have any trouble with cyan/magenta on specific backgrounds, white with an outline is the hardest-to-lose option across all maps. Marvel Rivals exposes crosshair outline as a setting — turn it on.
Size
Smaller than you think. The most common mistake is a chunky crosshair that fills 20+ pixels in the centre of your screen, obscuring the head-shot you're trying to land. A crosshair big enough to find at a glance but small enough not to cover a head at 20m is the right size.
Practical test: stand at 30m from a stationary bot in practice mode. Can you see the bot's head with the crosshair on it? If the crosshair covers more than the head, it's too big.
Shape
A plain cross or dot is correct for most heroes. The fancy gap-and- ring crosshairs you see in streamer screenshots are usually preference, not advantage. If you have a strong preference, go with it; if you don't, default to a simple cross with a 1-pixel centre dot.
Video and FPS: chase latency, not eye candy
Video settings determine your frame rate, and your frame rate determines your input latency. More frames mean less time between "I move the mouse" and "the game registers it." That's the whole story for competitive video settings.
Frame rate targets
- 60 FPS is the bare minimum. If you can't sustain 60, your aim is being held back by your hardware.
- 120–144 FPS is the comfortable competitive baseline, and matches the refresh rate of most competitive monitors.
- 240+ FPS is a marginal improvement above 144 — measurable in latency terms, but the diminishing returns curve is steep. If you're not already on a 240Hz monitor, prioritise the monitor over chasing the framerate.
If you have a high-end rig, your goal is stable 240+ FPS with the visual quality knobs that don't tank frame rate left on. Texture quality and view distance are usually safe to leave high. Effects, post-processing, and shadows are the first to drop.
V-Sync, G-Sync, and frame caps
- V-Sync: off. It adds significant latency to eliminate tearing. The tearing isn't worth it on a 144+ Hz monitor; the latency is.
- G-Sync / FreeSync: on, if your monitor supports it. It eliminates tearing without the latency cost.
- Frame cap: 3 below your monitor's refresh rate. So 141 cap on 144Hz, 237 cap on 240Hz. Keeps the framerate inside G-Sync's range and prevents the latency spikes that happen when frame pacing crosses the refresh-rate ceiling.
Audio: positional first, mix second
The single best audio setting in Marvel Rivals is headphones with positional audio on. You will hear footsteps, abilities, and ultimates from the direction they're coming from.
Beyond that:
- Voice-line volume: moderate, not loud. They're informational ("Ultimate ready!") but you don't want them drowning out footsteps.
- Effects volume: the highest of any audio bus. This is where positional sound lives — ability casts, gunfire direction, summon cues.
- Music volume: off, or very low. Music actively makes it harder to hear positional cues. Trade the immersion for information.
If you're streaming, lower the music below the threshold where it shows up in your stream mix at all. Your viewers won't miss it.
Hero-specific tweaks worth knowing
A few heroes have specific settings worth calling out.
Hawkeye (and other projectile heroes)
If you're playing Hawkeye, Hela, Black Widow, or another arc/ projectile hero, lower your sensitivity by about 10–15% from your default. Projectile heroes punish overshoot — you need a slower, deliberate aim more than you need flicks. We wrote up the projectile mental model separately in the Hawkeye guide.
Spider-Man and dive heroes
Spider-Man's swing changes your effective FOV mid-fight as the camera pulls back. Players who run very high FOV often find Spider disorienting; consider dropping to 100 or so if you main him.
Strange, Mantis, and other supports
Supports benefit from higher FOV (awareness > precision). 103–105 is a defensible default; some support players go higher.
Putting it together: a 20-minute calibration checklist
Stop reading and run this in practice mode:
- Sensitivity — pick an eDPI from your range and run the 180°–270° drag test. Adjust until it feels right.
- FOV — set 103 and commit for the rest of the session. If you feel cramped tomorrow, raise it. If you feel imprecise, lower it.
- Crosshair — cyan or white with outline, small, simple. Walk through all five maps briefly to confirm visibility.
- Video — turn V-Sync off, frame cap to (refresh - 3), drop effects and shadows until you sustain your target FPS.
- Audio — effects high, music off, voice-lines moderate. Headphones on.
That's the configuration. From there, you adjust one thing per week based on what's actually losing you fights. Not a wholesale rebuild every two days because a streamer used different numbers.
Where overlays fit in
Settings get your inputs to feel right. They don't change what the game does — they change how your hand talks to the game.
A hero-aware overlay does a different thing. It changes what you can see and how the game processes your aim intent. The projectile-lead solver works on top of your settings — it doesn't override your sensitivity or your FOV; it does the math you'd otherwise be doing in your head.
Once your settings are dialled, Nimbus's hero-aware aim and ESP let you focus on positioning instead of execution. The aim engine respects whatever sensitivity you've configured; ESP respects whatever FOV you've chosen. The product page has the feature list at /products/rivals, and the compare table puts us next to the alternatives if you're shopping around.
If you're new to overlays and the safety question is on your mind, read our overlay safety post before you buy anything — including ours.
Bottom line
Good settings won't carry a bad player; bad settings will hold back a good one. The four levers that matter are sensitivity, FOV, crosshair, and audio mix. Everything else is preference.
Spend twenty minutes in practice mode running the calibration above. You will be a measurably better Marvel Rivals player tonight than you were this morning — without copying a single number from a streamer's video.
Bookmark this post, run the test, and adjust one thing per week based on real fights you lost. That's how settings get better over time.
