Hi guys. I've been trying many things trying to narrow down the possibilities for the cause of the double-click issue in the M65 RGB mouse. I've been experiencing the same issue obviously. So I've tried many things and have been using the following site for subsequent click testing:
http://ift.tt/1r2KAZ9
Testing methodology: Click at a steady pace counting out loud and watch the counter. If it jumps, the problem still exists. Reset the counter by clicking clear all items.
I've tried the following things trying to narrow down possible causes and testing. All of the following failed to resolve the issue:
Tried different USB ports on different buses.
Tried switching mouse to USB 3.0 interface.
Tried turning off CUE (Corsair Utility Engine)
Even tried setting CUE to not load with windows, turning it off and then rebooting the computer.
Tried changing the polling rate
Tried disconnecting and turning off Corsair USB Vengeance Headset and turning off software
Tried turning off other running applications one by one to see if any software running on my computer could be isolated as a possible cause. None made any impact on fault.
Tried disconnecting all other USB devices that could be causing a conflict one by one.
None of these made any discernible difference.
Next I disconnected the mouse from my computer and connected it to my laptop (Which is running Linux Netrunner) and went to the web and continued to test. After several hundred clicks, I could not reproduce the issue on the laptop. So I disconnected it from the laptop and plugged in back on my main computer and tested again. Problem was still there on my main computer.
This means the issue is not likely to be with the mouse itself, but more likely with the CUE software and/or drivers or possible something more specific to Windows (I'm running Windows 7 64bit Ultimate on my main computer).
So I checked the device manager on my computer to ascertain what's currently installed for the mouse on my main computer. Here is the device map:
Next I uninstalled the CUE software. Bear in mind, that even if you have the CUE turned off on your computer and set to not autorun with Windows, there is still a driver component that is installed on your computer for the mouse (installed with CUE) that the computer uses instead of the driver windows automatically installs and uses when you plug the mouse in for the first and before you install the CUE software. It is important to bear that in mind to understand what happens next and how that may have an impact the results of tests following the uninstall of the CUE software.) During the uninstall process I took note of it uninstalling the drivers for the mouse. Then I checked the install directory to ensure that the CUE software was fully removed from the computer. For the record, the default directory the CUE software and drivers is the following:
C:\Program Files (x86)\Corsair\Corsair Utility Engine
Once the CUE was fully uninstalled I rebooted the computer again, just to be on the safe side. On boot up I checked the device manager again, and this is the device map I got back:
In case it's not apparant, here is an edited screenshot of the before screenshot to highlight the device manager entries that are no longer present after the uninstallation of the CUE software and drivers.
So I went back to the click counting site and retested. After hundreds of clicks, I have not been able to reproduce the issue. As a result, this seems to have resolved the issue on my mouse.
Here's where things get a little interesting, but it does seem logical given that this issue didn't appear initially until about a couple days "after" I originally set up my mouse.
So I reinstalled the CUE software, rebooted again and retested. I have not as yet, been able to reproduce the issue. But I have gotten some weird results from the CUE software. All of a sudden, when I went to polling speed, it was at 125hz and claimed a mouse malfunction. When I set the mouse back to the correct 1000hz, it refreshed and it no longer claims there's a malfunction. I went to the profile page and changed the profile to the Hardware profile, but now all of a sudden, it's not listing a set setting for right click. And now for that reason, I couldn't right-click. So I reset the hardware profile to reset the default settings. Then I set my custom settings back and saved it to the mouse. Went back to the click testing site and tested again. Still can't reproduce the issue after hundreds of clicks.
Now given, that this issue doesn't seem to surface until a couple days after setup of the mouse through the CUE. And simply reapplying your settings to the mouse seems to have no affect. But completely uninstalling and reinstalling the CUE software, and then resetting the mouse and re-applying your custom settings does seem to fix the issue. However, and this is the big however. I can not guarantee that the issue will not resurface a couple days of use later if you keep the CUE software installed. The only way to know for sure, is to test thoroughly. And that's why I'm here. The more people who can test, the better.
If you like the CUE software and wish to continue to use it, but are getting the double-click on left issue. Then try the following steps.
1: Fully uninstall the CUE (Corsair Utility Engine) software through Control Panel -> Progams and Features
2: After uninstallation, check to make sure that the CUE software folder was actually removed from the computer. Default Path = C:\Program Files (x86)\Corsair\Corsair Utility Engine
3: Reboot your computer
4: Reinstall the CUE software. Download the latest version that was released over Christmas if you haven't already.
5: After installation, start up the CUE software and in the Device tab of the Settings Section, check to make sure the polling option is set to the correct setting. Default is 1000hz.
6: In the Profile tab, change default listing to HwProfile1 and check to make sure everything is set correctly. If it's not (such as the issue I had where right click's setting mysteriously disappeared), then left click the 3 lines icon next to HwProfile1 and click reset device to defaults. Once this is done, then reapply your preferred settings. If you can find no issues with the HwProfile1, you might be able to skip this step. It's your call of the level of testing you end up wanting to do.
If you are unsure what hardware profile I speak of, you can see what I'm referring to in the following screenshot. It's one of the selectable profiles:
7: In the Profile tab, if you prefer to use software profile settings, then do the same as described in step 6, but also do it for your set software profiles. You may actually be able to skip this step, I don't know.
8: Test using the click counting site I highlighted here. If your issue is gone, great, but please post an initial post here saying as much. Then test over the next week through every day use. If the problem stay gone, great. If it comes back, bad luck. In either case, please report your week results here as well, as that is useful data for helping narrow down the cause of this issue.
http://ift.tt/1r2KAZ9
If you don't care for the CUE software and would rather just use the mouse with your profile settings permanently on the mouse and you've already properly set your hardware profile the way you like it. Then follow these steps.
1: Fully uninstall the CUE (Corsair Utility Engine) software through Control Panel -> Progams and Features
2: After uninstallation, check to make sure that the CUE software folder was actually removed from the computer. Default Path = C:\Program Files (x86)\Corsair\Corsair Utility Engine
3: Reboot your computer
4: Test using the click counting site I highlighted here. If your issue is gone, great, but please post an initial post here saying as much. Then test over the next week through every day use. If the problem stay gone, great. If it comes back, bad luck. In either case, please report your week results here as well, as that is useful data for helping narrow down the cause of this issue.
Note: In this scenario you will be testing using only the Windows default installed drivers. Not the corsair specific drivers installed by the CUE software.
http://ift.tt/1r2KAZ9
OK guys. This is the best I can do for the moment. Until I can do more testing, there's not much more information I can provide at this point. But if this helps all of you and helps Corsair with a tangible direction to look at for actually fixing this issue, then that would just be great for everyone. Looking forward to seeing all of your results. I hope this helps and good luck
http://ift.tt/1r2KAZ9
Testing methodology: Click at a steady pace counting out loud and watch the counter. If it jumps, the problem still exists. Reset the counter by clicking clear all items.
I've tried the following things trying to narrow down possible causes and testing. All of the following failed to resolve the issue:
Tried different USB ports on different buses.
Tried switching mouse to USB 3.0 interface.
Tried turning off CUE (Corsair Utility Engine)
Even tried setting CUE to not load with windows, turning it off and then rebooting the computer.
Tried changing the polling rate
Tried disconnecting and turning off Corsair USB Vengeance Headset and turning off software
Tried turning off other running applications one by one to see if any software running on my computer could be isolated as a possible cause. None made any impact on fault.
Tried disconnecting all other USB devices that could be causing a conflict one by one.
None of these made any discernible difference.
Next I disconnected the mouse from my computer and connected it to my laptop (Which is running Linux Netrunner) and went to the web and continued to test. After several hundred clicks, I could not reproduce the issue on the laptop. So I disconnected it from the laptop and plugged in back on my main computer and tested again. Problem was still there on my main computer.
This means the issue is not likely to be with the mouse itself, but more likely with the CUE software and/or drivers or possible something more specific to Windows (I'm running Windows 7 64bit Ultimate on my main computer).
So I checked the device manager on my computer to ascertain what's currently installed for the mouse on my main computer. Here is the device map:
Next I uninstalled the CUE software. Bear in mind, that even if you have the CUE turned off on your computer and set to not autorun with Windows, there is still a driver component that is installed on your computer for the mouse (installed with CUE) that the computer uses instead of the driver windows automatically installs and uses when you plug the mouse in for the first and before you install the CUE software. It is important to bear that in mind to understand what happens next and how that may have an impact the results of tests following the uninstall of the CUE software.) During the uninstall process I took note of it uninstalling the drivers for the mouse. Then I checked the install directory to ensure that the CUE software was fully removed from the computer. For the record, the default directory the CUE software and drivers is the following:
C:\Program Files (x86)\Corsair\Corsair Utility Engine
Once the CUE was fully uninstalled I rebooted the computer again, just to be on the safe side. On boot up I checked the device manager again, and this is the device map I got back:
In case it's not apparant, here is an edited screenshot of the before screenshot to highlight the device manager entries that are no longer present after the uninstallation of the CUE software and drivers.
So I went back to the click counting site and retested. After hundreds of clicks, I have not been able to reproduce the issue. As a result, this seems to have resolved the issue on my mouse.
Here's where things get a little interesting, but it does seem logical given that this issue didn't appear initially until about a couple days "after" I originally set up my mouse.
So I reinstalled the CUE software, rebooted again and retested. I have not as yet, been able to reproduce the issue. But I have gotten some weird results from the CUE software. All of a sudden, when I went to polling speed, it was at 125hz and claimed a mouse malfunction. When I set the mouse back to the correct 1000hz, it refreshed and it no longer claims there's a malfunction. I went to the profile page and changed the profile to the Hardware profile, but now all of a sudden, it's not listing a set setting for right click. And now for that reason, I couldn't right-click. So I reset the hardware profile to reset the default settings. Then I set my custom settings back and saved it to the mouse. Went back to the click testing site and tested again. Still can't reproduce the issue after hundreds of clicks.
Now given, that this issue doesn't seem to surface until a couple days after setup of the mouse through the CUE. And simply reapplying your settings to the mouse seems to have no affect. But completely uninstalling and reinstalling the CUE software, and then resetting the mouse and re-applying your custom settings does seem to fix the issue. However, and this is the big however. I can not guarantee that the issue will not resurface a couple days of use later if you keep the CUE software installed. The only way to know for sure, is to test thoroughly. And that's why I'm here. The more people who can test, the better.
If you like the CUE software and wish to continue to use it, but are getting the double-click on left issue. Then try the following steps.
1: Fully uninstall the CUE (Corsair Utility Engine) software through Control Panel -> Progams and Features
2: After uninstallation, check to make sure that the CUE software folder was actually removed from the computer. Default Path = C:\Program Files (x86)\Corsair\Corsair Utility Engine
3: Reboot your computer
4: Reinstall the CUE software. Download the latest version that was released over Christmas if you haven't already.
5: After installation, start up the CUE software and in the Device tab of the Settings Section, check to make sure the polling option is set to the correct setting. Default is 1000hz.
6: In the Profile tab, change default listing to HwProfile1 and check to make sure everything is set correctly. If it's not (such as the issue I had where right click's setting mysteriously disappeared), then left click the 3 lines icon next to HwProfile1 and click reset device to defaults. Once this is done, then reapply your preferred settings. If you can find no issues with the HwProfile1, you might be able to skip this step. It's your call of the level of testing you end up wanting to do.
If you are unsure what hardware profile I speak of, you can see what I'm referring to in the following screenshot. It's one of the selectable profiles:
7: In the Profile tab, if you prefer to use software profile settings, then do the same as described in step 6, but also do it for your set software profiles. You may actually be able to skip this step, I don't know.
8: Test using the click counting site I highlighted here. If your issue is gone, great, but please post an initial post here saying as much. Then test over the next week through every day use. If the problem stay gone, great. If it comes back, bad luck. In either case, please report your week results here as well, as that is useful data for helping narrow down the cause of this issue.
http://ift.tt/1r2KAZ9
If you don't care for the CUE software and would rather just use the mouse with your profile settings permanently on the mouse and you've already properly set your hardware profile the way you like it. Then follow these steps.
1: Fully uninstall the CUE (Corsair Utility Engine) software through Control Panel -> Progams and Features
2: After uninstallation, check to make sure that the CUE software folder was actually removed from the computer. Default Path = C:\Program Files (x86)\Corsair\Corsair Utility Engine
3: Reboot your computer
4: Test using the click counting site I highlighted here. If your issue is gone, great, but please post an initial post here saying as much. Then test over the next week through every day use. If the problem stay gone, great. If it comes back, bad luck. In either case, please report your week results here as well, as that is useful data for helping narrow down the cause of this issue.
Note: In this scenario you will be testing using only the Windows default installed drivers. Not the corsair specific drivers installed by the CUE software.
http://ift.tt/1r2KAZ9
OK guys. This is the best I can do for the moment. Until I can do more testing, there's not much more information I can provide at this point. But if this helps all of you and helps Corsair with a tangible direction to look at for actually fixing this issue, then that would just be great for everyone. Looking forward to seeing all of your results. I hope this helps and good luck
I am pretty sure i fixed my left button double clicking issue.
RépondreSupprimerAnd i hope this can help someone else too.
I opened up the mouse to potentially replacing the micro switch because i thought that to be the culprit. But none of the other similar micro switches had this fault, so after further inspection i found that the little white nylon plastic pieces that makes contact with the switches, did not look exactly the same.
i could see they were designed to be smooth, making a sliding motion over the switch contact when one actuates the button.
But the white nylon plastic in the left click button had a tiny divot in it, causing the action to be bumpy and therefore double clicking.
I carefully smoothed out the plastic with a nail file, reassembled the mouse, and i have not had any involuntary double clicking since.