LEAP MOTION V2 SOFTWARE
Software log file (tracker_log.txt) no longer grows indefinitely.
LEAP MOTION V2 UPDATE
Tracking service no longer crashes/stops after a firmware update to the Leap Motion Controller. LeapPollConnection() now respects the timeout parameter value prior to a connection to the service where the timeout is always at 2 seconds (OS timeout on Windows).
LEAP MOTION V2 CODE
Missing VC redistributable dlls no longer causes the following installation error “The code execution cannot proceed because VCRUNTIME140_1.dll cannot be found”. The Stereo IR 170 will now return an identification of eLeapDevicePID_SIR170 in the LEAP_DEVICE_INFO structure, rather than eLeapDevicePID_Rigel.
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ĪPI update: The PID identification for the Stereo IR 170 Hand Tracking Camera has been updated. Pressing “V” to cycle through the tracking modes will still make changes to the tracking mode used by the tracking service. It will first display the tracking mode that has already been set by another application (e.g. Tracking Visualizer does not default to Desktop mode when launched: Launching the Tracking Visualizer does not automatically set the tracking mode to Desktop. Please also refer to our Migration Guide Ultraleap Gemini V5.3 Release Notes The service should no longer crash/stop when disconnecting a Leap Motion Controller or Stereo IR 170. The Pause tracking feature will now work regardless of whether or not a client application is connected. LeapPollConnection will now work as expected when passing in a long timeout. There is no longer a memory leak in Tracking Visualizer application when tracking is paused. Tracking Visualizer render fps value will now match monitor refresh rate even when window is minimised and frame rate of the VR headset when in VR. There is no longer a small offset with skeleton hand overlay in Tracking Visualizer when using SIR170 in non-VR mode. There are no longer compatibility issues when using the Tracking Visualizer in VR mode with the Oculus Quest 2 or Valve Index and Ultraleap cameras. You can choose to stop sharing this anonymized data with us at any time by unchecking the "Help Improve Tracking" box in the Control Panel. Anonymized app and usage data will be sent to Ultraleap to improve future releases. We have improved the ‘look and feel’ of the Tracking Visualizer and included some new customizable features: We’ve added a new UI to the Visualizer so that a user is able to easily control how hands are being displayed and tracked, which makes it easier for a user to troubleshoot why tracking isn’t performing as expected.įor VR users, the Visualizer can now be configured to be viewed either on their standard displays or directly in their headset.ĭata analytics: We’ve integrated diagnostic data analytics. Please also refer to our Migration Guide Ultraleap Gemini V5.4 Release Notes The skeleton hands overlay is no longer misaligned in the Tracking Visualizer when swapping between camera devices. Note: Please uninstall previous versions of the Tracking Software to ensure there are no conflicts.
For example, if a user selects HMD (head-mounted) tracking mode and disconnects that device, when the device is reconnected, HMD mode will remain as the selected tracking mode for any client connected to the service. Tracking Mode persists on device and service reconnection: The selected tracking mode will now persist on device and service reconnection on a per-device basis, instead of resetting to the default tracking mode. Tracking Visualizer improvements: We’ve added help text popups to various menu options to help users understand what they are for. This increases the reliability of our TouchFree solutions.
Hand tracking improvements in Screentop tracking mode: We’ve made tracking improvements to pointing pose detection at longer distances. Please also refer to our Migration Guide Ultraleap Gemini V5.5 Release Notes
0 kommentar(er)
