Closed alexlnkp closed 1 week ago
Here's the wev
testing I've done:
[14: wl_keyboard] repeat_info: rate: 25 keys/sec; delay: 600 ms
[14: wl_keyboard] keymap: format: 1 (xkb v1), size: 68612
[14: wl_keyboard] key: serial: 11840; time: 3529492; key: 18; state: 1 (pressed) sym: 9 (57), utf8: '9'
[14: wl_keyboard] key: serial: 11841; time: 3529639; key: 18; state: 0 (released)sym: 9 (57), utf8: ''
[14: wl_keyboard] repeat_info: rate: 25 keys/sec; delay: 600 ms
[14: wl_keyboard] keymap: format: 1 (xkb v1), size: 68612
[14: wl_keyboard] key: serial: 13237; time: 3697686; key: 18; state: 1 (pressed) sym: 9 (57), utf8: '9'
[14: wl_keyboard] key: serial: 13238; time: 3697689; key: 18; state: 0 (released) sym: 9 (57), utf8: ''
[14: wl_keyboard] key: serial: 13239; time: 3697706; key: 18; state: 1 (pressed) sym: 9 (57), utf8: '9'
[14: wl_keyboard] key: serial: 13240; time: 3697709; key: 18; state: 0 (released) sym: 9 (57), utf8: ''
Hello,
the rivalcfg -r
command can only reset settings supported by Rivalcfg. On the SteelSeries Prime mouse, button bindings are not supported and thus cannot be reset.
Hello,
the
rivalcfg -r
command can only reset settings supported by Rivalcfg. On the SteelSeries Prime mouse, button bindings are not supported and thus cannot be reset.
Is there any way to modify what the buttons are mapped to? I'd rather have them simply mapped to mouse 5 and mouse 6 or something...
Yes, using the GG Engine on Windows or macOS (NOTE: this can also be done from a VM). If you want to do it with Rivalcfg, button support must be implemented first.
Yes, using the GG Engine on Windows or macOS (NOTE: this can also be done from a VM). If you want to do it with Rivalcfg, button support must be implemented first.
Alrighty then, thanks for the help! :)
Problem description
I was using Windows before, with the official SteelSeries Engine or whatever it's called. After I switched to Linux, to my surprise the settings of my mouse persisted (including the gradient of the LED, macros mapped to buttons, etc). One button on the side of the mouse inputs numpad's
9
, the other inputs numpad's9
twice in a quick succession with just 10ms in-between the inputs. I assume there's some kind of "memory" inside my mouse that keeps the settings? It would appear that it wasn't just the official SteelSeries software that was controlling what button did what on my mouse.However, if macros/button-mappings are stored in the memory of the mice itself, how come running
rivalcfg -r
does NOT reset them? Everything else, including the LED color, sensitivity and polling rate got reset, EXCEPT for the button mappings and macros...It would appear it's the
rivalcfg
itself that doesn't reset ALL of the settings, assumingly because it just doesn't see other configurable options?I installed rivalcfg using the official AUR package.
My mouse is SteelSeries Prime, a.k.a.:
Version info:
OS specs:
The
lsusb
output:Please, let me know if I've left something out. This issue's been bugging me for quite some time now...
Best, Alex