Unity supports XR development through its plug-in framework and a set of feature and tool packages. Use the XR Plug-in Management settings page to enable XR support in a Unity project and to choose the plug-ins for the XR devices your project supports. Use the Package Manager to install the additional feature packages.
다음 다이어그램은 현재 Unity XR 플러그인 프레임워크 구조와 플랫폼 공급자 구현과 함께 작동하는 방식을 보여줍니다.
Plug-ins for an XR platform implement the subsystem interfaces defined in the Unity XR SDK. The Unity Engine and XR packages use the subsystem interfaces to provide features to XR apps.
An XR provider plug-in is a Unity plug-in that supports an XR device platform. For example, the ARCore plugin supports the Android AR platform on hand-held Android devices, while the Oculus plug-in supports Oculus devices on both Windows and Android.
An XR provider plug-in implements interfaces defined by the Unity XR SDK. These interfaces are called Subsystems in Unity XR. A plug-in that implements one or more subsytems is called a Provider plug-in. Typically, a provider plug-in uses the device maker’s own native libraries to implement the Unity interfaces for their devices. The provider plug-in registers the subsystems it provides so that the Unity XR code knows which features are available when it loads the plug-in.
Unity code in the engine and packages use the subsystem interfaces to communicate with the active providers and to provide XR features to your application. Because of this common interface, you can generally reuse the same code across many XR devices. (Of course, if a provider or device doesn’t support a particular feature, then that feature cannot work when using that provider or on those devices lacking the required hardware or software support.)
XR subsystems provide XR features to your Unity application. The Unity XR SDK defines a common interface for subsystems so that all provider plug-ins implementing a feature generally work the same way in your app. Often you can change the active provider and rebuild your app to run on a different XR platform, as long as the platforms are largely similar.
The Unity Engine defines a set of fundamental XR subsystems. Unity packages provide additional subsytems. For example, the AR Subsystems package contains many of the AR-specific subsytem interfaces.
Unity 엔진에 정의된 보조 시스템은 다음과 같습니다.
보조 시스템 | 설명 |
---|---|
Display | 스테레오 XR 디스플레이 |
Input | 공간 트래킹 및 컨트롤러 입력 |
Meshing | 환경 스캔에서 3D 메시를 생성합니다. |
Note: Unity applications typically do not interact with subsytems directly. Instead, the features provided by a subsytem are exposed to the application through an XR plug-in or package. For example, the ARMeshManager component in the AR Foundation package lets you add the meshes created by the Meshing subsystem to a scene.
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.