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.
The Oculus Debug Tool (ODT) enables you to view performance or debugging information within your game or experience. It also enables you to tune or configure related parameters, such as the field of view (FOV) size for a mirrored flat-screen view of the VR experience (which could be streamed to an audience in a more comfortable viewing format).
To start the Oculus Debug Tool:
Program Files\Oculus\Support\oculus-diagnostics\. Note that the Oculus Debug Tool should always be run directly from this location, in order to ensure a version match with the Oculus distribution. If you copy the Oculus Debug Tool to another location, it might not work after subsequent Oculus updates.
Double-click OculusDebugTool.exe. The Oculus Debug Tool opens. The main window is shown below with all of the first-level list headings expanded:
The ODT user interface is described in the following paragraphs.
It is a good idea to turn off Asynchronous SpaceWarp (ASW), so that you can get a true sense of how your application is performing (without the assistance of ASW). To do this, set the Asynchronous SpaceWarp option to Disabled:
If you selected Performance HUD, select which Performance HUD you want to view. Options include: Latency Timing, Render Timing, Performance Headroom, and Version Information. For more information, see Performance Head-Up Display. The HUD enables you or your users to view performance information for applications built with the SDK. The following is an example of the Performance HUD:
If you selected Stereo Debug HUD, configure the mode, size, position, and color from the Stereo Debug HUD options. The following is an example of the Stereo Debug HUD:
If you selected Layer HUD. select the layer for which to show information or select the Show All check box. The following is an example of the Layer HUD:
Larger FOV for Streaming Game Play
The FOV-Tangent Multiplier setting is provided by the Oculus Debug Tool, as shown in the following screenshot. This setting can be used to improve the viewing experience when streaming game play to an audience. With this feature, you can increase the size of the field of view (FOV) as it appears on mirrored flat screens, relative to what is displayed within the headset. This makes it more comfortable to view streamed or recorded game play since the FOV that is used within the headset can appear too constricted on flat screens, and thereby cause motion sickness on the part of the viewing audience. The FOV-Tangent Multiplier feature has two settings: Horizontal and Vertical. Simply set these values to the desired multiplier for the FOV. For example, if you set Horizontal to 1.2 and Vertical to 1.1, then the streamed FOV will be 20% larger horizontally, and 10% larger vertically, relative to the FOV within the headset. The ODT shows the Horizontal setting, followed by a semicolon, followed by the Vertical setting. So the previous example would be entered as 1.2;1.1 on the FOV-Tangent Multiplier line: