FS2004 (FS9) 5 min read

How do I fix flickering aircraft textures in FS2004?

Adam McEnroe
In short

Fix flashing or flickering aircraft textures in FS2004 by isolating bad repaints, restoring mipmaps, correcting formats and checking GPU settings.

To fix flashing or flickering aircraft textures in FS2004, first determine whether the fault affects one repaint, one aircraft, or every aircraft. Reinstall a faulty repaint, restore FS2004-compatible extended BMP textures with mipmaps, then reset forced graphics-driver settings. Flicker confined to particular polygons usually indicates model z-fighting, not a texture fault.

What causes FS2004 aircraft textures to flicker?

Distance-dependent shimmer points to mipmaps or filtering, while angle-dependent patches usually point to overlapping model polygons.

What you seeLikely causeBest first action
Fine sparkling or crawling as the aircraft moves awayMissing or poor mipmaps, or unsuitable texture filteringRebuild the texture's mipmap chain and check filtering
Only one repaint flashes, turns grey or changes appearanceCorrupted, incompatible or incorrectly converted texture filesReinstall the FS2004 version of the repaint
Registrations, doors or small panels alternate with the surface beneathCo-planar polygons causing z-fightingUse the correct model variant or obtain a corrected model
Windows, propeller discs or reflective areas flickerDamaged alpha channel, mismatched texture or model transparency sortingRestore the original matching texture and preserve its alpha channel
Every aircraft shimmers or flashesFS9 display configuration, driver overrides or a graphics wrapperReturn the GPU profile to application-controlled settings

How do I isolate the faulty texture or setting?

A comparison with a known-good default aircraft will show whether the problem belongs to the repaint, its base model or FS2004's renderer.

  1. Back up the aircraft. Copy the affected aircraft folder before replacing or converting anything.
  2. Load a default aircraft. Use the same airport, time, weather and external view. If the default aircraft is stable, the global graphics configuration is probably not the main cause.
  3. Change liveries on the affected model. One bad livery indicates a repaint problem. If every livery flickers in the same places, suspect the model or shared textures.
  4. Watch how the fault changes. General shimmer that increases with distance suggests mipmaps. A sharply defined patch that alternates as the camera angle changes is normally z-fighting.

Confirm that the repaint was made for the exact FS2004 base model; a similarly named FSX model or another release of the same aircraft may use different texture mapping. Our checks for matching repaints with their base aircraft and configuration entries cover the installation side without duplicating it here.

If only Microsoft's default aircraft are affected, restore their original files from installation media or use our replacement pack for damaged default-aircraft textures. Do not overwrite the folders until you have made a backup.

How do I repair a flickering FS2004 repaint?

A repaint-only fault is usually fixed by restoring the original files or resaving them as FS2004-compatible extended BMP textures with a complete mipmap chain.

  1. Reinstall from the original archive. Replace the affected texture or texture.name folder rather than mixing old and new files. FSX DDS textures cannot simply be copied into an FS2004 aircraft.
  2. Match a working livery. Compare filenames, dimensions and formats with another repaint supplied for the same model. Preserve the original names exactly.
  3. Use an FS texture-aware editor. Save external skins as extended BMP files in a format already proven to work with that model. DXT3 is commonly used where a graduated alpha channel is required; 32-bit textures retain more detail but consume more texture memory. DXT1 is unsuitable when the material needs a smooth alpha gradient.
  4. Generate mipmaps. A complete mipmap chain prevents the renderer from repeatedly sampling the full-resolution skin at long range. Fine lettering may soften slightly, but omitting mipmaps commonly causes the sparkling or crawling associated with FS2004 aircraft texture flicker.
  5. Preserve the alpha channel. Depending on the model's material settings, alpha data can control reflection, shine or transparency. Replacing it with a solid channel may stop one symptom while producing opaque windows, excessive reflections or missing surfaces.
  6. Restart FS2004. Close the simulator fully before testing the repaired texture so it reloads the files.

For the editing details, see our guidance on FS2004 bitmap formats, mipmaps and alpha channels.

Model flicker that texture editing cannot fix

Texture editing cannot correct two model polygons occupying almost the same position. This z-fighting often appears along decals, doors, windows or registration panels and changes rapidly with the viewing angle.

Use the repaint with the exact model version for which it was designed. If the same patch flickers under every livery, the model itself needs correction; repeated texture conversion will not solve it. Similar flicker involving glass or propeller discs can also be an alpha-sorting limitation, so restore the model's matching propeller and glass textures before changing their alpha channels.

What if every aircraft flickers in FS2004?

Flicker across every aircraft is a renderer or graphics-configuration problem, not a collection of damaged repaints.

  1. Reset the graphics profile. In the GPU control panel, return FS2004 to application-controlled anti-aliasing and texture filtering. Disable driver-level sharpening and filtering optimisations while testing.
  2. Check FS9's display options. Select trilinear filtering and begin with the mipmapping-quality control around its middle range rather than at maximum. Anti-aliasing smooths object edges but cannot repair a faulty bitmap or missing mipmaps.
  3. Regenerate FS9.cfg. Close the simulator, find %APPDATA%\Microsoft\FS9\FS9.cfg, back it up and rename it. FS2004 will create a clean configuration on its next launch; then reselect the display device and add custom settings back one at a time.
  4. Remove non-native rendering changes. Temporarily move any DirectX wrapper, post-processing injector or replacement graphics DLL that you knowingly installed in the FS2004 directory. Do not delete unfamiliar Windows system files.
  5. Recheck the display driver. If the fault began immediately after a driver change, reset its profile or reinstall a vendor-supported driver rather than downloading loose DirectX DLL files.

Once the aircraft are stable, our FS9.cfg and texture-filtering adjustments for clearer FS2004 graphics explain how to reduce residual shimmer without reintroducing conflicting overrides.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members