Forum

Back when 2.8.5 was still around, there was a setting in your User.ini you could change to make your mouse movement more precise. You would change:

MouseX=Count bXAxis | Axis aMouseX Speed=2.0
MouseY=Count bYAxis | Axis aMouseY Speed=2.0

Into:

MouseX=Count bXAxis | Axis aMouseX Speed=1.0
MouseY=Count bYAxis | Axis aMouseY Speed=1.0

Currently, when you move your mouse in any direction, the game registers mouse movement in multiples of 2 pixels. This setting makes the game register movement pixel by pixel. This means that you have far more precision when aiming, especially for long-range, more control over recoil, and in general, the game feels a lot smoother. Unfortunately this setting doesn't work for 2.5 Assist, and changing it results you getting kicked for CVAR violations.

I suggest allowing this change in the next 2.5 update. After all, it doesn't make sense why 2 pixel mouse movement should be the default setting when it is necessarily more imprecise. I would even suggest that pixel-by-pixel movement should be the new default setting if it didn't throw off people's game so much (you have to increase mouse sensitivity to compensate for the decreased speed, and your mouse just "feels" different). So I think it should be a choice. Thoughts?

Nice, I thought so too.

one small thing though: Changing this to 1 pixel will also mean you need to double your mouse sensitivity in game in order to have the same speed.

For example my mouse sensitivity now is 0.41, I need to change it to 0.82 if this is changed.

Otherwise you will get many people being surprised .

I've changed it and  didn't get kicked so far.

MouseX=Count bXAxis | Axis aMouseX Speed=4.0
MouseY=Count bYAxis | Axis aMouseY Speed=4.0

[Engine.PlayerInput]
bInvertMouse=False
MouseSmoothingMode=1
MouseSmoothingStrength=0.000000
MouseSensitivity=1.750000
MouseSamplingTime=0.008253
MouseAccelThreshold=0.000000
DoubleClickTime=0.250000

NP

MouseX=Count bXAxis | Axis aMouseX Speed=2.0
MouseY=Count bYAxis | Axis aMouseY Speed=2.0

[Engine.PlayerInput]
bInvertMouse=False
MouseSmoothingMode=0
MouseSmoothingStrength=0.300000
MouseSensitivity=0.420000
MouseSamplingTime=0.008333
MouseAccelThreshold=0.000000
DoubleClickTime=0.000000

What does the mousesmoothingstrength and samplingtime do? Is it better to put it on 0?

MouseX=Count bXAxis | Axis aMouseX Speed=2.0
MouseY=Count bYAxis | Axis aMouseY Speed=2.0

[Engine.PlayerInput]
bInvertMouse=False
MouseSmoothingMode=0
MouseSmoothingStrength=0.300000
MouseSensitivity=0.420000
MouseSamplingTime=0.008333
MouseAccelThreshold=0.000000
DoubleClickTime=0.000000

What does the mousesmoothingstrength and samplingtime do? Is it better to put it on 0?

MouseSmoothingMode:

0 is unticked in your in-game settings
1 is ticked in your in-game settings

The smoothing strength gives nothing.

Sampling time is possible to set in mouse driver settings. In ini it has no difference with value do you set. Whatever, it gives nothing.

I'm more interested in axis speed, which was changed after first update half year ago. It was changed to default unchangable value 1, which makes the game hard playable for my mouse and DPI value (sensitivity 0.25 in game settings was too high, I used to play with axis speed 2 and sens 0,65.

It's hard to play with high DPI settings, if you can not set the lower sens than you actually have (if you have the lowest one). LOL.

You're changing the sampling rate not the hz.
The polling rate of 125Hz are 0.008 seconds.
The polling rate of 500Hz are 0.002 seconds.
The polling rate of 1000Hz are 0.001 seconds.

can we adjust these values now?