Skip to content

Ultraleap Unity Plugin 6.12.0

Compare
Choose a tag to compare
@MattGrayUL MattGrayUL released this 13 Sep 11:32
· 1179 commits to develop since this release

openupm-tracking openupm-tracking-preview

  • This release was tested against Unity 2021LTS and 2022LTS
  • Tracking contains stable content including Core, Hands and the Interaction Engine.
  • Tracking Preview contains experimental/pre-release content.

Headline features include:

Added

  • (MRTK Support) Added an MRTK3 subsystem for using Leap tracking directly (non-OpenXR)

Changed

  • (XRHands) XRHands subsystem will now use existing LeapXRServiceProviders found in the scene before considering generating new ones

Fixed

  • (XRHands) XRHands double-translates tracking data causing XRI InputActions to be wrongly positioned when the XROrigin is moved

Known issues

  • Use of the LeapCSharp Config class is unavailable with v5.X tracking service
  • Repeatedly opening scenes can cause memory use increase
  • Currently the Ultraleap Hand Tracking feature for OpenXR requires the New and Legacy input systems to be enabled, to simultaneously use OpenXR and the Ultraleap Unity Plugin's features.
  • The OpenXR Leap Provider does not currently support the Confidence hand property (and will return fixed values)
  • After using Ultraleap OpenXR in Unity Editor, the tracking mode of device 0 will be set to HMD until the Unity Editor session ends. This can stop the testing of non-XR scenes until the Unity Editor is re-opened
  • The OpenXR Leap Provider palm can be in unexpected position when using pre-1.4.3 OpenXR Layer. A workaround is to ensure you use 1.4.3 or newer - installed by the 5.12.0 or newer Tracking Service Installer
  • Running both the Ultraleap XRHands Subsystem and another XRHands Subsystem at the same time causes unstable results. Only enable one at a time.

Full Changelog (Tracking Package)

Documentation

Discussions

Discord

Community Support

Thanks to our contributors:

@MaxPalmer-UH
@rblenkinsopp
@MattGrayUL
@Dwarph
@rorygames
@MattFiler
@BryceNewell-UL

Note

If using the .UnityPackage method to import the Plugin, it is recommended to delete any previous version before importing to avoid import issues.