Unity Modules
Leap Motion's Unity SDK
Getting Started

UnityModules packages from our developer website support Unity 5.6.2, 2017.1-4, and 2018.1.

The UnityModules repository, however, expects Unity 2017.3 and up. If you are sourcing UnityModules directly from this repository, your mileage may vary with earlier versions of Unity.

Installing the modules

Core is the only dependency for any Module. If you are installing any Unity Modules for a new project, you need only to download the latest stable versions of Core and any modules of interest from our developer page. You can import new modules into your project at any time; to upgrade a module, simply delete its folder from your project to get rid of all of the files in that module, then import the latest module version.

This documentation is updated on a rolling basis, generally to match module releases. It is likely out-of-sync with the develop branch in the UnityModules repository.

For more details on upgrading modules, or if your project already contains older versions of our modules, check out our reference for Upgrading Unity Modules (it's easy).

Which modules are right for you?

  • Core is the dependency for all other modules. Leap Motion's Core Assets provide the foundation for VR applications with a minimal interface between Unity and the Leap Motion Controller and a collection of garbageless C# utilities. With Core, you can render a basic set of Leap hands, attach objects to hand joints, and find generally-useful utilities like a non-allocating LINQ implementation and a Tween library.
  • The Interaction Engine provides physics representations of hands and VR controllers fine-tuned with interaction heuristics to provide a fully-featured interaction API: grasping, throwing, stable 'soft' collision feedback, and proximity. It also comes with with a suite of examples and prefabs to power reliable, stable 3D user interfaces as well as any physics-critical experiences akin to Leap Motion's Blocks demo.
  • With the Graphic Renderer, you can render an entire curved, 3D, dynamic interface in 1-3 draw calls. The Graphic Renderer can be used in tandem with the Interaction Engine; see Graphic Renderer + Interaction Engine for details and a link to an example project.
  • The Hands Module provides the tools you need to rig your 3D hand assets to work with Leap hands, including the powerful hands-auto-rigging-tool.


If you're not seeing hands in your Unity application, check the following first:

  • If you aren't using a custom camera rig, make sure you have the Leap Rig (XR rig) prefab or the LeapHandController (desktop-mounted controller) prefab in your scene.
  • If you're using a custom camera or controller rig, check your application's scene hierarchy while your hand is in front of the sensor. Make sure the hand isn't simply being rendered in the wrong place relative to your camera. Additionally, double-check you have your rig is set up correct: Leap Motion XR rigs.
  • Check the Leap Motion icon in your task bar, which you'll have if you've installed the service from the developer SDK for your platform. If it's dark, the Leap service isn't sending any data. Double-check your Leap Motion hardware is plugged in, and check that the Leap Motion service is running.
  • Open the Leap Motion Visualizer from the right-click menu of the Leap Motion icon in your task bar. If you see hands in the Visualizer, the problem is mostly likely somewhere in Unity; otherwise, the problem is outside Unity.