Triggers
Connect a controller and press a button if the browser has not exposed it yet.
Gamepad Trigger Test: Normalized LT/RT Values and Reported Input Range
Inspect normalized controller trigger values reported by the Gamepad API. These values do not measure physical pressure or travel distance.
What this test checks
- Controller API detection
- Button, stick, trigger, or haptic behavior
- Live polling and input state
- Compare Left And Right Trigger Range
How to read the result
Triggers depends on the browser Gamepad API, so connect the controller and press a button first. Repeated drift, low polling, or missing button states usually deserve a second pass with the related controller diagnostics.
Connect A Controller With Analog Triggers
Many modern controllers expose analog trigger values. This test checks whether the browser receives intermediate values rather than only on/off states. Those values do not measure physical pressure or travel distance.
Squeeze Each Trigger Slowly
Press LT and RT gradually and watch whether their normalized values rise smoothly from rest to maximum. This matters for throttle, braking and camera control; it does not measure physical force or travel distance.
Compare Left And Right Trigger Range
The live values help users spot a trigger that does not reach full range, sticks above zero, or jumps unevenly during travel.
Retest After Cleaning Or Calibration
Trigger readings can improve after cleaning, recalibration, or reconnecting the controller. A second run gives a clearer before-and-after comparison.
Related I/O Checkup Tools
What does Triggers measure?
Inspect normalized controller trigger values reported by the Gamepad API. These values do not measure physical pressure or travel distance.
Do I need to install anything for Triggers?
No. Triggers runs directly in a modern browser. Some checks may ask for permission when they need camera, microphone, gamepad, pointer lock, touch, or audio output access.
Are results uploaded?
The test runs in your browser and uses local input events or browser hardware APIs for the visible diagnostics.
Why should I run related tests too?
Related tools help separate hardware issues from browser timing, display behavior, input device settings, or permission problems, which makes the final diagnosis more useful.
Detailed Testing Guide
Controller symptom
This controller page checks one part of the Gamepad API signal instead of assuming one button press proves the whole pad is healthy.
Start with a baseline run before changing device settings. Record any repeated symptom so the next comparison is useful.
API evidence
Watch button state, stick axes, trigger values, vibration response, polling updates, and whether the controller stays visible.
Watch Controller API detection, Button, stick, trigger, or haptic behavior, Live polling and input state, Compare Left And Right Trigger Range. These observations come from the browser; they do not reveal hidden firmware or factory calibration data.
Controller test method
Press a button to expose the pad, then test one control group at a time.
Keep the test conditions stable. Changing browser, cable, port, lighting, surface, volume, grip, or selected device all at once makes the result harder to trust.
Result reading
Browser support, Bluetooth latency, driver mapping, and firmware can all change what the page receives.
A repeated pattern matters more than a single spike. When something looks wrong, confirm it with another pass and compare a related tool before deciding the device itself is defective.
Limits and next checks
Use button, stick drift, trigger, vibration, and polling tests together for a complete controller pass.
For a closer comparison, try Gamepad Button Test, Stick Drift Test, Trigger Test, Polling Rate Test. Keep the same device and connection while you investigate the next symptom.