Guide

How to Convert Your CS2 Sensitivity to Rainbow Six Siege

If you already have a comfortable CS2 sensitivity, moving to Rainbow Six Siege should start by matching physical hip-fire turn distance, not by copying the same setting number. CS2 and R6 use different sensitivity scales, and R6 also applies the configurable MouseSensitivityMultiplierUnit from GameSettings.ini.

Quick CS2 to R6 formula

The calculator matches DPI × sensitivity × yaw. With the disclosed community anchors CS2 0.022 and R6 0.00573 at the official default R6 multiplier 0.02, the ideal raw same-DPI relationship is:

ideal R6 horizontal = CS2 sensitivity × 0.022 ÷ 0.00573

For example, CS2 sensitivity 1.00 at 800 DPI produces an ideal raw R6 value of about 3.8394. R6 accepts a whole-number horizontal slider from 1 to 100, so the legal starting value is 4. The calculator shows the remaining cm/360 difference and the custom multiplier that would make the chosen integer closer.

Why the converted value is only a starting point

Even when hip-fire cm/360 matches, CS2 and Siege have different pacing, recoil, aiming contexts, field-of-view behavior, and ADS systems. Siege also puts more emphasis on holding angles, clearing rooms, leaning, and making small crosshair adjustments around tight corners.

That is why the converted value should be treated as a first setting, not a final setting. The goal is to preserve your muscle memory well enough that you can start testing immediately instead of guessing from zero.

What changes when you move from CS2 to Siege

CS2 aim is often built around clean crosshair placement, counter-strafing, and quick corrections after movement. Siege has those same fundamentals, but the average engagement can feel more constrained. You may be holding a pixel angle, checking a doorway, or tracking a target through a small line of sight. A sensitivity that feels perfect for wide CS2 swings might still need slight refinement for Siege's tighter spaces.

For this reason, do not judge the conversion only by one large flick. Test slow tracking, micro-corrections, and recoil control too. Siege rewards stability as much as speed.

Keep your DPI consistent

Enter the DPI used in each game. If both values are the same, the DPI ratio cancels; if they differ, the target sensitivity changes. The calculator starts both fields at 800 DPI as an editable convenience, not as a Ubisoft or Valve default.

How to test your converted sensitivity in Siege

After copying your converted value, spend a few minutes testing common Siege actions. Track a target horizontally, flick between two fixed points, control recoil on a wall, and make small corrections while aiming down sights. If your crosshair constantly overshoots, lower the value slightly. If you keep stopping short of the target, raise it slightly.

Make small changes instead of large jumps. A 5-10% adjustment is usually enough to correct the feel without losing the benefit of your original CS2 muscle memory.

Common mistakes to avoid

Do not change your sensitivity after every missed shot. One bad round is not enough evidence that the setting is wrong. Look for repeated patterns instead: constant overshooting, constant undershooting, or trouble controlling recoil. Also avoid changing DPI, mouse pad position, ADS preferences, and in-game sensitivity all at the same time. Too many changes make the test meaningless.

A good workflow is simple: convert your CS2 value, play a short test session, make one small adjustment if needed, then test again. That gives your hand time to adapt while still letting you correct obvious problems.

Use the calculator

Use the R6 Sensitivity Calculator to enter your CS2 sensitivity, both DPI values, and your R6 multiplier. Review the ideal raw result, the nearest legal R6 slider, and both cm/360 values before testing in game.