Sinden Lightgun

Hello! Long time VirtualHere user here! I have encountered the very first device that VirtualHere is unable to forward correctly.

I use a (licensed) Nvidia SHIELD as a USB host and forward devices to several virtual machines that I run different games on. To date the only devices I have been using is a Mayflash DolphinBar and some USB sticks. A few days ago I received a lightgun and was excited to try it with some arcade games. Unfortunately it did not work. The lightgun is made of two "container" devices. A webcam, and an input device. Android is able to turn the webcam on and record video. Virtualhere is able to see the webcam/input device. When I attempt to forward the devices over IP they show as available and I am even able to connect. However, no application is able to use the forwarded webcam. Many even crash when trying to make a connection.

I was interested in seeing if this was a limitation of the Android version, but the Windows trial will only allow me to forward a single device at a time, and I am unable to test the device without at least 2 devices being forwarded. Is there any other way I can try to narrow down what the issue is? I am a software/devops engineer by trade and would be happy to spend extensive time getting this to work. As common as the Mayflash DolphinBar seems to be, I'm sure the Sinden Lightgun will come up as deliveries go out.

Thank you for this very helpful product!

#2

I should add, the webcam is able to function with a Linux laptop as the server. The Android/Windows builds seem to be the issue. I am unable to test the full functionality due to the licensing restriction.

#3

I managed to get the webcam forwarded via a Raspberry Pi, and the Camera application on Windows managed to connect. However, when trying to forward the second part of the device I was informed that I needed a license. After purchasing the license and forwarding the second device, the Sinden Lightgun software still will not connect properly. It managed to connect exactly one time, as the Windows Camera application was also using the camera, but there was no video feed to the lightgun software. I have tried using the specialized build of VirtualHere for the Pi, but it did not seem to make a difference. With SSL added the camera could not be detected by the Windows client at all.

Unfortunately I am now out of ideas. And I now have a license Raspberry Pi I have no current use for :(

#4

Can i have a look via teamviewer? If so email me at mail [at] virtualhere.com (mail[at]virtualhere[dot]com)

#5

I also just received my long awaited Sinden Lightgun and I am trying to use it with an nvidia shield to forward to my windows machine. Please post an update.

#6

I bought a license for my shield thinking the problem was maybe the single device limitation and it's still no bueno. When connected directly to the machine all is well but when connecting through virtualhere one of the two devices is missing. I am also a devops engineer by trade and would be willing to help sort this out.

#7

OK back in June 2021 i logged into the Sinden Lightgun website and spoke to the developer of the lightgun in their discord. He agreed to help get it working with virtualhere. I havent heard anything since, so i logged into today again and asked him about it. It needs a bit of a change either to the sinden firmware or virtualhere to get it working. So i dont have an Estimated Time of a Fix available but ill post back here if i hear something from him. (MrLightgun)

Edit: Perhaps you could also login to their discord and remind him if you can

#8

I was asking some other questions in that space. I will contribute something before asking for any favors. Can you detail what needs to be changed. I know some devs I can farm the work out too.

#9

My last correspondence with him from June last year we determined that a library he uses to find the webcam attached to the sinden was not working when the webcam was passed via virtualhere. All the devices did seem to be passed ok, its just his library couldnt gather them all together when passed via virtualhere.

#10

See I figured the issue was on the virtualhere side because when I plug the device directly into a windows|linux host it shows up as two devices where within the virtualhere client I only see one.

for example:
before plugging it in:
pi@retropie:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

after plugging it in:
pi@retropie:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 16c0:0f02 Van Ooijen Technische Informatica <-
Bus 001 Device 008: ID 32e4:9210 <-
Bus 001 Device 006: ID 0424:2512 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

or to be more verbose:
before:
pi@retropie:~ $ sudo lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

after:
pi@retropie:~ $ sudo lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 1: Dev 9, If 0, Class=Hub, Driver=hub/2p, 480M
|__ Port 1: Dev 11, If 0, Class=Video, Driver=uvcvideo, 480M
|__ Port 1: Dev 11, If 1, Class=Video, Driver=uvcvideo, 480M
|__ Port 2: Dev 10, If 0, Class=Communications, Driver=cdc_acm, 12M
|__ Port 2: Dev 10, If 1, Class=CDC Data, Driver=cdc_acm, 12M
|__ Port 2: Dev 10, If 2, Class=Human Interface Device, Driver=usbhid, 12M

So a video device (uvcvideo) aaaand a usb human interface device (usbhid).

All I get in windows when connecting via the virtualhere client is that cdc_acm port which is basically a thing for emulating serial ports over usb. I will totally ping him in discord and link this thread while I still have a fire in by belly and energy about it.

#11

It is currently not a high priority for them as they have a very long list of todos. I will post any updates here but I am guessing the more people that ask about it the higher it will be on their plate.

#12

OK thanks for the info

#13

I know this was from a bit ago, but I'm wondering if this issue was ever sorted out. With amazing emulators like TeknoParrot, I'd like to use my primary gaming rig (VERY non-portable) and stream lightgun games.

I'm keeping my fingers crossed... :)

#14

Sorry i dont know. Just give it a try and see if it works ok

#15

For anyone else doing a Google search and finding this thread, I can report that with the paid version of VirtualHere running on my Nvidia Shield Pro 2019, BOTH guns work PERFECTLY when plugged into the Shield with my emulators running on my PC.

LOVE this product!

#16

Great, thats excellent news!

#17

@wazooda

Thank you so much for confirming it worked for you. I also have the Nvidia Shield Pro 2019 and 2 Sinden guns and was able to get them working via Moonlight.

I made the mistake of buying the 3 device license from within the Android app and realized I needed the unlimited license (which wasn't an option through the app) to get 2 guns to work. I bought the unlimited license as well and will try to get a refund from the Play store.

 

#18

@redman223

Yeah. Pretty bulletproof. Occasionally, I'll hear the "bloop bloop" sound signifying a USB disconnect like I unplugged the guns from my computer. I think it is VH temporarily losing connection because it is often followed by the tone of replugging in the gun(s). Unfortunately, the Sinden software (I'm running Beta 2.05 I think) doesn't handle that well and I have to restart the lightgun software.

Other than that, I don't notice any appreciable lag over and above the "normal" Sinden issues.

 

BTW...Do yourself a favor and find Carnival King on MAME. I stumbled upon it and it is fantastic. Has a Toy Story feel like the ride at Disneyland/World.

 

Enjoy and Happy New Year!