Rainbow Six Siege Sensitivity Guide

A repeatable way to choose, measure, and verify your settings

Content and sources reviewed July 23, 2026.

Start with your measured setup

Calculate DPI, eDPI and cm/360 before changing settings

Enter your current DPI, Siege sensitivity, and usable mousepad width. The calculator estimates turn distance and checks whether swipe space is the actual constraint.

Open the R6 cm/360 calculator

There is no universal “best” sensitivity

A sensitivity value is useful only in context. Mouse DPI, Siege hipfire values, field of view, aspect ratio, optic magnification, available mousepad space, and input device all affect the setup you can actually use.

This guide does not prescribe a pro-player range or promise a fixed adaptation time. It gives you a controlled process: record the current setup, change one variable, repeat the same drill, and keep the result only when the evidence is consistent.

1. Record the complete baseline

Before changing anything, save enough information to reproduce the current setup:

  • Mouse DPI and the active mouse profile.
  • Horizontal and vertical hipfire sensitivity.
  • Every ADS value you use, including the optic magnification.
  • Field of view, aspect ratio, resolution, and input device.
  • The game version and test date, because updates can change available settings.

2. Measure physical turn distance

For mouse input, cm/360 is the desk distance required for one full in-game turn. Mark a starting point on the mousepad, aim at a fixed in-game reference, complete one turn, and measure the distance. Repeat the measurement to catch hand and alignment error.

A calculation can check the measurement when the game’s yaw scale is known. The physical measurement remains valuable because it tests the complete live setup, not just stored numbers.

cm/360 = (360 × 2.54) ÷ (DPI × sensitivity × yaw)

The yaw term is game-specific. eDPI alone does not make sensitivities comparable across different games.

3. Change one variable and run the same drill

Use a practice mode where the starting position and targets can be repeated. Keep DPI, FOV, aspect ratio, grip, and hardware unchanged while testing sensitivity.

  1. Check whether one comfortable mouse movement can cover the turn you need without reaching the edge of the pad.
  2. Repeat a wide target switch and note consistent overshoot or undershoot.
  3. Repeat a small correction on a distant point and note whether you can stop on target.
  4. Repeat a short tracking pass. Do not mix a new sensitivity with a new FOV or DPI.
  5. Make a small adjustment only when the same error appears across repeated attempts; then restart the drill.

What to record after each test

  • The exact value tested—not “a little higher.”
  • Which drill exposed the problem.
  • Whether the error was repeated overshoot, repeated undershoot, loss of control, or insufficient turn space.
  • Any hardware or game setting that changed during the session.

4. Treat ADS and each optic separately

Siege provides separate sensitivity settings for optic magnifications. Ubisoft’s Y5S3 guide documents the post–Shadow Legacy ADS system and the mathematical basis used to convert older ADS values.

A converted ADS value is a starting point, not proof that every optic will look or feel identical. Magnification and field of view change the visual motion on screen.

  1. Stabilize hipfire first.
  2. Generate an ADS baseline from the documented calculator.
  3. Test one optic at a time from the same position and target.
  4. Save any manual correction with the optic name and test date.

5. Use cross-game conversion as a baseline

Matching cm/360 preserves the physical distance for a full turn. It does not equalize field of view, zoom, recoil, movement speed, or target scale.

Our cross-game converter is deliberately limited to Siege, CS2, and VALORANT. The listed yaw references are empirical values cross-checked against a public reference and covered by calculation tests; they are not publisher guarantees.

R6 → CS2 / VALORANT

Troubleshooting by observed error

Repeated overshoot in the same drillLower only the sensitivity being tested, then repeat the identical sequence.
Repeated undershoot or running out of turnRaise only that value, or confirm that mousepad space is not the actual constraint.
Hipfire is stable but one optic is notLeave hipfire unchanged and retest only that optic’s ADS value.
Results vary from attempt to attemptCheck for a changed DPI profile, acceleration, unstable frame delivery, grip changes, or an inconsistent test position before editing sensitivity.
A converted game feels differentConfirm DPI and base sensitivity, then account for FOV and zoom differences instead of forcing numerical equality.

Controller and console inputs

The mouse cm/360 formula does not describe an analog stick. Controller response curves, dead zones, acceleration, and maximum turn speed interact with horizontal, vertical, and ADS settings.

For controller testing, record those variables and repeat the same camera movement from the same stick position. This guide intentionally does not publish “best” console ranges without a controlled device-specific test.

What this method cannot prove

  • It cannot identify one value that is best for every player.
  • A short drill cannot prove long-term performance improvement.
  • A mathematical conversion cannot make different games visually identical.
  • A missed shot alone cannot diagnose sensitivity; positioning, timing, recoil, and input consistency also matter.

Sources and review trail

We separate publisher documentation from measurement methodology and clearly label empirical cross-game references.

Create a documented ADS baseline

Enter your old ADS value, FOV, and aspect ratio, then test each generated optic value using the workflow above.

Open the ADS calculator