1/7/2016 Update significantly shifts mouse sensitivity value

[kvbev]

OS: Arch Linux Desktop: i3wm Graphics: amd 7870 running radeonsi open source drivers and mesa3d 11.1.0

Mouse: Corsair M65 hardware set DPI: 800

Mouse acceleration has been disabled globally for my desktop using the libinput method described here: https://wiki.archlinux.org/index.php/Mouse_acceleration#Disabling_mouse_acceleration

Ingame raw input: off Ingame accel: off

before the update I played with an in game sensitivity value of 1.4

after testing in deathmatch with the new patch the sensitivity value I have to use to even get close to the original aim movement speed is somewhere between 2.4 and 2.8.

I could probably get a more exact value however it seems minor movements of the mouse are lost on input or feel more sluggish and even with higher sensitivity values, finer aiming control does not feel as it was before.

for me I would consider the game playable once I find a new value to use however the massive shift of how the sensitivity value is interpreted is unfortunate.

for me turning raw input on or off does not change anything.

[JoshuaMurphynz]

This is on purpose. You just double what you had before. Now you can use the same sense across all platforms On 8 Jan 2016 17:43, "Kvbev" notifications@github.com wrote:

OS: Arch Linux Desktop: i3wm Graphics: amd 7870 running radeonsi open source drivers and mesa3d 11.1.0

Mouse: Corsair M65 hardware set DPI: 800

Mouse acceleration has been disabled globally for my desktop using the libinput method described here:

https://wiki.archlinux.org/index.php/Mouse_acceleration#Disabling_mouse_acceleration

Ingame raw input: off Ingame accel: off

before the update I played with an in game sensitivity value of 1.4

after testing in deathmatch with the new patch the sensitivity value I have to use to even get close to the original aim movement speed is somewhere between 2.4 and 2.8.

I could probably get a more exact value however it seems minor movements of the mouse are lost on input or feel more sluggish and even with higher sensitivity values, finer aiming control does not feel as it was before.

for me I would consider the game playable once I find a new value to use however the massive shift of how the sensitivity value is interpreted is unfortunate.

for me turning raw input on or off does not change anything.

— Reply to this email directly or view it on GitHub https://github.com/ValveSoftware/Counter-Strike-Global-Offensive/issues/574 .

[kvbev]

playing at 2.8 is not the same as 1.4 before the patch for me.

[JoshuaMurphynz]

The only reason why the library was updated was to make the sensitivity the same across all platforms. Are you sure this is a present bug? On 8 Jan 2016 17:45, "Kvbev" notifications@github.com wrote:

playing at 2.8 is not the same as 1.4 before the patch for me.

— Reply to this email directly or view it on GitHub https://github.com/ValveSoftware/Counter-Strike-Global-Offensive/issues/574#issuecomment-169896145 .

[kvbev]

I am going to play more to attempt to find a more accurate value however simply doubling my value did not feel the same.

also to make the claim that sensitivity is the same across platforms now does csgo use libSDL as the input subsystem on windows?

[jasonmit]

I could probably get a more exact value however it seems minor movements of the mouse are lost on input or feel more sluggish and even with higher sensitivity values, finer aiming control does not feel as it was before.

I am seeing this as well. If I move my mouse linearly in any direction the crosshair tends to stick to certain areas now. The game is unplayable.

Distributor ID: Ubuntu
Description:    Ubuntu 15.10
Release:    15.10
Codename:   wily

[Numkil]

I can confirm that moving the mouse very slowly will result in the croshair not responding on the screen. The mouse has to reach a minimum velocity before it get's parsed to the game. This may be related to me using a relatively new version of libinput?

Smaller aim adjustments are impossible to do now. I guess this will be yet another week of being forced to not play csgo.

System specs:

Distributor ID: Fedora Description: Fedora rawhide Release: Rawhide Desktop: Gnome

Mouse: Corsair M45 hardware set DPI: 800

Ingame raw input: off Ingame accel: off

Libinput version : 1.1.4-1

Graphics: amd r9 290 running with the open source radeonsi drivers with the latest rawhide version.

[kvbev]

after playing a few competitive matches im going to retract my original range of 2.4-2.8.

for me 2.1 feels pretty close as before for my 1.4, if that is accurate the formula could be to add 50% to your previous sensitivity value.

for me im still on the fence about if the fine control issues may be in my head, not to discount if others are having that issue.

[craysiii]

Also confirming slow mouse movement causes crosshair to become unresponsive.

Ubuntu 15.10 x64 Razer Mamba Chroma TE Raw Input: On Accel: Off Nvidia GTX 960 on 355.11

I was excited for this update because I had read a couple days ago about the SDL bug, but like its been said, it's currently unplayable.

[Toqozz]

Slow mouse movement results in no crosshair movement in game.

Arch Linux Razer Deathadder Chroma Raw Input: Off Accel: Off

Mouse acceleration has completely been turned off using the same method as OP.

[jamezmoran]

Judging from reddit, not everyone has the crosshair sticking issue. You should edit your posts with your full steam system information if you can.

[Crendgrim]

I do also have the sensitivity shift (old sensitivity multiplied by two feels off), but I do not have the deadzone issue.

openSUSE Tumbleweed 20160105 (Kernel 4.3.3) with Plasma 5.5.2 Intel i5 4670K, NVidia GeForce GTX 760 on 358.16 Logitech G502 raw input 1, accel off

[jamezmoran]

To be clear, the sensitivity shift is intended and is not a bug. The bug is the crosshair not responding to small movements in the mouse at all.

[hitcher404]

I have no 'deadzone' issue and doubling my previous sensitivity produces the same angle turned from moving from one side of my mousepad to the other. However I have noticed a strange inconsistency in the way mouse input moves in game.

I do not know if this was present before yesterdays update but I am inclined to think it was not as I noticed it very quickly when lining up a smoke throw I have done countless times before.

In game face directly upwards, pick up your mouse and place it at the bottom left corner of your pad, move diagonally to the top right corner, note how many rotations you do. Repeat this process but with the bottom right corner and moving to the top left. For me this produces significantly less motion.

Can anyone try this out and confirm? I have tried another mouse to rule out sensor malfunction, same result.

[atomicflag]

@hitcher404 this sounds like #44. The solution proposed there fixed the problem for me.

[mlandalv]

I also have the problem with slow mouse movement = crosshair doesn't move at all, so currently pretty much unplayable :(.

Processor Information:
    Vendor:  GenuineIntel
    CPU Family:  0x6
    CPU Model:  0x2a
    CPU Stepping:  0x7
    CPU Type:  0x0
    Speed:  5900 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported

Network Information:
    Network Speed:  

Operating System Version:
    "Arch Linux" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.3.3-2-ARCH
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11800000
    X Window Manager:  Xfwm4
    Steam Runtime Version:  steam-runtime-release_2015-06-12

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 960/PCIe/SSE2

    Driver Version:  4.5.0 NVIDIA 358.16
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x10de
    DeviceID:  0x1401
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1200
    Desktop Resolution: 1920 x 1200
    Primary Display Size: 20.43" x 12.76"  (24.06" diag)
                                            51.9cm x 32.4cm  (61.1cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 4096 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: 

Memory:
    RAM:  16019 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.utf8
    Microphone:  Not set
    Total Hard Disk Space Available:  168880 Mb
    Largest Free Hard Disk Block:  58040 Mb

Installed software:

Recent Failure Reports:

[hitcher404]

@coffee-lord Many thanks for linking that.

As the solution proposed in #44 involves patching libsdl, is it not reasonable to assume that the new version of it included in the recent update is the cause of the issue returning? Have other people experienced this 'halved sensitivity when moving up and left' (beyond 0,0 in whatever coordinate space libsdl uses)? Has this been happening all along?

[jamezmoran]

This is a shot in the dark, but a reddit user noted that changing resolution aspect ratio to 16:9 from 4:3 solved the problem. Can others try this and confirm whether it works or not?

[mlandalv]

@jamezmoran Nope, doesn't solve it, but I started testing different resolutions. I have a 1920x1200 monitor (16:10), but usually play with 1280x800. When changing to the native resolution all mouse movement is registered, even the slow. The lower resolution, the more mouse movement disappears. Same seems to happen with 4:3.

[jamezmoran]

@mlandalv have you tried using windowed mode? I'm wondering if this issue is being caused by a buggy initialisation of SDL.

[mlandalv]

I'm in the middle of work, but I did a very quick test, and 1280x800 worked fine in windowed mode.

[atomicflag]

@hitcher404 nope. As far as i know this issue is not caused by libsdl but rather csgo itself. I might be wrong though. Anyway i had this problem ever since csgo was released on linux and not a single new version of libsdl has fixed the issue. I had to manually patch libsdl every time.

So even though they shipped the new libsdl i'm still using LD_PRELOAD with the patched libsdl.

[jamezmoran]

@davidw-valve on top of the testing above, I'm receiving multiple confirmations on reddit that the problems with the awkward crosshair movements are eliminated when using windowed mode or by using the native desktop resolution when fullscreen. This appears to be an issue with how CSGO is setting up the fullscreen window using SDL, perhaps that the ingame resolution is mismatched with the window resolution.

I haven't tested this myself as I'm at work, but I highly suspect this issue is simply replicable by using fullscreen at less-than-native resolution.

[ghost]

I also have this issue. My sensitivity must be 3 times lower or something like that now. Are we supposed to change values manually or is this going to be fixed?

[sadger]

Have the same issue, moving the mouse very slowly does not cause the crosshair to move at all, as of the update yesterday. Makes the game unplayable for me. Raw input = on, Acceleration = off. Mouse steelseries kana v2.

Processor Information:
    Vendor:  GenuineIntel
    CPU Family:  0x6
    CPU Model:  0x1e
    CPU Stepping:  0x5
    CPU Type:  0x0
    Speed:  2934 Mhz
    8 logical processors
    4 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported

Network Information:
    Network Speed:  

Operating System Version:
    "Arch Linux" (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.2.5-1-ARCH
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11704000
    X Window Manager:  awesome
    Steam Runtime Version:  steam-runtime-release_2015-06-12

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 460/PCIe/SSE2

    Driver Version:  4.5.0 NVIDIA 355.11
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x10de
    DeviceID:  0xe22
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1680 x 1050
    Desktop Resolution: 1680 x 1050
    Primary Display Size: 18.66" x 11.65"  (21.97" diag)
                                            47.4cm x 29.6cm  (55.8cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 1024 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: VIA VT1828S

Memory:
    RAM:  7985 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_GB.UTF-8
    Microphone:  Not set
    Total Hard Disk Space Available:  531366 Mb
    Largest Free Hard Disk Block:  126265 Mb

Installed software:

Recent Failure Reports:

[jpleau]

@coffee-lord Can you show me the line you're using to use your own SDL with CS:GO?

I've tried editing csgo.sh and prepending LD_PRELOAD="/path/to/my/SDL.so" to the launch line but it doesn't seem to have any effect

[sadger]

The non-moving crosshair seems to be only apparent in fullscreen mode, windowed and fullscreen windowed work as expected.

[atomicflag]

LD_PRELOAD="/usr/lib32/libSDL2.so" %command%

@jpleau that goes into launch options in steam. If it still doesn't work make sure you're using 32-bit version of the library. Details on how to compile 32-bit lib can be found in #44. You can check which version csgo is using with

lsof -p `pidof csgo_linux` | grep libSDL

[jpleau]

@coffee-lord Thanks !

I was trying with a library built for amd64, that could also explain a few things

[davidw-valve]

The only change made to affect mouse cursor handling was upgrading to a new libSDL. If the new version of libSDL is causing you problems you can use a different version of libSDL as detailed by @coffee-lord

Testing on my system I see the behavior that @jamezmoran suggests -- that playing in windowed mode or in fullscreen mode at native resolution has no problems with small mouse movements not being recognized. Playing in fullscreen mode at lower resolutions than your native resolution causes this problem. Does anyone else report different behavior to this? I will look into fixing this bug in the meantime you could consider working around this problem by playing at your native resolution (perhaps lowering some other graphics settings to maintain performance).

[AtomiCharge]

Can confirm. I am playing on a 4k screen, downscaled in game. Native seems fine but lower resolutions seem to cause this behaviour. Also different aspect ratios like 4:3 do make a difference as well. It works fine on a native aspect ratio and resolution, but to me and plenty of other people it is difficult to play at such a resolution. Thank you!

[craysiii]

I'm back from rest and here to confirm that non-native resolutions are the cause of this for me at least.

I normally play 1920x1080 stretched because of the UI bug that causes the scoreboard among other elements to be scaled incorrectly. Switching to my native resolution stops the unresponsiveness.

Processor Information:
    Vendor:  GenuineIntel
    CPU Family:  0x6
    CPU Model:  0x3c
    CPU Stepping:  0x3
    CPU Type:  0x0
    Speed:  4400 Mhz
    4 logical processors
    4 physical processors
    HyperThreading:  Unsupported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported

Network Information:
    Network Speed:  

Operating System Version:
    Ubuntu 15.10 (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.2.0-23-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11702000
    X Window Manager:  GNOME Shell
    Steam Runtime Version:  steam-runtime-release_2015-06-12

Video Card:
    Driver:  NVIDIA Corporation GeForce GTX 960/PCIe/SSE2

    Driver Version:  4.5.0 NVIDIA 355.11
    OpenGL Version: 4.5
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x10de
    DeviceID:  0x1401
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  2560 x 1080
    Desktop Resolution: 2560 x 1080
    Primary Display Size: 26.65" x 11.42"  (28.98" diag)
                                            67.7cm x 29.0cm  (73.6cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM: 4096 MB
    Supported MSAA Modes:  2x 4x 8x 16x 

Sound card:
    Audio device: Realtek ALC892

Memory:
    RAM:  7924 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Microphone:  Not set
    Total Hard Disk Space Available:  226095 Mb
    Largest Free Hard Disk Block:  75722 Mb

[jonaz]

I can confim it works on native res and doubling my previous sensitivity.

[davidw-valve]

I am planning on fixing this by making it so mouse handling in fullscreen with a lower resolution than your display's native is handled in exactly the same way as a window of equivalent size would be handled.

So if you think this might be an issue for you please test our the resolution you use in windowed mode and give feedback on if the mouse feels right there.

[ghost]

I can confirm it DOES NOT work on native resolution plus doubling the previous sensitivity. It's garbage, unplayable.

EDIT: I can't find ANY sensitivity that works for me now. There's just something weird about the mouse behaviour after the update. Rollback please.

[craysiii]

@davidw-valve how is it handled in Windows? Whatever works will probably be fine with the community, and that might actually fix the issue people have where their sensitivity settings weren't exactly 2x their old sensitivity.

[davidw-valve]

@3HeadedMonkey: Can you elaborate on the behavior you experience? If you switch to an older version of SDL does it work well for you? What resolution are you running at?

[ghost]

@davidw-valve: I honestly can't explain it, it simply moves too fast or too slow, nothing feels right like before. The game is currently using libSDL2-2.0.so.0. What was the old one? I'm running at 1920x1080 Fullscreen, always have.

EDIT: I think this is the best way I can describe it. I need to increase sensitivity to have the look-around feeling I had before, but by doing that I can no longer do micro-adjustments.

[atomicflag]

@AtomiCharge if it's ingame downscaling that's causing the problem you could try downscaling xorg before you launch the game. Like so

xrandr --output DP-1 --mode 1920x1080

Switch out DP-1 for whatever connector you're using. You can see the list by running xrandr w/o arguments.

[AtomiCharge]

@coffee-lord Can confirm that that fixed the issue but I would have to make some scripts and edit my config for my wm to run that command before CSGO which really shouldn't happen.

EDIT: Downscaling the resolution to less than set by

xrandr --output DP-1 --mode 1920x1080

causes the issue.

[andras-kiss]

Can I get some help making the patched libSDL work? The game won't start for me with the either of the following launch options

LD_PRELOAD=/usr/local/lib/libSDL2-2.0.so.0.4.0 %command% LD_PRELOAD=/home/akiss/SDL2-2.0.4/build/.libs/libSDL2-2.0.so.0.4.0 %command% LD_PRELOAD=/usr/local/lib/libSDL2-2.0.so.0 %command% LD_PRELOAD=/home/akiss/SDL2-2.0.4/build/.libs/libSDL2-2.0.so.0 %command%

I tried

LD_PRELOAD="/usr/lib32/libSDL2.so" %command%

as well, but I don't have any libSDL2.so in /usr/lib32. I get an error message with the previous four launch options from csgo_linux:

SDL_Init(SDL_INIT_VIDEO) failed: No available video device.

Reading the posts, I need to make this work in order to fix the mouse in csgo, which is horrible right now since the new "gloves" update. The symptoms for me: mouse moves slower to the top left direction. It's worse when I lower my mouse refresh rate to 125 from 1000Hz, but still very noticable at 1000Hz, basically unplayable. Can someone help?

[paziman]

Same mouse issue was here. BUT somehow got it back by redoing HW accel on-save-q-off-save-q-on and by changing sensitivity and after back again.

[Toqozz]

I don't know if this is frowned upon, but here's the libSDL I compiled yesterday that is working for me.

https://www.dropbox.com/s/rs8d9k0wbbeappu/libSDL2-2.0.so.0?dl=0

@andras-kiss

[andras-kiss]

Thanks @Toqozz ! I've simply overwritten it in the csgo /bin folder. I see it's version 2.0.3. Have you tried it with 2.0.4? I'm going to give it another go tomorrow. Thank you for the help.

p.s.: What do you mean by frowned upon?

Forgot to mention it works :)!

[Toqozz]

@andras-kiss have not tried 2.0.4, I just downloaded the version linked in the other issue (#44).

As for what I meant by frowned upon, directly linking a file is usually not preferred (compiling is safer), but since the game actually is unplayable I figured that it was needed.

Also, more detailed system information that I didn't include in my first comment. (Fullscreen, 1280x960)

System:    Host: qhost Kernel: 4.3.3-2-ARCH x86_64 (64 bit) Desktop: N/A Distro: Arch Linux
Machine:   System: Gigabyte
           Mobo: Gigabyte model: Z77MX-D3H v: x.x Bios: American Megatrends v: F15 date: 09/17/2012
CPU:       Quad core Intel Core i7-3770 (-MCP-) cache: 8192 KB 
           clock speeds: max: 3900 MHz 1: 1647 MHz 2: 2075 MHz 3: 1624 MHz 4: 1888 MHz
Graphics:  Card: NVIDIA GK104 [GeForce GTX 760]
           Display Server: X.Org 1.18.0 driver: nvidia Resolution: 1920x1080@60.00hz, 2560x1440@144.00hz
           GLX Renderer: GeForce GTX 760/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 358.16
Info:      Processes: 170 Uptime: 1:05 Memory: 1316.8/16012.1MB Client: Shell (fish)

[AtomiCharge]

@Toqozz I tested it out and it seems to be working as expected. At least on my machine. Thank you for doing this :D Now when I switch to a lower resolution than native, mouse input works as expected. Though, I am not sure what VAC will think about this...

[BOHverkill]

It looks like they fixed it in the latest update Thank You! :+1: :smile:

[JoshuaMurphynz]

What like just now? On 9 Jan 2016 13:31, "BOHverkill" notifications@github.com wrote:

I looks like they fixed it in the latest update Thank You! [image: :+1:] [image: :smile:]

— Reply to this email directly or view it on GitHub https://github.com/ValveSoftware/Counter-Strike-Global-Offensive/issues/574#issuecomment-170169087 .

[kvbev]

https://www.reddit.com/r/GlobalOffensive/comments/403xeh/counterstrike_global_offensive_update_for_1816/

[Toqozz]

Now the mouse is off in the server browser! Visible mouse is up-left of actual position.

Not a big deal right now really, but just me?

[JoshuaMurphynz]

Oh jeez nice! Was getting scared that a revert might have to happen On 9 Jan 2016 13:40, "Kvbev" notifications@github.com wrote:

https://www.reddit.com/r/GlobalOffensive/comments/403xeh/counterstrike_global_offensive_update_for_1816/

— Reply to this email directly or view it on GitHub https://github.com/ValveSoftware/Counter-Strike-Global-Offensive/issues/574#issuecomment-170170078 .