sensitivity fluctuates unpredictably across various games, unrelated to mouse acceleration settings
sensitivity fluctuates unpredictably across various games, unrelated to mouse acceleration settings
I'm experiencing unpredictable shifts in sensitivity across several games (Division 2, Valorant, CS:GO, Rainbow 6). It often jumps to unusually high levels without any reason, never dropping back. The changes happen suddenly and abruptly—not a gradual increase like acceleration would produce. After a short while it usually returns to normal, but sometimes it lingers longer. Any assistance would be greatly appreciated. These issues occur on different devices—mouse acceleration is turned off. My main mouse includes a DPI button, but that doesn't resolve the problem. The sensitivity also fluctuates when pressing buttons, even with no DPI settings enabled in the game or Windows. I've tested this with various mice: Razer Viper Ultimate, Logitech G Pro X, Logitech G Pro Wireless, Logitech MX Master 2S, and Artisan FX models. All of them show the same behavior on the same drives. I've tried reinstalling the games, switching drives, updating drivers in both wired and wireless modes, adjusting DPI settings, changing polling rates, uninstalling mouse software (like Razer Synapse), restarting the game or the computer. A video demonstrating this issue is available here: https://youtu.be/NW52BeePUyc. My current sensitivity is 0.2 at 800DPI, meaning a full mousepad should rotate about 180 degrees—this isn't the typical range seen in the clip due to the bug.
System details:
- Windows 10 version: 19044.1645
- Processor: i7-8700K
- RAM: 16GB DDR4
- Storage: 2666GB NVMe, 2080TB SSD, 512GB NVMe, 500GB NVMe
- Case: Samsung 512GB NVMe Pro WD Black
- Power: 850W Thermaltake 90 Plus Gold
The problem remains the same across five mice and four different mousepads, indicating it isn't related to this specific case.
Well if the mice and mouse pads shift but the core issue remains, it likely points to the part that stays constant—like the operating system and background startup services. As an odd situation it pushes for a malware scan, though it might turn up clean. It could be a wait state activated somewhere. I’d consider a system refresh to observe changes, though it probably won’t help much. A refresh alters many OS files, making it hard to pinpoint the original fault. If it fails, it’s unlikely an OS corruption is the cause. Testing in safe mode helps verify if the problem stems from drivers. Not clear what else it does. It might not be resolvable that way. One simple method to distinguish hardware from software is switching to a different OS. If you have a blank, large USB drive, installing a Linux liveCD and booting from there can isolate the issue—though it could present its own challenges. Running offline might reveal whether the fix occurs without external connections. If it works offline, the problem likely involves the network card or internet connection. Anyway, here are a few ideas I have.