Oculus Go Development

On 6/23/20 Oculus announced plans to sunset Oculus Go. Information about dates and alternatives can be found in the Oculus Go introduction.

Oculus Quest Development

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.

Set Up for Platform Development with Unity

You can use the platform SDK to develop apps for Rift or mobile VR devices. This guide will walk you through the basics of setting up your development environment, initializing the SDK, and checking the user’s entitlement.

The Sample Apps are available as reference when implementing the steps on this page.

Note: As of version 1.32, the platform SDK supports Unity development for ARM64 mobile devices.

Create an App

Before you can integrate the Platform SDK, you’ll need to create an app if you have not done so already. To create an app see the information on the Creating and Managing Apps page.

Configure Your Development Environment

Configure your development environment by adding Oculus Platform Support to your Unity project. There are two ways to add the Oculus APIs to your Unity development environment.

  1. Navigate to the Oculus Integration page and select Open in Unity.
  2. In the Editor, select the Asset Store tab, Search for ‘Oculus Integration’, and select Import.

Once you’ve imported the Oculus Integration package, select the Oculus Platform tab at the top of the page and select Edit Settings. A panel will open for you to enter either your Oculus Rift App Id or Mobile App Id. These are your unique app identifiers and can be retrieved from the API page on the Oculus Dashboard.

If you’re planning to test your builds locally in standalone mode, also add valid test user credentials to the Use Standalone Platform section. Create test users for your organization in the Developer Center under the Settings tab. Additional information about using the SDK in Standalone Mode can be found below.

Configuring Your App for Local Development

The configuration steps in this section will allow developers to run local builds of the application during the development process. This process is required, otherwise local versions of the app will not pass the entitlement check that you’ll integrate below.

  1. Add the user(s) to your org. See the Manage Your Organization and Users for information about managing your organization.
  2. If some of your developers are not part of the application’s organization, and they need to run your application outside the normal install directory. Add the registry key AllowDevSideloaded as DWORD(1) to the registry folder at HKLM\SOFTWARE\Wow6432Node\Oculus\OculusThis does not bypass having a valid entitlement, it just bypasses the directory check.

Once the steps above are completed the entitlement check will succeed when running a local build of your application.

Initialize the SDK and Perform the Entitlement Check

The first step to integrating the SDK is implementing the initialization function, and performing the user entitlement check. For instruction on how to do this, see Entitlement Checks.

Use the Platform in Standalone Mode

Standalone mode allows you to initialize the Platform SDK in test and development environments. Standalone mode is useful for testing Matchmaking where you can run multiple apps on the same box to test your integration. Initializing in standalone mode limits the SDK from connecting any locally running Oculus Service processes.

To initialize the SDK in standalone mode, call Platform.InitializeStandaloneOculus to initialize in standalone mode with the OculusInitParams identified below.

Where the OculusInitParams are formed:

{
public int sType;
public string email;
public string password;
public UInt64 appId;
public string uriPrefixOverride;
}

The Init Param values are:

  • sType - Credential struct type.
  • email - Email address associated with Oculus account.
  • password - Password for the Oculus account.
  • appID - ID of the application (the user must be entitled to this app)
  • uriPrefixOverride - optional override for https://graph.oculus.com

Checking Errors

Sometimes things go wrong and you’ll want to know what happened. Checking the error code and message can provide insight to what happened. Some errors have an accompanying message that you can display to your users if the error results from their actions.

To check for an error:

  1. With every request you make to the Oculus Platform, check to see if the message is an error by calling Platform.Message.IsError().
  2. If the message is an error, then call Platform.Message.GetError() to retrieve the error object.
  3. The error object contains information you can use to debug the reason for the error:
    • Error.GetHttpCode() returns an http code for the request, such as 400 or 500.
    • Error.GetCode() returns a code representing the class of error. For example, all errors with 100 as the code are invalid parameter errors. Different errors may map to the same code. Review the error message for specifics of what went wrong. For example, an invalid id or mission required param would both return errors with 100 as the code.
    • Error.getMessage() returns a the raw error as a JSON string, which include the fields:
      • message: the description of the what went wrong and possibly how to debug/fix the issue.
      • code: It typically matches Error.GetCode, except in cases when there is a conflict in client/server code. Use the value from Error.GetCode instead.
      • fbtrace_id: Helpful for when you are contacting support. We use this internally to find more information about the failing request.
    • Error.getDisplayableMessage() returns a message that you may optionally display to the user. It has none of the technical information obtained from Error.getMessage. An example displayable message could be You're not yet ranked on this leaderboard. if you are querying for the leaderboard of the app that the user has not been placed in. The value may be empty in the cases where it is a developer-caused error rather than a user-caused error.