DPI Wizard

FOV is not accurate in this game, it varies slightly based on your aspect ratio. View full update

Correct, since BF3 does not have any scope specific sensitivities. If the game would have had it though, your goal would be to adjust the conversion setup to match your settings in the game, then convert from that.

Well, it's a mixed bag. MDV 0% is actually the same as MDH 0% as long as the aspect ratio is the same. But generally speaking, games that use vertical FOV tend to be either MDV 0% or MDV 100%, while games that use horizontal FOV tend to be MDH 100% based on a specific aspect ratio (like 4:3 or 16:9) or based on actual resolution. A lot of if's and but's here though. And quite a lot of games use no logical scaling at all (which is where this calculator comes in really handy!).

Because you are converting sensitivity within a single game, the scopes FOV/sensitivity is based on the hipfire FOV/sensitivity, so it will always be the same. If you convert from another game with a different hipfire FOV, the result will be different because the scopes will match the other games hipfire and not R6's. As for the scopes, 0.02 and 50 is the perfect match, you might get some decimals different simply because of lack of decimals.

You can choose all, it just happens to be that MDV 0% is 50 for all. If you instead set the conversion for ADS and scope to MDV 100% you will get different values for all scopes. As for what Monitor Distance to use, the default that R6 now uses (which is also the default a lot of games now) is generally considered the best method. Not saying it's for everyone, but it's the one that makes most sense mathematically.

The picture shows a quite different story than what you are describing (ADSMouseSens is different for all aims). XFactor is no longer in use. In the new R6 sensitivity 50 in-game and 0.02 in the config file (i.e. 0.2*50=1) is MDV 0%, that's why you get 50 for all aims with the default calculator setup witch is also MDV 0%.

The overlay is done in post, not live when capturing the video.

Also note that if you compare the same FOV in first person and third person, first person might appear more zoomed in.

You can only match one aspect of the sensitivity. For flicks it's monitor distance and a percentage that represents the distance between the crosshair and the edge of the monitor.

That depends on what you mean by same. As you touch on, with different FOV it's impossible to get the same sensitivity, only one aspect can be the same. The default (all to 50) is the same tracking speed, but flicking is different. If you match flicks, they will only be flicks to one specific point on your monitor and tracking will be different. If you match 360 distance high power scopes will be insanely sensitive. So you basically have to choose your poison

Nice, updated!

With smoothing enabled you will get negative acceleration and inaccurate sensitivity.

Too much smoothing in the demo, I'll check if it's fixes in the release when it's out.

Added, but you need to use the Arx Libertatis port

You have to use the Arx Libertatis port for the sensitivity to work correctly. View full update

Not possible I'm afraid, too much negative acceleration.

Too much negative acceleration to be added.

Tried it now, unfortunately no effect on the current release. If you have a mouse driver that supports different X and Y DPI you can multiply your X DPI by 4.44 and set this for Y. For instance if your DPI is 400, set Y to 1800 (400*4.44=1776, round up to 1800).

I noticed the same happen here where it rounded the value slightly and added a bunch of decimals. Tried a lot of different values now, but they have seemingly no effect. A shame it doesn't actually use this value, 5 sensitivity steps is way to little!

Strange, nothing happens here when I change it, tried 0.0001 and it's exactly the same as 10.

I tried changing mouseSensitivity here, but it didn't have any effect. MouseSenseIndex is the in-game sensitivity.

There is no best method, but what you have done is generally liked by most. Everything in the calculator looks correct