Trigger Test

Introduction

The DeviceHub Trigger Test is a free online LT/RT checker that visualizes left and right trigger travel as the browser Gamepad API exposes it, analog pressure when available, or digital pressed state when the stack only reports buttons. Racing and shooter players who feather throttle and aim-down-sights, technicians validating replacement trigger mechanisms, and shoppers comparing Hall-effect adaptive triggers versus simple pots use this page without installing console companion apps. Open the tool, wake the controller, and slowly pull each trigger while meters reflect normalized values. Healthy analog triggers typically climb smoothly from near zero at rest toward a full value at the stop; sticky midpoints, sudden jumps, or one side stuck at zero while the other works are actionable findings. DeviceHub is honest: the Gamepad API only reports what the browser and OS expose, and mapping may differ for non-standard pads, some devices place triggers on axes, others only on button slots with value 0 or 1. Adaptive trigger resistance on DualSense is a firmware haptic effect, not something a web page can mechanically actuate; this test reads position/pressure reports, not motorized resistance profiles. Because it runs in the browser, locked-down PCs can still triage triggers before a tournament or classroom session. Parents whose kids claim “brake doesn’t work” get a shared visual. Repair shops document asymmetric travel before ordering parts.

What this tool does

The page binds to the active Gamepad, reads the Standard mapping’s trigger button values (often indices 6 and 7 with analog value fields) and any related axes when present, and renders left/right meters plus numeric readouts. You can see rest floor, mid-travel smoothness, and full-depress ceiling. Status copy explains when a pad is digital-only so you do not expect a smooth ramp. Reset clears peak hold after you release. The tool does not calibrate OS trigger deadzones or rewrite Steam configs. Pair with Gamepad Test for general buttons, Joystick Test for sticks, Mapping Test when LT/RT appear swapped, Calibration Test for structured rest snapshots, and Vibration Test when rumble on trigger pull matters in native titles but you are checking browser actuator support separately. Shoulder bumpers remain distinct from triggers, exercise both if a user confuses LB with LT. Some racing wheels expose pedal axes instead of Standard triggers; Mapping Test prevents false “broken RT” conclusions. Live meters are deliberately simple so support calls stay concrete: “left peaks at 0.47 while right reaches 1.0.”

When to use it

Use Trigger Test after sticky or soft triggers, when racing titles ignore half throttle, when shooters treat ADS as binary, after trigger stops were adjusted on elite pads, and when comparing two controllers on one machine. Prefer Mapping Test first if you are unsure which index is LT, Gamepad Test if bumpers work but you have not confirmed basic presence, and Calibration Test when documenting rest floors for tickets. Run it after Bluetooth reconnects, some stacks report stale full values until you release and pull again. Esports staff screening loaner Xbox pads should pull both triggers five times looking for grit or dropouts. Sim racers using a pad for menus while a wheel handles pedals still benefit when verifying the pad’s triggers independently. After kids spill sugary drinks near the shoulder cluster, retest both sides before assuming the whole controller is ruined. Firmware updates that change adaptive trigger behavior will not show resistance here but may change reported curves, re-baseline after updates. Retail returns for “trigger not analog” claims become clearer when you can show a flat binary meter beside a known-good pad that ramps smoothly on the same PC. Tournament organizers lending practice pads should feather both triggers once after each battery swap because wireless brownouts sometimes freeze a mid-travel value until reconnect.

How it works

On the Standard Gamepad mapping, left and right triggers are buttons with an analog value from 0 to 1 in supporting browsers, sometimes mirrored on axes depending on the OS HID driver. DeviceHub displays those fields; it cannot measure spring force or adaptive resistance motors. Non-standard mapping may omit analog values and only flip pressed booleans, DeviceHub surfaces that limitation instead of inventing a fake curve. Polling uses getGamepads() snapshots. No Permissions API prompt is required. Safari and many mobile browsers may lack full trigger analog support, retest on desktop Chromium or Firefox for hardware conclusions. Steam Input, DS4Windows, and vendor remappers can digitalize or rescale triggers before the page sees them; disable remapping for a cleaner hardware read. DualSense adaptive trigger effects are not controllable via standard Gamepad haptics the same way dual-rumble is; do not interpret missing resistance as a failed Trigger Test. HTTPS is used for site consistency; gamepad reading itself needs no getUserMedia. Samples stay local. Background tabs may update less smoothly, keep the page visible while feathering travel. Compare wired versus wireless when mid-travel stutters; radio loss often looks like a sticky sensor. Elite adjustable stops change the physical end of travel without guaranteeing the browser still sees a full 1.0, capture peaks after every stop change. If Chrome shows analog ramps while another engine only flips pressed, document both engines when filing web-game bugs so developers know whether to read button.value or treat triggers as digital.

Step-by-step instructions

1. Open Trigger Test over HTTPS, connect the controller, and press a face button so the Gamepad appears; pick the correct device if several are connected.
2. Fully release both triggers and note the resting meter floors, ideally near zero. Non-zero rest can indicate sticky mechanisms or remapper offsets.
3. Slowly pull the left trigger through its entire travel, watching for smooth increase, sudden jumps, or a ceiling below full scale, then release and confirm return to rest.
4. Repeat with the right trigger and compare peaks and smoothness between sides; asymmetry is a common warranty evidence point.
5. If meters stay binary or sides appear swapped, open Controller Mapping Test to identify whether your pad exposes analog values and which indices map to LT/RT.
6. Finish by closing the tab, no permission revoke is required because the Gamepad API does not use a privileged permission prompt.

Common problems

Binary on/off meters usually mean the browser only received digital trigger buttons, or a remapper flattened analog range. Swapped LT/RT is a mapping issue, check raw indices. One side dead while bumpers work points to a trigger mechanism or flex cable fault. Rest values stuck high suggest sticky triggers or debris. Adaptive trigger “feel” cannot be verified here, only reported travel. Mobile Safari gaps are platform limits. Racing pedals on a wheel base may not appear as Standard triggers at all. If native games show analog travel but this page does not, remappers or exclusive mode may be intercepting, test with Steam closed. Cheap clones sometimes invert full-press values; Mapping Test plus a second known-good pad isolates that quirk. Remote sessions often quantize triggers; prefer local USB for RMA videos. Hair triggers on competitive FPS pads can make mid-travel hard to hold steady, use slow pulls and watch peaks rather than hunting a perfect half-press screenshot. If meters freeze mid-pull then jump on release, suspect wireless packet loss or a failing potentiometer rather than a CSS animation glitch on the page.

Privacy explanation

Trigger values stay in your browser session for on-page meters only. DeviceHub does not upload pull curves, gameplay telemetry, or controller ids. No camera or microphone permission is requested. Closing the tab clears peaks and live state. Shared lab machines are appropriate for hardware triage when you only exercise triggers. Private windows help avoid remapper extensions. Support recordings should focus on the meters without showing unrelated account pages. Nothing continues reading the pad after you leave. Clearing site storage is unnecessary for privacy because no privileged gamepad grant was stored for this diagnostic.