DPI Wizard

This seems like a bug, I'll look into it right away!

Simple mode converts hipfire to hipfire using 360 distance, and since neither of those games have sensitivity affected by FOV changing the FOV doesn't change the calculation. If you try to convert from a game like CSGO to Overwatch and change the CSGO FOV you will see that the calculation changes

With what game are you seeing this behavior?

If they scale directly to FOV, (meaning a scope with 45 FOV has twice the 360 distance of 90 FOV) I only need the FOV, how the FOV scales to configured FOV and if the scope sensitivity is independent or affected by hipfire sensitivity. If it's something more complex than this it's a lot harder to just ask for the info without being able to test it myself.

I see now that your FOV is probably wrong. Check the FpsCameraFov value in the config file, and make sure the FOV Type is Hdeg Res.

It's not uncommon that sensors are off by as much as 10%, so your true DPI is probably higher than 400. You can test your DPI here.

It can be done, will put it on the todo list

Just updated the calculator to support this, so the in-game FOV Type for BFV will now automatically switch to 4:3 Hdeg.

You must select the correct location, as in-game and config file uses different sensitivity. Also be sure to use the FOV from the config file, or switch FOV Type to Hdeg 4:3 if using the FOV from in-game as they are different as well. Lastly you must first convert your hipfire, and use the hipfire sensitivity as Sensitivity 1 for the scopes.

This, do not change the CSGO FOV unless you are playing solo or on a server with cheats that allow FOV changes. Also, the viewmodel FOV is NOT your FOV as a lot of people seem to confuse it with, it's just the rendering FOV of your weapon. As for the matching method, priority one is to match the FOV. If the FOV is close (as on a 16:9 monitor with CSGO at 106.26 and OW at 103), the match method has very little impact. Other than that the big difference is that 360 distance always keep a constant 360 distance... so you can accurately turn 90 or 180 degrees regardless of FOV. The other methods (monitor distance and viewspeed) are matching sensitivity to what you see on your monitor, so they are more suited to aiming at what you actually see. There is no best method however, it both depends on the game and your preference.

Each scope setting in PUBG use the scope's FOV to calculate the sensitivity, so when they are all set to the same value it's the same as USA 1.777778, or 100% monitor distance (for 16:9 resolutions). This is common for a lot of games. It's not adjustable though, so it's not the same as USA.

Looked into the FOV issue now, and as of now you have to use the FOV from the config file. Changing the game to use 4:3 hdeg FOV messes up all the formulas for the scopes as they use the vertical FOV. If this stays until the release I will fix it.

This is correct, the FOV type for ingame sensitivity was updated earlier to 4:3 hdeg FOV, but the formula for aim FOV still assume vertical degrees. Updating it now!

The confusing naming of the scopes in PUBG is because they have different names in-game and in the config file. I'm almost done with a new version that converts all scopes at once, which makes life a lot easier for you. Here's your conversion using the new function (there's a small bug in the aspect ratio scaling for scopes, all values should be the same as General Sensitivity): Since PUBG and Squad have the same scaling for scopes, you basically set all scopes in PUBG to the same value.

Off the top of my head: Logitech G903 Logitech G900 Logitech G PRO Wireless Logitech G203 Logitech G PRO Plugable PM-3360 Razer Mamba BENQ EC2-A Plus a bunch of older ones.

The config file uses vertical, as stated in the FOV notes in the calculator: Set the FOV in the PROFSAVE_profile config file, as the FOV in-game is a rounded value to the nearest 4:3 HFOV. The default USA is 100 in BFV, it's just not updated in the calculator yet. Always set the value to the same as you have in-game. Was going to wait for release to update them as they might change again, but think I'll do it tomorrow instead

The new one with the Hero sensor? If so I just got that one myself and will run some tests on it soon.

Not possible unfortunately, tested when it was released and it has tons of issues with the sensitivity so it's impossible to get a consistent result.

No, 100% (I assume you mean 56.25%)

360 distance is only suitable for hipfire or aims that have about the same FOV. Since it keeps a constant 360 distance it's not suitable for scopes since it would make them way too sensitive. Viewspeed 1 and 2 (now renamed Viewspeed Horizontal and Viewspeed Vertical) calculate the sensitivity based on FOV, one for horizontal and one for vertical. The big difference is that the vertical match do typically not change when you change aspect ratio. If you convert between the same aspect ratio they are about the same.

If you turn it on the ADS will change FOV when you change the FOV setting. If you have it off the ADS has a fixed FOV.

Added with hipfire sensitivity, aims coming soon.

Fixed

Thank you, fixed!