About the Oculus XR Plugin

The Oculus XR Plugin enables you to build applications for a variety of Oculus devices including the Rift, Rift S, Quest, and Go.

Supported XR plugin subsystems

Display

The display subsystem provides stereo rendering support for the XR Plugin. It supports the following graphics APIs:

• Windows (Rift, Rift S)
  • DX11
• Android (Quest, Go)
  • OpenGL ES 3.0
  • Vulkan (Experimental, Quest only)

Input

The input subsystem provides controller support, haptics, and tracking for the controllers and HMD.

XR Management support

Integration with XR Management isn't required to use the Oculus XR Plugin, but it offers a simpler and easier way of using this and other Providers within Unity. The Oculus XR Plugin package ships with built-in XR Management support. For more information, see XR Management documentation.

Integrating the Oculus XR Plugin with XR Management offers the following functionality:

• Runtime Settings - Configure runtime settings such as rendering modes, depth buffer sharing, Dash support, etc.
• Lifecycle Management - The Oculus XR Plugin ships with a default XR Plugin loader implementation that handles subsystem lifecycle such as application initialization, shutdown, pausing, and resuming.

Windows standalone settings (Rift, Rift S)

• Shared Depth Buffer - Enable or disable support for using a shared depth buffer. This allows Unity and Oculus to use a common depth buffer, which enables Oculus to composite the Oculus Dash and other utilities over the Unity application.
• Dash Support - Enable or disable Dash support. This inintializes the Oculus Plugin with Dash support, which enables the Oculus Dash to composite over the Unity application.
• Stereo Rendering Mode - You can select Multi Pass or Single Pass Instanced stereo rendering mode.
  • Multi Pass - Unity makes two passes across the scene graph, each one entirely indepedent of the other. Each pass has its own eye matrices and render target. Unity draws everything twice, which includes setting the graphics state for each pass. This is a slow and simple rendering method which doesn't require any special modification to shaders.
  • Single Pass Instanced - Unity uses a single texture array with two elements. Unity converts each call into an instanced draw call. Shaders need to be aware of this. Unity's shader macros handle the situation.

Android settings (Quest, Go)

• V2Signing - Enable this if you are building for Quest. This enables application signing with the Android Package (APK) Signature Scheme v2. Disable v2 signing if you're building for Oculus Go.
• Stereo Rendering Mode - You can select Multi Pass or Multiview stereo rendering mode.
  • Multi Pass - Unity makes two passes across the scene graph, each one entirely indepedent of the other. Each pass has its own eye matrices and render target. Unity draws everything twice, which includes setting the graphics state for each pass. This is a slow and simple rendering method which doesn't require any special modification to shaders.
  • Multiview - Multiview is essentially the same as the Sigle Pass Instanced option described above. The only difference is that the driver does the draw call conversion, so it requires less work on Unity's side. As with Single Pass Instanced, shaders need to be aware of the Multiview setting.