AimCurve · versioned hip-fire conversion

Sensitivity Converter

Convert hip-fire sensitivity between supported FPS games, keep the same physical cm/360 and see the formula behind the result.

AimCurve hip-fire conversionVersioned constants · transparent formula
Target sensitivity
Physical distance
Source eDPI
Target eDPI
ModelHip-fire 360°

Choose games and values to see the documented conversion.

Versioned game notes will appear here.

How to use: Sensitivity Converter

Choose the source and target game.

Enter the exact source sensitivity and mouse DPI.

Copy the rounded target value, then confirm it in a repeatable in-game 360-degree measurement.

What the result actually measures

The converter uses each supported game’s default horizontal angular scale to preserve physical rotation distance. It also shows source/target eDPI, but eDPI is labeled game-specific rather than treated as a universal comparison.

Measurement boundary: Matching cm/360 does not guarantee identical perceived aim. FOV, zoom multipliers, acceleration, frame rate, input processing and game mechanics can change the feel.

How to interpret the output

Target sensitivity

The displayed value preserves the modeled hip-fire angular distance under the documented default constants.

cm/360

This is the estimated physical distance needed for a full turn at the entered DPI. Real DPI can deviate from the label.

eDPI

DPI multiplied by in-game sensitivity is useful within one game, but different games use different scales.

Troubleshooting unexpected results

Converted aim feels different

Compare FOV and aspect ratio, disable acceleration, verify DPI and separate hip-fire from scoped settings.

A game is missing

AimCurve includes only constants we can document and explain. More games are added after verification, not by copying unreviewed ratios.

Frequently asked questions

Does the converter change my game settings?

No. It calculates a value for you to enter manually.

Does it convert scoped sensitivity?

No. Scope and hero-specific multipliers require separate models and clear context.

Is the result exact?

The arithmetic is deterministic for the documented constants; perceived feel and real DPI still vary.