How do I fix flickering scenery objects in FS2004?

Flickering scenery objects in FS2004 are usually caused by duplicate scenery layers rendering in the same place, z-fighting between overlapping models, or aggressive anti-aliasing and mipmap settings. First identify whether whole objects blink or only their edges shimmer, then isolate add-on layers before changing graphics settings or rebuilding FS9.cfg.

What type of scenery flicker are you seeing?

The appearance and location of the flicker usually reveal whether FS2004 has a scenery conflict or a graphics problem.

How do I isolate the conflicting FS2004 scenery?

The quickest reliable method is to disable add-on scenery in controlled groups until the flickering object disappears.

1. Confirm whether the problem is local. Visit a default airport in another region. If only one airport or city is affected, concentrate on scenery packages covering that location rather than changing global graphics settings.
2. Back up the affected add-on folders. Do not delete BGL files during diagnosis. Keep copies of the scenery and its configuration before moving or renaming anything.
3. Disable the most specific package first. Untick the affected airport or city in the FS2004 Scenery Library, close FS2004 and restart it. A restart ensures the scenery database is reloaded.
4. Test overlapping regional packages. If the flicker remains, disable nearby regional scenery, replacement airports and older versions of the same location. Work in small groups so the result identifies a particular package.
5. Look for leftover placement files. Check active add-on scenery folders, including shared locations such as Addon Scenery\scenery, for an old airport or object-placement BGL. File names often include an ICAO code, but this is not guaranteed, so verify a file before removing it.
6. Keep only one intended version. Once the conflict is identified, leave the obsolete package disabled or remove it according to its documentation. Retain a backup outside every active scenery folder so FS2004 cannot load it.

A mistake we see constantly is removing an add-on's main folder while leaving one of its airport files in a shared scenery directory. Our FS2004 scenery installation and folder guide explains the expected package structure and library activation process.

Why does changing scenery priority not always stop the flicker?

Scenery priority does not automatically prevent two BGL files from placing objects at identical coordinates.

A higher-priority package can replace some terrain or airport data, but separately placed library objects may still be drawn unless an exclusion removes them. Two nearly coplanar models then compete for the same depth values, producing z-fighting. In that case, moving a layer up or down may change the appearance without fixing the underlying duplicate.

The proper remedy is to disable the unwanted placement file or use a corrected package containing suitable exclusions. Do not remove default FS2004 scenery files merely because an add-on overlaps them.

Which graphics settings reduce object shimmer?

If scenery objects flicker across several unrelated locations, establish a clean FS2004 graphics baseline before making advanced driver changes.

• Return the graphics-card profile for FS9.exe to application-controlled settings.
• Enable anti-aliasing in one place initially rather than combining several driver and simulator overrides.
• Use trilinear filtering if it works correctly on the system.
• If distant textures sparkle, lower FS2004's mipmap-quality setting by one step and retest. Excessive sharpness often makes fences, roof lines and tree textures shimmer.
• Change one option at a time and test from the same saved flight and camera position.

Anti-aliasing can improve crawling edges, but it cannot cure two overlapping objects. For a balanced starting point, use our recommended FS2004 graphics and filtering settings rather than applying every available driver enhancement at once.

What if only trees, fences or transparent objects flicker?

Flicker limited to vegetation and mesh fences usually comes from alpha-textured polygons rather than duplicate scenery.

FS2004 trees commonly use intersecting flat polygons with transparent textures. Their edges can shimmer as the viewing angle changes, especially when mipmaps are missing or overly sharp. Moderate anti-aliasing and a lower mipmap-quality setting may reduce it, but a badly authored model or texture must be corrected by the scenery package itself.

If the fault affects one model only, reinstall that scenery and any required object library. Missing textures more often produce blank, black or untextured objects than regular geometric flicker, so do not assume every flashing object indicates a missing library.

What if objects disappear instead of flickering?

Objects that appear or disappear at repeatable distances are usually showing an LOD or draw-distance problem, not z-fighting.

Check that FS2004's scenery-complexity setting meets the add-on's requirement. If one particular model vanishes from certain angles even at high scenery complexity, its authored LOD levels or bounding box may be faulty and user-side display settings will not fully repair it. Broader distance-related symptoms are covered in our FS2004 scenery pop-in diagnosis.

Should I rebuild FS9.cfg?

Rebuild FS9.cfg only when object flicker affects many unrelated sceneries and survives both layer isolation and a graphics-driver reset.

Close FS2004, locate FS9.cfg in the simulator's user application-data location, and rename it to retain a backup. FS2004 will generate a clean configuration at the next launch. This resets display preferences, so reproduce the problem before restoring any tweaks.

If a clean configuration fixes the flicker, reapply settings gradually. If the problem remains confined to one airport with every other add-on disabled, the fault is in that scenery or its interaction with the default area; reinstalling FS2004 is unlikely to help.