Where is FSX scenery.cfg, and how do I edit it safely?

In FSX and FSX: Steam Edition, the active scenery.cfg is normally at %ProgramData%\Microsoft\FSX\scenery.cfg. A side-by-side boxed and Steam installation may instead use %ProgramData%\Microsoft\FSX-SE\scenery.cfg. Close FSX, confirm which file matches your Scenery Library, back it up, then edit it with a plain-text editor.

FSX scenery.cfg locations for boxed and Steam Edition

The active scenery configuration is in Windows’ shared ProgramData folder, not normally in steamapps\common\FSX, your roaming AppData folder or the main FSX installation directory. Press Windows key + R, enter %ProgramData%\Microsoft, and inspect the relevant folder.

%ProgramData% normally expands to C:\ProgramData, which Windows hides by default. Entering the environment-variable path directly still works when hidden items are not displayed.

FSX SE and FSXSE are common shorthand for Steam Edition, but the dual-install folder is written FSX-SE. Do not assume every Steam installation has that folder: a Steam-only installation commonly retains the ordinary FSX name.

Resumen breve en español

En FSX y FSX: Steam Edition, escriba %ProgramData%\Microsoft en la barra de direcciones y revise las carpetas FSX y FSX-SE. Por favor, cierre FSX y haga una copia de scenery.cfg antes de editarlo.

Is scenery.cfg the same as FSX.cfg?

No. scenery.cfg controls the Scenery Library, while FSX.cfg stores simulator settings such as graphics, controls and various tuning values.

If by “Steam cfg file location” you mean the simulator settings file rather than the scenery configuration, use our instructions for finding and safely editing FSX.cfg. Never rename one configuration file to replace the other.

Which scenery.cfg copy is active?

The active copy is the one whose Title= and Local= entries match the scenery shown in that FSX installation’s Scenery Library.

1. Open the Scenery Library: note the exact names of two or three distinctive add-on areas.
2. Exit FSX completely: do not inspect and edit the file while the simulator is still closing.
3. Open each candidate file: check both the FSX and FSX-SE folders if they exist.
4. Search for the recorded titles: confirm that their Local= paths and other nearby entries also match your library.

The newest modified date can support this check, but it is not proof. An add-on installer may have changed an old or inactive copy. Checking several live library entries is more reliable than checking one title alone.

Should I use the Scenery Library, Notepad or a scenery config editor?

Use FSX’s built-in Scenery Library for normal add-on management; edit the file directly only for a specific repair or path change that the library cannot complete.

Notepad is sufficient for direct repairs; a specialist scenery config editor is not required. Never run FSX and an external editor against the same file at the same time. For routine changes, follow our guidance on managing add-ons through the FSX Scenery Library.

How do I edit FSX scenery.cfg safely?

The safe method is to preserve an untouched backup, change only the intended area block and test the result before making another edit.

1. Close FSX: wait until the simulator process has ended so it cannot overwrite your changes.
2. Confirm the active copy: match its entries against the Scenery Library rather than relying only on the folder name.
3. Create a backup: copy scenery.cfg to another folder and give it a recognisable name such as scenery-before-edit.cfg.
4. Open it as plain text: use Notepad or another plain-text editor, not a word processor. Preserve the existing text encoding where possible.
5. Edit one complete area block: locate the intended [Area.nnn] header and verify its title and path before changing anything.
6. Check the filename: make sure the saved file is still exactly scenery.cfg, not scenery.cfg.txt.
7. Replace the file carefully: if Windows requires you to copy the edited file out and back, choose Yes at the replacement prompt only after confirming the destination and backup.
8. Test in FSX: inspect the Scenery Library, then load a flight in the affected area. Close FSX again before restoring the backup or making another change.

If Windows denies access, do not grant broad permissions across the entire ProgramData tree. Copy the file to a writable folder, edit it there, retain the original backup and then copy the edited file back with Windows’ normal administrator approval.

The fields most often involved are:

• [Area.nnn] — the area’s unique section header. Do not create a duplicate header.
• Title= — the label displayed in the Scenery Library; changing it does not rename or relocate the scenery.
• Local= — the scenery area’s path. It normally points to the parent folder containing a scenery subfolder and, where supplied, a texture subfolder.
• Layer= — the area’s priority layer. Avoid duplicate or mismatched layer values.
• Active=TRUE or FALSE — controls whether FSX loads the area.
• Required=TRUE — usually marks protected or essential scenery; do not remove these entries casually.

Do not renumber every area merely to make the sequence look tidy. Use the Scenery Library for priority changes and consult our explanation of safe FSX scenery priority and library order before moving airport, regional, mesh or default layers.

What if scenery.cfg is not there or Windows says “gibt es nicht”?

If the file is not there, first check the exact shared-data path and both possible folder names; do not create a blank scenery.cfg.

1. Use the correct location: enter %ProgramData%\Microsoft, not %AppData%\Microsoft or the FSX programme folder.
2. Check both names: inspect FSX and FSX-SE if both are present.
3. Show file extensions: confirm that the file has not become scenery.cfg.txt or been renamed as a backup.
4. Initialise FSX: if this is a new installation, run the intended FSX version once, let it reach its main interface, close it normally and check again.
5. Restore before rebuilding: if the file was deleted, restore a known-good backup before allowing a clean configuration to replace your add-on entries.

On German Windows, a message containing “gibt es nicht” means the entered path does not exist. The variable %ProgramData% is language-independent, so that spelling should still work; the usual causes are a mistyped path, use of FSX-SE when only FSX exists, or an installation that has not been initialised.

What if I paste the path and nothing happens?

Open File Explorer and paste only %ProgramData%\Microsoft into its address bar, then press Enter. Do not paste it into a web browser, a website search box or an editor’s file contents.

If the Run box still does nothing, enter %ProgramData% first and open the Microsoft folder manually. Finding another scenery.cfg through a whole-drive search does not prove it is active; installers and backups often leave extra copies.

Why does nothing happen after I edit scenery.cfg?

When a valid-looking edit has no effect, the usual cause is the wrong configuration copy, a hidden .txt extension, an incorrect scenery path or a change overwritten by FSX.

• Recheck that several Title= entries match the live Scenery Library.
• Confirm that FSX was closed while the file was saved.
• Verify that the intended block contains Active=TRUE.
• Check that Local= points to the area root, not one folder too high or directly to an individual BGL file.
• Confirm that the area root contains the expected scenery folder and scenery files.
• If the title appears in the library but the visual change is absent, check whether another higher-priority area is covering it.

A changed Title= only alters the library label. It does not install scenery, move files or repair a missing directory.

How do I recover from a bad scenery.cfg edit?

Close FSX and restore the untouched backup to the exact active location, retaining the filename scenery.cfg. Restart FSX, inspect the Scenery Library and test the affected location before attempting the edit again.

Do not delete the whole file as your first repair. FSX may generate a clean default configuration, but that can remove every third-party library entry even though the installed scenery remains on disk. If no usable backup exists, follow our procedure for repairing or safely rebuilding a damaged scenery.cfg.