Why doesn’t my game recognise my controller over remote play?

The pad works in the streaming app’s menus, the PC even shows a controller connected, and the game either ignores it, shows the wrong button prompts, or lists a device that is not yours. Your pro pad’s paddles do nothing; your wheel is a stick; your arcade stick has its buttons in the wrong order.

Rebinding in every game is a job, and some games cannot be rebound at all because they only accept devices they know.

You bought the controller for its identity — its driver, its profiles, its extra inputs — and the stream threw the identity away.

Moonlight, Steam Link and Parsec all do the same thing with controllers: the client reads your pad as a generic gamepad on the Android side, and the host creates a virtual Xbox-style controller on the PC to replay those inputs. The game sees that virtual pad. Anything the virtual pad does not have — extra buttons, paddles, pedals, a manufacturer identity — is lost, and games that check the identity refuse.

The alternative is not to translate at all: forward the USB device over the network so Windows enumerates the real thing with its official driver. That is what a USB-over-IP bridge does and why the ChimpDeck app started as one.

1. 01

   Plug the controller in over USB

   Into the phone, tablet or TV box running ChimpDeck. Over USB the device is forwarded whole; over Bluetooth it is emulated as a virtual Xbox 360 pad — good for many games, but with a generic identity and, today, no rumble (coming soon).

2. 02

   Check the PC sees the real device

   With ChimpDeck for Windows and its USB bridge driver, the PC’s device list shows your controller by name. Its manufacturer software and profiles work as if it were plugged in locally.

3. 03

   Check the permission switch

   ChimpDeck for Windows has three switches — pointer, typing, controller — enforced on the PC. If «use the controller» is off there, no game will see any input, whatever the phone sends.

4. 04

   Check which pad is forwarded

   Several pads can be plugged in at once; they are listed with filters and nicknames. Make sure the one in your hands is the one being forwarded — the Shield checklist covers the rest.

5. 05

   Test the pad itself

   The button tester on the Android side shows every button and undocumented bits; the PC test bench shows raw axes. If a button never lights up, it is the hardware — run the drift test while you are there.

6. 06

   Pick the identity for Bluetooth pads

   If you must use Bluetooth, choose the Xbox or PlayStation identity on the PC so the game shows the right prompts (A or ✕). The PlayStation identity has no rumble return, and the app says so.

• Games see your controller, not a stand-in

  Same identity, same driver, same button map as at the desk — including devices games only accept by name.

• Every input the device has

  Paddles, extra buttons, pedals, rotaries and hats arrive as the driver defines them.

• A tester on both ends

  Button tester and drift tools on Android; raw axes and link quality on the PC.

• Works without a stream

  The bridge is a product on its own: use the pad plugged into your phone while you sit at the monitor.