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 a couple critical issues as well as fixing some issues with App Home.
Please Note: I want to call out a breaking change for C# and Python developers who downloaded SDK 2.2.1 and started using Controller.Images, which was introduced in 2.2.1. We decided to change the method into a property, so anyone using it will need to reference the property correctly.
What's New
- Added serialNumber to the Device and LeapDevice classes.
- In C# (and Unity), changed Controller.Images from a method to a property.
- In Python, changed Controller.images from a method to a property.
- Linux SDK samples now compile without error
- Fixed an issue where the LEDs would stay on when Pausing Tracking
- Fixed issue in which tool tracking stopped working after a computer resumed from sleep.
- Fixed an issue in which App Home Terms of Service window did not close without ending the process
- Fixed various issues with the App Home tutorial
Known Issues (General)
- C# and Python applications built with SDK 2.2.1 that use the Controller.Images() Method must change it to use the Controller.Images Property
- Pausing/Resuming Tracking can cause the FPS to drop. The workaround is to Disconnect/Reconnect the device to bring the FPS back to normal.
- Secure Websocket on Firefox requires Firefox version 32 or higher
- The Close Firefox dialog window sometimes does not come to the foreground after installation (while Firefox was running)
- In order for Secure Websocket to work immediately on Firefox, please close Firefox prior to installing 2.2.0 or close when prompted
- In some situations it may appear that the Leap Service is not running. 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
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.
As always, we greatly appreciate your feedback on the build, especially as we continue to enhance the developer experience. In the coming weeks we intend to focus on improving our tracking immensely.
Cheers!
Matt