Overclock Validator

What to expect over Wired (USB-C)

Wired USB is the only transport that can reach a controller's native report rate — the HID interrupt pipe polls on a schedule the firmware controls, with no wireless cap imposed on top. Wired jitter comes from the OS input stack and polling cadence; if the graph shows a clean, flat report interval, the pipeline is healthy end to end.

The DualShock 4 is the classic overclock target because its stock wired report rate sits well below the pad's own capability. A flat, consistent interval in this validator is a stronger signal than the headline Hz number alone.

The DualShock 4 is the most documented overclock target in the space because its stock 1000 Hz-capable hardware ships configured well below that ceiling, and the hidusbf descriptor patch has been stable on it for years. Over USB you should see a flat interval very close to 1000 Hz after patching; Bluetooth is a different story — the DS4's wireless report rate is far lower and no descriptor hack changes that, because the connection interval is negotiated by the host stack. Expect the classic result: near-flawless wired pacing, and a clearly separate, noisier wireless band.

The DualShock 4 is the reference target for the hidusbf ecosystem because the descriptor patch has been battle-tested across Windows versions for years, and the pad accepts it without firmware conflicts. One catch specific to the DS4: the touchpad keeps sending its own reports, and some drivers interleave those into the same pipe, which can inject periodic jitter spikes into an otherwise clean wired graph. If you see a repeating spike pattern that tracks roughly once per second, that is the touchpad's report stream, not a failed patch — either ignore those frames when judging the interval or disconnect the pad and reconnect it with the touchpad left untouched during the sample.

A clean wired reading is the baseline every other measurement should be compared against. If the wired graph is noisy, the problem is almost never the pad — check for a hub, an extension cable, or a USB port sharing bandwidth with other high-throughput devices. The browser's gamepad loop also runs on its own cadence, so a 1ms physical report can arrive visibly quantized; treat the browser reading as the conservative floor. A flat interval with an occasional single-frame spike is normal scheduling, while a wandering band suggests OS-level input processing interference.

Is 1000Hz (1ms) always better?

Not necessarily. While 1000Hz reduces average input latency by a few milliseconds compared to 250Hz, it demands more CPU cycles. The key metric is stability (Jitter). An overclock that results in severe frame pacing spikes can feel worse than a rock-solid lower polling rate.

Does hidusbf work on Bluetooth?

No, the popular LordOfMice hidusbf utility only overrides USB device descriptor limits. Overclocking Bluetooth requires changing the polling interval in your OS Bluetooth stack or using custom dongles.