Skip to content

What are the best VR settings for MSFS 2020 with Quest 3?

Ian Stephens
  • 6 min read

In short

Best Quest 3 VR settings for MSFS 2020, with starting values for render scale, TAA or DLSS, refresh rate, traffic, blur and stutters.

In this answer
  1. Recommended Quest 3 settings for MSFS 2020
  2. Should Quest 3 use 72, 80 or 90 Hz in MSFS 2020?
  3. Is TAA or DLSS better for Quest 3 cockpit clarity?
  4. How should the preset be tuned for your PC?
  5. Why does MSFS 2020 still look blurry or stutter?

For Meta Quest 3 in Microsoft Flight Simulator 2020, start at 72 Hz, 100% in-sim VR render scale, TAA, High textures and clouds, 100 Terrain and Object LOD, Medium glass-cockpit refresh, and low traffic. Use DX11 first; lower render scale or clouds for a GPU limit, and LOD or traffic for a CPU limit.

Quest 3 VR requires the PC version of MSFS 2020; Xbox does not support VR. Connect through Quest Link, Air Link or Virtual Desktop, and complete the Quest 3 connection and OpenXR setup steps before tuning graphics.

This balanced preset targets readable instruments and stable frame timing without wasting performance on settings that barely improve the headset image. MSFS has a separate VR graphics profile, so make these changes while editing its VR settings rather than the normal flat-screen profile.

SettingRecommended starting valueAdjustment
Quest refresh rate72 HzTry 80 Hz only after the baseline is stable
Meta PC render resolutionAround 1.0xRaise gradually on faster GPUs; the displayed pixel resolution varies with refresh rate
OpenXR runtimeMeta for Link or Air Link; VDXR for Virtual DesktopUse one runtime path and avoid adding SteamVR unnecessarily
DirectX versionDX11Test DX12 separately; keep it only if frame timing is genuinely better on your PC
Anti-aliasingTAAUse DLSS Quality on a supported RTX GPU when more performance is needed
VR render scaling100Reduce to 80-90 if GPU-limited
Terrain Level of Detail100Lower at busy airports when MainThread-limited
Objects Level of Detail100Reduce to 80 if dense scenery causes CPU stutters
Texture ResolutionHighUse Ultra only with ample VRAM and no paging stutters
Anisotropic Filtering16xKeep this high; its performance cost is usually small
Volumetric CloudsHighMedium is one of the most effective GPU-saving changes
Offscreen Terrain Pre-CachingHighUse Ultra if VRAM allows and head-turning causes scenery pop-in
Shadow Maps1024Lower before sacrificing cockpit resolution
Ambient OcclusionMediumSet Low or Off when GPU-limited
Contact ShadowsMediumLow is acceptable in demanding airliners
ReflectionsLowHigher values provide little benefit inside most cockpits
Water WavesMediumUse Low for coastal cities or seaplane operations if needed
Windshield EffectsHighReduce during severe-weather flying if GPU load spikes
Glass Cockpit Refresh RateMediumLow helps CPU-limited airliners; High suits simpler aircraft
TrafficLowStart with AI or live traffic off, then enable it and keep ground, road and ship density low

Do not apply supersampling in several places at once. Establish a baseline with the Quest resolution near 1.0x, MSFS render scaling at 100 and any third-party OpenXR resolution override disabled. On a stronger GPU, raise the Meta render resolution gradually while leaving the in-sim scale at 100. Our RTX 4070-class VR preset provides a useful reference for that performance tier.

Should Quest 3 use 72, 80 or 90 Hz in MSFS 2020?

Use 72 Hz for the best balance of clarity and attainable performance. It gives the simulator more time to render each frame and allows asynchronous spacewarp to produce 72 Hz from a stable 36 fps when necessary.

  • 72 Hz: Best default for complex aircraft, large airports and mid-range hardware.
  • 80 Hz: A good upgrade if the PC can sustain either native 80 fps or a steady half-rate 40 fps.
  • 90 Hz: Smoother head movement, but demanding; half-rate operation requires a stable 45 fps.

Stable cadence matters more than the highest reported frame rate. Automatic spacewarp can feel uneven when it repeatedly switches between native and half-rate operation. A fixed half-rate mode can improve consistency, but propellers, wing edges and moving cockpit displays may show visible artefacts. Disable it if those distortions are more distracting than ordinary judder.

Is TAA or DLSS better for Quest 3 cockpit clarity?

TAA at 100 render scale usually produces the clearest glass-cockpit text in MSFS 2020. DLSS Quality improves performance on RTX cards, but small digits and moving displays may look softer or leave trails.

Choose DLSS Quality when the simulator is GPU-limited and lowering clouds is insufficient. Avoid DLSS Performance for normal Quest 3 flying because its lower internal resolution makes cockpit labels and distant scenery noticeably less defined. For the available modes and their trade-offs, see our detailed MSFS 2020 DLSS guidance.

If TAA still looks blurred, check the Quest application resolution before pushing MSFS render scaling above 100. Increasing both multiplies the workload quickly. Frame generation is not a substitute for VR frame rate or spacewarp because the headset still needs consistently timed rendered frames.

How should the preset be tuned for your PC?

The correct adjustment depends on whether MSFS reports a GPU or MainThread bottleneck. Use the simulator's built-in frame-rate display after enabling Developer Mode, test in a repeatable situation, and change one setting group at a time.

  1. Build a clean baseline. Use 72 Hz, TAA at 100, low traffic and the table settings. Disable extra supersampling and close unnecessary overlays.
  2. Test a demanding flight. Use the aircraft and airport you normally fly rather than an empty rural runway.
  3. Fix a GPU limit. Lower volumetric clouds first, then render scale, shadows, ambient occlusion and reflections. Keep textures High unless VRAM exhaustion is causing pauses.
  4. Fix a MainThread limit. Reduce Terrain LOD, Object LOD, traffic and glass-cockpit refresh rate. Lowering render scale will not solve a CPU bottleneck.
  5. Raise clarity carefully. Once frame timing is stable, increase the Meta render resolution in small steps and repeat the same test.

Our broader MSFS VR bottleneck guide covers the same diagnosis across other headsets and hardware levels.

Why does MSFS 2020 still look blurry or stutter?

Persistent blur or stutter usually comes from resolution being reduced in more than one place, wireless compression, an incorrect OpenXR runtime, or a CPU-heavy airport rather than one bad graphics setting.

  • Blurry instruments: Return to TAA and 100 render scale, avoid aggressive DLSS modes, and confirm that the Meta resolution has not been set unusually low.
  • Clear cockpit but smeared scenery: This often indicates Link compression. For Air Link, connect the PC to the router by Ethernet and keep the headset near a dedicated 5 GHz or 6 GHz access point. Compare against a cable before raising bitrate.
  • Wired Link still looks compressed: Confirm the connection is operating as USB 3. Leave bitrate on automatic first, then raise it gradually; an excessive fixed bitrate can cause audio breakup and frame drops.
  • Stutters at detailed airports: Reduce Terrain LOD, ground traffic and glass-cockpit refresh rate. These are common MainThread loads.
  • Stutters while turning your head: Raise Offscreen Terrain Pre-Caching if VRAM permits. If VRAM is already full, lower textures instead.
  • VR fails to start or opens through the wrong software: Make the Meta runtime active for Link or Air Link, or use VDXR for Virtual Desktop. Do not chain multiple OpenXR and SteamVR layers without a specific need.

We recommend solving network and runtime problems before reducing graphics. A poor wireless link can look like inadequate GPU performance, but lowering clouds or LOD will not repair dropped network frames or compression artefacts.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members