This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
1 / 10
Jul 2018

Is the Blocks application compatible with the latest version of the SDK?

It was working fine before the update but now I simply get the screen showing that I need to connect the Leap Motion controller. Device status is all green in settings and other applications appear to be working without any problems.

My firmware revision is 1.7.0

Blocks is one of my favorite applications for demonstrating VR and I was disappointed to not be able to use it tonight.

  • created

    Jul '18
  • last reply

    Jan '21
  • 9

    replies

  • 2.7k

    views

  • 5

    users

  • 4

    links

We have found that redownloading and reinstalling everything over again is the only way we could help the controller service and device find each other again...
after a Windows Update, Unity update or a change in any of the LEAP materials
...or actually anytime the Windows plug and play fires up...
Good luck

Is Blocks the only application giving you this issue or does this issue occur when running other apps as well?

Blocks appears to be the only problematic application. I'm able to run Cat Explorer, Paint, Particles, Pinch Draw, etc. without any issues. The Diagnostic Visualizer works fine as well.

If the service stops and needs to be restarted, you can do so by following the instructions here: https://support.leapmotion.com/hc/en-us/articles/223784008-How-to-Manually-Restart-Leap-Core-Services16

Thanks for the quick link! We have not been successful in stabilizing with this method... it just blows out again. However, we have quite a bit of other things going on in our development machines.

Next time this occurs, could you open up the software log in the Leap Motion Control Panel and post a copy of it so I can take a look?

2 years later

Did anyone find the cause of this or the fix? I just started having the same problem.

Uninstalled LEAP SDK and installed the latest 4.1, fresh copy of Blacks and still have the same issue.

FYI the links for the manual restart posted above are now dead.

The URL for this article changed after we migrated our Help Center and it is now hosted here3.

In my experience the Blocks app works better with our V3 software7 and I recommend installing this version of our SDK to use with Blocks.