Tune with evidence

Change the smallest setting that solves the problem.

Good tuning starts with a measurement, makes one controlled change and confirms that intentional movement still feels responsive.

Tune a deadzone floor

Measure the resting distribution, add a visible margin and check whether slow deliberate movement survives.

Controller tuning

Preserve cm/360

Carry a physical hip-fire reference across supported games, save the result locally and keep the formula.

AimCurve

Keep a local profile

Store device, DPI, sensitivity and deadzone notes together, then export a portable JSON backup.

Local only

The Keymap tuning loop

Baseline: record the current device state and in-game setting.
Measure: use the relevant lab under repeatable conditions.
Adjust: change one value at a time, in a small step.
Validate: confirm slow control, fast movement and consistency in the actual game.
Document: save the setting, DPI, connection and date in a local profile, then export a backup.

The workflow connects diagnostics to guided deadzone tuning, shareable AimCurve configurations and device-local profiles. Models whose constants or user-facing limitations cannot be explained and tested are intentionally excluded.