Bug with sensitivities below 0.4

[blayas]

- Basically any sensitivity selected below 0.4, seems to the crosshairs (sight) not respond to extremely slow mouse movements (fine adjustments), as if stuck and trying to move, it's a problem I already have for years forcing me to use very low dpi (causing pixelskipping in same cases) , since any sensitivity 0.1, 0.2 or 0.3 on the selected options will cause the bug.

Over the years i have tested multiple settings, but nothing was effective, I do not know if somebody else is facing the same problem, if necessary will add some video or information required for the post.

[Geronimo]

Hey, I don't have a solution but I just wanted to thank you because I didn't know that you can "fix" this by raising the sensitivity to 0,4. Until now I was playing with 0,2 and just dealt with the stickiness.

[Mats391]

I am playing with 0.3 and never noticed this. I have no issues aiming.

[PeppeJ]

What's your DPI? Do you use mouse acceleration? Can you change your mouse DPI dynamically (I.E any number instead of a fixed one)?

[blayas]

What's your DPI? Do you use mouse acceleration? Can you change your mouse DPI dynamically (I.E any number instead of a fixed one)?

Currently 500 dpi, acceleration always off, my mause has dynamic dpi change , but as I said, is a bug related to the engine, regardless of configs any sensibilidae below 0.4 causes the bug, so I can add a video to illustrate better. I'm sure this bug plagues many people over the years, without possess knowledge that is related to sensitivity.

[blayas]

500 DPI /0.4

https://youtu.be/P2O89zQ1VIY


800 DPI / 0.2

https://youtu.be/wMQjoWcMqZU

[PeppeJ]

Just tested it myself, yea it's definitely there and only when below 0.4. It's a bit odd as the camera seems to want to move (some pixels flicker, but the crosshair snaps back). It's probably some sort of smoothing that ends up rounding to 0 error and in order to solve those you need game-engine source code access (which devs don't have afaik, cause then this mod wouldn't be so buggy ).

I am playing with 0.3 and never noticed this. I have no issues aiming.

It only happens when you move your mouse just enough distance to turn the camera roughly 1 pixel. I suppose your DPI is too high for you to be able to turn ~1 pixel?

[Murphy]

I've played with .3 sensitivity for years and actually never really noticed this! I'm almost certain it's been like this since vanilla, and I have always just moved to the side ever so slightly (often on an shallow angle) to get that 1-2 pixel adjustment...

Also my vehicle sensitivity is .2, I have NEVER had that issue in a vehicle though.

[blayas]

I've played with .3 sensitivity for years and actually never really noticed this! I'm almost certain it's been like this since vanilla, and I have always just moved to the side ever so slightly (often on an shallow angle) to get that 1-2 pixel adjustment...

Also my vehicle sensitivity is .2, I have NEVER had that issue in a vehicle though.

It is strange because apparently seems to not affect everyone, being a very annoying bug because it prevents the use of higher values of DPI preventing sensitivity reduction.

[Mats391]

It only happens when you move your mouse just enough distance to turn the camera roughly 1 pixel. I suppose your DPI is too high for you to be able to turn ~1 pixel?

Nope, I can adjust pixels just fine. It even is easier when I turn my DPI down.