🌐

Match Your Aim Across Games

Exact Physical 360° Rotational Distance & Verified Scope Multipliers. Zero bloat, zero paywalls.

CONVERT FROM
HLO

Halo Infinite

Click to change
CONVERT TO
TF2

Team Fortress 2

Click to change
Target Sensitivity
0.6818
Distance / 360° 76.20 cm
Imperial / 360° 30.00 in
Effective DPI (eDPI) 545
Estimated Pad Fit: XL Tournament Pad (>=45cm) 40.8 cm / 360°
25cm (M) 35cm (L) 45cm (XL) 90cm+ (Deskmat)

Detailed Engine & Conversion Mechanics: Halo Infinite to Team Fortress 2

Technical Breakdown

When porting your aim from Halo Infinite to Team Fortress 2, direct 1:1 number copying fails because of differences between the Slipspace Engine and Source camera rotation pipelines. Halo Infinite operates at an angular yaw multiplier of 0.015 per mouse count, whereas Team Fortress 2 registers 0.022 per tick.

Mathematical Conversion Ratio: To maintain an identical physical mousepad distance for 360° rotational clearing, multiply your current Halo Infinite sensitivity by exactly 0.6818.

Team Fortress 2 Console Command sensitivity {VAL}
Team Fortress 2 Configuration File Steam\steamapps\common\Team Fortress 2\tf\cfg\config.cfg
Input Precision Limit 6 decimal places

💡 Optimization Notes for Team Fortress 2:

The foundation of Source engine mouse physics. Matches CS2, Apex, and Quake 1:1.

DPI Conversion Matrix

Mouse DPI Target Game Sens cm / 360° Feel Bracket
400 DPI0.6818152.4 cmUltra-Low (Full Arm)
800 DPI0.681876.2 cmUltra-Low (Full Arm)
1200 DPI0.681850.8 cmUltra-Low (Full Arm)
1600 DPI0.681838.1 cmTactical Low (Arm)
3200 DPI0.681819.1 cmHigh (Wrist / Speed)

Why doesn't sensitivity transfer 1:1 natively?

Each game engine defines its own angular displacement per mouse count (yaw). For example, Valorant uses Riot's calibrated standard of 0.07° per tick, while Source/Source 2 engines (CS2) default to m_yaw 0.022. AimSync bridges these differing rotational coefficients so your physical mouse displacement on the desk remains exactly identical.

Does FOV affect this conversion?

This calculator preserves hipfire 360° rotational distance, ensuring muscle memory for turning and clearing corners stays intact regardless of FOV.

Where do the raw yaw values come from?

Engine multipliers are extracted directly from official developer SDKs, engine source repositories (Valve Source/Source 2 m_yaw 0.022, Riot ShooterEngine 0.07), and verified community telemetry. Unverified proprietary titles feature the Raw Yaw Override input for direct empirical adjustment.