Home›Gamepad›Controller Deadzone Test

🎮 Gamepad

Controller Deadzone Test

Estimate stick distance from center and suggested deadzone.

🔒 Local-first◉ Modern browser recommended.

🎮

Controller Deadzone TestGamepad

Local-first

Ready

Gamepad values may be processed by firmware, drivers and the browser. These are not raw sensor measurements.

Mapping—

Index—

Connection state—

Button coverage—

Controller map

Standard mapping uses named controls. Unknown mapping uses button indices and user-selected axis pairs.

● Pressed · ✓ Tested · ○ Untested

Rest uses 3 seconds of visible snapshots: mean center, RMS noise around the mean, maximum offset + 0.01 deadzone estimate. Center magnitude above 0.05 suggests rechecking drift; full-circle sector radius below 0.9 suggests rechecking range.

Choose separate axis pairs for each stick. To swap them, clear one selection first.

Left stick

Axis pair

Dashed circle: radius 1 reference. Purple trace: browser coordinates. A square trace alone does not prove a hardware fault.

X—

Y—

Magnitude—

Angle—

Center offset—

Rest noise—

Center X—

Center Y—

Average offset—

Maximum offset—

Suggested deadzone—

Min X—

Max X—

Min Y—

Max Y—

Range X—

Range Y—

Circularity and advanced analysis

Minimum radius—

Maximum radius—

Mean radius—

Circularity deviation—

Asymmetry—

Eccentricity—

Sector coverage—

Missing sectors—

Axis-aligned samples—

Smallest observed step—

Center crossing gap—

Outer plateau samples—

Response asymmetry—

Circle metrics use the maximum radius in 36 sectors. Complete every sector; missing sectors are untested. Deviation is percent distance from a unit circle; eccentricity is a bounding-envelope estimate.

Advanced indicators count axis-aligned samples, coordinate steps, center crossing gaps and repeated outer values. Motion speed and firmware processing affect them; they do not prove snapping, quantization or a deadzone defect.

Right stick

Axis pair

Dashed circle: radius 1 reference. Purple trace: browser coordinates. A square trace alone does not prove a hardware fault.

X—

Y—

Magnitude—

Angle—

Center offset—

Rest noise—

Center X—

Center Y—

Average offset—

Maximum offset—

Suggested deadzone—

Min X—

Max X—

Min Y—

Max Y—

Range X—

Range Y—

Circularity and advanced analysis

Minimum radius—

Maximum radius—

Mean radius—

Circularity deviation—

Asymmetry—

Eccentricity—

Sector coverage—

Missing sectors—

Axis-aligned samples—

Smallest observed step—

Center crossing gap—

Outer plateau samples—

Response asymmetry—

Triggers

LT / L2

Current—

Minimum—

Maximum—

Return to zero—

Reaches full range—

Large value changes—

RT / R2

Current—

Minimum—

Maximum—

Return to zero—

Reaches full range—

Large value changes—

Trigger traces show values over time, not a calibrated physical response curve. Changes above 0.5 between snapshots require a slow retest; dropouts cannot be distinguished from fast release.

Browser-observed gamepad update rate

Samples—

Median interval—

P95—

Jitter—

Estimated updates/s—

Timing uses positive Gamepad.timestamp differences within 250 ms. RAF may miss updates. At least 10 intervals are required; this is neither input latency nor USB polling rate.

Haptics

Summary

Controller selection

How it works

Use the interactive panel above and watch the live measurements. Results depend on events and capabilities exposed by your browser.

Runs in your browser

Core tests are processed locally in your browser. Camera and microphone streams are not intentionally uploaded by Testvexa.

FAQ

Does this test upload my input?

Core interaction is processed in your browser. Testvexa does not intentionally upload camera or microphone streams.

Can browser limitations affect the result?

Yes. Browsers expose different hardware APIs, so unsupported access is not the same as faulty hardware.