Version: 20 Mar 2024

1.5.0 Version 1.0 - Unity MRTK Magic Leap Release Notes

SDK Delivered via The Magic Leap Hub

This Package Supports Magic Leap Unity SDK Version 1.3.0 as well.

Initial Update to 1.5.0

Voice Intents - Refer to SpeechCommandsDemoMagicLeap scene for usage.
Control - Refer to ControlMagicLeapDemo scene for usage.
HandTracking - Refer to HandInterationExamplesMagicleap for usage. Only Partially implemented on platform currently.
EyeTracking - Refer to EyeTrackingDemoMagicLeap for usage.
Meshing - Refer to MeshingDemoMagicLeap for usage.
AllInteractions - Refer to InteractionsDemoMagicLeap for Handtracking, Control, EyeTracking, and Voice usage together.

Updated to MagicLeap SDK 1.2.0-dev2 and MagicLeap Unity SDK 1.5.0.
In the Speech Commands Magic leap Profile added support for Voice Intent Slots.
Fixed issue when both handtracking and controller are tracked at once and added an option to disable handtracking for the hand holding the controller.
Begin updating UI look and feel to better match Magic Leap aesthetic.

Handtracking Performance issues when interacting with other objects. Continuous Improvements made each Sprint.
To use the simulator when running MRTK, you must set the Script Changes While Playing setting to Stop Playing and Recompile or Recompile and Continue Playing in the Unity Preferences.
The logs may show a single false Permission Denied error when running meshing.
Occationally the controller may not connect properly when launching a new application. Pauseing and resuming the application resolves this.

Instead of copying a configuration file, clone the DefaultMixedReality version and make adjustments. We have found copying an MRTK configuration file can cause issues such as Input Data Providers not loading or visualizers not attaching properly.
Controller Visualizer sometimes stops positioning and the logs say: Left_ControllerModel(Clone) is missing a IMixedRealityControllerVisualizer component! This happens sporatically, we have found adding the MixedRealityControllerVisualizer component to the model itself resolves this.
If your application builds and results in a blank/empty scene, you must adjust your projects quality settings. (Known issue in editors 2021.1 and older. To resolve this, remove all but one of the quality presets in your projects quality settings (Edit>Player Settings>Quality).
Users may need to add the tracked pose driver to the camera themselves.