Hey everybody,
We have a new update to our core software, v2.3.1, which can be found at www.leapmotion.com/setup for consumers and http://developer.leapmotion.com for developers!
In this bug-fix release we fixed a crash when going into HMD after disconnecting and reconnecting the Leap Motion Controller. We also addressed a latency bug which gradually grew over time.
I also wanted to remind people that on August 15, 2015 our new privacy policy went into effect. Non-identifiable 32-pixel-square infrared hand image data will report back to the server from beta software or tracking modes and will be used to improve overall tracking quality in future releases. No device ID or other unique identifiers are collected or stored with the image data. It may be turned off by unchecking “Send Usage Data” in the Leap Motion Control Panel.
What's New
- Resolved issue that caused tracking latency within apps to increase over time
- Fix for service crash after disconnecting/reconnecting in HMD mode
- Fix for errant disk full message in App Home on Windows
Known Issues (General)
- We support the image hand in robust mode, but it is not recommended to use full-on image passthrough in bright lighting / robust mode
- Pausing/Resuming Tracking can cause the FPS to drop. The workaround is to Disconnect/Reconnect the device to bring the FPS back to normal.
- Bone direction vector points in the wrong direction. It should point toward the distal end of the bone.
- Images cannot be extracted from serialized frames
- Device.isFlipped is always false
- Avast! Antivirus can interfere with Leap Motion Service installation (disable shields to work around)
- Secure WebSocket (TLS) on Linux Chrome requires running with --ignore-certificate-errors (caution: this also affects non-WebSocket services)
- Chrome on Windows 7 sometimes fails to respond to emulated touch points – to fix this, click inside the program with a mouse
- The sphereRadius and sphereCenter functions of the Hand class are unstable when the hand is fully open
- Tracking quality is lower when making a fist or with only one finger extended
- Tracking may not work as well with bracelets, rings, watches, sleeves, etc
- Linux does not support background apps or onFocus callbacks
Known Issues (VR Beta)
- The latest version of the Oculus firmware limits bandwidth for the DK2’s built-in USB port, which harms the controller’s performance. For now, we recommend using the free cable extender bundled with the mount to connect the controller directly to the computer.
- Tracking performance may degrade when closely facing large reflective surfaces like white walls or infrared-reflective curtains. (This is a broader issue with V2 tracking that we’re constantly improving on.)
- Tracking degrades when arms are held directly away from the body (i.e. elbows straight).
- Some poses are not currently tracked reliably in head-mounted display (HMD) mode (e.g. pinch/rotate, 3- and 4-finger poses).
- Minimized or out-of-focus applications using the HMD policy flag can affect the service state. Close such programs before switching back to non-VR apps.
As always, we greatly appreciate your feedback on the build, especially as we continue to enhance the developer experience.
Have fun developing!
Matt