My controller doesn’t work on the NVIDIA Shield — what can I do?

You plug a perfectly good controller into the Shield, open the game on the TV and nothing happens. Or the pad works in the TV menus but the game on the PC ignores it. Or it works, but rumble is dead and the triggers feel wrong.

Every layer blames the other: the Shield says the pad is fine, the streaming app says it is forwarding «a controller», the game says it sees an Xbox pad it does not like. You end up rebooting things at random.

The worst part is not knowing whether the pad itself is broken. A stick that drifts or a trigger that stops at 80 % looks exactly like a software problem from the sofa.

Three different things can be called «the controller». The physical USB device the Shield sees; what the streaming app sends to the PC (with Moonlight, Steam Link or Parsec, a generic emulated pad); and what the game finally receives, filtered by drivers and permissions on the PC. A failure at any step looks the same on the TV.

On the Shield in particular there is one more trap: other USB-sharing tools such as VirtualHere may already be using port 7575, the port ChimpDeck’s server core starts on. ChimpDeck moves to the next free port by itself and tells you, but the PC has to be pointed at that address.

1. 01

   Check the cable and the port

   USB OTG (USB host) is the only hard requirement on the Android side. A charge-only cable or an unpowered hub will not show the pad at all: plug it straight into the Shield’s USB port, and use a proper data cable.

2. 02

   Read the welcome screen

   The chain on ChimpDeck’s welcome screen lights up when the pad is seen and the PC is linked. If it says the server core failed to start on port 7575, another program on the Shield has that port; ChimpDeck already moved to the next free one and shows it — point ChimpDeck for Windows at that address.

3. 03

   Know what a Bluetooth pad becomes

   A pad paired to the Shield by Bluetooth reaches the PC as a virtual Xbox 360 controller (PlayStation identity selectable on the PC if the game shows ✕ prompts). It plays, but today it does not vibrate (Bluetooth rumble is coming soon): for the real device with everything it has, plug it in over USB.

4. 04

   Check the permissions on the PC

   ChimpDeck for Windows has three switches — move the pointer, type, use the controller — enforced on the PC. If «use the controller» is off there, nothing the Shield sends gets in, whatever the app says.

5. 05

   Run the button tester

   Gamepad tools → button tester shows every button and axis the pad sends, including undocumented bits. If a button never lights up there, it is the pad, not the stream. Then run the drift and dead-zone test while you are at it.

6. 06

   Check which pad is being 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, then start the session — the rest of the TV setup is the same as always.

• The real USB device on the PC

  Windows sees your actual pad with its official driver, not an emulation the game may reject.

• All four rumble motors

  Left trigger, left body, right body, right trigger, each addressed on its own — over USB.

• A tester that tells the truth

  Buttons, undocumented bits, drift, dead zone, trigger curve and a reaction test, on the Shield, with or without a PC.

• A latency figure you can trust

  The app synchronises clocks with the PC and shows the pad-to-PC trip with its margin of error, never a fake 0 ms.