Oculus Debug Tool

Oculus Debug Tool
Information
Type	PC VR diagnostic utility
Developer	Meta Platforms
Operating System	Windows
Supported Devices	Oculus Rift; Meta Quest through Link or Air Link
Website	Official documentation

Oculus Debug Tool (ODT) is a graphical utility for Meta Platforms' Windows PC VR runtime. It displays diagnostic overlays and changes rendering and streaming settings. It has been used with Oculus Rift applications and with Meta Quest Link and Air Link, through which Quest headsets display applications rendered on a PC.

ODT controls the PC runtime. For standalone Quest applications, Meta documents a different set of monitoring tools, including Meta Quest Developer Hub, OVR Metrics Tool and Perfetto.

Distribution and history

Meta's PC documentation gives the executable's location as Program Files\Meta Horizon\Support\oculus-diagnostics\OculusDebugTool.exe. ODT requires administrator privileges. Meta instructs users to run the copy in the installed distribution because a relocated copy can become incompatible after an update. The documented location in earlier Oculus software was C:\Program Files\Oculus\Support\oculus-diagnostics.

Road to VR described ODT as an Oculus SDK utility in June 2016, with developer diagnostics and control over compositor layers and pixel density. Its Rift tests also showed that increasing pixel density could exhaust the available graphics performance. In October 2020, UploadVR reported that an Oculus PC app test-channel update exposed Link's encoding bitrate through ODT. That report concerns the software and hardware tested in 2020; its bitrate limits and observed image quality are historical results.

Performance displays

ODT can show performance, stereo debugging and compositor-layer overlays in the headset. The Performance HUD is rendered by the runtime compositor and reports application and compositor activity separately.

HUD view	Information reported
Performance summary	Application frame rate, unused performance, application frame drops and compositor frame drops.
Latency timing	Tracking-to-display timing for the application, timewarp timing, and the interval between presenting a buffer and the first displayed scanline.
Application render timing	Application CPU and GPU render time, frame submission rate and missed submissions.
Compositor render timing	Final composition rate, compositor GPU time and missed display synchronization deadlines.
Asynchronous SpaceWarp statistics	Spacewarp availability, activation and extrapolated-frame counters.

The current ODT documentation also lists Oculus Link, Oculus Link Detail and Network Guardian Info modes.

The distinction between application and compositor drops can expose problems that an application's own frame counter misses. In an October 2021 Quest 2 test on Windows 11, UploadVR's David Heaney reported judder despite an application rate of 90 frames per second. Switching ODT views revealed compositor drops in both wired Link and wireless Air Link sessions.

Interpreting measurements

Meta's PC optimization tutorial uses the summary to identify missed frames, then compares CPU and GPU timing to isolate an intentionally overloaded shader. It supplements these runtime displays with Event Tracing for Windows, Windows Performance Analyzer and GPUView to examine scheduling and GPU work.

HUD timing has qualifications. Meta notes that application GPU time can include idle gaps when the CPU does not supply work fast enough. Near full GPU utilization, compositor work can also inflate the apparent application GPU time. Unused performance is computed from measured CPU and GPU times relative to the headset's native frame interval.

ODT's motion-to-photon latency display has also been used in original research. A 2021 study by Jacqueline M. Fulvio, Huiyuan Miao and Bas Rokers used ODT when characterizing an Oculus Rift DK2 experimental setup. The tool reported 14 ms, but the authors also filmed physical headset movement and the display at high speed because the runtime measurement did not include the true onset of physical movement. These were measurements of their apparatus, not a general latency specification for ODT or Rift headsets.

A separate 2024 study, PredATW, used ODT to collect variations in timewarp latency on Quest 2. For the study's deeper analysis of GPU scheduling, however, Akanksha Dixit and Smruti R. Sarangi found its aggregate statistics insufficient and used NVIDIA Nsight Graphics and simulation. The paper illustrates both a use of ODT for runtime measurements and a limit on the detail available from those measurements.

Rendering and spacewarp controls

The pixel-density override changes the resolution at which an application renders. In Rift software, Road to VR described its use for supersampling: a density factor of two produced four times as many rendered pixels. Its 2016 tests found a visible improvement but also a substantial GPU cost; the publication explicitly qualified compatibility and interaction with in-game density settings as incompletely tested.

ODT also exposes a horizontal and vertical field-of-view tangent multiplier for changing the rendered view, including wider desktop mirrors for gameplay capture.

Asynchronous SpaceWarp (ASW) extrapolates intermediate frames when a PC application cannot maintain the required native rate. Meta's Rift documentation describes a 90 Hz display with the application reduced to 45 frames per second while ASW supplies intermediate frames.

Documented PC ASW option	Purpose in Meta's Rift testing description
Auto	Lets the runtime activate ASW when needed.
Disabled	Turns ASW off.
Force 45fps, ASW disabled	Tests reduced application rendering without ASW extrapolation.
Force 45fps, ASW enabled	Tests reduced application rendering with ASW extrapolation.

Meta's ODT measurement workflow disables ASW to assess the application's performance without frame synthesis. The PC ASW system is distinct from Application SpaceWarp, which developers integrate into standalone Quest applications.

Link and Air Link settings

Link sends the PC's rendered output to a Quest headset as compressed video. Rendering resolution, encoding resolution and bitrate therefore describe different parts of the output process: the application image, the transmitted image's dimensions, and the data transmitted per second. UploadVR's 2020 Link report distinguishes these controls and describes compression artifacts that changed with bitrate.

Control	Function
Encode Resolution Width	Overrides video width while retaining aspect ratio.
Video Codec	Selects the default codec, H.264 or H.265.
Sliced Encoding	Enables or disables encoding in slices.
Bitrate controls	Set encoding bitrate, dynamic adaptation and its maximum.
Dynamic Bitrate Offset (Mbps)	Adds a constant offset and overrides the maximum-bitrate setting.

Meta states that changes in this group require an OVRServer restart and that high bitrate values can cause instability.

For image sharpening, Meta's July 2023 documentation introduced Super Resolution through ODT's Link Sharpening option set to Quality. This is a spatial upscaling and sharpening operation in the Quest compositor. Meta notes that its GPU cost varies with image content and that the choice between sharpening and a higher eye-buffer resolution depends on the application's bottleneck.

Settings interactions have changed with software versions. UploadVR's May 2022 Air Link guide reported that a manually assigned ODT Link bitrate could impair Air Link performance, and described removing that override before using the wireless connection. The guide also distinguished Air Link's own fixed and dynamic bitrate controls and the tradeoff between image quality, latency and stuttering. Those instructions describe the 2022 software; they do not establish a single suitable bitrate or override combination for every PC, network and headset.

Capture and desktop output

Related diagnostic tool	Documented use
Performance Profiler	Graphs application performance in real time and exports captured statistics to a CSV file.
Lost Frame Capture	Records dropped-frame events, saves and opens Oculus Debug Archive (.oda) files, groups nearby losses into clusters, and displays associated eye images and frame-rate graphs. Meta documents it in the Rift PC workflow.
Compositor Mirror	Displays the compositor's headset output on a PC monitor, including system overlays. Its executable is OculusMirror.exe in the installed Support\oculus-diagnostics directory; it has its own display and capture options.

The compositor mirror can itself drop frames that were displayed in the headset. Meta documents a mirror frame-drop indicator for detecting these losses, so a desktop capture is not automatically a record of every frame seen in the headset.

Standalone Quest development

Meta Quest Developer Hub (MQDH) is a separate Windows and macOS application for managing Quest devices, deploying applications, reading logs, recording the headset view and uploading builds. Its Performance Analyzer obtains headset metrics through an ADB connection, displays configurable graphs and device logs, and launches Perfetto traces. MQDH can also install OVR Metrics Tool to display and record metrics for applications running on the headset. These tools measure the standalone application on Quest; ODT's PC HUD and Link controls belong to the PC rendering and streaming context.

Reviewed 12 October 2026. PC runtime diagnostics, documented installation paths and controls, dated Rift and Link reporting, and the cited studies' measurement methods. About review dates.