How we verify our data
SensLib's product is accuracy. Sensitivity tools are only useful if the numbers behind them are right — one wrong conversion value silently ruins every result a player copies. This page documents exactly how our data is produced, checked, and kept current.
The rules
- Two independent sources per value. Every game constant (yaw values, pro-player settings, crosshair codes) is checked against at least two unrelated sources before it publishes. Sources are cited on the page where the value appears.
- Physical verification of the math. Our conversion formulas are validated against community-measured physical 360° turns — real distances measured on real mousepads, not just arithmetic round-trips. A round-trip test can pass with two wrong values; a physical measurement cannot.
- Visible last-verified dates. Every data-backed page shows when its values were last checked. Stale data is marked stale, not hidden.
- A public correction channel. Every data page carries a report-an-error link. Corrections are triaged weekly and fixed fast; we note the change on the page.
- No scraping. We do not copy competitor databases. Their errors would become ours, and their staleness is the problem we exist to fix.
The golden tests
Our conversion engine runs an automated test suite on every build, anchored to physical reference measurements — for example, Valorant 0.4 at 800 DPI must produce a 40.8 cm/360, and the Valorant-to-CS2 ratio must be exactly 3.18182 (0.07 ÷ 0.022). If any test fails, the build does not ship.
Coverage and status
Games are added to the converter only after their yaw value clears the two-source rule. Games without import-code systems (Deadlock, Marvel Rivals) get settings guides instead of fake codes — we say what a game can and cannot do.
| Game | Yaw (deg/count) | Converter status |
|---|---|---|
| Valorant | 0.07 | Supported — yaw verified |
| Counter-Strike 2 | 0.022 | Supported — yaw verified |
| Apex Legends | 0.022 | Supported — yaw verified |
| Overwatch 2 | 0.0066 | Supported — yaw verified |
| Team Fortress 2 | 0.022 | Supported — yaw verified |
Found an error?
Email corrections@senslib.com with the page and the value you believe is wrong — ideally with a source or an in-game measurement. Verified corrections typically ship within days, and the page's last-verified date updates so the fix is visible.
Related: About SensLib · Contact