Issue with sensitivity in cs2 | Razer Insider
Skip to main content
Question

Issue with sensitivity in cs2

  • October 20, 2024
  • 6 replies
  • 163 views

clxvded

I currently have the Viper V3 Pro and this issue started a week ago in a random cs2 match. My sensitivity was drastically slower in game and when I tried to change my sensitivity in game and change it back nothing changed. This first happened a week ago and I restarted my pc and the issue fixed however it happened again 2 days ago when I tried to play faceit and had to restart my game to run their anti cheat. Since then it occurs randomly and the only way to fix it seems to be to close the razer apps in my system tray which only fixes it sometimes and completely reinstalling the razer software. This usually fixes it but reinstalling the software every time this issue happens is very inefficient and annoying. 

Did this topic help you find an answer to your question?

6 Replies

FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7358 replies
  • October 21, 2024

Hi,

Do you have the latest firmware for your mouse? https://mysupport.razer.com/app/answers/detail/a_id/14169


Hi I can confirm this is still a problem


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7358 replies
  • May 12, 2025

Do you use auto switch polling rate? If yes try to disable it and test.


FiszPL wrote:

Do you use auto switch polling rate? If yes try to disable it and test.

Hi. yes, i originally had a profile for CS2 that swapped when i changed games. I disabled switching on launch and tried playing with polling rate, DPI, and sensitivity and still had this problem. I also tried completely removing Synapse and restarting and simply closing out of it to no avail. Once i load FACEIT anticheat and launch the game it takes effect. Weird slight mouse acceleration or “deadzone” and about a 70% lower percieved sensitivity, sometimes this happens right away in local practice and sometimes it happens when a competitive match server is joined. I have a feeling faceit is intentionally blocking the driver or is heavily processing the input for some reason.



Ive figured this out. For whatever reason, when the faceit client itself is left open this happens(not the anti cheat). To fix it, simply queue with it, join the match, and then close it after you join and play the game. Playing with faceit client settings does not resolve, disabling the suspected overlay doesn't fix it either.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings