DPI Wizard

Remember to disable acceleration as it is default on. View full update

No, it won't make any difference to go for an exact value like that.

Sensitivity is affected by framerate, so this game cannot be added.

This game does not have any numerical sensitivity setting available, just a slider with no numbers or notches.

This game does not have any numerical sensitivity setting available, just a slider with no numbers or notches.

Sensitivity is affected by framerate, so this game cannot be added.

Sensitivity in this game is affected by framerate, so it probably can't be added.

Hdeg 4:3 is the FOV type the game uses, the calculator will always default to the correct FOV type for the game you select. When you switch to Vdeg, you simply tell the calculator that you want for instance 72 vertical degrees. It will then calculate what you actually need to configure in the game to get exactly this. Absolutely, the output will then tell you what multiplier you need to use to get the Hdeg 4:3 FOV you want. Any of the FOV types work for this, but the output doesn't tell you all of them. It only shows you the true vdeg and hdeg, so it's easiest to use one of them. Vdeg is also the most commonly used type. If you already know your preferred FOV, let's say 90 Hdeg 4:3, you can perfectly fine use this for all games that supports changing FOV.

You can't convert the multiplier between games, it is unique to that specific game. You need to use a standard FOV Type, the easiest is Vdeg. So select Vdeg for TF2 and copy the "Actual VFOV" value from the Apex calculations. The FOV you need to configure in TF2 will then show up in the "Config FOV" in the output.

Checked it now, and it should be spot on. Can you link your conversion? Stupid question maybe, but you have the game updated to the latest version?

I tried now, and it does go above 1.55. However it maxes out at 1.642857, which might seem like a weird number, but it's equal to exactly 115 hdeg in 4:3. Going above this does not increase the FOV, unless I'm doing something wrong I've updated the max FOV for the config file calculations. It used to go down to 0.01, but it does indeed reset to 0.2 now so I've updated the minimum.

Got it, I'll check it out!

First off, cl_fovScale 1.7 does not work unless there's some kind of workaround I'm not aware of. The game maxes out at 1.55 As for the deviation, the hipfire is off by 0.0002% due to rounding, the ADS calculation accounts for this so they are perfectly matched.

Neither of these games can be added as they just have a sensitivity slider without any numbers or notches.

Your conversion setup matches how the game scales sensitivity: So the sensitivity stays the same when you change FOV.

Check if it's possible to set the value and that it stays. If the game doesn't change it in the config file after you start it, it's most likely valid.

It is, but the aesthetics of the game makes it feel quite differently than games with e.g. realistic graphics.

The aiming sensitivity for Payday 2 is only correct for ironsight with FOV Relative Sensitivity on, I have not analyzed the sniper. PS, always check the game notes, these things are usually mentioned there Can I easily get a sniper to analyze by using cheats/mods or something? If so I can add it.

Actually I think I misunderstood, I though you wanted your R6 settings to Valorant since you posted them first, but I see it's the other way. That's a lot easier if you have 0.5 for both hipfire and ADS in Valorant: https://www.mouse-sensitivity.com/?share=3175d45e675c7aec2722431719f8ee9c

Ok, the scaling of your scopes doesn't really match any conversion method, but you can get pretty close by setting it up like this: https://www.mouse-sensitivity.com/?share=482dd7f782a91a78b1e96b79afd3b8f7

The scope sensitivity is a product of all the values, so for e.g. 1x it's all these: MouseYawSensitivity ADSMouseMultiplierUnit MouseSensitivityMultiplierUnit ADSMouseSensitivity1x So to help you we need to know all the values from R6.

It's currently only ironsight. Can I pick up scope easily?

Same issue still unfortunately.