FlightGear wiki - User contributions [en]

Command line options

2023-04-21T11:31:53Z

FurryMLG:

'''Command line options''' are a common way to tell applications what to do/how to act on startup. With [[FlightGear]] they are used for many things, from simple ones like selecting an aircraft up to complex stuff like network traffic and weather parameters.

The easiest way to handle those options for FlightGear is using a tool with a graphical user interface like the [[FlightGear Qt launcher]]. This way one doesn't have to bother about them at all.

However, there are users who don't want or are not able to run a GUI and therefore are interested in this. Those who need them or just want to learn more about FlightGear, but have no idea what we are talking about, may read the wiki page on the general usage of the [[command line]]. The launcher GUI works by setting command-line options for the options you choose. Try different options and see what the launcher sets from menu in Qt launcher <code>*** > View command-line</code> or by use {{Key press|Ctrl|L}} keyboard shortcut.

A good place to store the personal options is a file called [[fgfsrc]]. This file is read by FlightGear on each startup.

The following lists show the options for FlightGear including a short description and sorted by categories. Please have in mind that keeping those lists up to date on the wiki is not an easy task. Also there are different versions of FlightGear out there which don't share exactly the same options. Therefore you better also check your versions ones with <code>fgfs --help --verbose</code>. If this command fails, you may add the option <code>--fg-root=[path]</code> as well, see below.

It is sad but true, not even this command is, at least in Git, up to date all the time. At the time of writing at least one option which is supported is not shown with <code>fgfs --help --verbose</code>. So if you have serious issues with an option, the source code is, as always, also the best source for info. In the file ''src/Main/options.cxx'' all the options are listed with their hard coded ''default'' setting and type.

The file [[$FG_ROOT]]/options.xml is used to generate the output for <code>fgfs --help [--verbose]</code>. That's the reason why <code>--fg-root=[path]</code> has to be added to this, if it is not set as environmental variable or as option in fgfsrc.

Note that some command line options are not listed. The complete list can be found by examining the sources
*{{fgdata file|options.xml}}

Usage in terminal: <code>fgfs [OPTION [OPTION ...]]</code>

The way to use options by [[FlightGear Qt launcher|Qt Launcher]]: go to the "Settings" tab and in the "Additional Settings" section enter the following options, each on a new line. The options entered there take precedence over those defined by Qt Launcher. To see the entire list of command line options used by Qt Launcher, use the keyboard shortcut {{Key press|Ctrl|L}} or select "View command-line" from the Launcher menu.

= Legend how to read the following options =

# <code>--option1</code> (<code>--option2</code>) - in this case <code>--option2</code> is the aliast for <code>--option1</code> which is exactly the same as <code>--option1</code>.
# <code>--option1</code> <code>--option2</code> - two different options, mutually exclusive. They cannot be used simultaneously, but are connected due to a common description.
# <code>--option1</code>, <code>--option2</code> - two different options that can be used simultaneously and are connected due to a common description.

= General Options =

<code>--help</code> (<code>-h</code>)
::Show the most relevant command line options.

<code>--verbose</code> (<code>-v</code>)
::Show all command line options when combined with <code>--help</code> or <code>-h</code>.

<code>--version</code>
::Display the current FlightGear version.

<code>--fg-root=path</code>
::Specify the root data path.

<code>--fg-scenery=path[:path...]</code>
::Specify the base scenery path. Defaults to [[$FG_ROOT]]/Scenery.

<code>--fg-aircraft=path</code>
::Specify additional aircraft directory path(s) (alternatively, you can use <code>--aircraft-dir</code> to target a specific aircraft in a given directory).

<code>--addon=path</code>
::Specify a path to addon. Multiple instances can be used.

<code>--download-dir=path</code>
::Store aircraft and scenery downloaded via the simulator in path. The TerraSync directory may be specifically set with the <code>--terrasync-dir</code> option.

<code>--data=path</code>
::Specify an additional base data directory (FGData), before the [[$FG_ROOT]] directory.

<code>--enable-terrasync</code> 
<code>--disable-terrasync</code>
::Enable/disable automatic scenery downloads/updates.

<code>--terrasync-dir=path</code>
::Specify the [[TerraSync]] scenery path. Defaults to [[$FG_HOME]]/TerraSync.

<code>--language=code</code>
::Select the language for this session. Available codes: <tt>ca</tt>, <tt>de</tt>, <tt>en</tt>, <tt>es</tt>, <tt>fr</tt>, <tt>it</tt>, <tt>nl</tt>, <tt>pl</tt>, <tt>pt</tt>, <tt>ru</tt>, <tt>tr</tt>, <tt>sk</tt>, <tt>zh</tt>.

<code>--launcher</code>
::Run [[FlightGear Qt launcher|Qt Launcher]]. Without this option, it will immediately start the simulator in the default configuration or in the configuration read from the [[Fgfsrc|fgfsrc]] file - if it exists.

<code>--enable-splash-screen</code> 
<code>--disable-splash-screen</code>
::Enable/disable splash screen.

<code>--enable-mouse-pointer</code> 
<code>--disable-mouse-pointer</code>
::Enable/disable extra mouse pointer (i.e. for full screen Voodoo based cards).

<code>--browser-app=path</code>
::Specify path to your web browser.

<code>--prop:[type:]property=value</code>
::Set the given property to the given value. Type can be one of <tt>string</tt>, <tt>double</tt>, <tt>float</tt>, <tt>long</tt>, <tt>int</tt>, or <tt>bool</tt>.

<code>--prop:browser=property</code>
::After starting the simulator, open the properties dialog immediately on the given property. If you need more windows, just add more browser indexes like <tt>browser[1]</tt>, <tt>browser[2]</tt> etc., for example:
--prop:browser=/sim/presets
--prop:browser[1]=/devices/status/keyboard/event
which will open two dialogs with the given properties.

<code>--config=path</code>
::Load additional properties from path.

<code>--no-default-config</code>
::Do not load any default configuration files (like [[Fgfsrc|fgfsrc]]) unless explicitly specified with <code>--config</code>.

<code>--units-feet</code> 
<code>--units-meters</code>
::Use feets (default) or meters for distances.

<code>--allow-nasal-read=path[:path...]</code>
::Allow Nasal scripts to read files from directories listed as path (separate multiple paths with a semicolon (Windows) or a colon (UNIX)). By default, for security reasons, Nasal scripts can only read data from certain directories, such as [[$FG_ROOT]], [[$FG_HOME]], etc.

<code>--read-only</code>
::Make [[$FG_HOME]] read-only.

<code>--ignore-autosave</code>
::Ignore the autosave file, i.e. the settings saved in this file will not be loaded during startup, nor will the settings be saved to this file when closing the simulator.

<code>--enable-save-on-exit</code> 
<code>--disable-save-on-exit</code>
::Allow/Disallow save preferences upon program exit.

<code>--restore-defaults</code>
::Reset all user settings to their defaults (rendering options etc.)

<code>--disable-gui</code>
::Enable headless mode.

<code>--jsbsim-output-directive-file=file</code>
::Log JSBSim properties. An output directives file contains an <code><output></code> element, within which should be specified the parameters or parameter groups that should be logged. See [[JSBSim Logging]].

= Features =

<code>--composite-viewer={1|0}</code>
::Enable (1), disable (0) CompositeViewer (extra view windows).

<code>--enable-panel</code> 
<code>--disable-panel</code>
::Enable/disable 2D instrument panel.

<code>--enable-freeze</code> 
<code>--disable-freeze</code>
::Start in a pause state or unpause.

<code>--enable-fuel-freeze</code> 
<code>--disable-fuel-freeze</code>
::Fuel tank quantity forced to remain constant or fuel is consumed normally.

<code>--enable-clock-freeze</code> 
<code>--disable-clock-freeze</code>
::do not advance clock or clock advances normally.

<code>--ai-scenario=scenario</code>
::Add and enable a new scenario. Multiple options are allowed. Scenarios are in [[$FG_ROOT]]/AI/.

<code>--enable-ai-models</code> 
<code>--disable-ai-models</code>
::Enable/disable the AI subsystem. When disabled this also disables showing the models of other multiplayer aircraft.

<code>--enable-ai-traffic</code> 
<code>--disable-ai-traffic</code>
::Enable/disable the autogenerated traffic subsystem.

<code>--enable-vr</code> 
<code>--disable-vr</code>
::Enable/disable the Virtual Reality.

<code>--restart-launcher</code>
::Open Launcher automatically when exiting the FlightGear.

<code>--load-tape={name|url}</code>
::Load recording of earlier flightgear session. For <name>, if <name> ends with .fgdata it is treated as the local path of the recording file; otherwise we form the local path by prepending <name> with the tape directory and appending ".fgtape". For <url> (starting with http:// or https://) we download the remote recording (which must be a Continuous recording) in the background to a url-dependent filename while replaying it; if the url-dependent filename already exists it is assumed to be a truncated download and we only download any remaining data.

<code>--load-tape-create-video</code>
::Encode video while replaying tape specified by <code>--load-tape</code>.

<code>--load-tape-fixed-dt=value</code>
::Set fixed-dt mode while replaying tape specified by <code>--load-tape</code>.

= Aircraft =

<code>--aircraft=name</code> (<code>--vehicle=name</code>)
::Select an aircraft profile as defined by a top level -set.xml.

<code>--aircraft-dir=path</code>
::Specify the exact directory to use for the aircraft (normally not required, but may be useful). Interpreted relatively to the current directory. Causes the <code><path-cache></code> from autosave_X_Y.xml, as well as <code>--fg-aircraft</code> options and the FG_AIRCRAFT environment variable to be bypassed.

<code>--show-aircraft</code>
::Print a list of the currently available aircraft types.

<code>--min-status={alpha|beta|early-production|production}</code>
::Allows you to define a minimum status level (=development status) for all listed aircraft.

<code>--enable-auto-coordination</code> 
<code>--disable-auto-coordination</code>
::Enable/disable auto coordination. Disabled as default. If enabled, the rudder will respond according to the movement of the ailerons.

<code>--livery=name</code>
::Select aircraft livery.

<code>--state=value</code>
::Specify the initial state of the aircraft to the given value. The states that can be used depend on the aircraft. For example, the Cessna 172P has only one state: <tt>auto</tt>.

= Flight Model =

<code>--fdm={ada | acms | aisim | balloon | jsb | larcsim | magic | network | pipe | ufo | yasim | external | null}</code>
::Select the core flight dynamics model.

<code>--aero=name</code>
::Select aircraft aerodynamics model to load.

<code>--model-hz=n</code>
::Run the FDM this rate (iterations per second).

<code>--speed=n</code>
::Run the FDM 'n' times faster than real time.

<code>--trim</code> 
<code>--notrim</code>
::Trim or do not attempt to trim the model (only with <code>--fdm=jsbsim</code>).

<code>--on-ground</code> 
<code>--in-air</code>
::Start at ground level (default) or in air (implied when using <code>--altitude</code>).

= Initial Position and Orientation =

<code>--airport=ICAO</code>
::Specify airport (e.g. KOAK).

<code>--runway=rwy_no</code>
::Specify starting runway (must also specify an airport).

<code>--parking-id=name</code> (<code>--parkpos=name</code>)
::Specify a gate at the airport (e.g. 747d11).

<code>--carrier={name|ID}</code>
::Specify starting position on an AI carrier.

<code>--carrier-position={abeam|FLOLS|name}</code>
::Specify a starting position relative to the carrier where you can use the predefined <tt>abeam</tt> (start on downwind abeam) or <tt>FLOLS</tt> (start on final approach) values, or specify the name of the carrier's parking position. Must also specify a carrier by <code>--carrier</code>.

<code>--vor=ID</code>
::Specify starting position relative to a VOR.

<code>--vor-frequency=frequency</code>
::Specify the frequency of the VOR. Use with <code>--vor=ID</code>.

<code>--ndb=ID</code>
::Specify starting position relative to an NDB.

<code>--ndb-frequency=frequency</code>
::Specify the frequency of the NDB. Use with <code>--ndb=ID</code>.

<code>--fix=ID</code>
::Specify starting position relative to a fix.

<code>--offset-distance=nm</code>
::Specify distance to reference point (nautical miles).

<code>--offset-azimuth=degrees</code>
::Specify heading to reference point.

<code>--lon=degrees</code>
::Starting longitude (west = -).

<code>--lat=degrees</code>
::Starting latitude (south = -).

<code>--altitude=value</code>
::Starting altitude (in feet unless <code>--units-meters</code> specified).

<code>--heading=degrees</code>
::Specify heading (yaw) angle (Psi).

<code>--roll=degrees</code>
::Specify roll angle (Phi).

<code>--pitch=degrees</code>
::Specify pitch angle (Theta).

<code>--vc=knots</code> 
<code>--mach=num</code>
::Specify initial airspeed in knots or mach number.

<code>--glideslope=degrees</code>
::Specify flight path angle (can be positive).

<code>--roc=fpm</code>
::Specify initial climb of rate (can be negative).

<code>--uBody=units_per_sec</code>
::Specify velocity along the body X axis (in feet unless <code>--units-meters</code> specified).

<code>--vBody=units_per_sec</code>
::Specify velocity along the body Y axis (in feet unless <code>--units-meters</code> specified).

<code>--wBody=units_per_sec</code>
::Specify velocity along the body Z axis (in feet unless <code>--units-meters</code> specified).

<code>--vNorth=units_per_sec</code>
::Specify velocity along a South-North axis (in feet unless <code>--units-meters</code> specified).

<code>--vEast=units_per_sec</code>
::Specify velocity along a West-East axis (in feet unless <code>--units-meters</code> specified).

<code>--vDown=units_per_sec</code>
::Specify velocity along a vertical axis (in feet unless <code>--units-meters</code> specified).

= Audio Options =

<code>--show-sound-devices</code>
::Show a list of available audio device.

<code>--sound-device=name</code>
::Explicitly specify the audio device to use. To get available names use <code>--show-sound-devices</code>.

<code>--enable-sound</code> 
<code>--disable-sound</code>
::Enable/disable sound.

= Rendering Options =

<code>--prop:/sim/rendering/multi-sample-buffers={true|false}</code>
::Enable/disable multi sample buffer (anti-aliasing).

<code>--prop:/sim/rendering/multi-samples=value</code>
::Specify number of multi samples (anti-aliasing). Valid values is 2, 4, 8, 16.

<code>--aspect-ratio-multiplier=factor</code>
::Specify a multiplier for the aspect ratio.

<code>--bpp=depth</code>
::Specify the bits per pixel.

<code>--compositor=path</code>
::Specify the path to XML file for multi-pass rendering. The path is relative to [[$FG_ROOT]] (defaults to <tt>Compositor/default.xml</tt>).

<code>--enable-horizon-effect</code> 
<code>--disable-horizon-effect</code>
::Enable/disable celestial body growth illusion near the horizon.

<code>--enable-distance-attenuation</code> 
<code>--disable-distance-attenuation</code>
::Enable/disable runway light distance attenuation.

<code>--enable-specular-highlight</code> 
<code>--disable-specular-highlight</code>
::Enable/disable specular reflections on textured objects.

<code>--enable-clouds</code> 
<code>--disable-clouds</code>
::Enable/disable 2D (flat) cloud layers.

<code>--enable-clouds3d</code> 
<code>--disable-clouds3d</code>
::Enable/disable 3D (volumetric) cloud layers.

<code>--enable-texture-cache</code> 
<code>--disable-texture-cache</code>
::Enable/disable texture cache (DDS).

<code>--texture-cache-dir=path</code>
::Set the DDS texture cache directory to be different than the default location.

<code>--enable-fullscreen</code> 
<code>--disable-fullscreen</code>
::Enable/disable fullscreen mode.

<code>--enable-random-objects</code> 
<code>--disable-random-objects</code>
::Include/exclude random scenery objects (buildings, etc.)

<code>--enable-wireframe</code> 
<code>--disable-wireframe</code>
::Enable/disable wireframe drawing mode.

<code>--fog-disable</code> 
<code>--fog-fastest</code> 
<code>--fog-nicest</code>
::Set the fog. The <code>--fog-disable</code> option will turn off the fog, resulting in increased visibility and a decrease in performance (more terrain to render). The <code>--fog-fastest</code> option will enable fog rendering in a less realistic way, but improving performance. By default, the <code>--fog-nicest</code> option is used to render a realistic fog, at the expense of performance. These options are deprecated.

<code>--fov=degrees</code>
::Specify field of view angle.

<code>--geometry=WidthxHeight</code>
::Specify window geometry/resolution (640x480, etc).

<code>--graphics-preset={minimal-quality|low-quality|medium-quality|high-quality|ultra-quality}</code>
::Specify a graphic preset.

<code>--materials-file=file</code>
::Specify the materials file used to render the scenery (default: Materials/regions/materials.xml).

<code>--max-fps=Hz</code>
::Maximum frame rate in Hz.

<code>--shading-smooth</code> 
<code>--shading-flat</code>
::Enable smooth or flat shading. These options are deprecated.

<code>--texture-filtering=value</code>
::Specify anisotropic filtering of terrain textures. Valid values is 1, 2, 4, 8, 16. Default is 1.

<code>--view-offset=value</code>
::Specify the default forward view direction as an offset from straight ahead. Allowable values are <tt>LEFT</tt>, <tt>RIGHT</tt>, <tt>CENTER</tt>, or a specific number in degrees.

<code>--terrain-engine={tilecache|pagedLOD}</code>
::Specify the terrain engine you want to use: <tt>tilecache</tt> or <tt>pagedLOD</tt>.

<code>--lod-levels=levels</code>
::Specify the detail levels, where levels are a space-separated numeric list of levels. The default is "1 3 5 7 9". Use with <code>--terrain-engine=pagedLOD</code>.

<code>--lod-res=resolution</code>
::Specify the resolution of the terrain grid. Defaults is 1. Use with <code>--terrain-engine=pagedLOD</code>.

<code>--lod-texturing={bluemarble|raster|debug}</code>
::Specify the method of texturing the terrain. The default is <tt>bluemarble</tt>. Use with <code>--terrain-engine=pagedLOD</code>.

<code>--lod-range-mult=multiplier</code>
::Specify the range multiplier (point from low to fine detail). Defaults is 2. Use with <code>--terrain-engine=pagedLOD</code>.

<code>--season={summer|winter}</code>
::Enable <tt>summer</tt> season or <tt>winter</tt> - default <tt>summer</tt>. Available until FG 2020.3.

== WS3.0 ==
<code>--prop:/scenery/use-vpb=true</code>

: Activate the use of World Scenery 3.0

== HDR ==

<code>--compositor=Compositor/HDR/hdr

: Enable the HDR pipeline

= Hud Options =

<code>--enable-hud</code> 
<code>--disable-hud</code>
::Enable/disable Heads Up Display (HUD).

<code>--enable-anti-alias-hud</code> 
<code>--disable-anti-alias-hud</code>
::Enable/disable anti-aliased HUD.

<code>--enable-hud-3d</code> 
<code>--disable-hud-3d</code>
::Enable/disable 3D HUD.

<code>--hud-tris</code> 
<code>--hud-culled</code>
::Hud displays number of triangles rendered or percentage of triangles culled.

= Time Options =

The following time and date setting options are not compatible with each other, so only one of them should be given.

<code>--timeofday={real|dawn|morning|noon|afternoon|dusk|evening|midnight}</code>
::Specify a time of day.

<code>--time-offset=[+-]hh:mm:ss</code>
::Add this time offset to <code>--time-match-real</code>.

<code>--time-match-real</code>
::Synchronize time with current time at chosen airport.

<code>--time-match-local</code>
::Synchronize time with system time of computer.

<code>--start-date-sys=yyyy:mm:dd:hh:mm:ss</code>
::Specify a starting date/time with respect to system time.

<code>--start-date-gmt=yyyy:mm:dd:hh:mm:ss</code>
::Specify a starting date/time with respect to Greenwich Mean Time.

<code>--start-date-lat=yyyy:mm:dd:hh:mm:ss</code>
::Specify a starting date/time with respect to Local Aircraft Time.

= Network Options =

<code>--proxy=[user:password@]host:port</code>
::Specify the proxy server and port to be used. Username and password are optional. If present, they should be listed as MD5 hashes. This option is only useful when <code>--real-weather-fetch</code> is enabled.

<code>--httpd=port</code>
::Enable HTTP server on the specified port.

<code>--telnet={port|socket,bi,hz,localhost,port,tcp}</code> (<code>--props={port|socket,bi,hz,localhost,port,tcp}</code>)
::Enable telnet server on the specified port. Optionally, you can change the hz (number of packets per second).

<code>--jpg-httpd=port</code>
::Enable screen shot HTTP server on the specified port. This option has been withdrawn, instead use <code>--httpd</code> and /screenshot URL.

<code>--allow-nasal-from-sockets</code>
::Remove security flag, which means that network connections will be allowed full access to the simulator including running arbitrary scripts. Ensure you have adequate security such as a firewall which blocks external connections.

<code>--enable-sentry</code> 
<code>--disable-sentry</code>
::Enable/disable crash and error reports from being sent to the development team for analysis.

= MultiPlayer Options =

<code>--callsign=name</code>
::Assign a unique name to a player. A call sign must be at most 10 characters long and can only contain numbers, letters of the English alphabet, hyphens (-) and underscores (_). Longer call signs are truncated, and characters that do not match those listed above are replaced with hyphens.

<code>--multiplay={in|out},hz,address,port</code>
::Specify multipilot communication settings. Multiple instances can be used.

<code>--enable-fgcom</code> 
<code>--disable-fgcom</code>
::Enable/disable built-in FGCom (voice communication with ATC.)

<code>--disable-hold-short</code>
::In multiplayer mode, when you select an initial position on the runway, you will be moved by default to the hold-short position, which is on the taxiway, just in front of the runway. The <code>--disable-hold-short</code> option allows you to disable this behavior, but keep in mind that this is undesirable, as it may interfere with others taking off or landing.

= Route/Way Point Options =

<code>--wp=ID[@alt]</code>
::Specify a waypoint for the GC autopilot. Multiple instances can be used.

<code>--flight-plan=file</code>
::Read all waypoints from a file.

= IO Options =

<code>--generic=params</code>
::Open connection using a predefined communication interface and a preselected communication protocol.

<code>--atlas=params</code>
::Open connection using the Atlas protocol.

<code>--atcsim=params</code>
::Open connection using the ATC sim protocol (atc610x).

<code>--AV400=params</code>
::Emit the Garmin AV400 protocol required to drive a Garmin 196/296 series GPS.

<code>--AV400Sim=params</code>
::Emit the set of AV400 strings required to drive a Garmin 400-series GPS from FlightGear.

<code>--AV400WSimA=params</code>, <code>--AV400WSimB=params</code>
::The Garmin WAAS GPS uses 2 serial channels to communicate with the simulator. These 2 channels are represented by the FGAV400WSimA and the FGAV400WSimB classes. The "A" channel is similar to the previous AVSim400 protocol. The "B" channel is considered the "GPS" channel and uses a different protocol than the "A" channel. The GPS unit expects input on the "B" channel at two different frequencies (1hz and 5hz, normally). The "B" channel also expects responses to certain output messages.

<code>--flarm=params</code>
::Open connection using the FLARM protocol, which includes NMEA/GPS and traffic reporting messages.

<code>--garmin=params</code>
::Open connection using the Garmin GPS protocol.

<code>--hla=params</code>
::Open a remote connection using the HLA protocol. Currently, this option is disabled.

<code>--hla-local=params</code>
::Open a local connection using the HLA protocol. Currently, this option is disabled.

<code>--igc=params</code>
::Open connection using the International Gliding Commission (IGC) protocol.

<code>--joyclient=params</code>
::Open connection to an Agwagon joystick.

<code>--jsclient=params</code>
::Open connection to a remote joystick.

<code>--native=params</code>
::Open connection using the FG Native protocol.

<code>--native-ctrls=params</code>
::Open connection using the FG Native Controls protocol.

<code>--native-fdm=params</code>
::Open connection using the FG Native FDM protocol.

<code>--native-gui=params</code>
::Open connection using the FG Native GUI protocol.

<code>--nmea=params</code>
::Open connection using the NMEA protocol.

<code>--opengc=params</code>
::Open connection using the OpenGC protocol.

<code>--props=params</code>
::Open connection using the interactive property manager (same as <code>--telnet</code>).

<code>--pve=params</code>
::Open connection using the PVE protocol.

<code>--ray=params</code>
::Open connection using the Ray Woodworth motion chair protocol.

<code>--rul=params</code>
::Open connection using the RUL protocol.

Under Windows, you must use a special escape sequence if you need to specify a COM port higher than 9.

Example: <code>--generic=\\.\COM10,out,1,/tmp/data.xml,myproto</code>

This is per the Microsoft KB article here: http://msdn.microsoft.com/en-us/library/aa363858%28v=vs.85%29.aspx

= Avionics Options =

<code>--com1=frequency</code>, <code>--com2=frequency</code>
::Set the COM1 and COM2 radio frequency.

<code>--nav1=[radial:]frequency</code>, <code>--nav2=[radial:]frequency</code>
::Set the NAV1 and NAV2 radio frequency, optionally preceded by a radial.

<code>--adf1=[rotation:]frequency</code>, <code>--adf2=[rotation:]frequency</code>
::Set the ADF1 and 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. The <code>--adf</code> option is deprecated.

<code>--dme={nav1|nav2|frequency}</code>
::Slave the ADF to one of the NAV radios, or set its internal frequency.

= Environment Options =

<code>--enable-real-weather-fetch</code> 
<code>--disable-real-weather-fetch</code>
::Enable/disable METAR based real weather fetching. Enable requires an open internet connection.

<code>--enable-horizon-effect</code> 
<code>--disable-horizon-effect</code>
::Enable/disable celestial body growth illusion near the horizon.

<code>--visibility=meters</code> 
<code>--visibility-miles=miles</code>
::Specify initial visibility in meters or in statute miles.

<code>--wind=DIR[:MAXDIR]@SPEED[:GUST]</code>
::Specify the direction from which the wind is blowing (DIR in degrees) and its SPEED (in knots). If the wind direction is variable, specify the range as DIR:MAXDIR, as a minimum and maximum angle in degrees. If you want the simulator to also model wind gusts, set the maximum :GUST rate in knots.

<code>--turbulence=value</code>
::Specify turbulence where value must to be from 0.0 (calm) to 1.0 (severe).

<code>--ceiling=FT_ASL[:THICKNESS_FT]</code>
::Create an overcast ceiling, optionally with a specific thickness (defaults to 2000 ft).

<code>--random-wind</code>
::Set up random wind direction and speed.

<code>--metar="metar string"</code>
::Starts with a certain METAR string. Only works if live weather is disabled.

= Situation Options =

<code>--failure={pitot|static|vacuum|electrical}</code>
::Fail the pitot, static, vacuum, or electrical system (repeat the option for multiple system failures).

= Debugging Options =

<code>--console</code>
::Display console (Windows specific).

<code>--developer</code>
::Enable developer mode which will log more events.

<code>--enable-fpe</code>
::Abort on encountering a floating point exception.

<code>--fgviewer file</code>
::Use a model viewer rather than load the entire simulator.

<code>--json-report</code>
::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.

<code>--log-level={bulk|debug|info|warn|alert}</code>
::Set the logging level for this session. 0 = verbose, 5 = alerts only. See also [[Commonly used debugging tools#fgfs.log]].

<code>--log-class={none|ai|aircraft|astro|atc|autopilot|clipper|cockpit| environment|event|flight|general|gl|gui|headless|input|instrumentation| io|math|nasal|navaid|network|osg|particles|sound|systems|terrain| terrasync|undefined|view|all}</code>
::Specify which logging class(es) to use.

<code>--log-dir=dir</code>
::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.

<code>--trace-read=property</code>
::Trace the reads for a property; multiple instances can be used.

<code>--trace-write=property</code>
::Trace the writes for a property; multiple instances can be used.

<code>--uninstall</code>
::Remove [[$FG_HOME]] directory. For Windows, it additionally removes TerraSync, Aircraft and TextureCache directories from download directory.

= Related content =
== Wiki articles ==
* [[Command line]]

== Source files ==
* {{fgdata file|options.xml}}
* {{flightgear file|src/Main/options.hxx}}
* {{flightgear file|src/Main/options.cxx}}

[[Category:FlightGear]]
[[Category:Lists]]

[[de:Command Line Options]]
[[fr:Options de ligne de commande]]
[[pl:Opcje wiersza poleceń]]

FlightGear Newsletter April 2023

2023-04-12T19:25:12Z

FurryMLG:

{{User:Skybike/Template:Newsletter-header-translate|2023-04}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==


HDR Pipeline is now More or less stable, and is compatible with WS2.0 (Major Thanks to Icecode)

WS3.0 Shader Ported to HDR




== In the hangar ==









== Scenery corner ==
















== Help wanted ==
{{Help wanted}}

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2023 04]]

FlightGear Newsletter April 2023

2023-04-08T17:19:48Z

FurryMLG: Newsletter creation, automatic preload from here

{{User:Skybike/Template:Newsletter-header-translate|2023-04}}
{{TOC_right|limit=2}}
''We would like to emphasize that the monthly newsletter cannot live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) is welcome to contribute to the newsletter. If you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

''The new Visual Editor makes editing the wiki as simple as using a Word-processor, and even easier than using the forum as you don't even need to know the syntax for a url. Just hit the 'edit' link and start.''

== Development news ==


HDR Pipeline is now More or less stable, and is compatible with WS2.0 (Major Thanks to Icecode)




== In the hangar ==









== Scenery corner ==
















== Help wanted ==
{{Help wanted}}

== AI ==


The AI team makes FlightGear more realistic, colorful and lively every month. You can support the development of ''Interactive Traffic'' and contribute at the FlightGear {{forum link|title=AI|f=23}}.



== Community news ==








=== FlightGear on Facebook ===
Since early December 2010, FlightGear has an [https://www.facebook.com/FlightGear official Facebook page]. If you have a Facebook account please feel free to join the page.

=== FlightGear on Instagram ===
In January 2018 the [https://www.instagram.com/flightgear_sim/ @flightgear_sim Instagram account] was brought back to life. If you've got nice screenshots to be featured, feel free to {{forum link|text=contact the maintainer|t=33636}}.

=== FlightGear on FlightSim.com ===
FlightGear has also a [https://www.flightsim.com/vbfs/forumdisplay.php?102-FlightGear sub-forum] on flightsim.com - just like the commercial flight sims. It is an opportunity to showcase what FG can do, get people curious and answer any questions they may have with regard to the software or the project.

== Multiplayer events ==









== Contributing ==
=== Translators needed ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, you can start by looking at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang mit dem [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help:Traduzir|Help:Traduzir]].
|-
| [[File:zh.gif]]
| FlightGear 百科仍然需要志愿者将其翻译为各种语言。如果你有兴趣让FlightGear百科支持更多语言, 你可以查看 [[Help:Translate]].
|}

=== FlightGear logos ===
If you want some graphic elements for your FlightGear-related site (such as a hangar or YouTube channel), please feel free to visit [[FlightGear logos]] for a repository of logos. And if you have some art skills, please don't hesitate to contribute with your own design creations.

=== Screenshots ===
The FlightGear project always needs screenshots, which show features that were added since the last release. These should be of good quality, especially in content and technical image properties. It is therefore recommended to use the best viable filter settings ([[anti-aliasing]], texture sharpening, etc.). More info at [[Howto:Make nice screenshots]].

==== Screenshot of the Month ====

If you want to participate in the screenshot contest, you can submit your candidate to the {{forum link|title=this|f=88|t=}}. Be sure to see the first post for participation rules. For purposes of convenience and organization, at the end of the month or after 20 entries have been submitted, a new forum topic will be started containing all shots in an easy-to-view layout. The voting will then take place there.

''Thanks for reading {{PAGENAME}}!''

{{Appendix}}


[[Category:Changes after 2020.3]]
[[Category:FlightGear Newsletter|2023 04]]

Airbus A320 family/info

2023-02-09T22:31:35Z

FurryMLG: Updated the VC image!

<includeonly>{{infobox aircraft
| name = Airbus A320 Family
| hangar = fgaddon
| aircraft = A320-family
| image = A320-family.jpg
| image2 = A320VirtualCockpit.png
| alt2 = The 3d [[cockpit]] of the A320-family
| type = Airliner
| config = Low wing aircraft/Monoplane aircraft/Retractable gear aircraft/Tricycle landing gear aircraft
| propulsion = Twinjet
| manufacturer = Airbus
| authors = Josh Davidson (Octal450)/legoboyvdlp/merspieler/Matthew Maring (hayden2000)/Thorsten Herrmann (TH-555)/Semir Gebran (CaptB)
| fdm = JSBsim
| status-fdm = 4
| status-systems = 5
| status-cockpit = 5
| status-model = 4
| fgname = A320-100-CFM/A320-200-CFM/A320-200-IAE/A320neo-CFM/A320neo-PW
| status = Beta
| ready = checklist/canvas
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Airbus A320 Family]].
[[Category:Aircraft infobox documentation]]
</noinclude>

File:A320VirtualCockpit.png

2023-02-09T22:30:54Z

FurryMLG: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=This is the updated virtual cockpit of the A320-Family}}
|date=2023-02-09
|source={{own}}
|author=[[User:FurryMLG|FurryMLG]]
|permission=
|other versions=
}}

=={{int:license-header}}==
{{self|cc-by-sa-4.0}}

[[Category:Airbus A320 cockpit screenshots]]

Boeing 757/info

2022-09-29T03:25:44Z

FurryMLG:

<includeonly>{{infobox aircraft
| name = Boeing 757-200, 757-300, C-32A, C-32B
| hangar = fgaddon
| aircraft = 757-200
| image = 757-2002.jpg
| alt = The 757-200 in the British Airways livery
| image2 = 757200updatedcockpit.png
| alt2 = The 3D [[cockpit]]
| type = Airliner
| config = Narrow-body aircraft/Low wing aircraft
| propulsion = Twinjet
| manufacturer = Boeing
| authors = Juuso Tapaninen/John Williams/Liam Gathercole (3d)/Skyop (FDM, etc.)/Isais V. Prestes (3d cockpit shell)
| fdm = YASim
| fgname = 757-200-RB211 (Rolls Royce)/757-200-PW2040 (Pratt and Whittey)/757-200-fo/757-300/C-32A (USAF variant of 757-200)/C-32B (USAF Special Ops variant of 757-200)
| status-fdm = 3
| status-systems = 4
| status-cockpit = 4
| status-model = 4
| forumtid = 9944
| liverydbid = 37
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Boeing 757-200]].
[[Category:Aircraft infobox documentation]]
</noinclude>

File:757200updatedcockpit.png

2022-09-29T03:20:30Z

FurryMLG:

Updated cockpit for 757-200