Sensor and Performance

The Gamesense Meta is equipped with the PixArt PMW3360. According to specifications, the 3360 is capable of up to 12,000 CPI, as well as a maximum tracking speed of 250 IPS, which equals 6.35 m/s. Out of the box, seven pre-defined CPI steps are available: 400, 800, 1600, 2400, 3600, 5000, and 12,000.

All testing was done on the latest firmware ("1 mm"). 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. As you can see, deviation is consistently positive and quite significant. A below average result overall. In order to account for the measured deviation, adjusted steps of 400, 800, 1500, and 3000 CPI have been used for testing, which resulted in mostly near-perfect accuracy.

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.


First, I'm looking at two xCounts plots—generated at 1600 and 3200 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." As you can see, no such kinks can be observed at 1600 CPI, whereas at 3200 CPI, it is plainly visible. This is in line with what to expect from a 3360, which has 32 frames of smoothing at and above 2100 CPI with SROM 4 or earlier. SPI timing jitter is reasonably low.


In order to determine motion delay, I'm looking at xSum plots generated at 1600, 2100, and 12,000 CPI. The line further to the left denotes the sensor with less motion delay. There is no motion delay differential at 1600 CPI. At and above 2100 CPI, where the 3360 has 32 frames of smoothing, the Meta does something I've only seen on the Sharkoon Light² 180. Basically, there is a shift after roughly 50 ms worth of counts. Before that shift, motion delay is 3 ms, and after it, motion delay is 4 ms, which then slowly goes back down to 3 ms. This is true all the way up to 12,000 CPI. Note the visible dip around the 50 ms mark in the third plot. I do not have an explanation for this unusual behavior, though I also don't consider it harmful.

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 4.5 m/s, which is within the proclaimed PCS range and shows no sign of the sensor malfunctioning.

Polling Rate Stability

On the Meta, polling stability depends on the set polling rate and RGB lighting effect. Both 125 Hz and 500 Hz are stable irrespective of the currently active RGB lighting effect. At 1000 Hz, all RGB lighting effects save for two exceptions will result in occasional off-period polls (first plot below); those two exceptions are "Finger movement" and "Flip up and down," which introduce significant instability (second plot below):


Furthermore, and even more curiously, the "Neon" lighting effect is perfectly stable even at 1000 Hz, rendering it the only RGB lighting effect this applies to.

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 and 3200 CPI, the latter of which already has smoothing applied. The same goes for 12,000 CPI, which shows moderate jitter. Lastly, there is no sensor lens movement.

Lift-off Distance

The Meta offers two pre-defined LOD levels. At the "Low" setting, the sensor does not track at a height of 1 DVD (<1.2 mm). Using the "High" setting, the sensor does track 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

Since mechanical switches are being used for the buttons in most computer mice, debouncing is required in order to avoid unintended double clicks. Debouncing typically adds a delay (along with any potential processing delay), which shall be referred to as click latency. As there is no way to measure said delay directly, it has to be done by comparing it to a control subject, which in this case is the Logitech G203. Within the software, a setting called Debounce Time can be found, which nominally controls click latency, but had no effect whatsoever in my testing. Click latency has been measured to be roughly +1.2 ms when compared to the SteelSeries Ikari, which is considered as the baseline with 0 ms, with standard deviation being 0.82 ms. Comparison data comes from this thread as well as my own testing, using qsxcv's program.