Provider plug-ins are packages created to support XR devices and platforms.
Use the XR Plug-in Management settings to manage which XR devices and platforms your project supports. You can also configure key settings for these XR provider plug-ins.
See XR provider plug-in framework for information about provider plug-ins and how they work.
Before you can enable XR plug-ins, you must install the XR Plug-in Management package. You can install the package directly from the Project Settings window:
Open the Project Settings window (menu: Edit > Project Settings).
Select XR Plug-in Management from the list of settings areas along the left side of the settings window.
Before installing the XR Plug-in Management package
If necessary, click Install XR Plug-in Management.
After installing the XR Plug-in Management package
The XR Plug-in Management settings page displays a tab for each available build target. Each tab displays the list of available XR provider plug-ins for that platform. This list contains the plug-ins officially supported by Unity or its partners and also any third-party provider plug-ins you have installed with the Package Manager.
Tip: Use the Unity Hub to install platform modules, such as Android or iOS, to add support for additional build targets. See Add modules in the Unity Hub documentation for instructions.
When you enable a plug-in, XR Plug-in Management installs the associated package.
To enable a provider plug-in:
Open the Project Settings window (menu: Edit > Project Settings) and select the XR Plug-in Management section.
Select the tab for the target build platform. For example, to enable a plug-in for a device that runs the Android operating system, click the tab with the Android icon.
Android build platform with the ARCore provider enabled
Enable the desired provider plug-in.
Repeat for additional plug-ins.
注意:
After you enable a provider plug-in and Unity installs the associated package, any settings for the provider are displayed as subsections under the XR Plug-in Management settings.
Oculus provider plug-in settings under XR Plug-in Management
If a plug-in supports more than one build target, its settings page includes a tab so that you can configure the settings for each target independently.
To configure the settings for a provider plug-in:
See the documentation of individual plug-ins for information about plug-in settings. You can access the documentation using the View documentation link in the Package Manager.
Use the View documentation link to access plug-in documentation
Some provider plug-ins and other packages implement project validation checks to help ensure that your project is set up correctly. You can view the status of these checks on the Project Validation section underneath XR Plug-in Management on the Player Settings window.
Project validation checks
If a validation check is followed by a Fix button, you can click the button to automatically fix the issue. Otherwise, you must fix the issue manually. Clicking Edit opens the settings UI to the appropriate section so that you can make any needed changes. Validation checks marked with a red stop icon must be corrected. Checks marked with a yellow warning icon can be ignored or deffered, but you should fix them if possible for best performance or compatibility.
Refer to XR project validation window for additional information.
You can enable more than one provider plug-in to support multiple XR devices and platforms in the same project.
Note: In some cases, one provider plug-in can support more than one device and operating system. For example, the OpenXR plug-in supports multiple XR devices, operating systems, and build targets.
Unity includes all the enabled plug-ins for the current build target when you make a build. At runtime, Unity uses the first plug-in that loads successfully. Unity attempts to load provider plug-ins in the order they are shown in the XR Plug-in Management list, which is in alphabetical order by default. If you need more control over which plug-in is loaded, you can do one of the following:
See XR loading for more information about customizing how provider plug-ins are loaded and initialized.
Note: The Mock HMD Loader plug-in only works in the Unity Editor during Play mode and does not affect builds.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.