Best MSFS 2024 VR settings for Quest 3, covering OpenXR, refresh rate, render scale, TAA or DLSS, LOD, traffic and stutter fixes.
For Meta Quest 3 in Microsoft Flight Simulator 2024, start with 72 Hz, the Meta OpenXR runtime for Quest Link or Air Link, and the PC app’s recommended render resolution. Use TAA at 80–100% or DLSS Quality, High clouds, terrain and object LOD 100, and Low traffic; then tune the confirmed bottleneck.
What should I set in the Meta Quest software?
Quest 3 runs MSFS 2024 as a PC VR headset; the simulator does not run on the headset itself. Establish a clean PC-to-headset connection before changing graphics settings, otherwise network or encoding problems can look like poor simulator performance.
- Choose the connection: use a good USB cable while establishing your baseline. Air Link can work well, but the PC should be wired to the router and the headset should have a strong, uncongested local wireless connection.
- Select the matching OpenXR runtime: make Meta the active OpenXR runtime for Quest Link or Air Link. Virtual Desktop users should select its direct OpenXR option, such as VDXR where available. Avoid adding SteamVR as an extra compositor unless your configuration specifically requires it.
- Set 72 Hz first: this gives the PC the largest frame-time allowance and makes a stable half-rate 36 fps possible when reprojection is used.
- Leave headset resolution near its recommended position: do not maximise Quest resolution, MSFS Render Scaling and external supersampling together. That stacked supersampling is one of the most common causes of unexpectedly poor VR performance.
- Keep encoding conservative: begin with the default or dynamic bitrate. Raise it only after frame timing is stable; an excessive bitrate can cause latency, audio faults and head-turn judder without improving cockpit readability.
Our Quest 3 connection and OpenXR setup walkthrough covers Link, Air Link, Virtual Desktop and VR activation in more detail.
Which MSFS 2024 graphics settings should I use?
The following settings are a balanced Quest 3 baseline rather than a promise that every PC can hold the same frame rate.
| MSFS 2024 setting | Quest 3 starting value | When to change it |
|---|---|---|
| Anti-aliasing | TAA, or DLSS Quality on RTX cards | Use TAA for clearer cockpit text; use DLSS Quality when GPU-limited |
| Render Scaling | 90–100 with TAA | Reduce in 5–10% steps if GPU frame time is too high |
| Terrain Level of Detail | 100 | Reduce to about 80 when limited by the main thread, especially near cities |
| Objects Level of Detail | 100 | Reduce around detailed airports or dense urban scenery |
| Volumetric Clouds | High | Use Medium for heavy weather or a GPU-bound system |
| Texture Resolution | High | Use Medium if VRAM pressure causes pauses, texture swapping or instability |
| Anisotropic Filtering | 16x | Usually inexpensive; retain it for sharper runways and ground textures |
| Buildings, trees and grass | Medium or High | Reduce these before sacrificing cockpit resolution |
| Shadows and contact shadows | Medium | Lower when GPU-limited at complex airports |
| Ambient occlusion and reflections | Low or Medium | These are sensible cuts when more GPU headroom is required |
| Glass cockpit refresh rate | Medium | Lower it if an airliner cockpit is main-thread limited |
| AI, road, airport and ship traffic | Low; roughly 10–20 where sliders are used | Reduce first when busy airports stutter despite acceptable GPU timing |
| Motion blur | Off | Leave disabled for a cleaner VR image |
These values preserve the features that matter most inside Quest 3: readable instruments, stable head movement and useful terrain detail. Our broader MSFS VR settings reference explains the visual and performance cost of each option across different headsets.
Should Quest 3 use TAA or DLSS?
TAA is usually the better choice for cockpit clarity, while DLSS Quality is preferable when the GPU cannot meet the required frame time. TAA tends to keep labels and glass displays more stable, although it needs a higher native rendering load.
DLSS Quality can recover substantial GPU headroom on an NVIDIA RTX card, but small text, moving displays and distant details may look softer or leave temporal trails. Balanced and Performance modes should be fallback options rather than the starting point for Quest 3’s high-resolution panels.
DLSS does not fix a main-thread bottleneck. If lowering render scale or selecting DLSS barely changes performance, reduce terrain LOD, object LOD, traffic and glass-cockpit refresh rate instead.
Should I use 72 Hz, 80 Hz or 90 Hz?
Use 72 Hz unless the PC can sustain a higher refresh mode consistently. A lower, stable target generally feels better in a flight simulator than oscillating between native and reprojected frame rates.
- 72 Hz: the best general starting point, targeting either native 72 fps or a steady 36 fps with half-rate reprojection.
- 80 Hz: useful when the system can hold native 80 fps or a dependable 40 fps reprojection lock without cutting important visual settings.
- 90 Hz: choose this only with enough CPU, GPU and encoding headroom for native 90 fps or a stable 45 fps half-rate mode.
Reprojection can smooth scenery movement, but it may create distortion around propellers, wing edges and glass displays. Try the runtime’s automatic mode first. If it repeatedly switches modes or produces distracting artefacts, either lock a sustainable half rate where supported or disable it and tune for stable native delivery.
How do I tune the settings for my PC?
The correct adjustment depends on whether MSFS, the GPU, the headset encoder or the wireless connection is missing its target.
- Create a repeatable test: use the same aircraft, airport, weather and cockpit view. A complex airliner at a major airport is much heavier than a small aircraft over open countryside.
- Check the limiting component: use the simulator’s frame-time display rather than relying only on average fps. Native refresh requires about 13.9 ms at 72 Hz, 12.5 ms at 80 Hz and 11.1 ms at 90 Hz.
- Fix GPU limitation: reduce render scaling or use DLSS Quality, followed by clouds, shadows, ambient occlusion and reflections.
- Fix main-thread limitation: reduce terrain LOD, object LOD, traffic and glass-cockpit refresh rate. Changing Quest resolution will not solve this bottleneck.
- Fix VRAM pressure: lower texture resolution and avoid excessive headset supersampling. VRAM exhaustion often appears as intermittent pauses rather than a uniformly low frame rate.
- Change one group at a time: if MSFS Dynamic Settings are enabled, disable them while building the baseline so their automatic changes do not hide the result.
For hardware-specific diagnosis, use our CPU, GPU, VRAM and compositor optimisation guide.
Why is Quest 3 still blurry or stuttering?
Blurry instruments, compression blur and simulator stutter have different causes, so lowering every graphics option usually wastes image quality.
- Blurry cockpit labels: use TAA or DLSS Quality, increase MSFS render scale cautiously, and then raise the Quest PC render resolution if GPU headroom remains.
- Blocky distant scenery during head movement: suspect Link encoding or wireless bitrate rather than terrain LOD. Test with a cable and return bitrate controls to conservative values.
- Judder only inside the headset: verify the correct OpenXR runtime and remove unnecessary compositor layers. A smooth desktop mirror does not prove that headset delivery is healthy.
- Stutter at large airports: reduce traffic, terrain LOD, object LOD and glass refresh rate. This is commonly a main-thread problem.
- Pauses while new terrain loads: check VRAM, storage, network streaming and rolling-cache behaviour before sacrificing anti-aliasing quality.
If the frame rate appears adequate but head movement still skips or vibrates, follow our MSFS 2024 VR jitter and stutter diagnosis to separate simulator, compositor, network and tracking faults.