Sensor and Performance

The Razer Viper V3 Hyperspeed is equipped with the Focus Pro 30K (PixArt PAW3950). According to specifications, the Focus Pro 30K is capable of up to 30,000 CPI, as well as a maximum tracking speed of 750 IPS, which equals 19.05 m/s. Out of the box, five pre-defined CPI steps are set: 400, 800, 1600, 3200, and 6400.

CPI Accuracy

"CPI" (short for counts per inch) describes the number of counts registered by the mouse if it is moved exactly an inch. There are several factors (firmware, mounting height of the sensor not meeting specifications, mouse feet thickness, mousing surface, among others) which may contribute to nominal CPI not matching actual CPI. It is impossible to always achieve a perfect match, but ideally, nominal and actual CPI should differ as little as possible. In this test, I'm determining whether this is the case or not. However, please keep in mind that said variance will still differ from unit to unit, so your mileage may vary.


I've restricted my testing to the four most common CPI steps, which are 400, 800, 1600, and 3200. As you can see, deviation is consistently positive and moderately high, which is a good result overall. In order to account for the measured deviation, adjusted steps of 400, 750, 1500, and 3050 CPI have been used for testing.

Motion Delay

"Motion delay" encompasses all kinds of sensor lag. Any further sources of input delay will not be recorded in this test. The main thing I'll be looking for in this test is sensor smoothing, which describes an averaging of motion data across several capture frames in order to reduce jitter at higher CPI values, increasing motion delay along with it. The goal here is to have as little smoothing as possible. As there is no way to accurately measure motion delay absolutely, it can only be done by comparison with a control subject that has been determined to have the lowest possible motion delay. In this case, the control subject is a Logitech G403, whose PixArt PMW3366 sensor has no visible smoothing across the entire CPI range. Note that the G403 is moved first and thus receives a slight head start.


First, I'm looking at two xCounts plots—generated at 1600 and 30,000 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." As you can see, neither plot shows any, which strongly suggests there not being any smoothing. Owing to sensor-level MotionSync, SPI timing jitter is minimal.


In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 30,000 CPI. The line further to the left denotes the sensor with less motion delay. I can measure a motion delay differential of roughly 0.5 ms at 1600 CPI and 2 ms at 30,000 CPI. The latter showing appears to be related to what is described below.


Much like on the Basilisk V3 Pro, DeathAdder V3 Pro, or Viper V2 Pro, when using the included full-speed dongle, a rather peculiar behavior may show up. Essentially, at some ultimately random point within the motion, a shift occurs, beyond which motion delay increases. I've only been able to demonstrate this behavior when using the included full-speed dongle at 1000 Hz in wireless mode. Unfortunately, I'm unable to assert what causes this behavior.


Upon closer inspection, it becomes clear that any of these shifts correlates with an off-period poll.

Speed-related Accuracy Variance (SRAV)

What people typically mean when they talk about "acceleration" is speed-related accuracy variance (or SRAV for short). It's not about the mouse having a set amount of inherent positive or negative acceleration, but about the cursor not traveling the same distance if the mouse is moved the same physical distance at different speeds. The easiest way to test this is by comparison with a control subject that is known to have very low SRAV, which in this case is the G403. As you can see from the plot, no displacement between the two cursor paths can be observed, which confirms that SRAV is very low.

Perfect Control Speed

Perfect Control Speed (or PCS for short) is the maximum speed up to which the mouse and its sensor can be moved without the sensor malfunctioning in any way. I've only managed to hit a measly 5 m/s, which is within the proclaimed PCS range and shows no sign of the sensor malfunctioning.

Polling Rate Stability

For wired mice, polling rate stability merely concerns the wired connection between the mouse (SPI communication) and USB. For wireless mice, another device that needs to be kept in sync between the first two is added to the mix: the wireless dongle/wireless receiver. I'm unable to measure all stages of the entire end-to-end signal chain individually, so testing polling-rate stability at the endpoint (the USB) has to suffice here.


First, I'm testing whether SPI, wireless, and USB communication are synchronized. Any of these being out of sync would be indicated by at least one 2 ms report, which would be the result of any desynchronization drift accumulated over time. I'm unable to detect any periodic off-period polls that would be indicative of a desynchronization drift.


Second, I'm testing the general polling-rate stability of the individual polling rates in wireless mode. Running the Viper V3 Hyperspeed at a lower polling rate can have the benefit of extending battery life. Of the available polling rates (125, 500, and 1000 Hz), only 1000 Hz looks fine. In terms of performance, Razer has assured me that both 125 and 500 Hz are working as intended, despite not looking that way. In fact, 500 Hz in particular is said to be faster than many 1000 Hz implementations, which I've been able to corroborate. When using the HyperPolling Wireless Dongle instead of the included full-speed one, the plots look significantly different:

Paint Test

This test is used to indicate any potential issues with angle snapping (non-native straightening of linear motion) and jitter, along with any sensor lens rattle. As you can see, no issues with angle snapping can be observed. No jitter is visible at 1600 CPI. 15,000 CPI shows significant jitter, which is amplified to major levels at 30,000 CPI. This is in line with what to expect from a sensor lacking smoothing entirely. Lastly, there is no sensor lens movement.

Lift-off Distance

The Viper V3 Hyperspeed offers a wider range of possible LOD adjustment than most mice. One can set the LOD to pre-defined levels of low, medium, or high. Manual calibration is no longer present as the sensor already does this by itself. When using the "low" option, the sensor does not track at a height of 1 DVD (<1.2 mm), which doesn't change when using the "medium" option. When using the "high" setting, the sensor does track at a height of 1 DVD, but not at a height of 2 DVDs (1.2<x<2.4 mm, x being LOD height). Additionally, Asymmetric Cut-off can be enabled, which allows for a higher lift-off distance while keeping the landing distance low. Keep in mind that LOD may vary slightly depending on the surface (mouse pad) it is being used on.

Click Latency

In most computer mice, debouncing is required to avoid double clicks, slam-clicks, or other unintended effects of switch bouncing. Debouncing typically adds a delay, which, along with any potential processing delay, shall be referred to as click latency. In order to measure click latency, the mouse has been interfaced with an NVIDIA LDAT (Latency Display Analysis Tool). Many thanks go to NVIDIA for providing an LDAT device. More specifically, the LDAT measures the time between the electrical activation of the left main button and the OS receiving the button-down message. Unless noted otherwise, the values presented in the graph refer to the lowest click latency possible on the mouse in question. If a comparison mouse is capable of both wired and wireless operation, only the result for wireless (2.4 GHz) operation will be listed.

Using the included full-speed dongle, click latency has been measured to be 1.1 ms, with standard deviation being 0.41 ms. When using the HyperPolling Wireless Dongle at a polling rate of 1000 Hz, click latency has been measured to be 0.8 ms, with standard deviation being 0.29 ms. When using the HyperPolling Wireless Dongle at a polling rate of 2000 Hz, click latency has been measured to be 0.6 ms, with standard deviation being 0.15 ms. When using the HyperPolling Wireless Dongle at a polling rate of 4000 Hz, click latency has been measured to be 0.5 ms (0.51 ms), with standard deviation being 0.08 ms. Finally, when using the HyperPolling Wireless Dongle at a polling rate of 8000 Hz, click latency has been measured to be 0.5 ms (0.45 ms), with standard deviation being 0.07 ms.

The main button switches were measured to be running at 1.913 V. I'm not aware of the voltage specifications of the Kailh GM 4.0 (60 M) switches, but 1.913 V does seem rather low to me, albeit not excessively so.

Extra: 8000 Hz Wireless Polling

As part of a recent firmware update, the Viper V3 Hyperspeed, much like any other Razer wireless mouse compatible with the HyperPolling Wireless Dongle, can now be set to 8000 Hz polling. As a result, reports occur at an interval of 0.125 ms (or 125 μs), achieving equity with Razer's wired HyperPolling mice. Due to the differences in antenna performance present between each compatible model, the results below will not be fully applicable to each of them, but can be considered generally representative of expected performance nonetheless. The testing has been performed at 3200 CPI.


Despite MotionSync being enabled, count distribution is slightly looser compared to lower polling rates. An interval of 0.125 ms is averaged, and the odd outlier aside, polling is stable. The Viper V3 Hyperspeed is ahead of the G403 by roughly 0.6 ms.


Even though polling is generally stable, missed polls can be observed here and there, though this is expected outside of an anechoic chamber.


In addition, we can see that at times, MotionSync is barely able to keep up. This typically happens at framerate transition points.