Search the Community
Showing results for tags 'middle mouse button'.
Hello! As many people have, i am now experiencing a problem with my middle mouse button not working. The common answer to this issue is to rapidly click the button(and/or blow it with compressed air), to loosen any dirt that might be stuck in there, however this time it hasn't worked. So i've been trying to remap the middle mouse button to m4 or m5, but it doesn't seem to be possible with the icue, since i can't click the middle mouse to use it as an action. I've been fiddling around with AutoHotkey, and used this line: MButton::XButton1 - Doesn't work either (which may just be because idk what i'm doing). Does anybody here have an idea as to how i can remap this key? What i'm specifically trying to achieve, is to be able to open a window in a new tab (in one click), so maybe there's some way to change the keybinds for chrome specifically? Tyvm
I'm on my second Scimitar Pro RGB mouse and, after RMAing the first one in September 2018 for the same issue. The scroll wheel click now works perhaps 1 out of 10 presses. I have tried to clean around the scroll wheel to no avail, updated the iCUE software as well as the mouse drivers, however nothing has helped. Running Firmware v 3.1.4 With the games I play, this button i used almost as much as the main right and left click buttons, so this is really hindering me. I had the exact same issue with a previous mouse of the same model, however I RMA'd it for a new mouse and this sorted it. I have a lot of faith in Corsair, I prefer the look and feel of this mouse over things like the Naga, however this issue really is make or break for me. If I can't find a solution I really do not want to get a third mouse with the fear of this simply happening once again.
Hi everyone my middle mouse button on my M65 is not working (works if i press it down harder sometimes) after updating the firmware to 2.04. Now i am not sure if it is actually the firmware or if my middle mouse button decided to give up on life. Anyone else experiencing it after the firmware upgrade?