Oculus/Meta Quest 3: Best OculusLink.ini for 120Hz Air Link

To achieve 120Hz without “rainbow vomit” artifacts or massive lag spikes ($L_{ms}$), you must bypass the standard 200 Mbps cap.

Configuration Interface

Instead of a .ini file, Meta uses the Oculus Debug Tool.

Path: C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe

Optimized “120Hz Air Link” Configuration Table

Parameter	Recommended Value	Technical Purpose
Pixels Per Display Pixel Override	1.2	Forces 20% supersampling for elite clarity.
Asynchronous Spacewarp	Disabled	Prevents “ghosting” by disabling 60fps-to-120fps interpolation.
Video Codec	H.264	Crucial. H.264 allows for higher bitrates than HEVC/AV1 on Air Link.
Encode Bitrate (Mbps)	500 (Paste via Notepad)	Bypasses the 200 Mbps UI limit for near-wired quality.
Link Sharpening	Quality	Uses the Quest 3’s native CAS (Contrast Adaptive Sharpening).
Sliced Encoding	Enabled	Reduces latency by encoding/decoding frames in chunks.

HowTo: Engineering the Perfect Wireless Pipeline

Follow these GameEngineer.net technical steps to stabilize your 120Hz stream:

1. The Notepad Bitrate Hack: The ODT UI often prevents you from typing values above 500. Open Notepad, type 500 (or up to 800 if on Wi-Fi 6E), copy it, and paste it into the Encode Bitrate field.
2. Meta Link App Resolution: In the PC app, go to Devices > Quest 3 > Graphics Preferences. Set Refresh Rate to 120Hz and slide the Resolution to 1.5x (5408×2736). This is the 1:1 “Native” point for the Quest 3 lenses after distortion correction.
3. The “OVRServer” Priority Fix: To prevent background tasks from causing stutters, open Task Manager > Details. Right-click OVRServer_x64.exe and set Priority to High. This ensures the encoding thread has immediate CPU access.
4. Audio Stutter Workaround: If you experience “crackling” audio at 120Hz, go to Windows Sound Settings and ensure your Default Output is set to your PC speakers, then tell the Meta Link app to “Mirror Audio” instead of direct output. This bypasses a common driver-level synchronization bug.
5. FOV Tangent Multiplier: If your GPU (e.g., RTX 3080/4070) is struggling, set the FOV Tangent Multiplier to 0.9;0.9. This slightly crops the edges of the image (which you can’t see anyway) to reduce the total rendered pixel count by ~19%.

Technical Explanation: Bitrate vs. Decode Latency

In a wireless environment, the Total Latency ($L_{total}$) is defined as:

$$L_{total} = T_{render} + T_{encode} + T_{network} + T_{decode}$$

At 120Hz, a new frame must be presented every 8.33ms. While HEVC/AV1 provides better compression, their Decode Time ($T_{decode}$) on the Quest 3’s mobile chip is significantly higher ($>10\text{ms}$). By forcing H.264 at a high bitrate (500+ Mbps), we utilize a simpler decoding path on the headset. This drops $T_{decode}$ to ~5ms, allowing the entire pipeline to fit within the 120Hz window without triggering the dreaded Asynchronous Spacewarp, which would otherwise drop your perceived frame rate.