Unity® MRTK Package 2.0.0-pre.2
- Magic Leap Unity SDK Version 2.4.0
- Unity® Version: 2022.2 (custom)
- MRTK Foundations v2.8
- MRTK Examples v2.8
Release Focus
- Initial Update to 2.5.0 and EyeTracking Update
Release Features
- 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.
2.0.0-pre.2 Version 1.0 Updates
MagicLeapEyeGazeDataProvider has been updated to use the base OpenXR Eye Gaze Interaction Profile instead of Magic Leap 2 Eye Tracker. OpenXR Settings may need to be adjusted.
2.0.0-pre.1 Version 1.0 Updates
- Added OpenXR Provider Support.
- Added dropdown for OpenXR Origin Modes in the Camera Settings Profile. Only valid with OpenXR Provider.
Known Issues
- OpenXR Performance issues with MRTK shaders at startup causing delays resulting in a few seconds of no content. This is noticeable with multiple Data providers or especially scenes with Eye Tracking. Temporarily the Interactions Example uses HeadTracking as a fallback instead of EyeTracking and the simple scenes use the URP Unlit Shader while this problem is looked into.
- 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 Conintue Playing in the Unity Preferences.
- The Slot Example in the Speech Commands Sample scene will trigger the change color MRTK popup.
- Occationally the controller may not connect properly when launching a new application. Pauseing and resuming the application resolves this.
Important Notes
- 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 sporadically, 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 project's 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.