I’ve been using Dynamic Sensitivity since buying my Razer mouse and had it calibrated perfectly for almost a year.
I play FPS games at 1600 DPI with low in-game sensitivity. Dynamic Sensitivity lets me keep the slow, accurate sensitivity I want for normal aiming, while increasing to 2.15x when I make a very fast flick, allowing me to quickly turn 180° without having to move my mouse repeatedly across the pad.
This worked perfectly for months.
This was my original curve. 44 counts/ms was enough to keep normal mouse movements below the threshold, so 2.15x would only activate when I made a genuinely fast flick.
Today, something suddenly changed. My normal mouse movements are now reaching ~120 counts/ms. This means my normal aiming movements are now triggering 2.15x.
I’ve had to move the threshold to around 120 counts/ms just to get back to how it behaved before. I’ve only tested this new setting for one match, before I quit.
My main question is: what the **** has changed?
Before today, having my Dynamic Sensitivity curve start increasing at around 44 counts/ms was enough. My normal mouse movements stayed below that, and I would only reach the higher sensitivity when I made a genuinely fast flick, such as when doing a 180°. That was exactly how I wanted it to work.
Now, suddenly, my normal mouse movements are reaching around 120 counts/ms, with some movements reaching 160–200+. Because of that, my old curve no longer works. My normal aiming movements are now triggering the 2.15x sensitivity that was previously reserved for fast flicks.
I've had to move the point where the sensitivity starts increasing to somewhere around 120 counts/ms just to get back to the behaviour I had before.
So what has actually happened here?
If this is something Razer has changed, why has something been changed that fundamentally affects how my mouse behaves without me doing anything? I've spent a very long time calibrating my sensitivity around how this mouse behaved, and now something outside of my control has suddenly changed it.
If this isn't something Razer changed, then what the hell has caused it? What is my mouse doing differently now that makes my normal movements register at around 120 counts/ms when they previously stayed below 44?
And this is the part I really want to understand: what is actually happening with my mouse right now?
Is my mouse genuinely tracking my movements differently? Is there something about the sensor, tracking, polling, firmware, Synapse, or one of the tracking settings that has changed? Or has the way Razer calculates or reports counts/ms somehow changed?
I can compensate for it by changing my Dynamic Sensitivity curve, but that's not really the point. I'm having to recalibrate something that worked perfectly for almost a year, and I don't even know why it suddenly stopped behaving the way it did.
What worries me is that I don't feel like I'm in control of something that directly affects my aim. If this can just happen without me changing anything, what's stopping it from happening again in the future?
For now, I can only try to find a new threshold that works. But before I settle on a new setup, I really want to understand what changed, why it changed, and whether my mouse is now doing something differently that I'm completely unaware of.
Has anyone else using Dynamic Sensitivity noticed it behaving differently recently?