This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.
Feb 2017
1 / 14
Feb 2017
Jan 2018
user-250018621
Feb '17

Dear LM,
I have used Leap Motion for several years and really enjoy its functionality. However, I recently installed Orion on a machine running Windows10 and cannot get it to work outside the demos. 

 Specifically, although the visualizer works perfectly and I'm also able to get Touchless and GameWave to work in their demo environments, as soon as I leave the demo pages, I cannot get either to work beyond the latter pages.

 Is there a known problem in using either of these in a Windows 10 environment?  It seems like the basic functionality is there, but I can't get it to extend beyond the demo environments.  It seems like a switch needs to be thrown somewhere?  I do note the suggestion to install v2 in a Win10 environment, but because I can get the controller to work in the demo environments, I want to say my problem is different.  But, I'm not entirely sure.  Does anyone have any insight ion this issue?  Thank you.

GenomeIP

  • created

    Feb '17

  • last reply

    Jan '18
  • 13

    replies

  • 8.0k

    views

  • 6

    users

  • 4

    likes

jhung
Feb '17

Could you elaborate on what you mean by the "demo environment"? There shouldn't be any issues using the controller on Win10

Some older apps will only work when the app window is in focus when running the Orion software. Installing the older V2 software should resolve this issue

user-250018621
Feb '17

Thank you for your comments. Essentially, within Touchless, there is an introductory orientation module that shows you how it works. When I'm within that demo, I can get Touchless and the Leap Motion device to work perfectly (same within GameWave). But, as soon as I close those windows/modules, the pointer simply doesn't respond to any inputs at all - even though both Touchless and GameWave were activated. I have selected the pages in which I wanted to use Leap Motion (i.e., to ensure it is in focus), but that doesn't make a difference here.

I want to say it is an ActiveX issue because when I open the Touchless demo module, it also won't respond to inputs until I activate ActiveX by clicking on the dialog box that pops-up asking whether or not to activate the same. As noted before, the device is working fine (e.g., in visualizer, in these demo pages), it's just that I can't get it to work outside of these environments.

With that said and assuming my intuition is correct, I don't know how to activate ActiveX in the absence of a dialog box asking me if I want to do so.

jhung
Feb '17

What Leap Motion software version do you have installed? You can check on the About tab in the Leap Motion Control Panel

user-250018621
Feb '17

I have installed 3.2.0+45899, and am running Windows 10 Pro, version 1607, build 14393.693

Hope that helps.

jhung
Feb '17

As I said in my earlier message, there's a bug with older apps on the Orion software that prevent them from working in the background. Try downgrading to the V2 software and they should work in the background again

jhung
Feb '17

Happy to hear it! Please let me know if there's anything else I can help you with

10 days later
Aremi
Mar '17
jhung

Thanks you! I had the same problem and i have solved it with LeapDeveloperKit_2.3.1 smile

10 months later
mirv
Dec '17

So do people just not use orion at all anymore & only use V2 since there's a bug with the service?

AlexColgan
Jan '18

They do if it's critical that they run older (pre-Orion) apps that are required to run in the background on Windows 10.

mirv
Jan '18

Roger, thank you!

That brings up the second issue then - but i'll make new issue for tracking.

21 days later
ylm2103
Jan '18
jhung

It works with version 3.2

but it is stop dead for every 10 second

Let me know how to solve it

jhung
Jan '18

Open up the software log and send me a copy of the contents so I can troubleshoot the issue for you