DPI Wizard

Added with in-game and file calculations. View full update

FOV in CSGO is locked unless cheats are enabled, so just do with the default settings.

If you are playing Aim Hero and use the Overwatch settings, simply use the same numbers as you use in the game, no conversion needed

What Dayz file are you editing? I see that I now have a "[USERNAME].DayZProfile.062" file in the folder, which is the one I need to edit.

You don't have to worry about it, as it only shows the default value anyway. Ignore it and have great game!

I'm still working on videos etc, but I'll pop inn to say that ANY calculation on this site is tuned to horizontal movement only. Any vertical movement fill just have to follow whatever is set horizontally. And I know there's a lot of smart guys here, so maybe we can come up with something better than Monitor Distance and Viewspeed. Monitor Distance is good as it can be for what it is, but for viewspeed we might be able to do some tuning. I''ll start working on this soon

Please PM me a referral link, and I'll get right on it

I think I have a solution to this. Haven't read through everything here yet, it might be something similar to what is already suggested here.

Ok, I see your point now. However the calculator is using formulas so the vertical chord much closer to 1440 (1519), but still off. I'll look into the formulas

Select Viewspeed instead of 360 Distance

If I understand you correctly, the green chord is a 4:3 monitor and the black chord is a 16:9 monitor, so they must have a different chord length to have the same radius. I'll look more at all the discussion here later, working on a video at the moment

Indeed, that's why I have a machine to do it for me But as long as you do the same movement with both mice, you will get a good idea of their difference even though the measurement might not be accurate.

Unless you notice some performance degradation in the game, use 1000 hz.

Try the DPI Analyzer

0 is a "bad" value for zoomsens, as it is in reality around 0.9 when set to 0. If using 0.9 instead of 0, fill out the calculator like this and go through the scopes for PUBG:

This is the case with some games, but usually the config file settings take precedence. If you change the sliders in-game it will overwrite the config file, so don't touch them

If you haven't seen them, check out these videos:

A simple explanation is that it uses the chord length as a constant, and converts to and from it based on the difference between it and the arc length.

They use the same sensitivity, but KOTK isn't added as a separate game. I will do it soon to avoid any confusion, and get the right path and files in the info

I think I've looked at this before, and it had acceleration issues. But I will take another look!

Only if the actual FOV is identical.

You are right, this game was added before support for different FOV types. Updated it now

Good news, it's finally fixed.. to some degree. Turn off V-Sync, and the sensitivity is stable and calculations spot on.