DPI Wizard

Is there any configfiles found under C:\Program Files (x86)\Crysis 3\ at all?

Put it in, the calculator will only use the FOV value if it affects the sensitivity:) Resolution have no effect on sensitivity in CS though, so you don't have to worry about that.

Great to hear! There's a lot of variables to consider, but raw mouse input usually eliminates most of them

Games are still being added, but I'm quite busy at work so I don't have time to do this as much and fast as I'd like to!

FOV definitely affects sensitivity in CS:GO, try to start a singleplayer map with no bots, do "sv_cheats 1" in the console and try "fov_cs_debug 60" vs "fov_cs_debug 110". The difference is huge. However, this command does not work on servers without cheats enabled, and I have not tested any 3rd party FOV changers if there is any. If there is, these might not affect the sensitivity like the built in FOV changer does, and 90 is indeed the correct value to use for calculations.

Try enabling raw mouse input for all the games. The MarkC fix is not relevant for newer games, only old ones. Raw mouse input ensures nothing is messing with the signals from the mouse, and is vital for the calculations to be correct Also, you will usually measure 5-10% off compared to the calculated distance due to mouse sensor inaccuracy and the fact that you are not able to move your mouse in a perfect straight line.

HiCS:GO uses the well known Source formula for calculating sensitivity. Check a few things in the config file that can affect the sensitivity, they should be the default values here: m_customaccel ""0"" m_forward ""1"" m_mouseaccel1 ""0"" m_mouseaccel2 ""0"" m_mousespeed ""1"" m_pitch ""0.022"" m_rawinput ""1"" m_side ""0.8"" m_yaw ""0.022"" Escpecially m_yaw is important. I just fired up CS:GO here, and used your numbers (2.6 sens, 400 DPI and 106 FOV), and the calculations are spot on. Your measurements are so far off, something must be wrong somewhere indeed. Fist of all check the settings I listed here, also if you can try in another Source based game, or any other game for that matter, and see if they also are off.Regarding pixelskipping, you are just below with your settings

In CS:GO sensitivity changes with FOV, and in Garry's mod it scales with your Windows Pointer speed settings. Make sure they are at default values (90 FOV and 6 WPS), and they should be exactly the same.

Good point!

Added! View full update

I'll see when I add it

I've put all of the missing ones to the poll/upcoming list now, so I will add them

CS 1.6 is coming soon!

I've seen some CS games mess up the sensitivity if you e.g. at one point has used the FOV command in the console, even though it doesn't actually change your FOV.

Calculations for ADS is coming in the app, so that will make this even easier

Thanks, they are added to the list There's a Paypal donation box under the poll.

They are coming

Added!

There's really no reason not to use max DPI unless the mouse sensor is bad when at max, or if the game settings do not allow you to get the preferred distance with max DPI. Other than being way too sensitive in the menus that is... Some games do have a separate menu sensitivity though. I have about 3.3" @ 8200 DPI, and about 7.5" @ 3600. One of the most under-used features of the calculator is the DPI conversion: If you select BF4 as both current and new game, then enter your current settings (500 DPI, 4.5" distance), and enter 8200 DPI for the new game, you will get the sensitivity you need to set with 8200 DPI in order to get the exact same distance as with 500 DPI. But at 8200 DPI the movement will be smoother With your current settings you have about 2500 counts/360. That means that the minimum distance you can move your crosshair is about 2 pixels. Take a look at this page, you are currently using a sensitivty equal to the second one from the top. If you convert to 8200 DPI your movement will be twice as smooth as the bottom one!

Hey, what game?

Do you mean what settings I use? If so, I use sensitivity 0.00075 and quickswitch between 8200 DPI and 3600 DPI for hipfire, and 2400 DPI for ADS. G700s DPI is off by about 10% btw (at least mine), so if you want precise calculations add approx. 10% to your DPI. I.e. use 9000 instead of 8200, 4000 instead of 3600 etc.

Cool, I'll check it out!

This is most likely due to inaccuracy in the mouse sensor. The distance calculated is a direct result of the DPI you put in. If your mouse is set to 450 DPI, but in reality is 430 DPI, you will get a different measurement than the calculated distance. Most mice I've tested are not delivering the DPI they are set to, some are off by as much as 10%! But the important thing to notice is that this inaccuracy is constant, so you will get the same distance in all games, altough not exactly what the calculator says.

Added it to the poll

Hey, are you playing Ghosts multiplayer or singleplayer? If you change the sensitivity in-game instead of the file, is the sensitivity in the file updated?