Hello,

I'm looking for assistance in regards to VR development with the Leap controller and Oculus Rift DK2.

I'm experiencing serious problems with the Leap tracking FPS whenever the Oculus positional tracker turns on. Similar problems have been observed by others in the following threads:

community.leapmotion.com Leap FPS drops when used with Oculus Rift DK2 It's already attached directly to an USB port. Even changing the port doesn't solve anything.

community.leapmotion.com Leap Motion extremely slow with ANY usb-camera connected - Oculus Rift Hub working fine! What was most strange is, other combinations (f.e. Oculus IR Cam + Webcam) work well together. Maybe it is something in the Leap-Motion-Camera-Driver throttling to willingly?! More on this once the USB3 card arrives...

However, none of the replies in these threads provide a solution. This situation halts my development (and research) and I'm struggling to find a way to continue with my project.

Here is my setup:

Asus G751Y laptop with 4 USB 3.0 ports. Only things plugged into the ports are the Leap controller, Oculus Rift HMD and the Oculus positional trackers. The Leap tracking has been calibrated with a very clean mirror and the tracking works fine initially.

I'm using Oculus Runtime 0.5.0.1, Leap Software Version: 2.2.5+26752 and Leap Firmware Revision: 1.7.0.

Testing procedure:

Initially, Leap tracking works fine indicated by the visualizer displaying ~115 FPS. Turn on Oculus Config Tool, which turns the positional tracking camera on as well. Leap tracking FPS drops to ~8-15 immediately and the device is unusable in this state. Closing the Oculus Config Tool turns the positional tracker off. Leap tracking FPS goes up to ~81 and stays there. Reconnecting the Leap controller bring the tracking FPS back to ~115.

I have 4 USB ports and I repeated this test with the devices plugged into the laptop in every possible configuration. The same behavior was observed in every case. Connecting the Leap to the USB port on the Rift HMD gives the same results.

I also did this test with another, freshly unboxed and unused Leap controller and observed the same results. Another test with another computer (a desktop machine) and it's USB ports (both in the front and the back) showed similar results, although the tracking only fell to around ~30 FPS. It was still unusable for any scenario. This desktop computer had Oculus Runtime 0.4.2 installed, so I would conclude that the problem does not lie with the new 0.5.0.1 version.

Help?

To me, this is a serious show stopper as I can't use these devices together, which is the whole point of my project and research. I would like to hear from the Leap guys or anyone else with similar problems, has anyone found a solution? Is this a hardware problem? Can I solve it with an externally powered USB hub? I can't install additional USB cards as I'm working with a laptop.

Edit: I have made a support request via https://support.leapmotion.com.