Pubg has new sensitivity settings

[ayefinzherb]

Hi

The last PUBG update was released today

They added new features about sensitivity and deleted the vehicle driver one

Link of the patch note: https://steamcommunity.com/games/578080/announcements/detail/3077529898696206477

Your website needs a little update too ^^

Thanks for your support

[DPI Wizard]

The "new" sensitivity setting is basically setting all the scopes to the same value so it doesn't need an update.

Vehicle sensitivity is removed.

[Tobias Bieri]

16 hours ago, DPI Wizard said:

The "new" sensitivity setting is basically setting all the scopes to the same value so it doesn't need an update.

Vehicle sensitivity is removed.

They changed the name from "MouseSensitiveName" to "SensitiveName", maybe update that in the calculator. 

I don´t know if you´ve seen my other post, but i think this might be also important:
 

"I was sure it (3x and 4x) was faster than before, and I figured out why. Usually I just adjusted the LastConverted Value and it worked fine. Like this: SensitiveName="Scope4X",Sensitivity=50.000000,LastConvertedSensitivity=0.010424

But I had the impression it was way too fast. I adjusted now the "Sensitivity" value also and it is back to normal:
SensitiveName="Scope4X",Sensitivity=35.849648,LastConvertedSensitivity=0.010424

So it seems the game doesn´t just look at the LastConverted value anymore. 
Could it be possible to combine config file setting 1 and 2 in the calculator, so it just gives out the whole line, with both values included?
"
But amazing work with the calculator. I realized how much better I got since matching all my sensitivities when they suddenly were wrong again and I could't hit absolutely nothing

[DPI Wizard]

I've updated the variable names now 

[poppe]

Anyone else's 3X sensitivity really really slow while only using the config file 1 method?

[Tobias Bieri]

For me config 1 method doesnt work anymore. Do both, config 1 and 2, that fixed it for me

[ayefinzherb]

I had problems too using cfg file 1. I just use both now.

I noticed that the game just rounds the "config file 1" value if you click apply in-game when "gameusersettings.ini" is not "read only".
But if you let "gameusersettings.ini" not "read only" and never click "apply" in-game, it will still change the "config file 1" value of a few decimals.
Why ?

[Skidushe]

On 6/22/2018 at 9:37 PM, DPI Wizard said:

The "new" sensitivity setting is basically setting all the scopes to the same value so it doesn't need an update.

Vehicle sensitivity is removed.

Do you know what conversion they use?

[DPI Wizard]

On 26/06/2018 at 02:03, ayefinzherb said:

I had problems too using cfg file 1. I just use both now.

I noticed that the game just rounds the "config file 1" value if you click apply in-game when "gameusersettings.ini" is not "read only".
But if you let "gameusersettings.ini" not "read only" and never click "apply" in-game, it will still change the "config file 1" value of a few decimals.
Why ?

Bug in the game, but the few decimals changed are negligible.

30 minutes ago, Skidushe said:

Do you know what conversion they use?

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

[Skidushe]

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

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

I mean for scope sensitivities. is there an mm match or formula that fits their variation in scope sensitivites

[MuntyYy]

3 minutes ago, Skidushe said:

I mean for scope sensitivities. is there an mm match or formula that fits their variation in scope sensitivites

Its entirely up to you. Try mm 00%, if it's too slow go for viewspeed v2. I personally use 100%.

Edited June 30, 2018 by MuntyYy

[DPI Wizard]

4 minutes ago, Skidushe said:

I mean for scope sensitivities. is there an mm match or formula that fits their variation in scope sensitivites

Yes they scale directly with the horizontal FOV, i.e. half the FOV = double the 360 distance. This is the same as 100% monitor match.