DPI Wizard

I hope you didn't get too excited when you saw this topic I've gotten many requests to make support for the XIM 4. But from what I've seen the XIM 4 is way too inconsistent to be integrated into the calculator. Pretty much all games have some form of smoothing or acceleration (both positive and negative), and it's in general just a mess at the moment. Should Sony or Microsoft release native support for keyboard and mouse, I'll look at this again! I hope they do, because that opens up a whole new use for this site!

Correct, that is best for consistency

Just checked the release version, and it has the same issue as the beta. You can set it below 1, but it actually doesn't do anything. I.e. 0.5 and 1 is resulting in the same sensitivity.

As long as you use Monitor Distance, it makes no difference if you use CSGO or PUBG hipfire as the source for your conversions (if the PUBG hipfire sensitivity is already converted as Monitor Distance from CSGO). But to make it easy, use CSGO as the source for all of them

I'm guessing you use FOV 90 as the actual FOV , and not configured vertical FOV? If so, you are indeed very close to sensitivity 50 in PUBG: Go through the scopes with these settings. If you haven't changed the USA or other zoom sensitivities in Battlefield, use Monitor Distance 75% for the exact same feel.

You're doing it correctly, just do the same for each scope and aim. If you do not play 1st person in PUBG, skip that aim. If you do play it, remember to enter your configured FOV as well.

Check out these videos, they'll hopefully get you started! You should use Monitor Distance at a preferred percentage (games like CSGO uses 75% between hipfire and scope, PUBG uses 100%). Viewspeed is around 70%. The most important thing is to use the same method for all conversions, like in the video below (25% is just an example).

Yes, increase PUBG FOV to 103, and use Monitor Distance 0% for all calculations

I haven't done any changes, but sometimes the calculation doesn't fire from each keypress like it should, so when you enter the last digit it might be stuck at a the previous number. For instance 0.0 instead of 0.09. Execution will be improved in the next update

Like this? Should work, try clicking into the sensitivity 1 box and press enter if it doesn't update.

@Drimzi Correct, only odd guy out is driving a bike, then the 1st person adjustable FOV is used.

1st and 3rd person will always match to 100% Monitor Distance, which makes them feel similar regardless of FOV.

The only difference between 1st and 3rd person servers is that you cannot change to 3rd person on the 1st person servers. The FOV slider affects targeting and hipfire in 1st person, and nothing else (regardless of server).

Just added KOTK as a separate game (reload if you don't see them both). They are identical in terms of sensitivity, but paths for the config file is different etc, so I separated them.

Indeed correct! (they may of course change this at any moment again...)

Try 100% instead, that would match the whole desktop movement

All scope FOV's were changed, but the scaling is still the same (100% Monitor Match) between all of them. So the sensitivity formula is the same (almost, added a small tweak to make it 100% correct by using a fraction instead of a decimal number), but the FOV part is updated. The calculator is correct, buy there's been quite a few changes since the 1st person patch.

You are using a very weird resolution 1600x888, is that correct? Also make sure the FOV is what you have actually configured. Lastly, see how it feels in first person mode, 3rd person is quite difficult to compare. I think he means 0% Monitor Distance match in the calculator. Although 0 in-game should still move your mouse, albeit slowly.

Scoping is still 70 actually.

Added it now!

This much requested game is now in the calculator! View full update

Added by popular request! I'll be all over this game as soon as I can

The payment is still pending, check your status here. If it has gone through on your side, give me the transaction id and I'll fix it. Edit: Never mind, just took a few minutes.