ADS Sensitivity Feels Wrong? Choose What You Want to Match

“Make ADS one-to-one” sounds precise until two players mean different things by one-to-one. One wants the same hand movement for the same camera angle. Another wants a similar correction for a target close to the center of the screen.

Those are different goals, particularly when magnification changes.

Separate the matching methods

A “0% monitor distance” convention generally refers to center-focused, infinitesimal matching. Check the calculator's exact convention and axis; the label does not mean zero sensitivity or that every point on the screen is matched.

Why zoom changes the comparison

In a standard perspective projection, screen position depends nonlinearly on the angle from the camera center. Increasing magnification changes how that angular movement appears on the display.

MDN's perspective-projection explanation provides the underlying camera context. Actual game scopes may use additional rules, animations and per-optic scaling, so a generic camera equation is not a complete implementation guide for every game.

This is why copying a hip-fire number into an ADS field can disappoint. The field may be a multiplier, an independent sensitivity or part of a game-specific system.

Build a scope-by-scope comparison

Start with hip-fire that you have already verified. Then choose one optic and one task.

1. Record the game, optic, zoom state, FOV and all relevant sensitivity fields.
2. Choose a stationary target near the center for small-correction testing.
3. Pick a second target farther from the center for a wider correction.
4. Test the current setting on both tasks without changing your DPI.
5. Adjust only the relevant ADS control and repeat.
6. Save which task improved and which became less comfortable.

Keep target distance and zoom state consistent. A moving target or a changing optic can make a comparison feel different for reasons unrelated to the multiplier.

Use the DCPROSENS ADS calculator as a starting aid. Check the method and game support it exposes; verify the result inside the game rather than treating the calculated number as proof of a perfect match.

Interpret the symptom

If every camera mode feels unfamiliar after switching games, read same cm/360, different feel before modifying each scope independently.

Keep a record you can restore

Create one row per optic with the old value, new value, matching goal and observed result. “Better” is too vague. Write “small corrections required less overshoot, but broad turns needed more lifting,” if that describes what you observed.

There may be a trade-off rather than a single winner. Choose based on the task the optic serves, not because a decimal value looks more mathematically impressive.