Another 8bitdo issues thread

Submitted by agusluc88 on #1

I found several post with the 8bitdo having some issues with Virtualhere, but i couldn't find exactly my problem so i'm opening a new thread.

Setup:

  • Windows11 client
  • Android Server (licensed) - FireStick 4k MAX
  • Sunshine+moonlight streaming
  • 8bitdo ultimate 2 wireless controller (in 2.4g mode, the USB dock with the receiver inside plugged into a USB Hub that is connected using an OTG cable)

Timeline of events:

  • First i connected one 8bitdo controller and worked fine, played for a few days, no issues at all.
  • Then i plugged the second controller and the problems began. Controllers stopped working, they both show up on virtualhere client but the didn't work, if i tried to use/activate the device, the screen would flick and the device would be instantly disabled again.
  • I started removing devices from the device manager but nothing helped
  • Then i tried the onReset.$VENDOR_ID$.$PRODUCT_ID$= custom event handler and now the first controller works again, but the 2nd controller doesn't show up on the virtualhere client device list and it doesn't work.
  • After a few reconnects/retries the 2nd device shows but doesnt work because it's not recognized as a controller. Screenshoot: https://imgur.com/a/ZLpwFYa

After some testing i figure out that the controller when it works (and it's not docked) shows as "8BitDo Ultimate 2 Wireless Controller for PC" on VirtualHere and gets recognized by joy.cpl, and when it doesn't work it shows as "Ultimate 2" on VirtualHere and doesn't get recognized by joy.cpl. This 2nd device name "Ultimate 2" sems to be the device name of the dock.

 

Submitted by agusluc88 on Tue, 2025/07/22 - 09:52

#2

Some additional info: Sometimes i can make the 2nd controller work, but then the first one stops working. Seems that on the Virtualhere client both controllers are being match to the same device, looks like VirtualHere it's not being able to distinguish one controller from the other, sometimes it connects to the first one and some other times connect to the second one. Maybe is using the Vendor ID/Product ID instead of the Serial to identify the devices? Or maybe it's a side effect of using onReset.$VENDOR_ID$.$PRODUCT_ID$= ?

Submitted by Michael on Tue, 2025/07/22 - 11:52

#3

(Its not possible for virtualhere to confuse USB devices because when it controls the USB device it uses a unique number to do so which is provided by Android.)

I'm assuming you are talking about this controller

I suspect android is the problem. The 8bitdo is unusual in that it tries to be other devices by rebooting and changing its firmware. Android doesn't allow too much control over USB devices to handle this nicely. You see the name change because of this.

It is critical that you use 2.4g mode and not Bluetooth because Windows can only have one Bluetooth controller/dongle active at any one time and will disable any other bluetooth radios automatically.

If you switch dongles and have only the non-working one connected, does that work ok? If so then it is some android issue which i cannot control. Normally in plain linux or even windows there is some extra control to help the 8bitdo switch modes but its not possible on Android.

 

Submitted by agusluc88 on Sat, 2025/07/26 - 09:53

#4

Yes, i'm using 2.4g mode. Sadly these controllers are not playing well with virtualhere. Any chance i can ask for a refund? Thanks

Submitted by Michael on Sat, 2025/07/26 - 11:24

#5

No refunds for the android unless its through the playstore which i think is a day or so.