galvanash

I don't know. I saw a thread about this same problem with a Raptor M45 though: http://forum.corsair.com/v3/showthread.php?t=127830 My mouse is an M65 Pro RGB though.

My monitor is 60mhz, but I have the framerate cap turned off in Overwatch so my framerate is about 250 fps or so.

This is how I have mine set up now in CUE: DPI Assignments (1-5): 400, 6000, 8000, 10000, 12000 Sniper DPI: 400 Pointer Speed: 15 (4 notches from fastest) Enhanced Pointer Precision and Angle Snap: Disabled When setup like this, and with the mouse sensitivity in Overwatch set to 1, there is never any random sensitivity changes. I usually play on DPI setting 2 or 3, and I use 1 (or just use the snipper button) to navigate the menus and whatnot. I just played like 4 hours straight so it definitely works. If you reduce the pointer speed, you'll have to increase the DPI, and vice versa. At 15, 6000-8000 DPI seems best for me, but Im sure it will be different for others.

I dont know for sure, but I have tried 2 different brand new M65 Pros and both behaved exactly the same in Overwatch (random sensitivity increases). What I would like to know is if ANYONE with the M65 does NOT have this problem with Overwatch. If it works without jacking with the in game mouse sensivity for anyone, then we need to figure out whats different with their system then ours (the ones experiencing the problem).

Possible. I would just recommend that anyone having this problem with Overwatch specifically try setting the in game sensitivity to 1 and then work from there. The issue seems to be triggered by that setting, at least on my rig. Ill play with it some more to get my settings dialed in, but Im just happy it is working now. Even the DPI adjustment and sniper button all work flawlessly now, the only issue is with sensitivity set to 1 in overwatch the DPI and/or sensitivity in CUE have to be cranked up really high to compensate for it. I suspect the in game sensitivity is some kind of multiplier, and setting it to 1 just turns it off. Whatever it does when it is on, it makes the mouse go bananas. ps. It is definitely not resetting to 2500 now that I think about it... At 2500, with the in game sensitivity set to 1, the mouse barely moves. It is odd though, because you would think at 12000 it would be ridiculously twitchy, but it isn't - at all. My problem now is actually getting it to respond faster - it is always _slightly_ too slow for me. I suspect you are right though, this doesn't fix it - it just masks the underlying problem somehow.

I think I have it now... So I realize now I had also changed up some in game settings in Overwatch at the same time I switched ports. I went back to my case ports and everything was still working... I figured out the setting - definitively I think. If you set the mouse sensitivity in Overwatch (not in CUE or in Windows control panel - in the game itself) to 1 (lowest setting), the problem disappears. If you set it to ANYTHING else it starts behaving erratically again. I tried it multiple times, back and forth - it is definitely this setting cause the issue. Catch is you have to set your in game DPI really really high to compensate. I was playing with it at 12000 and it was almost perfect, never glitched at all. But the sensitivity setting in Overwatch only kicks in when in a game, so you'll have to dial it down on the mouse when using the in-game menus and whatnot cause you can barely see the cursor move it's so twitchy :) Anyway, this is certainly not a perfect solution, but it works. I suspect the problem with cs go some people reported is similar. It's not the mouse itself, it is how it interacts with these game's internal mouse sensitivity settings.

For the benefit of others (skip to possible cause/solution at the end)... I have a M65 Pro RGB, got it about 2 weeks ago. Latest CUE software, latest firmware. I was having the exact issue described in this thread - sensitivity would randomly increase for no reason. The only thing that would correct it was to cycle the DPI settings up and down to restore it, or just unplug/replug. This happened anywhere from every 5 minutes or so to sometime 20 or 30 minutes. No real pattern other than it always seemed to happen when I was making very aggressive movements with the mouse. I do not know if this happened with all games, but it definitely happened with Overwatch. I was basically using default CUE settings. 1000 mhz polling rate, and mouse set at 800 DPI as default. Windows mouse pointer setting was 6, with acceleration turned off. I tried everything mentioned here and other places, saved profile to mouse and turned off CUE. Set all DPI settings to same value. etc. etc. Nothing worked. I returned mouse last Friday and got a replacement (same model) - just to see if it was a hardware issue. The new mouse did exactly the same thing. So backstory done. On to solution... I use a K65 keyboard with the pass through USB, i.e. the keyboard has 2 USB connectors. The mouse is plugged into the keyboard and the connection passes through to the 2nd USB connector. I had both USB connectors plugged into my case's front USB ports. As a last stab at trying anything that might work (I really like this mouse otherwise) I tried plugging the 2 USB connectors into my motherboards rear USB ports... Boom. Problem gone. Hypothesis: This problem is likely due to either poor connection on some USB ports, shoddy wiring on some cases between the case supplied connectors and the motherboard USB headers, or simply having 3 separate jacks between the mouse and the MB (one on the keyboard, one on the case, and one at the MB header). Combine that with the (relatively) high data load the mouse puts on the USB port, and you get occasional USB noise/dropout/crosstalk/whatever and the mouse goes wonky... Solution: Try plugging DIRECTLY into your motherboards rear USB jacks. No hubs, no case jacks, straight into the MB. If one port doesn't work, try another. Mine works like this using the pass-through USB on the keyboard, but if all else fails try plugging the mouse straight into the MB itself. You'll probably get it to behave doing one of these. Hope this helps someone.