Treat a completed multi-sample window as evidence of the browser-delivered controller signal.
IP-CTL-01 / AXES / BUTTONS / TIME
Controller Trigger Range Test
Measure trigger rest, minimum, maximum, usable range and rapid threshold reversals.
A trigger does not reach full input, returns slowly or activates by itself.
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
Leave both triggers released and note the rest value.
- 02
Press each trigger smoothly through its full travel.
- 03
Release and inspect range, transitions and bounce flags.
Evidence the result should expose.
DIRECT / INFERREDRest value
DIRECT / INFERREDMinimum/maximum
DIRECT / INFERREDUsable range
DIRECT / INFERREDBounce flags
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
Trigger sensor wear
02
Mapping differences
03
User movement around the threshold