Find the Prepar3D scenery.cfg location, open the Scenery Library and see why add-on.xml scenery may be stored elsewhere.
In Prepar3D, the active legacy scenery configuration is normally stored at C:\ProgramData\Lockheed Martin\Prepar3D vX\scenery.cfg, where vX is the installed major version. Open the in-simulator Scenery Library after loading a scenario by choosing World > Scenery Library. ProgramData is hidden by default; add-on.xml scenery may be registered separately.
Where is scenery.cfg stored?
The Prepar3D scenery.cfg location is inside the version-specific Lockheed Martin folder under Windows ProgramData. The quickest way to reach the correct area is:
- Press Windows key + R.
- Enter
%PROGRAMDATA%\Lockheed Martinand press Enter. - Open the folder matching the Prepar3D major version you use, such as
Prepar3D v5. - Find
scenery.cfgand make a backup before changing it.
Each installed major version has its own configuration folder. Windows may display the file simply as scenery when known file extensions are hidden. Do not confuse it with Prepar3D.cfg, which is a different file stored in the user's AppData area.
Where is the Scenery Library in Prepar3D?
The Scenery Library is an in-simulator dialogue, not a folder on the drive. Load a scenario, open the menu bar and select World > Scenery Library.
This dialogue lets you add, remove, enable and reorder traditional scenery areas. Entries nearer the top generally receive higher display priority. Prepar3D v5 users can follow our steps for registering scenery through the Scenery Library rather than editing the configuration file directly.
Why is an add-on missing from scenery.cfg?
An add-on can work in Prepar3D without having a conventional entry in scenery.cfg. Prepar3D supports both the older Scenery Library method and package-based scenery declared through add-on.xml.
| Registration method | Where it is defined | How to manage it |
|---|---|---|
| Legacy scenery area | scenery.cfg under ProgramData | World > Scenery Library |
| Add-on package | add-on.xml inside the package, with separate discovery records | The package declaration and Prepar3D add-on controls |
Package scenery may appear in the library as an add-on-controlled entry while remaining absent from scenery.cfg. Its files can be under the standard Documents add-ons folder or another location chosen by its installer. Our guide to legacy entries and add-on.xml package management explains which method to use.
Can I edit scenery.cfg manually?
Yes, but using the Scenery Library is safer for routine additions and priority changes. Manual editing is best reserved for removing a known broken entry or repairing a configuration that the dialogue cannot open correctly.
- Exit Prepar3D so it cannot overwrite the file while you edit it.
- Copy scenery.cfg to a safe backup location.
- Use a plain-text editor and preserve the numbered
[Area.nnn]sections, paths and layer values. - Restart Prepar3D and verify the result in the Scenery Library before deleting the backup.
Never copy scenery.cfg wholesale from another Prepar3D major version. Default scenery layers, installed paths and package records can differ.
What if Scenery Library changes will not save?
If changes disappear after restarting Prepar3D, scenery.cfg is usually read-only, blocked by permissions or being edited in the wrong version folder. Confirm that the file under the active version's ProgramData folder changes when you use the library.
For access-denied messages, failed writes or a library that repeatedly reverts, use our Prepar3D scenery.cfg permission fixes. Avoid running the simulator permanently as administrator merely to conceal a folder-permission problem.