Rivalcfg
[hotfix] Rivalcfg v4.16.1 released with a fix for the Rival 3 Wireless Gen 2 sensitivity settings
A bug in Rivalcfg v4.16.0 affects the sensitivity settings of the SteelSeries Rival 3 Wireless Gen 2 mouse.
When fewer than 5 sensitivity presets are configured, Rivalcfg sets an incorrect sensitivity value on the Y axis. For example, if you configure only one preset, the vertical axis sensitivity is set to 100 DPI, causing the cursor to appear to move almost exclusively horizontally, which effectively makes the device unusable.
This bug is now fixed in Rivalcfg v4.16.1, released today. If you own a SteelSeries Rival 3 Wireless Gen 2, you are encouraged to update as soon as possible.
If you were affected by this issue, simply reconfigure the sensitivity settings using this new version of Rivalcfg. Doing so will restore the correct configuration and make the device behave normally again.
For a more technical description of the problem, please refer to issue #273.
Complete Changelog
Here is the complete changelog for Rivalcfg 4.16.1:
- fix(device): Fixed Rival 3 Wireless Gen 2 becoming unusable after setting sensitivity (@flozz, #273)
- fix(handler): Fixed multidpi_range_choice_xy handler with xxyy mapping using less than max_preset_count presets (@flozz, #273)