GameMapa

Mouse sensitivity in ARC Raiders: what is known and what is not

Work out cm/360, in/360 and eDPI on the CS 2 side, then carry the feel into ARC Raiders by hand. Automatic conversion is off: no turn coefficient for ARC is established.

The yaw value for ARC Raiders is not established in any public source, so conversion is disabled. The CS 2 ↔ CS 2 pair below still works — carry the resulting cm/360 into ARC by feel.

A whole number above zero. There is deliberately no upper limit: no published standard for maximum DPI exists.

CS 2: from 0.01 to 100, step 0.01.

Fill this in if you are switching mice as well. Defaults to the same DPI.

It does not change the turn distance, because the formula uses the absolute value. The box is here so you can see that instead of guessing.

Result

cm/360, cm25.98
in/360, inches10.23
eDPI1,600
Sensitivity in the target game2.00

m_yaw = 0.022 comes from community command references. Valve does not confirm it officially: developer.valvesoftware.com returns 403.

m_yaw=0.022 — спільнотні довідники; первинне джерело Valve (developer.valvesoftware.com) віддає 403. Вертикальний множник (m_pitch) не встановлений окремим джерелом.

How we calculate

ARC Raiders is a new game, and documentation of its mouse scale simply does not exist yet. We went looking for a degrees-per-count coefficient and found it in no public source: not in the patch notes, not in the open part of the sensitivity references. That is why the ARC row in our data table is empty rather than filled with a plausible-looking number. Those are different things, and we are not going to confuse them.

The practical workaround is the one that worked in every shooter before calculators existed. Compute cm/360 for CS 2, that is, how many centimetres of mouse movement a full turn takes, then adjust sensitivity in ARC Raiders until a full turn demands the same hand movement. Check yourself against a fixed landmark: a full turn should bring the crosshair back to exactly the same spot.

The arithmetic on the CS 2 side is: degrees per inch = m_yaw × sensitivity × DPI, inches per 360° = 360 ÷ degrees per inch, centimetres = inches × 2.54. The value m_yaw = 0.022 comes from community references, because the official Valve page returns 403, and it is flagged as unconfirmed. eDPI (DPI × sensitivity) is shown for comparison within one game; carrying it between games does not work.

Sources

checked 18 August 2026

Questions and answers

Why is conversion for ARC Raiders disabled?

Because the turn coefficient, meaning how many degrees one unit of sensitivity gives per mouse count, is not established in any open source. The game is recent and the community has not settled on documentation yet. Until the number exists, we show an empty field rather than a guess.

What does the calculator on this page actually compute?

The CS 2 ↔ CS 2 pair: cm/360, in/360, eDPI, and the sensitivity recalculation when you change DPI. That gives you a reference in centimetres which you can carry into ARC Raiders by hand.

How do I set sensitivity in ARC Raiders without a coefficient?

Compute cm/360 for a game you know well, then change sensitivity in ARC until a full turn takes the same movement of the mouse across the desk. The easiest way to check is against a fixed point on a flat surface.

Will the same eDPI work?

No. eDPI ignores the coefficient of the specific game, so the same figure in CS 2 and in ARC Raiders produces different turn angles. It is a metric for comparing players within one game.

What has to happen for conversion to be enabled?

A public, verifiable source giving the yaw value for ARC Raiders. As soon as one appears, the row in the data table gets filled in and the option in the select becomes active.

All ARC Raiders guides

Unofficial tool. Not affiliated with Embark Studios.