Device detection problem in VM

[inux]

I want to use a Leap device in VM.
The host and guest OS are Windows 8.1 and the guest is running in the latest version of Virtualbox.
I connected an USB port to the VM and the Leap is shown as a webcam device in the Virtualbox setup menu.
However, Leap manager in the guest OS does not detect the Leap.
I attempted to remove Leap driver from the host OS, but it didn't work.
How can I use my Leap device in this VM Windows setup?

[jdonald]

Dealing with device connectivity issues inside a VM isn't too different from troubleshooting on actual hardware.

Could you show a screenshot of how the Leap Motion Controller enumerates in Device Manager inside the guest OS? That will give us an idea of whether it's the guest OS having a problem enumerating the device, more so than the "Leap manager".

If you don't see the Leap Motion controller under Imaging Devices or any other node, then the problem is higher up such as with VirtualBox or the guest OS. Whereas if you see problems like a red x or a yellow question mark, we can troubleshoot those issues with approaches like the WinUSB driver (C:\Program Files (x86)\Leap Motion\Drivers\dpinst64.exe).

[inux]

I attached a screenshot of device manager in Virtualbox (Sorry for the korean labels).
The guest OS recognizes the device as a webcam while the leap manager says the device is turned off.

[jhung]

Does anything happen if you right click on the Leap Motion control panel icon and select "resume tracking"?

[jdonald]

While this had typically worked for us under VirtualBox VM, my coworker was able to reproduce your issue. It appears you must have connected the device to the guest as a Webcam. If you instead select it under Devices -> USB, that should make it at least enumerate properly in Device Manager.

See attached screenshot for reference.

[inux]

Thank you for the response.
I tried to connect the device in both ways and they didn't work: as a normal USB device and a webcam.
When I selected the leap controller on the list of USB devices, it didn't leave a check mark with an error code of E_INVALIDARG (0x80070057).
Should I install the device driver on the host OS or not?
Currently, the driver was uninstalled from the host OS.

[jdonald]

Not sure if we'e seen E_INVALIDARG via the Device Manager before. Could you post a screenshot of that?

Normally we don't recommend installing the WinUSB driver, but it is a workaround if the Leap Motion controller fails to enumerate and shows a red X or yellow question mark in Device Manager. You can install it via C:\Program Files (x86)\Leap Motion\Core Services\Drivers\dpinst64.exe. Well, assuming that's what you mean by the "device driver".

It's also possible that when you say "device driver" you are referring to the Leap Motion Core Services software (the one that puts everything under C:\Program Files (x86)\Leap Motion), and yes you should install that!

[inux]

I resolved the problem by using VMware, instead of VirtualBox.
Thank you for the support.

[aecroft]

Hi,

I am struggling with a similar issue trying to connect Leap Motion on Mac using Virtual BoxWinDev1612Sys and Windows 10 (64-bit). I've checked the Device Manager that my Leap is detected as a USB device:

And I have run the Drivers\dpinst64.exe

The only error I am coming across is when I try to recalibrate the device:

And I haven't been able to find a solution to this. Could this be causing my problems?

Basically when I open the Diagnostic Visualiser nothing appears even though in the control panel the Leap is detected and the icon is green.

Any help would be greatly appreciated!!

Thanks,

Amy

[jhung]

That error seems to mention an issue with the screen resolution. Have you checked to ensure that the color settings are set to 32-bits?

What happens when you try running other Leap Motion apps?