Destiny 2 to Hunt: Showdown sensitivity converter
Convert your Destiny 2 sensitivity to Hunt: Showdown instantly. Same hand motion, perfect muscle memory across both games.
Why Destiny 2 sens doesn't match Hunt: Showdown
At 0.4 sens on 800 DPI, Destiny 2 sweeps 432.95 cm across a full 360°. To reproduce that exact arm motion in Hunt: Showdown, you need sens 0.406154 — about 1.02× your Destiny 2 number. Nothing changed except Hunt: Showdown's yaw of 0.0065 vs Destiny 2's 0.0066; the centimeters of mouse travel stay the same.
- Destiny 2 · Yaw
- 0.0066
- Hunt: Showdown · Yaw
- 0.0065
- Destiny 2 · Default FOV
- 90
- Hunt: Showdown · Default FOV
- 80
How to apply the converted sensitivity in Hunt: Showdown
Open Hunt: Showdown's settings, paste the converted sensitivity into the sens field and keep your 800 DPI if that matches how you play Destiny 2. Run a 360° check on a practice map: the mouse sweep should cover roughly 432.95 cm on your pad — the same distance as in Destiny 2. Only start tuning if the sweep feels off, never before the 360° check.
Common mistakes when converting Destiny 2 to Hunt: Showdown
- Copying the sens without matching DPI
A converted Destiny 2-to-Hunt: Showdown number is tied to the DPI you used during conversion. If your Hunt: Showdown 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 Destiny 2 and Hunt: Showdown does not give matching turn speed, because their yaws are 0.0066 and 0.0065. Always compare cm/360° (or in/360°), not eDPI, when swapping games.
- Ignoring scoped and ADS overrides
Destiny 2 and Hunt: Showdown 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 Hunt: Showdown separately, otherwise scoped aim will feel wrong even with a perfect hipfire match.
Destiny 2 → Hunt: Showdown FAQ
Why is my converted Hunt: Showdown sens different from my Destiny 2 number?+
Hunt: Showdown has a yaw of 0.0065 compared to Destiny 2's 0.0066. Their ratio is about 1.02×, so Sens Converter multiplies your Destiny 2 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 Destiny 2 and Hunt: Showdown?+
Yes, when possible. Keeping DPI identical means only the in-game multiplier changes, which is the cleanest switch. If you run different DPI in Hunt: Showdown, enable 'different DPI' in the converter and it absorbs the extra math.
How many decimals should I use in Hunt: Showdown?+
Hunt: Showdown 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 Destiny 2 to Hunt: Showdown 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.