HyperX Pulsefire Haste Review 4

HyperX Pulsefire Haste Review

Software & Lighting »

Sensor and Performance

The HyperX Pulsefire Haste is equipped with the PixArt PAW3335. According to specifications, the 3335 is capable of up to 16,000 CPI, as well as a maximum tracking speed of 400 IPS, which equals 10.16 m/s. Out of the box, four pre-defined CPI steps are available: 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 beyond ridiculous and exclusively positive. This is the single largest deviation I've measured so far. A very poor result overall. Though the software allows for increments of 50, the sensor does not, so only values that are multiples of 100 are in fact applied. In order to account for the measured deviation, adjusted steps of 300, 700, 1300, and 2600 CPI have been used for testing. These steps are still considerably off, however.

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 16,000 CPI—to quickly gauge whether there is any smoothing, which would be indicated by any visible "kinks." As you can see, no kinks are in sight. Thus, we can conclude that the 3335 implemented in the Pulsefire Haste has no visible smoothing across the entire CPI range. We also see rather low SPI timing variance, which results in tight count distribution.


In order to determine motion delay, I'm looking at xSum plots generated at 1600 and 16,000 CPI. The line further to the left denotes the sensor with less motion delay. Neither 1600 nor 16,000 CPI show any difference in motion delay. This merely confirms the results seen above.


What people typically mean when they talk about "acceleration" is speed-related accuracy variance (or, for short, 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


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), at which no sign of the sensor malfunctioning can be observed.

Polling Rate Stability

Polling stability is rather curious on the Pulsefire Haste. If everything is going well, all four available polling rates (125/250/500/1000 Hz) look perfectly stable. That said, 125 Hz consistently showed periodic outliers on my system:


Occasionally, there is the odd case of periodic outliers on other polling rates as well:


Things change when HyperX NGENUITY is running. What used to be nice looking plots are now turned into horrible abominations:

In short, I strongly recommend closing NGENUITY whenever possible, especially when gaming.

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. Minor jitter is visible at 5000 CPI, which is further amplified at 10,000 CPI. Finally, 16,000 CPI shows major jitter, as expected from a sensor lacking any smoothing. Lastly, no sensor lens rattle can be observed.

Lift-off Distance

The Pulsefire Haste does not offer any sort of LOD adjustment options. This is unfortunate as the 3335 would be fully capable of it. At the default (and only) setting, the sensor does not track at a height of 1 DVD (<1.2 mm). 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 G100s. Click latency has been measured to be roughly +4.5 ms when compared to the SteelSeries Ikari, which is considered as the baseline with 0 ms. Please keep in mind that the measured value is not the absolute click latency. Comparison data comes from this thread as well as my own testing, using qsxcv's program.
Next Page »Software & Lighting
View as single page
Dec 25th, 2024 19:25 EST change timezone

New Forum Posts

Popular Reviews

Controversial News Posts