Start with a clean baseline
Use raw browser input to separate a physical control/event problem from game/app mapping. Test the exact failing key, button, axis or wheel action rather than a generic connected/not-connected state.
Live evidence
Relevant checks
First sequence
Do the high-signal checks before risky changes
- 1
Run Gamepad Test
- 2
Move each axis slowly through full range
- 3
Check simulator bindings only after browser input is confirmed
Decision points
What the result should change
If raw events are correct herePrioritize app/game bindings, profiles, sensitivity or remapping.
If duplicates/drift reproduce hereThe symptom is independent of the affected app; compare connection mode and official calibration.
If the entire device freezes intermittentlyPrioritize receiver/cable/power/interference before a single switch or stick component.
Browser can help check
- Observe exposed axes/buttons
- Identify some HID devices
- Help separate hardware input from simulator mapping
Browser cannot prove
- Read all vendor-specific force-feedback/profile features
- Replace manufacturer calibration tools
Repair boundary
Know when to stop browser troubleshooting
- Do not flash unofficial firmware to fix an input symptom.
- Browser polling estimates are not kernel-level USB analyzers.
- Cleaning/disassembly methods vary by manufacturer and switch design.
Used-device inspection
What to verify before paying or signing off a repair
- Every key/button and repeated-press behavior
- Stick/axis center, full range and dead zones where applicable
- Wireless receiver/Bluetooth plus wired mode if supported