Reduce shimmering textures in FS2004 with the right mipmap, trilinear and anisotropic settings, plus fixes for faulty add-ons.
To reduce shimmering textures in FS2004, select trilinear filtering, keep mip-mapping quality around the middle of its range, enable anisotropic filtering in the graphics driver, and avoid a negative texture LOD bias. If only one add-on shimmers, its textures may lack mipmaps or its scenery may overlap another package.
Which FS2004 settings reduce texture shimmer?
The best starting point is moderate mip-mapping combined with trilinear and anisotropic filtering, rather than pushing every sharpness control to maximum.
- Select trilinear filtering. Open FS2004's display hardware settings and change texture filtering from bilinear to trilinear. This blends transitions between mipmap levels, reducing the visible bands and crawling detail that appear as the aircraft moves.
- Set mip-mapping quality near the middle. Start at 4 if the slider displays numbers, or use its midpoint. Higher settings keep sharper texture levels visible farther away, but they can make runways, roofs and detailed terrain sparkle. Lower the setting by one step if distant scenery still shimmers.
- Enable anisotropic filtering for
fs9.exe. Use an application profile in the graphics driver rather than changing the global setting. Start at 8x; try 16x if performance remains stable. Anisotropic filtering improves oblique surfaces such as runways without relying on an excessively sharp mipmap setting. - Remove negative LOD bias. If the graphics driver offers a texture LOD bias control, use its neutral or clamp option. Negative values sharpen textures artificially and are a common cause of moving grain and distant sparkle. Leave the setting alone if your driver does not expose it.
- Use anti-aliasing for edges, not as the main texture fix. Anti-aliasing smooths aircraft outlines, buildings and other geometry, but ordinary multisampling does little for texture detail inside a polygon. Use either FS2004's anti-aliasing or a driver override; stacking conflicting methods can produce poor results.
- Restart and test one change at a time. Close and reopen FS2004 after changing the driver profile. Compare the same runway, altitude, view direction and weather so that cloud shadows or viewing angle do not confuse the result.
If these changes cost too many frames, our balanced FS2004 graphics and frame-rate settings provide a practical baseline without maximising every slider.
Why does only one add-on still shimmer?
Shimmer confined to one aircraft, airport or texture replacement usually points to the add-on rather than FS2004's global graphics settings.
Textures intended to be viewed at different distances should contain progressively smaller images called mipmaps. If an add-on omits them, FS2004 has to sample the full-resolution image at long range, causing fine lines and high-contrast details to sparkle.
- Temporarily disable the affected scenery or livery and repeat the test with default content.
- Reinstall the add-on from an unmodified copy if its textures may have been converted or overwritten.
- Undo replacement ground textures and undocumented FS9.cfg changes before changing the whole simulator. Our guidance on checking texture replacements and FS9.cfg modifications covers the relevant cautions.
- Do not batch-add mipmaps to every texture. Alpha channels, night textures and specialised effects can be damaged by indiscriminate conversion.
If the effect is limited to runways, taxiways or terrain, follow our more specific airport and ground-scenery flicker checks. A livery or fuselage that flashes instead needs the separate aircraft-texture flicker diagnosis.
Is it texture shimmer, z-fighting or screen tearing?
True texture shimmer looks like fine detail crawling or sparkling as the camera moves; fixed-location flashing and horizontal frame splits have different causes.
| What you see | Likely cause | What to change |
|---|---|---|
| Distant terrain, roofs or runway markings sparkle while moving | Texture aliasing or an aggressive mip/LOD setting | Use trilinear filtering, moderate mip-mapping and anisotropic filtering |
| Two surfaces alternate at one exact location | Overlapping scenery polygons, known as z-fighting | Disable duplicate or conflicting airport scenery |
| A horizontal split moves through the entire image | Screen tearing | Use vertical synchronisation or an appropriate frame-rate limit |
| Only trees, fences or other transparent edges sparkle | Alpha-tested texture aliasing | Try transparency or supersampling anti-aliasing if the driver supports it, accepting the performance cost |
Can FS2004 texture shimmer be eliminated completely?
FS2004 may retain some crawl on distant high-contrast textures and transparent autogen even after correct configuration. Its renderer cannot handle every aliasing case as cleanly as a newer simulator.
The practical trade-off is sharpness against stability: lower mip-mapping by one step when motion shimmer is distracting, or retain the midpoint and use anisotropic filtering when runway and terrain clarity matter more. Maximum sharpness is rarely the best-looking choice in FS2004.