Have you managed to have a play around with our Gemini Developer Preview yet?
If so, we’d love to hear what you think!
Your feedback is really valuable and will help us shape the general release.
Drop us an email at email@example.com.
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?
Thanks for reporting this, I have responded to your other post here.
I wanted to try it, but unformately it supports only "Intel® Core™ i3/i5/i7 processor" and I have i9.
Those processors listed are part of the minimum system requirements, the i9 is a more powerful processor than these and the Leap Motion Controller or Stereo IR 170 Evaluation Kit will work with it.
To add for future readers of this thread, the issue above with the Leap Service not running correctly was due to the PC uses an Intel Xeon which does not support AVX, a current requirement for our Gemini Developer Preview.
I have been using it in C# (using a version of the Unity library), and love the improved tracking. However, I've gone back to the 4.0 SDK because I found that after some amount of time (30 minutes+), the tracking would just stop and I would stop receiving events until I restarted my app. I didn't spend time debugging because I figured it was a beta release issue and I'd save my debugging energy in case it showed up in final because it was probably my fault
Source code for my app is here.
Hi Frenzon, thank you for reporting this. This isn't an issue that we have seen with our V5 Developer Preview before and we would like to investigate this further.
Please can you email me a copy of the Leap motion software log when this issue occurs and your system specifications to firstname.lastname@example.org so we can look into this?
Unfortunately, I had to downgrade to the v4 because of 2 things:1. Sometimes my hands wont be initialized when entering Play mode in Unity editor, need to re-exit Play mode in order to get it working. Using unity 2020.2.4 with Leap 4.7.1 modules.2. Bending down ring finger only (while other fingers stay straight) will give some strange and wrong pose estimation.
Thanks for sharing this feedback, I am sharing this report of these issues with our tracking team.
If you have any information, screenshots or screen recordings that show these issues please can you send this to me at email@example.com and this will help us to investigate further.
I use Gemini in a Unity, the second hand still disappears if hiden with the first hand.the second problem is that when the scene starts, the hands do not appear, this sometimes happens twice
Thanks for reporting this Anvarito, please can you send me some information about the device and software versions that you were using and the orientation of the tracking module? Ie. was this a Leap Motion Controller or Stereo IR 170 in VR or Desktop Mode and which versions of Unity and our Unity modules were being used?
I have fed this back to our tracking team and this information will help them investigate further.
Device Stereo IR 170, version Unity - 2019.4.18f1.Can you describe in more detail how to switch modes between Desktop and VR?
I recommend having a look at our Unity Modules documentation for our Core Modules here as well as the second question in the FAQs section here which will guide you to get hand tracking into your Unity scene in both VR and Desktop mode.
I occasionally get 2 hands appearing when I only have a single hand in the tracking area. The two hands are partially on top of each other, with one hand being at a very different angle than the actual hand. This occurs both in the virtualizer and my own app.
Please can you let me know which camera position you are using when you see this issue?
Is the tracking module in VR mode or desktop mode?
camera on tabletop looking up - I just tried to replicate it but was unable to. I'll try later today and get a video for you.
No hands there
Hi, thank you for reporting this issue.
To test this please can you face a blank wall and hold up your hands in front of you. Are these able to be tracked well and without the issues shown in your screenshots or do the issues persist?
Additionally are you able to place the tracking module in desktop mode and see if there are any issues with tracking present with this orientation?
When LeapMotion is recognizing a hand and I move my hand quickly, the recognized hand is no longer recognized.This is not the case in v4.1.
Hi, thank you for this feedback!
Are you using the Leap Motion Controller in desktop mode or VR mode?
It would be great to see a screen recording of this so we can share it with our engineering teams. Are you able to record this happening and share it with firstname.lastname@example.org?