DPI Wizard

Use the config file calculations for best range and accuracy.

Added this now.

That's the same as doing this in the new version:

It means that you must set these values in the config file for the calculated sensitivity to be correct. Also make sure you enter the correct FOV for R6.

The conversion needs to know some of your existing values, but if you select "All w/ ADS" or "All w/ ACOG" instead the default value will be automatically used.

Very limited sensitivity range in this game!

Done

The original game, or else you will get different scope sensitivity in games that have different FOV from the original.

In this case it's how far you have to move the mouse to aim at something at the very edge of your monitor.

Calculate everything automatically so you don't have to first calculate hipfire, then scopes using the results from hipfire https://www.mouse-sensitivity.com/forum/topic/4706-multi-calculations-are-here/

Adjusted FOV slightly and added Y axis calculations as it is a little bit slower.

Configure Aim Hero like this using the Fortnite sensitivity: Mouse Sensitivity 0.069993 Zoom Scale 1 2.1 Zoom Sensitivity Ratio 1 0.655865 Field of View 50.53

Yes, and that's why it's important to always use the same source for your conversion.

The first one is using TPP, the second one is using FPP. These are different for General sensitivity since TPP is locked to a specific FOV, while FPP has a variable FOV. For the first one your actual FOV is 92, while Squad is 90. That's why you get a slightly different result for General (which is matched to 360 distance) and the scopes which are matched to 100% of the 90 FOV. For the second one the actual FOV is 103.5 which is why the General sensitivity is so much lower. The scopes are still matched to Squad with 90 FOV however. In the last one everything is matched to the FOV of FPP, so they are all the same. The important thing to note is that all the sensitivities will be calculated based on the hipfire sensitivity of the input game. So when you do like the first and second one the scopes are not matched to General sensitivity in PUBG, but Squad hipfire.

Yeah.

The ones generated by the game are actually slightly off, the calculator is accurate. But the difference is barely even measurable.

True, but they all achieve the same goal unless you are converting between different aspect ratios. Also note that Monitor Distance Vertical 100% will in most cases be the same regardless of the monitor AR (some games do change vertical FOV depending on AR though).

It depends on you conversion setup. Since Targeting is classified as ADS, it will use the ADS setting from your setup. So if you i.e. match Normal to 360 distance and ADS to Monitor Distance 0%, General and Targeting will be different if the FOV is different between the input and output game. If you use the same method for Normal and ADS they will be the same regardless of FOV.

Yeah, the games doesn't clean up the config file unless you delete it so you will have lots of deprecated entries there.

Let's see what your preferred conversion method is for the different aims. If your answer is another percentage than one listed, please specify. I joined ADS and scope into one poll as most people probably prefer these to be the same, but do tell if you want them different.

You are converting 75% Monitor Distance from Squad to PUBG, change the Normal conversion mode to 360 Distance if you want that to be 35cm for all games This is also why you get different results when you plug in 35 cm directly for PUBG.

Fixed now

Vehicle sensitivity was removed from the game about three months ago