musicalcas.blogg.se

In the imported Oculus folder (It should be found at Assets/Oculus), there is a scriptable object called OculusProjectConfig.

The MRTK repo contains a csc file that converts warnings to errors, this conversion halts the MRTK-Quest configuration process. It will also update the csc file to filter out the obsolete warnings produced by the Oculus Integration assets. Doing this will update the asmdefs with definitions and references needed for the Navigate to Mixed Reality Toolkit > Utilities > Oculus > Integrate Oculus Integration Unity Modules. All versions of the Oculus Integration Package can be found from this archive. Prior versions will not work due to change made to the Oculus API. Setting up the Oculus Integration Unity package to enable hand trackingĭownload and import Oculus Integration from the Unity Asset Store. 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 XR SDK Pipeline for QuestĮnsure that the Oculus XR Plugin is installed under Window -> Package Manager The Oculus Integration Unity package allows for the use of hand tracking and controller models with the Quest.

This is required to deploy MRTK applications to the Quest. To use this pipeline, make sure that you using Unity 2019.3 or newer. This pipeline is the standard for developing XR applications in Unity 2019.3 and beyond. The Unity XR SDK Pipeline enables the use of Oculus Touch controllers and head tracking with the Quest. The Oculus XRSDK Data Provider enables the use of both sources and must be used to deploy MRTK on the Oculus Quest. 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. See Configuring MRTK for the XR SDK pipeline for more information on ensuring your profile is ready for OpenXR. After enabling OpenXR, ensure any required features are enabled (likely "Hand Tracking" and "Meta Quest Support").Įnsure your profile (if not using the MRTK default) is set up with the OpenXR Device Manager. You can use the Mixed Reality OpenXR Plugin to deploy MRTK applications to the Quest.

The OpenXR XRSDK Data Provider enables the use of both sources and must be used to deploy MRTK on the Quest. 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.