Sensor and Performance

The ASUS M3 Gen II is equipped with the PixArt PAW3318. According to specifications, the 3318 is capable of up to 8000 CPI, as well as a maximum tracking speed of 300 IPS, which equals 7.62 m/s. Out of the box, five pre-defined CPI steps are set: 400, 800, 1600, and 3200.

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 minimal, which is an excellent result. In order to account for the measured deviation, adjusted steps of 400, 800, 1600, and 3150 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 8000 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.



In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 8000 CPI. The line further to the left denotes the sensor with less motion delay. Motion response isn't consistent across the entire motion, as at the onset, the differential is small, but gets progressively larger until it settles around 4 ms, both at 1600 and 8000 CPI.

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

All of the available polling rates (125, 250, 500, and 1000 Hz) are fully stable. Polling stability is unaffected by any RGB lighting effects.

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. 3200 CPI already shows minor jitter, which is amplified to moderate levels at 8000 CPI. Lastly, there is no sensor lens movement.

Lift-off Distance

The M3 Gen II offers various ways of adjusting LOD. By default, the "no calibration" preset is active, which has the sensor barely track at a height of 1 DVD (<1.2 mm), and which then can be fine-tuned by choosing between "low" or "high." However, I've found that both settings result in the same LOD, having me believe that this selection is indeed not functional. In addition, there are several presets for various ASUS mouse pads, which may net a slightly different LOD. Performing a manual calibration is also possible and may lower LOD beyond the default. 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. All of the listed values have been gathered without any sensor motion. If latency differs between no motion and motion, it will be noted as such.

Click latency has been measured to be 12.7 ms, with standard deviation being 0.50 ms.