Unable to run Blocks application after updating to Orion 4.0.0+52173

Tags: #<Tag:0x007f81cc153e70>

SteveCox 2018-07-17 02:58:27 UTC #1

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.

HOTTHANDS 2018-07-17 04:26:49 UTC #2

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

jhung 2018-07-17 15:24:28 UTC #3

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

SteveCox 2018-07-17 16:24:56 UTC #4

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.

jhung 2018-07-17 18:45:47 UTC #5

Could you download and run our log collecting tool?
https://leapmotion.box.com/s/stflcgfa35tvi55x67ma1biho95jtcqc

It should make a directory on your desktop with a bunch of files in it. You can PM me the files if you don't wish to publicly share them.

jhung 2018-07-17 20:45:33 UTC #6

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-Services

HOTTHANDS 2018-07-17 21:40:11 UTC #7

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.

jhung 2018-07-18 15:52:41 UTC #8

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?

Evil_Lord_X 2021-01-08 11:55:56 UTC #9

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.

dankirby 2021-01-12 16:52:12 UTC #10

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

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