SCORE 0
60
ACC –

Measuring…

Move the mouse straight to the right along your ruler for exactly 20 cm, then press Space.

0
counts (X)  ·  off-axis (Y): 0

Paused

Pointer released. Click Resume to lock the mouse and continue.

CS2 AIM TRAINER

Esc releases the mouse (pauses). R restarts a run. Z zeroes the Sens-lab readout.

Your CS2 settings

Type either sensitivity or cm/360 – the other follows. Rotation is sensitivity × m_yaw(0.022)° per mouse count, identical to CS2 (m_pitch is also 0.022). Resolution does not change sensitivity in CS2, and does not here.

Mouse input

Count scale multiplies every mouse delta. Keep it at 1 unless the Verify / calibrate tab shows your browser reports scaled movement (it can when the Windows or browser zoom is not 100%).

Render

4:3 renders with an exact 90° horizontal / 73.74° vertical FOV (CS2’s reference). The picture is then stretched to your monitor exactly like CS2’s stretched 4:3, so targets look wide and move across the screen at the same speed per mouse count. For a faithful match use fullscreen (F11 or the checkbox) on the same monitor you play CS2 on.

Crosshair

1 · Prove 1:1 against CS2

  1. Set the same sensitivity & DPI in CS2 and here. Windows pointer speed 6/11 and “Enhance pointer precision” off; CS2 m_rawinput 1.
  2. In CS2 read your view angles with cl_showpos 1 (or the getpos console command, which prints setang pitch yaw 0), then drag the mouse a fixed distance along a ruler (e.g. one full 360° turn = – cm).
  3. Open Sens lab here, press Z, and move the mouse the same distance. The yaw readout must show the same degrees as CS2 (360° for one full turn). The counter shows raw counts: 360° = – counts.

2 · Check the browser isn’t scaling movement

Tape a ruler to your mousepad, place the mouse at 0, press Measure, drag straight right the full distance, press Space.

Run history

WhenModeScoreAccAvg TTKSenscm/360