DPI Wizard

It's unlikely to change considering the current scaling are consistent with MDH 0% and the scope's FOV scaling makes mathematical sense.

The fact that the game reads this file is a bug, so it might be solved in a patch. If you prefer to have it on for now you can get the correct sensitivity by multiply your calculated sensitivity by FOV/90, so in your case 0.019907*119/90

Looked into this now, and it's actually the exact same bug as with KovaaK's FPS Aim Trainer! You probably have this file on your system: %LOCALAPPDATA%\Unreal Engine\Engine\Config\UserInput.ini With this line: bEnableFOVScaling=False This overrides the games default value which is "True". Delete or edit this line to say True and the calculations will be correct

Sounds like your FOV is still 90, make sure it is applied correctly (if you set it in-game I've noticed that the change is not always applied). Note that the config file FOV is in a different file mentioned in the FOV notes.

Still got .20 in my Epic launcher, will check when I get the update.

Yes, they are different because Y is 70% of X

Find a short-term solution for your long-term problems!

Satisfactory is in!

Coming up next!

Both have acceleration/smoothing/joystick simulation issues unfortunately.

It depends on you conversion setup, set ADS to 360 distance if you prefer this.

It's just your brain The graphic style and gameplay of different games can greatly impact how the FOV is perceived, so while it is the same as CSGO at 90 you might prefer a wider FOV for Apex.

Aim sens use the same scaling as the first game, but I'm playing this now to get some aims to analyze!

I think you are using MDH 0% on the new one and MDH 75% on the old one. With the same percentage they should be the same.

You can already do that, just select Distance instead of Sensitivity in the Convert from selection (Unless you mean something else?)

When you select an "All" option, everything will be matched to the hipfire sensitivity of the game you convert from. The only reason not to use this is if your aim preference is not achievable with the conversion methods available. It's highly recommended to use the "All" option however, as it makes conversion mathematically sane and consistent. People are different though, so some prefer other matches. If you can't match your preference with the conversion methods, you need to do the calculations in (at least) two steps. First convert hipfire to hipfire, then convert ADS to ADS (or Scope to Scope) using the previously calculated hipfire sensitivity if the game uses that for ADS/Scope. The separate aim selections are also useful for finding out the FOV of a specific aim, as this will be shown in the "Actual HFOV" and VFOV in the output. No games other than some aim trainers give you the option to change FOV Type in the game. The reason for the option to change is that it also works as a converter. If you want the same FOV in Apex as in BFV, you simply change the FOV Type for Apex to Vdeg (because that's what BFV uses) and enter the exact same value as you have in BFV. The output will show you the Config FOV for Apex that you need to configure to match the FOV.

No, the in-game value is off by up to 2 degrees +/- (at least). If it's vastly off somethings probably wrong somewhere, but the cl_fovscale value is the FOV that is actually applied to the game.

Are you sure your Fortnite sensitivity is 0.7 and not 0.07?

Aye, it's in!

Golf with accuracy!

If you're testing that way, MDH 100% is the correct conversion for you. This means that your test will be the same distance as moving the cursor from the center of the monitor to the edge in Windows. Regarding DPI, as long as you have the same DPI in both the game and Windows the calculation will not change

Because you are converting 360 distance for hipfire, and Aimtastic sensitivity is not affected by 360 distance as stated in the notes. This means the 360 distance will be the same regardless of FOV, so as long as you match the sensitivity with 360 distance it will be unchanged. If you choose any other method (monitor distance or viewspeed) the sensitivity will change.