Method

How ConsoleAim works

This page describes what the converter actually does — which inputs it reads, how a stored answer is produced, what is estimated rather than measured, and where the limits are. If a claim here and the app ever disagree, the app is what is wrong.

Why a controller is not a mouse

Mouse and keyboard sensitivity is a ratio: a count of mouse travel to a number of degrees turned. Because a mouse reports distance and a camera maps distance to rotation, the arithmetic is exact and a converter only needs the game's yaw constant.

A thumbstick reports a deflection, not a distance. The game decides what that deflection means: it subtracts a dead zone, runs the remainder through a response curve, and applies a turn rate. Every title makes those three decisions differently, and several let the player change them.

So a controller conversion cannot copy a number across. It has to compare what each game does with the same stick movement — which is why ConsoleAim asks about the response curve you use and puts the answer on the target game's own slider scale.

What the converter asks for

Four things, and nothing else: the game you play now, the game you are moving to, the response curve you use in the source game, and your horizontal and vertical sensitivity.

It does not ask for a controller, a dead zone, an acceleration setting, a field of view or an ADS setting. That is a deliberate limit, and it is also why the picture below can never be complete — see what it does not account for.

How the value is produced

1. Your setting is read as your position on your own slider. If 42 on a 100-point slider is your value, that is 42% of the range, whatever the number means in that game.

2. The nearest stored level is taken. The answer bank holds answers on a 5% sensitivity grid, so a value between two levels uses the closer one rather than an interpolated guess.

3. The curve decides which record is read. Each game's curve menu is held by name — Linear Ramp, Exponential Ramp and Dual Zone for Overwatch 2, Classic, Steady, Fine Aim, High Velocity and Linear for Apex Legends, and so on — and the record for the curve you selected is the one used. A curve the bank has no record for produces no value, never a substitute.

4. The answer is expressed on the target game's own scale, then snapped to the steps its slider actually allows. If the arithmetic lands between two steps, the nearer step is used and the result says so.

5. The curve to pair with it comes back with the number. A converted sensitivity set to a curve the game does not have is not a conversion, so the recommended curve is part of the answer.

What is measured, and what is estimated

Nothing in a cross-game conversion is measured. ConsoleAim has not put a controller on a rig and timed a camera rotation in any of these games. The stored answer is a precomputed best estimate, derived from each game's documented settings and from a modelled maximum turn rate held in its profile — not from a laboratory reading, and not from a value the developer published.

That is why a result is labelled an estimate rather than a measurement, and why the confidence on every stored answer is the same: estimated. The app has no high-confidence cross-game answers, because it holds no measurement that would earn one.

Two things in ConsoleAim are read live, and neither is a game measurement: the dead zone tester reads your controller's own stick position through the browser's Gamepad API, and the Aim Assist Baseline times your own input against on-screen targets. Both measure you, not the game.

The answer bank holds nine controller titles. The converter currently publishes 7 of them.

What a conversion does not account for

Dead zone. Your source game is read at the bank's baseline dead zone, and the target is returned at a neutral anchor, because the converter has no input for either. If you run an unusually large or small dead zone, the feel will differ from the number.

Acceleration and boost. Same story: baseline on the source side, neutral on the target side. Titles that ramp turn speed with stick deflection are the ones most likely to feel different from a converted value.

Aim assist and aim ease-in. Neither is modelled. They change how a shot tracks a moving target even when the turn rate matches.

Field of view and zoom. A wider FOV changes how far the camera travels for the same rotation. The converter does not take FOV, and it does not convert ADS or per-optic zoom settings — those are separate controls in each game and are not entered here.

Patches. Games change their response, curves and dead zone handling between updates. A converted value carries the game model ConsoleAim holds, not necessarily the build you are playing today.

Resolution of the answer. A 5% grid and the target game's slider steps cap how precise the answer can be. Two different source values can honestly land on the same target value.

How to check a conversion yourself

Set the converted value and the recommended curve in the target game, then test in a place where nothing is shooting at you.

Turn test: hold the stick fully to one side and time how long a complete 360° camera rotation takes. Compare it with the same measurement in your source game. A conversion built on a modelled turn rate should bring the two close, not identical.

Fine-control test: nudge the stick a small amount and check the camera moves as little as you expect. This is where an unmodelled dead zone or curve mismatch shows up first.

Time-to-target test: pick a fixed landmark, look away, and sweep back to it. If you consistently overshoot, move the value down a point; if you undershoot, move it up.

Repeat the whole thing at your real ADS settings — the hipfire value the converter gives you says nothing about your aim while zoomed.

If a conversion looks wrong

Conversion values are meant to be checked, not trusted. If one looks off, the most useful report says which two games, which value you entered, which curve you use in each, which value you got back, what the game is doing instead, and which platform and patch you are on.

Send it through the contact page. Reports are read and go into how the stored answers are reviewed; ConsoleAim will not fill a gap with an invented measurement to close one.

Reporting a wrong conversion or sending test feedback

Use the contact page for either. Include the two games, both sensitivities, the curve you use in each, the platform and the patch. Reports about a value you can reproduce are the ones that can be acted on.

Contact support

ConsoleAim is an independent tool and is not affiliated with, endorsed by or sponsored by any game developer or publisher. It does not modify, inject into or run inside any game, and provides no cheat, exploit, automation or unfair-advantage functionality.

ConsoleAim is an independent tool. It is not affiliated with, endorsed by, sponsored by or approved by any game developer or publisher. All game names, titles, logos and trademarks are the property of their respective owners and are used only to describe the games ConsoleAim converts between. ConsoleAim does not modify, inject into or run inside any game, and provides no cheat, exploit, automation or unfair-advantage functionality. Conversion values are ConsoleAim's own best estimates, not official developer values and not measurements taken from the games.