Sharing XBOX 360 gamepad between 2 Windows 10 computers does not work

Submitted by weelupek on #1

Hi,

I am getting error when I am trying to share XBOX 360 gamepad. When I click on use this device it shows that there was an error for this device. Virtualhere server shows following :

2017-03-23 08:01:46 ERROR :Cannot capture device because it is currently in use at the server. Please exit the program that is using the device, then try again. (USB\VID_045E&PID_0719\FF3D06F0)
2017-03-23 08:01:51 ERROR :Cannot capture device because it is currently in use at the server. Please exit the program that is using the device, then try again. (USB\VID_045E&PID_0719\FF3D06F0)
2017-03-23 08:01:51 ERROR :Error binding device 7 [045e:0719] to connection 3, BIND_ERROR

I am not aware of any program which would use the gamepad at that moment.

Can you please give some advice what I am doing wrong ?

The goal is to use the gamepad while playing Steam game using Steam streaming. I do not want to buy Steam link.

Thanks

weelupek

Submitted by Michael on Fri, 2017/03/24 - 12:00

#2

I dont think its going to work because something is preventing virtualhere from taking control. Its likely some microsoft service or something holding the controller. The xbox based controllers are problematic under a windows server if you have a pi i would suggest using that as the server instead.

Submitted by Michael on Mon, 2017/06/05 - 10:59

#5

I didnt think virtualhere worked at all with the x360 & win10 both ends? Are you using win10 as the server?

Submitted by Vhsrocks on Tue, 2017/07/11 - 01:56

#6

Yes, I was using a winbook tablet (windows 10) running as a server connected to a xbox 360 dongle. The client is my desktop PC running windows 10. I had it working for about 10 minutes, but then I got the same errors reported by weelupek when I tried to use it again.

I originally had the steam client version(I also use this software with a steam link), but I think I may have downloaded the windows client version here as it was a newer version to get it to work.

Submitted by Michael on Wed, 2017/07/12 - 11:57

#7

I think you may have to unplug/replug the controller. The way i wrote virtualhere for windows is to be very conservative with capturing the device, so if windows says its busy i don't forceably capture it

Submitted by Vhsrocks on Sat, 2017/07/15 - 00:41

#9

I tested this a few times last night and found that if I had the client on and then plugged in the wireless dongle, the controller would work as expected as long as the green light on the dongle came on after virtualhere had established a connection to the server. After unplugging and plugging it back in a few times though, it seemed like the green light would come on immediately when plugging in the dongle. When that happened, the controller was no longer working as expected. So, I reached a point at which it no longer was working. It does seem like if vitrualhere can get access before windows does, it works fine. However, if windows gets access first,....no dice.