SteelSeries Rival 3 Wireless Gen 2

Supported Models

SteelSeries Rival 3 Wireless Gen 2 (2.4 GHz mode)

1038:1872

Missing Features

The following feature are currently not supported by Rivalcfg:

Color / illumination
Wheel mapping
Powering settings (high efficiency, smart illumination, sleep timer)

Command-Line Usage

usage: rivalcfg [-h] [--list] [--version] [--no-save] [--update-udev]
                [--print-udev] [--print-debug] [-s SENSITIVITY]
                [-p POLLING_RATE] [-b BUTTONS_MAPPING] [-r] [--battery-level]

options:
  -h, --help            show this help message and exit
  --list                List supported devices and exit
  --version             show program's version number and exit
  --no-save             Do not persist settings in the internal device memory
  --update-udev         Updates udev rules (Linux only, requires to be run as
                        root)
  --print-udev          Prints udev rules and exit
  --print-debug         Prints debug information and exit

SteelSeries Rival 3 Wireless Gen 2 (2.4 GHz mode) Options:
  -s, --sensitivity SENSITIVITY
                        Set sensitivity preset (DPI) (up to 5 settings, from
                        100 dpi to 18000 dpi, default: '800:800, 1600:1600')
  -p, --polling-rate POLLING_RATE
                        Set polling rate (Hz) (values: 125, 250, 500, 1000,
                        default: 1000)
  -b, --buttons BUTTONS_MAPPING
                        Set the mapping of the buttons (default:
                        buttons(button1=button1; button2=button2;
                        button3=button3; button4=button4; button5=button5;
                        button6=dpi))
  -r, --reset           Reset all settings to their factory default
  --battery-level       Print the battery level of the mouse and exit

Please report any bug on Github: https://github.com/flozz/rivalcfg/issues

Sensitivity (DPI)

This mouse supports up to 5 sensitivity presets. You can set different DPIs on X and Y axis. You can define them like this:

rivalcfg --sensitivity 800       # 1 preset (x=800dpi:y=800dpi)
rivalcfg --sensitivity 800,1600  # 2 presets
rivalcfg --sensitivity 800:1000,1600:1800  # 2 presets ;
#                      ↑x1 ↑y1  ↑x2  ↑y2   # x1=800dpi  : y1=1000dpi,
                                           # x2=1600dpi : y2=1800dpi

You can switch preset using the button under the mouse wheel.

Note

When you set the sensitivity through the CLI, the selected preset always back to the first one.

Note

From Python API, you can pass an int, a tuple or a list as parameter. You are also able to change the currently selected preset:

mouse.sensitivity(800)
mouse.sensitivity("800, 1600")
mouse.sensitivity([800, 1600])
mouse.sensitivity([
    [800, 1000],   # preset1 -> x1=800dpi,  y1=1000dpi
    [1600, 1800],  # preset2 -> x2=1600dpi, y2=1800dpi
])
# select the second preset (1600 dpi)
mouse.sensitivity([800, 1600, 2000, 4000], selected_preset=2)

Buttons

This mouse supports buttons mapping. Buttons can be mapped with:

some special actions,
mouse buttons,
multimedia keys,
and keyboard keys.

The general syntax for buttons mapping is the following:

buttons(layout=<LAYOUT>; button1=<mapping1>; buttonN=<mappingN>)

Example:

rivalcfg --buttons "buttons(layout=QWERTY; button1=button1; button2=PlayPause; button3=disabled; button5=A; button6=DPI)"

Arguments:

layout: The keyboard layout to use when papping the keys (see the “Mapping Keyboard Keys” section bellow).
button1: The first button of the mouse.
button2: The second button of the mouse.
buttonN: The Nth button of the mouse (The number of available buttons depends of the mouse model).

Note

All parameters are optional. If you do not define a mapping for a specific button, it will be reset to its default value.

You can also reset all buttons to their factory default by passing "default" as parameter:

rivalcfg --buttons default

Warning

Be sure to map the mouse button button1 on some button, else you will not be able to click with the mouse!

Mapping Special Actions

The following special actions are available¹:

disabled: disable the button,
dpi: use this button to switch between DPI presets,
ScrollUp: simulate a scroll up (not available on all devices¹)
ScrollDown: simulate a scroll down (not available on all devices¹)

Example:

buttons(button4=disabled; button5=disabled; button6=DPI)

Note

¹ The ScrollUp and ScrollDown actions are not available on all devices.

Rival 300 / Rival: OK
Sensei [RAW]: Not supported

Mapping Mouse Buttons

Mouse buttons can be mapped to any other mouse button.

For example, this swaps the 1 and 2 buttons of the mouse:

buttons(button1=button2; button2=button1)

Mapping Multimedia Keys

Mouse buttons can be mapped to multimedia keys. The following keys are available:

Mute: turn off the sound
Next: play next media
PlayPause: toggle play / pause on the currently playing media
Previous: play the previous media
VolumeUp: increase the volume
VolumeDown: decrease the volume

Example:

buttons(button4=VolumeDown; button5=VolumeUp)

Mapping Keyboard Keys

Mouse buttons can be mapped to any keyboard key, using different layouts.

To select the desired layout, just use the layout parameter. If this parameter is not specified, the QWERTY layout will be used by default.

Available layouts:

QWERTY (see available keys)

The available keys depend on the selected layout.

Example:

buttons(layout=QWERTY; button7=PageDown; button8=PageUp)

Note

Some characters like ; or = cannot be used as a key identifier as they interfere with the buttons() syntax. For those keys, use one of the available aliases, like semicolon (instead of ;) or equal (instead of =).

Example:

buttons(button4=semicolon; button5=equal)

Python API

TODO