Multi-calculations are here!

[DPI Wizard 822]

This will make the calculator a lot easier to use!

All games that have support for aim sensitivity now have an "All" option under aim, and this option will calculate all aims automatically.

For this to work there's been a re-design of the conversion method input, as you need to specify how you want each aim calculated. All the aim selections are put into one of these four categories:

• Normal - Hipfire or default view
• ADS - Targeting, ironsight, holo, red dot and scopes up to 1.5x
• Scopes - All scopes more powerful than 1.5x
• Win/2D - Windows and 2D games like osu and LoL

The active conversion method(s) for your selection will be highlighted in blue.

Note that if you load an old saved entry, all conversion will be set to the same value.

There are likely a few quirks to this new function, please report them here if you find anything weird.

[RexVoluntas 7]

For games that only allow you to set one aim sensitivity such as Battalion, how does it work out the result? Is it just an average of all of them?

[DPI Wizard 822]

1 minute ago, RexVoluntas said:

For games that only allow you to set one aim sensitivity such as Battalion, how does it work out the result? Is it just an average of all of them?

It uses a scope with an FOV in the mid-range. For games that have different scaling for scopes such as Rainbow Six I've added two "All" options.

[Skidushe 28]

9 minutes ago, DPI Wizard said:

It uses a scope with an FOV in the mid-range. For games that have different scaling for scopes such as Rainbow Six I've added two "All" options.

Would it be possible to add an option like this? https://www.mouse-sensitivity.com/forum/topic/4398-averaged-aim-fovs/

[DPI Wizard 822]

1 minute ago, Skidushe said:

Would it be possible to add an option like this? https://www.mouse-sensitivity.com/forum/topic/4398-averaged-aim-fovs/

Yes, will see about this in the next update.

[mateofeo11 0]

Good job with this new addition of settings.  I'm loving it.

[Snook_ 0]

11 hours ago, DPI Wizard said:

This will make the calculator a lot easier to use!

All games that have support for aim sensitivity now have an "All" option under aim, and this option will calculate all aims automatically.

For this to work there's been a re-design of the conversion method input, as you need to specify how you want each aim calculated. All the aim selections are put into one of these four categories:

• Normal - Hipfire or default view
• ADS - Targeting, ironsight, holo, red dot and scopes up to 1.5x
• Scopes - All scopes more powerful than 1.5x
• Win/2D - Windows and 2D games like osu and LoL

The active conversion method(s) for your selection will be highlighted in blue.

Note that if you load an old saved entry, all conversion will be set to the same value.

There are likely a few quirks to this new function, please report them here if you find anything weird.

You are missing 'VehicleDriver' Sensitivity in PUBG conversions at the moment 

[MuntyYy 12]

He is not "missing" any conversion, he just didn't include it at All sensitivity rubric.

[Snook_ 0]

So, what your saying is 'VehicleSensitivity' is missing? rofl

Brought it up because unaware people will copy and paste the config method straight in and stuff it up.

[MuntyYy 12]

You said that its missing. Vehicle sensitivity in PUBG is the same as the general one.

On 6/28/2018 at 11:09 PM, DPI Wizard said:

Do you mean for vehicle? If so it uses General Sensitivity.

 

[MuntyYy 12]

People should read first the important topics that they have questions on, that way there won't be 20 threads asking the same thing. Also a simple keyword specific search will, most of the time provide you the adequate answer.

 

Edited September 17 by MuntyYy

[DPI Wizard 822]

3 hours ago, Snook_ said:

You are missing 'VehicleDriver' Sensitivity in PUBG conversions at the moment 

Vehicle sensitivity was removed from the game about three months ago  

[Snook_ 0]

Interesting, mines still there but I havn't deleted my config at all since Beta.

 

(SensitiveName="Normal",Sensitivity=34.948502,LastConvertedSensitivity=0.010000),(SensitiveName="VehicleDriver",Sensitivity=34.948502,LastConvertedSensitivity=0.010000),(SensitiveName="Targeting",Sensitivity=34.948502,LastConvertedSensitivity=0.010000),(SensitiveName="Scoping",Sensitivity=33.632103,LastConvertedSensitivity=0.008232),(SensitiveName="Scope4X",Sensitivity=32.555946,LastConvertedSensitivity=0.008957),(SensitiveName="Scope8X",Sensitivity=32.488876,LastConvertedSensitivity=0.008929),(SensitiveName="Scope15X",Sensitivity=32.470234,LastConvertedSensitivity=0.008921),(SensitiveName="Scope2X",Sensitivity=32.934849,LastConvertedSensitivity=0.009114),(SensitiveName="Scope3X",Sensitivity=32.630898,LastConvertedSensitivity=0.008988),(SensitiveName="Scope6X",Sensitivity=32.502380,LastConvertedSensitivity=0.008935)

[Snook_ 0]

 

Can I ask why Targeting comes out different now? I didn't think the FOV changed at all from General?

[DPI Wizard 822]

Just now, Snook_ said:

Interesting, mines still there but I havn't deleted my config at all since Beta.

 

(SensitiveName="Normal",Sensitivity=34.948502,LastConvertedSensitivity=0.010000),(SensitiveName="VehicleDriver",Sensitivity=34.948502,LastConvertedSensitivity=0.010000),(SensitiveName="Targeting",Sensitivity=34.948502,LastConvertedSensitivity=0.010000),(SensitiveName="Scoping",Sensitivity=33.632103,LastConvertedSensitivity=0.008232),(SensitiveName="Scope4X",Sensitivity=32.555946,LastConvertedSensitivity=0.008957),(SensitiveName="Scope8X",Sensitivity=32.488876,LastConvertedSensitivity=0.008929),(SensitiveName="Scope15X",Sensitivity=32.470234,LastConvertedSensitivity=0.008921),(SensitiveName="Scope2X",Sensitivity=32.934849,LastConvertedSensitivity=0.009114),(SensitiveName="Scope3X",Sensitivity=32.630898,LastConvertedSensitivity=0.008988),(SensitiveName="Scope6X",Sensitivity=32.502380,LastConvertedSensitivity=0.008935)

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

[DPI Wizard 822]

Just now, Snook_ said:

 

Can I ask why Targeting comes out different now? I didn't think the FOV changed at all from General?

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.

[a634754420 0]

The new version without the Base length and Discrepancy
@DPI WizardThis is old version and new version ,0% Monitor distance

 

Edited September 21 by a634754420

[Pyroxia 0]

 

 

 

I'm using USA in bf4 and all sliders %100 but all option give me this calculations.

[DPI Wizard 822]

7 minutes ago, Pyroxia said:

I'm using USA in bf4 and all sliders %100 but all option give me this calculations.

You have to make sure the conversion setup matches your settings. For BF4 this means setting ADS and Scope to the same Vertical Monitor Distance as your USA setting:

[Pyroxia 0]

thank you bro 

[a12014712 0]

Multiplier 1 should be calculated by OW FOV, so it should be calculated by FOV of second games.

[DPI Wizard 822]

5 minutes ago, a12014712 said:

Multiplier 1 should be calculated by OW FOV, so it should be calculated by FOV of second games.

It is calculated using OW FOV, but it is matched to the first game. It wouldn't make sense to match it to OW hipfire, as that would make all calculations different.

[a12014712 0]

1 hour ago, DPI Wizard said:

It is calculated using OW FOV, but it is matched to the first game. It wouldn't make sense to match it to OW hipfire, as that would make all calculations different.

Thanks,i understand roughly.It is based on the first game， which make computing unified and not chaotic.But i still think  it's more accurate to base on the second game, because the FOV settings for the two games may not be the same.

[DPI Wizard 822]

On 10/16/2018 at 2:57 PM, a12014712 said:

But i still think  it's more accurate to base on the second game, because the FOV settings for the two games may not be the same.

That kinda defeats the purpose of the calculator though, as it is converting from the first game to the second.

Doing the aim match based on different FOV's means that your aims will be different too, so you won't get any consistency. 

[a12014712 0]

15 hours ago, DPI Wizard said:

That kinda defeats the purpose of the calculator though, as it is converting from the first game to the second.

Doing the aim match based on different FOV's means that your aims will be different too, so you won't get any consistency. 

Thanks for your reply.I can understand it. because it is converting from the first game to the second game.So the calculation to base on the first game, after all, to make the second game after the conversion and the first game all aspects of the data consistent,So computing with the first game data is more consistent with the user's original idea.