How do I optimise Microsoft Flight Simulator 2024 for VR?
To optimise Microsoft Flight Simulator 2024 for VR, establish a stable headset connection first, then tune for consistent frame time rather than maximum desktop FPS. Lower render scale, clouds and effects when GPU-limited; reduce terrain LOD, object LOD and traffic when the main thread is limiting performance, and watch VRAM use.
Do not begin by copying another simmer’s Ultra preset. Headset resolution, refresh rate, aircraft complexity, airport scenery and available VRAM can make the same settings perform very differently. If VR itself is not configured reliably, follow our headset and OpenXR setup procedure before attempting to optimise it.
Build a clean VR performance baseline
A controlled baseline shows whether Microsoft Flight Simulator 2024, the VR runtime or the headset connection is causing the problem.
- Update the relevant components. Install simulator and headset software updates, then use a known-stable graphics driver. Restart the PC after changing a driver or the active OpenXR runtime.
- Confirm the correct OpenXR runtime. Only one runtime should own the VR session. Avoid routing the headset through an additional compositor unless that is required by its connection method.
- Remove competing resolution changes. Put the headset or OpenXR resolution at its normal 100% value, if expressed as a percentage, and disable runtime-level upscaling while testing. Adjust one resolution control at a time so you know what caused the improvement.
- Load a repeatable test flight. Use a default aircraft, clear weather, low traffic and no third-party scenery or aircraft. Start at an ordinary airport, then repeat the test at a detailed hub or city before accepting the result.
- Measure frame time. Use the simulator’s performance display or the headset runtime’s timing overlay. Headset FPS alone can be misleading when reprojection is holding the output to a fixed fraction of the refresh rate.
A practical balanced baseline is 100% headset resolution, an in-simulator render scale around 80, Terrain LOD and Objects LOD around 100, Medium clouds and shadows, Low reflections, low traffic and texture resolution chosen to fit available VRAM. Treat this as a diagnostic starting point, not a universal final preset. Our hardware-tier starting settings for MSFS 2024 VR provide more specific profiles.
Which MSFS 2024 VR settings should I lower first?
Lower the setting tied to the active bottleneck; cutting every option to Low often produces a blurry cockpit without fixing a main-thread or headset-transport problem.
| Setting | Main limitation | When to lower it |
|---|---|---|
| Headset resolution and Render Scaling | GPU and VRAM | Lower these first when GPU frame time is high. Change only one of the two controls at a time. |
| Terrain Level of Detail | Main thread | Reduce it for dense cities, detailed airports and low-altitude flying when render-scale changes barely affect performance. |
| Objects Level of Detail | CPU, GPU and VRAM | Lower it when complex airports or urban areas cause a marked slowdown or memory pressure. |
| Volumetric Clouds | GPU | Reduce from Ultra or High during heavy weather. Medium is a sensible VR baseline. |
| Texture Resolution | VRAM | Lower it when performance deteriorates after loading detailed aircraft or scenery, especially if hitching increases over time. |
| Shadows, reflections and ambient occlusion | GPU | Reduce these before sacrificing cockpit readability. Reflections and shadow quality are common candidates for Low or Medium. |
| Aircraft, road and airport traffic | Main thread | Lower traffic at large hubs or when the MainThread time is dominant. |
| Glass-cockpit refresh rate | Main thread | Reduce it, where available, when a complex avionics aircraft is smooth externally but slow from the cockpit. |
Anisotropic filtering is normally inexpensive and helps preserve runway and ground-texture detail at an angle, so it should not be the first setting reduced. Make sure changes are being applied to the active VR graphics profile rather than only to the flat-screen profile.
How do I tell whether VR is CPU- or GPU-limited?
Use frame-time data and change one relevant setting: render scale exposes a GPU limit, while Terrain LOD, traffic and cockpit systems expose a main-thread limit.
- GPU-limited: GPU frame time is highest, and reducing render scale, clouds or shadows produces an immediate improvement.
- Main-thread limited: lowering render scale has little effect, but reducing Terrain LOD, Objects LOD, traffic or avionics workload helps.
- VRAM-limited: the flight may begin smoothly, then develop severe hitching after loading detailed textures, changing views or entering a complex area. Reduce texture resolution and object detail, and close other GPU-accelerated applications.
- Compositor or connection-limited: simulator frame time looks stable while the headset reports dropped frames. Check the OpenXR runtime, USB or wireless connection, headset refresh rate and competing overlays.
If the limiting component is still unclear, use our CPU, GPU, VRAM and scenery-streaming diagnostic before changing more VR settings.
A repeatable VR tuning order
The quickest tuning method is to solve one bottleneck at a time and retest the same flight after each change.
- Disable reprojection temporarily. This reveals the simulator’s real frame time rather than a compositor-controlled output rate.
- Reduce GPU load. Lower in-simulator render scale in small steps, followed by clouds, shadows, reflections and ambient occlusion.
- Reduce main-thread load. Cut Terrain LOD, Objects LOD and traffic. Reduce glass-cockpit refresh rate if a complex airliner is the main problem.
- Restore cockpit clarity. Increase render scale until instruments remain readable, but spend spare performance on resolution before reflections or elaborate shadows.
- Choose the final refresh and reprojection mode. Select a combination the PC can hold consistently rather than one that continually switches between native and reprojected frames.
- Stress-test the result. Repeat the flight in poor weather, at a detailed airport and in the aircraft you normally use. Leave enough headroom for camera movement and scenery loading.
Should I use TAA, DLSS or motion reprojection?
Use TAA when native image clarity matters and the GPU has enough headroom; use DLSS Quality when an RTX GPU needs lower frame time, and use motion reprojection only when the simulator can sustain a stable fraction of the headset refresh rate.
| Option | Best use | Trade-off |
|---|---|---|
| TAA | Readable cockpit displays and stable fine detail | Higher GPU cost at demanding headset resolutions |
| DLSS Quality | RTX systems that are GPU-limited | May soften glass-cockpit text or introduce ghosting; try Quality before more aggressive modes |
| DLAA | Systems with substantial GPU headroom | Good anti-aliasing quality but little performance relief |
| FSR, when offered | Compatible non-RTX hardware or extra GPU relief | Inspect gauges, power lines and distant buildings for shimmer or softness |
For motion reprojection, select the headset refresh rate first. A 90 Hz headset usually needs a steady 45 rendered frames per second for half-rate reprojection; 80 Hz needs 40, and 72 Hz needs 36. Runtime capabilities differ, so use the fixed fraction your headset supports and can maintain.
Reprojection can produce artefacts around propellers, rotors, wing edges and moving glass-cockpit content. If those are distracting, a lower native headset refresh rate may feel better than half-rate reprojection. Desktop frame-generation settings do not replace the VR compositor’s reprojection and should be left off while diagnosing VR performance.
Why does MSFS 2024 VR still stutter?
Persistent VR stutter usually comes from frame-time spikes, scenery streaming, VRAM exhaustion, add-ons or headset transport rather than an average frame rate that is simply too low.
- Shader compilation: the first flight after a simulator or graphics-driver update may hitch as shaders are rebuilt. Retest the same aircraft and location before changing the preset.
- Scenery streaming: temporarily disable online scenery features to compare results. If the stutter disappears, inspect connection stability and rolling-cache behaviour rather than lowering every graphics option. Rebuild the cache only when corruption is suspected; repeatedly deleting it forces data to be fetched again.
- VRAM pressure: lower texture resolution and Objects LOD, then restart the flight. Detailed airports, high-resolution aircraft textures and background GPU applications can combine to exceed the usable memory budget.
- Main-thread spikes: reduce AI traffic, airport activity, Terrain LOD and CPU-heavy aircraft systems. A faster GPU will not solve a MainThread limit.
- Add-ons and overlays: repeat the test without third-party aircraft, scenery, recording utilities, monitoring overlays or injector layers. Reintroduce them individually.
- Headset transport: test a wired connection if a wireless headset shows dropped frames despite stable simulator timing. For wired headsets, try a suitable direct motherboard port and check the cable before altering image quality.
Match the profile to the type of flying
The best final settings depend on where and what you fly, so protect the resources that matter most for that workload.
- Airliners at detailed hubs: preserve instrument readability, but reduce Terrain LOD, Objects LOD, traffic, airport activity and glass-cockpit refresh rate.
- Low-level VFR: retain as much Terrain LOD as the main thread allows, then save GPU time through clouds, shadows and moderate render scaling.
- Helicopters and fast low-level aircraft: prioritise stable cadence and low latency. Rotor artefacts can make native frames at a lower refresh rate preferable to reprojection.
If render scale must be reduced until cockpit text is unreadable, the GPU or its VRAM is probably the practical limit. Before upgrading, compare how GPU class, VRAM and headset resolution interact in flight-simulator VR; if MainThread timing remains dominant, a graphics-card upgrade alone will provide limited improvement.