Skip to main content
GEARCHECK LAB
Controller Lab // Analog Input Diagnostics

CONTROLLER TRIGGER TEST

Measure LT/RT or L2/R2 trigger output from rest to full press. Watch live analog values, record the highest value reached, check whether the trigger returns close to zero after release, and compare left and right behavior.

LOCAL TESTTrigger data is read with the browser Gamepad API and stays in this browser session.
Live diagnostic

Analog trigger travel

AWAITING CONTROLLER
Connect a controller and press any button.For the standard Gamepad mapping, the left and right analog triggers are normally exposed as button indices 6 and 7. If the browser reports a non-standard mapping, this page keeps showing raw button 6/7 values but stops treating them as verified LT/RT trigger channels.
LEFT TRIGGER // LT / L2

Button index 6

0%
REST50%FULL
LIVE0.000
PEAK0.000
LOWEST SEEN0.000
WAITING FOR INPUT
RIGHT TRIGGER // RT / R2

Button index 7

0%
REST50%FULL
LIVE0.000
PEAK0.000
LOWEST SEEN0.000
WAITING FOR INPUT

Release checks appear here after both triggers are fully released.

How to run a repeatable controller trigger test

  1. Connect the controller, press any button, and confirm that this page reports a standard mapping before interpreting LT/L2 and RT/R2 labels.
  2. Leave both triggers untouched for several seconds. Note each live value and capture a release check.
  3. Press the left trigger slowly from rest to its physical stop, pause, then release it fully. Repeat three times.
  4. Do the same with the right trigger. Watch for a steady rise, a repeatable peak, and a return close to the earlier rest value.
  5. Reset peaks and repeat once more. Compare the two sides and ignore a single isolated spike unless it repeats.
  6. If a result is suspicious, compare USB with Bluetooth or another browser before making a repair or replacement decision.

What the trigger values mean

The live value is the current browser-reported analog position from 0.000 to 1.000. Peak is the highest value seen since reset; lowest seen is the smallest. The release check averages about 0.7 seconds of untouched input so one frame does not decide the result.

The verdict bands are practical screening cues, not manufacturer calibration limits. “Near-full press + rest observed” means the page saw a peak of at least 0.95 and a minimum no higher than 0.05; it does not certify the trigger.

Worked trigger result examples

  • Left peaks at 0.992 and rests at 0.004: the browser saw near-full travel and a near-zero release. Repeat to confirm consistency.
  • Right peaks around 0.82 on three slow presses: compare connection modes and another browser; if the limit repeats and affects a game, inspect calibration or warranty options.
  • Left rests near 0.11 while untouched: recapture the release check after several full presses. A repeatable elevated value may explain unintended acceleration or braking.
  • Values jump from 0.30 to 0.75 during a slow press: this page shows the jump but cannot identify whether hardware, firmware, mapping or the browser caused it.

Trigger symptoms and next checks

  • Nothing moves: use the full controller test to find whether the device exposes triggers as axes or different button indices.
  • One side stops early: reset, repeat three presses, then compare USB/Bluetooth and another browser.
  • Input remains after release: capture two release samples and check whether the game itself applies a trigger threshold.
  • Only one game is affected: check that game's bindings, trigger thresholds and controller profile before blaming the hardware.
  • Both sides look wrong: update controller firmware or drivers when the manufacturer provides them, then reconnect and retest.

Standard and non-standard controller mappings

For a browser-reported standard gamepad mapping, LT/L2 and RT/R2 are normally button indices 6 and 7. When the mapping is non-standard, this page keeps showing raw button 6 and 7 values but labels them as unverified rather than claiming they are the physical triggers.

Some devices expose analog triggers as axes. If the trigger bars stay still while the controller works elsewhere, inspect all raw inputs in the full controller test.

Browser, game and hardware limits

The Gamepad API reports what the browser receives after device firmware, drivers and operating-system processing. A game can add its own threshold, remapping or response curve, so the same physical press may behave differently there.

This page cannot inspect springs, stops, Hall sensors, potentiometers, wiring or solder joints. It is a screening measurement, not a repair diagnosis, manufacturer calibration or warranty decision.

Controller trigger test FAQ

What should a fully pressed controller trigger read?

On many standard-mapped controllers, a full press approaches 1.000. Treat that as a browser-observed endpoint, not a universal manufacturer specification, and compare repeated presses on both sides.

Why does my trigger never return to exactly zero?

A tiny non-zero value can be normal. A repeatable resting value that remains elevated after several releases and causes unwanted input in games is more meaningful than one small reading.

Can this test recalibrate or repair my triggers?

No. GearCheck Lab reads values exposed by the browser. It cannot change firmware, operating-system calibration, game settings or physical trigger parts.

Why do the bars not move although other controller buttons work?

The device may use a non-standard mapping or expose triggers as axes instead of standard button indices 6 and 7. Open the full controller test to inspect every reported button and axis.

Should I compare USB and Bluetooth results?

Yes when a result looks suspicious. Connection mode, drivers, firmware and browser behavior can change what reaches the Gamepad API, so a second connection or browser is a useful control.

Can this page prove that a trigger sensor is worn out?

No. It can reveal repeatable browser-visible resting and endpoint behavior, but it cannot inspect springs, Hall sensors, potentiometers, stops, wiring or firmware directly.