Leap Motion behavior and solution you may not have know you needed.

[dmitriyc]

Hey peeps! I tried this on two separate Leap Motions and with the same results: When you bring your hand into the sensor field of operation and the Leap module registers your hand (say the right), it will let you bring in the opposite hand (left in this case) in and out of the field without any anomalous behavior. It gets tricky, however if the original hand disappears from the sensor field and the new hand stays. The sensor data for palm sphere radius and a bunch of other arrays cut off for a very significant amount of frames and there is no output other than "num hands" and "frame id".

The solution: linking "num hands" to the "enable hands" in the Leap module so that every time only one hand is operating the Leap, it toggles itself off and on and you're able to avoid this weird behavior.

If there is a more elegant solution, would love to hear about it.

-Update: So in dealing with spheres (fist vs open hand), because of the resetting solution above, a data matrix based on "hand presence" is necessary to route the correct data stream to the correct hand.

-Update: So the data only seems to stop at the Leap module, but if connected to an array, the info still passes, leaving my solution to be a dead end. Equally as important to note is that in order to differentiate which array gets which hand's telemetry and stays there, a solution is to make a workflow that clamps down which hand was first. I know there is a script around the forums that gets you there, but it changes the index even though there is a hand already on the leap, which then alternates which hand is read. The solution to THAT is upon sensing presence of first hand, the behavior of which array is being passed stops the flow of the other hand being able to change the index until both hands are off the leap.

[nay-seven]

Thanks for the tips !