Engineered for Aim Athletes.
Grounded in Sub-Pixel Math.
SensScale was founded by competitive FPS engineers and aim enthusiasts who grew exhausted by bloated, paywalled legacy calculators with outdated yaw numbers and disruptive ads. Our mission is singular: provide instantaneous, zero-latency 1:1 camera rotation conversion across every major 3D engine in existence.
0ms Input Latency
All mathematical conversions compute locally in your browser. No server round-trips, no loading spinners, and zero layout shift ($CLS = 0$).
100% Free Forever
Competitors paywall newly released games behind $3-$5 monthly memberships. SensScale provides all 120+ engines completely unrestricted to the esports community.
Verified Camera Yaws
Constants are extracted directly from native engine memory dumps, SDK headers, and game configuration files—never guessed or estimated.
How Engine Camera Yaw Multipliers Work
When you move your physical mouse across a pad, its optical sensor records discrete counts of movement (determined by your hardware DPI). In an FPS game, the game engine does not move a 2D cursor; instead, it rotates a 3D camera around its vertical axis (Yaw) and horizontal axis (Pitch).
Because different engines assign drastically different native angular constants to their sensitivity sliders, your muscle memory cannot rely on the raw number. For instance:
Why cm/360° is the Universal Aim Standard
While "eDPI" is convenient for talking to teammates within the exact same game, it has zero scientific validity across different engines. A 280 eDPI in Valorant equals 890.9 eDPI in Counter-Strike 2.
Human muscle memory does not store slider floats or game-specific eDPI values; it relies on proprioception—the precise motor memory of how many millimeters your wrist, forearm, and shoulder must travel across your mousepad to snap your crosshair 90 degrees to an enemy's head.
cm/360 = (360 × 2.54) / (In-Game Sensitivity × Native Yaw × Hardware DPI)
SensScale Telemetry Rig & Verification
Every game engine in our database undergoes a strict three-tier verification protocol before being marked as verified:
We inspect engine configuration files (GameUserSettings.ini, cs2_user_keys.vcfg, settings.cfg) and verify the internal pitch/yaw cvars.
Using optical encoders on high-precision mechanical rigs, we transmit 10,000 counts of raw mouse input and record angular rotation in degrees down to four decimal places.
We cross-validate calculated numbers with Tier-1 professional athlete tournament configurations to ensure full alignment with competitive reality.