How do I reduce shimmering and flickering textures in FSX?
Stop shimmering and flickering textures in FSX with the right anti-aliasing, anisotropic filtering, mipmap and driver settings.
To reduce shimmering and flickering textures in FSX or FSX: Steam Edition, run at native resolution, enable anti-aliasing and select anisotropic filtering. Use per-application transparency supersampling only for trees, fences and other alpha textures. If one aircraft or airport alone flashes, suspect missing mipmaps, overlapping geometry or duplicate scenery, not global graphics settings.
First identify what is actually flickering
Shimmering, z-fighting, blur and screen tearing can look similar in motion, but they require different fixes.
| What you see | Likely cause | Best first action |
|---|---|---|
| Runway markings, roof edges or aircraft outlines crawl as the camera moves | Edge aliasing | Enable anti-aliasing |
| Runways and terrain sparkle towards the horizon | Weak anisotropic filtering, excessive sharpening or poor mipmaps | Select anisotropic filtering and disable sharpening |
| Trees, fences, aerials or railings shimmer | Aliasing in transparent or alpha-tested textures | Try transparency anti-aliasing |
| One surface alternates rapidly between two images | Overlapping geometry or duplicate scenery | Find and disable the conflicting add-on |
| The whole image has a horizontal split during camera movement | Screen tearing | Use VSync, variable refresh rate or a suitable frame cap |
| Detail remains consistently soft while stationary | Low resolution, low texture quality, upscaling or texture-loading trouble | Correct the resolution or texture setting rather than adding more AA |
Which FSX settings reduce shimmering graphics?
FSX’s native-resolution, anti-aliasing and anisotropic-filtering settings provide the safest starting point for reducing texture shimmer.
- Open the display settings. In FSX, go to
Options > Settings > Display. - Select the native display resolution. In full-screen mode, use the monitor’s native resolution. In windowed mode, make sure Windows itself is using the correct native resolution.
- Set filtering to Anisotropic. This improves the sampling of runways, taxiways, terrain and other textures viewed at shallow angles.
- Enable Anti-aliasing. This smooths polygon edges such as aircraft outlines, buildings and runway markings.
- Keep Global Texture Resolution high enough for the add-on. Lowering it can hide sparkle by making every texture softer, but that is not a proper solution.
- Test a repeatable scene. Use the same aircraft, airport, weather and camera position. Change one option at a time and restart FSX after changing driver settings or DX10 Preview.
Native resolution prevents scaling blur, anti-aliasing treats geometric edges, and anisotropic filtering preserves oblique texture detail. Our FSX anti-aliasing and native-resolution checklist covers the core settings when jagged aircraft and scenery edges remain visible.
What do anti-aliasing, transparency supersampling and mipmapping fix?
These techniques address different sources of flickering, so increasing one cannot compensate fully for a problem handled by another.
| Technique | What it improves | What it does not fix |
|---|---|---|
| Standard anti-aliasing | Polygon edges, aircraft silhouettes, buildings and painted geometry | Missing mipmaps or overlapping surfaces |
| Anisotropic filtering | Textures receding towards the horizon | Thin alpha-tested fences and trees |
| Transparency multisampling | Some transparent-texture edges at relatively modest cost | Not effective with every FSX texture or driver |
| Transparency supersampling | Fine trees, fences, grilles, aerials and similar alpha textures | Z-fighting; it can also reduce frame rate heavily |
| Mipmaps | Distant textures by supplying progressively smaller texture levels | Screen tearing or duplicate geometry |
Transparency supersampling is the anti-aliasing option most likely to tame sparkling vegetation and fences, but it should not be the first setting applied. Establish a clean in-simulator baseline before adding it through the graphics driver.
Mipmaps are part of the texture itself. If an aircraft repaint or scenery texture was supplied without suitable mip levels, no amount of anti-aliasing can generate them at run time. Our explanation of how anti-aliasing and mipmapping solve different artefacts helps distinguish edge shimmer from a defective texture package.
Should I force anti-aliasing in NVIDIA Control Panel?
Use a per-application profile for fsx.exe only when FSX’s own settings leave visible shimmer; do not force experimental settings globally.
- Exit FSX. Driver changes may not apply correctly while the simulator is open.
- Select the correct executable. Boxed FSX and Steam Edition both use
fsx.exe, although their installation locations differ. - Start with application-controlled anti-aliasing. Leave FSX anti-aliasing enabled and verify that the basic configuration works.
- Force anisotropic filtering only if needed. A high per-application level can improve distant runway and terrain clarity without affecting other software.
- Choose one AA strategy. An enhancement mode works with application AA, while an override mode attempts to replace it. Do not combine several unexplained overrides.
- Add transparency anti-aliasing last. Try transparency multisampling first if offered. Use the lowest effective supersampling level when multisampling does not control fences and trees.
- Remove causes of artificial sparkle. Disable driver image sharpening for FSX if it exaggerates distant detail. If the driver exposes a negative texture LOD bias control, use
Clamp.
NVIDIA, AMD and Intel drivers do not expose identical controls, and option names can vary between driver generations. Some forced anti-aliasing modes also behave differently under FSX’s DX10 Preview renderer. Our recommended per-application NVIDIA settings for FSX explain the useful controls without relying on a global profile.
Why does only one aircraft or scenery area flicker?
Flickering confined to one aircraft, airport or scenery package nearly always points to add-on content, scenery priority or renderer compatibility.
- Duplicate airports or scenery: Two packages may draw aprons, runways or buildings in almost the same position. Disable overlapping scenery entries one at a time and retest.
- Z-fighting: Two polygons occupying nearly the same plane alternate as the viewpoint changes. This requires corrected geometry or removal of the conflicting package; anti-aliasing will not cure it.
- Missing or poor mipmaps: If one repaint, sign set or ground texture sparkles only at a distance, reinstall or replace that texture package. Texture authors need to regenerate suitable mip levels.
- DX10 Preview incompatibility: Turn off DX10 Preview, restart FSX and test the same view. If the fault disappears, use the normal DirectX 9 renderer or a version of the add-on intended for DX10 Preview.
- Flickering shadows: Temporarily disable the relevant aircraft or scenery shadow option. If only the shadow stops flashing, treat it as a shadow-rendering or add-on compatibility fault rather than texture shimmer.
If the entire display flashes, overlays appear and disappear, or the fault began after a driver override, reset the FSX application profile and compare full-screen with windowed operation. Our modern-PC FSX flicker diagnosis covers DX10 Preview, overlays, driver conflicts and add-on z-fighting in more detail.
How do I reduce shimmer without making textures blurry?
Keep native resolution and anisotropic filtering, then reduce costly or softening anti-aliasing options before lowering texture quality.
- Disable driver-level FXAA or similar post-process smoothing if the entire cockpit and interface look soft.
- Remove display scaling or upscaling and test at the panel’s native resolution.
- Keep anisotropic filtering enabled for runway and terrain clarity.
- Reduce transparency supersampling before standard anti-aliasing if frame rate falls sharply.
- Remove excessive sharpening rather than countering it with stronger anti-aliasing.
A common mistake we see is lowering Global Texture Resolution until the shimmer is hidden. That merely exchanges texture shimmering for blur. If textures remain low-resolution after the aircraft stops moving, investigate texture loading, available graphics memory and the affected add-on rather than increasing supersampling.
Is MSFS 2024 screen tearing the same as texture shimmering?
MSFS 2024 screen tearing is a display-synchronisation problem, not texture flickering, and anti-aliasing or anisotropic filtering will not fix it.
- Confirm the refresh rate. On PC, make sure Windows and the simulator are using the intended monitor refresh rate.
- Enable one VSync method. Use the simulator’s display option or a per-application graphics-driver setting, then test before adding another limiter.
- Configure variable refresh rate correctly. If the monitor and graphics card support it, enable the feature throughout the display chain and keep the final frame rate inside the display’s supported range.
- Check frame generation separately. Generated frames can push output beyond the monitor’s refresh range or introduce their own motion artefacts. Test with frame generation off before blaming textures.
- Compare display modes. A full-screen or borderless presentation mode may interact differently with Windows composition and driver synchronisation.
On Xbox Series X|S, PlayStation 5 and PS5 Pro, graphics-driver profiles are not available. Use a compatible television or monitor mode, enable variable refresh rate where supported by the complete console-to-display setup, and test without display-side motion interpolation. A horizontal tear across the whole frame is distinct from sparkling trees, taxiway lines or shadows.
What about blurry textures or flickering shadows in Control?
In Remedy’s Control, blurry textures and flickering shadows are game-specific rendering symptoms; the FSX profile and transparency-supersampling advice above should not be applied to its executable.
For diagnosis, reset any Control-specific driver overrides, use native output resolution, temporarily match render resolution to output resolution, and test without DLSS or other upscaling. Compare its DirectX 11 and DirectX 12 modes, then disable ray-traced shadows separately if shadow flicker occurs under DirectX 12. If textures stay blurry while the camera is stationary, suspect texture streaming or installation data rather than anti-aliasing.