-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rival 3 Wireless button mapping #178
Comments
The command looks correct, so I do not know what is going wrong... I will have to ask my colleague to lend me his mouse again to test this... (but it will be complicated right now, as I work mostly from home because of the French COVID policy...) |
No worries! i can try and work something temporary out in the meantime. Hopefully you can get it soon |
I have the mouse for few days. I tried the following command:
And it worked for me. If I press the button 4, the text input of the focused windows is filled with I will try to find if there any way of reproducing your issue |
I had this exact same issue recently. Eventually installed the proprietary steel series tool and it flagged the fact that the mouse had old firmware. After an update I can now use the button options in rivalcfg. |
Just got my Rival 3 Wireless and was having trouble mapping buttons. I'm pretty sure I'm passing the right commands since the program doesn't yell at me and the json file shows the correct mappings, but the buttons won't work.
I set all the binds to 1 as a test but they still don't type out the number when pressed. At this point I'm not sure if I'm being an idiot and typing something wrong and if that is the case I'm sorry for submitting a pointless question lol.
print-debug output
The text was updated successfully, but these errors were encountered: