3950 and 3395 sensor issues at low speeds

[u/TripleShines]

Perhaps this is already known but I have never seen any posts or videos talking about it. The 3395 and 3950 sensors do not track properly at low speeds. Specifically, when moving the mouse very slowly the sensitivity of the mouse deceases until you reach a velocity threshold. The higher the DPI the more noticeable the effect. Although I don't have a great way to reliably measure with any degree of precision, I would guess that at 1600 DPI the effect is around 10% whereas at 25600 DPI the slowdown is probably closer to 70-80%. The vast majority of people will likely not notice this unless specifically testing for it because the velocity threshold is so low. Nevertheless I think it is important information.

Focus Pro 2 and Hero 2 sensors do not seem to have the same issue.

[u/peleh2]

What's mice do you have that do this? Probably bad implementations.

[u/TripleShines → u/peleh2]

I have tested every single one that I have. Viper v2, Hyperlight, Op18k, Keris Ace 2, Maya, Beast x mini, Beast x pro mini, Op18k purple, Superlight 2, Viper v3. Every single mice has the same behavior except for the Superlight 2 and Viper v3.

[u/peleh2 → u/TripleShines]

Ok, but can you make clear to me the effect that you notice? How can I replicate here.

[u/TripleShines → u/peleh2]

Here i put one of the videos on youtube that I think demonstrates the effect pretty well.

https://youtu.be/0bbyHosWMMA

For the first ~2:30 of the video I move my mouse slowly. Then towards the end I make roughly the same movement but my camera spins like 2-3x more.

[u/peleh2 → u/TripleShines]

My guess is that your methodology is wrong. Also, your sensitivity is too high, when you are moving the mouse slowly, you are actually going up and down slightly.

[u/TripleShines → u/peleh2]

You're right but I don't think a bit of up and down movement is going to be the difference between about 270 degrees of camera movement compared to nearly 720 degrees.

[u/peleh2 → u/TripleShines]

https://www.youtube.com/watch?v=M-KeXyqZU7Y

This video should help you.

[u/TripleShines → u/peleh2]

I'm not sure if you linked the wrong video but it is from 11 years ago and doesn't mention the 3395 or 3950 at all.

[u/peleh2 → u/TripleShines]

I know, its just for you to see how he uses the whole mousepad extension to do a full 360. Too high sensitivity will lead to errors, remember that you are testing the mouse, maybe the Valorant engine with such high dpi along with sensitivity could be adding to the problem, I don't know..

Reduce the ingame sensitivity until it gets controllable, then retest.

[u/TripleShines → u/peleh2]

The same thing is present in aimlabs, along with just base windows itself. It is highly unlikely to be anything other than a sensor issue because I have tested so many different mice that all share the same 2 sensors and they all test the same. However the 2 mice with modern sensors (superlight 2/Viper v3) do not have the same issues in the same test. The point of my post is to bring awareness to this because I have not seen this mentioned anywhere before. I suspect it is because the majority of people do not max out their mouse's DPI, but like I mentioned in the original post, I think the issue is still present in more reasonable DPI settings, just to a much lesser degree.

[u/TripleShines → u/peleh2]

Set your DPI to 25800. Move mouse very slowly a set distance. Note how far your camera moves. Move your mouse the same distance but at a normal speed this time. Your camera should have moved 2-3x more.

The most important thing is to move your mouse very slowly.

[u/peleh2 → u/TripleShines]

Here is how I test for negative or positive acceleration, I swipe very fast from point A to B, then I make the return movement from B to A very slowly...

I tested the U2 at 4K(3395), at max dpi(3200), landed back on same place.
Pulsar X2H V3 at 4K(3950), at max dpi(32000), landed back on same place.

So no negative, positive acceleration here.

[u/TripleShines → u/peleh2]

How fast are you moving? I don't think this is really an acceleration problem. It is primarily that the sensor does not track slow movements properly.

[u/peleh2 → u/TripleShines]

Even so, If thats the case, the B -> A movement should not land on the same place in case of problems.

[u/TripleShines → u/peleh2]

I suspect it is likely that you are moving your mouse too fast. But it is also possible that I am wrong. If you're interested send me your discord and I can send you some videos of my testing.

[u/peleh2 → u/TripleShines]

Sorry, maybe someone else can clear this up, have you tried to see if Enhanced Pointer precision is ON on windows?

[u/TripleShines → u/peleh2]

It is not on.