Aim assist slows, it does not snap
The first thing to unlearn: controller aim assist in Marvel Rivals does not lock your reticle onto a target. It slows the crosshair as it passes over a hitbox, giving you a window to land the shot. That single fact explains every setting below — they are all trade-offs between stickiness (the assist holds you on a body) and switching (you can leave that body to find another).
This page is the console and controller counterpart to the PC settings guide. If you are on mouse and keyboard, read that one instead.
The three settings that actually matter
| Setting | What it does | Failure mode if wrong |
|---|---|---|
| Window size | How far from the hitbox the assist engages | Too large → crosshair will not leave a body; too small → assist never kicks in |
| Ease-in | How gradually the assist ramps near the hitbox | Too abrupt → fights your small corrections; too soft → feels unresponsive |
| Strength | How hard the slow pulls | Too high → sticky and hard to switch; too low → barely noticeable |
The diagnostic is one line: if you lose fights because your crosshair will not leave a body, shrink the window; if you lose because it will not settle on a body, widen it. Change one at a time — all three move the same feeling, so moving all three tells you nothing.
Self-test your deadzone
Deadzone is the stick travel the game ignores before it registers input. Get it wrong and your aim drifts or feels delayed. Test it in the practice range:
- Hold the stick dead center. If the camera drifts or slow-aim engages on its own, your deadzone is too low — raise it.
- Tilt the stick the smallest amount. If the camera does not move until you push further, your deadzone is too high — lower it.
- The right value is the lowest setting with no drift. Consensus lands both input deadzones near 1 for most players.
Do not copy a number blind. The self-test takes two minutes and beats any preset, because your stick’s wear is unique.
A starting point, not a destination
Community consensus clusters on a Linear Curve (some use Dual-Zone S-Curve), both deadzones near 1, and ease-in around 80 projectile / 40 hitscan / 0 melee. Reported starting points include Strength 90 / Window 40 on a linear setup, or Strength 100 / Window 20 on a dual-zone S-Curve.
Treat those as “does it feel alive” checks, not targets:
- If the assist feels absent, raise Strength by 10 and re-test.
- If you cannot leave a target, drop Window by 5 and re-test.
- If small flicks overshoot, lower ease-in on the relevant weapon type.
Sensitivity: start, then climb
There is no verified database of pro controller configs, so do not chase one. A workable method is to start sensitivity around 300 and climb 25–50 per day only while your accuracy holds. The moment your hit rate drops, stop — you have found your ceiling for now.
If-then
- Crosshair sticks to bodies you want to leave → lower Window.
- Crosshair won’t settle on a body → raise Window.
- Stick drifts at rest → raise deadzone.
- Stick feels delayed → lower deadzone.
For the PC-side equivalents and the frame-time math behind why stable frame rate matters more than any aim number, the settings guide covers it from the mouse-and-keyboard side.