Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsThe reliable way to test a controller outside Steam is to check it in layers: make sure the operating system sees the controller, verify its buttons and axes in a browser gamepad tester, then test the exact non-Steam game or application. A browser result confirms that the browser can read input; it does not prove that a particular game supports the controller or its button mapping.
Connect the controller by USB or pair it through the computer’s Bluetooth settings. Open a tester such as Controller Test, focus the page, and press a button or move a stick. If every control responds, launch the target application and check its own controller settings and prompts. When something fails, test only one layer at a time so you can tell whether the problem is the connection, browser access, input mode, or the application.
As an Amazon Associate I earn from qualifying purchases.
What the three-layer test tells you
There are three separate questions, and each needs its own check:
| Layer | What to test | What a positive result proves | What it does not prove |
|---|---|---|---|
| System | The operating system lists the wired or paired controller. | The computer has a connection to the device. | That a browser or game can interpret every control. |
| Browser | A gamepad tester reports button, D-pad, trigger and stick changes. | The browser is receiving controller events and values. | That your target game supports the device, mode or mapping. |
| Target app | The non-Steam game or application detects the pad and responds to its controls. | This particular app is accepting the controller in its current mode. | That other apps will use the same API or layout. |
Keeping these results separate prevents a common misdiagnosis. A controller can be visible to Windows but absent from a browser, visible in a browser but unsupported by a game, or detected by a game with an incorrect button order.
#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.
Before you start
Use a connection the computer can actually see
For USB, plug the controller into the computer with a cable that carries data, not a charge-only cable. For Bluetooth, complete pairing in the operating system before opening a test page. A webpage cannot pair a controller or make an unpaired device available to the computer.
Temporarily account for software that changes input
Steam Input and other controller-remapping utilities can capture, translate or expose a different virtual device. If the browser or game shows an unexpected controller, close those tools temporarily or disable their remapping for the test. Re-enable them after you have established that the physical controller works.
Know what you are trying to establish
Testing an existing controller does not require buying another one. If you have a known-working second controller, it can be a useful comparison, but the basic diagnosis works with one device.
Step-by-step: test the controller outside Steam
1. Connect the controller at the system level
- Connect the controller by USB, or pair it in the operating system’s Bluetooth settings.
- Wait for the operating system to finish adding the device. If it offers a choice of input modes, note which mode is active.
- Keep the controller awake. Some wireless pads go to sleep until you press a button.
Do not begin with the browser. If the operating system has not established the connection, a tester page has nothing to read.
2. Open a browser gamepad tester and wake controller access
- Open a normal browser tab with a gamepad tester, such as Controller Test.
- Click or otherwise focus the page.
- Press a physical button or move a stick. If the controller was connected before the page loaded, this input may be what makes it appear.
The W3C Gamepad API Working Draft dated 10 July 2025 describes this behavior: “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.” The document is a Working Draft, not a final recommendation; treat it as the browser-facing specification under development. Read it at W3C’s Gamepad API Working Draft.
3. Exercise every physical control
Do not stop when the tester displays a controller name. Check the individual inputs:
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
- Press each face button separately and verify that only the intended indicator changes.
- Tap every direction on the D-pad. Some devices expose directions in a familiar standard arrangement; others report a raw order or a different representation.
- Press both bumpers and squeeze both triggers through their full travel. Watch for a value that never changes or remains active after release.
- Move the left and right sticks up, down, left and right, then rotate them through their range. Check whether an axis moves while the stick is untouched.
- Release every control and look for stuck buttons, drifting axes or values that do not return to their idle state.
Write down exactly which control fails. “The controller is broken” is less useful than “right trigger stays at one-quarter travel” or “left stick’s horizontal axis does not move.”
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →4. Interpret the browser’s values
The Gamepad API model represents axes as normalized values from -1 to 1 and button values from 0 to 1, as described in the W3C Working Draft. A tester may display these as bars, numbers or a visual diagram. The important check is movement in the expected direction and a stable idle reading, not a particular graphic design.
Browser mappings can make a familiar controller look orderly, while an unfamiliar device may expose raw button ordering. Compare the tester’s labels with the control layout expected by your game. A browser showing activity only establishes that an input event arrived; it does not automatically translate that event into the game’s preferred layout.
5. Test the actual non-Steam game or application
- Leave the browser result recorded, then launch the exact game or application you want to use outside Steam.
- Open that program’s controller, gamepad or input settings. Look for a device list, calibration page, control-binding screen or controller prompts.
- Press buttons and move sticks in the application itself. Confirm that the action shown on screen matches the physical control.
- If the program offers a remapping screen, bind one non-critical action first and test it before changing the complete layout.
- Check whether the application expects a particular input mode, such as XInput or DirectInput on Windows.
A browser pass cannot substitute for this step. Applications choose their own supported APIs, device lists and mappings, so one game may work while another ignores the same controller.
6. Isolate a failed connection
- For USB failures, try another USB port and a cable known to carry data.
- For Bluetooth failures, remove or disconnect the controller in the operating system, pair it again, reload the tester, and press a button after the page is focused.
- Close Steam Input and other remapping software temporarily. Repeat the browser test to see whether the visible device or mapping changes.
- Test the target application again after the browser result is stable.
Change one thing at a time. Swapping the cable, changing the connection type and enabling a remapper simultaneously makes it impossible to identify the cause.
Windows input modes: XInput and DirectInput
Windows applications do not all read controllers through the same interface. Microsoft documents both XInput and DirectInput, and their supported features can differ by application. A positive result through one path therefore does not establish universal compatibility.
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
| Question | How to test it | Why it matters |
|---|---|---|
| Which API does the app use? | Check the game’s controller documentation or settings, then test the controller in the mode it supports. | An app listening for one API may ignore a device exposed through another. |
| Does the controller have a mode switch? | With the controller disconnected or powered down as directed by its manual, select the alternate mode and reconnect it. | The same hardware can present different buttons and capabilities in different modes. |
| Are both triggers being read correctly? | Observe each trigger separately in the browser and in the app. | Microsoft specifically documents differences between XInput and DirectInput feature handling, so trigger behavior should be checked rather than assumed. |
For the formal Windows comparison, see Microsoft’s “Comparison of XInput and DirectInput features”. If your controller has a physical XInput/DirectInput switch, test each supported position according to its manual, repeating the system, browser and target-app checks after every change.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Diagnose by symptom
The operating system does not show the controller
- USB: move to another port and replace a suspect cable with a known data cable.
- Bluetooth: remove the old pairing, put the controller into pairing mode, and pair it again in the operating system.
- Power: charge or replace batteries and press a button to wake the controller.
- Mode: if the controller has an input-mode switch, select the mode required by the computer or app, then reconnect.
Until the operating system sees the device, browser and game troubleshooting is premature.
The operating system sees it, but the browser shows nothing
- Reload the tester after the controller is connected.
- Focus the page.
- Press a button or move an axis to trigger browser exposure for a controller that was already connected at page load.
- Close remapping utilities and repeat the test.
If it still does not appear, compare wired and Bluetooth connection if both are available. This separates a radio or pairing problem from a controller or browser problem.
Recommended Free Tools
The browser sees it, but one control is missing or stuck
Repeat the control slowly and note whether the value changes at all, changes only partway, or fails to return to idle. Try the other connection type and inspect the controller’s mode. If the same physical control fails in both connections and in more than one tester session, the evidence points toward the controller or its configuration rather than the target game.
The browser works, but the game ignores the controller
- Open the game’s own input settings and confirm that a controller is selected.
- Check whether the game supports the controller’s current API or mode.
- Temporarily disable Steam Input and other remappers that might be capturing or replacing the device.
- Look for a manual binding option if automatic prompts do not appear.
- Compare the game’s expected button order with the browser’s reported order, especially for an unfamiliar controller.
This is an application-compatibility or mapping problem until the same failure can be reproduced in the browser.
The game detects it, but the buttons are wrong
First determine whether the controller is presenting a non-standard or raw layout. Use the game’s binding screen to assign each action manually, or switch to the controller mode the game documents. Do not infer a hardware failure from swapped labels: a browser can report every button correctly while a game uses a different mapping.
Wired versus Bluetooth: a useful comparison
| Test condition | What it can reveal | How to run it |
|---|---|---|
| USB only | Whether the controller, cable and USB connection provide stable input without wireless pairing. | Connect with a known data cable, reload the tester, and repeat the full control check. |
| Bluetooth only | Whether pairing, wireless power and the operating system’s Bluetooth connection are working. | Pair in system settings, focus the tester, press a button, and repeat the same controls. |
| Both | Whether the fault follows the controller or one connection method. | Record which buttons and axes fail in each mode before changing remapping settings. |
Use identical control checks in both modes. A difference between them is more informative than simply observing that one connection “feels” unreliable.
Record a result you can act on
A short test record makes support requests and later troubleshooting much easier. Capture:
- Connection type: USB or Bluetooth.
- Whether the operating system listed the controller.
- Browser tester result after pressing a button or moving a stick.
- Each failed, stuck or drifting control.
- Active controller mode, if the device offers more than one.
- Whether Steam Input or another remapper was running.
- The target application’s detection result and any control-mapping mismatch.
That record identifies the failing layer without relying on a vague statement that the controller “doesn’t work.”
What this test can and cannot guarantee
A successful system check proves availability to the computer. A successful browser check proves that the browser receives gamepad input and can display changing button or axis values. Only a successful test inside the intended game establishes that the application accepts the controller’s current connection, API and mapping.
Because the W3C Gamepad API document remains a Working Draft, browser behavior can differ in how devices are exposed. Windows applications can also choose between XInput and DirectInput. Treat each result as evidence about that layer, then continue to the next layer instead of treating any single green light as universal compatibility.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
