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?