How do I fix MSFS VR flickering, ghosting and freezes?
To fix flickering, ghosting and freezing in Microsoft Flight Simulator VR, first disable motion reprojection and temporal upscaling as a test, then stabilise CPU and GPU frame times. Check the active OpenXR runtime, remove overlays and add-ons, lower VRAM-heavy settings, and distinguish a simulator stall from a headset or tracking fault.
These checks apply to PC VR in both MSFS 2020 and MSFS 2024. Menu wording differs between simulator and headset versions; OpenXR, graphics-driver and Community-folder instructions are PC-specific.
What causes flickering, ghosting and freezing in MSFS VR?
The pattern of the fault usually identifies its source more reliably than an FPS counter.
| Symptom | Likely cause | Useful confirming test |
|---|---|---|
| Double images around wings, buildings or cockpit frames when moving your head | Motion reprojection, motion smoothing or ASW | Disable reprojection temporarily and repeat the same movement |
| Trails behind digits, labels or moving controls | DLSS or another temporal reconstruction method | Switch to TAA without changing resolution |
| Shimmering gauges, fences and distant buildings | Insufficient render resolution or aggressive upscaling | Increase one resolution control slightly, provided GPU headroom exists |
| Flashing surfaces at one airport only | Overlapping scenery or z-fighting | Test with Community and optional scenery packages disabled |
| Headset freezes but the desktop mirror continues moving | OpenXR compositor, tracking, cable, USB or wireless-link fault | Check another VR application and watch whether MSFS still runs on the monitor |
| Headset and desktop view pause together | Main-thread spike, VRAM exhaustion, scenery streaming or an add-on | Use a default aircraft at a modest airport with traffic and add-ons disabled |
How do I isolate the fault without guessing?
Build a clean, repeatable test and change only one variable at a time. Changing the headset resolution, render scale, reprojection mode and anti-aliasing together makes the result impossible to interpret.
- Create a repeatable test. Load a default aircraft at a relatively simple airport with clear weather. Use the same cockpit view and head movement after every change.
- Watch the desktop mirror. An effect visible only inside the headset normally comes from reprojection, the compositor or the headset connection. A pause visible on the monitor as well points back to MSFS, its add-ons or the PC.
- Remove injection layers. Close performance overlays, recording software and VR utilities that add an OpenXR layer. Disable Community add-ons and optional third-party content; use Safe Mode if MSFS offers it after an abnormal shutdown.
- Test reprojection and upscaling separately. Turn motion reprojection off first. Then compare the existing anti-aliasing mode with TAA. Do not alter render resolution during either comparison.
- Reduce the correct workload. Lower traffic and Terrain/Object Level of Detail for a main-thread limit. Reduce render resolution, clouds, shadows, reflections and ambient occlusion for a GPU limit. Lower textures and high-resolution scenery if VRAM is full.
- Check location-specific content. If only one airport flickers or freezes, disable duplicate airport packages and nearby scenery. Temporarily test without live traffic and streamed scenery features; delete and rebuild the rolling cache through the simulator if it is enabled.
- Verify the VR runtime. Make the headset manufacturer's supported OpenXR runtime active. Do not force an additional SteamVR path unless that headset requires it.
- Restore features individually. Add traffic, scenery, utilities and reprojection back one at a time. The first change that restores the fault identifies the useful troubleshooting branch.
Why does motion reprojection cause ghosting?
Motion reprojection creates synthetic frames when MSFS cannot render at the headset's full refresh rate. It can make head movement feel smoother, but guessed pixels often produce doubled wing edges, warped propellers and trails around cockpit text.
Reprojection works best when the real frame rate holds a stable fraction of the headset refresh rate. If frame time repeatedly crosses that threshold, the runtime can switch states and create visible pulsing or flicker. Lower the limiting settings until the cadence is stable, use a fixed supported mode if the runtime provides one, or leave reprojection disabled if its artefacts are more distracting than the judder.
DLSS ghosting is a separate problem because it is produced inside the rendered image. It may therefore appear in the desktop mirror as well. TAA generally gives cleaner glass-cockpit text and fewer trails, but costs more GPU time; a quality-focused DLSS mode is the compromise when TAA cannot maintain acceptable frame times.
Which MSFS VR settings should I change first?
Change settings according to the bottleneck rather than applying a generic low preset.
- GPU-limited: reduce the headset's per-application resolution or the in-sim VR render scale, then clouds, shadows, reflections and ambient occlusion.
- Main-thread limited: reduce Terrain Level of Detail, Object Level of Detail, AI or live traffic, ground aircraft and other vehicle traffic. Cockpit display refresh can also matter where that option is available.
- VRAM-limited: lower texture resolution, render resolution and demanding scenery. Close browsers and hardware-accelerated background applications that consume GPU memory.
- Streaming stalls: test a less demanding airport, disable live traffic and streamed scenery features temporarily, and check the connection rather than reducing every graphics option.
A mistake we see constantly is increasing both the headset resolution and MSFS render scale. Those controls multiply the workload. Leave one at its default while tuning the other. MSFS 2024 users can follow our GPU, CPU, VRAM and compositor diagnosis for VR; MSFS 2020 users have a separate OpenXR and render-scale tuning sequence.
Headset, runtime and connection faults
If the desktop view keeps running while the headset blacks out, loses tracking or freezes, graphics settings inside MSFS are unlikely to be the primary fault. Restart the headset software and OpenXR runtime, check the headset cable or wireless link, avoid unpowered USB hubs, and test another VR application.
Update the headset software and use a stable graphics driver. If the problem began immediately after a driver update, reverting to the previous stable driver is a better diagnostic than repeatedly changing MSFS settings. Remove GPU or CPU overclocks and undervolts as well; a system that survives flat-screen flying can still fail under the combined VR and compositor load.
Hard freezes and simulator-wide pauses
When MSFS, its desktop window and audio all stop together, concentrate on add-ons, memory pressure, cache corruption, drivers and hardware stability. Start with an empty Community folder, a default aircraft and reduced textures, then restore content in small groups.
Short pauses that recover are usually frame-time or streaming spikes; our MSFS 2024 frame-time and stutter checks cover traffic, scenery streaming, overlays and caches. If the freeze ends in a crash to desktop or requires terminating the simulator, follow the broader MSFS crash and lock-up isolation process instead.