Rivalcfg

Rivalcfg v4.17.0 released with Rival 5 and Prime+ support

2026-04-03T00:00:00+02:00

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:

https://flozz.github.io/rivalcfg/devices/rival5.html

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!

SteelSeries Rival 5 mouse. Left: regular version, Right: Destiny Edition

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:

https://flozz.github.io/rivalcfg/devices/prime_plus.html

SteelSeries Prime+ mouse with its OLED screen

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:

2026-02-24 - New standalone builds for Linux, macOS and Windows

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.

List of supported and unsupported devices

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)

[hotfix] Rivalcfg v4.16.1 released with a fix for the Rival 3 Wireless Gen 2 sensitivity settings

2026-03-10T00:00:00+01:00

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)

New standalone builds for Linux, macOS and Windows

2026-02-24T00:00:00+01:00

Hello folks!

I know it was sometimes difficult to use Rivalcfg because installing it from sources requires using unusual tools for those who are not Python developers (venv, pip, etc.). It is even worse on Windows where you have to install Python first as it is not part of the system.

That's why I am glad to announce the brand new standalone builds of Rivalcfg that have been requested one year and a half ago! Standalone builds are compiled versions of Rivalcfg you can run without installing any dependencies. You only have to download an archive (.tar.gz for Linux, .zip for Windows) or a disk image (.dmg) for macOS and extract the files from it. That's it!

Standalone releases of Rivalcfg for Linux, macOS and Windows

For Windows users that may be less used to the command line, I added a help message and a pause in the execution of the program if Rivalcfg is run without arguments, which is the case when you double-click on the executable. This is to avoid having just a "flashing" terminal window that closes immediately, which may be interpreted as "it does not work".

Standalone version of Rivalcfg on Windows

I did not want to wait for the next Rivalcfg version to bring the standalone builds to folks who wanted to use them, so I released standalone builds for the last Rivalcfg version (v4.16.0). I flagged them as "experimental" as they are brand new. Do not hesitate to open an issue on GitHub if you find a bug.

Please note that it is known that the --print-debug option is broken on those builds, and probably on the "regular" v4.16.0 version too, since I removed the dependency on setuptools, this will be fixed in the next release.

On a more technical note, those builds are made with a Python compiler named Nuitka. The Linux and macOS versions are compiled with Python 3.14, which brings a beautifully colored help output. The Windows version, however, use Python 3.13 as it crashes with Python 3.14 (this Python version is still experimentally supported by Nuitka).

Rivalcfg colored help output (Rival 100)

Along with this new way to distribute Rivalcfg, I added a "download" page on the website that references the standalone builds, and I updated the install documentation to make things simpler.

See you in a month or two for the next Rivalcfg release! 😄️

Rivalcfg v4.16.0 released with new supported devices and a lot of improvements!

2026-02-14T00:00:00+01:00

Rivalcfg v4.16.0 was released on 2026-02-13. It adds support for 3 new devices and improves the CPI (sensitivity) setting for many mice. On the technical side, this version adds official support for Python 3.14 and drops support for Python 3.9. The packaging has also been modernized (the old setup.py / setuptools combo was replaced by pyproject.toml and Flit).

Three new devices supported

As mentioned in the introduction, this version brings support for 3 new SteelSeries mice.

Aerox 3 Wireless CS2 Dragon Lore Edition

The first one is the "SteelSeries Wireless Gaming Mouse CS2 Dragon Lore Edition". It is just a skin of the Aerox 3 Wireless, so it was easy to support. You will find more information about this mouse in the documentation:

https://flozz.github.io/rivalcfg/devices/aerox3_wireless.html

SteelSeries Wireless Gaming Mouse CS2 Dragon Lore Edition (Aerox 3 Wireless)

Rival 3 Gen 2

The second one is the Rival 3 Gen 2, a new iteration of the Rival 3. The main change is the ability to set different sensitivity values for X and Y axes. This required implementing a new handler to fully support the device. More info in the doc:

https://flozz.github.io/rivalcfg/devices/rival3_gen2.html

Also, I would like to thank Orson Teodoro who helped support this mouse! 😁️

Rival 3 Gen 2, black and white versions

Rival 3 Wireless Gen 2

And the last one is the Rival 3 Wireless Gen 2. Like the wired version, it is just a new iteration of the previous Rival 3 Wireless, with the ability to set different CPI values on X and Y axes.

Please note that, as for the first version, the support of the Gen 2 is partial. The following features are currently not supported:

Color / illumination,
Wheel scroll mapping,
Power settings (high efficiency, smart illumination, sleep timer).

I will work on this later for both Gen 1 and Gen 2 devices. More information in the doc:

https://flozz.github.io/rivalcfg/devices/rival3_wireless_gen2.html

Rival 3 Wireless Gen 2, black, white, lavender and aqua versions

Improvement of the CPI setting

To set the mouse sensitivity, Rivalcfg must convert the CPI requested by the user, (for example, 1800 dpi) to a value understood by the sensor, such as 0x14.

Some sensors are linear and are easy to map. For those, we may have [100 dpi = 0x01], [200 dpi = 0x02], [300 dpi = 0x03] and so on. However, some other sensors are not linear and use a fixed conversion table that contains unexpected "jumps". For example, the TrueMove Air sensor is mapped with [100 dpi = 0x00], [200 dpi = 0x02], [300 dpi = 0x03], etc.

TrueMove Air sensor is non-linear, so we can see "jumps"

For non-linear sensors, Rivalcfg used to approximate values using a linear function. This works for most values, but for some of them it does not match the ones of the fixed table. In such cases, the behavior is undefined. It may set a slightly different sensitivity than the requested one, or it may not work at all.

Anyway, this is now fixed. Rivalcfg v4.16.0 includes value tables for the TrueMove Air, TrueMove Core and PMW3326 sensors, so it now perfectly matches the SteelSeries GG Engine behavior.

Mouse families that now have accurate CPI values are:

Aerox 3
Aerox 3 Wireless
Aerox 5
Aerox 5 Wireless
Aerox 9 Wireless
Prime Wireless
Rival 106 device
Rival 110 device
Rival 3
Rival 3 Wireless
Rival 300S device

Complete Changelog

Here is the complete changelog for Rivalcfg 4.16.0:

feat(devices): Added support for the Aerox 3 Wireless CS2 Dragon Lore Edition (1038:187a, 1038:1878) (@flozz)
feat(devices): Added support for the Rival 3 Gen 2 (1038:1870) (#249, #257, @flozz, @orsonteodoro)
feat(devices): Added support for the Rival 3 Wireless Gen 2 (1038:1872) (#258, @flozz)
feat(handler): Added range_choice handler (@flozz)
feat(handler): Added multidpi_range_choice handler (@flozz)
feat(handler): Added multidpi_range_choice_xy handler (@flozz)
fix(devices): Fixed DPI values for devices using the TrueMove Air sensor (@flozz):
- Aerox 3 Wireless (1038:183A, 1038:187A, 1038:1838, 1038:1878)
- Aerox 5 (1038:1850)
- Aerox 5 Wireless (1038:1854, 1038:185E, 1038:1862, 1038:1852, 1038:185C, 1038:1860)
- Aerox 9 Wireless (1038:185A, 1038:1876, 1038:1858, 1038:1874)
- Prime Wireless (1038:1842, 1038:184A, 1038:1840, 1038:1848)
- Rival 3 Wireless (1038:1830)
fix(devices): Fixed DPI values for devices using the TrueMove Core sensor (@flozz):
- Aerox 3 (1038:1836)
- Rival 3 (1038:1824, 1038:184C)
fix(devices): Fixed DPI values for devices using the PixArt PMW3326 sensor (@flozz):
- Rival 106 device (1038:1816)
- Rival 110 device (1038:1729)
- Rival 300S device (1038:1810)
misc(tests): Added tests for the Aerox 5 device (1038:1850) (@flozz)
misc: Modernized packaging setup.py/setuptools -> pyproject.toml/flit (@flozz)
misc: Added Python 3.14 support (@flozz)
misc!: Removed Python 3.9 support (@flozz)

10 years of Rivalcfg, new Web site and a logo!

2026-02-13T00:00:00+01:00

Hello folks!

This year, Rivalcfg turns 10 years! How time flies!

It's been 10 years since I started reverse engineering USB devices. When I wrote the first commit of this project on March 28, 2016, I only wanted to be able to change the color of my brand new Rival 100 mouse on Linux. I had no idea that 10 years later I would still be working on this project.

Photo of my old Rival 100 mouse and screenshot of Rivalcfg 1.0.0 (released on April 5, 2016)

Today, Rivalcfg aims to support any SteelSeries gaming mouse. I can currently count 73 devices listed by "rivalcfg --list". It sounds like a lot, but be aware that some are counted twice (when they have two different product IDs for wired and wireless modes), and some devices are just skins of identical mice (for example, the Rival 300 family counts 10 devices, all technically the same).

If I count "by hand", I find 24 different families of mice 🐭️. That's still a lot for a single maintainer! Anyway, Rivalcfg now supports — or at least partially supports — most SteelSeries mice. Some are still missing, but I am working to fix that. 😉️

A brand new Web site

After 10 years of existence, it is a shame this project still does not have a Web site, so I made one. Currently, it is mostly a landing page with links to the documentation and GitHub, but I will add more content later.

I used to post about Rivalcfg on my blog and on my BuyMeACoffee page. But the content is mixed with other things and my blog is in French. This Web site will allow me to post some news about the project (mostly release announcements) in one place, and in English, to make it accessible to more people.

Rivalcfg now has a Logo

This week, I finally drew a logo for Rivalcfg. It represents a mouse with its scroll wheel, forming an "R", like in Rivalcfg. It is inspired by the SteelSeries one but not too close to it, to avoid any legal issues.

Rivalcfg logo

The logo is already used on this Web site, and I will add it on GitHub too. It may also be used later for a future GUI.

Future of the project

In 2025 I almost not worked on Rivalcfg. That year was a difficult one for me, and I must admit I felt a little fatigue on this project... But I am back!

A new Rivalcfg version (v4.16.0) will be released very soon. It will add support for latest SteelSeries mice and will improve the CPI (sensitivity) settings of all devices using the TrueMove Core, TrueMove Air and PMW3326 sensors.

After this release, I will have to review a pull request that adds support for the Rival 5 mouse, which should be released in v4.17.0. Then I will try to work on the ability to send multiple USB packets for a single setting. This will allow to support button bindings on the Aerox 9 and the bindings of the scroll wheel on some other devices.

In a later futur, I want to work on a graphical user interface (using GTK 4). It would make Rivalcfg simpler to use for less technical folks, especially gamers who are new to Linux.

Preliminary work for this GUI already started years ago (in the v4.4.0, released at the end of 2021), when I added code to save mouse settings to the computer's disk. This is required to allow Rivalcfg to display the current state of the settings in the GUI as they cannot be retrieved from the device itself.

Interestingly, I already developed a proof of concept for a GTK 3 GUI during a live coding session on Twitch, but I never had time to go further.

Proof of concept GTK 3 GUI for Rivalcfg

That's all folks

That's it for today. I hope you enjoyed the reading and that Rivalcfg is useful to you. To stay informed about Rivalcfg, you can now subscribe to the Atom feed of this Web site, join the Discord server, or follow me on Mastodon and Bluesky.

See you soon for the v4.16.0 release announcement! 😄️

Rivalcfg

Rivalcfg v4.17.0 released with Rival 5 and Prime+ support

New Supported Devices

Rival 5 and Rival 5 Destiny Edition

Prime+

Print Debug Crash Fixed

Standalone Builds

Documentation and Website

Complete Changelog

[hotfix] Rivalcfg v4.16.1 released with a fix for the Rival 3 Wireless Gen 2 sensitivity settings

Complete Changelog

New standalone builds for Linux, macOS and Windows

Rivalcfg v4.16.0 released with new supported devices and a lot of improvements!

Three new devices supported

Aerox 3 Wireless CS2 Dragon Lore Edition

Rival 3 Gen 2

Rival 3 Wireless Gen 2

Improvement of the CPI setting

Complete Changelog

10 years of Rivalcfg, new Web site and a logo!

A brand new Web site

Rivalcfg now has a Logo

Future of the project

That's all folks

Rival 5 and Rival 5 Destiny Edition

Rival 3 Gen 2

Rival 3 Wireless Gen 2