How do I fix shimmering and washed-out visuals in MSFS VR?
To fix shimmering or washed-out visuals in Microsoft Flight Simulator VR, reset headset/OpenXR colour overrides, test HDR off, then use TAA or DLAA at a sensible render resolution with little or no extra sharpening. Compare the headset with the desktop mirror first: over-bright colour and edge shimmer come from different stages of the VR pipeline.
Find where the visual fault is introduced
The quickest diagnosis is to compare the headset image, desktop mirror and different parts of the same scene.
| What you see | Likely source | First check |
|---|---|---|
| Headset and desktop mirror are washed out | MSFS, HDR, weather or a visual add-on | Reset graphics and weather, then test with HDR disabled |
| Only the headset is washed out | OpenXR layer, headset colour setting, streaming or optics | Reset the headset software and disable optional API layers |
| Thin edges, trees and buildings sparkle | Anti-aliasing, low render resolution or excessive sharpening | Use TAA or DLAA and remove stacked sharpening |
| Edges distort only while moving your head | Motion reprojection or unstable frame timing | Disable reprojection temporarily and retest |
| The fault appears in one eye only | VR compositor, API layer or graphics driver | Restart the runtime and remove injected overlays |
The mirror is not a perfect copy of the final headset image, but this comparison prevents a common mistake: changing MSFS colour settings to correct a fault created after the simulator has rendered the frame.
Fix MSFS VR colour and shimmer in the right order
Most cases are fixed by resetting the VR pipeline before tuning individual graphics sliders.
- Create a clean test scene. Use a default aircraft, a default airport and a clear daytime weather preset. Temporarily remove visual, weather, lighting and cockpit mods from the
Communityfolder. - Compare the headset and mirror. Check the menus, cockpit and outside view separately. If menus are also pale or over-bright, suspect the runtime or headset rather than simulated sunlight.
- Remove colour-processing layers. Disable OpenXR post-processing, contrast, gamma, sunglasses, sharpening and colour-filter overrides. Restart the VR runtime and MSFS after changing them. Our explanation of how MSFS, OpenXR and headset resolution fit together helps identify which application controls each stage.
- Test without HDR. If HDR is enabled in Windows or MSFS, switch it off for one controlled test and restart the simulator. Desktop HDR does not always control the headset directly, but an incorrect HDR or colour-space hand-off can affect some VR paths and the desktop mirror.
- Establish a neutral rendering baseline. Select TAA, set the headset runtime to its recommended resolution and begin with the MSFS VR render scale near 100. If performance is inadequate, reduce one resolution control gradually instead of lowering both the runtime and simulator scales.
- Remove excessive sharpening. Reset sharpening in MSFS, the graphics driver, headset software and any OpenXR layer. Stacking two or three sharpeners creates bright outlines and makes fences, trees and cockpit labels crawl.
- Disable glare effects for diagnosis. Turn off bloom and lens flare temporarily, and reduce bright flood or instrument lighting. These settings can create halos, but they do not correct genuinely clipped whites or grey-looking blacks.
Open the VR graphics options while the headset is active; changing the ordinary desktop preset alone is not a reliable way to alter the VR image. Once the fault has gone, use our balanced VR settings for MSFS 2020 and 2024 to rebuild quality without changing several variables at once.
Which anti-aliasing mode reduces MSFS VR shimmer?
TAA is the safest starting point for stable edges, while DLAA can produce a cleaner native-resolution image when it is available and the GPU has enough headroom.
| Mode | Choose it when | Main drawback |
|---|---|---|
| TAA | You want stable scenery, cockpit edges and glass displays | Can look soft at a low render scale |
| DLAA | You have performance headroom and want maximum clarity | More demanding than an upscaling mode |
| DLSS Quality | You need additional performance | May soften instruments or create temporal artefacts |
| Lower-quality temporal upscaling | Only when frame rate matters more than fine detail | More visible shimmer, blur and ghosting in VR |
If shimmer is confined to glass-cockpit text, change from DLSS to TAA or DLAA before altering scenery settings. For runways, roofs and trees, raise render resolution first. Anisotropic filtering improves ground textures viewed at an angle, but it does not remove geometric edge aliasing.
Very high Terrain or Objects Level of Detail is not automatically better. It can introduce more sub-pixel detail in the distance, making vegetation and buildings sparkle. Contact shadows and screen-space reflections can also flicker; disable them individually to identify the offender. Our focused fixes for jagged edges and temporal shimmer cover those settings in more depth.
Why is MSFS VR too bright only inside the headset?
If the desktop mirror looks normal but the headset is washed out, reset the headset runtime’s brightness, contrast, gamma and colour enhancements rather than compensating inside MSFS.
Monitor controls and desktop graphics-driver colour adjustments often do not affect the headset at all. For a streamed headset, restore default encoding and colour options and test a wired connection if one is supported. Compression commonly causes banding and blockiness; it is less likely to cause scene-wide white clipping.
If only the outside view is overexposed while menus retain proper blacks and whites, compare a default aircraft and standard weather preset. MSFS eye adaptation, haze, direct sunlight and reflective cockpit glass can make the exterior much brighter than a dark cockpit. Bloom changes the halo around bright objects, not the underlying exposure.
Could lens glare or fogging make VR look washed out?
Optical glare, dirty lenses, fogging and an incorrect headset position can mimic low contrast without appearing in the desktop mirror.
Reposition the headset within its visual sweet spot, set the correct interpupillary distance where supported and clean the lenses using the headset manufacturer’s approved method. Halos that move with your eyes rather than with the simulated scene are usually optical, not an MSFS graphics fault.
Why does shimmer appear only when I move my head?
Shimmer that becomes trails, doubled edges or wobbling geometry during head movement normally points to motion reprojection or uneven frame delivery.
Disable reprojection for a short test. If the static image remains clean but moving objects become distorted when reprojection returns, lower clouds, shadows, traffic or resolution until frame timing is stable. Do not mistake reprojection artefacts for ordinary anti-aliasing; our VR flicker, ghosting and freeze troubleshooting addresses that separate failure mode.
Should I clear caches or reinstall MSFS?
Reinstallation should be the last step because shimmering and washed-out VR colour are usually caused by active settings, runtime layers or headset processing.
- Rolling cache: clear it only if streamed terrain or photogrammetry is visibly corrupt. It does not normally control anti-aliasing, exposure or headset colour.
- Shader cache: rebuild it if the fault began after a simulator or graphics-driver change and appears across every aircraft and location. Expect temporary stuttering while shaders are recreated.
- Add-ons: test with the
Communityfolder empty and disable relevant visual packages managed elsewhere in MSFS. - Graphics profile: reset both the simulator’s VR graphics settings and any per-game driver profile before reinstalling the simulator.