Leap Motion not working

[dan-ewo]

Activated in menu, no finger are showing up.

[jbaicoianu]

I've started moving the hand tracking code away from the old websocket-based leap motion specific code and onto the new WebXR Hands spec, so the old code has been disabled in favor of the new standard way of working with tracked hands. This should give us access to hand tracking on any OpenXR-enabled device.

Leap motion has released an experimental OpenXR build, which is available here: https://developer.leapmotion.com/openxr

Chromium devs have expressed an intent to prototype support for exposing OpenXR hands in desktop Chrome, but it looks like there hasn't been much progress on this front yet. https://groups.google.com/a/chromium.org/g/chromium-discuss/c/NXdO6NOGkao and https://www.chromestatus.com/feature/5719474055413760 track that status.

Another possibility is if someone were to create a polyfill that presents the Leap Motion hand tracking data through the new WebXR Hands interface. I'm not sure if anyone's started that project yet, but if someone wants to take on that task I'd be more than happy to share my expertise and help guide that project.

[jbaicoianu]

I asked around on Twitter, sounds like Oculus did work with devs from Microsoft and this should be working with MS Edge now. I've been trying all day to get it working, but with no luck so far. I can't get the Leap Motion to work with native OpenXR apps either though, so I suspect I need to figure out what's happening there before it'll work in WebXR.

I suspect it may be due to the fact that UltraLeap just released a major new revision today, so maybe that broke something either in the UltraLeap OpenXR package, or in Edge. Will keep banging on it, because it would be awesome to get this working again.

[jbaicoianu]

Twitter thread here, for reference https://twitter.com/bai0/status/1453423174230573057