Xbox Wireless Controller unresponsive after reconnecting

Submitted by GeorgeJensent on #1

Server: NVIDIA SHIELD TV Pro 2019 running VirtualHere Server 4.5.8 (Build 1067)
Client: Windows 11 Pro PC (22H2) running VirtualHere Client 5.5.1

On my SHIELD, I use an Xbox Wireless Controller that's connected via the official Xbox Wireless Adapter. The controller runs Microsoft's latest firmware (5.17.3202.0), and the Windows drivers for the controller and adapter are up to date.

Approximately once an hour, the controller disconnects for several seconds and then automatically reconnects. However, 20% of the time, the controller stops responding to commands after reconnecting. Here are the symptoms:

  • Guide button stays lit solid white, suggesting that the controller is still connected to the adapter
  • Controller is inactive/hidden in Device Manager and is not listed in the Windows "Game Controllers" settings menu
  • Adapter remains active/in-use in Device Manager and the VirtualHere Client

The controller will start responding again once I restart my PC, although I would like a less disruptive solution. I was able to get it working without a restart recently by restarting the VirtualHere client service on my PC (among other steps), although that fix only worked once. Is there anything that you would recommend trying?

Submitted by Michael on Mon, 2023/06/05 - 07:28

#2

1. Is the shield connected to the network via Ethernet?

2. In the virtualhere client right click USB Hubs->About->Statistics, what does that generally show when you are connected ok?

3. When it drops, could you unplug and replug the controller (without restarting the virtualhere client). Does that resolve it?

 

Submitted by GeorgeJensent on Mon, 2023/06/05 - 10:46

#3

  1. The Shield and PC both connect via Ethernet.
     
  2. My VirtualHere client (5.5.1 for Windows) does not have a Statistics menu. When I right-click USB Hubs, there is an "About" button that opens a menu that describes the terms of my license.
     
  3. I usually try several things, but the controller remains unresponsive (even though the guide button still lights up solid white): 
    1. Unplug and replug the wireless adapter into the SHIELD
    2. Plug the wireless adapter directly into the PC
    3. Remove and replace the controller's batteries

Submitted by Michael on Mon, 2023/06/05 - 10:49

#4

2. OK that is because the client is running as a service. Can you uninstall it as a service just for this testing Right click USB Hubs->Uninstall Service

Submitted by GeorgeJensent on Mon, 2023/06/05 - 11:22

#5

Thanks! It's mostly a straight line around 0.5ms. Once or twice every 60 seconds, it spikes to 2ms for a short amount of time.

Submitted by Michael on Mon, 2023/06/05 - 11:29

#6

Ok that is fine, if you can just check when the dongle drops (you can leave the latency window open)

Submitted by GeorgeJensent on Wed, 2023/06/07 - 02:26

#7

I haven't experienced any drops yet. Can you think of any reasons why the connection might be more stable running as a program rather than as a service, or is it probably just a coincidence?

Submitted by Michael on Wed, 2023/06/07 - 08:04

#8

Probably just a coincidence.

Submitted by GeorgeJensent on Thu, 2023/06/15 - 05:27

#9

Over the last week, I've reproduced this problem twice when running the client as a program.

I don't see anything unusual in the statistics file. Average and max latencies around the time of the disconnect are 0.7ms and 3ms respectively. These are virtually identical to the overall numbers. I don't see any errors in the client's System Messages window, either.

Submitted by GeorgeJensent on Tue, 2023/06/20 - 15:53

#10

I just bought a new Xbox controller (same model) and it has the same issue as my other one.

For one test, I connected both controllers simultaneously via the same wireless adapter. When one controller became unresponsive, the other still worked. Given that, I don't feel that my issue is related to VirtualHere, but let me know if you have other thoughts.

Submitted by Michael on Wed, 2023/06/21 - 09:30

#11

Im not entirely surprised. Microsoft very regularly changes their xbox dongle drivers for some reason. Sometimes they break compatibility directly (or via virtualhere). Its happened a few times before.