A question about a sensitivity change caused a new aspect ratio

[Kilroy]

If I change my aspect ratio, say from 16:9 to 4:3 stretched onto a 16:9 monitor, would it be correct, assuming my goal is to keep the same cursor speed I had before, to change my horizontal sensitivity without changing vertical sensitivity, because now there are 0.75 times the pixels, (and therefore degrees) horizontally, whereas there is the same amount vertically?

 

Should I use this snazzy, new fov formula to do so? I can't tell if it's changing the horizontal central angle only, or if something else nefarious is happening, when changing aspect ratios...

 

(360/newfov)(edge to edge distance- percentage increase from arc to chord lengths)

 

...or should I use some other way that doesn't affect vertical sensitivity?

 

Lastly, a question specific to CSGO and other games in the source engine with the command m_yaw, how does it work? I've heard that it changes horizontal sensitivity, but I've also heard that its value is a ratio between horizontal and vertical sensitivity, so it would affect both.

 

 

[Drimzi]

Edited January 28, 2018 by Drimzi

[Kilroy]

Well, in 4:3 stretched, the fov technically changes in a strange way, right? Because if you turn that 16:9 into a 12:9 and leave it black bars, then you cut out 2 units from the left and right, meaning the angle decreases, but the edge to edge distance accompanies it in difference so it's all the same. Unless you stretch it, because now the edge to edge is the same as it was before, but the field of view has been changed on its own and you will see less to the left and right. The vertical angle stays the same though, so that's why I think I should change only the horizontal sensitivity.

 

So is the hfov now 106.26(12/16) = 79.695 degrees?

 

I have 24.3161 e-e

 

With 16:9

(360/106.26)(24.3161-15.91183425%) = 69.27272727 cm/360

 

With 4:3?

(360/79.695)(24.3161-8.54061173%) = 100.46011 cm/360

 

I have very strong doubts about this because if all this were true, then in a 16:9 aspect ratio, 106.26 horizontal field of view should be:

 

106.26(9/16) = 59.77125 vertical field of view, but the calculator says 73.74 degrees, unless vertical degrees is not what I think it is.

[Drimzi]

Edited January 28, 2018 by Drimzi

[Kilroy]

Yeah, the game doesn't know that it's being stretched, so to the game it is the same sensitivity as before, meaning it'll move in the same speed as before. To us, after using the monitor to scale it up horizontally 16/12 times the original picture, the game continues to obey the original sensitivity because it doesn't know any better. So it ends up faster, because now it moves through a visually larger distance in the same time.

 

Let's say for the sake of argument there are only 12 active pixels along the length, at the middle of a monitor, and there are 2 pixels of black to the left and to the right. Move a set distance to bring the crosshair from the leftmost active pixel to the rightmost active pixel, A and B. Move this same set mouse distance, but this time the picture of the active pixels is stretched over the 4 total pixels to the left and right, so there are 16 active pixels along the length. You'll move from pixel A to pixel B in the same time, because the game doesn't realize that there are more pixels now. This would make it much faster, right?

 

Also, I have a theory about why people usually switch back to m_yaw 0.022 eventually, I think that it's because they are more in sync with the map then they are with their own sensitivity. Because when using 4:3 stretched, the map is now stretched, and so they spend as many centimeters moving right to get to that familiar corner as they did before they stretched the map and their sensitivity.

[DNAMTE]

If you were to plot Lines from your head to the edges of your monitor and measure the angle it would become very clear how difficult it is to display 90FOV inside that window and make it appear 'normal'. Increasing the FOV, increasingly distorts the image from the centre outwards. Stretching 4:3 to 16:9 can often appear more natural after using it, quite possibly because you are offsetting some of the distortion,

 

As for viewspeed, on a speed/ pixel measurement then there is a difference but I wouldn't change sensitivity to try accomodate this difference as it's relative to the image. If you wanted to test then increase your sensitivity by the % increase of the ratio.

 

IMO leave it the same.

[Drimzi]

Edited January 28, 2018 by Drimzi

[stereo3D]

you can calculate m_yaw by selecting hipfire (advanced).

 

match at 0 % = m_yaw "0.016500" (0.022 / 1.3333333)