DPI Wizard

The sensitivity is still correct, but it's important that you select Aim Lab as "Use Setting From". Others will be added soon for clarity! If you're still finding the conversions to be wrong, please provide your settings and I will test them.

You have the wrong FOV for CSGO, it should be 90

Unreal Gold has a lot of acceleration, so it's not added. I think the base sensitivity is the same though, but haven't confirmed it.

Like this:

With TPP you are stuck with the locked FOV. So you can't convert back and forth and get the same result with three games, this is why it's important to use one specific game as the source for all conversions so you don't get wrong calculations because of the FOV. I changed the FOV to 88.66 so FPP matches the Actual FOV of BFV as you can see in the output. PUBG has a bug/quirk in how it scales FOV with different aspect ratios, that's why you get the weird value with 21:9.

Actually you should do the FOV like this: To make sure the FOV is the same. Note that TPP in PUBG has a locked FOV, but you can change it for FPP to match BFV.

Nothing's wrong in the calculator, you have different FOV in Aimtastic (70.53 Vdeg) and BFV (55 Vdeg) which makes the calculations different

Yes, you have the wrong FOV type It should be Vdeg for Warframe, this has a huge impact on the sensitivity.

Seems to be the same here, how and where exactly are you testing? I think certain buffs etc that changes your FOV also change your sensitivity. Also, what are your settings?

Can you post a screenshot of the two conversions?

You shouldn't set them to the same value as your hipfire sensitivity, but the same value as you had them to before you changed sensitivity.

The ADS and scope sensitivity in Fortnite are based on your hipfire sensitivity, so you shouldn't have to change them at all.

It seems like it's looking for every imaginable UE4 file both in localappdata and the documents path:

I found the cause! bEnableFOVScaling in %LOCALAPPDATA%\Unreal Engine\Engine\Config\UserInput.ini affects how the game behaves. As I had bEnableFOVScaling set to True in this file it affected everything in the aim trainer. Deleting the file or setting it to False solves the issue.

MDH 0% is the lowest matching method, and you are a fraction below it. So the calculator compensates your 0.999965 by adding 0.000035 to the scopes. In reality this difference is hardly even measurable.

I see, they enabled raw input so WPS doesn't affect the game any more. Updated it now

The sens is in %USERPROFILE%\Saved Games\Respawn\Apex\local\settings.cfg

I see now The in-game FOV in Apex is very inaccurate so don't pay too much attention to it. The correct FOV is the multiplier in the file, that's what's actually applied to the game. The FOV is in the config file %USERPROFILE%\Saved Games\Respawn\Apex\profile\profile.cfg

What conversion method you want to use depends on what you prefer, but MDH 0% is the most popular one.

Yes, the correct FOV for all scopes are calculated based on the FOV configured for the game.

If you have the same FOV for hipfire in both games it doesn't matter as they will all produce the same result. 0% is a valid percentage btw, it will match the tracking speed of your crosshair between aims.

It shouldn't do this, what exactly are doing that's causing this? Any steps I can try to replicate would be great! The correct way of finding the FOV is to set Apex to FOV Type Hdeg Res and value 103, and see the output for the correct Config FOV.

The difference in ADS sensitivity is because it is matched to the hipfire sensitivity of the game you are converting from. And since you have slightly different FOV's in your examples (103 in Overwatch vs 105.25 in Apex) you get a slightly different ADS sensitivity.

Actually everything seems like before, what settings are you trying with?

Checking this game now, they probably changed something.