Treat a completed multi-sample window as evidence of the browser-delivered controller signal.
IP-CTL-01 / AXES / BUTTONS / TIME
Controller Stick Drift Test
Capture a five-second idle window and separate persistent center offset from isolated stick noise.
A character or camera moves while the controller is untouched.
This focused entry uses the shared Controller protocol. The measurement logic and Evidence version remain identical to the complete lab.
Remove the easiest false alarms first.
01
Connect one controller, press a button and keep this tab visible.
02
Place the controller on a stable surface before any idle capture.
03
Test USB and Bluetooth as separate sessions instead of changing mid-run.
Run one repeatable protocol.
- 01
Connect the controller and press a button so the browser exposes it.
- 02
Place it on a stable surface and release both sticks.
- 03
Run the five-second idle capture, then confirm a significant result once.
Evidence the result should expose.
DIRECT / INFERREDP95 center offset
DIRECT / INFERREDMedian radial offset
DIRECT / INFERREDJitter
DIRECT / INFERREDConfidence
Separate observed, review and inconclusive.
Repeat the same protocol twice with the same connection before escalating persistent drift, bounce or missed transitions.
No Gamepad API signal, an unsupported actuator or one release spike cannot prove a physical controller fault.
Start with the likely path, then retest.
01
Worn stick sensor
02
Calibration or remapping
03
Unstable Bluetooth path