DPI Wizard

Damn it, no more than one decimal supported by the game. More decimals in the config file will not be read and replaced with zeros. Setting the file to read-only doesn't help.

Reload the page Config File config ASAP.

HALO IS IN!

Halo: Reach is in!

Do you have this issue in other games, or just CSGO? Could you attach your config.cfg?

Is your m_yaw set to 0.022 in CSGO?

What exactly was your result?

Did you try the DPI Analyzer?

I'll be all over Halo when it's out!

No, just what is shown in the config file. I deleted it myself now, and it came up as "fov 115.55556".

Done

Yes. The raw input fix is supposed to not be affected, but it is.

Correct, the placeholder value for games that supports coefficient will be automatically calculated based on your conversion setup. The two should match, because games with coefficients scale everything to this, so you don't need to set any multipliers (unless you have different preferences for different aims). You can override this value by entering your own number.

It's certainly is updated! At 65 it's not quite the same FOV as the Hunting Rifle which is 40. I've updated the calculator to support both the new AR and the Hunting Rifle.

True, it's pretty horrible at 30 FPS. I'll check if it's the monitor refresh rate or actual FPS that affects it. If it's the monitor it should be easy. And either way most computers should be able to reach a cap consistently if it's FPS.

I used this one for the "Raw Input on" calculation. Still affected by vsync though.

Added Kraber now!

Updated the calculator now.

So the issue is that turning vsync off so you get a smooth frame rate also affect sensitivity. And when the frame rate directly affect sensitivity it's impossible to make the calculations, so I can only make it for vsync on unfortunately.

Tested it now, and the file completely changes the sensitivity. Working on an update now. However you should notice huge differences with and without, strange if you don't.

In my opinion yes, as it will make it easier to navigate. Different FOV's will visually feel different, but since hipfire is usually used for navigating and not aiming, having a consistent 360 distance is more important.

The default 1 is the same as MDH 0%, so if your preference is different (like 100%) you will get a higher zoom sens.

Added!