• As of 4.0.0 our Windows service is now 64bit only along with the other applications we include in the installer
  • Legacy applications that support Gestures, Motions, Tools, Pointables and Tip Velocity are no longer supported on Orion
  • Leap Motion Service uses more CPU resources to provide a better tracking experience
  • USB 3.0 support for Rigel is in an experimental state and may have degraded frame rate depending on the USB bandwidth.
  • Apps that use the new Image API policy can not stream at the same time as app that use the old API
  • 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
  • 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.
  • 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
  • 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)
  • Tracking performance may degrade when closely facing large reflective surfaces like white walls or infrared-reflective curtains.