Offset between eyes and Leap Motion on HTC Vive

NerdGirl88 2017-05-02 13:57:26 UTC #1

Hi guys,
I realized that the distance between the eyes and the physical position of the Leap Motion causes a distant effect of the hands to their real position.
Is there a way to fix the problem?

_mike 2017-05-25 00:35:09 UTC #2

I have possibly the same issue... a mismatch between LEAP hand positions in VR and real hands.

I thought I saw an offset value somewhere to account for the distance between the LEAP sensor and the eyes, but I can't find it anymore.

anyone know?

thx!

AlexColgan 2017-05-25 12:47:42 UTC #3

This is achieved by VRHeightOffset: https://developer.leapmotion.com/documentation/unity/unity/Unity.Prefab.LMHeadMountedRig.html

_mike 2017-05-25 17:35:07 UTC #4

Hi Alex,

We are talking about an offset between the eyes(camera) and the LEAP sensor.

This is just our guess at a possible solution to the mismatch between real hand positions and virtual hands.

...not the height of the VR camera, not sure where you got that from

thanks

AlexColgan 2017-05-26 12:01:40 UTC #5

You're right, that was my mistake. There is an offset value between the center eye anchor game object and the Leap Motion prefab. We're looking into an issue that may be related, stay tuned.

jbonastre 2017-09-13 13:46:42 UTC #6

Hi Alex, could you explain how to change the leap motion offset? I´m trying to move the camera to a higher z position but I´m not able to adjust the hands offset in any way =(

AlexColgan 2017-09-14 19:57:55 UTC #7

Get the latest version of the Unity Core Assets from https://developer.leapmotion.com/unity as we just introduced a new method to make adjusting the offset easier.

Specifically, we added a checkbox to allow manual Leap Motion Controller pose alignment on the LeapVRTemporalWarping script. Available parameters are forward offset, vertical offset, and upward/downward tilt. These settings are tied to the application, not the headset, so these settings should only be used under circumstances where the application will be run in a known headset configuration

jbonastre 2017-09-15 06:45:38 UTC #8

Could you check the version.txt file? It indicates that it´s version 4.3.1 instead of 4.3.2.

Cheers!

AlexColgan 2017-09-15 11:48:46 UTC #9

Thanks for flagging; the version number in version.txt is incorrect. I've submitted a PR to fix it.