DPI Wizard

Your credit is in EUR, so choose that when you buy the item in the store and it will work.

Original version or redux? Make sure to select the correct version in the special options.

You have to use Monitor Distance or Viewspeed for scopes, 360 distance will always feel wrong. Which on is best is down to personal preference really.

Definitely sounds like something is up with PUBG indeed. Can you PM me the entire config file?

If you have a Logitech G mouse or keyboard available, I can give you a script to verify the calculations in the games.

This feature is actually being considered, it would be very nice to have. But a lot of games do not have config files you can edit, so it would only work on some games.

No, I don't mean set 100% for ADS, set ADS to the calculated scope sensitivity. Those numbers are interchangeable, but will only be correct for the scope you are converting to. So if you for instance want to convert from PUBG to Nyne, do like this (all values are just examples): Now it doesn't matter if you set ADS to 100% and 3.4X to 26.71%, or ADS to 26.71% and 3.4X to 100%, the result will be the same.

Here When you select a game in the calculator, you can scroll down to the Game Info section and click the game title to get directly to the game thread.

All scopes are affected by the ADS sensitivity, not just some of them. So yes, set it to 100%, and calculate each scope. Alternatively you can set everything to 100%, then do one calculation for e.g. 1.5X, then enter the calculated sensitivity as ADS, and keep the scope to 100%.

You must select something else than 360 distance when converting scopes. Try with Monitor Distance 75% or Viewspeed

It's actually not uncommon that mice are 5-10% off of what they say the DPI is. I don't know about your mouse specifically though. Either way you should get the same result in PUBG and Squad. These games are even based on the same engine (Unreal Engine 4), and sensitivity 1 in Squad is exactly the same as 0.07 in PUBG in first person with FOV 90 (0.07 is the default in UE4).

Targeting and scoped sensitivity is not actually in the config file, but you can convert the config file normal sens and convert it to in-game targeting and scoped.

You are not aiming to move the DPI you specify in the analyzer, you are aiming to move the distance. The DPI will be calculated based off of this. You should stop at 10 cm, and the DPI measured then is the correct one. If you are moving 12 cm to get the correct DPI, the actual DPI of your mouse is off by 15-20%.

Do it just for the DPI Analyzer test to make the mouse move within the boundaries, not for the games. The results should be almost exactly the same with any WPS setting.

You have to adjust the Windows pointer settings too then (both in Windows and in the calcualtor), so it moves much slower.

Have you tested the actual DPI of your mouse in the DPI Analyzer? It's not uncommon that measurements are off by as much as +/- 10% depending on how you measure and most importantly what the true DPI of the mouse is. Another test is to measure in another game as well.

Are you testing the 360 in third person? 26 cm with those settings are about correct for first person you see.

Correct. They have a nice mix of terminology between in-game and config file settings, but you can always see what the actual setting is in the output or game info.

Very nice updated features! I was however only able to load it once (didn't time it, took around 20 secs probably), any subsequent attempt result in: Even after a reboot and in incognito mode. Only tried with Chrome so far though.

Fixed it now, try again.

Need a key, if anyone got a spare one PM me.

Updated it now.

It does sound weird. I know people have been using keybinds making impossible jump-crouch moves etc earlier, but I think they removed this possibility from the files. Modifying sensitivity should obviously be permitted...

I see a lot of posts regarding this, it's amazing that they see this as a bannable offence when the in-game settings provide such poor granularity. So yeah don't modify the files. I'll maybe remove the calculations actually so people don't do it by without knowing the possible repercussions.

This is done correctly. The PUBG scope sensitivities are using Monitor Distance 100% by default, that's why you get such little variation with 75%. Setting the sensitivity in the config file is more accurate, but there's been an update recently I need to check regarding this.