Set up FlightGear for the first time: install it, configure scenery and controls, choose an aircraft, tune graphics and fix common launch problems.
To get started with FlightGear, install a stable build for your operating system, open FlightGear Launcher, select the Cessna 172P and a runway, enable automatic scenery downloads, configure and test your controls, then begin with engines running, clear weather and modest graphics settings. Change one setting at a time after that.
FlightGear first-time setup, step by step
FlightGear Launcher brings the aircraft, location, environment and simulator settings together, although labels and their positions can vary between releases and operating-system packages.
- Install one complete FlightGear release. Use the package intended for your operating system and keep its application and base data together. Windows users can follow our complete FlightGear installation walkthrough. Do not combine a new executable with an old base data package.
- Open FlightGear Launcher. Confirm that it displays the included aircraft. If it asks for a data directory, select the base package supplied with the same release, commonly called
FGData, rather than a scenery cache or an individual aircraft folder. - Select the Cessna 172P. It is a forgiving trainer with conventional controls. If the selected aircraft offers an engine-running start, use it for the initial test.
- Choose a runway start. Search for an airport by name or ICAO code, select a runway and use daylight with clear weather and little wind. Parking positions can produce a cold-and-dark start or place the aircraft somewhere awkward.
- Configure scenery downloads. Enable TerraSync and give its cache a writable location with adequate free space. Keep that cache outside protected application directories; our TerraSync setup instructions cover the available choices.
- Test the controls before moving. Check pitch, roll, rudder and throttle from the cockpit or input display. Make sure each axis moves in the correct direction and is assigned only once. Use our FlightGear control configuration guide if a joystick, yoke or throttle is not detected correctly.
- Leave advanced graphics settings alone initially. Start with the default renderer and moderate shadows, cloud detail, visibility and anti-aliasing. Establish a working baseline before increasing quality.
- Run a short ground test. Release the parking brake, apply a little power, confirm steering and braking, then return the throttle to idle. Only attempt take-off once every primary control responds properly.
A mistake we see constantly is adding aircraft, custom scenery and experimental launch options before the standard installation has completed one successful flight. Test the unmodified simulator first; faults are much easier to isolate that way.
Which aircraft and airport should I choose first?
The Cessna 172P at a quiet, uncomplicated airport is the best first-flight combination for most FlightGear users.
Choose a paved runway long enough to leave room for an imperfect take-off, and avoid strong winds, poor visibility, carrier operations, helicopters and complex airliners. An airport near scenery already present in the cache also removes network downloads from the first test.
Once the installation and controls work, follow our Cessna 172 first-flight procedure for starting, taxiing, taking off and establishing a stable climb.
Do I need a joystick to start FlightGear?
No; keyboard and mouse controls are sufficient to verify that FlightGear works, but an analogue joystick or yoke makes pitch and roll far easier to manage.
For an initial controller profile, assign only the four essentials: pitch, roll, rudder and throttle. Add mixture, propeller, trim and view controls later. If an axis jitters while untouched, calibrate it through the operating system and add only a small dead zone; an excessive dead zone makes the aircraft difficult to control near the centre.
Check for duplicate assignments when the throttle moves backwards, the rudder snaps to one side or the brakes remain partly applied. Gamepads and unused controllers can claim an axis automatically, so disconnecting them is a useful diagnostic step.
How should I set up FlightGear scenery and graphics?
Use TerraSync for scenery and conservative graphics settings until the simulator has loaded the same airport successfully more than once.
TerraSync retrieves terrain around the selected location and stores it in its cache. A first visit can therefore take longer or briefly show flat terrain, water or missing detail. If you intend to fly without an internet connection, allow the required tiles to finish downloading beforehand.
For poor frame rate, reduce shadows, cloud detail, visibility and anti-aliasing one at a time. Changing several settings together makes it difficult to identify the expensive option. A black or blank window is more likely to involve the graphics driver, an unsupported advanced option or damaged saved preferences than missing scenery.
Why is the first FlightGear launch slow or broken?
The first launch can take longer while FlightGear prepares caches and downloads scenery, but repeated stalls usually point to mismatched base data, an unwritable cache, graphics settings or conflicting controls.
| Symptom | Likely cause | First fix |
|---|---|---|
| No aircraft appear in the launcher | Missing or mismatched base data | Reinstall the complete package and ensure the launcher uses the matching FGData. |
| Airport appears in water or terrain is missing | The scenery tile has not downloaded | Check TerraSync, the network connection, cache permissions and available storage, then allow the tile to finish. |
| Aircraft ignores or fights the controls | Wrong input mode, reversed axis or duplicate binding | Test one controller at a time and clear duplicate assignments. |
| Aircraft will not taxi | Parking brake, wheel brakes, engine state or throttle assignment | Confirm the engine is running, release the parking brake and inspect the throttle and brake inputs. |
| Black, white or crashing display | Graphics driver or incompatible saved option | Return graphics settings to defaults, restart with clean user preferences and check the installed graphics driver. |
| Scenery downloads again every session | Cache path is changing or cannot be written | Select one permanent user-writable cache directory and verify that files remain there after closing FlightGear. |
The first-time setup is complete when the cockpit loads reliably, local terrain appears, every primary control moves correctly and the aircraft can taxi without unexpected braking or steering. At that point, add graphics features, live weather, more aircraft and extra scenery individually so any new problem has an obvious cause.