Oh and I use viewmodel_fov 90 (Which sets it to 68), viewmodel_offset x 3 (Which is 2.5), viewmodel_offset y 3 (Again 2.5), viewmodel_offset z -3 (Also -2.5), and cl_lower_bob_amt 10. These could be the problem.

 

Valve capped fov to 68 and viewmodel offsets to 2.5 respective in each directions.

Sounds like hardware mouse acceleration along with lower-than-advertised DPI. Always a good idea to manually measure it since mouse mats and mouse feet can change it.

 

Also, CS:GO automatically scales FOV with aspect ratio, so just leave it at 90.

Having some issue going from BF4 to CS:GO. My 360 degree turn is 10.5 cm which is 1.875 in CS:GO however when i turn 360 degree in CS:GO it's nearly double in length (too big for my mousepad atleast)

Viewmodel is just the rendering of the gun if I'm not mistaken? Correct me if I'm wrong. Other than that, the calculator uses the 4:3 FOV in the calculations, I know this can be confusing, and not exactly easy to work with. An upcoming update will let you enter both resolution and FOV in either horizontal or vertical FOV or Radians. And also calculate these numbers for you

Ok thanks. I'm using 16:9 Aspect Ratio.

Hello Wiz, is there a way to make a calculator for the ADS sensitivity in CS GO? It would be great if you can make one for sniper rifles.

TY very much!

I think there is something wrong with the calculations for Counter Strike Global Offensive. In the info box it says that that the ingame FOV does affect the sensitivity, however it doesn't.

As you can see in the following image:

 

http://ineye-media.de/myHYPER/wp-content/uploads/2012/08/csgo_vergleich.png

 

The vertical FOV is always the same in the source engine (roughly 74°).

 

At an aspect ratio of 16:9 my FOV seems to be 106°H, but when I type that value in the standard calculator it gives me a clearly wrong sensitivity, 90°H gives the right value.

 

4:3 = 90°

16:10 = 100°

16:9 = 106°

 

source:

http://forums.steampowered.com/forums/showpost.php?s=165a8d668f3e5cfc126570ae775ebc2e&p=31476234&postcount=13

 

I tested it out ingame and there is no way it's only 90°H on 16:9

Maybe the new calculator gives the correct result, but I dont know what all these values like FOV Base etc. mean.

Apart from this I really love this website and your service so a big THANK YOU to you.

Thanks! I'll look into this soon, and get the FOV calculations more accurate. Originally I only used horizontal FOV, which makes the calculations for some games hard to get right. I will go through all games and update them with correct base FOV

Is the sensitivity really as per CSGO? It feels much slower in Titanfall when I use the same sens in CSGO

It should be, as they use the same game engine. But I'll look into this!

Hey, I'm just wondering... If i take my BF4 sensitive and turn it into CS:GO sensitive will it be same as aimdownsigh or hipfire in bf4?

Hipfire!

Is this information for cs:go correct? because i am unsure on how to convert my sensitivity from one res to another if there is different fovs for each res, which cannot be modified.

 

On 4:3 resolutions (such as 1024x768 and 1280x960), the horizontal FOV is 90.

On 16:10 resolutions (such as 1440x900 and 1680x1050), the horizontal FOV is 100.

On 16:9 resolutions (such as 1280x720 and 1920x1080), the horizontal FOV is 106.

or is it 90 on a 16:9 res, 74 on a 4:3 res.

You do not have to convert your sensitivity based on resolution in this case as the engine uses the ""90"" setting, but automatically adds field of view based on aspect ratio.

 

(It is indeed 106 for 16:9)

Are you sure 16:9 has a fov of 106. I measured movement with a ruler and it was way closer to the 90 fov calculation than the 106.

It's correct that the actual FOV changes depending on aspect ratio, but as far as sensitivity goes, resolution and AR doesn't affect it for CS:GO. So the configured FOV is what you should enter in the calculator

So I've tested the fov thing a tiny bit, but not sure what the information I found means. What I did was go into a bot game, put cheats on and try to change the fov_cs_debug to 90, then 100, then 106. It didn't change with the first, and the got wider with the other two, on a 1920:1080 resolution, 16:9 (my monitor's native). So clearly the default value for fov_cs_debug is 90.

 

As I said, not sure if that means 90 is default horizontal fov for 16:9. Just throwing some info out there

 

Going by feeling, I never noticed much discrepancy between tf2/l4d2 (steam games, not affected by fov) and cs:go on 90. I thought I felt it was a bit different, but I thought it was due to the fact how cs plays compared to the other two, and how accuracy is much more important. Either way, not 9 cm different, but who knows.

 

edit: Oh, nvm, wizard already answered. I'll leave it here anyway.

Edited September 13, 201411 yr by Mednes

DPI Wizzard, is it possible to add calculations for scoped sensitivity? I know it has something to do with the "zoom sensitivity"/"zoom_sensitivity_mouse" but I can't seem to be able to get the right sensitivity.

DPI Wizzard, is it possible to add calculations for scoped sensitivity? I know it has something to do with the "zoom sensitivity"/"zoom_sensitivity_mouse" but I can't seem to be able to get the right sensitivity.

I'll look into it!

waz up 

i would like to change from 4:3 to a 16:10 resolution can i match the sensitivitys using this tool?

if so help me pls will be grateful  

waz up 

i would like to change from 4:3 to a 16:10 resolution can i match the sensitivitys using this tool?

if so help me pls will be grateful  

If you keep the same FOV setting, the sensitivity (for 360 degree turn) will be the same

using 4:3 ingame but my monitor is 16:9. do i still use fov 90? 

And it puts my dpi at 2.5156... should i round up to 2.52 or down to 2.51? it feels more natural like my mouse at 2.52 but 2.51 feels slower/maybe some more control?

Edited January 16, 201510 yr by Michael Woo

using 4:3 ingame but my monitor is 16:9. do i still use fov 90? 

And it puts my dpi at 2.5156... should i round up to 2.52 or down to 2.51? it feels more natural like my mouse at 2.52 but 2.51 feels slower/maybe some more control?

I believe that the FOV doesn't change on 4:3 that is used to calculate, and you can use the console (press the ~ key, you might have to enable it in game settings) and type in "Sensitivity 2.5156" then press enter.

I believe that the FOV doesn't change on 4:3 that is used to calculate

Correct. 90 is the configured FOV regardless of AR.