It's been a while since our last update but we have some tracking improvements, official LeapC documentation within the SDK package, as well as some under-the-hood changes that will lay the groundwork for new and exciting changes! The SDK can be found at our developer page and if you just want the installer it can be found here.
- Improved initialization speed
- Improved stability of tracking some poses
- Better tracking and initialization in desktop mode
- Updated Unity Visualizer to fix a latency issue
- Official LeapC documentation in the SDK package
- Various changes to LeapC including:
- Added LeapPixelToRectilinear()
- Added LeapRectilinearToPixel()
- Added invalid and unknown device types
- Renamed eLeapDeviceType to eLeapPID
- Added record to file and playback from file
- Added 3x3 Matrix struct
- Added quaternion to LEAP_PALM to represent orientation
- Added LeapInterpolateFrameFromTime() function
- Our software auto-updating feature will not work when updating from any release prior to 3.2.0. This will work again when going from 3.2.0 to any future updates. You will need to manually update via our developer portal.
- Some legacy applications are no longer supported on Orion. These apps are Digit Duel, NY Times, Google Earth, Out of the Blocks, PWN9, and TVO Kids Caterpillar Count. These apps will still be available for V2 users.
- Although much improved, some poses are not currently tracked as well as V2; this can be seen in the form of occasional bad initialization/reinitialization, right/left misinterpretation, and some wrong poses
- The skeleton hand can shift slightly away from the hand as you move left or right; most noticeable in apps that use Image Hands and also display the skeletal hands
- Tracking may not work as well with bracelets, watches, sleeves, etc
- Although very much improved, occluded hands can still get killed at times
- Devices embedded in HP laptops and keyboards are not supported on Orion
- Hand confidence is currently always 1.0 and does not fluctuate; a new solution is on the horizon
- Tools are not currently supported in Orion
- Automatic controller orientation can in rare cases stop functioning. A Leap Motion service restart will fix this or you can manually orient the controller from the Leap Motion Control Panel.
- Tracking along the x-axis may appear slightly skewed
- Desktop mode initialization is not as reliable as HMD mode initialization
- Pausing/Resuming Tracking can cause the FPS to drop. The workaround is to disconnect and then reconnect the device to bring the FPS back to normal
- Avast! Antivirus can interfere with Leap Motion Service installation (disable shields to work around)
- 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.
- 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 and the ongoing Orion Developer Beta.