Counter-Strike 1.6/ CZ

[MuntyYy]

Hello community !

I have one more issue to nag about in C.S 1.6. DPI Wizard, I'm aware you're already working on monitor match at different FOVs, but I need to address another problem, unfortunately.
And that is the following: The game has horrible mouse acceleration, mostly negative thus making small adjustments in aim almost impossible to handle ( more of this I will explain thoroughly in another post + a possible fix for it ). I will keep it short - when attempting to match the sensitivity of CS:GO in CS 1.6 and converting it with the 360 method, all good ( almost ); but moving the mouse across fewer degrees ( 90, 45, 30 ) on the screen, results in a 10 to 20% "loss" in sensitivity. To clarify it, imagine you need 9cm to move across a 53.13 degree field of view & about 30 to do a 180 turn. But, upon testing it, I realized that the 9cm required movement isn't 9, but closer to 7/8, whilst the value for a 180 turn remains unchanged ( almost,  as the acceleration sux ).

Is there anything that can be done for it ? I've read some forums, and I ain't the only one that realized the issue, a lot of peeps said to decrease the sensitivity to about 20% of your initial one.

Have a wonderful day,
Munty

Edited June 15, 2018 by MuntyYy

[MuntyYy]

I'm just gonna put this here, can't be bothered to spam with another post.

The reason why cs 1.6 has acceleration even with rawinput 1 might be because of its base FOV. The game has 73.74 ( or atleast that's what I think from my tests; I however, stand corrected ) and not 90 that explains why my sensitivity from cs go - 1.703917 won't do the trick and rather 1.44318 ( IW2 engine ) works decent enough. Also, since even stretched the hFOV remains the same the game inputs acceleration. More of this can be seen on this topic - https://play.esea.net/index.php?s=forums&d=topic&id=625908&find_comment_number=28.

So, to get rid of the acceleration and make the feel natural, the following must be done:
1. Change m_yaw from 0.022 to 0.0165
2. Multiply your sensitivity, for example 1.44318 by either 1.33 or 1.142857142857143 ( I'm not quite sure yet ) & that's all.

To note is the following: - I've only checked the acceleration problems on 4:3 resolutions; best one being 1440X1080.

If there's any doubt or questions, feel free to join this conversation.

 

Munty.

Edited June 15, 2018 by MuntyYy

[MuntyYy]

If anyone wonders from where I got the number "1.142857142857143" >>>
 

"old sensitivity 1.44318, m_yaw 0.022 -> (1.44318 * 0,022) + (1.44318 * 0.022) = 0.048...

then

new sensitivity 1.649348571428572 (1.44318 * 1.142857142857143 in this case), m_yaw 0.0165 -> (1.649348571428572 * 0.0165) + (1.649348571428572 * 0.022) = 0.048... -> same result"

 

The difference is like night and day

http://www.notalent.org/sensitivity/sensitivity.htm

Edited June 15, 2018 by MuntyYy

[MuntyYy]

Update: disregard what I've said, messing with the yaw will make pitch feel faster and viceversa. The game has 73.74 FOV that's the only problem I have. If anyone could come up with a fix, or an external program ( I manly train with bots ) I would appreciate it.

 

Good nite,
Munty

[DPI Wizard]

Sent you a PM

[Quackerjack]

can u tell us also what u did=??