What's new in Leap Motion 2.3.1 Build 31549
Jan 14, 2016
- Fix for service crash after disconnecting/reconnecting in HMD mode
- Fix for gradual climb in latency in apps
- Fix for errant disk full message in App Home
New in Leap Motion 2.3.0 (Jan 14, 2016)
- Fix tracking hang in apps that use Image API
- Tracking is more accurate while in Robust Mode
- Slight decrease to current CPU usage
- Fix for HP firmware updates not triggering
- Brand new VR out of box experience
- Added Controller.now() to the Objective-C API
- Added a feature to avoid poor performance when tracking quality is degraded
- Privacy policy update and control panel opt out: starting August 15, 2015 when our new privacy policy goes 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. May be turned off by unchecking “Send Usage Data” in the Leap Motion Control Panel
New in Leap Motion 2.2.7 (Jan 14, 2016)
- Images are now on by default
- Fixed gesture parameters in C#/Unity
- Fix for Software log and issue report windows preventing shut down on Mac
- Fix for App Home crash on Mac when disk full message appears
- Automatic power saving now appears in the software log when triggered
- Added App Store button when searching App Home for apps not present
New in Leap Motion 2.2.6 Build 29154 (Jun 23, 2015)
- Added an image.data_pointer hook for faster image API access in Python
- Fix for device.serial_number in Python
- Finger.Type is now a property in C#
- C++: Leap::FingerList and other list types now work with std::find_if()
- Support for Unity 5 Editor (32-bit)
- Fixed crash on libxs library
- Added Device.baseline to report the distance between the Leap Motion cameras. (In current devices, this is always 40mm)
- Invalid Arm objects now have an identity matrix as their basis rather than a zero matrix
- Improved error log reporting
- Improvements to Image while in Robust mode
- Fix for window focus issue on Mac
- Fix for window color scheme issue on Mac
- New Sign-Up button in App Home
- Apps that have not been installed are clearly marked
- Fix for App Home download failures
- App Home fix for crash on app install if the hard drive was full
- Added hard drive space check prior to downloading a new app in App Home
New in Leap Motion 2.2.6 Build 29153 Pre (May 23, 2015)
- We have made the newest release available on Installer Preview. You can get the builds here: https://developer.leapmotion.com/downloads/installer-preview2
- This update was focused on providing a better UX experience within App Home as well as addressing some much needed developer fixes.
- Here is a snippet of the changes going into this release:
- Support for Unity 5 Editor (32-bit)
- Adding an image.data_pointer hook for faster image API access in Python
- Fix for device.serial_number in Python
- Finger.Type is now a property in C#
- C++: Leap::FingerList and other list types now work with std::find_if()
- Fixed crash on libxs library
- Improved error log reporting
- Improvements to Image while in Robust mode
- New Sign-Up button in App Home
- Apps that have not been installed are clearly marked in App Home
- Fix for App Home download failures
- Since this is an early preview of the software it will not be supported through our regular support channels. If you experience any issues or have any feedback about this version of the software please make sure to report them here.
New in Leap Motion 2.2.4 Build 26750 (Mar 25, 2015)
- What's New:
- Added support for Unity 5 - Note: If you are using one of our Unity asset packages, new versions of these packages that support Unity 5 will be released separately.
- Improved latency of the Image Api in C# by 2ms
- Lowered CPU use when processing frames
- Now code signing the .NET DLLs
- Added an option on Mac to specify if the Leap Motion Control Panel launches on startup
- 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.
New in Leap Motion 2.2.3 Build 25971 (Mar 12, 2015)
- WHAT'S NEW:
- Better hand initialization and reinitialization for HMD and up-facing tracking modes
- Fixed an issue where tracking did not resume after sleep on Ubuntu14.04 or higher
- Fixed an issue where Tools appeared as hands
- Removed Leapd.dll on Windows (use Leap.dll for Debug)
- Libstdc++ libLeap.dylib removed on Mac
- Added HMD and up-facing visualizer view modes
- Various installation fixes
- 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 co