Why Use the Classic View?
When a controller doesn't map cleanly to the standard Xbox layout, the raw data view shows exactly which numerical index corresponds to which physical input. This is essential for emulator configuration, custom keybindings, and identifying unknown gamepads.
Unlike our visual controller tester: which assumes a standard layout and may show wrong labels for non-standard controllers: the classic view makes no assumptions. It simply lists every button index with its current pressed state and value, and every axis with its current value.
Understanding Button Indices
The Gamepad API attempts to standardize button positions: A=0, B=1, X=2, Y=3, LB=4, RB=5, LT=6, RT=7, Back=8, Start=9, L3=10, R3=11, DPad=12-15, Home=16. Controllers reporting the 'standard' mapping follow this convention.
Non-standard controllers (older USB gamepads, exotic input devices) report indices in vendor-specific order. The classic view shows the raw indices so you can build your own mapping by pressing each button and noting which index lights up.
Understanding Axis Values
Axes report a continuous value from -1 to +1. Sticks typically use two axes per stick: Left Stick X is usually axis 0, Left Stick Y is axis 1. Right Stick X and Y are axes 2 and 3.
Triggers can be reported as a button value (0-1) or as an axis (-1 to 1), depending on the controller and mapping mode. If your trigger doesn't appear in the button table, check the axes: it might be reporting there.
Custom Mapping for Emulators
Most retro game emulators (RetroArch, Dolphin, PCSX2, Cemu) require you to map controller inputs manually. Use the classic view to identify each button's index, then enter those indices in the emulator's input configuration.
For controllers that report as multiple devices (Joy-Cons appear as two separate gamepads), the classic view shows each device with its own table, making it easy to identify which is which.