Leap Motion interferes tracking of Vive Tracker

[AlexColgan]

To be honest, this seems like it might possibly be part of a broader issue with how the Vive motion trackers handle ambient (or artificial sources of) infrared light. We don't have the bandwidth internally to tackle this particular use case and in any event it seems likely that only HTC can resolve it.

[ariza.oscar]

We are experiencing exactly the same issue reported by bynumdav
Have you found any solution to this problem?

[danielleithinger]

I assume that there is no solution to this problem? I am running into exactly the same problem here and will have to use an alternative to the Leap Motion for my project as it renders the Vive Tracker completely unusable. Shame.

[jhung]

Unfortunately, we haven't been able to reproduce the issue with the Vive controllers, though there seems to be consensus in the VR community that puck tracking is not as robust and more issues may be anticipated. we don't have any tips other than experimenting with the placement of the base stations.

[antoinerigitano]

Hello,

There is no problems with the Vive controllers, only with the vive trackers:

VIVE™ | Vive Tracker

Could you experiment on one of those?

Thanks a lot for investigating on this.

[mmorselli]

Hi Jhung, let me be direct, you can answer with yes or no: have you tried it with trackers? (not controllers)

[jhung]

Yes, our engineers have tested with the tracker.

[Aver]

Hi everyone, we are experiencing this issue also and would really appreciate a fix.

This thread explains why the trackers may be more succeptible than the HMD/motion controllers:

VIVE Trackers conflict with cameras of motion capture system

The Vive HMD and the controllers use an HTC/Valve designed light to digital converter and PBC assembly whereas the Vive Trackers are using Triad manufactured TS3633's as well as a new PBC design. This could explain why they're more susceptible to IR interference than the HMD/controller technology. They fundamentally preform the same function but have underlying differences in design. This may mean that other technologies that will use the TS3633 may also face similar interference issues.

Do you guys know how we might be able to get around this issue with the SteamVR 1.0 trackers, and whether or not this issue will be a problem with the SteamVR 2.0 trackers?

[AlexColgan]

Getting a 404 error on that link.

[Aver]

Sorry, I fixed the link =)

VIVE Trackers conflict with cameras of motion capture system

Is there any way to dim the IR light coming from the leap motion perhaps?

[AlexColgan]

Unfortunately there is not.

[Aver]

Are we able to shift the IR spectrum frequency? Or perhaps the frequency/duration of the the light pulses?

Perhaps there's a film we could put over the LEDs that would absorb some of the IR - this would come at the cost of hand tracking distance or perhaps the ability to detect hands in a brightly lit environment (our particular use case could be in a reasonably dark environment).

[Aver]

Has anyone been able to get their hands on the new (2018) trackers and are able to share if Leap Motion interferes with that version also please?

[mat_kinotek]

yep still interfering pretty badly ..

[bradherman]

Heads up that this seems to work now with 2018 trackers, 2.0 lighthouse, and 4.0 leap.

[diedredesign]

Hello,
It is/was stable or near for you ? Any news ? Still get the same issue with vive tracker 2018 (blue logo).

[kipphil]

Still having this issue, but I'm using 2018 trackers with a 1.0 lighthouse. It is definitely the leap motion interfering An extra datapoint to validate that it's not obstruction from the lighthouse: if I plug in and out the leap motion, the problem reappears. I'm going to get a 2.0 lighthouse to try as well.