Fix corrupted or misaligned FS2004 scenery by finding duplicate BGLs, bad layer priority, mesh conflicts, missing textures and stale indexes.
FS2004 scenery is usually corrupted or misaligned because two BGL files cover the same area, the Scenery Library order is wrong, terrain mesh or airport elevations conflict, textures are missing, or the add-on was compiled with incorrect coordinates. Disable layers until the fault disappears, then correct, replace or remove the offending files.
The scenery file itself is not always damaged. In FS2004 (FS9), apparent corruption can come from a perfectly valid add-on conflicting with another package, an elevation correction installed elsewhere, or scenery made for a different simulator or base package.
FS2004 scenery symptoms and likely causes
The pattern of the fault usually identifies which type of scenery file needs attention.
| Symptom | Likely cause | First check |
|---|---|---|
| Runway, taxiways and buildings do not align | Duplicate airport or AFCAD BGL, or an airport designed for a different regional base | Disable other scenery covering the same airport and search active folders for files containing its ICAO code |
| Airport is sunken, floating or on a plateau | Conflicting mesh, flatten or airport-elevation BGL | Disable broad terrain packages and look for a separate elevation correction supplied with the airport |
| Photographic ground is shifted or rotated | Incorrect coordinates, projection, datum, pixel spacing or source dimensions | Test the photo layer without other local scenery; a consistently shifted image normally requires recompilation |
| Black, blank or patchwork surfaces | Missing, damaged or incorrectly installed texture files | Confirm that the active area has the required Texture folder and seasonal texture variants |
| Ground surfaces flash or shimmer | Two polygons or airport surfaces occupy the same position | Disable duplicate airport and ground-detail layers |
| Scenery is distorted everywhere | Display configuration, graphics driver or global texture problem | Test a stock aircraft at a stock airport before changing individual scenery packages |
If the only fault is flashing ground rather than displaced objects, use our focused steps for isolating overlapping ground polygons and duplicate airport files.
How do I isolate the bad scenery layer?
The fastest safe method is to disable third-party scenery in controlled groups until the problem disappears.
- Create a repeatable test. Load the same airport, runway, season and time each time. A missing seasonal texture may appear only under particular conditions.
- Back up the configuration. Save a copy of
scenery.cfgand the suspect add-on folder before moving or replacing anything. - Disable the newest local layer. Untick it in the FS2004 Scenery Library, close FS2004 completely and restart it. Do not delete the package yet.
- Divide the remaining add-ons into groups. Disable half the third-party areas, test, and repeat with the affected half. This is much quicker than testing every entry individually.
- Inspect the folder structure. A conventional scenery area has sibling
SceneryandTexturefolders beneath its package folder. Double nesting and activating the wrong parent folder are mistakes we see constantly; our FS2004 scenery installation and folder-order guidance covers the correct arrangement. - Remove duplicate BGL files from the test. Search filenames for the airport ICAO code, but do not rely on names alone because some packages use internal naming. Move one suspect
.bgloutside every active scenery folder rather than deleting it. - Check compatibility and dependencies. Confirm that the package explicitly supports FS2004 and whether it expects a particular mesh, landclass or regional scenery product.
- Reinstall only the isolated package. Extract it into a clean folder instead of copying over the old installation, which can leave obsolete BGL files active.
How should FS2004 scenery priority be set?
Airport-specific scenery should normally sit above broader regional scenery, while broad terrain and default layers remain below it.
- Detailed airport package: above regional airports, landclass and broad terrain packages covering the same location.
- Companion airport entries: kept in the relative order specified by the package documentation.
- Regional scenery and landclass: below individual airports unless the package instructions explicitly say otherwise.
- Broad mesh and default scenery: generally lower, with the original default-layer order left intact.
Terrain mesh is a special case. FS2004 can select a higher-resolution mesh ahead of a lower-resolution one despite their apparent library positions, so changing priority may not cure cliffs, spikes or airport plateaux. Use the separate explanation of terrain mesh, ground textures and elevation conflicts when the underlying terrain is deformed.
An airport elevation BGL may also have been installed in a globally active scenery area rather than the airport's own folder. That file can remain active after the visible airport entry is disabled, so search for companion files before deciding the airport package is innocent.
Can layer order fix shifted photoreal scenery?
No: layer priority cannot translate, rotate or resize a photoreal image compiled with incorrect geographic data.
If roads, coastlines and the airport align with each other but the photographic tile is consistently displaced, the source coordinates or compilation settings are wrong. Latitude and longitude order, hemisphere signs, datum, projection, pixel spacing and image dimensions all need checking. Our photoreal compilation and alignment guidance explains those corrections.
If the photographic ground aligns but only the runway and buildings are displaced, return to the airport BGL search. That pattern usually indicates a duplicate AFCAD or scenery built against a different version of the airport.
When should I rebuild indexes or reinstall?
Rebuild generated files only after the conflicting layer and folder structure have been checked.
If FS2004 continues to use an old file list after BGL files have changed, close the simulator and back up the affected area. Remove only its generated scenery index, commonly named scenery.dat; FS2004 should recreate that index at the next load. Do not remove any .bgl or texture files as part of this step.
If Scenery Library changes do not remain saved, verify which copy of scenery.cfg FS2004 is actually updating. On modern Windows installations under a protected folder, file virtualisation can create a per-user copy. Change one library entry through FS2004, close the simulator, and compare file modification times rather than editing several copies blindly.
Rebuilding FS9.cfg is appropriate only when corruption affects stock and add-on scenery across the simulator. Back it up before allowing FS2004 to generate a fresh copy because display, control and other preferences will be reset.
Repair the stock FS2004 installation only if the defect remains with every third-party scenery area disabled. A complete reinstall is the last resort: it will not fix a duplicate BGL left in an add-on folder or a conflicting file retained in a virtualised Windows location.