Reach 1.0.1 + latest Orion drivers

Reach always sends
/Right/palm 0. 0. 0.
/Left/palm 0. 0. 0.

Currently there is no support for tracking rotational data of the hands. An implementation of this could greatly enhance the possibilities of creating OSC driven projects using Reach.

When set to normalised values and head mounted mode, the value of the right hand's Y-axis does not change with the hand's distance from the sensor. Instead, it emulates the X-axis value with a different range.

The value in regular mode (non normalised) works correctly.

Hi Niccolò, grreat stuff!
Is Reach supporting the last LeapMotion Gemini? Any link to Orion leads me to Gemini download...
thanks

Currently there is no support for tracking whether the user's hand is open or closed. An implementation of this feature could greatly enhance the possibilities of creating OSC driven projects using Reach.

The previous link to Orion V3 is no longer valid (it links to V4). Here is an updated link that you should consider placing in your documentation: https://developer.leapmotion.com/releases/leap-motion-orion-321-39frn-3b659

would you consider adding velicity (for... everything !) and elbow position to the OSC output messages ?
(I'm using it to draw fingers / hands in VR, having the additional elbow position would be cool :-)

thanks

Hi,
Leap Motion does not seem to connect with Reach. Not sure if it has to do with the versions or doing something wrong. I can't seem to find any instructions of setup either. Any ideas?

Consider:

https://developer-archive.leapmotion.com/documentation/cpp/devguide/Leap_Policies.html?highlight=hmd

Implement:

controller.setPolicy(Leap::Controller::POLICY_OPTIMIZE_HMD);

Thanks for sharing Reach !

is there a way to avoid entering manually my ip / port / framerate settings in the UI each time I start Reach ?
maybe using command line arguments ? (couldn't find doc about it)