What are FlightGear data files and how do I fix errors?

FlightGear data files are the simulator’s non-program resources: configuration, aircraft definitions, instruments, textures, sounds, navigation databases and scenery. A missing-data-file error usually means the data root points to the wrong folder, an archive remains compressed, an add-on is incomplete, or scenery sits outside FlightGear’s configured search paths.

What are FlightGear data files?

The FlightGear executable runs the simulation, but it cannot work without a matching collection of resource files. The main resource tree is commonly called FGData, while FG_ROOT means the path FlightGear uses to find that tree.

A valid data-root folder normally contains defaults.xml directly inside it, alongside resource subfolders. World scenery and downloadable aircraft may use separate search paths, so downloading more scenery will not repair a missing core file such as defaults.xml, a shader or a Nasal script.

How do I identify which FlightGear data path is broken?

The first missing pathname in FlightGear’s log or console usually identifies the broken subsystem; later messages may only be consequences of that initial failure.

• An error mentioning defaults.xml, Nasal, Shaders, Textures, Fonts or common sounds usually points to an incorrect or incomplete data root.
• A path containing Aircraft or a missing *-set.xml, model, cockpit or livery file normally means one aircraft package is incomplete or nested incorrectly.
• References to Terrain, Objects, airport data or scenery tiles indicate a scenery-path problem rather than a damaged FlightGear installation.
• Permission denied is not the same as file not found. The file may exist but be unreadable by the account running FlightGear.

How do I repair the FlightGear data root?

Fix core-data errors by restoring a complete data package that matches the FlightGear executable, then point the simulator at the folder containing defaults.xml.

1. Record the first error. Copy the first missing filename and its expected path before changing anything. This prevents an aircraft or scenery fault from being mistaken for a broken base installation.
2. Extract every archive fully. FlightGear cannot use its resource tree while it remains inside a ZIP or similar archive. Preserve the supplied folder structure rather than extracting selected files; our base FlightGear package and extraction notes cover this requirement.
3. Select the correct folder level. The configured data root must be the directory that directly contains defaults.xml. A mistake we see constantly is selecting its parent, leaving FlightGear looking one directory too high.
4. Check saved path overrides. Remove or correct an obsolete FG_ROOT environment variable, launcher option or shortcut left by an older installation. For command-line diagnosis, the relevant option is --fg-root="/absolute/path/to/data"; quote paths containing spaces.
5. Match the executable and data release. Do not combine a FlightGear binary from one release with FGData from another. If you compiled FlightGear yourself, its source code and matching data tree are separate components.
6. Check permissions. The account running FlightGear needs read access to every data subfolder. Avoid protected or administrator-owned locations when using a manually extracted installation.
7. Repair the complete installation if files are absent. Reinstall the executable and base data together rather than downloading individual missing scripts or textures. On package-managed Linux systems, repair both components through the same package manager instead of mixing packaged files with an unrelated manual data tree.

What if only one aircraft reports missing files?

If FlightGear starts with a supplied aircraft but fails with one add-on, leave FG_ROOT

• Make the aircraft search path point to the parent directory containing the aircraft folders, not to an archive or an unrelated folder above them.
• Open the aircraft folder and confirm its *-set.xml file is present. Extra nesting such as Aircraft/Aircraft/MyAircraft is a common extraction error.
• Preserve filename capitalisation. Paths that appear to work on a case-insensitive file system can fail on Linux.
• Re-extract the whole aircraft if a model, instrument or sound is missing. Copying one file from another release can create further dependency errors.

What if the missing data belongs to scenery?

A scenery-only error is fixed by correcting the scenery search path or restoring the affected scenery tile, not by changing the core data root.

For manually installed scenery, select the parent directory containing folders such as Terrain and Objects, rather than selecting an individual tile or the Terrain folder itself. Our guide to the correct FlightGear scenery-folder structure and search-path setup explains extraction, TerraSync, permissions and missing-object problems.

Missing optional scenery generally causes ocean, absent terrain or missing objects while the simulator continues to run. TerraSync can obtain supported scenery when enabled and able to connect, but it cannot replace missing base data, aircraft models or shaders.

How do I know the data-file repair worked?

The repair is successful when FlightGear starts with its supplied aircraft and location without reporting a base-package failure.

• Test the unmodified default setup before enabling downloaded aircraft or scenery.
• Check that the first missing-file message has disappeared rather than concentrating on harmless later warnings.
• Restore additional aircraft and scenery paths one at a time. If the error returns, the last path or package added is the likely cause.

If FlightGear still cannot reach the launcher or simulation after its data root has been verified, use our broader FlightGear start-up troubleshooting checklist to check graphics initialisation, saved settings and installation damage.