Jump to content
Corsair Community

Vengeance M65 button 4 mapping problem


havocwreaker

Recommended Posts

Does anyone have the issue where when you try to map a keystroke to button 4 it continues to toggle it until button 5 is pressed?

 

 

For example if I map keystroke (1) to button 4 and I press button 4 the output is:

1111111111111111111111...until I press button 5 mapped to keystroke (2)

 

Button 5 does not exhibit this behavior and it works as it should. My 8 button mouse is effectively a 7 button one as I do not use DPI switching. I have verified that "Playback once" is selected.

 

The mouse is 2 days old and I updated the firmware upon installation. Everything went well with the update and the rest of the mouse works well.

 

I hope someone can shed some light on this issue.

Link to comment
Share on other sites

I have verified that "Playback once" is selected.

 

 

Yes, thanks for the response. As I mentioned, button 5 works fine, but button 4 does not respond well. I'm guessing it's a firmware glitch? I need someone to confirm if they have the same issue or I just have a defective mouse.

Link to comment
Share on other sites

I have tried reflashing the F/W. It was "successful". I will try to re-install the software in the morning, I need some sleep. lol

 

I don't see why the software would even be a factor as all the other configurations and buttons work as they should. All custom mappings are good except for button 4. When I set button 4 to "no function", it becomes disabled. Also, if I set the button to DPI select, it toggles through my DPI settings without going crazy. It reacts normally.

 

The ONLY time button 4 misbehaves is when it is set to a "keystroke".

Link to comment
Share on other sites

  • Corsair Employees
There is a bug with button 4 (endless repeating) that we will resolve with the next update. You can do a workaround though by enabling hardware playback if you still wish to use it. It won't happen if you do so.
Link to comment
Share on other sites

There is a bug with button 4 (endless repeating) that we will resolve with the next update. You can do a workaround though by enabling hardware playback if you still wish to use it. It won't happen if you do so.

 

Awesome Ram Guy! Thanks for confirming this. I also confirm your "temp" solution worked. Thank you!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...