Fix FS2004 ground scenery flicker by correcting texture filtering, mipmaps, anti-aliasing, duplicate AFCADs and conflicting scenery layers.
Ground scenery flicker in Microsoft Flight Simulator 2004 usually comes from texture shimmering, overlapping scenery layers, or incompatible add-on textures—not a failing graphics card. Enable trilinear and anisotropic filtering, use sensible mipmap and anti-aliasing settings, then isolate duplicate airport or ground scenery if the flicker affects only one location.
What kind of FS2004 flicker are you seeing?
The pattern of the flicker usually identifies whether FS2004 has a graphics-setting problem or conflicting scenery.
| What you see | Likely cause | First test |
|---|---|---|
| Distant ground textures sparkle or crawl as the view moves | Texture aliasing, weak filtering or excessive mipmap sharpness | Use trilinear filtering and driver-level anisotropic filtering |
| A runway, apron or taxiway flashes between two surfaces | Overlapping scenery polygons or duplicate airport files | Disable the most recently installed airport or regional package |
| Flicker occurs only in one add-on region | Scenery priority, texture or elevation conflict | Test the area with that Scenery Library entry disabled |
| Large terrain squares alternate between blurred and sharp | Late texture loading rather than true flicker | Use a sustainable frame-rate limit and reduce scenery load |
| A horizontal split crosses the entire picture while panning | Screen tearing | Enable vertical synchronisation; scenery changes will not fix it |
How do I stop FS2004 ground texture shimmering?
If the effect follows the camera across every airport and distant terrain, treat it as texture aliasing first.
- Select trilinear filtering. Open FS2004's display hardware settings and choose trilinear rather than bilinear filtering where the option is available. It gives smoother transitions between distant mipmap levels.
- Keep MIP mapping quality moderate. Start near the default or middle position rather than pushing the slider straight to maximum. An excessively sharp setting can make distant terrain crawl; increase it one step at a time only if textures look too blurred.
- Apply anisotropic filtering to FS9. In the graphics driver's application profile for
fs9.exe, try 8x filtering first and 16x if performance remains satisfactory. This is particularly effective on ground textures viewed at a shallow angle. - Configure anti-aliasing in one place. Try FS2004's anti-aliasing option first. If the driver does not honour it properly, disable the in-game option and use an application-specific driver override instead. Anti-aliasing smooths polygon edges; filtering and mipmaps do more to control terrain shimmer.
- Set a sustainable frame-rate target. Running FS2004 unlimited can leave less time for scenery loading on some systems. A stable cap may reduce blurred tiles and texture swapping, although it cannot cure two surfaces fighting for the same depth.
Change one setting at a time and repeat the same saved flight, location and view. Our guide to practical FS2004 filtering, mipmap and frame-rate combinations explains the useful trade-offs without relying on extreme driver settings.
What if trees, fences and roofs shimmer, but terrain does not?
Shimmer limited to vegetation, fences or detailed roof edges usually comes from FS2004's cut-out transparency textures rather than the ground.
Ordinary multisample anti-aliasing does not always smooth these textures. If the graphics driver offers transparency anti-aliasing or supersampling for fs9.exe, test it cautiously; it can be demanding. Poorly mipmapped add-on textures can still shimmer even with strong anti-aliasing.
Why does only one FS2004 airport flicker?
Flicker confined to one airport is usually z-fighting: two runways, aprons or ground polygons occupy almost the same position, so the renderer alternates between them.
How do I remove a duplicate AFCAD or scenery layer safely?
Disable suspected scenery rather than deleting files until the conflicting package has been identified.
- Disable the newest local package. Untick its entry in the FS2004 Scenery Library, restart the simulator and load the same airport.
- Check for another package covering the airport. Two third-party AFCAD or airport packages for the same ICAO code are a common cause. The default airport remaining underneath an add-on is normal; the problem is usually multiple add-on definitions or ground layers that were not designed to work together.
- Test scenery priority. Keep the local airport above broad regional scenery unless the package instructions require a different order. Restart FS2004 after each change so every BGL is reloaded.
- Move uncertain files out of active scenery folders. An airport code in a BGL filename is a clue, not proof of what the file contains. Move it to a holding folder outside the active scenery tree instead of deleting it.
A mistake we see constantly is installing a replacement airport while leaving an older AFCAD active in another add-on folder. Our FS2004 scenery installation and library-priority instructions show the correct folder structure and activation process.
If terrain pokes through the runway, or the airport sits on a shelf or in a hollow, check for an elevation or flatten conflict. Mesh alone does not normally make painted surfaces shimmer, but conflicting airport elevations can expose overlapping layers. See our guidance on testing ground textures, terrain mesh and airport-elevation conflicts.
Could damaged ground textures be causing the flicker?
Damaged or unsuitable replacement textures are likely when flicker begins immediately after installing a global texture set or affects only one add-on region.
A texture can display correctly nearby yet sparkle at distance if it lacks suitable mipmap levels. Disable or reinstall the affected package, preserving its intended folder structure. If a global replacement overwrote FS2004's main texture files, restore the package's backup or the original default files rather than copying unrelated textures into the folder.
Should I reset FS9.cfg?
Resetting FS9.cfg is worthwhile when flicker is global and remains after sensible in-game and driver settings have been applied.
- Close FS2004.
- Back up the configuration. Rename
%APPDATA%\Microsoft\FS9\fs9.cfgrather than deleting it. - Start FS2004 again. FS9 creates a clean configuration file automatically.
- Test before restoring tweaks. Configure resolution, filtering and the frame-rate target, then load a default airport before adding manual changes back.
This reset does not remove installed aircraft or scenery, but it does discard many simulator preferences. Before reapplying old entries, consult our explanation of how FS9.cfg texture and terrain controls affect image stability.
Do I need to reinstall FS2004?
A complete reinstall is rarely the right first fix because it does not remove driver overrides, duplicate add-on scenery or a bad configuration retained in the user profile.
Reinstall only when default texture files were overwritten without backups, or when a clean configuration and a default airport still show damaged or missing scenery. For flicker everywhere, prioritise filtering, mipmaps and the graphics profile; for one airport, prioritise duplicate AFCADs, ground polygons and scenery order.