How We Test Controller Inputs

The method, scope and limits of the tools.

Observations, not diagnoses

The site shows data exposed by the Gamepad API, character inputs and mouse events. It does not certify hardware faults, calibration, universal compatibility or physical input latency.

Rest measurement

Over five seconds, the page observes axes 0/1 and 2/3. For each pair it computes sqrt(x² + y²) × 100. The report stores the largest radial value seen across either stick, the number of samples and the time window. A non-zero value is not proof of a fault.

Interruptions and mapping

Hiding the tab or changing the controller connection interrupts a measurement, which must be repeated. The illustration uses a generic layout and highlights only some buttons. Read numbered inputs when a mapping is non-standard.

Demo and device validation

Demo mode is optional, simulated and labelled in the interface and exports. Software and interface tests do not replace testing each physical model. We do not claim to have checked a device without a specific validation record.

Deadzones and screen checks

The deadzone threshold is visual and does not alter hardware. Solid color fields allow visual inspection; they neither repair pixels nor calibrate a display. True USB polling frequency and end-to-end physical latency are not measured here.

Technical references