Leap Motion won't connect on Windows 10/Raspberry Pi (Tried hotfix)

[b7022714]

I am trying to use a Leap Motion for development with Processing, but the LM won't connect.

first i used to latest SDK and the LM works in the control panel but wont connect when i try to run code in processing. (i have code running which constantly prints if the LM is connected or not).

I then tried downgrading to version 3.2.1 of the Orion software and i get the exact same issue as before.

then I tried the hotfix with the version 3.2.1 of the Orion software from here: https://forums.leapmotion.com/t/resolved-windows-10-fall-creators-update-bugfix/6585

but after i unzip the hotfix files into core services and try to start Leap Service again i get the following error:
Windows could not start the Leap Service service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion,

In Device Manager, the Leap Motion is recognised under 'Cameras'.

I also tried to downloaded the linux SDK on a raspberry pi, but when i try to install the .deb file i get an error saying:
A package could not be found that allows the action to complete.

Any idea how to fix any of this?
I was hoping to use the LM on the raspberry pi so if anyone knows what that error could be also that would help too.

[dankirby]

Sorry for the confusion, you don't need to add the hotfix files to the V3 SDK as this is already updated to work with the Fall Creators Update and later releases of Windows 10.

Have you seen the guide to using the Leap V3 SDK with processing in our documentation here?

If you do a straight install of our V3 SDK from here do you see any errors? If so, please send a few screenshots of the Leap Motion Control Panel tabs to support@ultraleap.com and I will be able to help you with this.

Please note that our V3 Leap SDK does not support background apps, if this might cause an issue for you then an alternative is to use our V2 SDK available here and apply the hotfix.

In its natural state our hand tracking software is too substantial to be deployed on a Raspberry Pi. However, we are aware of situations where people have been able to get this to work through modification of the software to lighten it. My recommendation is to stay tuned to our social channels and news feeds later this year for any announcements that we make concerning this. Unfortunately I cannot say more than that at this time.