INPUTPROOF
VIEW
Open lab
SYSTEM READYENGINE PLATFORM-V1SUITES 07 / 37 ENTRIESPROCESSING ON DEVICERAW UPLOAD 0 BOUTPUT JSON / SCORECARD / PRINT
GAMEPAD TESTER

Connect a controller. Press any button. Test it live.

See buttons, sticks, triggers and drift in one place. No account, no install and no raw controller input leaves this tab.

Open live tester
02 / CONTROLLER DIAGNOSTIC

Controller tester

Awaiting signal source
1Connect a controller

Use USB or Bluetooth. Keep only one controller active for a clean read.

2Press any button

The browser usually exposes the controller only after the first input.

3Watch the map, then run a test

Buttons, sticks and triggers respond live. Use the idle test for drift.

ACTIVE DEVICENo active controller
PROTOCOL IP-CTL-01 V1.5API UNAVAILABLESOURCE LIVEMAP —
WINDOW
5.0 SEC
PRIMARY
RADIAL P95
HEALTHY
≤ 0.050
MINOR
0.051–0.100
SIGNIFICANT
> 0.100
FRAME QUALITY
AWAITING
STORAGE
MEMORY ONLY
L STICKR STICKD-PADABXY
live signalattention threshold
LEFT STICK0.000
X  0.000Y  0.000
RIGHT STICK0.000
X  0.000Y  0.000
GUIDED STICK SWEEP / 6 SEC

Trace both stick edges through full circles.

Move both sticks around the outer gate several times. Range, angular coverage and circularity are calculated from browser-mapped axes.

LEFT STICK HEATMAP0 SAMPLES
RIGHT STICK HEATMAP0 SAMPLES
APPLICATION DEADZONE PREVIEW0.10 RADIAL
LEFT RAW 0.000 / OUT 0.000RIGHT RAW 0.000 / OUT 0.000

This previews an application-layer radial deadzone. It does not change controller firmware or game settings.

DIAGNOSTIC ACTION ENGINECOMPLETE THE PROTOCOL

Connect a controller or load a reference trace

No active Gamepad API signal source is available.

1 FINDING(S)1 ACTION(S)RULES / EVIDENCE-BOUND
01
INFO

Connect a controller or load a reference trace

No active Gamepad API signal source is available.

LIKELY CAUSES
  • The controller is disconnected or has not produced an input event.
ACTIONS
  1. Connect the controller, press a button and keep this tab visible.
RETEST CONDITION

The active device name and live axes must appear before capture.

Actions are generated from visible Evidence fields and versioned product rules. They do not identify a physical root cause with laboratory certainty.

LOCAL BASELINE HISTORY / OPT-IN

Compare repeat tests without an account.

0 / 20 SAVED · 90 DAY RETENTION
Device report

Complete this protocol before saving a baseline.

CONTROLLER REPEATABILITY / LAST 5NEEDS MORE RUNS
0/5 RECENT COMPATIBLE RUNS

Save 3 more compatible run(s).

Left P95 offset—NEEDS 3 VALUESSTABLE ≤0.015 · REVIEW ≤0.03NEEDS MORE RUNS
Right P95 offset—NEEDS 3 VALUESSTABLE ≤0.015 · REVIEW ≤0.03NEEDS MORE RUNS
Left jitter—NEEDS 3 VALUESSTABLE ≤0.01 · REVIEW ≤0.02NEEDS MORE RUNS
Right jitter—NEEDS 3 VALUESSTABLE ≤0.01 · REVIEW ≤0.02NEEDS MORE RUNS
0 incompatible/incomplete and 0 older compatible run(s) excluded. The browser cannot verify controller identity, connection mode or firmware.
No raw axes, key logs, audio, video, images, full user agent or device ID is stored. Clearing browser site data also removes this history.
WHY THE WINDOW MATTERS

A moving dot is not a verdict.

Mechanical sensors produce small fluctuations, and browser scheduling adds timing noise. InputProof uses a sample window and robust statistics because a single maximum value can exaggerate an otherwise healthy controller.

The result remains browser-observed evidence. It does not read firmware calibration, USB packets or the exact deadzone used by a particular game.

HOW TO PREPARE
  1. Connect directly over USB or stable Bluetooth.
  2. Close software that remaps or captures the controller.
  3. Place the controller on a stable surface.
  4. Release every stick, trigger and button.
  5. Keep this tab visible until capture completes.
  6. Repeat a significant result before taking action.
QUESTIONS / ANSWERED
01

What is an acceptable controller stick drift value?

InputProof treats a P95 idle offset at or below 0.05 as its initial healthy browser-observed envelope, 0.05–0.10 as a minor deviation, and above 0.10 as significant. These are transparent product thresholds, not manufacturer certification limits.

02

Can a browser fix stick drift?

No. A browser can reveal repeatable symptoms and help you decide what to try next. Software deadzones may hide minor drift, but they do not repair a worn physical sensor.

03

Does InputProof upload controller input?

No. Raw axes and button values stay inside the active browser tab. Reports are generated locally and omit the complete device identifier.