Use Oculus Debug Tool to tune Quest Link and Air Link for flight simulators, with safe ASW, bitrate, FOV and diagnostic settings.
To improve VR performance in PC flight simulators with Oculus Debug Tool, start from defaults, monitor frame timing, keep ASW on Auto, avoid stacked resolution scaling, and tune Link bitrate separately from simulator graphics. Change one setting at a time, then retest the same aircraft, airport, weather and cockpit view.
What can Oculus Debug Tool improve?
Oculus Debug Tool controls the Meta PC compositor and, with Quest headsets, the Link or Air Link video stream. It can adjust reprojection, encoded image quality and rendered field of view, but it cannot remove a simulator's CPU bottleneck or compensate for demanding traffic, scenery and cockpit systems.
The tool is installed with the Meta Quest Link software for Windows. Link-specific encoder settings affect a Quest connected through wired Link or Air Link; they do not govern Steam Link or another PC-VR streaming system. On a native Rift headset, ASW and pixel-density controls may apply, but the Link encoder settings are irrelevant.
If the headset is not entering PC VR reliably, establish the Quest Link or Air Link connection for flight simulation before changing debug settings. The same tuning principles then apply to Microsoft Flight Simulator, X-Plane, DCS and Prepar3D.
Safe Oculus Debug Tool settings for flight simulators
The safest starting point is automatic or default values, with ASW on Auto and no extra pixel-density multiplier. In Oculus Debug Tool, a value of 0 often means that the runtime should choose its default automatically.
| Setting | Starting value | When to change it |
|---|---|---|
| Asynchronous Spacewarp | Auto | Force a half-rate mode only when the simulator can hold half the headset refresh rate consistently. Disable it temporarily to diagnose reprojection artefacts. |
| Pixels Per Display Pixel Override | 0 or default | Leave this alone and control resolution in one place. It can stack with the Meta headset resolution, OpenXR scaling and the simulator's render scale. |
| FOV-Tangent Multiplier | 0;0 or default | Try a modest reduction such as 0.90;0.90 only when extra GPU headroom is needed and no dark border becomes visible. |
| Encode Resolution Width | 0 or default | Avoid fixed values copied from older headset guides. Automatic sizing normally handles differences between Quest models and software revisions. |
| Encode Bitrate (Mbps) | 0 or automatic | With wired Link, increase it gradually only to reduce visible compression. With Air Link, use the automatic or dynamic bitrate control rather than forcing competing values. |
| Encode Dynamic Bitrate | Automatic for Air Link | Set a lower limit or cap only when wireless latency and frame drops indicate that the connection cannot sustain its selected rate. |
| Link Sharpening | Auto | Change it for image preference, not as a major performance adjustment; its performance effect is normally small. |
Leave settings such as Distortion Curvature, Sliced Encoding and Mobile ASW at their defaults unless diagnosing a known runtime problem. Changing every available field rarely produces a useful flight-simulation preset.
How do I tune Oculus Debug Tool step by step?
Tune Oculus Debug Tool by identifying whether the missed frames come from the simulator, compositor or Link transport before altering the associated setting.
- Choose a realistic headset refresh rate. Set this in the Meta PC software, not Oculus Debug Tool. At 90 Hz, for example, the simulator must produce either 90 native frames per second or a stable 45 fps for half-rate ASW; available refresh rates vary by headset.
- Open Oculus Debug Tool. Its usual installation path is
C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe. Connect Link or Air Link before starting the simulator. - Restore the baseline. Set ASW to
Auto, clear forced bitrate and resolution values, and return the FOV multiplier to its default. Record any existing settings before replacing them. - Enable a diagnostic HUD. Use Performance Summary or App Render Timing to inspect application performance. The Oculus Link HUD, where available, helps expose transport and encoding trouble.
- Repeat one demanding scenario. Use the same aircraft, runway, weather, traffic, cockpit view and head movement. Testing unrelated flights makes it impossible to tell whether a change helped.
- Adjust the actual bottleneck.
- If application GPU timing is too high, reduce headset resolution, simulator render scale, clouds, shadows or reflections.
- If CPU timing is too high, reduce traffic, terrain or object detail, and other simulator-side workloads. Oculus Debug Tool cannot solve this by lowering bitrate.
- If application timing is stable but the Link HUD shows drops or latency spikes, lower the encoded bitrate and inspect the USB or wireless connection.
- If only the compositor is missing its target, try Auto ASW or a lower headset refresh rate.
- Reconnect when required. Some changes apply immediately, while encoder and FOV changes may require Link to be disconnected and reconnected. If a value appears to be ignored, restart the Oculus service from the tool's Service menu, then reconnect; this will end the active VR session.
- Turn off the HUD. Once the chosen settings are stable, disable diagnostic overlays and confirm the result in a normal flight.
Microsoft Flight Simulator 2024 users should combine this process with a measured approach to render scale, level of detail, reprojection and VRAM usage; our MSFS 2024 VR optimisation sequence covers those simulator-side controls.
Should I force ASW in a flight simulator?
Keep ASW on Auto unless the simulator stays comfortably above half the headset refresh rate but cannot reach the full rate. A stable half-rate output usually feels better than continually switching between native and reprojected frames.
ASW can distort propeller discs, rotor blades, wing struts, glass-cockpit text and fast-moving terrain. Disable it briefly to confirm that reprojection causes an artefact, but leaving it disabled can produce more obvious judder during head movement. If frame rate also falls below the half-rate target, reduce simulator settings or headset refresh instead of forcing ASW harder.
Should I increase Link bitrate or render resolution?
Increase render resolution for genuinely soft instruments, but increase bitrate only for compression artefacts such as blockiness, colour smearing or detail breaking up during head movement. Bitrate does not create extra panel detail that was never rendered.
For wired Link, begin with automatic bitrate and increase it in small steps while watching latency and dropped frames. Audio breakup, black edges during rapid head turns, sudden latency increases or disconnections are signs that the selected bitrate is too aggressive for the connection or headset decoder.
Air Link normally benefits from dynamic bitrate because wireless capacity changes with interference and network load. A mistake we see constantly is combining a high fixed Oculus Debug Tool bitrate with a separate dynamic Air Link setting, producing instability without improving cockpit readability. Our guide to separating cockpit resolution blur from Link compression explains which image-quality control to change.
Can reducing the FOV multiplier improve VR performance?
A modest FOV-Tangent Multiplier reduction can lower the number of pixels rendered without reducing central cockpit resolution. Start around 0.90;0.90, check every edge while moving your eyes and head, and return to default if black borders or premature image clipping appear.
This is most useful when the headset renders an area outside the portion you can actually see. The acceptable value varies with headset fit, lens spacing and face interface, so there is no universal flight-simulator preset.
Why can Oculus Debug Tool make stutter worse?
Oculus Debug Tool usually makes stutter worse when several resolution multipliers are stacked, bitrate exceeds the connection's capacity, or reprojection settings conflict with another runtime.
- Stacked supersampling: Meta headset resolution, Pixels Per Display Pixel Override, OpenXR scaling and simulator render scale can multiply together. Use one main resolution control and leave the others neutral.
- Excessive bitrate: Higher values improve compression only while the encoder, cable or wireless link and headset decoder can sustain them.
- Wrong bottleneck: Lowering Link bitrate will not repair a CPU-limited airport or glass cockpit. It only reduces streaming load and image quality.
- Multiple reprojection systems: When another runtime or compositor sits in the path, do not assume Oculus ASW is the only active motion-smoothing control.
- Settings that reverted: Debug values can return to defaults after service restarts or software updates. Verify them before troubleshooting a new regression.
- Too many simultaneous changes: A copied preset may alter FOV, bitrate, resolution and ASW at once, concealing which setting caused the fault.
If application frame timing looks acceptable but motion still jumps or oscillates, use our VR jitter and stutter diagnosis for MSFS 2024 to separate simulator, headset, streaming, CPU and GPU causes. The dependable general baseline remains defaults, ASW Auto, one resolution scaler and automatic bitrate until measurements justify changing them.