Rivalcfg v4.17.0 released with Rival 5 and Prime+ support
Rivalcfg v4.17.0 was released yesterday. This new version adds support for 3 new devices and fixes a bug with --print-debug option. Standalone builds are no longer considered experimental.
New Supported Devices
This version now supports three new devices: two variants of the Rival 5 and the Prime+.
Rival 5 and Rival 5 Destiny Edition
The SteelSeries Rival 5 is a mouse that comes with 9 programmable buttons, 10 configurable LEDs and a lot of options. It is now almost fully supported, the only missing feature is the ability to set the rainbow effect only for some of the LEDs. This may be implemented later.
The Rival 5 comes in two flavours, both now supported:
- the regular one (1038:183c),
- and the Destiny Edition (1038:183e).
Device documentation:
A big thanks to Saltblob and nonoo who helped to support this mouse, and to all contributors that supported this project as it allowed me to actually buy the device to finalize its support!
Prime+
The SteelSeries Prime+ mouse has 6 buttons and one LED (under the wheel). It is almost identical to the regular Prime except it has a small OLED screen under the device. Currently, only the most important features like sensor sensitivity (DPI), LED color, and button bindings are supported for this device. The following features are not supported yet and may be implemented in the future:
- OLED screen under the mouse
- Lift-off distance of the sensor
- Advanced illumination configurations
- Button bindings on the wheel (scroll)
Prime+ documentation:
Print Debug Crash Fixed
Since the change of build system operated in v4.16.0 (setuptools replaced by Flit), the "rivalcfg --print-debug" command, that prints some information useful when you want to report a bug, was not working anymore as it relied on setuptools to get the version of the hidapi library. This is now fixed.
Note that the command may have worked for you if you installed Rivalcfg from source as setuptools may already be present on your system.
Standalone Builds
Standalone builds are compiled versions of Rivalcfg, available for Linux, macOS and Windows. They are easy to use as the only thing you have to do is extract some files and you have a working version of Rivalcfg. No dependency to install, no developer tool to use (pip, git, venv,...).
I already published a post about standalone builds in February if you want to read more:
Since this v4.17.0 version of Rivalcfg, standalone builds are no longer considered experimental and are the recommended way to use the software.
Documentation and Website
The Rivalcfg website and documentation are being improved.
A new "device" page was added to the website. It lists all supported mice with a direct link to their documentation, and it also lists all devices that are not yet supported.
The "installation" page of the documentation was fully rewritten to be simpler to read and now only documents installing from sources. Standalone build downloads and other ways to install Rivalcfg (like the AUR package for Arch Linux) are now listed on the "download" page of the website.
The theme of the documentation has also been updated to use the same colors, logo and favicon as the website.
Complete Changelog
Here is the complete changelog for Rivalcfg 4.17.0:
- feat(device) Added support of the Rival 5 (1038:183C) mouse (@Saltblob, @nonoo, @flozz, #165, #268)
- feat(device) Added support of the Rival 5 Destiny Edition (1038:183E) mouse (@flozz)
- feat(device) Added initial support of the Prime+ (1038:182C) mouse (@BenJamesAndo, @flozz, #201)
- fix(debug): Fixed a crash when getting hidapi version without having setuptools installed (@flozz)
- misc(standalone): Added a standalone build for Linux (@flozz)
- misc(standalone): Added a standalone build for Windows (@flozz, #231)
- misc(standalone): Added a standalone build for macOS (@flozz)
- misc(ssdb): Updated ssdb script to extract the product_id of wireless mice dongles (@flozz)
- docs(device): Added missing Aerox 5 documentation (@flozz)