DPI Wizard

Oh, in that case viewspeed no doubt

The last two screenshots have identical output numbers.

Not quite what it means But try changing FOV for H1Z1 on both sides of the calculation now, and you will see that the 360 distance and sensitivity stays the same, that's what unaffected by FOV means.

Not affected by FOV means that the 360 distance (i.e. the sensitivity) is unaffected by it. When you do calculations with monitor distance or viewspeed, it will affect it either way. For all games unless noted otherwise, enter your configured FOV. The scope FOV will either be calculated based on this, or it has a fixed FOV.

Make your browser-window a little wider, and you won't get double boxes. Working on a fix for that now Other than that, it's looking fine. Use the multiplier 1 you get from that calculation, and choose either Iron sight or ACOG for the aim calculation. They use the same sensitivity variables, so you have to choose which one to match perfectly. For sensitivity 2 on acog/iron sight, just enter the default value 50 or whatever other value you have there.

Calculations with acceleration is impossible to do accurately because there is no way to know how much acceleration is applied, as it depends on acceleration amount, movement speed, time to reach x speed, deceleration time and a bunch of other variables. Calculations for min and max could probably be done, but it will not represent any actual reproducible data.

Thank you, and I'm currently working on a brand new version of the calculator which will make everything a whole lot better, more user-friendly and dynamic, all thanks to the subscribers. No more details on this yet though.

No, both his payments went through but were tagged as refused. They are checked out correct now, so one of them is refunded.

Buy gift card for yourself, there is no requirement for a credit card there.

I can probably add a timer to the DPI Analyzer. Also you have this mouse tester tool which does a lot of the same plus more.

The payment failed on Paypal's side for some reason, I cant' see exactly see why. Try again now, in the meantime I've given you premium access

Seems like some of the conversions are failing. I'll take a look at it. But unless you are playing osu! on a different resolution / AR, the result will always be 1 as long as you are playing with the same DPI.

First do conversion to hipfire, and use this calculated value for the iron sight

Added a new Release Notes section here, so anyone interested can check out the changes done (Not updated will all previous versions yet) Click follow on the release notes page if you want to get notified when there's an update.

When you change the DPI for the input game, the value will be cloned to the DPI of the output game as a placeholder value. This happens unless you have actually entered a DPI for the output game. And if this is what's happening, the output doesn't change because both games are using the same DPI.

Rising Storm 2: Vietnam is added!

Rising Storm 2: Vietnam is up with in-game and config file calculations! View full update

Excellent, will start analyzing it immediately!

LawBreakers is up! Had a key myself, but thanks for the offer

Config file settings does not work, but in-game sensitivity is added. Note that sensitivity below 1 does not work either. View full update

I did a quick check in KotK a few weeks back, but nothing in depth. I'll take a closer look

What settings are you using and what are you converting from? Yes, unless you match 360 distance FOV will make a difference.