Gemini Preview Leap Service will not connect

T8er8 2021-02-19 23:34:49 UTC #1

Re posting this to a separate thread but was mentioned in developer feedback as well

Hi, Unfortunately this preview has not been working for me, Orion has worked great, but it seems like in Gemini the Leap Service (leapsrvc.exe) crashes right after it starts. I am on Windows 10 and I have a few dmp files if needed. I've tried countless ways of starting the service, and changing the drivers. I tried to use the Orion leapsrvc.exe file in Gemini which started the service properly but it refused to make device connection, which makes sense given its a different version. The Hex code hotfix looked like it was already included, I replaced it anyways and it still failed. The service still stops itself right after starting. any help?

dankirby 2021-02-22 12:01:36 UTC #2

Hi, thank you for reporting this.

Please can you send these dmp files to support@ultraleap.com along with your machine spec and I will help you directly with this. Also, a few questions to help me investigate:

Was the version of Orion that was working well for you either 4.0.0 or 4.1.0?
If you redownload the software and perform a fresh install do you still get this error?
If you open the services app and manually start the Leap Service does is consistently crash straight away?

T8er8 2021-02-22 15:30:00 UTC #3

Thanks for the response,

I just sent over a dmp file along with my system spec to the email provided.

To answer your questions:

I'm using 4.1.0+52211_win which works perfectly
Done multiple times and the same error still occurs
As soon as I start it in the Services app, it starts for about half a second, then crashes

Some more behaviour I've gathered:

Starting leapSvc.exe as admin brings up a command prompt window which has the following output right before it crashes

While trying to get this screenshot I noticed that it decided to not crash one time, in this case it did not show the last two lines, however when I tried to run the diagnostic visualizer, the cameras would run but it would not pick up my hands, the data fps was only around 3 and it certainly was not working properly, that occurrence could just be an anomaly.

I can run the calibration test perfectly fine without having the service connected.

Thanks,

T8er8 2021-02-22 16:33:03 UTC #4

For anyone else with this issue as well, Gemini needs the AVX instruction set which isn't supported on older CPU's such as mine (Xeon x5680).

klejens 2022-03-26 02:14:45 UTC #5

"Gemini needs the AVX instruction set" -- we do not understand that decision by leap motion at all -- as a game developer company we need to be compatible with our users and not everyone (most) have the latest CPUs in their pc's --- unfortunately we will have to look into a different hand tracker solutions because of this.

dankirby 2022-05-20 15:39:05 UTC #6

The Gemini V5 hand tracking will not work with non-AVX CPUs as the software requires this to function, please see our release notes here for details on the minimum requirements of Gemini V5.

Unfortunately it is not possible to get Gemini V5 working with a CPU that does not support AVX instructions. Whilst the majority of modern CPUs support AVX instructions if you are using a non-AVX CPU then I recommend using our Orion V4 hand tracking software which doesn't have this requirement.

Currently this not a requirement that we are currently looking at changing as AVX instructions give us the optimisations that we need for our tracking improvements. I hope this provides some context.