Why isn't one measurement enough?
The same symptom can come from stick centering, the connection path, calibration, or the game's deadzone/input layer. One browser result cannot separate all of those causes by itself.
The goal is not to show more numbers. First we try to reproduce the issue in the browser; if needed, change one condition and repeat the same measurement.
—
—
The browser sees normalized axes from the Gamepad API. This does not directly read the physical sensor or measure a game's deadzone/filtering behavior.
The same symptom can come from stick centering, the connection path, calibration, or the game's deadzone/input layer. One browser result cannot separate all of those causes by itself.
When a result looks suspicious, it does not just say “try another port.” It repeats the same measurement under the condition you choose and compares both results.
If the browser measurement is clean and the issue appears only in one game, that does not prove the hardware is healthy. But it is weak evidence for replacing the controller before checking game deadzone, Steam Input/remapping, calibration, or game-specific settings.
Some sticks look stable at rest but do not return to the same point after movement. For “it drifts after release,” controlled return samples are more useful than static drift alone.