DPI Wizard

No, you're using a different conversion (360 distance vs MDH 0%). They will result in a different sensitivity unless the FOV is the same.

Doesn't seem like the scalars do anything unfortunately, so it's all tied to the same sensitivity at the moment.

It's the same according to your settings. If the FOV is different there is no real same sens, but methods to convert between them. What you prefer is up to you actually, there's no right answer.

That's expected when you don't use 360 distance and the FOV is different. Some like it, others don't.

This is correct!

Yes.

It affects all scopes, but you can only use one of scopes for your calculation. 0% is generally considered better than 100%.

If you're comparing the "All" calculation (which does hipfire and a scope at the same time), you need to compare it to the Assault Rifle, as this is the scope used with the "All" option. Also you are using MDH 100% for the scopes, and 0% for the rest, so you will not be able to convert back and forth without using the methods.

The "All" calculation use the Assault Rifle, not the sniper

Config file is added, which supports at least 6 decimals. Also updated with holo, 6x and 10x. It is a bit inaccurate, which is why scope calculations will be off by a few counts.

Working on this right now, will update when done!

Config file sensitivity is added.

It depends on what you want. In the first one SWBF2 hipfire is matched to OW hipfire using 360 distance, and ADS and scopes for both games are matched to OW hipfire using MDH 0% In the seconds one SWBF2 sniper is matched to SWBF2 hipfire using MDH0%. The All conversion actually uses the sniper, but that's not the main issue. OW hipfire and SWBF2 hipfire have different FOV's and you used 360 distance in the first conversion, that's why you get a different result here. For the last one you are using MDV 0% for hipfire instead of 360 distance, so converting just scopes like you did in the second one does work with this setup:

MDV 0% most likely, only tested ADS so far though.

Updated!

Apex Legends is in! I put everything on hold to add this game quickly, enjoy

Apex Legends

#APEXLEGENDS coming very soon!

While there might be bugs in the calculator, none of the examples you give are bugs. Everything is working exactly as intended, the calculator is giving you the correct sensitivity based on you setting. Nothing here is broken. If you doubt the validity of any conversion, just try converting to and from a game that use any of the methods, and you'll see that it is 100% correct, bar rounding limitations. CSGO for instance use MDV 133.3333% as default, as you can see it's perfectly calculated: In BFV you can set the same USA value as MDV, and you'll get a perfect result: The same goes for BO4: PUBG use MDH 100%, again spot on: If the conversion in your example makes CSGO feel too fast, well then you need to use another method. MDH 100% will be quite a lot slower.

First of all, why are you converting zoom sensitivity to hipfire? Other than that, the calculator is doing exactly what you tell it to. It's a mathematical tool, not magic. The sensitivity you are getting is equal to MDH 0%, it will be faster for higher FOV's, just like scopes etc are slower than hipfire. If MDH 0% doesn't feel right to you, you should using something else, like MDV or MDH 100% for instance.

I see, can you show a screenshot of your calculation, and I'll check the game.

Might this be due to the gear you are wearing slowing your turning speed?

Does you mouse support DPI change? If so you need to use a higher DPI for Creative Destruction for the sensitivity to be within range.