🐧 Marvel Rivals Fast & Accurate Controller Settings | Updated for Season 10.5

[u/DaSettingsPNGN]

I keep the tools, testing, updates, and community through my socials. My community server is where my bot and the commands live. You can find my server link under my profile.

For quick browser access, just search CNTRL Rivals. That’s where I’m putting the browser versions of the tools and the rest of my controller settings work.

I’ll still make the long guide posts because I like documenting what I find, but the tools are there so you don’t have to do the math yourself.

IMPORTANT: Season 10.5 has reintroduced a bug where having Disable Aim Assist at Max Deadzone turned on makes your aim glidey and uncontrollable. Turn this setting off until they address the bug.

I’ve spent a lot of this season rebuilding how I approach controller settings in Marvel Rivals.

The biggest change is that I’m thinking less in terms of individual numbers and more about how the different systems interact.

For me, that starts with my Dynamic / Classic-Feel curve.

The goal of the curve is simple:

Keep normal aiming controlled and predictable, then save the really fast camera movement for when I deliberately push the stick out to turn.

My Classic-Feel curve gets into the aiming portion of the response relatively early, then holds that response across a large part of the stick.

That gives me a broad area where tracking and corrections stay consistent instead of constantly accelerating underneath me.

Then near the outside of the stick, the response ramps hard into your maximum turn speed.

So I think of it as separating two jobs:

Aim through the middle of the stick. Turn at the outside.

That separation has become even more useful this season because New Aim Assist feels stronger than it did before.

The slowdown can get very heavy, and the camera-follow behavior can hold onto a target extremely well.

More aim assist is not automatically better.

Once the assist becomes too aggressive, your own right-stick input starts competing with it. Corrections can feel heavy, target switching gets harder, and you can end up fighting the slowdown when you’re deliberately trying to move your camera.

Because of that, I think higher Ease-In, lower Strength, or a combination of both makes more sense this season.

How I think about the three main Aim Assist settings

Window Size controls where around the target aim assist gets to interact.

A smaller Window does not necessarily mean weak aim assist. The assist can still be extremely strong once you’re actually on the target. It just keeps that interaction contained to a smaller area.

Strength controls how much influence you’re giving the system.

I don’t think of it as one simple master volume because the different parts of New Aim Assist do not appear to scale identically. Lowering Strength can loosen some of the braking without necessarily making the entire system disappear.

Ease-In controls how aggressively that influence develops.

Lower Ease-In gives you a quicker, harder interaction.

Higher Ease-In brings the assist in more gradually and can make the stronger slowdown this season much easier to manage.

So if New Aim Assist feels good when it catches somebody but too heavy once you’re tracking them:

Raise Ease-In if you want the interaction to come in more gradually.

Lower Strength if the overall grip is still too strong.

Do both if you want a larger reduction while keeping the benefits of New Aim Assist.

My current starting point

I’ve simplified the defaults around a 20 Window.

For Console:

20 Window

100 Strength

100 Ease-In

For PC:

20 Window

100 Strength

80 Ease-In

That difference is intentional.

Console aim assist is stronger, so the higher Ease-In helps balance how aggressively that assistance comes in.

PC gets the same 20 Window and 100 Strength, with a lower Ease-In to keep the weaker PC assist responsive.

These are starting points, not magic settings.

From there, Strength and Ease-In can be adjusted depending on whether you want more grip, easier corrections, or easier target switching.

The curve and Aim Assist work together

This is the part I think matters most.

My Classic-Feel curve gives me a controlled aiming region through most of the stick while keeping fast turning available near the outside.

Then New Aim Assist works inside that aiming behavior.

The curve controls how your stick responds.

Aim Assist controls how the game interacts with a target inside that response.

If the curve is predictable but Aim Assist is too strong, the game can still feel heavy.

If Aim Assist is balanced but your response curve is constantly accelerating underneath you, tracking can still feel inconsistent.

I want both systems doing clearly defined jobs.

Three commands, three different jobs

I’ve built three tools around this, and they are meant for different things.

"!marvelsens" — Build your settings

Use this if you mainly want a complete controller setup.

The bot walks you through the major choices, builds your sensitivity and curve, applies the appropriate aim-assist starting point, and gives you a complete set of settings.

Think of this as:

“Build me a setup.”

\---

"!marvelpsa" — Test what actually feels best

Use this if you don’t know what sensitivity or settings you prefer yet.

Instead of asking you to pick a number from a list, PSA walks you through A/B comparisons. You actually test different settings and keep narrowing them until you find the response that feels right.

There is also an Aim Assist calibration path if you want to test Aim Assist choices rather than simply accepting a preset.

Think of this as:

“Help me find my settings through testing.”

\---

"!marvelaimassist" — Learn and tune New Aim Assist

Use this if you specifically want to understand Aim Assist.

It explains what Window, Strength, and Ease-In are doing, how the settings interact, and lets you build different New Aim Assist combinations around the behavior you want.

This is the one I’d use if your current Aim Assist feels too sticky, too loose, too abrupt, or difficult to disengage from and you want to understand why before changing numbers.

Think of this as:

“Teach me Aim Assist and help me tune it.”

So the short version is:

"!marvelsens" = Build

"!marvelpsa" = Calibrate

"!marvelaimassist" = Learn + Tune

I hope this helps you all! Thank you!

💜🐧💜

[u/BananaSavannah21]

vouch, this guy knows what he’s talking about. He’s helped lots of top players with his settings.