Sens ConverterSens ConverterDrive your aim
Menu
Game data

Game Data Standard

476 game records are loaded from public sensitivity sources. Loaded values are unverified and treated as estimates.Methodology

Games476
StandardLoaded Yaw
Loaded records: 476. Values come from public and competitor sources. They are not all independently verified, and several fields use documented fallbacks. Treat every result as an estimate.

Sources and verification status

The loaded records combine competitor data and records imported from public sources. The source labels recorded in the repository include Aiming.Pro and SensConverter Pro for competitor records, and the mouse-sensitivity.com public simple converter for records derived or imported from that snapshot.

  • Source-provided data: yaw, sensitivity bounds and sensitivity step where the imported source supplied usable values.
  • Calculated or fallback data: the runtime uses a 0.001 sensitivity-step fallback, a 0.0001–100 bounds fallback where bounds were unavailable, and default-FOV yaw approximations for some source-flagged non-linear records.
  • Estimates: converter outputs are deterministic calculations on these records, but they are estimates, not guaranteed in-game aim parity.
  • Owner-approved publication: some records were force-published or imported from raw snapshots at the site owner’s request. Publication approval is not independent verification.
  • Not stored: exact per-record source URLs, access dates and independent testing history are not stored in the runtime records, so they are not displayed per game.

Not every record has passed an independent evidence review. The limitations stored with each record are shown on its game page, and theconversion methodology explains the calculation.

What every record must include

  • Game name, identifier and slug.
  • Game version and the supported mode. The initial model covers hip-fire only.
  • A yaw parameter with explicit units: degrees per count at sensitivity 1.
  • Supported sensitivity minimum and maximum values.
  • Whether DPI, eDPI and cm/360 are supported by the loaded model.
  • A source label where the imported record provides one. Exact source URLs, access dates and independent testing history are not stored in the runtime records.
  • Publication metadata from the runtime approval record, such as the brief and date.
  • Known limitations, including mode, version and fallback caveats.
  • Update metadata where the runtime record provides it.

Data standard

Every record uses the same shape: a game identifier, a supported mode, a yaw value, sensitivity bounds, step, publication metadata and known limitations. Records with missing or invalid yaw are excluded from the converter.

The runtime validation layer enforces record shape, positive yaw, valid bounds and approval metadata before a record can be loaded.

What is not included

  • Values that conflict across sources without a documented resolution.
  • Values inferred from a different game, engine or mode.
  • ADS, scope or FOV multipliers that have not been separately implemented and tested.

About the current coverage

The loaded records come from competitor data and the mouse-sensitivity.com public simple converter. Some yaw values were missing or outside a basic sanity range; those records were excluded. Where bounds were unavailable, the runtime uses a broad fallback and labels the limitation. Exact per-record provenance beyond the stored source label is not available for every record.

The conversion methodology explains how a loaded record is used and what the model deliberately leaves out. The sensitivity conversion guide explains how yaw and input behavior affect a converted value.

Last reviewed: 2 November 2026