ASUS ROG Keris II Ace Review 14

ASUS ROG Keris II Ace Review

by
pzogel
,
on ,
in Mice.
Manufacturer: ASUS
Testing 8000 Hz Wired & 4000 Hz Wireless »

Sensor and Performance

The ASUS ROG Keris II Ace is equipped with the AimPoint Pro. According to specifications, the AimPoint Pro is capable of up to 42,000 CPI, as well as a maximum tracking speed of 750 IPS, which equals 19.05 m/s. Out of the box, four pre-defined CPI steps are available: 400, 800, 1600, and 3200.

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

CPI Accuracy

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

Motion Delay

What is 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.

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 42,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. Due to MotionSync being permanently enabled, SPI timing jitter is very low.


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

Wireless testing

Not much changes when running the Keris II Ace in wireless mode as SPI timing jitter and general tracking are virtually on the same level as when wired.


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

What is Speed-related Accuracy Variance?
What people typically mean when they talk about "acceleration" is speed-related accuracy variance (or 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

What is 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 causes no observable sensor malfunction.

Polling Rate Stability

What is Polling Rate?
Strictly speaking, one has to distinguish between polling rate and report rate. Polling rate describes the number of times the host (typically the user's PC) polls the device, whereas report rate describes the number of times the device reports to the host. Thus, a device can be set to be polled a certain number of times per second, but report at a lower rate regardless, either by design (i.e., if there have been no movement changes since the previous report) or not by design, and the latter case is what will be tested under the moniker of "polling rate stability" hereafter. To this end, the mouse is set to a sufficiently high CPI step and moved at a sufficiently high velocity to ensure that the maximum possible report rate is achieved at all times. Polling rate can be conceived of as a frequency, which is typically measured in Hz, though a more apt way of looking at it would be as an interval. For reference, a frequency of 1000 Hz is tantamount to an interval of 1 ms. Likewise, a frequency of 125 Hz would translate to an interval of 8 ms, and a frequency of 8000 Hz to an interval of 0.125 ms.

Wired testing


All the available polling rates (125, 250, 500, or 1000 Hz) are fully stable.

Wireless testing
For wired mice, polling rate stability merely concerns the wired connection between the mouse (SPI communication) and 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 Keris II Ace at a lower polling rate can have the benefit of extending battery life. All polling rates are fully stable.

Paint Test

What is the 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. There is no jitter visible at 1600 CPI. 21,000 CPI already shows major jitter, which is increased to massive levels at 42,000 CPI. This is in line with what to expect from a sensor lacking any smoothing. Lastly, there is no lens movement.

Lift-off Distance

What is Lift-off Distance?
Lift-off distance describes the distance the mouse can be lifted off the tracking surface until the sensor no longer tracks.

The Keris II Ace offers multiple ways of adjusting LOD: several pre-calibrated surface options, two pre-defined LOD levels (high/low), and manual calibration. By default, the "no calibration" preset is active, which has the sensor not track at a height of 1 DVD if set to "low." If set to "high," the sensor tracks at a height of 1 DVD, but not at a height of 2 DVDs (1.2 mm<x<2.4 mm, x being LOD height). Furthermore, several pre-calibrated surfaces are available to choose from, which then can be fine-tuned manually by adjusting the high/low-selection. Performing a manual calibration may lower LOD beyond the default. In my case, doing so resulted in an LOD below 1 DVD.

Click Latency

What is 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 at a polling rate of 125/250/500/1000 Hz, click latency has been measured to be 0.3 (0.25) ms, with standard deviation being 0.01 ms. In wired mode and at a polling rate of 2000/4000/8000 Hz, click latency has been measured to be 0.4 (0.35) ms, with standard deviation being 0.05 ms. In wireless mode and at a polling rate of 1000/2000/4000 Hz, click latency has been measured to be 0.5 (0.49) ms, with standard deviation being 0.05 ms. Please note that these values have been exclusively gathered while using the Polling Rate Booster. NVIDIA Reflex readings are supported, but will be off by 0.1 ms for readings in wireless operation.
View as single page
Next Page »Testing 8000 Hz Wired & 4000 Hz Wireless
View as single page
Sep 27th, 2024 10:21 EDT change timezone

Latest GPU Drivers

New Forum Posts

Popular Reviews

Controversial News Posts