DPI Wizard

Indeed, it should be opposite for the coefficient, enter the configured FOV regardless of the setting. Some numbers will be off though, but the important output is the coefficient value.

Done!

That formula was wrong, as Skwuruhl wrote BF1 uses trig to calculate the FOV, so the correct formula is: [Link] Where: x = The configured vertical FOV in radians y = The default scope FOV in radians z = The default FOV in radians So for a 2x aim with FOV 74 configured the values would be: x = 74 degrees in radians = 1.291543646 y = 29.2 degrees in radians = 0.509636142 z = 55 degrees in radians = 0.959931089 [Link]

Unfortunately it's not that simple, but if you tell me the scopes and preferably the fastest way to acquire them, I can add them. Sadly I don't have much time to actually play the games, I just analyze them

Sorted out the gremlins, the new version should work fine now

Are you using Monitor Distance for the aims? 360 distance will not work, and will make the scopes too sensitive. What you should do is first match Depth to BF1 like you did. Since the FOV is the same, it doesn't matter if you chose 360 Distance or Monitor Distance. Then when you select coefficient, switch to Monitor Distance, and select a desired Match At percentage. When you do this, the input field changes, and the second one is no longer the coefficient, so be sure to check the values in the output. But note that the coefficient has a very narrow range, and you might as well use the Soldier Zoom Sensitivity as it has a much wider range

Had to move the new version to a new selection in the navigation menu for now, as it only works for subscribers.

The new version is currently bugged for non members, working to fix it.

And it's up! All possible BF1 weapon aim calculations are now supported, both for in-game and config file sensitivities. Thanks for all the input, there was a lot of pieces needed for everything to work perfectly Hopefully any questions asked can be answered by playing around a bit with the calculator! Please report if you find anything strange.

In an hour or so!

Sorry about that, my bad! Fixed now

Could you post a screenshot of the calculator so I see everything you put in?

Yes, they're coming in a day or two I hope.

I've gotten a possible solution to this in a PM btw, will test it later today!

If you select Horizontal Deg | Res. Base in the FOV Type for both games and enter your desired actual HFOV, and the calculator will calculate the needed config FOV for the game So if you e.g. want 110 hfov for BF1, the config FOV is 77.55

I initially though so as well, but Wolfram solves the two examples somehow. It might require some serious code though... The rounding of the results are because the input is rounded. I might look into the Wolfram API

Not in use if USA is off. The coefficient tells you where on the monitor you will match the sensitivity. 1 is from the crosshair to the top of the screen, hence is 1.33 75% of the distance from the crosshair to the edge on the side, and 1.77778 is 100%.

Correct! Added now

I just have one piece of the BF1 puzzle left, if anyone can assist me there's a prize in it for you Solve this problem!

I know there's quite a few very skilled people here, so if anyone can solve this problem, there's a €20 Steam Gift Card in it for you Solve this equation for x: [Link] In other words; a, b and y are known, and the equation to calculate x is needed. If you think you got it, you can verify it with these two examples, which Wolfram|Alpha manages to solve but doesn't show how (ignore rounding of x): | x = 1.33 [Link] | x = 0.5 [Link] This is a simplification of the equation used to calculate the zoom sensitivity coefficient for BF1/BF4. Rules: The first person to post a working solution wins. Any takers?

That was a bug, it was intended to be 50. Fixed

Yes, I will add this. The sensitivity in BF4 works like in BF1, so I will update BF4 to support this and all other variables soon

2x in BF1 is 29.2 (or FOV*(29.2/55) if scaling is on) vertical degrees FOV, that's the one I've been testing with so far.