Double Scope With Awp Issue

[stormy9699]

This bug has been around since 1.5, when you double scope with the awp and move your mouse slowly to the left, your crosshair jitters and it doesn't move to the left. However, it moves fine to the right. Also, this bug doesn't exist with the scout or auto-snipers. It might have something to do with the reduced movement speed the awp has. This usually happens when your sensitivity is below 2.0. Would love to see this get fixed! :)

[r3n4m3]

dupe for https://github.com/ValveSoftware/steam-for-linux/issues/1493

[Gr1mRe4pEr]

I can also confirm this. Using an old Intelli Explorer 3.0a with no USB tweaking. I know its been around for a while, since I was using Windows XP

Now Win 7 x64 SP1

Happens with m_rawinput = 1 on the beta

[f4k3]

I can reproduce that with scout and even without zoom.

1. With mouse at 400 dpi with sens 0.2 while not zoomed. It's seems like dx around -10 didn't counted or applied.
2. With mouse at 3500 dpi with sens 0.2, default fov 1000. It's seems like dx around -50 didn't counted or applied.
3. With mouse at 1800 dpi with sens 0.2 m_yaw 0.019, fps max 1000. dx is around -2.

It's fps dependant, with higher fps it's more noticeable. If you use mouse with 400 dpi you can be affected by this bug at high fps and midle sensitivity. Even without zoom.

It seems like small negative movement on the axis line X didn't applied to the YAW, or has been discarded for some reasons. Positive movement is fine.

If you need to reproduce that bug use high fps and small sensitivity, with high dpi you can use default_fov and m_yaw. Move slowly mouse across mousepad from right to left.

IMHO issue is in setviewangles mechanism or in mouse specific code.

[f4k3]

any comment from dev? this bug is crucial, we cannot play with low/mid sens with high fps.

[LeRaldo]

I also experience this issue. It happens regardless of m_rawinput 1 or 0. Currently using in-game sensitivity of 1.000000 and Windows sensitivity of 6/11 aka 5/10, at 1150 DPI. I've had this problem as long as I can remember, across all kinds of different mice and operating systems, so it's not just a bug introduced by any of the recent updates.

[f4k3]

http://youtu.be/8Z09xvpNQ3E

[idderf]

I really think this needs a working fix asap =)

[nsbroderick]

Just came across this recently. A workaround I found - provided your mouse's CPI can be adjusted - is to lower your CPI/DPI and increase your sensitivity such your CPI-Sensitivity Product remains constant. E.g., if your sensitivity is 1.0 and your DPI is 800, the workaround could be achieved by setting your DPI to 400 and your in-game sensitivity to 2.0. (Note that 1.0 800 = 2.0 400 = 800, the CPI-Sensitivity Product in this example). This should resolve the issue while maintaining your effective sensitivity (or get you very close to it).

[10th]

In most cases (in some cases, the sensitivity value is different): sniper scope > zoom = x2 m_yaw 0.022 zoom_sensitivity_ratio 1.2 sensitivity 1.8700685 - good sensitivity 1.87006849 - bad (at a very, very low speed of moving the mouse to the left sight remains in place)

[djdallmann]

Yea this is annoying at best, hard to slow move to the left with awp when zoomed. I'm more curious why this happens and how we can avoid it, if it can't be fixed.

[xiaoxufeiji1a]

I have 800 CPI, 2.0 sens, 1.0 zoom sens. then I feel this bug very significant when I using AWP double scope. at latest counter-strike on steam: Protocol version 48 Exe version 1.1.2.7/Stdio (cstrike) Exe build: 15:58:59 Apr 3 2019 (8196)

now 2019 november 30,this bug still exist and not been fixed

[Maxi605]

I have 800 CPI, 2.0 sens, 1.0 zoom sens. then I feel this bug very significant when I using AWP double scope. at latest counter-strike on steam: Protocol version 48 Exe version 1.1.2.7/Stdio (cstrike) Exe build: 15:58:59 Apr 3 2019 (8196)

now 2019 november 30,this bug still exist and not been fixed

Once the new update is released they're more than likely will check and patch it, just be pacient, the game isn't going anywhere.

[satnatantas]

This bug is still here!

[mjsmith707]

This bug has plagued me for years. Finally found the issue for it.....

[satnatantas]

BTW, this is present even at sensitivity=1. I can't feel any effect at sensitivity=5 for sure for example.

[perforatorRU]

The more frames per second, the more obvious the bug.

Its a critical bug, fix this plz!!

[djdallmann]

yea this bug is NASTY

[BlackShadow]

@mikela-valve it would be a really nice if you can fix this. Playing double-scoped is impossible.

[BIMBOM]

Bump!

1. Mouse skiping coords on moving left with double zoom. Fix it plz. Aiming bugs should be given the highest priority. CS not TETRIS, CS = First Person Shooter!!!
2. Need more range precision "sensitivity" "0.001" minimum. (like CS:GO) becouse i have 25600 DPI limit on my mouse, i want use it. Now (eDPI = 1024): DPI = 800; Sens = 1.28; ----> DPI = 25600; Sens = 0.04;

THANK U!

[SmilexGamer]

Bump!

1. Mouse skiping coords on moving left with double zoom. Fix it plz. Aiming bugs should be given the highest priority. CS not TETRIS, CS = First Person Shooter!!!
2. Need more range precision "sensitivity" "0.001" minimum. (like CS:GO) becouse i have 25600 DPI limit on my mouse, i want use it. Now (eDPI = 1024): DPI = 800; Sens = 1.28; ----> DPI = 25600; Sens = 0.04;

THANK U!

Don't bump the thread, it's already in the "Future Release" milestone.

[ghost]

I honestly doubt this will ever be fixed. It's an honestly sad bug. It forces me to play at 200 DPI (and 3.7 sens). Otherwise I'd use 800 DPI and 0.85 sens, or 400 DPI and 1.7 sens.

[perforatorRU]

Values less than m_yaw 0.25 cause a bug

https://youtu.be/Q3LLnwlhdco

DPI 400 m_rawinput "1" cl_mousegrab "0" m_customaccel "0" m_customaccel_exponent "1" m_customaccel_max "0" m_customaccel_scale "0" m_filter "0" m_forward "1" m_mousethread_sleep "1" m_pitch "0.25" m_side "0.8" m_yaw "0.25" sensitivity "0.2" zoom_sensitivity_ratio "1"