Why is NL2000 scenery not working in FSX: Steam Edition?
Fix NL2000 scenery missing in FSX: Steam Edition by checking the simulator path, modules, Scenery Library, layer order and active scenery.cfg.
NL2000 v4 works in FSX: Steam Edition, but missing scenery usually means its packages were installed for boxed FSX, the wrong scenery.cfg was updated, a required module is absent, or a registered path no longer exists. Point the NL2000 installer at Steam Edition’s fsx.exe, repair its library entries, then restart FSX.
Why does NL2000 not appear in FSX: Steam Edition?
NL2000 usually disappears because its installed files and FSX scenery registration no longer agree.
- The installer detected boxed FSX: an old CD/DVD installation or its remaining configuration can cause NL2000 to register itself with the wrong simulator.
- Only some NL2000 modules are installed: v4 is modular, so installing an airport package does not necessarily install the surrounding ground scenery, supporting objects or regional coverage.
- The wrong configuration was changed: boxed FSX and Steam Edition can use separate
scenery.cfgfiles when both have existed on the same computer. - The registered folder moved: a new drive letter, restored backup or manually relocated NL2000 directory leaves the library pointing to an obsolete path.
- Registration was blocked: Windows permissions may allow packages to be downloaded while preventing changes to FSX’s scenery configuration.
- Another scenery layer has priority: older NL2000 releases or other Netherlands scenery can cover or duplicate parts of v4.
How do I fix NL2000 scenery in FSX Steam Edition?
Fix the simulator target and package installation first, then repair the Scenery Library rather than reinstalling FSX.
- Close FSX completely. Do not edit its scenery configuration while the simulator is open; FSX may write its in-memory configuration back to disk when it exits.
- Find the Steam Edition executable. Use Steam’s installed-files function to locate the directory containing
fsx.exe. Steam libraries can be on any local drive, so do not assume the default boxed-FSX path is correct. Our guide to finding the real FSX installation folder explains how to distinguish the executable from shortcuts and configuration folders. - Check the target selected by NL2000. If its installer or package manager displays a simulator or destination, confirm that it refers to the Steam installation you launch. Choose the FSX-compatible package type rather than a package intended for another simulator.
- Verify the complete package set. Confirm that the regional, airport and supporting packages needed for the area you want are installed. Follow the NL2000 v4 package, season and simulator-configuration instructions for the intended installation sequence. Reinstall an individual module if its extraction was interrupted or its scenery folder is empty.
- Run the manager with sufficient permissions. Use the same Windows account under which you run FSX. If the manager reports write or registration errors, start it with administrator rights, particularly when FSX or NL2000 is under a protected Windows directory. Avoid elevating it as a different Windows user, which may expose another user’s configuration.
- Inspect the FSX Scenery Library. Open Settings, then Scenery Library. NL2000 areas should be listed, enabled and placed above the default FSX scenery. Use our Scenery Library registration and priority procedure if the entries are absent or disabled.
- Check each registered folder. An entry must lead to the individual scenery-area folder that directly contains a
Scenerysubfolder and, when supplied, aTexturesubfolder. A mistake we see often is registering the single NL2000 parent directory when the installation contains several separate scenery areas beneath it. - Remove conflicts methodically. Disable old NL2000 entries and other Netherlands add-ons temporarily, but preserve the internal order of the v4 layers. Test v4 alone before enabling competing scenery one area at a time.
- Restart and test inside installed coverage. Allow FSX to refresh its scenery database, then load at a recognisable Dutch airport or region included in the modules you verified. Testing outside the installed package’s coverage can make a correct installation appear broken.
Which scenery.cfg does FSX Steam Edition use?
FSX: Steam Edition reads its active scenery.cfg from Windows configuration data, not normally from the folder beside fsx.exe.
The folder name can differ depending on whether boxed FSX was also installed. Use the steps for identifying and backing up the active Steam Edition scenery.cfg before changing anything.
Search the active file for NL2000 titles. Each enabled area should have a valid Local= path, an active setting and a unique area/layer definition. If a path no longer exists, repair it through the NL2000 manager or FSX Scenery Library where possible; manual editing should be the fallback after making a backup.
Do not copy an entire boxed-FSX configuration into Steam Edition. Even if its entries look valid, they may refer to another installation, different drive letters or missing scenery folders.
Can NL2000 remain on another drive?
Yes. NL2000 does not have to reside inside the FSX program directory, provided its drive is available and every Scenery Library path remains valid.
If you move the package later, remove or repair the old entries before adding the new location. Keeping both sets active can produce duplicate airports, conflicting ground textures and startup warnings about missing scenery areas.
Why is only part of NL2000 showing?
Partial NL2000 coverage means FSX is loading at least one layer, but another module, object library, texture set or registration is missing.
| Symptom | Likely cause | What to check |
|---|---|---|
| No NL2000 entries in the library | Registration went to another scenery.cfg or was blocked | Steam Edition target, active configuration and permissions |
| FSX reports that a scenery area cannot be found | The registered folder was moved, deleted or entered at the wrong level | The entry’s Local= path and actual folder structure |
| One airport or region is missing | Its separate package was not installed or enabled | Package status and matching Scenery Library entry |
| An airport appears but the surrounding ground remains default | Only the airport module is installed | Required regional or terrain package |
| Ground scenery appears but buildings or objects do not | A supporting object package is absent, or Scenery Complexity is too low | Supporting packages and FSX display settings |
| Duplicate runways or older scenery appear through NL2000 | A conflicting layer has equal or higher priority | Older NL2000 and other local scenery entries |
| Seasonal textures are wrong or incomplete | The supplied seasonal option was not configured completely | The season procedure and texture packages described in the v4 manual |
Do not combine folders or library entries from different NL2000 generations. Disable the older release first and establish that v4 works by itself before rebuilding a mixed scenery setup.
Do I need to reinstall NL2000 or FSX?
Reinstall only the affected NL2000 package when its actual scenery files are missing; reinstalling FSX is rarely justified when default scenery still works.
Steam’s file verification does not install NL2000 modules, correct an external folder path or register scenery in the active library. Reinstall or verify FSX itself only when default airports and scenery are also damaged. If NL2000 alone is absent, repair its packages, paths and library entries instead.