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 browsers using the standard Gamepad mapping, the left and right analog triggers are normally exposed as button indices 6 and 7. Non-standard controllers may map them differently.
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

How to test controller triggers

  1. Connect the controller and activate it with any button.
  2. Release both triggers completely and confirm the live values settle close to 0.
  3. Press the left trigger slowly from rest to full travel and watch for a smooth increase.
  4. Repeat on the right trigger. A full press should normally approach 1.000 on standard-mapped analog triggers.
  5. Release both and use the release check to compare their resting values.

How to read the result

A healthy analog trigger normally starts near zero, increases smoothly as you press it, reaches close to its maximum value, then returns near zero when released.

This page uses practical diagnostic bands, not manufacturer calibration specifications. A low peak or high resting value should be repeated several times and compared by USB/Bluetooth or another browser before treating it as a hardware fault.

Common trigger problems

  • High resting value: the trigger appears partially pressed while untouched.
  • Low peak: a full physical press never reaches the expected upper range.
  • Uneven travel: the value jumps, stalls or changes inconsistently during a slow press.
  • Left/right mismatch: one trigger reaches clearly different resting or peak values than the other.

Browser and mapping limitations

Standard-mapped controllers commonly expose LT/L2 at index 6 and RT/R2 at index 7, but this is not guaranteed for every device. Some controllers can expose triggers as axes or use a non-standard mapping.

If the trigger bars do not move but other controller buttons work, use the full controller test to inspect all button and axis values before concluding that the trigger is broken.

Controller trigger test FAQ

What should a fully pressed trigger read?

On many standard-mapped controllers, a full press approaches 1.000. Small variation can occur because of hardware calibration, firmware, drivers and browser behavior.

Why does my trigger never return to exactly zero?

A tiny non-zero value can be normal. A consistently elevated resting value that affects games is more significant than a single small reading on this page.

Can this test recalibrate my triggers?

No. GearCheck Lab only reads browser-reported input. It does not write firmware settings or change operating-system calibration.