Need help tracking mouse resolution issue

[Furtrapper]

Hi all

I'm hoping someone here can help point me in the right direction for tracking down a problem I'm having.

Basically, my mouse seems to work at a strange "stepped" resolution in a number of games. I'm pretty sure it's not lag, and it's definitely not sensitivity. It's more that I have to move the mouse a certain distance before it picks up the input. If I move the mouse really slowly to one side, it will do nothing for a while, and then suddenly the camera will turn a few degrees. I am unable to have fine grained control of my camera (in an FPS). It seems to be stuck at set angle increments. This makes aiming at range a bit of a nightmare as I often have to strafe to get the reticule over a target as mouse alone will end up aiming either side.

I have noticed the issue in a number of Unity games (I'm actually a game developer who uses Unity, so I've done a lot of digging there but found nothing), and another game that is affected is Payday 2. Games like CS:GO and Doom work fine. The mouse I use is a Razer Deathadder Chroma so should be a good quality mouse, and I also use an Nvidia 1070, so framerate isn't really an issue in most games (I get 120fps in Payday 2).

I have tried messing with the Windows mouse settings to disable enhanced precision. I have tried with and without vsync and gsync in games, and I have tried reinstalling mouse drivers.

The only possible lead I've come up with is I know that 1 game I have the issue with runs in borderless windowed mode instead of exclusive fullscreen.

Does anybody have any input on what could be causing this? I love FPS games, so this is really getting on my nerves and I've hit a dead end looking for a solution.

 

Thanks

Chris

[Drimzi]

Edited January 28, 2018 by Drimzi

[Furtrapper]

Hey, thanks for your help.

I've done as suggested (and then some), having set the mouse sensitivity and polling rate to the max (10k dpi, 1000Hz)  in the Razer software and reduced the windows cursor speed until it felt right in windows (3 in my case too, QHD).

That does seem to have made quite a difference in the games I was having a problem with, so thanks. It does still seem weird that it was having those issues before though. Previously, my windows speed was on 6, with the razer polling rate at max, but sensitivity about on the center (4000dpi). As mentioned, some games were absolutely fine before and I'll have to go and tweak their settings now to match the new sensitivity (no biggy).

Regarding resolution, in investigating the Unity side (where a number of games have issues for me) it seemed like that should only affect things in certain situations. Unity input has 3 main ways to get mouse input: 

1. Input.mousePosition - This gets the cursor position within the window space. Used for RTS or RPG games that display a cursor, for example, and would definitely be affected by resolution.
2. Input.GetAxisRaw () - This should directly get input from the mouse, without any interference from Windows. Not frame rate dependent.
3. Input.GetAxis () - This is as with raw, but with added smoothing configured in the project settings

It was my understanding that only the first is affected by resolution, and that the game would just multiply the mouse's distance moved by some angle and then do whatever smoothing / acceleration it wanted to that. I may be totally wrong, though, and the input is still measured in whole pixels. That seems a bit nuts though.

[Drimzi]

Edited January 28, 2018 by Drimzi

[DNAMTE]

Sounds like a mouse driver issue to me. 4000dpi is more than enough for smooth aiming. IMO so is 400dpi. I seem to recall a similar issue with an OLD razer mouse I had... Razer Diamondback I think... It had a driver issue which resulted in very 'stuttered' movement. I bought a new mouse and the problem was gone. Later I fixed the issue with a driver update.

 

Something to think about.