fgfs - Man Page

Display usage information about the most relevant command-line options and exit.

When combined with --help/-h, display usage information about all command-line options, not just the most relevant ones.

Display version information about fgfs and some of the libraries used by the program (SimGear, OpenSceneGraph, PLIB), then exit.

Set the FlightGear data root directory ($FG_ROOT) to path. If this option is not set, fgfs uses the path specified in the FG_ROOT environment variable or, absent that, the FlightGear data directory chosen at the time the program was compiled.

Set the FlightGear scenery directories ($FG_SCENERY) to path.

You can specify multiple directories by separating them with colons (:), as in /first/path:/second/path (on Microsoft Windows operating systems, multiple paths should be separated by semicolons instead): in that case, fgfs will follow the order the paths are written in to search for scenery files, stopping as soon as a match is found.

If this option is not set, fgfs uses the path specified in the FG_SCENERY environment variable or, absent that, the Scenery subdirectory inside $FG_ROOT.

Load additional aircraft from path besides the Aircraft subdirectory inside $FG_ROOT. Alternatively, you can use --aircraft-dir to target a specific aircraft in a given directory.

Store aircraft and scenery downloaded via the simulator in path.

The TerraSync directory may be specifically set with the --terrasync-dir option.

Allow Nasal aircraft scripts to read files from the directories listed in dirs (separate multiple paths with colons, or semicolons on Microsoft Windows operating systems).

By default, Nasal scripts are allowed to read data only from $FG_ROOT and $FG_HOME, as a security measure.

Make $FG_HOME (the location where user-specific FlightGear data is stored) read-only.

Set the language used by the simulator to code, where code is an ISO 639-1 two-letter locale code (for example, en or it).

Reset all user settings to their defaults.

Save/do not save user settings when the program exits.

Ignore the user settings saved the previous time FlightGear was run. This option implies --disable-save-on-exit.

Use the Web browser specified in path to open aircraft documentation.

Set the property name to value. You can optionally specify the property type by setting type to string, double, float, long, int or bool.

Load additional configuration directives from path. The file should follow the format described in fgfsrc(5).

Do not load any configuration files unless they were explicitly specified with --config.

Use feet as the internal measure unit for distances.

Use meters as the internal measure unit for distances.

Display a console window for simulator/aircraft debugging purposes.

This option is recognized only on Microsoft Windows operating systems; on other systems, debug messages are always printed to standard output/standard error.

Start the FlightGear Launcher, a graphical Qt-based interface to the simulator.

This option is available only if FlightGear was compiled with Qt support enabled.

Print a report in JSON format on the standard output. The report will give useful information for debugging purposes, such as the FlightGear version, the scenery/aircraft paths in use, the TerraSync and the data download directories and the paths to navigation data files.

Enable/disable the pop-up aircraft instrument panel if the chosen airplane has it.

Enable/disable the heads-up display (HUD) if the chosen airplane has it.

Enable/disable heads-up display antialiasing.

Enable/disable the 3D version of the heads-up display.

Display the number of triangles rendered when painting the heads-up display.

Display the number of triangles culled when painting the heads-up display.

Show/hide random scenery objects, such as buildings. Scenery objects increase realism, but require more resources (memory and graphic card power).

Show/hide random vegetation.

Show/hide random buildings.

Enable/disable the internal AI subsystem, which is required for multiplayer gaming, AI traffic and many other animations. Disabling the internal AI subsystem is deprecated.

Enable/disable artificial plane traffic.

Add and enable the AI scenario scenario. This option may be repeated multiple times to enable multiple scenarios.

Start the simulator in a frozen (paused) state.

Start the simulator in a running (unpaused) state.

Do not consume any fuel (keep its quantity in the tanks constant).

Consume fuel normally.

Do not let the clock advance while running the simulation.

Let the clock advance normally.

Fail the aircraft pitot, static, vacuum or electrical systems. This option may be repeated multiple times to fail more than one system.

Load and replay the flight recorder tape tape.

Show a list of available audio devices and exit.

Set the sound device to use to name, where name is the device name shown by the --show-sound-devices option.

Enable/disable sound in the simulator.

Choose the terrain engine to use. tilecache is the "traditional" terrain engine (recommended); pagedLOD is a new, experimental terrain engine designed to minimize memory usage by loading more detailed versions of scenery objects on demand.

The pagedLOD engine is available only if FlightGear was compiled with GDAL support.

Set the level of detail levels to levels, where levels is a space-separated list of numeric levels. This option is available only if the terrain engine in use is pagedLOD.

Set the terrain mesh resolution to resolution. This option is available only if the terrain engine in use is pagedLOD.

Set the terrain texture method. This option is available only if the terrain engine in use is pagedLOD.

Set the range multiplier (the breakpoint from a low to a high level of detail) to multiplier. This option is available only if the terrain engine in use is pagedLOD.

Enable/disable the Rembrandt engine, which adds deferred shading (rendering all properties of an object, such as shading, lighting, fog) in more than one pass.

If the Rembrandt engine is enabled, use the rendering pipeline described in $FG_ROOT/Effects/name.xml.

Show/hide the simulator splash screen while loading the aircraft/scenery.

Force enable display/do not force display the mouse pointer at startup.

Limit the maximum frame rate of the simulator to frequency Hz (frames per second).

Use a color depth of depth bits per pixel to display the aircraft and scenery.

Choose the fog/haze rendering technique. --fog-disable will disable fog/haze entirely; --fog-fastest will explicitly ask the graphics card driver to choose the most efficient, but possibly less accurate, fog/haze rendering algorithm; --fog-nicest will leave the algorithm choice to the driver, leading to higher quality results.

Enable/disable enhanced runway lighting. This option is deprecated.

Enable/disable runway light distance attenuation (the runway lights become less intense as distance increases).

Enable/disable the celestial body growth illusion near the horizon.

Enable/disable specular reflections on textured objects.

Set the field of view angle (FOV) to degrees. High field of view angles allow you to see a wider part of the world; low angles allow you to "zoom in" on details.

Set the horizontal and vertical aspect ratio multiplier to factor.

Enable/disable fullscreen mode.

Use flat/smooth shading. If flat shading is active, the simulator uses the same color to paint the face of an object: this is faster, but makes edges more pronounced. Smooth shading smooths color changes between vertices, leading to higher-quality results, at an expense in performance.

Load the definitions of the materials used to render the scenery from file. By default, materials are loaded from $FG_ROOT/regions/materials.xml.

Set the anisotropic texture filtering to value. The acceptable values are 1 (default), 2, 4, 8 or 16.

Enable/disable the wireframe drawing mode (in which only object edges are painted).

Set the window geometry (size) to widthxheight (both width and height are in pixels).

Specify the default forward view direction as an offset from straight ahead. The allowed values are LEFT (-90°), RIGHT (90°), CENTER (0°) or a specific number in degrees.

Load an aircraft/vehicle from a set file named name-set.xml. The file is searched for in $FG_ROOT/Aircraft, in the directory pointed to by the environment variable FG_AIRCRAFT and in the directories passed to fgfs(1) using the --fg-aircraft option.

Explicitly specify the directory in which the -set.xml file should be searched for. If this argument is used, the path cache stored in ~/.fgfs/autosave_X_Y.xml, the directories passed with the --fg-aircraft option and the directory specified in the FG_AIRCRAFT environment variable are not taken into account.

Print a list of available aircraft and exit.

Do not list aircraft having a status level (development status) lower than the one specified. See the FlightGear wiki "Aircraft rating system" page for an extended description of aircraft ratings.

Select the core flight dynamics model to use among the following ones:

• jsb: the JSBSim flight dynamics model, which takes a data-driven approach to modeling: given the performance data for an aircraft (mass and balance, ground reactions, propulsions, aerodynamics...), it assembles it together to produce the global aircraft dynamics;
• larcsim: the LaRCsim flight dynamics model, the original model used in FlightGear up to 2000, developed at NASA, now inactive;
• yasim: the YASim flight dynamics model, which, given the physical and flying characteristics of an aircraft, attempts to solve for them;
• magic: the "Magic Carpet" flight model;
• balloon: a hot air balloon simulation;
• ada: an externally-driven flight dynamics model designed by the Aeronautical Development Agency of Bangalore, India;
• external/null: use an external flight dynamics model (the external option has the same meaning as null and is maintained for backward compatibility purposes).

Load the aircraft aerodynamics model from the file name.xml in the aircraft directory.

Run the flight dynamics model at a frequency of n Hz (n times per second).

Run the flight dynamics model n times faster than real time.

Trim/do not attempt to trim the model. This option is only valid if the flight dynamics module in use is JSBSim.

Start the aircraft on the ground. This is the default option.

Start the aircraft in the air. This option is implied if --altitude is specified.

Enable/disable auto coordination (joint control of rudder and ailerons).

Load the aircraft livery from a file named name.

Set the initial aircraft state to value. The states that can be used are aircraft-dependent.

Start the simulator at the specified time of day:

• real: real clock time;
• dawn: the time when the Sun is 90° E on the horizon;
• morning: the time when the Sun is 75° E on the horizon;
• noon: the time when the Sun is 0° on the horizon;
• afternoon: the time when the Sun is 75° W on the horizon;
• dusk: the time when the Sun is 90° W on the horizon;
• evening: the time when the Sun is 100° W on the horizon;
• midnight: the time when the Sun is 180° on the horizon.

Load summer/winter textures.

Add a time offset to the startup time specified with the --timeofday option.

Synchronize the simulator time with real world GMT time.

Synchronize the simulator time with real world local time.

Specify the simulator starting date and time with respect to the local timezone of the system.

Specify the simulator starting date and time with respect to the Greenwich Mean Time.

Specify the simulator starting date and time with respect to the timezone of the starting airport.

Start the simulator at the airport having ID as its ICAO code.

Place the aircraft at the parking position name. This option requires the --airport option to be present.

Place the aircraft on runway number. This option requires the --airport option to be present.

Place the aircraft on the AI carrier named name/having the ID ID.

Place the aircraft at the starting position name. This option requires the --carrier option to be present.

Place the aircraft over the VOR ID.

Set the frequency of the VOR to frequency. This option requires the --vor option to be present.

Place the aircraft over the NDB ID.

Set the frequency of the NDB to frequency. This option requires the --ndb option to be present.

Place the aircraft over the fix ID.

Place the aircraft nm statute miles away from the reference point specified by the previous options.

Place the aircraft at a heading of degrees degrees with respect to the reference point specified by the previous options.

Place the aircraft at the point with the coordinates (lat, lon). Northern longitudes/eastern latitudes must be positive; southern longitudes/western latitudes must be negative.

Place the aircraft at an altitude of value feet (meters if the --units-meters option was specified).

Specify the initial heading (yaw) angle (psi) of the aircraft.

Specify the initial roll angle (phi) of the aircraft.

Specify the initial pitch angle (theta) of the aircraft.

Specify the initial velocity along the body X axis.

Specify the initial velocity along the body Y axis.

Specify the initial velocity along the body Z axis.

Specify the initial velocity along the body North-South axis.

Specify the initial velocity along the body West-East axis.

Specify the initial velocity along the body vertical axis.

Set the initial airspeed of the aircraft to knots knots.

Set the initial airspeed of the aircraft to Mach number.

Set the flight path angle to degrees degrees. The value can be positive.

Set the initial rate of climb to fpm feet per minute. The value can be negative.

Enter the waypoint (VOR, NDB, fix) ID into the autopilot. The optional part @alt can be used to specify the altitude at which ID should be crossed.

Read a flight plan from file.

Set the COM1 frequency to frequency MHz.

Set the COM2 frequency to frequency MHz.

Set the NAV1 frequency to frequency MHz. You can optionally specify a radial by prefixing the frequency with the heading and a colon.

Set the NAV2 frequency to frequency MHz. You can optionally specify a radial by prefixing the frequency with the heading and a colon.

Set the ADF1 frequency to frequency kHz. You can optionally specify the rotation angle of its compass card by prefixing the frequency with the angle and a colon. The --adf option is deprecated.

Set the ADF2 frequency to frequency kHz. You can optionally specify the rotation angle of its compass card by prefixing the frequency with the angle and a colon.

Slave the automatic direction finder to the NAV1/NAV2 radio or set its internal frequency to frequency.

Simulate the weather conditions described by the METAR string METAR. This option implies --disable-real-weather-fetch.

Enable/disable METAR-based real weather fetching. This feature requires an active Internet connection.

Enable/disable 2D (flat) cloud layers.

Enable/disable 3D (volumetric) cloud layers.

Set the initial visibility to meters meters.

Set the initial visibility to miles miles.

Specify the direction the wind blows from (dir) and its speed (speed knots). If the wind is not meant to blow from a fixed direction, but rather from a range of directions, specify the range as dir:maxdir, where dir and maxdir are the minimum and maximum angles in degrees. If you want the simulator to model wind gusts as well, set gust to their maximum intensity in knots.

Randomize the direction and speed of the wind.

Set the turbulence intensity to intensity. The intensity can range from 0.0 (calm) to 1.0 (severe).

Create an overcast ceiling at a height of ft_asl feet above the mean sea level. You can optionally specify a thickness by appending a colon (:) and the desired thickness in feet; if you omit it, the simulator will default to 2000 ft.

Set the multiplayer callsign to value. The callsign must be at most ten characters long and must contain only numbers, letters of the English alphabet, dashes (-) and underscores (_); longer callsigns are truncated, and characters not matching those listed above are replaced with dashes.

Specify the multiplayer communication settings.

The first field specifies whether the settings apply to inbound (in) or outbound (out) communications. The second field (hz) specifies the frequency (in Hz, times per second) at which data should be sent. The third field (address) must be set to the IP address of the network interface that FlightGear should use to send/receive data, or left blank to let the simulator use all available interfaces. The fourth field (port) should be set to the port to use (usually 5000).

Specify the proxy server and port to use. The username and password are optional; if they are present, they should be given as MD5 hashes.

This option is only useful if --real-weather-fetch is enabled.

Enable the Phi interface (HTTP server) on the specified address and port. The address is optional.

Enable the Telnet interface on the specified port.

Enable the screenshot HTTP server interface on the specified port. This option is deprecated: use the Phi interface instead.

Enable/disable automatic scenery/object downloads.

Set the directory where the downloaded scenery will be stored to directory.

Enable/disable the FGCom (voice ATC) integration.

Open a connection to drive external programs or hardware.

Specify the protocol by using the correct command-line option:

• generic: a predefined communication interface and a preselected communication protocol;
• atlas: the Atlas protocol;
• atcsim: the ATCsim (atc610x) protocol;
• AV400: the Garmin AV400 protocol, required to drive a Garmin 196/296 series GPS;
• AV400Sim: the set of AV400 strings required to drive a Garmin 400-series GPS;
• AV400WSimA, AV400WSimB: the set of strings required to drive a Garmin WAAS GPS (where the A channel uses a variant of the AVSim400 protocol and the B channel communicates with the GPS unit);
• garmin: the Garmin GPS protocol;
• hla, hla-local: the HLA protocol, either remote or local;
• igc: the International Glider Commission protocol;
• joyclient: the protocol used by Agwagon joysticks;
• native-ctrls: the FlightGear Native Controls protocol;
• native-gui: the FlightGear Native GUI protocol;
• native-fdm: the FlightGear Native FDM protocol;
• native: the FlightGear Native protocol;
• nmea: the NMEA protocol (used to drive most GPS units);
• opengc: the protocol used by OpenGC, a software used to render high-quality glass cockpit displays for simulated flightdecks;
• props: the interactive property manager protocol;
• pve: the PVE protocol;
• ray: the Ray Woodworth motion chair protocol;
• rul: the RUL protocol.

The parameters (params) must be in the form medium,direction,hz,medium_options where medium is the medium used by the protocol (serial, socket, file...), direction is the communication direction (in, out or bi), hz is the frequency the channel should be processed at (floating point values are accepted) and medium_options are:

• for serial protocols, device,baud, where device is the device name to be opened and baud is the communication baud rate;
• for socket protocols, machine,port,style, where machine is the machine name or the IP address of the server (if the simulator should act as a client) or is left empty (if the simulator should act as a server), port is the port to use (or is left empty to ask the operating system to choose an available port) and style is tcp or udp;
• for file protocols, filename, where filename is the name of the file data should be written to.

Abort when a floating-point exception is encountered.

View the scenery and the aircraft in a simple model viewer, without loading the entire simulator.

Set the minimum logging level. Log messages having a severity greater than or equal to the specified value are recorded; the others are discarded.

Log only events belonging to the specified log classes (all logs all events, none logs none). Multiple classes can be specified by separating them with commas or pipes, for example: --log-class=ai,flight.

Save the logs in the directory dir. If dir is desktop, the logs are saved on the Desktop. This option may be given several times, using a different directory each time. Inside the specified directory, the log file will be named FlightGear_YYYY-MM-DD_num.log, where YYYY-MM-DD is the current date and num is a progressive number starting at 0.

Trace the reads/writes for a property (print a log message whenever property is read from/written to).

Enable developer mode.