Deploying to Quest — MRTK2

A Meta Quest (1 or 2) is required.

Setting up project for the Quest

1. Follow these steps to ensure that your project is ready to deploy on Quest.
2. Ensure that developer mode is enabled on your device. Installing the Oculus ADB Drivers is optional.

Setting up the scene

1. Create a new Unity scene or open a pre-existing scene like HandInteractionExamples.
   1. If creating a new scene, add MRTK to the scene by navigating to Mixed Reality Toolkit > Add to Scene and Configure.

MRTK integration

OpenXR (XR SDK)

MRTK's support for Quest devices comes via two different sources: Unity's OpenXR Plugin package for the XR SDK pipeline and the Mixed Reality OpenXR Plugin package. The OpenXR XRSDK Data Provider enables the use of both sources and must be used to deploy MRTK on the Quest.

You can use the Mixed Reality OpenXR Plugin to deploy MRTK applications to the Quest. After enabling OpenXR, ensure any required features are enabled (likely "Hand Tracking" and "Meta Quest Support").

Ensure your profile (if not using the MRTK default) is set up with the OpenXR Device Manager. See Configuring MRTK for the XR SDK pipeline for more information on ensuring your profile is ready for OpenXR.

Oculus (XR SDK)

MRTK's support for Quest devices comes via two different sources: Unity's Oculus Plugin package for the XR SDK pipeline and the Oculus Integration Unity package. The Oculus XRSDK Data Provider enables the use of both sources and must be used to deploy MRTK on the Oculus Quest.

The Unity XR SDK Pipeline enables the use of Oculus Touch controllers and head tracking with the Quest. This pipeline is the standard for developing XR applications in Unity 2019.3 and beyond. To use this pipeline, make sure that you using Unity 2019.3 or newer. This is required to deploy MRTK applications to the Quest.

The Oculus Integration Unity package allows for the use of hand tracking and controller models with the Quest.

Setting up the XR SDK Pipeline for Quest

1. Ensure that the Oculus XR Plugin is installed under Window --> Package Manager

   

2. Make sure that the Oculus Plug-in Provider is included in your project by going to Edit --> Project Settings --> XR Plug-in Management --> Plug-in Providers

   

Setting up the Oculus Integration Unity package to enable hand tracking

1. Download and import Oculus Integration from the Unity Asset Store. The latest version tested to work is 39.0.0. Prior versions will not work due to change made to the Oculus API. All versions of the Oculus Integration Package can be found from this archive.

2. Navigate to Mixed Reality Toolkit > Utilities > Oculus > Integrate Oculus Integration Unity Modules. Doing this will update the asmdefs with definitions and references needed for the relevant Quest code to function. It will also update the csc file to filter out the obsolete warnings produced by the Oculus Integration assets. The MRTK repo contains a csc file that converts warnings to errors, this conversion halts the MRTK-Quest configuration process.

   

3. In the imported Oculus folder (It should be found at Assets/Oculus), there is a scriptable object called OculusProjectConfig. In that config file, you need to set HandTrackingSupport to "Controllers and Hands".

   

Using the Oculus XR SDK Data Provider

1. Configure your profile to use the Oculus XR SDK Data Provider
   • If not intending to modify the configuration profiles
     • Use any of the default MRTK profiles, which are all configured across Unity's XR pipelines. The previous DefaultXRSDKConfigurationProfile is now labeled obsolete.
     • Go to Build and deploy your project to Quest.
   • Otherwise follow the following:

     • Select the MixedRealityToolkit game object in the hierarchy and select Copy and Customize to clone the default mixed reality profile.

       

     • Select the Input Configuration Profile.

       

     • Select Clone in the input system profile to enable modification.

       

     • Open the Input Data Providers section, select Add Data Provider at the top, and new data provider will be added at the end of the list. Open the new data provider and set the Type to Microsoft.MixedReality.Toolkit.XRSDK.Oculus > OculusXRSDKDeviceManager.

       

1. The Oculus XR SDK Data Provider includes an OVR Camera Rig Prefab which automatically configures the project with an OVR Camera Rig and OVR Hands to properly route input. Manually adding an OVR Camera Rig to the scene will require manual configuration of settings and input.

Removing Oculus Integration from the Project

1. Navigate to Mixed Reality Toolkit > Oculus > Separate Oculus Integration Unity Modules
2. Let Unity refresh as references in the Microsoft.MixedReality.Toolkit.Providers.Oculus.asmdef and other files are modified in this step
3. Close Unity
4. Close Visual Studio, if it's open
5. Open File Explorer and navigate to the root of the MRTK Unity project
6. Delete the UnityProjectName/Library directory
7. Delete the UnityProjectName/Assets/Oculus directory
8. Delete the UnityProjectName/Assets/Oculus.meta file
9. Reopen Unity

Build and deploy your project to Quest

1. Plug in your Quest via a USB 3.0 -> USB C cable

2. Navigate to File > Build Settings

3. Change the deployment to Android

4. Ensure that the Quest is selected as the applicable run device

   

5. Select Build and Run

   • You may encounter the following set of build errors when you select Build and Run the first time. It shouldn't prevent deployment. See issue #10449 for more information and potential mitigation options.

   

6. Accept the Allow USB Debugging prompt from inside the Quest

7. See your scene inside the Quest

Common errors

Quest not recognized by Unity

Make sure your Android paths are properly configured. If you continue to encounter problems, follow this guide.

Look under Edit > Preferences > External Tools > Android: