Your test data stays in this browser.Security and Privacy
Device Test Bench

Observation → comparison → next step

Plan a Controller Drift and Mapping Check

Compare browser controller discovery, centered axes and game behavior before changing dead zones or assuming a damaged stick.

Published 2026-10-01

Your working record stays in this page. No automatic device access, media capture or saved test history. Copy or print only if you choose.

Controller behavior depends on discovery, mapping, axis values and the application interpretation of those values. A small nonzero browser reading at rest can be relevant without proving a faulty stick. A missing controller can also mean the browser has not exposed it yet. This plan records each boundary and separates a centered-value observation from the movement seen in a game.

Before the comparison

Comparison 1 of 3

Verify discovery and mapping

Open Gamepad Test, interact with the controller and confirm that buttons or axes update. Check the reported mapping before assuming that on-screen button positions match the case labels.

Why it matters. A browser-exposed controller is not necessarily standard-mapped. Missing discovery is not evidence of drift, and a different button order can be a mapping question.

Open Gamepad Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
The controller appears and values updateThis browser exposed live controller input.Release the sticks and compare centered values next.
It appears but the mapping differsInput is present, but positions may not match a standard layout.Compare individual controls with the target application mapping.
It remains undiscovered after interactionThe browser input boundary is unresolved.Compare another supported browser or connection and record discovery separately from stick condition.

Comparison 2 of 3

Compare centered axis values

Release the stick, observe its resting values, move it gently through its normal range and release again. Repeat the same axis, keeping other controls still.

Why it matters. Center offsets, calibration and application dead zones can interact. A browser value does not establish a universal unacceptable drift threshold.

Open Controller Stick Drift Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
A similar offset repeats after each releaseThe centered-value pattern is reproducible in this browser.Compare idle behavior in the target game before changing a dead zone.
The values change but there is no repeatable offsetThis sample does not show a stable centered pattern.Repeat under the same connection and record variation without a fault verdict.
The axes do not respond as expectedThe issue may concern mapping, discovery or the input path.Check the correct axis and connection before evaluating centered drift.

Comparison 3 of 3

Compare the target application

Use the same controller and connection in the game or application where the issue occurs. Compare idle movement, then change only one documented dead-zone or input setting if appropriate.

Why it matters. A game can suppress an offset or interpret a mapped axis differently. Settings can change the visible outcome without repairing a physical stick; restore changes that do not help.

Open Gamepad Button Test (new tab)

All possible observations and next steps
ObservationWhat it suggestsUseful next step
The game does not move while the stick is releasedThe application handles the present values without visible idle movement in this sample.Record the browser offset and application behavior separately; neither is a universal hardware pass.
Idle movement repeats in the game tooThe symptom is reproducible across these two input paths.Compare a supported connection or follow manufacturer calibration and support instructions.
One input-setting change alters the symptomApplication interpretation matters to the observed behavior.Record the exact changed setting and do not describe the physical stick as repaired.

Your private comparison record

Use a general device description, not a serial number or private recording. Do not enter passwords, complete typed messages or sensitive personal information. Leaving or reloading this page can discard the record; the site does not save it.

How to describe evidence

Illustrative example, not a measured case report. A small resting axis value is present in the browser, but the game shows no idle movement with its existing dead zone.

Useful conclusion. The browser offset and game outcome differ. Increasing a dead zone is not automatically necessary and is not a repair diagnosis.

Stop conditions and limits

Do not disassemble a controller or replace parts based on a single browser value. Use only model-approved calibration procedures and qualified help for physical faults.

This workflow cannot certify hardware, decide warranty eligibility or replace model-specific inspection. It does not request camera, microphone or controller access. Dedicated tests require separate deliberate actions.

Primary and official references

These sources document browser behavior or platform troubleshooting. Our comparison sequence is an editorial workflow, not a manufacturer-approved repair procedure.

Questions about this comparison

Is a nonzero resting value always a fault?

No. It is an exposed axis value that needs repetition and comparison with application behavior and model-specific guidance.

Why do button numbers differ from the printed labels?

The browser reports an array and mapping information. A nonstandard mapping or application profile can interpret those positions differently.

Read the detailed explanation

Choose another problem · Report a correction

Search