PUBG: BATTLEGROUNDS (PlayerUnknown's Battlegrounds)

[Vaccaria]

3 hours ago, DPI Wizard said:

You have to select "In-game" for individual calculation of the "Sensitivity" value for the config file. The game only uses the "Sensitivity" value now I think, but you should add both to avoid any overwriting of the values. Setting the sensitivity in the config file for each scope should work fine.

That depends on your conversion setup.

i tested all the options that came to mind and not one worked as expected, except to round up and there will be an error

[DPI Wizard]

23 hours ago, Vaccaria said:

i tested all the options that came to mind and not one worked as expected, except to round up and there will be an error

What exactly are you trying to achieve?

BTW, I've updated the game now, LastConvertedSensitivity is no longer read, so I changed the calculations.

[sonorciff]

Heya, I used the calc for PUBG yesterday and it worked fine, but now it seems it doesn't work anymore - the LastConvertedSensitivity is default (0.020000) for every line, and it's missing the ScopingMagnified line. Copy and pasting the results into the ini now resets all in-game sens to default (50).

[Vaccaria]

1 hour ago, DPI Wizard said:

What exactly are you trying to achieve?

BTW, I've updated the game now, LastConvertedSensitivity is no longer read, so I changed the calculations.

I have sensitivity data that I want to test in games. since in pubg, no matter how much I tried, I could not feel the similarities, I left the game for an unknown period. Returning to the game with new knowledge and experience, I started testing. First, I made the lines appear, after I entered "LastConvertedSensitivity", there was no result. I entered data into LastConvertedSensitivity and Sensitivity but it was considered to be rounding to 43 (42.670372).

1) Removed "Sensitivity"(If you put just 0 in the game, then only "LastConvertedSensitivity" is displayed in the file.), "LastConvertedSensitivity" remained.

The game displayed:

At 0, only general, aim sensitivity works.(I wrote earlier that ADS also works, but this is not correct information, I was wrong)

2) Set the universal sensitivity for all zooms, the “ScopingMagnified” line appears, also works only with “Sensitivity”

3) Removed "LastConvertedSensitivity" from ADS, Zoom, leaving only "Sensitivity"

Hipfire turn 360 degrees

1. 
2. 

8x turn 360 degrees

1. 
2. 

I update to 50

As you can see, the values at which a shot from a weapon most often occurs are rounded and there will be an error in sensitivity.  It seems that he did not miss anything and tried to put it into a single whole.

[DPI Wizard]

9 hours ago, sonorciff said:

Heya, I used the calc for PUBG yesterday and it worked fine, but now it seems it doesn't work anymore - the LastConvertedSensitivity is default (0.020000) for every line, and it's missing the ScopingMagnified line. Copy and pasting the results into the ini now resets all in-game sens to default (50).

The LastConvertedSensitivity value is no longer in use, so I removed it to simplify things a bit. I've fixed the copying issue now.

[LimaBravo]

ME, TOO. PLEASE FIX PUBG LASTCONVERTEDSENSITIVITY FIX ISSUE.

[DPI Wizard]

12 hours ago, sonorciff said:

Heya, I used the calc for PUBG yesterday and it worked fine, but now it seems it doesn't work anymore - the LastConvertedSensitivity is default (0.020000) for every line, and it's missing the ScopingMagnified line. Copy and pasting the results into the ini now resets all in-game sens to default (50).

 

1 hour ago, LimaBravo said:

ME, TOO. PLEASE FIX PUBG LASTCONVERTEDSENSITIVITY FIX ISSUE.

I see there's some aims affected by LastConvertedSensitivity and others not, so I brought it back now. The "All" conversion from the Config File 1 location will do everything as before. There's also now a dedicated LastConvertedSensitivity conversion in Config File 2.

[DPI Wizard]

11 hours ago, Vaccaria said:

As you can see, the values at which a shot from a weapon most often occurs are rounded and there will be an error in sensitivity.  It seems that he did not miss anything and tried to put it into a single whole.

Try again now with the "All" conversion from Config File 1.

[Vaccaria]

4 hours ago, DPI Wizard said:

Try again now with the "All" conversion from Config File 1.

All sensitivity:

In game sensitivity:

Hipfire 360:

Targeting 360:

ADS AR:

ADS Pistol:

ADS SMG:

ADS SMG SHIFT(holding breath and decreasing FoV):

2x:

2x; 30value:

2x; 31value:

2x; 32value:

8x:

All screenshots, size limit. https://www.dropbox.com/s/rpt96br4et8545q/New folder.rar?dl=0

So what we have. The sensitivity depends on the FoV, well, this is not a secret, and so it was clear. I remembered that in ADS the sensitivity is not rounded, you can see it in the screenshots, it only works with "Sensitivity". With additional data +- one value makes it clear that the data is rounded to +. This means that the file that takes data from here simply rounds up to certain decimal places. Showed the most curious screenshots.

 

Edited January 5, 2021 by Vaccaria

[DPI Wizard]

Can you link your conversion too? Share it with the purple button.

[Vaccaria]

3 minutes ago, DPI Wizard said:

Can you link your conversion too? Share it with the purple button.

https://www.mouse-sensitivity.com/?share=fa571ff2883e3527278b1400b1b5ead7

This conversion was done for tests, I usually do it for every single FoV

[DPI Wizard]

1 hour ago, Vaccaria said:

With additional data +- one value makes it clear that the data is rounded to +. This means that the file that takes data from here simply rounds up to certain decimal places. Showed the most curious screenshots.

Indeed, tested it now and the data is not converted correctly. There's always been a bug in the game when converting the in-game sensitivity to LastConvertedSensitivity, but previously when the game actually read the LastConvertedSensitivity and applied it you could fix it by changing it in the config file. Now that it doesn't read it anymore this doesn't work obviously.

Maybe if I can reverse engineer the conversion bug I can fix it, I'll have a look.

[DPI Wizard]

31 minutes ago, DPI Wizard said:

Maybe if I can reverse engineer the conversion bug I can fix it, I'll have a look.

Done some testing now, and this can't be done unfortunately. Sometimes the relation between the Sensitivity and LastConvertedSensitivity is 100% correct, other times it's off. So it's kinda random what you'll get.

[sonorciff]

Thanks, actually it worked like you said without lastconverted once you added back in the missing line for copy and pasting.

But am I reading this right, PUBG is rounding up the decimals on some scope sensitivities..? Oof.

[DPI Wizard]

1 minute ago, sonorciff said:

Thanks, actually it worked like you said without lastconverted once you added back in the missing line for copy and pasting.

But am I reading this right, PUBG is rounding up the decimals on some scope sensitivities..? Oof.

Confusingly it still used lastconverted for hipfire and ADS, but not scopes... It rounds randomly (but seemingly always up), sometimes it's spot on though.

[sonorciff]

That's weird, for me I think even hipfire and ADS were correct even without lastconverted. In any case, yikes on the rounding... and knowing PUBG corp, this may take a long time to fix if it ever is.

[DPI Wizard]

1 minute ago, sonorciff said:

In any case, yikes on the rounding... and knowing PUBG corp, this may take a long time to fix if it ever is.

I think what happens is that (as is the case with many games) the slider is not accurate, and both values (sensitivity and lastconverted) are derived from the position of the slider, and they read it slightly differently. I don't think the devs care though, if they did they would just allow you to input 6 decimals in-game. This did work a few years ago, but doesn't anymore.

[Snook_]

2 hours ago, DPI Wizard said:

I think what happens is that (as is the case with many games) the slider is not accurate, and both values (sensitivity and lastconverted) are derived from the position of the slider, and they read it slightly differently. I don't think the devs care though, if they did they would just allow you to input 6 decimals in-game. This did work a few years ago, but doesn't anymore.

So are you saying converting sense is now useless into the config file and you may as well just type in whole values because even though the config file says 6 decimal places it will only read it rounded up? Or is that a visual bug in game and it’s still reading the sense correctly?

 

always thought pubg felt stuffed sense wise and I’m always mucking around with it 

[DPI Wizard]

2 minutes ago, Snook_ said:

So are you saying converting sense is now useless into the config file and you may as well just type in whole values because even though the config file says 6 decimal places it will only read it rounded up? Or is that a visual bug in game and it’s still reading the sense correctly?

No, using the config file calculation is still the best option. The issue is not that it rounds up to the whole number you see in-game, but that the value you see in the config file is slightly different from the value actually applied. The error is in the 0-0.5% range, so it's not a lot.

[Snook_]

2 minutes ago, DPI Wizard said:

No, using the config file calculation is still the best option. The issue is not that it rounds up to the whole number you see in-game, but that the value you see in the config file is slightly different from the value actually applied. The error is in the 0-0.5% range, so it's not a lot.

Haha wow how is that even a thing.... these devs geez. Pubg has always felt weird sensitivity wise to me and inconsistent. Maybe this has something to do with it.

[LimaBravo]

When select "Aim" except "all"

LastConvertedSensitivity shows absolutely 0.020000.

Please fix it.

[DPI Wizard]

3 minutes ago, LimaBravo said:

When select "Aim" except "all"

LastConvertedSensitivity shows absolutely 0.020000.

Please fix it.

See the game notes mate

Replace the LastConvertedSensitivity value with the calculation from "Config File 2".

[DOTx4]

@DPI Wizard

I want to know the difference between 'config file 1' and 'config file 2'.

and I want to convert sensitivity to 0%mdv in Windows, can you tell me how to use this part?

Edited March 10, 2021 by DOTx4

[DPI Wizard]

4 minutes ago, DOTx4 said:

@DPI Wizard

I want to know the difference between 'config file 1' and 'config file 2'.

They are just pointing to the two different sensitivity values in the config file, "Sensitivity" and "LastConvertedSensitivity". You should set both of them, so you need to calculate both using the two different config file locations. But if you just use the "All" conversion in "Config File 1" everything is done in a single calculation.

[DOTx4]

14 minutes ago, DPI Wizard said:

They are just pointing to the two different sensitivity values in the config file, "Sensitivity" and "LastConvertedSensitivity". You should set both of them, so you need to calculate both using the two different config file locations. But if you just use the "All" conversion in "Config File 1" everything is done in a single calculation.

Thanks for your fast reply.

One more question,  When I convert sensitivity to a game in Windows, only half of the value is output.

For example, I use 600 dpi (wps6/11), but I need to input 1200 dpi (wps6/11) to get a similar sense.

sorry, i'm not good English.