DPI Wizard

In the simple version have a lot of options removed. This includes conversion methods, FOV Type and special options that are locked to pre-selected values, and some conversions do not work because it is limited to one sensitivity input. It also defaults to in-game sensitivity rather than config file sensitivity where it is available. The only downside is the obvious one, you have less options to play around with. It should however work fine in most cases.

The FOV Type is dependent on the game, the calculator will automatically switch to the correct type for the game you select. The calculation you posted has the wrong FOV Type hence the wrong FOV. Switch it either to Hdeg 4:3 and enter 104 (if this is what you have in-game), or check the config file for the correct multiplier. It's in a separate config file listet in the game notes.

The config file calculations primarily use the FOV multiplier in the config file. If you want to enter the in-game FOV you must change the FOV type to Hdeg 4:3. But using the multiplier from the config file is recommended as it is more accurate.

For those games just do exactly the same, but use the default FOV (it will automatically be loaded when you select the game). If hipfire feels wrong using 360 distance, try another method like MDH 0%.

What is your ADS sensitivity in Apex?

The default conversion setup should work for you, the only part you might want to play around with is the Normal conversion (i.e. hipfire), as some prefer 360 distance and others MDH 0% (or another percentage in some cases). Note that if you can match the FOV between games the conversion method doesn't matter as they will all result in the same sensitivity. And matching the FOV is always recommended whenever possible. So for instance to convert form Apex to PUBG do like this: Note that the FOV Type and FOV value for PUBG is changed to match that of Apex, the output will show you the correct FOV to configure in PUBG to get the same FOV as in Apex (106.26 in this case).

Use the multiplier value from the config file, the in-game menu shows inaccurate values.

That's probably the cause of this. Everything in your conversion is based on the Apex hipfire sensitivity, so when you change the Apex FOV everything else will change too.

Yes that would be better.

Ok, so it seems to be completely unrelated to mouse hardware or drivers then. Annoying bug!

Do any of you use a dedicated Logitech profile for BFV with different DPI settings than you use in Windows? I.e. could the issue be that Logitech sometimes does not switch to the correct profile?

You should try with setting the ADS match to 360 distance. Also set the Apex FOV to Vdeg 83 so it matches R6, and see the output for the config FOV in Apex to get this FOV.

I can see that it is definitely canceled now.

Games use different scaling methods and different FOV's for ADS, in addition to different attributions of the ADS sensitivity (if it's being a multiplier of the hipfire sens, a standalone value or a monitor matching value). So there's no magic way to convert from one game to another other than using the calculator and entering all your values.

Unless promod does something else with the FOV scaling, use 112 and Hdeg 4:3. This is very wide though, you should see pretty quickly if the Apex FOV matches or not.

Yes, but I think it should be 112 with Hdeg 4:3. Is this with promod? I'm not sure, but isn't fovscale locked to either 1 or 1.125? I'm on a bit of thin ice here, haven't looked too much into fovscale in this game.

Actually, what is your configured FOV in CoD 4? According to the screenshot it should be 96.07.

Yes

It's 0%, but it's decoupled from your hipfire sensitivity. So if you set the zoom sens to the same value as hipfire they will be matched MDH 0%.

Is it possible to get a hold of 1.0.6 again? It seems like this happened when going from UE 4.19 to 4.21. Would be interesting to test if it's that or something I have installed/done between 1.0.6 and 1.0.7.

FYI, just tried creating a new Windows user profile on my main computer. And there FOV does not affect sensitivity using the same game installation. So hardware, drivers and game installation is not issue, there's something on my user account / local settings that must be causing this.

I will! I have almost 400 games installed, do you think there's any chance UE4 for some reason might be affected by this? Like reading settings from some generic UE4 registry location or path? That's a can of worms, I know all about it!

It matches the tracking speed of your crosshair so it is consistent between aims:

Tried on another computer now, and on that one the sensitivity is unaffected by FOV. So something on my main computer is causing this. I've updated the calculations in the calculator to not be affected by FOV again, as the results I'm getting seem to be invalid. Now to try and figure out the reason for this happening...

I just uninstalled the game, deleted the folder under %LOCALAPPDATA% and re-installed. And it still acts the same way