Sensor and Performance
The Waizowl OGM Cloud is equipped with the PixArt PAW3395. According to specifications, the 3395 is capable of up to 26,000 CPI, as well as a maximum tracking speed of 650 IPS, which equals 16.51 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 one 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 inconsistent and rather large, which is a subpar result. In order to account for the measured deviation, adjusted steps of 400, 800, 1650, and 3250 have been used for testing. Of note is that some input values will not be applied, such as 850. In addition, results are far from consistent, so the values given above may vary.
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 PMW3366 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.
Wired testing
First, I'm looking at two xCounts plots—generated at 1600 and 26,000 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." Neither plot shows any kinks, strongly suggesting there not being any smoothing across the entire CPI range.
The OGM Cloud also allows enabling MotionSync, which effectively synchronizes SPI reads with USB polls, resulting in very low SPI timing jitter as seen above.
In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 26,000 CPI, both without (first row) and with (second row) MotionSync. The line further to the left denotes the sensor with less motion delay. Without MotionSync, there is no motion delay differential at 1600 and 26,000 CPI. Enabling MotionSync adds a bit more than 0.5 ms worth of motion delay.
Wireless testing
Not much changes when running the OGM Cloud in wireless mode, aside from a different sensor run mode being used.
Upon enabling MotionSync, SPI timing is tightened.
The OGM Cloud also allows enabling a so-called high-speed mode, which changes the sensor run mode to corded mode. MotionSync (second plot) once again tightens SPI timing.
In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 26,000 CPI. The line further to the left denotes the sensor with less motion delay. Without MotionSync (first row), a motion delay differential of roughly 0.5 ms is present at both 1600 and 26,000 CPI. With MotionSync (second row), a motion delay differential of a bit more than 1 ms can be measured.
With high-speed mode enabled, but MotionSync disabled (first plot), the motion delay differential is reduced to zero, whereas enabling MotionSync (second plot) once again increases motion delay by a bit more than 0.5 ms.
Speed-related Accuracy Variance (SRAV)
What people typically mean when they talk about "acceleration" is speed-related accuracy variance (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 results in no observable sign of the sensor malfunctioning.
Polling Rate Stability
Considering the OGM Cloud is usable as a regular wired mouse as well, I'll be testing polling rate stability for both wired and wireless use.
Wired testing
All the available polling rates (125, 250, 500, and 1000 Hz) look and perform fine.
Wireless testing
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. 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 OGM Cloud at a lower polling rate can have the benefit of extending battery life. All the available polling rates look and perform 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. Even though it doesn't look that way, there is no difference in jitter between having ripple control disabled (second row) and enabled (third row) at 26,000 CPI, and I've been able to corroborate that this setting indeed is not functional. Lastly, there is no sensor lens movement.
Lift-off Distance
The OGM Cloud offers two pre-defined LOD levels. At the "1 mm" setting, the sensor does not track at a height of one DVD (<1.2 mm). Using the "2 mm" setting, the sensor does track at a height of one DVD (1.2 mm<x<2.4 mm, with x being LOD height), but not at a height of two DVDs. Keep in mind that LOD may vary slightly depending on the mousing surface (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. All the listed values have been gathered without any sensor motion. If latency differs between no motion and motion, it will be noted as such.
In wired mode and using a debounce time of 0/1 ms, click latency has been measured to be roughly 1.1 ms, with standard deviation being 0.41 ms. In wired mode and using a debounce time of 2 ms, click latency has been measured to be roughly 2.1 ms, with standard deviation being 0.44 ms. In wireless mode and using a debounce time of 0/1 ms, click latency has been measured to be roughly 1.5 ms, with standard deviation being 0.29 ms. The 0 and 1 ms debounce time settings are equivalent, and scaling is linear.
Using the 4K Wireless Dongle, a polling rate of 1000 Hz, and a debounce time of 0 ms, click latency has been measured to be roughly 0.7 (0.70) ms, with standard deviation being 0.27 ms. Using the 4K Wireless Dongle, a polling rate of 2000 Hz, and a debounce time of 0 ms, click latency has been measured to be roughly 0.7 (0.68) ms, with standard deviation being 0.28 ms. Using the 4K Wireless Dongle, a polling rate of 4000 Hz, and a debounce time of 0 ms, click latency has been measured to be roughly 0.6 (0.59) ms, with standard deviation being 0.24 ms. With sensor motion present at 4000 Hz, click latency is increased to 0.8 (0.80) ms, with standard deviation being 0.25 ms.
The main button switches were measured to be running at 3.11 V. I'm not aware of the voltage specifications of the used Huano switches, but consider it very likely that they are running within specifications.
