Xbox One controller cannot be shared from macOS to Win10

Submitted by kiler129 on #1

Server log:

Thu Feb 23 18:25:31 2023 LOG_INFO Connection 1 remotely disconnected gracefully (rx msg size)
Thu Feb 23 18:25:32 2023 LOG_INFO 10.141.30.239 connected as connection 2 (Standard TCP)
Thu Feb 23 18:25:40 2023 LOG_INFO Connection 1 successfully removed (reason:timeout)
Thu Feb 23 18:25:40 2023 LOG_WARNING Error -536870203 capturing device 1048576, Failed to create IOUSBHostObject. (Exclusive open of usb object failed.)
Thu Feb 23 18:25:40 2023 LOG_ERR Error binding device 1048576 [24c6:581a] to connection 2, BIND_ERROR
Thu Feb 23 18:25:40 2023 LOG_INFO Unmanaging device 1048576 [24c6:581a]
Thu Feb 23 18:25:40 2023 LOG_INFO Found Full speed device [24c6:581a] 'BDA, XB1 Classic controller' at address 1048576

Is there anything I can try? I updated both the server and the client to no avail. Other devices are passed without a problem.

Submitted by Michael on Fri, 2023/02/24 - 12:32

#2

Correct, its blocked on macos at the moment by apple.

Submitted by kiler129 on Fri, 2023/02/24 - 16:42

#3

So, in short no way around that, besides a dedicated hardware box for now? Does this apply to all xbox-esq devices like custom wheels etc, or is it just about gamepads? Did I miss some FAQ, or is that a new issue?

Submitted by Michael on Fri, 2023/02/24 - 16:50

#4

New issue, apple will block redirecting network/bluetooth devices. (The xbox dongle is just a wifi adapter) Just use a pi or something like that instead.

Submitted by peter on Wed, 2023/03/01 - 04:12

#5

@kiler129

which version of the virtual here server do you use? If I use version 4.3.6 on my mac, it works.

Submitted by Michael on Fri, 2023/03/03 - 08:42

#6

Actually i just realized this is not actually a genuine  xbox one controller, its a copy made by PowerA. Im not sure then why it doesnt work

 

Submitted by Michael on Wed, 2023/03/08 - 17:03

#7

I think i found a bug preventing it from being used via virtualhere

Could you download and run 4.5.2 of the server from here https://www.virtualhere.com/osx_server_software and see if that resolves it

Submitted by peter on Thu, 2023/03/09 - 06:08

#8

I downloaded and tested version 4.5.2. My xbox controller can now be shared. But my windows computer does not initialize the device properly. The leds are flashing all the time. Looks like the problem is not completely solved yet...

Submitted by Michael on Thu, 2023/03/09 - 15:41

#9

OK download and try 4.5.3 i found another bug and its fixed in that build

Submitted by peter on Fri, 2023/03/10 - 05:52

#10

Version 4.5.3 works for me

Thanks!

Submitted by kiler129 on Sun, 2023/03/12 - 09:12

#11

@Michael: well sir, you're a true MVP - the controller works perfectly now. It was just more a random pick for me as I extenda-borrowed it from my wife ;)

 

Thank you!

Submitted by kiler129 on Tue, 2023/03/14 - 16:41

#12

@Michael: I'm testing it for 2 days now and while the Xbox controller is working there's a substantial regress in other gaming peripherals. It looks like the peripherals aren't shared exclusively. For example my Stadia controller still opens games selector menu on macOS when connected via VH to a Windows computer remotely. In such case it appears in the Windows gamepad menu but doesn't pass any inputs... it's like a ghost. My steering wheel has the same exact behavior now - appears in Windows but doesn't produce any inputs (+ its management software crashes with communication errors). Reverting the macOS server to 4.5.0 removes all these issues.

Submitted by kiler129 on Wed, 2023/03/15 - 15:27

#14

The beta does work for most of the cases. I tested the Stadia Controller, the random PowerA controller, as well as a genuine Xbox Series X one from macOS to Windows 11. Just for testing I installed a fresh copy of Win 11 with nothing on it and VH with no config to eliminate any possibilites.

 

The steering wheel is an interesting case thou. It does work only from my RPi 2 (via generic ARM binary) and does so perfectly and every time. When shared from macOS or Ubuntu (newest one from live usb) it exhibits the same behavior which is VERY wild. The steering wheel normally shows as a COM port and it is detected by Windows Gamepad panel. It is also *sometimes* detected by the proprietary software. However, it never passes any inputs FROM the wheel to Windows over network, but I am able to change the wheel's settings - it is bizarre... it seems to work half-way? I tried for literally 5h with everything and it will never work as a game input device, but it will allow for firmware flashing (i.e. there's communication from the device to windows presumably to verify it). There are really no logs I can provide, unless there's some debug flag.

 

RPi 2 server (working):

Wed Mar 15 04:53:33 2023 LOG_INFO    >>> Starting VirtualHere USB Server v4.5.3 (Built: Mar  9 2023, 14:56:44)<<<
Wed Mar 15 04:53:33 2023 LOG_INFO    Using configuration /home/pi/config.ini
Wed Mar 15 04:53:33 2023 LOG_INFO    Server licensed to=unlicensed max_devices=1
Wed Mar 15 04:53:33 2023 LOG_INFO    Using large URB's
Wed Mar 15 04:53:33 2023 LOG_INFO    Listening on all network interfaces at TCP port 7575
Wed Mar 15 04:53:36 2023 LOG_INFO    10.xxxxx connected as connection 1 (Standard TCP)
Wed Mar 15 04:54:34 2023 LOG_INFO    Found Full speed device [346e:0004] "Gudsen, MOZA R5 Base" at address 114
Wed Mar 15 04:54:39 2023 LOG_INFO    Device 114 [346e:0004] BOUND to connection 1
Wed Mar 15 04:56:43 2023 LOG_INFO    Device 114 [346e:0004] SURPRISE UNBOUND from connection 1
Wed Mar 15 04:56:43 2023 LOG_INFO    Unmanaging device 114 [346e:0004]
Wed Mar 15 04:56:48 2023 LOG_INFO    Found Full speed device [346e:0004] "Gudsen, MOZA R5 Base" at address 114
Wed Mar 15 04:57:02 2023 LOG_INFO    Device 114 [346e:0004] BOUND to connection 1
Wed Mar 15 04:59:08 2023 LOG_INFO    Device 114 [346e:0004] SURPRISE UNBOUND from connection 1
Wed Mar 15 04:59:08 2023 LOG_INFO    Unmanaging device 114 [346e:0004]

 

macOS server (not working): https://i.imgur.com/9wd2ygP.png (cmd+c clears the log and right click => copy does nothing ;))

There's nothing substantial in the system messages on the client.

Submitted by Michael on Wed, 2023/03/15 - 22:10

#15

Was the wheel previously working with 4.5.0?

Submitted by kiler129 on Thu, 2023/03/16 - 05:51

#16

I wanted to immediately say "yes".... but I double checked and it doesn't work with 4.5.0 anymore. So this is most likely something changing in firmware/driver/macOS update :(

 

Can I help somehow more in debugging this issue?

Submitted by kiler129 on Thu, 2023/03/16 - 17:59

#18

Log sent; about 200K via email.

Submitted by Michael on Sat, 2023/03/18 - 08:32

#19

For reference the solution to @kiler129's issue with the Moza base was to right click on the base in virtualhere and select Custom Event Handler... then paste in this line:

onReset.$VENDOR_ID$=