Best Marvel Rivals Settings — Sensitivity, FOV and Frame Time

Three numbers decide every settings question

Every “best settings” list online is a preset somebody else is running. Presets do not transfer, because your monitor, your mouse pad and your frame rate are not theirs. Three measurements do transfer, and every setting worth changing feeds one of them.

Frame time, in milliseconds. One number, and it is the only one with a competitive return.

Degrees per centimetre of mouse movement, usually expressed as cm per 360 — how far you move your hand to spin a full circle.

Pixels per degree of field of view — how much of your screen one degree of the world occupies.

If a setting does not move one of those three, it is cosmetics. That is the whole filter.

Frame time is the only setting with a measurable return

Frame rate is quoted as a rate; what your hands and eyes experience is a duration. Divide 1,000 by the frame rate.

The column that matters is the last one, and it is not linear. Going from 60 to 144 buys you 9.8 milliseconds. Going from 144 to 240 buys you 2.8 milliseconds. The first jump is worth about 3.5 times the second, and it costs less hardware.

That produces a hard priority order:

1. Get to your monitor’s refresh rate before anything else. Below it, every frame is a frame you did not get to react in.
2. Then stop there. Once you are at 144 on a 144 Hz panel, extra frames cost image quality for a gain you cannot see.
3. Cap just under your refresh rate rather than letting the frame rate float. A stable 141 is better than a fluctuating 150 that beats against the panel.

So the correct question on a mid-range machine is not “which graphics option looks best” but “which graphics option is stealing frame time”. The answer is almost always resolution and effects, rarely shadows, and never the crosshair.

Sensitivity is a distance, not a number

This is where the “sensitivity converter” searches come from, and the whole problem dissolves once you change units.

eDPI = mouse DPI × in-game sensitivity

eDPI is the only comparable figure between players. 800 DPI at 4.0 and 1,600 DPI at 2.0 are both eDPI 3,200, which is the same turn rate to your hand. The in-game number alone is meaningless without the DPI attached to it.

Then convert to something physical:

1. Pick a landmark on your mouse pad and a fixed point on the screen.
2. Move the mouse exactly 30 cm in a straight line and note how far the camera turned. Repeat and average.
3. That gives your cm per 360 — the real figure, not the menu figure.
4. If you want to change it, scale by ratio: new sensitivity = old sensitivity × (target cm ÷ measured cm).

Going from a measured 60 cm-per-360 to a target of 40 is old × (40 ÷ 60), or two-thirds of your current number. No converter table, no game-specific constant, and it works when you change DPI or switch from another shooter. Once the number is stable, the projectile aim guide is the next thing worth changing.

What should the target be? Not a number someone else uses — a constraint. Your 360 has to fit inside the space you actually have. Measure your usable mouse arc, subtract a safety margin at both ends, and treat that as your ceiling. A player with 20 cm of clear pad cannot run a 60 cm turn rate without picking the mouse up mid-fight, and a player with a full desk who runs 15 cm cannot hold a tracking beam steady. The constraint picks the number.

FOV trades peripheral vision for target size

Field of view is the setting most often recommended without a trade-off, and it has a sharp one. What changes is how many pixels one degree of the world occupies.

pixels per degree = screen width ÷ horizontal field of view

Now convert a target into pixels. A hero roughly 0.6 metres wide, seen from 30 metres, subtends about 1.15 degrees. On a 1080p screen at 100 degrees of horizontal view that is 22 pixels. At 15 metres it is 44 pixels; at 60 metres it is 11.

Two conclusions, and they point in different directions:

• Wider FOV is better for awareness. You see the flank that would otherwise arrive off-screen.
• Wider FOV is worse for long-range precision. At 110 degrees the same distant target is 17 pixels wide instead of 21, and 4 pixels is the difference between a head and a miss.

So FOV is a hero decision, not an account decision. A close-range brawler should be wide. A sniper should be narrower. Anyone telling you one FOV value is correct for all 54 heroes is telling you they play one hero. The heroes tier list groups them by range, which is the attribute FOV actually follows.

Aim assist is three settings that fight each other

Controller aim assist gets discussed as a single switch. It is a set of settings with opposite failure modes, and the trade-off is always the same: stickiness versus switching.

• Window size is how far from the hitbox the assist begins to engage. A large window grabs earlier and holds longer, which helps tracking and makes it harder to leave a target you no longer want.
• Ease-in is how gradually the assist ramps as you approach the hitbox. Gradual feels smooth and gives you fine control near the target; abrupt feels responsive and fights your small corrections.
• Type decides whether the assist slows the reticle or follows the target. Slowing is better for precision on a stationary target; following is better for a target that strafes.

The diagnostic is simple. If you lose fights because your crosshair will not leave a body, shrink the window. If you lose fights because it will not settle on a body, widen it. Change one thing at a time, because all three settings move the same feeling and you cannot tell which one fixed it if you move all three.

What to change on a low-end PC, in order

For the “best settings for low end pc” case the priority is different, because you are buying frame time rather than precision.

1. Render resolution or upscaling. The single largest lever by a wide margin. Dropping from native to 70% costs some sharpness and returns more frames than every other option combined.
2. Effects and shadows. Costly and mostly cosmetic. Shadows do carry information on some maps, so drop them last of the two.
3. Frame rate cap. Set it just under your refresh rate, then set everything else around keeping it there.
4. Motion blur off. It does not cost much frame time; it costs clarity during exactly the movement where you need to track something.
5. Everything else. Anti-aliasing, ambient occlusion, texture filtering — measurable but small, and worth keeping at a level that does not turn the screen into noise.

One rule survives all five steps: never trade frames for shadows. A prettier frame you receive 10 milliseconds later is a worse frame.

The control layer most players never open

Two bindings in the default layout cause more avoidable deaths than any graphics setting.

The ultimate is Q on PC but both sticks pressed on PlayStation and Xbox. That is a two-input combination, not a single button, which is why ultimates misfire or fail to fire on console under pressure. If you play controller, rebind it to something single-press before you play ranked.

Ascend and Descend are separate binds from Jump. Flight heroes use a different input layer, and a player who never opened the control menu is trying to fly with a jump button. On PC ascend shares the space bar and descend sits on left control; on console they are mapped to the triggers. If flying feels wrong, it is the binding, not the hero.

Melee is the other one worth knowing: V on PC, right stick press on console, and it is a universal attack every hero has rather than a hero-specific ability. If you are still choosing what to play, the beginner guide covers the heroes that tolerate a bad control setup.

Per-hero sensitivity follows kit type, not a number

There is no per-hero sensitivity table worth copying, because the right value depends on your mouse, your pad and your frame rate — the three measurements from the top of this page. What you can decide per hero is the direction your sensitivity should move, based on what the hero asks your aim to do. Group your roster by aim type and tune within each group.

Hitscan precision heroes → lower sensitivity

Heroes that reward crisp, single-shot accuracy want a lower cm-per-360 so a small hand move is a small crosshair move:

• Hawkeye, Black Widow, The Punisher, Hela (precision hitscan or sniper-style output). A lower sensitivity keeps long-range shots on target and makes flicks controllable.

Projectile and tracking heroes → moderate sensitivity

Heroes whose damage travels or who hold a beam need mid-range sensitivity so you can track a moving target without overshooting:

• Magneto, Doctor Strange, Emma Frost, Psylocke (projectile or close-tracking kits). Moderate lets you lead a target and hold a beam without losing it on a fast flick.

Mobile and flying heroes → higher sensitivity

Heroes that reposition constantly need a higher turn rate to keep up with their own movement and with dive angles:

• Spider-Man, Iron Man, Human Torch, Star-Lord (swing, flight, or constant repositioning). Higher sensitivity turns the camera as fast as the hero moves.

Crosshair by role, not by hero

The same grouping works for crosshair choice. Precision heroes want a thin, high-contrast dot; tracking and projectile heroes want a small cross with a gap so the center stays readable; mobile heroes want a larger reticle that survives fast camera motion. Change the crosshair per hero loadout, but keep the shape tied to the aim type above.

None of this replaces the cm-per-360 measurement — it tells you which way to scale it. The controller settings guide covers the same aiming problem from the gamepad side, where aim assist does part of the tracking for you. For which heroes are worth tuning first, the heroes tier list ranks the roster by kit.