The original implementation was discussed in openrazer/openrazer#231.
Take a look at the kernel log ( dmesg) to see if there's any output from razermouse after setting the DPI. It's likely the case that the device just isn't accepting the instruction, and so it stays at 3500. There could be a silent error by the driver, which would be a good starting point to raise an issue in OpenRazer's repo. Another user had a similar problem with DPI doing nothing but in the end, their solution was changing the mouse acceleration speed: openrazer/openrazer#1183 (comment) It's looking like a bug in OpenRazer for the DeathAdder 3.5G. How it handles that on the backend is a mystery I suppose - maybe it maps my selection to the closest of those four presets that I see in the Controller's drop-down (450, 900, 1800, 3500)? It has a slider that allows a selection of any value between 1, in increments of 100 (i.e.
Razer deathadder dpi how to change windows#
You know way more about this stuff than I, so I trust you know what you're talking about when it comes to what potential DPI values are possible for this particular mouse - but I thought it worth mentioning how the Razer Synapse app in Windows handles adjustments to DPI. I can select a new value from the drop-down, but it resets back to 3500 like before. I base that on two things: (1) the feel of the mouse speed didn't change at all after running the command, and (2) in the Polychromatic controller, the DPI was still being reported as 3500.Īs for the behavior in the Controller, it is unchanged. I tried it with both 900 (which is one of the presets in the Polychromatic drop-down) and 800, but neither seemed to work.
Without it throwing an exception now, but the DPI doesn't seem to change when I do that.
Unfortunately, it doesn't seem to have fixed the issue. I really appreciate you getting back so quickly, thank you! I tried running the command you gave me, and it did what it's supposed to do (I checked to verify the changes in openrazer.py).
0 kommentar(er)
