Best VR settings for Microsoft Flight Simulator 2024?
Find the best VR settings for Microsoft Flight Simulator 2024, with clear starting values for sharper cockpits, steady frame times and less stutter.
For the best Microsoft Flight Simulator 2024 VR balance, start at 100% OpenXR resolution, then use either 80–100% in-sim render scaling with TAA or DLSS Quality on an RTX card. Set Terrain and Object LOD to 100, clouds to High, traffic low, motion blur off, and enable reprojection only if it stays stable.
Recommended MSFS 2024 VR settings
This preset is a dependable PC VR starting point, not a universal maximum-quality configuration. Headset resolution, aircraft complexity, scenery, weather and CPU performance all affect which setting becomes the limit.
| Setting | Recommended starting value | When to change it |
|---|---|---|
| Headset/OpenXR resolution | 100% or the runtime default | Leave this fixed while tuning the simulator. |
| Anti-aliasing and scaling | TAA at 80–100%, or DLSS Quality on RTX hardware | Use TAA for clearer instruments; lower the scale or use DLSS when GPU-limited. |
| Terrain Level of Detail | 100 | Lower towards 70–80 when limited by the MainThread at large airports. |
| Objects Level of Detail | 100 | Lower it when dense airport buildings or city scenery cause CPU spikes. |
| Volumetric Clouds | High | Use Medium if bad weather causes a large GPU frame-time increase. |
| Texture Resolution | High | Choose Medium if VRAM pressure causes hitching or degraded textures. |
| Anisotropic Filtering | 16x | Normally leave it here; its performance cost is modest on modern GPUs. |
| Buildings and Trees | High | Use Medium on lower-end systems or in dense urban areas. |
| Grass and Bushes | Medium | Raise it only if low-level flying is important and GPU headroom remains. |
| Shadow Maps and Terrain Shadows | Medium | Lower shadows before sacrificing cockpit resolution. |
| Ambient Occlusion, Contact Shadows and Reflections | Low | These can be raised after resolution, clouds and frame pacing are stable. |
| Off Screen Terrain Pre-Caching | High | Try Ultra if there is spare VRAM and scenery appears while turning your head. |
| AI, live and road traffic | Off while testing; Low afterwards | Increase gradually because traffic can make the simulation MainThread-limited. |
| Motion Blur, Depth of Field and V-Sync | Off | Desktop V-Sync does not control the headset refresh cycle. |
These values apply to PC VR. Console builds do not expose the same OpenXR runtime, resolution overrides and PC graphics controls.
Set up OpenXR before changing graphics settings
Microsoft Flight Simulator 2024 should use one correctly selected OpenXR runtime with no accidental stack of resolution overrides. Start with the runtime resolution at 100%, disable additional supersampling, and make most resolution changes inside the simulator.
A mistake we see constantly is combining headset supersampling, an OpenXR override and an increased in-sim render scale. The resulting GPU load is difficult to diagnose. Our OpenXR runtime and resolution setup walkthrough explains how to select the correct runtime and avoid competing scale controls.
Should I use DLSS or TAA in MSFS 2024 VR?
Use DLSS Quality when an RTX GPU needs more performance, but choose TAA when cockpit text and moving displays must remain as clear as possible.
- DLSS Quality: Usually the best performance-quality option on RTX cards. It can soften small labels and produce ghosting on glass displays, propellers and fast-moving edges.
- TAA: Produces more stable cockpit lettering at a high render scale, but costs more GPU time. Start around 80% and increase in small steps.
- FSR: A useful alternative when DLSS is unavailable and TAA cannot meet the target frame rate. Inspect avionics text carefully because aggressive performance modes can look soft in VR.
Sharpening can restore edge contrast, but it cannot recover detail lost through an excessively low render resolution. Too much sharpening creates halos and shimmering around instruments.
Should motion reprojection be on or off?
Leave motion reprojection off when the computer can sustain the headset’s native refresh rate; otherwise use it only at a stable half- or third-rate target.
For example, a 90 Hz headset commonly needs a steady 45 frames per second for half-rate reprojection, while an 80 Hz headset needs 40. A fluctuating frame rate that repeatedly crosses the reprojection threshold often feels worse than a lower but locked rate.
Reprojection suits airliner flying, where head movement is controlled and the outside scene moves relatively slowly. Native rendering is often preferable for helicopters, aerobatics and low-level flying because reprojection can distort propeller discs, glass displays, wing edges and nearby buildings.
How do I tune VR settings for my PC?
The correct tuning order is resolution first, GPU effects second, CPU-heavy detail third and traffic last. Changing everything together hides the actual bottleneck.
- Create a repeatable test. Use the same aircraft, runway, weather and cockpit view at a demanding airport. Do not tune with an empty rural flight if large hubs are part of normal use.
- Choose the refresh target. Decide whether the goal is native refresh or a stable reprojection ratio. Remove unrelated frame caps while testing.
- Find the GPU limit. Adjust TAA render scale or DLSS mode, then clouds, shadows, ambient occlusion and reflections. If reducing resolution improves frame time, the GPU was the constraint.
- Find the CPU limit. If lower resolution changes little, reduce Terrain LOD, Object LOD and airport or vehicle activity. A MainThread limit cannot be fixed by making the image blurrier.
- Add traffic gradually. Restore live, AI, multiplayer and road traffic one category at a time, then test poor weather and a complex glass-cockpit aircraft.
For a fuller bottleneck-first method, use our guide to identifying CPU, GPU, VRAM and compositor limits.
Why does VR stutter even when the FPS looks acceptable?
Acceptable average FPS can still feel poor when individual frame times are uneven. Watch for a repeating cadence rather than relying only on the displayed average.
- Stutter during head turns: Raise Off Screen Terrain Pre-Caching if memory permits, and check that tracking cameras have suitable lighting.
- Hitching that worsens at detailed airports: VRAM may be exhausted. Lower Texture Resolution, render resolution and pre-caching before reducing every visual setting; our VRAM reduction priorities show which controls matter most.
- Regular double images or rhythmic judder: The frame rate is probably crossing a reprojection threshold, or two frame caps are competing.
- Exterior judder while the cockpit remains responsive: Reduce Terrain LOD, Object LOD and traffic because this usually points to a MainThread limit.
- Blur or pauses on a streamed headset: Test the USB or wireless link separately. Encoding and network problems cannot be repaired with MSFS cloud or shadow settings.
Persistent pacing, tracking and reprojection problems need a different diagnosis from low average FPS. Our VR jitter and stuttering checklist separates those causes.
Which settings should change for different aircraft?
Complex airliners need more CPU margin, while helicopters and low-level aircraft benefit most from low latency and native frames.
- Airliners at major hubs: Keep traffic low, use Terrain and Object LOD around 80–100, and prefer DLSS Quality if clouds and cockpit displays overload the GPU.
- General aviation: Spend spare performance on Terrain LOD, clouds and cockpit clarity rather than airport traffic.
- Helicopters and low-level flying: Prioritise native frame rate, reduce shadows or clouds if necessary, and disable reprojection when its visual distortions become distracting.
The best preset is the one that leaves enough frame-time margin for turns, weather changes and arrival at a detailed airport. A sharper image that repeatedly misses its refresh target is rarely the better VR experience.