Fix NL2000 scenery in FSX Steam Edition: check the simulator target, package install, scenery.cfg registration, permissions and layer order.
NL2000 v4 can work in FSX: Steam Edition. When it does not appear, the installer usually targeted boxed FSX, required packages are missing, or its library entries went into the wrong scenery.cfg. Select the Steam Edition target, run the installer as administrator, verify each layer, and restart FSX.
What causes NL2000 to disappear in FSX Steam Edition?
The most common cause is a mismatch between the simulator NL2000 configured and the FSX installation you actually launch.
- Wrong simulator target: a boxed FSX installation, even an old or incomplete one, can cause the package manager to register NL2000 there instead of in Steam Edition.
- Missing scenery packages: NL2000 is modular. Having its installer or package manager does not prove that the required terrain, airport and supporting packages have been installed.
- Wrong configuration file: boxed FSX and Steam Edition can maintain separate scenery configurations, particularly when both have existed on the same PC.
- Blocked registration: Windows permissions can let files download while preventing the installer from updating
scenery.cfg. - Broken paths: moving the NL2000 folder, changing drive letters or restoring files from a backup leaves scenery entries pointing to locations that no longer exist.
- Layer conflicts: old NL2000 versions or other Netherlands scenery can cover parts of the installation when their entries have higher priority.
How do I fix NL2000 scenery in FSX Steam Edition?
- Close FSX completely. Do not alter scenery entries while the simulator is running, because FSX may overwrite the changes when it exits.
- Confirm the Steam installation folder. In Steam, inspect FSX: Steam Edition's installed files and locate the directory containing
fsx.exe. Do not assume it is on the system drive; Steam libraries can be placed elsewhere. - Use the correct package manager. Obtain the NL2000 v4 installer and package manager provided in our library. Select the FSX or FSX: Steam Edition package option and confirm that the detected simulator path is the Steam folder containing
fsx.exe. - Run the installer as administrator. This is particularly important when either FSX or NL2000 is under a Windows-protected directory. It allows the manager to create folders and register scenery areas.
- Check the installed packages. Verify that the supporting packages and the regional or airport packages you expect to see are marked as installed. Reinstall any package whose download or extraction did not finish.
- Inspect the Scenery Library. Start FSX, open Settings and then Scenery Library. NL2000 areas should be present and enabled. Their folders must still exist, and the NL2000 group should sit above the default FSX scenery while retaining the order created by its installer.
- Register missing areas properly. Rerun the package manager's registration process before adding folders manually. If manual registration is necessary, follow the package selection and scenery-registration sequence in the NL2000 v4 manual; do not add one top-level folder when the installation contains several separate scenery areas.
- Restart and test in the covered area. Let FSX rebuild its scenery database, then load at a clearly identifiable Dutch airport included in the packages you installed.
Which scenery.cfg does FSX Steam Edition use?
FSX: Steam Edition uses an active Windows application-data copy of scenery.cfg, not necessarily the similarly named file beside the simulator's program files. Its exact configuration naming can also differ when boxed FSX is or was installed.
Use our instructions to identify the active Steam Edition scenery.cfg safely. Search that file for NL2000 entries and check that every Local= path points to a real folder containing the expected Scenery subfolder and, where supplied, a Texture subfolder.
If the entries have duplicate area numbers, invalid paths or damaged section formatting, back up the file before changing it. Our procedure for repairing malformed or invalid FSX scenery.cfg entries covers that problem without replacing the entire configuration. Never copy a boxed FSX configuration wholesale into Steam Edition; its paths may refer to a different simulator directory.
Why is only part of NL2000 showing?
Partial coverage usually means the installation is loading but one regional, airport or supporting package is absent or disabled.
| Symptom | Likely cause | What to check |
|---|---|---|
| No NL2000 entries in the library | Wrong scenery.cfg or blocked registration | Steam Edition target and administrator permissions |
| Area not found during startup | Moved or deleted scenery folder | The entry's Local= path |
| One region or airport is missing | Its package was not installed | Package status in the NL2000 manager |
| Ground scenery appears but buildings do not | Missing object package or low display settings | Required packages and Scenery Complexity |
| Default or older scenery covers NL2000 | Incorrect layer priority | Disable conflicting scenery temporarily and preserve NL2000's internal order |
Do not mix folders and library entries from different NL2000 generations. Disable older entries first, test v4 on its own, and only then re-enable other Netherlands add-ons one at a time.
Do I need to reinstall FSX Steam Edition?
No. Reinstalling FSX or verifying its Steam files does not install NL2000 packages, correct an external scenery path or register entries in the active scenery library.
Repair the NL2000 package installation and configuration first. Reinstall FSX only if default scenery also fails and the simulator's own files are known to be damaged; it is rarely the right fix when NL2000 alone is missing.