Sensor and Performance

The Logitech Pro X Superlight 2 is equipped with the HERO 2. According to specifications, the HERO 2 is capable of up to 32,000 CPI, as well as a maximum tracking speed of 500 IPS, which equals 12.7 m/s. Out of the box, five pre-defined CPI steps are available: 800, 1200, 1600, 2400, and 3200.

All testing was done on the latest firmware (32.1.20/7.1.10). As such, results obtained on earlier firmware versions may differ from those presented hereafter.

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. There is no deviation at all, which is a perfect result.

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 without special equipment, it is done by comparison with a control subject that has been determined to have consistent and low motion delay. In this case, the control subject is a Logitech G403, whose 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.

Wired testing

First, I'm looking at two xCounts plots—generated at 1600 and 32,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.


In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 32,000 CPI. At both 1600 and 32,000 CPI, a motion delay differential of roughly 0.5 ms can be measured, further confirming there not being any smoothing across the entire CPI range.

Wireless testing

Not much changes when running the Pro X Superlight 2 in wireless mode as SPI timing jitter and general tracking are virtually on the same level as when wired.


Once again, 1600 and 32,000 CPI are tested. At both 1600 and 32,000 CPI, a motion delay differential of roughly 0.5 ms can be measured.

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 Pro X Superlight 2 is usable as a regular wired mouse as well, I'll be testing polling rate stability for both wired and wireless use.

Wired testing


Of the available polling rates (125, 250, 500, and 1000 Hz), 125, 250, and 500 Hz are fully stable, whereas 1000 Hz displays periodic off-period polls.

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. Several 2 ms polls are visible, though it is unclear whether these are causally related to a desynchronization drift.



Second, I'm testing the general polling-rate stability of the individual polling rates in wireless mode. Running the Pro X Superlight 2 at a lower polling rate can have the benefit of extending battery life. Much like in wired mode, 125, 250, and 500 Hz are fully stable, whereas 1000 Hz displays periodic off-period polls.

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. 16,000 CPI already displays moderate jitter, which is amplified to major levels at 32,000 CPI. This is in line with what to expect from a sensor lacking any smoothing. Lastly, there is no sensor lens movement.

Lift-off Distance

The Pro X Superlight 2 offers three pre-defined LOD levels. At the "Low" or "Medium" settings, the sensor does not track at a height of 1 DVD. If set to "High," the sensor tracks at a height of 1 DVD (1.2 mm<x<2.4 mm, with x being LOD height), but not at a height of 2 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. If latency differs between no motion and motion, it will be noted as such.

In wired mode, click latency has been measured to be 0.5 ms, with standard deviation being 0.26 ms. In wireless mode at 1000 Hz, click latency has been measured to be 1.4 ms, with standard deviation being 0.18 ms. In wireless mode at 2000 Hz, click latency has been measured to be 1.0 ms, with standard deviation being 0.13 ms. In wireless mode at 4000 Hz, click latency has been measured to be 0.9 ms, with standard deviation being 0.10 ms. There is no difference in click latency between the "hybrid" and "optical only" switch configuration modes.