The site has a new content architecture. We've added the ability to select your development device to show device-specific content. Please read our blog post Oculus Developer Center Update: Device-centric Documentation Architecture for more information.
All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.
This section describes the process to configure and build Unity applications targeted at Android platforms.
During the build process, Unity projects with VR support enabled are packaged with an automatically-generated manifest which is configured to meet our requirements (landscape orientation, vr_only, etc). All other values, such as Entitlement Check settings, are not modified. Do not add the
noHistory attribute to your manifest.
To build an application for submission to the Oculus Store, you must build a custom manifest using the Oculus Integration.
Unity’s Universal Render Pipeline (URP) allows you to control to modify the render pass of your application. See Unity’s documentation about how to use (or upgrade) and modify the URP - https://docs.unity3d.com/Packagesemail@example.com/manual/index.html
For Oculus development, we recommend that developer use the linear color space. The gamma color space is supported, but not recommended. Oculus runtimes support sRGB textures, using the linear color space and leveraging hardware sRGB for the conversion is the recommended configuration.
We recommend that developers do not use any post-processing. There is a measurable performance cost to any post-processing pass.
From the File menu, select Build Settings…. Select Android as the platform. Set Texture Compression to ASTC.
We recommend unchecking Development Build for your final build, as it may impact performance.
All required settings are enforced automatically, but you may wish to make additional settings as appropriate. For example, Multithreaded Rendering, where the engine will move graphics API calls from the main thread to a separate worker thread, and Low Overhead Mode, where the engine will skip error checking in release versions of an app (only on apps using OpenGL ES).
For more information on our recommended settings, see the Best Practices for Rift and Mobile section.
Navigate to Edit > Project Settings > Quality. We recommend the following settings:
|Pixel Light Count||1|
|Texture Quality||Full Res|
|Anisotropic Textures||Per Texture|
|Anti Aliasing||2x or 4x Multi Sampling|
|Realtime Reflections Probes||Select|
|Billboards Face Camera||Select|
The Anti-aliasing setting is particularly important. It must be increased to compensate for stereo rendering, which reduces the effective horizontal resolution by 50%. An anti-aliasing value of 2X is ideal, 4x may be used if you have performance to spare. We do not recommend 8x.
For more information on our recommended settings, see Best Practices for Rift and Mobile.
You may build an APK locally and sideload it to your phone. For information on getting development builds on your device, please review the Device Setup page in the native development guide.
Oculus provides the OVR Build APK and Run and OVR Scene Quick Preview tools to reduce the time required to build and deploy APK and scenes on your Android device. See the Unity Build Tools page for details.
The Oculus Unity Integration provides the OVRPlatform Tool that you can use to upload your app to Oculus. You can upload development builds to a pre-production release channel, or your final build for Store Review. The OVRPlatform Tool uses the Oculus Platform Command Line Utility.
For information about uploading your apps to a Release Channel or Store using the Oculus Dashboard, please see the Uploading Android Apps page.
To use the OVRPlatform Tool, open the diaglog by selecting Oculus / Tools / Oculus Platform Tool.
Review Oculus Platform Command Line Utility for information about the parameters in the OVRPlatform Tool dialog.