Learn how to update scenery add-ons in FSX safely, choose a patch or clean replacement, retain Library entries and fix duplicate scenery.
To update scenery add-ons in FSX or FSX: Steam Edition, back up the existing package, close the simulator, then apply the supplied patch or replace the old package with the complete new version. Keep its Scenery Library path valid, remove obsolete files, and restart FSX to rebuild the scenery database.
Should I patch over the old scenery or replace it?
Use an incremental patch only on the exact scenery version it was made to update; use a clean replacement when you have downloaded a complete new package. The mistake we see most often is merging a full release into an old folder, leaving obsolete .bgl files active.
| Update supplied as | Correct method | Main risk |
|---|---|---|
| Incremental patch | Apply it over the supported existing version as instructed. | Patching the wrong base version can leave missing or mismatched files. |
| Complete replacement | Back up and empty the old package folder, then copy in the complete new release. | Merging both versions can produce duplicate airports, flickering or elevation faults. |
| Complete package using a new folder | Install it separately, deactivate the old Scenery Library area and register the new one. | Leaving both areas active creates overlapping scenery. |
| Automatic installer | Select the active FSX installation and use the installer's update or removal process. | An installer may target the wrong folder when boxed FSX and Steam Edition coexist. |
How do I update FSX scenery manually?
A safe manual scenery update preserves a rollback copy while ensuring FSX sees only one version of the package.
- Read the update instructions first. Establish whether the download is a patch, a full replacement or an installer. Check whether a specific earlier release is required.
- Find the active scenery folder. Open
Settings > Scenery Libraryin FSX and note the area's folder and priority. Do not assume the add-on is inside the defaultAddon Scenerydirectory; FSX can use scenery stored elsewhere. - Back up the whole package. Copy its parent folder to a location outside every active scenery area. A typical package contains paired
SceneryandTexturefolders, although some products use additional folders or external object libraries. - Close FSX completely. For a patch, copy the supplied files into the existing package exactly as directed. For a full release, remove the old package contents before copying the replacement. Do not overwrite stock FSX scenery unless the package explicitly requires it and those files have been backed up.
- Check the resulting folder structure. The registered package folder should normally contain
Sceneryand, where required,Texture. Avoid accidental nesting such asPackageName\PackageName\Scenery, which causes FSX to ignore the files. - Confirm the Scenery Library entry. If the replacement uses the same folder path, the existing entry can remain. If its path has changed, deactivate the old area and register the new folder using our manual scenery folder and activation procedure.
- Restart and inspect the location. Allow any scenery database rebuild to finish, then check the airport or region for correct ground textures, buildings, runways and elevation.
With an automatic installer, verify that it points to the FSX edition you actually run. Steam libraries can be placed on custom drives, while older installers may assume a different location or lack permission to write there. After installation, inspect the active scenery folder rather than trusting a success message alone.
Do I need to add the scenery to the Library again?
No, not when the updated scenery remains at the same registered path. FSX's Scenery Library entry points to the package folder, so replacing files inside that folder does not normally require a second entry.
If the update creates a differently named folder, disable the old area before activating the new one. Put the replacement at the appropriate priority for overlapping airports, terrain or regional packages; our explanation of how FSX scenery priority resolves conflicting layers covers that decision without requiring direct edits to scenery.cfg.
If the entry disappears or fails to remain enabled after restarting, use the recovery steps for missing Scenery Library areas rather than creating several duplicate entries.
Why does FSX still show the old or broken scenery?
FSX usually shows old or damaged scenery because duplicate files remain active, the update went to the wrong installation, or the package folder is nested incorrectly.
- Old airport still appears: search active scenery areas for the previous airport or layout file. Deactivating the old area is safer than deleting uncertain files.
- Double runways or buildings: two versions of the same airport are active, or another airport package has higher priority.
- Airport is sunken or raised: an obsolete elevation-correction file may remain in a separate scenery area. Remove it only when the package documentation identifies it; never delete a similarly named stock file on a guess.
- Black or missing textures: the
Texturefolder may be absent, incorrectly nested or dependent on an object library not included with the patch. - No visible change: the files may have been installed into boxed FSX while Steam Edition is running, or vice versa. Compare the active Library path with the actual update destination.
- FSX crashes near the scenery: restore the backup first. A mixed release, incompatible
.bglor incomplete patch is more likely than a general graphics setting problem.
How do I roll back a failed scenery update?
Close FSX, remove the updated package and restore the complete backup to its original path. The existing Library entry can remain if that path is unchanged. If an installer also updated shared object libraries, use its repair or removal process rather than deleting shared files that other scenery packages may require.