Controller button and input tester
Every press is logged. Work through the checklist until all buttons turn solid, and watch the history for ghost or double inputs.
Input map
Registered / 17- South
- East
- West
- North
- Left bumper
- Right bumper
- Left trigger
- Right trigger
- Select
- Start
- Left stick
- Right stick
- Up
- Down
- Left
- Right
- Guide
Raw input
Axes
0
1
2
3
Input history
- Waiting for input
How to run this test
- Connect the controller and press any button.
- Press every button once. Each one turns solid in the checklist.
- Squeeze both triggers slowly to see their analog travel.
- Watch the input history for presses you did not make.
How to read the result
- Checklist
- A button that never turns solid is either broken or mapped to a different index. Look at the raw list to see whether any other number lights up when you press it.
- Analog values
- Triggers and some face buttons report a value between 0 and 1. A trigger that stops below 1.00 at full squeeze has lost range; one that sits above 0.00 at rest may need cleaning.
- Input history
- Each line is a new combination of pressed buttons. Two lines for one press means a double click, a common fault on worn mouse style switches in bumpers.
Questions about this test
- Why are my buttons in a different order?
- Controllers that the browser does not recognise use a non standard mapping, so numbers can differ from the diagram. The raw index list is always accurate.
- My controller has back paddles. Do they show up?
- Only if the controller reports them as separate buttons. Many controllers map paddles to existing buttons in hardware, so pressing a paddle lights up the button it copies.
- How do I test for a double clicking button?
- Press the button slowly ten times and count the history lines. More lines than presses means the switch is bouncing.