Solving Problem with CSGO to other games

[davixx500]

So since few days i have been crushing my head over this problem. 2 years ago i stopped playing csgo and now i got back into it i used to play 16:9 with 1600dpi and 0.87 sens with default m_yaw now obviously when you switch to 4:3 streched it changes the sensitivity as well so i read about m_yaw and  its 0.018025 so far so good i tested the sense out and it feels good, But here is my problem. the 360 distance of 16:9 0.87 sens is 29.8589 the 360 distance of the 4:3 sens is 36,4436 so the 4:3 sens is much slower then on 16:9 ? shouldnt i be getting 1:1 from 16:9 to 4:3 by using the m_yaw? and what about zoom sensitivity ? to have 1:1 what do i set it at becaasue i cant seem to be able to calculate it, Also that leaves me with Problems converting senses to other games becasue i dont know what to use if i convert from the 4:3 sensitivity or the 16:9 one. Im just so confused i hope someone can explain all this to me

Edited February 22, 2020 by davixx500

[DPI Wizard]

The 360 distance will be the same with the default m_yaw. Using m_yaw 0.018025 means that the 4:3 stretched sensitivity is matching 16:9 using MDH 75% which is the default match for CSGO (i.e. the same scaling as scopes using zoom sens 1). This only affects the horizontal sensitivity, the vertical is not changed.

When converting to other games select "Calculate m_yaw" for CSGO and you can enter your m_yaw value:

[SeizureStorm]

This is kinda separate but before CSGO had sensitivity 2 enabled for the "all" setting. Could that be put back instead of defaulting it to .81?

[DPI Wizard]

3 hours ago, SeizureStorm said:

This is kinda separate but before CSGO had sensitivity 2 enabled for the "all" setting. Could that be put back instead of defaulting it to .81?

You're probably thinking of when "Calculate m_yaw" is selected, then sensitivity 2 is enabled as you must enter the m_yaw value. When using the All setting with "Calculate sensitivity" the sensitivity 2 value will be calculated based on the conversion setup. So if you're not using 0.81xxxx adjust the setup to match your configuration. 

[davixx500]

13 hours ago, DPI Wizard said:

The 360 distance will be the same with the default m_yaw. Using m_yaw 0.018025 means that the 4:3 stretched sensitivity is matching 16:9 using MDH 75% which is the default match for CSGO (i.e. the same scaling as scopes using zoom sens 1). This only affects the horizontal sensitivity, the vertical is not changed.

When converting to other games select "Calculate m_yaw" for CSGO and you can enter your m_yaw value:

Thank you! but what i dont get is. if i for example want to convert sens from csgo to cod mw it will tell me that from 1920x1440 the sense is 2.89 and from normal 16:9 2560x1440 its 2.37. But shouldnt the sensitivity be the same on csgo no matter 4:3 or 16:9 by changing the m_yaw? then why is there a difference converting from 4:3 to 16:9 and vice versa. it would be nice if you could explain that so it maakes sense in my head and i can understand why.

[DPI Wizard]

1 minute ago, davixx500 said:

Thank you! but what i dont get is. if i for example want to convert sens from csgo to cod mw it will tell me that from 1920x1440 the sense is 2.89 and from normal 16:9 2560x1440 its 2.37. But shouldnt the sensitivity be the same on csgo no matter 4:3 or 16:9 by changing the m_yaw? then why is there a difference converting from 4:3 to 16:9 and vice versa. it would be nice if you could explain that so it maakes sense in my head and i can understand why.

It depends on what you are converting. If you convert 360 distance then there is no difference as aspect ratio does not affect 360 distance for these games. But if you use a horizontal method (Monitor Distance or Viewspeed) then changing aspect ratio will change the FOV, which is used to match the sensitivity. So if you match FOV then converting from 4:3 with m_yaw 0.018025 is the same as 16:9 with default FOV:

[davixx500]

2 hours ago, DPI Wizard said:

It depends on what you are converting. If you convert 360 distance then there is no difference as aspect ratio does not affect 360 distance for these games. But if you use a horizontal method (Monitor Distance or Viewspeed) then changing aspect ratio will change the FOV, which is used to match the sensitivity. So if you match FOV then converting from 4:3 with m_yaw 0.018025 is the same as 16:9 with default FOV:

I completely forgot about the FOV in this case. Great! my understanding is a bit better what mostly confused me is that i used this converter years ago and i remembered 0.87 being 30cm 360 so i was confused why with the m_yaw its 36 now basically much slower. You said the 4:3 stretched will match 16:9 so if Fov is the same at 90 and all is the same why does it go from 30 to 36, Besides i wondered is the feeling maybe the same with 30cm 360 at 16:9 versus 36cm 360 at 4:3 streched ? but then again why does the calculator show still 36 cm 360 when i calculate with a 16:9 resolution. So confusing this topic. 

 

Also 106 fov in cod mw is like fov 90 in csgo (16:9) in 4:3 the hfov is 90  but with matching fov so meaning, in csgo its always 90 and mw its 90 4:3 to 16:9 the sens gives me 2.89 if i switch csgo to resolution 16:9 so i convert 16:9 to 16:9 with matching fov csgo at 90 and mw at 106 it gives me much slower sens 2.37 ahhh confusing the hell out of me  what i want to use. i just want my old sens that i used in csgo years ago so 0.87 with default m_yaw at 16:9 resolution to feel the same at 4:3 stretched and then i want this same sensitivity to convert to other games like apex or cod mw or whatever. So which one of those is the right one? the one that gives me 2.37 in mw or 2.89