Start by separating hardware from software.
A trigger that repeatedly stops below the expected maximum may be affected by a physical trigger lock, a saved profile, calibration, mechanical wear, debris, or the way its current input mode is mapped.
The browser displays normalized values delivered by the operating system, so 1.00 is useful but not a universal factory specification. The important signs are repeatability, smooth travel, full release, and whether the game recognizes the press as complete.
Compare left and right triggers only after matching their physical stops and profile settings. Record the starting result before changing anything.
Work through the likely causes.
- 01
Inspect adjustable trigger stops or hair-trigger locks and set both sides to full travel.
- 02
Press and release each trigger slowly several times while watching for jumps, flat sections, or a value that does not return.
- 03
Switch to a default onboard profile and remove custom trigger curves using supported manufacturer software.
- 04
Reconnect in the recommended PC input mode, then compare USB and wireless behavior if both are supported.
- 05
Check the controller in official configuration or calibration software before considering cleaning or repair.
Check what the browser can see.
Open the full tester to inspect buttons, sticks, triggers, mapping, range, and neutral noise.
Repeat before you conclude.
A repeatable issue across connections, browsers, and native games is stronger evidence of a controller fault than a one-time browser reading. If the problem appears only in one game, review that game’s controller support, deadzone, remapping, and launcher settings.
What to keep in mind
Do not force a trigger beyond its physical stop.
How the browser readings are defined
Our live tools use the standardized browser Gamepad interface and explain its limits in our methodology. Device mappings and proprietary features can still differ by operating system, browser, connection, firmware, and controller mode.
Questions about this issue
Is 0.98 a broken trigger?
Not automatically. Browser normalization and game thresholds vary. If the value is smooth, repeatable, and games recognize full activation, the small difference may not matter.
Can I calibrate the trigger in this website?
No. Use supported operating-system or manufacturer tools. The site measures the input it receives and can help compare before and after.
Why are triggers different in DirectInput mode?
Some DirectInput mappings combine both triggers on one axis or scale them differently. Test the mode your game is designed to use.