How do I install scenery in FlightGear?

To install scenery in FlightGear, extract the download into a dedicated scenery folder, preserving its Terrain, Objects and optional Buildings subfolders. Add that folder—the one directly containing those subfolders—to FlightGear’s scenery search path, place it ahead of TerraSync or default scenery, restart FlightGear, then load an airport inside the package’s coverage.

Should I use TerraSync or manual FlightGear scenery?

Use TerraSync for automatic worldwide coverage with an internet connection; install scenery manually when you need offline coverage, a specific airport or a third-party scenery package.

Enable automatic scenery downloading in the FlightGear launcher to use TerraSync, and choose a writable cache location with sufficient free space. TerraSync does not fetch the whole world in advance. Our overview of FlightGear’s automatic and offline scenery options explains the distinction.

Keep manually installed packages out of the TerraSync cache because FlightGear manages that directory itself. Manual scenery and TerraSync can be used together, with the custom package given higher search priority where their coverage overlaps.

Which FlightGear scenery folder should I select?

Select the directory that directly contains Terrain, Objects and any other scenery subfolders supplied by the package.

• Correct root: if the archive produces MyScenery/Terrain and MyScenery/Objects, add MyScenery.
• One level too high: if extraction produces Download/MyScenery/Terrain, do not add Download; select MyScenery.
• One level too low: do not select Terrain or Objects individually.

Not every package contains every subfolder. Terrain-only and object-only add-ons exist, while larger packages may also include folders such as Buildings, Models or Airports. Preserve folder names and capitalisation, especially on case-sensitive file systems.

How do I install downloaded scenery manually?

The safest manual method is to keep each FlightGear scenery package in its own directory and add its root through the launcher.

1. Read the package instructions. Check its stated coverage, required FlightGear data and any dependencies. Our offline HD world scenery download with package-specific placement notes is a practical example.
2. Extract the complete archive. FlightGear cannot load scenery from a ZIP or other compressed file. For a multipart download, obtain every required part and extract it as the package directs.
3. Find the actual scenery root. Open the extracted folders until you reach the directory containing Terrain, Objects or the other supplied scenery directories.
4. Store it outside FlightGear’s core files. A dedicated user-owned scenery directory avoids permission problems and prevents an application update from disturbing the add-on.
5. Add the directory to FlightGear. In the launcher settings, use the control labelled along the lines of Additional scenery folders; its exact position varies between launcher releases. Command-line users can supply --fg-scenery=/full/path/to/MyScenery as a launch option.
6. Set the search order. If the launcher permits reordering, place custom scenery before TerraSync and default scenery so the intended files take priority.
7. Restart and test within the coverage area. Load a specific airport or coordinate named in the package description. Testing somewhere nearby but outside the included tiles can give the false impression that installation failed.

Aircraft do not belong in the scenery path; they use a different directory structure covered in our separate FlightGear aircraft installation instructions.

Why is my FlightGear scenery not showing?

The usual causes are an incorrect folder level, incomplete extraction, lower search priority or testing outside the downloaded area.

• Only ocean or empty ground appears: confirm that the selected path directly contains the scenery subfolders and that the package covers the aircraft’s location. With TerraSync, allow the required tile to finish downloading.
• Default scenery still appears: move the custom directory ahead of the TerraSync and default paths, then restart FlightGear.
• Terrain loads but buildings or objects do not: check that all archive parts and supplied Objects, Buildings or model files were extracted. Also check the package notes for dependencies.
• The airport layout has not changed: the package may contain surrounding objects without replacement airport data. Verify what the download actually includes.
• Objects flicker or appear twice: overlapping packages may both provide the same content. Disable the competing package or adjust the path order rather than merging their files blindly.
• TerraSync never fills the missing area: verify that automatic downloads are enabled, the cache is writable and storage is available. Do not place third-party files inside that cache.

If the problem remains, temporarily disable other custom scenery, test a location explicitly listed by the package and inspect FlightGear’s startup log for the scenery paths it opened. That separates a path configuration error from a damaged or incompatible package.