Sensor and Performance

The Razer Orochi V2 is equipped with the PixArt PAW3369, which I believe to be a customized PAW3335. According to specifications, the 3369 is capable of up to 18,000 CPI, as well as a maximum tracking speed of 450 IPS, which equals 11.43 m/s. Out of the box, five pre-defined CPI steps are available: 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. Aside from the 400 CPI step, all steps exhibit consistently positive deviation of widely varying yet mostly significant degree, which is a below average result overall. In order to account for the measured deviation, corrected but still off-target steps of 400, 700, 1500, and 3000 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 G403, whose 3366 has no visible smoothing across the entire CPI range. Note that the G403 is moved first and thus receives a slight head start.

Testing is restricted to 2.4 GHz mode as Bluetooth is not suitable for non-casual gaming applications.


First, I'm looking at two xCounts plots—generated at 1600 and 18,000 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." As you can see, such kinks are on display in the second plot, which indicates there being smoothing. Even though the 3369 lacks MotionSync as present on the 3399 (Focus+), SPI timing variance is appreciably low.


In order to determine motion delay, I'm looking at xSum plots generated at 1600, 6200, and 18,000 CPI. The line further to the left denotes the sensor with less motion delay. As the Orochi V2 is using a 3335 variant, an additional delay at the onset of motion could be expected, but that is not the case. Rather, the 3369 behaves similarly to the 3399, for instance, having consistent delay across the entire motion. At 1600 CPI, a motion delay differential of around 1.5 ms has been measured. At and above 6200 CPI, the first level of smoothing is applied, resulting in a motion delay differential of roughly 5 ms. At and above 11,700 CPI, the second level of smoothing is applied, resulting in a motion delay differential of roughly 9 ms, which holds true all the way until 18,000 CPI. These smoothing transition points are within expectations for a 3335 variant.

Speed-related Accuracy Variance (SRAV)

What people typically mean when they talk about "acceleration" is speed-related accuracy variance (or short SRAV). 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 4.5 m/s (which is within the proclaimed PCS range), at which no sign of the sensor malfunctioning can be observed.

Polling Rate Stability

For wired mice, polling-rate stability merely concerns the wired connection between the mouse (SPI communication) and the 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. As you can see, no off-period polls are visible, which has me believe that there is no desynchronization present.


Second, I'm testing the general polling-rate stability of the individual polling rates in wireless mode. Running the Orochi V2 at a lower polling rate can have the benefit of extending battery life. All available polling rates (125, 500, and 1000 Hz) look and perform just fine.

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. 6100 CPI is the highest step without smoothing and shows little jitter that is then taken care of at 6200 CPI. 18,000 CPI has the second level of smoothing but displays significant jitter regardless. Lastly, there is no lens movement.

Lift-off Distance

The Orochi V2 offers two pre-defined LOD levels to choose from, along with the ability to select a pre-calibrated Razer surface. Using the "1 mm" preset, the sensor does track at a height of 1 DVD (1.2<x<2.4 mm, x being LOD height), but not at a height of 2 DVDs. This does not change when selecting the "2 mm" preset. Keep in mind that LOD may vary slightly depending on the mousing surface (pad) it is being used on.

Click Latency

Most gaming mice use mechanical switches for their buttons. By wiring the switches of the test subject together with the switches of a control subject, I'm able to measure click latency very accurately; i.e., standard error of around 0.05 ms. However, this method is not applicable to mice with non-mechanical switches and wireless-only mice in general. As such, other methods ought to be employed, one of which being NVIDIA's Latency Display Analysis Tool (LDAT). The LDAT allows me to measure the entire end-to-end latency between the mouse click and photon transition on the monitor. By establishing the relative difference to a control subject, I'm able to provide values that I consider sufficiently accurate; i.e., standard error of around 0.2 ms. Many thanks go to NVIDIA for providing me an LDAT v2 device.

Click latency has been measured to be roughly +4.1 ms when compared to the Razer Viper 8K, which is considered as the baseline with 0 ms. Standard deviation is 2.5 ms, but since the indicated value is neither the absolute click latency nor the measured end-to-end-latency, standard deviation ends up looking disproportionally large. Comparison data comes from my own testing and has been exclusively gathered with the LDAT.

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