Bojamijams

Is there an App that reports the raw sensitivity currently being used so that we can monitor it and note exactly WHEN it changes?

Any updates on the double shots Corsair?

The new mouse I got after RMAing doesn't have any issues

Thank you for keeping us up to date!

Agreed. Please note the firmware you have now so that if the new firmware DOES break it, you know what to request from Corsair to go back to. And also help us in knowing what to request too

I've heard from a Corsair rep that I filed the ticket with that he has received a mouse with this similar issue and was able to recreate it in Diablo 3 on 1080p @ 60Hz. So it doesn't seem to be FPS related and does seem to be the issue with the hardware itself. Maybe the Pixart sensor itself is faulty. I've also gone back to the Raptor M45 (which CUE doesn't support so I'm not using it either) and I haven't had this issue reoccur, so it doesn't seem to be me, but rather the mouse itself. My RMA has been approved and I'll send my mouse back in. Hopefully I don't get one with the same issue (or worse, the same mouse back). I'll keep checking here for updates and update with my own status once I have something new

Here's another question to all of us who are having this issue? Do you have a high refresh rate monitor or play at 100+ fps?

Mine is straight into a Intel USB 3.0 port on the back of the motherboard.

Let's try to figure out the common thing (other than the M65 RGB Pro) that is causing this for us because random DPI changes on Corsair mice has been an issue since 2012 it seem s. OS: Windows 10 Pro X64 Motherboard: Gigabyte Z170X-Gaming 7 USB Port: Motherboard Rear USB3 Other USB Devices: Steam Controller Receiver Logitech G930 Receiver 2x Saitek Cyborg amBX Gaming Lights USB 3.0 Hub Microsoft Xbox 360 Receiver Vengeance K70 Keyboard

I wonder if yours is more of a bandaid fix in that you had to set the mouse sensitivity to MAX (12000 DPI). So it seems if your sensitivity is 2500 or higher you don't get the issue, but if it's below 2500, then it seems to reset to 2500 (my guess, but that's how it feel when it changes, like it got to around 2500)

It is definitely not the ports since I also only use the rear ports. No hubs, no passthroughs and I've noticed it in Overwatch too (originally in Starcraft 2 but I don't play that anymore) Is everyone here on Windows 10? I wonder if it has something to do with USB Selective Suspend or the Enhanced Power Management (though in my case both are disabled, but maybe that's the problem too?) Corsair approved an RMA for me but seeing here that it didn't fix the issue, I really don't want to go through the hassle for nothing.

Okay I will. Thanks Jay. Try sending the profile to the mouse and not letting CUE start with windows. That's what I had. then run SC2. I also disabled a lot of USB Enhanced Power Management and Selective Suspend settings in the registry though I haven't had a chance to fully test that one.

Did you try saving your settings to the mouse and not running CUE in the background? That is how I noticed my issue (though it could also be the latest firmware). I've since re-enabled running CUE with Windows Start (and thus in background) and will monitor. BTW, Are you running Windows 10?

I am also exhibiting this issue. Happening a lot in Starcraft 2. Does Corsair read this or do we need to post under Support forum?