gemini v5 release notes

Ultraleap Gemini V5.3 Release Notes

  • Tracking Visualizer does not default to Desktop mode when launched: Launching the Tracking Visualizer does not automatically set the tracking mode to Desktop. It will first display the tracking mode that has already been set by another application (e.g. TouchFree). Pressing “V” to cycle through the tracking modes will still make changes to the tracking mode used by the tracking service.

  • Software log rotation: Log rotation is now setup so that the most recent logs are in tracker_log.txt followed by tracker_log.1.txt , tracker_log.2.txt and tracker_log.3.txt

  • API update: The PID identification for the Stereo IR 170 Hand Tracking Camera has been updated. The Stereo IR 170 will now return an identification of eLeapDevicePID_SIR170 in the LEAP_DEVICE_INFO structure, rather than eLeapDevicePID_Rigel.

Note: Please uninstall previous versions of the Tracking Software to ensure there are no conflicts.

For support and information on known issues head over to Technical Support.

Upgrade from previous versions of Ultraleap Hand Tracking Software with our Migration Guide.

Something on your mind? We love to learn more about our developers and what they want. Share your honest feedback and help us make hand tracking work better for you.


 

Ultraleap Gemini V5.2 Release Notes

Tracking Engine updates

HMD mode

  • Improved side to side finger fidelity

  • Two hand performance noticeably improved

  • Arm accuracy noticeably improved

  • Improved stability during initialization and termination

  • Improved hand rotation sensitivity especially for fists

  • Performance for small and large hands noticeably improved

  • Improved smoothness 

  • Maximum tracking velocity decreased for certain palm orientations

  • Some decrease in depth calibration accuracy on Stereo IR 170

  • Some decrease in stability when pinching through rotations


Desktop mode

  • Significantly more robust and accurate hand tracking

  • Two hand performance noticeably improved

  • Improved hand tracking initialization - especially for fists

  • Arm accuracy and stability improved

  • Improved high angle tracking

  • Improved distance tracking

  • Improved performance for small and large hands

  • Improved hand rotation performance

  • Improved smoothness

  • Decreased pinky fidelity

  • Decreased single finger isolated performance

  • Some decrease in depth calibration accuracy on Stereo IR 170


removed features

  • Launch on Startup: This option has been removed. The Control Panel-Tray Icon will automatically be enabled to launch at Windows startup. To disable this, go to Task Manager > Start-up > Ultraleap Tracking Control Panel and right-click to disable.

  • Automatic power saving: This feature has been removed as it is more relevant to mobile applications.

  • Robust mode: This feature has been removed.

  • Low Resource mode: This feature has been removed.

  • Avoid Poor Performance: This feature has been removed.

  • Recalibration for LMC: This feature has moved to our Customer Support page.

  • AppHome: This has been removed from the installer. The Leap Motion App Store is obsolete.

  • LeapJS and WebSocket server: The WebSocket server is not supported in this version.

  • Auto-orient camera feed: Auto-orientation of the camera feed for tracking has been removed.

 

API and SDK specific updates

  • LeapC API remains backwards compatible with past 4.x.x releases and the 5.0.0-preview/5.0.1-preview release. However, the client-server protocol has been replaced since 5.2. Client applications will need updating to the new 5.2 LeapC.dll when using the 5.2 tracking service. Client applications built with past 4.x.x SDKs and the 5.0.0-preview/5.0.1-preview SDKs will not communicate with 5.2 service or vice versa.

  • The tracking service now supports a new tracking mode – Above Facing User.

    • LeapC API allows setting the tracking mode via LeapSetTrackingMode() and the corresponding enum eLeapTrackingMode. Available tracking mode enumerations are eLeapTrackingMode_Desktop, eLeapTrackingMode_HMD and eLeapTrackingMode_ScreenTop, for the operation of up-facing, head-mounted, and down-facing devices.

    • Setting of tracking mode is confirmed by a new asynchronous event type LEAP_TRACKING_MODE_EVENT. Note that changing the tracking mode also results in LEAP_POLICY_EVENT prior to the corresponding LEAP_TRACKING_MODE_EVENT emitted via LeapPollConnection().

    • The tracking mode related policy flags eLeapPolicyFlag_OptimizeHMD and eLeapPolicyFlag_OptimizeScreenTop can be used to switch the tracking mode but are marked deprecated. The new LeapSetTrackingMode() function is strongly recommended over using policy flags.

  • The number of supported eLeapDeviceStatus enumeration values have been reduced. Device events will only contain the values: eLeapDeviceStatus_Streaming, eLeapDeviceStatus_Paused and eLeapDeviceStatus_UnknownFailure. Support for eLeapDeviceStatus_Smudged, eLeapDeviceStatus_Robust and eLeapDeviceStatus_LowResource may be reintroduced in future releases.

  • The service configuration file format has been changed and now read from %ProgramData%/Ultraleap/HandTracker/config.json. Previous config locations were %USERPROFILE%/AppData/Roaming/Leap Motion/config.json and %ProgramData%/Leap Motion/config.json.

  • The LeapSaveConfigValue() and LeapRequestConfigValue() functions are currently provided as no-op implementations and included for compile time backwards compatibility. We expect these functions to be reintroduced in a future releases. Similarly the LeapPollConnection() events LEAP_CONFIG_RESPONSE_EVENT and LEAP_CONFIG_CHANGE_EVENT will not be generated.

  • The LeapInterpolateHeadPose(), LeapGetPointMappingSize() and LeapGetPointMapping() functions have been replaced with no-op implementations and only included for compile time backwards compatibility. We expect to remove these functions in future versions of the software. Similarly the LeapPollConnection() events LEAP_HEAD_POSE_EVENT and LEAP_POINT_MAPPING_CHANGE_EVENT will no longer be generated.

  • The LeapPollConnection() events LEAP_LOG_EVENT and LEAP_LOG_EVENTS will no longer be generated. Logging is handled by the service writing directly to log files.

  • Some experimental Ex functions have been added to support specifying camera devices, such as LeapPixelToRectilinearEx() . These are currently for internal use.