Supported Razer mice

Which Razer mice freenapse 0.4.2 configures, and what it can set on each one. A verified mouse has been tested setting by setting on real hardware; every other one opens read-only until its owner tests it.

Feature by feature

The mice an owner has tested. Everything marked here is written to the mouse’s onboard memory and read back, so it keeps working with freenapse closed or on another computer.

FeatureViper V3 ProBasilisk V2DeathAdder V3 Pro, wired
StatusVerifiedVerifiedBeing tested: writes need allow_unverified
ConnectionUSB cable, HyperSpeed or HyperPolling dongleUSB cableUSB cable
Product id0x00C0, 0x00C10x00850x00B6
DPI stagesUp to 5, 100 to 35000Up to 5, 100 to 20000Up to 5, 100 to 30000
Polling rate125 to 8000 Hz; 8000 through the HyperPolling dongle125, 500, 1000 Hz125, 500, 1000 Hz
ButtonsAll 7, normal and Hypershift layerAll 13, normal and Hypershift layer: wheel tilts, DPI up and down, sensitivity clutch, profile buttonRead back and written by an owner
MacrosNo macro memory: the tray app plays them, as Synapse doesStored in the mouseNot tested yet
Dynamic SensitivityClassic, Natural, Jump and a custom curveNo, the firmware refuses itNo, the firmware refuses it
Sensor rotation−30 to 30 degreesNoNo
Lift-offSmart Tracking 1, 2, 3 mm and asymmetric cut-offNoSmart Tracking
Battery, sleep, low powerBattery in the tray, idle sleep, low-battery modeNo battery: the tray shows it as wiredIdle sleep and low-battery mode
LightingNo LEDsLogo and wheel: off, static, breathing, spectrum, brightnessNo LEDs
Dongle pairingPair, unpair, auto-pairing, dongle LEDWired onlyWired only
Per-game profilesDPI, polling and buttons per game, tray appDPI, polling and buttons per game, tray appDPI, polling and buttons per game, tray app
Config fileconfig.tomlconfig-basilisk-v2.toml, so two mice on one PC never share settingsconfig.toml

Every mouse freenapse knows

This is the program’s own device list. The rows nobody has tested take product id, polling command and DPI ceiling from OpenRazer’s device list; on those, status and probe work and every write is refused.

MouseProduct idPollingDPI up toStatus
Viper V3 Pro, wired0x00C0classic: 125, 500, 1000 Hz35000Verified
Viper V3 Pro, HyperSpeed or HyperPolling dongle0x00C1HyperPolling: 125 to 8000 Hz35000Verified
Basilisk V20x0085classic: 125, 500, 1000 Hz20000Verified
DeathAdder V3 Pro, wired0x00B6classic: 125, 500, 1000 Hz30000Being tested
DeathAdder V3 Pro, wireless0x00B7classic: 125, 500, 1000 Hz35000Read-only
DeathAdder V4 Pro, wired or wireless0x00BE, 0x00BFHyperPolling: 125 to 8000 Hz45000Read-only
DeathAdder V3, wired 8K0x00B2HyperPolling: 125 to 8000 Hz30000Read-only
Viper V2 Pro, wired or wireless0x00A5, 0x00A6classic: 125, 500, 1000 Hz30000Read-only
Viper V3 HyperSpeed0x00B8classic: 125, 500, 1000 Hz30000Read-only
Viper Mini SE, wired or wireless0x009E, 0x009FHyperPolling: 125, 500, 1000 Hz wired, 125 to 8000 Hz wireless30000Read-only
Viper 8KHz0x0091HyperPolling: 125, 500 to 8000 Hz20000Read-only
Cobra Pro, wired or wireless0x00AF, 0x00B0classic: 125, 500, 1000 Hz30000Read-only
Pro Click V2 Vertical, HyperSpeed dongle0x00C8classic: 125, 500, 1000 Hz30000Read-only: probed by its owner, write tests next
Basilisk V3 Pro, wired or wireless0x00AA, 0x00ABclassic: 125, 500, 1000 Hz30000Read-only
HyperPolling wireless dongle, on its own0x00B3HyperPolling: 125 to 8000 Hz30000Read-only
Any other Razer mouseany, vendor 0x1532classic assumed30000 assumedRead-only

The same list is on the Devices page of the settings window, with the mouse that is connected marked.

Add your mouse

Run freenapse probe with Synapse closed and paste the output into a “New mouse” issue. The probe only reads: it lists what the mouse answers to, every button code included. The next step is testing the writes on your mouse, with [device] allow_unverified = true in the config, and sending its row of src/device.rs. CONTRIBUTING.md has the steps; the DeathAdder V3 Pro and the Pro Click V2 Vertical arrived this way.