Tactical FPS · Updated 2026-08-09

Counter-Strike 2 input lab

Measure CS2 aim distance, event consistency and key combinations without turning one professional profile into a universal recommendation.

Default modelm_yaw 0.022AimCurve assumes the default horizontal yaw value; a changed console value invalidates the model.
Rate evidenceMedian + P95 intervalBrowser delivery stability matters more than one momentary peak.
Bind scopeCombat / buy / UISeparate contexts before flagging duplicate keys.

Separate physical distance from game feel

AimCurve can preserve modeled hip-fire cm/360, but view motion, frame pacing and a player’s existing motor pattern still affect perception. Keep the mathematical transfer and the comfort decision as two separate results.

Record any non-default yaw command with the profile. A converter that silently assumes the default is worse than no converter because its output looks precise while using the wrong model.

Repeatable checklist

  • Confirm default yaw or record the custom value
  • Measure physical turn distance
  • Save DPI, sensitivity and date together

Screen mouse delivery as a distribution

A browser cannot certify USB firmware rate. It can reveal whether pointer events delivered to the page form a stable interval distribution under repeatable movement.

Compare the same five-second motion with the same browser state. If the result changes after moving USB port, power mode or background load, the difference is a troubleshooting clue rather than an automatic hardware verdict.

Repeatable checklist

  • Close heavy background work
  • Run three movement samples
  • Compare median and 95th percentile intervals
Game-specific boundary: Custom m_yaw, acceleration or driver processing changes the assumptions behind a standard conversion.
Do not lose the baseline

One change. Same test. Clearer answer.

Keep the device, connection, platform, game build and previous setting beside every result.