freenapse

Guides

Viper V3 Pro settings not saving to onboard memory

The mouse stores everything itself. When a setting does not stick, either something is rewriting it or the write never reached the mouse. Here is how to tell which.

Read the mouse, not the app

freenapse status

This asks the mouse what it holds right now and prints it: DPI stages and the active one, polling rate, the button assignments on both layers, Dynamic Sensitivity, lift-off mode, sleep timeout, low power threshold, battery. It is the ground truth. If status shows your value, the mouse has it, whatever any app displays. If it does not, one of the four causes below applies.

The four reasons a setting does not stick

Synapse is still running
While Razer Synapse runs in the background it rewrites the settings it thinks it owns within about fifteen seconds, so anything written by another program appears to revert. Quit it from the tray, or uninstall it. Do not run both for long.
The mouse was asleep
The wireless Viper V3 Pro stops answering the dongle after a few seconds without input, and a write sent then is lost. Keep moving the mouse while a command runs. The tray app and the settings window keep the change pending and write it when the mouse wakes; the status line under the content says so.
The config file was edited but not applied
Changes in config.toml reach the mouse only with freenapse apply. The settings window and the CLI commands write immediately; the file is for edits by hand and for carrying a setup to another PC.
It was never an onboard setting
Some of what Synapse shows is not stored in the mouse at all. On the Viper V3 Pro, macros, per-game profiles, the in-game polling rate and software bindings such as launching a program are played by the software and vanish when it is not running. The mouse has no macro memory. freenapse does the same for macros and per-game profiles, through the tray app.

Write it again and check

freenapse apply     # write the config file to the mouse
freenapse status    # read it back
freenapse import    # the other way: rebuild the config from what the mouse holds

One value is an exception: the asymmetric cut-off levels (lift-off and landing). The mouse accepts them but cannot read them back on firmware 1.11, so status cannot show them and freenapse rewrites them on every apply. Smart Tracking at 1, 2 or 3 mm reads back normally.

Questions

Does the Viper V3 Pro have onboard memory?
Yes, one profile. It holds the DPI stages, the polling rate, the button assignments on the normal and Hypershift layers, Dynamic Sensitivity, the lift-off setting, the idle sleep timeout and the low power threshold. It holds a single profile and refuses the others, and it has no macro memory.
Do I need freenapse running to keep the settings?
No. Once written, the settings are in the mouse and work on any PC with nothing installed. The tray app adds the battery icon, quick switching, macros and per-game profiles, which are software features by nature.
Can I see the exact bytes the mouse answers?
freenapse probe prints every read with its command and argument bytes, serial numbers masked. It is also what to paste into an issue for a mouse other than the Viper V3 Pro.
Set the DPI and polling rate without Synapse
The five commands, and what the mouse does with each value.
Uninstall Razer Synapse and keep your settings
Remove the program that keeps rewriting the mouse.