How do I fix shimmering and washed-out visuals in MSFS VR?

Microsoft Flight Simulator VR is a PC feature in both MSFS 2020 and MSFS 2024; Xbox consoles do not support it. VR was introduced on 22 December 2020. To fix shimmering or washed-out visuals, compare the headset with the desktop mirror, reset the VR pipeline, then retune anti-aliasing, render scale and colour settings.

An Xbox player cannot enable MSFS VR by connecting a headset or changing a graphics option. MSFS 2024 also launched on PS5 and PS5 Pro, with PSVR2 support announced through a free 2026 update; the OpenXR and PC-runtime procedures below do not apply to that console path. MSFS 2020 was never released on PlayStation.

What is this visual effect called?

The correct name depends on what the image is doing. For readers asking “¿cómo se llama ese efecto?”, use these distinctions when searching settings or describing the fault:

• Aliasing or shimmer: thin aircraft edges, trees, fences, roofs or runway markings sparkle or crawl, even when the view is nearly still.
• Temporal shimmer: fine detail changes from frame to frame, often because resolution is too low or temporal upscaling lacks enough information.
• Reprojection artefacts: objects wobble, double or develop trails specifically while the head or aircraft is moving.
• Washed-out colour or raised blacks: the whole image has weak contrast, pale colours or grey areas that should be black.
• Bloom or lens glare: bright lights produce halos or haze without changing the underlying colour range.

Compare the headset, desktop mirror and scene first

The location of the fault tells you which part of the VR pipeline to change. Do this before moving several graphics sliders.

1. Hold the view still. Decide whether edges sparkle while stationary or distort only during head movement.
2. Compare outputs. Look at the headset and desktop mirror, including menus as well as the rendered cockpit.
3. Change the scene. Compare day and night, a default aircraft and a default airport using standard weather.
4. Check both eyes. A one-eye fault usually comes from the compositor, driver or an injected OpenXR layer rather than anti-aliasing.

The desktop mirror is rendered before some headset processing and does not reproduce the lenses, panel black level or every compositor adjustment. It is still a valuable dividing line: if the mirror is normal, changing MSFS exposure to compensate for a headset-only fault usually makes matters worse.

Use the MSFS 2024 VR graphics menu, not the desktop profile

In MSFS 2024 Sim Update 5, open Settings, select Graphics and edit the dedicated VR graphics page or profile after the headset has initialised. The ordinary PC graphics profile does not reliably control the image rendered in VR.

MSFS 2020 uses the same principle: open its Graphics options and select the VR Mode page while VR is active. TAA, DLAA, DLSS, render scale, HDR diagnosis and reset procedures below apply to both simulators, although the menu layout and available options can differ.

Runtime resolution and the in-simulator render scale compound one another. Lowering both can produce a deceptively smooth but unstable image in which cockpit lettering, vegetation and distant buildings no longer have enough pixels to remain steady.

How should I reset the VR graphics profile?

Reset the dedicated VR profile and external processing together, then rebuild from a neutral baseline.

1. Record useful settings. Take screenshots of the VR page before resetting it.
2. Reset the VR page. Use the simulator’s reset-to-defaults control while viewing the VR graphics profile, not just the PC profile.
3. Remove external overrides. Reset per-game graphics-driver changes, OpenXR post-processing and headset colour or sharpening overrides.
4. Restart the complete chain. Exit MSFS, restart the headset software or runtime, then launch the simulator again.
5. Use clean content. Test a default aircraft, airport and weather preset with visual, lighting and cockpit modifications removed temporarily from the Community folder.

Once the image is stable, our practical MSFS 2024 VR performance baseline explains which clouds, LOD, traffic and shadow settings to reduce without sacrificing cockpit clarity.

Which anti-aliasing mode fixes shimmering in MSFS VR?

TAA is the safest diagnostic starting point because it usually keeps scenery and cockpit edges stable. DLAA can produce a cleaner image at the target resolution when supported hardware has enough performance headroom.

If only glass-cockpit text shimmers or smears, switch from DLSS to TAA or DLAA before reducing scenery quality. If trees, roofs, aircraft outlines and runway markings sparkle, increase VR render resolution gradually and confirm that driver or runtime sharpening is not stacked on top of MSFS sharpening.

Anisotropic filtering improves runway and ground textures viewed at an angle, but it does not remove geometric edge aliasing. Very high Terrain or Objects Level of Detail can expose more distant sub-pixel detail and make a marginal resolution look noisier. Contact shadows and screen-space reflections can also flicker, so turn each off separately rather than lowering every setting at once.

For shimmer centred on aircraft edges and fine geometry, use our deeper anti-aliasing and render-scale checks for jagged detail.

Why does MSFS VR look washed out only inside the headset?

If the desktop mirror looks normal but the headset is pale or over-bright, the fault is usually downstream of MSFS. Reset brightness, contrast, gamma, colour-range and enhancement controls in the headset or streaming software instead of darkening the simulator.

Check the headset’s own menus. If those also have raised blacks or clipped whites, MSFS is not the source. Monitor controls and desktop graphics-driver colour adjustments generally affect the monitor rather than the headset panel.

Test Windows and simulator HDR off, but treat this as diagnosis rather than a universal performance tweak. Desktop HDR does not necessarily mean that a headset is receiving HDR output. A faulty HDR hand-off may alter the mirror or a particular streaming path, while most headset colour is still controlled by its compositor.

Dirty lenses, fogging and poor headset positioning can mimic washed-out colour. Reposition the headset in its visual sweet spot, set the correct interpupillary distance where supported and clean the lenses only by the manufacturer-approved method. Optical haze or glare that moves with the eye rather than the simulated scene will not appear in the desktop mirror.

Virtual Desktop and VDXR troubleshooting

VDXR is Virtual Desktop’s OpenXR runtime. Virtual Desktop still handles the wireless video stream, while VDXR supplies the OpenXR path used by MSFS instead of routing the simulator through SteamVR.

Use this clean-test order so codec, colour, network and OpenXR changes do not become mixed together:

1. Start with a repeatable scene. Use a default aircraft in clear daylight and record the existing Virtual Desktop settings.
2. Disable video and colour enhancements. Turn off optional sharpening, colour vibrance, expanded colour-range and headset-side upscaling or enhancement features. Their names can change between Virtual Desktop releases.
3. Remove OpenXR processing. Disable post-processing, sunglasses, contrast, gamma, sharpening, performance overlays and other API layers. Restart Virtual Desktop, the headset and MSFS.
4. Restore codec and colour choices. Return forced codec, bit depth and colour-range selections to Auto or their defaults. A limited/full-range mismatch can raise blacks or clip dark cockpit detail.
5. Check bitrate sensibly. A bitrate that is too low causes blocks, banding and loss of fine detail; one that exceeds a stable wireless link causes dropped frames and stutter. Bitrate alone is less likely to cause uniform white clipping.
6. Compare another transport. Where the headset supports it, compare VDXR wireless streaming with a USB headset connection or another OpenXR runtime. Keep the MSFS VR profile unchanged during this comparison.

If the fault exists only through Virtual Desktop and VDXR, concentrate on its stream, colour range and overlays. If it remains over USB and through another runtime, return to MSFS, the graphics driver or the headset display settings.

Check the correct OpenXR runtime for your headset

MSFS should reach the headset through one intended OpenXR runtime, without unnecessary overlays or a second compositor being launched by mistake.

Why might an HP Reverb stop working after a Windows update?

HP Reverb headsets depend on Windows Mixed Reality. WMR was removed from Windows 11 24H2 and later, so a Reverb may be unusable on those Windows releases even if SteamVR and OpenXR applications remain installed.

SteamVR does not supply the missing WMR device stack. Resetting MSFS, reinstalling an OpenXR overlay or changing anti-aliasing cannot correct that platform-level removal. The practical options are an operating-system installation that still supports WMR, with its support and security implications understood, or different headset hardware.

If VR fails to initialise rather than merely looking wrong, follow our full OpenXR runtime, headset-service and Community-folder checks.

Why is MSFS VR grey or over-bright at night?

Grey blacks or glaring lights at night can come from simulated exposure and cockpit lighting, but menus and loading screens reveal a true headset colour fault.

• Eye adaptation: a dark cockpit beside bright runway, apron or city lights can make the exterior appear overexposed as simulated exposure adjusts. Compare outside and cockpit views in a default aircraft.
• Cockpit and instrument lighting: floodlights or displays at maximum brightness flatten perceived contrast and reflect from cockpit surfaces. Reduce them with the aircraft’s own dimmers.
• Bloom: creates a soft halo around lamps and illuminated instruments. Turn bloom off to test it; this does not repair raised black levels.
• Lens glare: halos or rays that shift with eye position are optical and usually absent from the desktop mirror.
• Colour-space or black-level fault: menus, loading backgrounds and unlit areas remain grey in every aircraft and at both day and night. Reset the headset or streaming colour range rather than changing weather or exposure.

Headset panel technology also sets the lowest black level the device can display. A uniform dark grey floor can be normal for some panels, while sudden crushing, clipping or a change after selecting a codec or colour option points to configuration.

Why does shimmer appear only when I move my head?

Shimmer that becomes doubled edges, trails or wobbling geometry during head movement normally comes from motion reprojection or uneven frame delivery, not ordinary anti-aliasing.

Turn reprojection off briefly. If the static image remains clean and the distortion returns only when reprojection is re-enabled, lower costly settings such as clouds, shadows, traffic or resolution until frame timing stabilises. Reprojection artefacts around propellers, window frames and moving aircraft can remain visible even when the underlying image is sharp.

Persistent movement-related problems need the separate checks for VR flicker, ghosting, freezes and frame timing rather than more colour adjustment.

Should I clear caches or reinstall MSFS?

Reinstallation should be the last step because shimmering and washed-out VR colour usually come from active graphics settings, runtime layers or headset processing.

• Rolling cache: clear it only when streamed terrain or photogrammetry is visibly corrupt. It does not normally control anti-aliasing, exposure or headset colour.
• Shader cache: rebuild it if the problem began after a simulator or graphics-driver change and affects every aircraft and location. Temporary stuttering is expected while shaders are recreated.
• Add-ons: test with the Community folder empty and disable relevant visual packages managed through the simulator.
• Graphics profiles: reset the simulator’s VR profile, active OpenXR layers and per-game driver profile before reinstalling the simulator.