New
v1.4.0
Change Log
- Updated: Support for Unity 5.2.
- Updated: Support for Leap Motion Core Assets 3.0.0.
- Updated: Support for Oculus 0.7.0 (built into Unity 5.2).
- Updated: Code and demo scenes to support the latest Unity, Leap, and Oculus versions.
- Removed: Leap Motion and Oculus Unity assets from repository.
Migration Notes
- Breaking Change: This version of Hover VR requires Unity 5.2+ and Leap Motion 2.3.1+.
- Breaking Change: To run the demo scenes, you must first install the Leap Motion Unity Core Assets 3.0.0 into the Unity assets folder. See instructions.
- Upgrading to Unity 5.2 simplifies VR setup. Place a standard camera into the scene, then enable the VR option in Unity's Player settings. You can place the Leap
HandControllerand Hover VR elements as a child of that camera, just like you would do with the previousCenterEyeAnchor. - To run the non-VR demo scenes, you'll need to disable the VR option in Unity's Player settings.
- Known Issue: An error appears upon importing Hover VR into Unity 5.2. The error does not seem to cause any issues with the import process or other functionality. See https://github.com/aestheticinteractive/Hover-VR-Interface-Kit/issues/33 for details.