Hey there!
I’m using a Corsair M65 Elite wich ist on the list of supported devices but i got some problems with the additional mouse buttons.
On ‘Mouse Settings’ there is no option to set a keybind for the additional mouse buttons. Only options are DPI-Settings.
So i reinstalled ICUE to set up my hardware keybinds, but it seems that SignalRGB ist overwriting those.
When i have the device enabled in SignalRGB (ICUE not running) hardware keybinds of the mouse won’t work. When disabled the hardware keybinds work just fine ( ICUE still not running).
Any ideas?
The overwriting issue happens because when SignalRGB app is running it takes full control of the device and, since the additional mouse buttons are present on the app, it doesn’t work. You can use our “Macros” feature to keybind the mouse buttons.
This does not work for the top buttons on the Corsair Scimitar. For macro->key pressed trigger it registers every other button but does nothing when pressing the top buttons behind the scroll wheel. These top buttons are by default set to cycle DPI settings, but I remapped them in iCue and saved them to a hardware profile so they register as mouse button 5 and 6, then uninstalled iCue. SignalRGB overrides this, and sets it back to DPI cycle, and will not register as a macro key press.
It’s worth noting though that all my other mouse buttons mapped in the harware profile are fine. E.g. all of my side buttons are mapped to the keypad 1-9 etc. These don’t change, and I don’t need a macro to rebind them.
I can see the DPI behavior in the SignalRGB device console, every other mouse button registers correctly like:
plugin: Bit IDX:8
plugin: Button Pressed: Keypad 1
plugin: Bit IDX:8
But the top buttons only register as:
plugin: Bit IDX:5
plugin: DPI UP
plugin: Bit IDX:5
and
plugin: Bit IDX:6
plugin: DPI DOWN
plugin: Bit IDX:6
IDX, or index, is correct. It should be mouse button 5 and 6, but DPI UP/DOWN is incorrect. How can I change this or get it to register in the macro creation to remap it to a different output?
