Hi everyone,
I’m pleased to announce a new V2 tracking software update which is available to consumers at www.leapmotion.com/setup, as well as for developers at http://developer.leapmotion.com! This release was focused around fixing some important SDK issues as well as various optimizations.
What's New
-
Users must update their Leap Motion service to version 2.2.0+ to run applications built with the 2.2.0 SDK (not applicable to JavaScript apps)
- If necessary, users are prompted to update when launching a v2.2.0 app
- Optimized the amount of CPU used in apps that use image-passthrough
- Fix for Leap service not working on some installs (Error 1053)
- Fix for a rare hang when exiting an app and switching between apps
- Fixed defunct processes on Linux
- In the Mac SDK, the version of libLeap.dylib found in the SDK lib folder is compiled against libc++ rather than against libstdc++ by default
Known Issues (VR Beta)
- Applications using the Image API must link with updated DLLs from SDK 2.1.2 or higher.
- Applications using the Image API should update to 2.2.0 to improve performance
- 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.
Known Issues (General)
- Secure Websocket on Firefox requires Firefox version 32 or higher
- In order for Secure Websocket to work on Firefox, please close Firefox prior to installing 2.2.0 or close and relaunch it after installing to pick up the changes
- In some situations when it appears the Leap Service is not running, it is stuck in a loop consuming a full core's CPU. When this happens, simply restart the service
- Applications built with SDK 2.1.0 or 2.1.1 must update DLLs to 2.2.0
- 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
- JavaScript client library and WebSocket protocol do not support setting gesture parameters
- 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.
- A tap gesture may register when a small circle gesture is made
- Linux does not support background apps or onFocus callbacks
As always, we greatly appreciate your feedback on the build, especially as we continue to enhance head-mounted tracking.
Cheers!
Matt