Start by separating hardware from software.
XInput and DirectInput are Windows input paths that games may support differently. XInput uses a predictable Xbox-style control set, while DirectInput can represent a much wider variety of buttons, axes, hats, wheels, and legacy devices.
For many current Windows games, XInput offers simpler automatic labels and prompts. DirectInput remains valuable for older games and specialized hardware, but it may need manual mapping and can expose triggers or D-pads differently.
Some controllers have a physical X/D switch or startup shortcut. After changing modes, reconnect the device and reload the page so the operating system and browser enumerate it again.
Work through the likely causes.
- 01
Check the exact controller manual for its supported modes and safe switching procedure.
- 02
On Windows, try XInput first for a current game that expects an Xbox-style controller.
- 03
Use DirectInput when the game or specialized controller documentation explicitly calls for it.
- 04
Open the raw mapping test after each switch and record changed button, trigger, axis, or D-pad indexes.
- 05
Avoid running multiple translation layers unless the game needs one; duplicate virtual devices can cause double input.
Check what the browser can see.
Open the full tester to inspect buttons, sticks, triggers, mapping, range, and neutral noise.
Repeat before you conclude.
A repeatable issue across connections, browsers, and native games is stronger evidence of a controller fault than a one-time browser reading. If the problem appears only in one game, review that game’s controller support, deadzone, remapping, and launcher settings.
What to keep in mind
Use the controller manual before changing hardware modes or firmware settings.
How the browser readings are defined
Our live tools use the standardized browser Gamepad interface and explain its limits in our methodology. Device mappings and proprietary features can still differ by operating system, browser, connection, firmware, and controller mode.
Questions about this issue
Is XInput better than DirectInput?
It is often easier for modern Windows games, but DirectInput supports more varied device layouts. The better choice is the one the game and controller officially support.
Why are both triggers on one axis in DirectInput?
Some DirectInput layouts represent the two triggers as opposite directions of one axis. XInput normally exposes them separately.
Can a browser change my controller mode?
No. Mode selection happens on the controller, receiver, operating system, driver, or native software.