Small Hands discovered as the wrong Right/Left in Top Down

[zvilich]

Hello,

Does Leap support Non-HMD Top Down tracking?

(Leap sensors facing down , hand palm is facing up).

I have read conflicting posts in the Forum, i currently still use the 3.2.0 Core SDK.
the app was written two years ago but there are some field testing issues now.

The main issue is that small hands are sometimes tracked incorrectly. we always use right hand.
and sometime the Leap's tracking thinks it is left (Via isRight=false and the flickering display).

So, does Leap support Non-HMD Top Down tracking? and from which version?
Any other thoughts or example on fixating the hand to be right only?

Thanks
Yair

[AlexColgan]

We don't support non-HMD top-down tracking (e.g. directly downwards towards the hand) and there is no way to predetermine the hand chirality (left vs right).

[zvilich]

Is the Issue is the table or the position of the hand?

[AlexColgan]

The orientation of the device relative to the hand is the issue, since our software makes certain assumptions to determine chirality.

[zvilich]

I appreciate the quick response
1. What general affect on the tracking or assumptions does the _isHeadMounted property of LeapServiceProvider have?
2. in _isHeadMounted = true, what should the general Device <-> Hand orientation be ?
3. in _isHeadMounted = false, what should the general Device <-> Hand orientation be ?
4. I understand the sensors are agonstic to the orientation in real space and do not have a gyro, do i assume correctly?
5. What is the good option to set when mainly using the palm facing towards the sensors?

Thanks

[AlexColgan]

The head-mounted flags flip the software between the desktop and HMD-mounted tracking states. The sensor is agnostic to where it is in space, but as an optical sensor it has to interpret what it sees. If the palm is mainly facing towards the sensors and the hands are oriented downwards, the best option is desktop mode.

[zvilich]

if i change _isHeadMounted at runtime and not in the editor does it have an affect on the tracking state?( or is it set once in initilization)?

****edited
I managed to do this with calling the SetPolicy; and i see the affect at runtime;