What makes a trigger analog?
This page labels a rolling signal analog after it contains at least eight distinct values rounded to three decimals. Fewer steps are described as digital or discrete.
ANALOG TRIGGER TEST · LOCAL INPUT
Analog Trigger Tester
Compare LT and RT travel, value steps, release baselines, and recent history without uploading controller input.
LT / RT · ROLLING LOCAL EVIDENCE
No controller selected
Compare each trigger independently across the newest ten seconds of browser-observed input.
No controllers detected.
Waiting for controller
Browsers expose a controller after it sends an input. Keep this page active, then press a physical controller button.
- Index
- Not available
- Mapping
- Not available
- Connected
- No
- Stale
- No
Local report
The report is created in this browser and downloaded directly to your device. Nothing is uploaded.
This tool exports summary data only.
Two independent signals
Understand trigger travel and release
This analog trigger tester follows left and right trigger values independently. Each side keeps its own current value, recent minimum and maximum, observed range, release baseline, value-step classification, and ten-second trace. A confirmed mapping is required before semantic LT or RT evidence appears.
Four deliberate steps
How to test analog triggers
01
Connect and choose
Connect a controller, activate it with a physical input, and choose the intended device when more than one is available.
02
Release both triggers
Leave LT and RT untouched long enough to collect at least ten low samples for each release baseline.
03
Sweep each trigger
Press and release one trigger slowly, then repeat with the other so their travel and value steps stay easy to compare.
04
Read the rolling evidence
Compare current value, extrema, observed range, release baseline, and the newest ten seconds of each trace.
Evidence boundary
Measurement limitations
These are browser-observed values after controller firmware, transport, operating-system, driver, mapping, and page scheduling effects. A stepped trace can reflect the exposed mapping as well as the physical control. The results do not certify trigger hardware, manufacturer tolerances, or the cause of an unusual value.
When a trace stays flat
Troubleshooting trigger input
- Keep this tab active and press a physical controller control after connecting.
- Choose the intended controller when the selector lists multiple devices.
- For an unmapped controller, watch raw values and assign LT and RT to two different buttons.
- Try another cable, USB port, Bluetooth pairing, or current desktop browser if values remain unavailable.
Plain answers
Frequently asked questions
Why is the release baseline unavailable?
A baseline needs at least ten values at or below 0.10 in the current rolling window. Keep the trigger released while the page remains active.
Why did an earlier maximum disappear?
Statistics use a rolling ten-second window capped at 600 samples. Older values leave the window so the summary stays focused on recent input.
Does the report include raw controller input?
No. The local JSON contains summary metrics only. It excludes raw sample streams, the controller identifier, browser user agent, and network data.