ποΈ Overview
The transition to OpenXR involves the phasing out of MLSDK in favor of OpenXR extensions. To align with this change, Magic Leapβs Unity SDK is shifting from Unity's platform specific XR Plugin (ie: com.unity.xr.magicleap) to Unity's OpenXR Plugin (com.unity.xr.openxr). This shift is accompanied by the addition of new OpenXR Features and API for accessing the functions previously defined by MLSDK C-APIs. This document will outline the rationale behind the move to OpenXR, detail the steps involved in the migration process, and provide insights into the changes and enhancements introduced by this transition.
ποΈ Example Project
Magic Leap Unity (OpenXR) Examples
ποΈ Getting Started
8 items
ποΈ Controller
3 items
ποΈ Eye Gaze
3 items
ποΈ Hand Tracking
4 items
ποΈ Head Tracking
2 items
ποΈ Localization Map
2 items
ποΈ Marker Understanding
2 items
ποΈ Meshing Subsystem
2 items
ποΈ MRTK OpenXR Compatibility
Use the following chart to see if your project is compatible with MRTK 2.8 or MRTK 3.0.
ποΈ Near Clip Policy
In order for virtual content to be rendered comfortably, Magic Leap 2 enforces a minimum clipping plane. By default this value is .37 meters or 37 centimeters but can be adjusted by the user inside the device settings (Settings > Display > Advanced > Display Zone) based on their comfort preferences, up to a minimum of 25 centimeters. Applications can choose if they want to use the near clipping plane distance set by the user or if it should remain at the default minimum value. If the Camera's Near Clip Plane value is set to lower than the enforced range it will be reverted to the enforced value.
ποΈ Permissions
4 items
ποΈ Plane Detection
3 items
ποΈ Platform Detection
This section includes details on detecting if an application is running on a Magic Leap 2 and if a developer is targeting Magic Leap in Unity's XR Manager.
ποΈ Reference Space
1 items
ποΈ Rendering Extensions
3 items
ποΈ Spatial Anchors
2 items
ποΈ User Calibration
This document demonstrates how to use the User Calibration OpenXR Feature to determine if the user has calibrated the device to fit and track their eyes properly. This feature can be used in conjunction with Android Intents to:
ποΈ MLSDK Features
Overview