# Enable Leap motion and 3D slicer to work together

**URL:** <https://discourse.slicer.org/t/enable-leap-motion-and-3d-slicer-to-work-together/6794>\
**Category:** Support\
**Created:** [May 15, 2019, 3:05am UTC](https://discourse.slicer.org/t/enable-leap-motion-and-3d-slicer-to-work-together/6794 "2019-05-15T03:05:02Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jcfr](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jcfr/32/17825_2.png) [@jcfr](https://discourse.slicer.org/u/jcfr)\
**Post date:** [May 15, 2019, 3:21am UTC](https://discourse.slicer.org/t/enable-leap-motion-and-3d-slicer-to-work-together/6794/2 "2019-05-15T03:21:37Z")

</div>

We recently discussed what is missing to add support for Leap motion. In a nutshell, the bindings available with the v3.2 of Leap motion SDK would need to be re-generated and compiled for python 3.

This is discussed at length in this post: [SlicerLeapMotionControl in Slicer 4.11.0](https://discourse.slicer.org/t/slicerleapmotioncontrol-in-slicer-4-11-0/6770/10)

We welcome contributions and if you would like to help out, we are happy to provide guidance. To move forward, consider adding comments and questions in the post referenced above.

---

_[View the full topic](https://discourse.slicer.org/t/enable-leap-motion-and-3d-slicer-to-work-together/6794)._