fov_cs_debug

[Kilroy]

Hey, so I wanna do this thing with changing fov in csgo in private, offline maps, using the fov_cs_debug command. I noticed that in the calculator, it says that sensitivity is affected by fov, unlike in other games like tf2 (which by the way runs on the same engine, I'm pretty sure). I went in-game to see this for myself, and sure enough, it is affected, and it seems to use zoom_sensitivity_ratio_mouse instead whenever fov_cs_debug is anything other than 90 or 0 (figured this out by putting a high number like 10, it becomes obvious).

Not so bad at this point, I could probably figure out the right zoom_sensitivity_ratio_mouse to use with the viewspeed conversion, just so long as it normally turns the same amount of degrees independent of fov. But it doesn't. I tested setting fov to 89 just so the right command kicks in, and moved a rough distance to turn some degrees away from an object in-game. Then I set it to 1, and I can very apparently see that it doesn't turn with nearly the same degrees per distance of mouse movement. So at this point, I'm thinking that not only does it switch to zoom_sensitivity_ratio_mouse, it also factors fov into the whole equation.

But I can't figure out how, and I was wondering if anybody knows? Maybe it was mentioned somewhere in the csgo or technical forums, but there's too many pages there to sift through. Thanks.

[Drimzi]

Edited January 28, 2018 by Drimzi

[Kilroy]

Thanks for the quick fix!

[Kilroy]

Wait, I just realized I forgot about zoom_sensitivity_ratio_mouse, which as I tested affects the sens when fov is different. I noticed that you have them different in your examples, but the calculator doesn't say anything about it when I use it, so how did you figure those out?

[DPI Wizard]

I think Drimzi (correct me if I'm wrong) is using a little trick on the calculator. He is matching his Windows sensitivity to CSGO hipfire, but using the FOV of the scope he wants to match. He then uses this sensitivity to match the scope. The scopes have fixed FOV's in the calculator.

As mentioned, calculations when changing FOV in CSGO needs to be verified in the calculator. I'll give you a heads up when it's done.

[Drimzi]

Edited January 28, 2018 by Drimzi

[Kilroy]

I'm getting very mixed up about the words scope and stuff like that, what I understand is that need to do this (to get the right zoom_ratio, sens) for the right hip fire sens at different fovs right? I'm not doing it in order to have a correct awp zoom sens at a different base fov, right?

Thanks for the help.

Edited May 7, 2017 by Kilroy

[Kilroy]

That's weird... when I do this, I get a much more drastic difference in zoom_sens than you do Drimzi.

If I put in the right cm/360 and the right sens for the fov I want, it's like this:

At 60 4:3 base fov, it's 102.170038520154 cm/360 and 0.0508510350025474 sens, which gives me 1.5 zoom_sens.

At half that, 30 4:3 base fov, it's  215.243643715452 cm/360 and 0.0482750813479842 sens, which gives me 0.75 zoom_sens.

Basically, I just multiply the fov by 0.025 and I get the answer I'm looking for, but it's drastically different from yours which is also decreasing when fov increases, unlike mine...

[Drimzi]

Edited January 28, 2018 by Drimzi

[Kilroy]

I technically do switch dpi, but not in the way you would think, and I plan to use the same mouse forever. I use a mouse driver that I downloaded online. I suppose a better name for this is a "filter". It allows me to enter a multiplier of 0.0083565917*12000= 100.2791 DPI for my desktop at 960 by 540 res, and the mouse driver also keeps track of fractional values. Then, I get into a game and I use a multiplier of 1, essentially allowing me to use the same x dpi in both things, since the "filter" operates independent of the mouse and its settings. I don't know if this would lead to the same problems, I don't see how it would. Even if I do change anything in the future, I don't think it would be too big a deal to simply adapt to a bit of change.

As for my abundance of decimal numbers, I know that the game doesn't account for sensitivity beyond too many decimals; I just copy & pasted my numbers from my excel sheet, sorry about the confusion.

As for the zoom_sens, I finally get what I did wrong. Ignore my last post. 

[Drimzi]

Edited January 28, 2018 by Drimzi

[Kilroy]

Yeah, that's exactly right, so I just hit a hotkey in order to switch profiles, to have a desktop sens while I'm navigating menus, then I switch back while playing the game. Happy to hear that logitech mice are good, because I'm using a g403.

[DPI Wizard]

So I took a look at CSGO and fov_cs_debug now. And sure enough, when I change FOV, the base sensitivity changes. Just changing to 91 makes a huge difference in 360 distance. But changing from 91 to 100 scales like expected. So I was a little bit confused, as I think people would have noticed this... Then I tested on another machine with a brand new CSGO installation, and there it scales like expected and according to the calculator; changing to 91 makes just a very small difference.

The CSGO installation that scales wrong have been used for a lot of r_input testing, analysis with different variables and so on. So I have somewhere set a variable or switch that makes FOV scale differently. I'll look through the config file and see if I can find the cause, but unless you have the same "problem", the calculator is correct.