Forum Discussion

PsyhiX69's avatar
PsyhiX69
Seasoned Ace
4 years ago
Solved

Can some one explain how my mouse is slower when ADS in game?

Why do my mouse is slower when I have enemy on my crosshair?

I have spent many hours in fire range and have never encountered this. Yet many times when I have enemy on my crosshair it slows my mouse down.

This is not an issue with fps, nor with connection. It is purely something in the game engine. This basically makes me miss my shots. 

Like I said I have never encounter this in fire range. Also this only happens for some enemies. It's like some lag but applied to mouse movement?

My cpu staty low and cool the same goes for gpu. I have locked fps to 138 so I know when game feels laggy.

What is going on? I am losing fights because of that!

  • Yesterday I saw that my Windows 11 updated "Razer Inc - HIDClass" drivers and since then I haven't encountered the issue... I think it has been fixed.

    Screenshot:

3 Replies

  • There are two sets of settings.  One set is when you ADS and the other is when you are not ADS.  You can adjust either setting independent of the other.

  • PsyhiX69's avatar
    PsyhiX69
    Seasoned Ace
    4 years ago

    I am aware of that there are settings that control sensitivity for ADS and normal movement separately.

    I am talking about rare occurrence where when I am ADS at enemy (even around them) my mouse movement is slowed down sometimes like the game has issues processing inputs and what is going on at the same time.

    It happens sometimes only and only for some enemies. Usually it's fine. Meaning the mouse feels exactly like at fire range.

    But sometimes when this "bug" hits I am unable to track enemy with the same precision. Like the sensitivity drops by 10-30% or something. The cursor feels like it drags. 

  • PsyhiX69's avatar
    PsyhiX69
    Seasoned Ace
    4 years ago

    Yesterday I saw that my Windows 11 updated "Razer Inc - HIDClass" drivers and since then I haven't encountered the issue... I think it has been fixed.

    Screenshot: