Leap Motion Orion bugging on LattePanda (4G RAM, 64G eMMC)

Tags: #<Tag:0x005609311cbb10> #<Tag:0x005609311cb980>

GranieriNiccolo 2017-12-29 10:19:41 UTC #1

Leap Motion is exhibiting a strange behaviour on LattePanda 4G RAM, 64G eMMC running Windows 10 Home edition, Version 10.0.16299. (Latest update released 10/17/2017)

The SDK installs fine, no problem encountered. The leap motion, connected to the USB 3.0 port, is detected correctly, on the settings the signal and all the other parameters are analysed as good. The light on the device is green, and on the icon too.

The problem appears when the visualiser is launched. The leap motion not connected screen appears, and stays there no matter what. Also the VR headset not detected shows up, but that doesn't seem to be a problem on my other windows machine. The same behaviour happens with my unity app. The app runs fine but no hands are tracked even if the leap motion is detected correctly.

Also, there is nothing on the logs that might point at a specific fault.

The weird behaviour is that when in settings I tried to troubleshoot the visualiser, it works fine. The image from the LeapMotion comes through clean and the hands are tracked smoothly on screen without hiccups.

Is there any major difference between the visualiser and the troubleshoot visualiser that would prevent the first one to work.

Might windows 10 home be the issue? Does Orion need Windows 10 pro?

Thanks

jhung 2017-12-29 16:06:46 UTC #2

Try restarting the service to see if that helps https://support.leapmotion.com/hc/en-us/articles/223784008-How-to-Manually-Restart-Leap-Core-Services

GranieriNiccolo 2017-12-29 16:30:13 UTC #3

Tried restarting manually the services just now, and nothing changes.

Nothing, except for the "Diagnostic Visualiser" works.

jhung 2017-12-29 16:32:10 UTC #4

Does hand tracking work with any apps downloaded from gallery.leapmotion.com ?

GranieriNiccolo 2017-12-29 16:41:54 UTC #5

Just tried downloading the Hands Modules from the gallery and it works. Visuals flicker for some reason, but both hands are detected, and there is tracking.

jhung 2017-12-29 16:44:14 UTC #6

Strange, it looks like like a problem within your Unity application then since tracking works with other apps and demos from the Gallery. Unfortunately, I'm not able to provide any assistance with debugging as I'm not too well versed with the SDK but our community members and engineering team may be able to assist you

GranieriNiccolo 2017-12-29 16:48:25 UTC #7

It could be. But why doesn't the inbuilt visualiser work? I hope somebody from the community or engineering team comes to assist. Thanks a lot jhung.

jhung 2017-12-29 16:52:12 UTC #8

What Leap Motion software version do you have installed and what app did you test with from the Gallery?

GranieriNiccolo 2017-12-29 16:56:38 UTC #9

Leap Motion Version: 3.2.1+45911
App: https://gallery.leapmotion.com/hands-module/

jhung 2017-12-29 17:02:52 UTC #10

Thanks for the info. I've forwarded this thread to our engineering team

GranieriNiccolo 2017-12-29 18:06:43 UTC #11

Rebuilding the app from the LattePanda fixed the issue for my Unity app, but the visualiser keeps saying the leap motion is not connected.

jhung 2018-01-02 16:41:25 UTC #12

Is this issue limited to the visualizer? Are other apps functioning correctly?

GranieriNiccolo 2018-01-02 16:53:27 UTC #13

After recompiling on the LattePanda itself, my app works sort of fine (minor some stuttering). And the other apps from the gallery I tried work fine.

The visualiser instead continues not to work.

jhung 2018-01-02 16:54:58 UTC #14

Thanks for the info, I've notified our engineering team to investigate

jdonald 2018-01-02 20:15:45 UTC #15

Is there any major difference between the visualiser and the troubleshoot visualiser that would prevent the first one to work.

This is the VRVisualizer, the one opened by right-clicking the Leap Motion Control Panel -> Visualizer...? If so, yes that is an app written in Unity using the LeapC API (albeit an old build of it), while the Diagnostic Visualizer uses the even older but more battle-tested C++ API.

That said, we'd like for both to consistently work. It's not clear why the VRVisualizer has trouble on your particular Windows 10 system. We've fixed a number of issues in the LeapC layer and will look into ensuring this is resolved on all systems on the next release of the VRVisualizer Unity app.

In case this is already fixed with the latest LeapC.dll, you can build it from source from the UnityModules repo, this scene file.