Find FlightGear scenery add-ons and install them correctly with TerraSync or a manual path. Fix folder nesting, path priority and missing scenery.
You can find FlightGear scenery add-ons among the FlightGear files in our downloads collection, or let TerraSync fetch standard world scenery automatically. For manual packages, extract the archive, point FlightGear at the folder containing Terrain, Objects or Airports, give it the correct path priority, then restart the simulator.
Where can I download FlightGear scenery?
The right source depends on whether you want automatic worldwide coverage, a particular airport or detailed offline scenery. Check each package description for its covered area, prerequisites and compatible FlightGear generation before downloading it.
| Scenery option | Best used for | Main limitation |
|---|---|---|
| TerraSync | Automatic standard scenery for places you visit | Needs an internet connection for uncached areas and consumes storage as its cache grows |
| Manual regional package | Custom airports, terrain, objects or orthophotos | You must manage installation paths, updates and compatibility |
| Offline world package | Broad coverage without downloading tiles during a flight | Large download and extracted storage requirements |
For broad offline coverage, our large HD world scenery download is one option. Regional packages are usually more practical when you only fly in a few countries or need one enhanced airport.
How do I install FlightGear scenery manually?
Install manual scenery by extracting it into a separate writable folder and adding its scenery root to FlightGear's search paths.
- Read the package instructions. Some scenery is self-contained, while orthophoto or object packages may require additional terrain, models or effects.
- Extract the archive fully. FlightGear cannot load scenery from a ZIP, 7z or RAR archive. Keep custom scenery outside the main program installation so simulator updates do not mix it with bundled files.
- Find the scenery root. Select the folder directly containing directories such as
Terrain,ObjectsorAirports. If the structure isMyRegion/Scenery/Terrain, addMyRegion/Sceneryrather thanMyRegionor theTerrainfolder itself. - Add that root in the launcher. Use the launcher's additional scenery folders control; its exact wording and position can differ between FlightGear launcher releases. Command-line users can configure the same root with
--fg-scenery, while preserving any other required scenery entries. - Set the search priority. A custom airport or replacement terrain should be searched before TerraSync and default scenery when matching files overlap. Keep the TerraSync location available afterwards as fallback coverage.
- Restart FlightGear and test the covered area. Start at an airport inside the package's stated coverage rather than assuming a nearby region uses the same scenery tile.
Our detailed manual scenery installation walkthrough covers path selection and operating-system-specific checks in greater depth.
Should I use TerraSync or manual scenery?
Use TerraSync for convenient standard coverage and manual scenery when you need a specific enhancement, offline access or control over the installed data.
- Choose TerraSync if you fly in many areas and are happy for FlightGear to download scenery tiles as needed.
- Choose a manual package for an enhanced airport, custom terrain mesh, orthophotos or a region that must be available offline.
- Use both when custom scenery covers only part of the world and TerraSync can provide everything else.
Can custom FlightGear scenery work with TerraSync?
Yes. Keep custom packages and the TerraSync cache in separate folders, then place custom scenery earlier in the search order. Do not extract third-party files into the TerraSync cache because later synchronisation can replace files or leave an unpredictable mixture.
If automatic tiles are not downloading, check the cache location, write permissions and network configuration using our TerraSync configuration and troubleshooting steps.
Why is my FlightGear scenery not showing?
Scenery usually fails to appear because FlightGear has been given the wrong folder level or another scenery path is taking priority.
- Wrong root folder: the mistake we see most often is adding a directory one level above the actual
Sceneryroot. FlightGear does not recursively search arbitrary nested folders. - Archive still compressed: seeing the package in a file manager does not mean FlightGear can read it; extract it first.
- Incorrect priority: default or TerraSync files may be loaded before a replacement airport or terrain package.
- Incomplete package: object-only scenery may rely on separate terrain, while an orthophoto package may require components named in its documentation.
- Version or format mismatch: older scenery can load partially or fail when it depends on data formats, effects or models not present in the installed FlightGear release.
- Wrong test location: confirm the airport identifier or coordinates are inside the package's actual coverage.
FlightGear's log can reveal which scenery paths were searched and which tiles or resources were missing. If terrain appears but buildings do not, concentrate on the Objects data and dependencies rather than reinstalling the terrain immediately.
How do I update or remove manual scenery?
Install an update into a clean folder, verify it, then replace the old path entry rather than merging new files over an unknown older version. Keep only one version active to avoid priority conflicts. To remove scenery, delete its launcher path first; after confirming FlightGear starts normally, the package folder can be deleted without affecting TerraSync stored elsewhere.