3D Aim Trainer to Half-Life 2 sensitivity converter
Convert your 3D Aim Trainer sensitivity to Half-Life 2 instantly. Same hand motion, perfect muscle memory across both games.
Why 3D Aim Trainer sens doesn't match Half-Life 2
At 0.4 sens on 800 DPI, 3D Aim Trainer sweeps 129.89 cm across a full 360°. To reproduce that exact arm motion in Half-Life 2, you need sens 0.4 — about 1.00× your 3D Aim Trainer number. Nothing changed except Half-Life 2's yaw of 0.022 vs 3D Aim Trainer's 0.022; the centimeters of mouse travel stay the same.
- 3D Aim Trainer · Yaw
- 0.022
- Half-Life 2 · Yaw
- 0.022
- 3D Aim Trainer · Default FOV
- 103
- Half-Life 2 · Default FOV
- 90
How to apply the converted sensitivity in Half-Life 2
Open Half-Life 2's settings, paste the converted sensitivity into the sens field and keep your 800 DPI if that matches how you play 3D Aim Trainer. Run a 360° check on a practice map: the mouse sweep should cover roughly 129.89 cm on your pad — the same distance as in 3D Aim Trainer. Only start tuning if the sweep feels off, never before the 360° check.
Common mistakes when converting 3D Aim Trainer to Half-Life 2
- Copying the sens without matching DPI
A converted 3D Aim Trainer-to-Half-Life 2 number is tied to the DPI you used during conversion. If your Half-Life 2 mouse profile runs a different DPI, the math no longer holds — use Sens Converter's 'different DPI' toggle instead of eyeballing.
- Trusting eDPI across engines
Matching eDPI between 3D Aim Trainer and Half-Life 2 does not give matching turn speed, because their yaws are 0.022 and 0.022. Always compare cm/360° (or in/360°), not eDPI, when swapping games.
- Ignoring scoped and ADS overrides
3D Aim Trainer and Half-Life 2 each apply their own scoped / ADS multiplier on top of the base sensitivity. Converting the base is step one — confirm the per-zoom multiplier in Half-Life 2 separately, otherwise scoped aim will feel wrong even with a perfect hipfire match.
3D Aim Trainer → Half-Life 2 FAQ
Why is my converted Half-Life 2 sens different from my 3D Aim Trainer number?+
Half-Life 2 has a yaw of 0.022 compared to 3D Aim Trainer's 0.022. Their ratio is about 1.00×, so Sens Converter multiplies your 3D Aim Trainer sens by that factor to keep cm/360° identical. The raw number looks different, but the arm motion is the same.
Should I keep the same DPI in 3D Aim Trainer and Half-Life 2?+
Yes, when possible. Keeping DPI identical means only the in-game multiplier changes, which is the cleanest switch. If you run different DPI in Half-Life 2, enable 'different DPI' in the converter and it absorbs the extra math.
How many decimals should I use in Half-Life 2?+
Half-Life 2 accepts at least 3 decimals; 4-6 is common. Sens Converter outputs enough precision that rounding to 3 decimals keeps the 360° error below one millimetre on a typical 800 DPI setup.
Does FOV affect 3D Aim Trainer to Half-Life 2 conversion?+
For the base sensitivity, no — sens is independent of FOV in both engines. If you use a 0% MonitorDistance or similar scaling mode in either game, convert at the FOV you actually run in-game.