Skip to main content
Version: 21 Aug 2024

Configure Project Settings

This section provides detailed steps on how to manually configure your Unity Project so that you can build and deploy OpenXR applications for Magic Leap 2.

Prerequisites​

This section provides detailed steps on how to manually configure your Unity Project so that you can build and deploy applications for Magic Leap 2.

Quickstart​

The fastest recommended way to set up your project for Magic Leap 2 development is to use the latest version of the Magic Leap Setup Tool.

  1. Download the Magic Leap Setup Tool from the Unity Asset Store
  2. After adding it to your asset library, click the Open in Unity button to show the tool inside Unity's Package Manager.
  3. Select Download then Import to import the tool into your project.
Unity's Package Manager window with the Import option highlighted
  1. Keep all of the package contents selected in the Import Unity Package window and select Import.
Import Assets window with the Import option highlighted
  1. After the package is imported, you should see the Magic Leap Project Setup Tool popup window. If you do not see it, go to Magic Leap > Project Setup Tool in the Unity menu.
Magic Leap Project Setup Tool window
  1. The project setup tool will walk you through all of the steps necessary to complete setup. Start by setting the Magic Leap SDK by selecting Locate SDK. Then select the folder containing the latest version of the Magic Leap Unity SDK.
  2. After setting the SDK folder, you can select the Apply All button on the bottom of the window to quickly change all of the required settings.
  3. After accepting all prompts and restarting the editor, your project will now be ready for Magic Leap 2 development.

Manual Setup​

Import Magic Leap Unity SDK​

The Magic Leap SDK provides access to Magic Leap's perception and input API. The Magic Leap Unity SDK can be installed using the Unity Package Manager by importing the SDK from your computer or a scoped registry.

  1. Open the Package Manager window ( Window > Package Manager).

  2. Select the "+" (plus) button in the top-left corner, then Add package from tarball.

Unity Editor Package From tarball
  1. Navigate to the location of the following folders and select the .tgz file within to add the package from com.magicleap.unitysdk.tgz (downloaded via ML Hub). For example:
  • Mac : $HOME/MagicLeap/tools/unity/<Version>/com.magicleap.unitysdk.tgz
  • Windows : %USERPROFILE%/MagicLeap/tools/unity/<Version>/com.magicleap.unitysdk.tgz
Unity tarball file in a folder
You may see the following pop-ups appear:

  • "This project is using the new input system package, but the native platform backends for the new input system are not enabled in the player settings. This means that no input from native devices will come through. Do you want to enable the backends? Doing so will RESTART the editor and will DISABLE the old UnityEngine.Input APIs."

    • Select Yes

  • "This project may contain an obsolete method to validate interactions between XR Interactors and Interactables. This Update is only required for older projects updating the XR Interaction Toolkit package. If this package was newly installed, please cancel this operation. If you choose 'Go Ahead', Unity will update all Interactors and Interactables in Prefabs and scenes to use the new Interaction Layer instead of the Unity physics Layer. You can always manually run the XR InteractionLayerMask Updater fro... (For the full error message, see the editor log file located at ...)"

    • Click I Made a Backup, Go Ahead!

Verify OpenXR Unity Package Version​

  1. Open the Package Manager (Window > Package Manager).
  2. Verify that your project contains OpenXR Plugin version 1.10.0 or greater.
  3. If the package is not present or an older version is installed. Select the OpenXR Plugin Package and click install.
Unity OpenXR Plugin in the Package Manager

XR Plug-in Management​

The Magic Leap OpenXR Feature Group needs to be enabled before when deploying to a Magic Leap 2 device. To do this:

  1. Go to Edit > Project Settings > XR Plug-in Management select the Android tab
  2. Enable the OpenXR provider enable Magic Leap feature group , this will add support for Magic Leap 2.
OpenXR enabled under the Android tab in XR Plug-in Management
note

If converting an existing project which uses the Magic Leap XR provider, it is highly recommended that you disable the Magic Leap provider to avoid unpredictable behavior.*

Enable Magic Leap OpenXR Features​

Once you have the Magic Leap 2 Unity SDK package installed, you will have access to a collection of OpenXR Features corresponding to supported vendor extensions, as well as the Magic Leap 2 Controller interaction profile.

  1. Under Edit > Project Settings > XR Plug-in Management, select OpenXR in the left sidebar.
XR Plug-in Management OpenXR Magic Leap support features list

This window allows you to enable corresponding supported OpenXR Features and Interaction Profiles. Alternately, you can also toggle the Magic Leap Feature Group on the OpenXR Tab or on the XR Plug-in Management tab to switch on all Magic Leap 2 Features

Features which have additional settings that can be configured by selecting the ⚙(gear) icon to the right of the feature. Clicking this icon will open an additional window where the Feature’s options can be changed.

note

The Magic Leap 2 Support Feature MUST be enabled if your project contains the Magic Leap XR Plugin package. This is due to a graphics bug. At some time in the future, the Unity SDK will not install the ML XR Plugin as a dependency, but for now this is still the case.

Player Settings​

Under the Edit > Project Settings > Player section, make sure the Android tab is selected, then configure the following settings:

  1. At the top, set the following identifiers:
    1. Company Name - the name of your company.
    2. Product Name - the name of your app or product as you want it to appear on the in-device menu.
  2. Navigate to the Other Settings section
    1. Set the Color Space property to Linear. This enables more realistic rendering. For more information, read Unity’s gamma and linear color space workflow guide.
    2. Disable Auto Graphics API and make sure the only Graphics API listed is Vulkan.
    3. (Recommended) Enable Multithreaded Rendering.
    4. Set the Texture Compression Format to either DXT + RGTC(BC4, BC5)(Recommended) or DXT.
    5. Set Normal Map Encoding to DXT5nm-style. This will ensure that normal maps display correctly on Magic Leap 2.
  3. Navigate to the Identification section
    1. Make sure the the Package Name is unique, otherwise it may conflict with an app already installed on your device.
    2. Set the Minimum API Level to 29.
  4. Locate the Configuration section
    1. Set the Scripting Backend to IL2CPP.
    2. Check the box next to the Target Architecture x86-64 (Chrome OS and Magic Leap 2) and set the Target Devices dropdown to All Devices.

Custom Manifest​

This section provides instructions on how to create a custom manifest file and declare Magic Leap 2 specific permissions for your application. For more information, see the Permissions Overview guide.

info

Editing your application's permissions through the Unity Editor Window is only available if you have a valid MLSDK path assigned the Unity Editor's Preferences Window.

  1. Enable a custom manifest in your project's settings by going to Edit > Project Settings > Player, then under Publishing Settings select Custom Main Manifest.
  2. Go to Edit > Project Settings > Magic Leap > Permissions to enable permissions for various features.

Build Settings​

Build Settings let you set the target platform, configure build-related settings, and start the build process.

  1. In the menu, go to File and select Build Settings.
  2. Under Platform, select Android.
  3. Click Switch Platform.
  4. You are now ready to add scenes to the build order and build to the device!

Validate Project Settings​

Developers can use Unity's Project Validation tool to validate that project's settings have been configured properly.

  1. Open the OpenXR Project validation window (Window > XR > Open XR > Project Validation).
  2. Verify that no issues are listed. If there is an issue, select Fix All in the top right of the Project Validation window.
info

This tool can be used to configure new projects in the future. Note, the validation tool does not check your project's Manifest, API level, or XR Plugin Management settings.

Troubleshooting Magic Leap Hub Interaction​

If you experiencing issues connecting and deploying a project to your device, it might be because the Unity Editor is using a version of ADB that conflicts with the one the Magic Leap Hub is using. The can cause device communication to terminate incorrectly. To fix this, you can set the Magic Leap Hub's ADB installation path to the one used by the Unity Editor.

  1. Open the Magic Leap Hub.
  2. Navigate to the Magic Leap Hub's Developer Settings by selecting Home > Settings > Magic Leap Hub > Developer
  3. Select the Use custom adb checkbox and set the path to the Android Tools used by Unity.
  4. To save the path you set, deselect the Use custom adb checkbox.

If you are unsure which SDK path is used by your Unity installation, you can view the Android SDK path used by the Unity Editor inside Unity's Preferences Window.

  1. In the Unity Editor, open your project. If you don't have a project created, you can view the Android SDK path by opening a new project.
  2. Select Edit > Preferences (macOS: Unity > Preferences).
  3. In the left navigation column, select External Tools. The Android section of the External Tools panel contains entries for JDK, SDK, NDK, Gradle.
  4. Copy the SDK path.
  5. In the Developer Setting page in the Magic Leap Hub, paste the copied path into the Use custom adb field. Note that the adb service is located in the SDK's platform-tools directory.
C:\Program Files\Unity\Hub\Editor\[EditorVersion]\Editor\Data\PlaybackEngines\AndroidPlayer\SDK

Finally disable the Kill ADB server on exit option for your project, unless you specifically need this behavior. By default, the preference is active, which can cause disruptions when using the Magic Leap Simulator.

  1. Open the Unity Editor.
  2. Select Edit > Preferences (macOS: Unity > Preferences).
  3. In the left navigation column, select External Tools.
  4. Scroll down to the Kill ADB server on exit option and deselect the checkbox.

Next Steps​