iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Test a controller in three separate layers: first confirm that Windows or macOS sees it, then verify its buttons and axes in a browser gamepad tester, and finally test the exact game or application you intend to use outside Steam. A browser result proves that the operating system and browser can read the controller; it does not prove that every non-Steam game supports that device or its button mapping.
The three-layer test
Use this order so each result answers a different question:
- System detection: Is the controller connected by USB or paired over Bluetooth and visible to the operating system?
- Browser detection: Can a normal browser tab read the controller’s buttons, D-pad, triggers and sticks?
- Target-app detection: Does the specific game or application outside Steam recognize and correctly map those inputs?
Do not skip directly to a game. A controller can pass the browser test but fail in a particular title because that title supports a different input API, does not support the device, or expects another button layout. Conversely, a game may work through its own input layer even when a browser session has not exposed the pad yet.
What you need before testing
- The controller and, for a wired test, a USB cable that carries data rather than charge only.
- A USB port or a computer with Bluetooth enabled.
- A regular browser tab with a gamepad tester such as Controller Test.
- The non-Steam game or application you actually want to use, installed and ready to launch.
- Access to Steam Input or other controller-remapping utilities so you can close or disable them temporarily during diagnosis.
Connect the controller at the operating-system level first. A webpage cannot pair a Bluetooth device or make an unplugged USB controller available to the computer.
#1 Best Overall
- With broad game support, the Logitech Gamepad F310 works with old standbys to today's biggest titles, so it's easy to set up and use with your favorite games.
- Profiler software allows the gamepad to be programmed to perform keyboard and mouse commands for games without gamepad support.* * Requires software installation.
- A familiar control layout that doesn't require a learning curve to be able to use, with all the same buttons as on an Xbox 360.
- The unique floating D-pad rests on four switches-instead of a single pivot point-making it responsive to quick changes in direction.
- The six-foot cord lets you lean back and play a comfortable distance from your PC monitor.
Step 1: connect the controller to the operating system
USB connection
- Plug the controller directly into the computer rather than through an unpowered hub.
- Wait for the operating system to finish installing or selecting the device driver.
- If there is no response, move the cable to another USB port.
- Replace the cable with one known to transfer data; many inexpensive cables provide charging only.
A USB controller that is not visible to the operating system will not appear in a browser tester or in a game. If it disconnects when the cable moves, treat that as a connection or hardware fault before investigating software mappings.
Bluetooth connection
- Open the operating system’s Bluetooth settings and put the controller into its documented pairing mode.
- Select the controller in the available-device list and complete pairing.
- Confirm that the status is connected, not merely remembered or paired while powered off.
- If it was previously paired with another device, remove that old connection or power the other device down, then pair again.
After reconnecting Bluetooth, keep the settings window available long enough to confirm that the controller remains connected. Then open the browser tester and continue with the input-wake step below.
Step 2: make the browser expose the controller
Open a gamepad tester in a normal browser tab and focus the page. Press a physical button or move a stick once. A controller that was already connected when the page loaded may not appear until there is user input. The W3C Gamepad API Working Draft dated 10 July 2025 states: “If a gamepad was already connected when the page was loaded, the gamepadconnected event SHOULD be dispatched when the user presses a button or moves an axis.”
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11This interaction-sensitive behavior is normal for the browser API. If the tester is still blank:
- Click the page so it has focus.
- Press a face button and move each stick briefly.
- Reload the page, then repeat the input.
- Reconnect USB or Bluetooth at the operating-system level and reload the tester again.
The W3C document describes browser-facing button values from 0 to 1 and axis values normalized from -1 to 1. It is a Working Draft, not a final recommendation, so individual browsers and devices can still expose details differently.
Rank #2
- The 2.4 GHz wireless connection uses a tiny Plug-and-Forget Nano-receiver that stays in your USB port, even on laptops, for fast data transmission with minimal delays, dropouts, or interference.
- With broad game support, the Logitech Wireless Gamepad F710 works with old standbys to today's biggest titles, so it's easy to set up and use with your favorite games
- Profiler software allows the gamepad to be programmed to perform keyboard and mouse commands for games without gamepad support.* Requires software installation
- Dual vibration motors let you feel every hit, crash and explosion in games that support vibration feedback for a more realistic and immersive experience
- A familiar control layout that doesn't require a learning curve to be able to use, with all the same buttons as on game console controllers
Step 3: inspect every control
Do not stop when the tester displays a device name. Exercise each control and watch whether the expected value changes, returns to rest, and stays independent from other controls.
| Control | What to do | What a healthy reading looks like | Fault clues |
|---|---|---|---|
| Face buttons | Press each button separately and release it. | The corresponding button changes only while pressed and returns to its idle value. | No change, a permanently active button, or another button changing at the same time. |
| D-pad | Press up, down, left and right individually, including diagonals if supported. | Each direction reports reliably and releases when you let go. | One direction is missing, stuck, or reported as an unexpected button or axis. |
| Bumpers | Press the left and right shoulder buttons. | Each side has a distinct response. | Only one side responds or both sides report the same input. |
| Triggers | Squeeze each trigger gradually from rest to full travel. | The value changes smoothly through its range and returns to rest. | A trigger is binary when the game expects analog travel, moves without being touched, or never reaches its full range. |
| Left and right sticks | Move each stick up, down, left and right, then release it. | Each axis moves through its range and returns close to center. | Drift at rest, a dead direction, an axis that reaches only part of its range, or the wrong stick moving. |
Record what the tester reports rather than relying only on the picture of a familiar controller. Standard mappings can make common pads look predictable, while an unfamiliar device may expose a raw button or axis order that differs from the labels printed on its shell.
Free tools Windows power users keep installed
One-click scans. No signup required.
Step 4: test the actual non-Steam game or application
- Close, disable, or account for Steam Input and other remapping utilities while diagnosing. These programs can capture input, create a virtual controller, or change the device and button order that an application sees.
- Launch the game or application directly, not through a Steam shortcut.
- Open its controller, input, or key-binding settings.
- Check whether the controller is listed as an available device and whether the on-screen prompts match the physical buttons.
- Bind one obvious action, such as jump or confirm, to a face button and test it in a safe menu or tutorial.
- Test movement, camera control, bumpers, triggers and the D-pad in the application itself.
A positive browser result establishes browser access only. The target application must implement support for that controller, its mapping and its chosen input path. If the game offers separate input modes, try the mode recommended in its documentation and restart the game after changing it.
Windows input APIs: why one application can work and another cannot
Windows applications commonly use either XInput or DirectInput, and Microsoft documents differences between the two APIs at “Comparison of XInput and DirectInput features”. They do not expose exactly the same device features or data in the same way. Therefore, a controller that responds in a browser or in one game is not automatically supported by every Windows title.
Triggers are an important example: Microsoft’s comparison describes XInput’s separate trigger handling, while DirectInput applications can expose a different feature set. If your controller has a physical XInput/DirectInput switch, test each mode separately and follow the controller manufacturer’s instructions. The mode can change the device identity, button order and whether a game recognizes it at all.
Rank #3
![ZD-V+ USB Wired Gaming Controller Gamepad For PC/Laptop Computer(Windows XP/7/8/10/11) & PS3 & Android & Steam - [Black]](https://m.media-amazon.com/images/I/41Ddk2Xp33L._SL160_.jpg)
- Support PC Windows XP / 7 / 8 / 10 / 11 & PS3 & Steam
- Support Android (version 4.0 or above, and the device must fully support OTG function). Not inlciud a OTG adapter in the package.
- Support Plug and Play, only for PC games supporting Xinput mode / PS3
- Feature: Multi-mode: Xinput & DirectInput / Vibration Feedback Function / JD-SWTICH Function (exchange the functions of D-pad and Left-Stick in Xinput mode)
- USB Wired Gamepad (PS architecture) - Does not support the Xbox 360 / Xbox One / Mac OS
Do not interpret “DirectInput” or “XInput” as a quality rating. They are input paths. The useful question is which path the target application supports and what the controller reports in that mode.
Recommended Free Tools
Use a diagnostic matrix instead of guessing
| Layer | Test | Pass means | If it fails |
|---|---|---|---|
| System | USB or Bluetooth status in operating-system settings | The computer shows a connected controller that stays connected. | Change USB port or data cable; reconnect Bluetooth; resolve pairing or power problems before opening the tester. |
| Browser | Tester page after a button press or stick movement | The device appears and controls produce changing readings. | Focus and reload the page, provide physical input, reconnect the device, and temporarily close remapping software. |
| Target app | Controller settings and an in-game action | The application detects the device and actions match the intended controls. | Check the game’s support and bindings, try the controller’s other documented mode, and test with remappers disabled. |
Write down the result at each layer. This prevents a target-app compatibility problem from being mistaken for a bad cable, and prevents a stuck trigger from being hidden by a game that reads only digital buttons.
Troubleshoot by symptom
The operating system does not detect the controller
- For USB, try another port and a known data cable.
- For Bluetooth, remove the old pairing, power-cycle the controller, and pair it again in system settings.
- Make sure the controller has charge or fresh batteries.
- Do not proceed to browser or game testing until the connection remains present.
The operating system detects it, but the browser tester is empty
- Focus the tester page and press a button or move an axis; a connected-at-load device may wait for that input before the browser reports it.
- Reload the page after reconnecting the controller.
- Close Steam Input and other remapping or virtual-controller tools temporarily, then test again.
- Try the same wired or Bluetooth connection after isolating the other one. A wired pass and Bluetooth failure point to the wireless link or pairing state, not necessarily the controller electronics.
The tester shows the controller, but a control is missing or stuck
- Repeat the control test slowly and check whether the value returns to rest.
- Compare the reading in the controller’s other documented input mode, if it has one.
- Test a second application. If the same physical control is wrong everywhere, suspect hardware, firmware or the controller’s mode; if it is wrong only in one application, investigate that application’s mapping.
- For analog sticks, distinguish a small center deviation from a full-range failure. The browser reports numerical axes, so a value that never settles near center indicates drift or calibration trouble rather than a missing game setting.
The browser passes, but the non-Steam game does not respond
- Confirm that the game actually supports controllers and open its own input settings.
- Disable Steam Input and remappers, then relaunch the game so it sees the physical device rather than a virtual replacement.
- Try the controller’s XInput or DirectInput mode that matches the game’s documented support.
- Check whether the game expects a standard layout but is receiving raw ordering. Rebind controls manually if the game allows it.
- Use a known second controller only as a comparison. You do not need to buy another controller for the basic three-layer test.
The game detects it, but prompts or actions are wrong
This is a mapping problem, not proof that the controller is dead. Open the game’s binding screen, assign each action explicitly, and verify the D-pad, triggers and both sticks rather than relying on automatic labels. If the game offers a controller-layout choice, select the layout that matches the mode currently selected on the controller.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Wired versus Bluetooth: isolate one variable at a time
Testing both connection types can reveal whether the problem follows the controller or the link:
- Run the complete system, browser and target-app sequence over USB.
- Disconnect USB and complete a fresh Bluetooth pairing.
- Repeat the same controls in the same tester and the same game.
- Compare which layer changes from pass to fail.
If USB and Bluetooth both fail in the same way, concentrate on controller mode, mapping or hardware. If USB works and Bluetooth fails at system detection, concentrate on pairing, radio range, battery state or the computer’s Bluetooth connection. If both are detected but only one has incorrect mappings, compare the controller’s documented modes and the device identity exposed in each connection.
Testing a controller with a physical mode switch
Some PC controllers provide an XInput/DirectInput switch. Logitech’s F310 Gamepad Quick Start Guide, for example, documents USB setup and the two-mode switch for that model. The general diagnostic method is the same for any controller: disconnect or power it down, select one documented mode, reconnect it, run the browser test, and then repeat the complete sequence in the other mode.
Do not change the switch while a game is running and assume the application will refresh automatically. Many games read the device only at launch, so quit and relaunch after changing modes.
What the browser values mean
The Gamepad API gives a common vocabulary for checking raw behavior. In the W3C Working Draft dated 10 July 2025, button values are represented on a 0-to-1 scale and axes are normalized from -1 to 1. A centered stick should therefore be near the middle of its axis range, while moving it toward either extreme should change the corresponding value toward the end of the range.
These values help you separate a physical signal from a game-specific interpretation. They do not tell you that a particular title will use the same button numbers, accept analog triggers, or support the controller’s mode. The specification is still a Working Draft, and device-specific mappings can vary.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When you can call the test complete
You have a useful answer when all three statements are true:
- The operating system keeps the controller connected.
- The browser tester displays every required control with sensible movement and no unexplained stuck input.
- The exact non-Steam application detects the controller and performs the actions you tested with the intended mapping.
If only the first two statements are true, the controller and browser path are functioning, but the target application remains unsupported, misconfigured or incompatible with the controller’s current input mode. If the first statement fails, fix the physical or pairing connection before drawing conclusions from any software test.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
