FlightGear wiki - User contributions [en]

Command line options

2023-04-21T06:45:21Z

Erik: /* Rendering Options */ Add WS3.0 and HDR

'''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><br/><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><br/>
<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><br/>
<code>--disable-splash-screen</code>
::Enable/disable splash screen.

<code>--enable-mouse-pointer</code><br/>
<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><br/>
<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><br/>
<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><br/>
<code>--disable-panel</code>
::Enable/disable 2D instrument panel.

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

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

<code>--enable-clock-freeze</code><br/>
<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><br/>
<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><br/>
<code>--disable-ai-traffic</code>
::Enable/disable the autogenerated traffic subsystem.

<code>--enable-vr</code><br/>
<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><br/>
<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><br/>
<code>--notrim</code>
::Trim or do not attempt to trim the model (only with <code>--fdm=jsbsim</code>).

<code>--on-ground</code><br/>
<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><br/>
<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><br/>
<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><br/>
<code>--disable-horizon-effect</code>
::Enable/disable celestial body growth illusion near the horizon.

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

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

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

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

<code>--enable-texture-cache</code><br/>
<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><br/>
<code>--disable-fullscreen</code>
::Enable/disable fullscreen mode.

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

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

<code>--fog-disable</code><br/>
<code>--fog-fastest</code><br/>
<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><br/>
<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>--prop:/scenery/use-vpb=true</code>

: Enable the HDR pipeline

= Hud Options =

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

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

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

<code>--hud-tris</code><br/>
<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><br/>
<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><br/>
<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><br/>
<code>--disable-real-weather-fetch</code>
::Enable/disable METAR based real weather fetching. Enable requires an open internet connection.

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

<code>--visibility=meters</code><br/>
<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ń]]

Canvas SVG parser

2023-03-04T08:40:52Z

Erik: /* Known Limitations */ Comment about the shapes found in the Vector Graphics Utility Library

{{Stub}}

{{Infobox subsystem
|name = Scripted SVG parser for Canvas
|image = Canvas SVG demo.png
|alt = svg.nas at work
|description = Implements a scripted SVG parser in [[Nasal]] space for the [[Canvas]] system by mapping a subset of SVG to Canvas elements (text, OpenVG, raster images)
|status = Under active development
|maintainers = {{usr|TheTom}}
|developers = TheTom
|changelog = {{Git File History|project=fgdata|path=/Nasal/canvas/svg.nas}}
}}

{{Template:Canvas Navigation}}

The '''scripted SVG parser''' basically just maps the SVG xml structure to the property tree by adding corresponding Canvas elements as child nodes. It is implemented in [[Nasal]] on top of the XML parsing facilities already provided by FlightGear/Nasal (see $FG_ROOT/Nasal/io.nas).

There's a tiny Nasal module named svg.nas (see $FG_ROOT/Nasal/Canvas) that will read those SVG/XML files and convert them into Canvas nodes (OpenVG/ShivaVG paths) - in other words, depending on the nature of the differences in the output, it should be possible to patch up the svg parser to also support the new format.
To make changes to that module, you need to understand how parsing works and how a stack works (the data structure).
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=280763#p280763
| title = <nowiki>Re: Strange thing with font mapper</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Mar 28th, 2016
| added = Mar 28th, 2016
| script_version = 0.25
}}
</ref>

* a Canvas represents an actual OpenGL texture (2D)
* is hardware-accelerated
* is using OSG for most of its features
* there is an actual scenegraph
* uses Nasal instead of ECMAScript/JavaScript

A FlightGear Canvas is primarily a property tree in the main property tree, where attributes of the texture, and each element, are mapped to "listeners" (or updated via polling).
Internally, this will dispatch events/notifications to the current texture/event.
A Canvas in texture is an invisible offscreen rendering context (RTT/FBO) - it is made visible by adding a so called "placement" to the main FlightGear scenegraph, where the static texture will be replaced with one of the dynamic Canvas textures.
A FlightGear Canvas supports events for UI purposes, so that listeners can be registered for events like "mouseover" etc.
The Canvas scenegraph is a special thing, its root is always a Canvas group - each group can have an arbitrary number of children added, i.e. other elements (or other groups).
The primary Canvas elements are 1) raster images, 2) osgText nodes, 3) map, 4) groups and 5) OpenVG paths.
The FlightGear Canvas system does not understand SVG images - instead, it is using the OpenVG back-end to translate a subset of SVG/XML to Canvas properties by mapping those to OpenVG primitives.
There are many features that are not supported by this SVG parser (svg.nas), but it is written in Nasal and can be easily extended to also support other features, e.g. support for raster images and/or nested SVG images.
Apart from OpenVG, there's no lower level drawing support (think pixels).
<ref>{{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=277769#p277769
| title = <nowiki>Re: Canvas documentation</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Feb 27th, 2016
| added = Feb 27th, 2016
| script_version = 0.25
}}
</ref>

for the supported commands, refer to $FG_ROOT/Nasal/canvas/api.nas and the segments listed in the canvas.Path hash (OpenVG should support arc/circle paths, not sure if those are currently made available or not)
For reference, you can look up the corresponding ShivaVG/OpenVG examples on the web, all primitives listed in api.nas should also be supported by the Canvas/ShivaVG implementation.
BTW: Once you know how to draw a circle using OpenVG paths, you can also extend svg.nas to parse the <circle> tag
<ref> {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=280009#p280009
| title = <nowiki>Re: Drawing a circle</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Mar 20th, 2016
| added = Mar 20th, 2016
| script_version = 0.25
}}
</ref>

== Vector Image Support ==
Using separate canvas elements instead of a single image will always be slower as every little piece of the canvas hat to be triangulated and afterwards rendered every time the canvas gets updated instead of just copying an image. On the other hand you if you use the canvas you can dynamically update the contents of the image and also get (theoretically) unlimited resolution, even changeable at runtime. For SVG, already existing tools (Inkscape) can be used to create images and then just load them via Nasal and add some dynamic features to them.

If you find some SVG feature not working, please check the console for errors - our SVG parser is hand-written and only supports a limited subset of SVG instructions, so may need to be extended, or simply use supported inkscape primitives instead (see svg.nas). $FG_ROOT/Nasal/canvas/svg.nas is our existing example on populating a canvas procedurally by parsing an XML file.

Basically, it looks for supported SVG primitives, and turns those into Canvas/OpenVG primitives by setting properties.

The SVG standard explicitly supports referencing other images (including raster images and SVGs) via the "image" tag - even recursively, so I'd be surprised if inkscape didn't support that. However, our svg parser doesn't currently support this IIRC - but it's "just" Nasal code, so would probably just require ~10-15 lines of code to add support for the image/object tags.

the svg parser is hand-written and can be found in $FG_ROOT/Nasal/canvas/svg.nas, it can be easily extended to support additional primitives/tags, you just need to map them to the corresponding OpenVG equivalents, I think supporting shapes would make sense and shouldn't be too difficult.

our svg.nas parser could also be extended to support external SVGs directly, i.e. using the <use> and <image> tags. The other concern here is performance - once instruments are self-contained and can be treated as such, we can also update them more selectively, i.e. we don't necessarily have to use timers for each individual element, but can instead update instruments in a holistic fashion.



== Hello World ==

[[File:Svgpre.png|thumb|Demonstrate how to preview SVG Images using Canvas]]

Paste this into your [[Nasal Console]] and click run:
<syntaxhighlight lang="nasal">
var CanvasApplication = {
##
# constructor
new: func(x=300,y=200,file="/gui/dialogs/images/ndb_symbol.svg") {

var m = { parents: [CanvasApplication] };
m.file=file;
m.dlg = canvas.Window.new([x,y],"dialog");

# you can change the background color here
var color = {WHITE:[1,1,1,1], BLACK:[0,0,0,1]};
m.canvas = m.dlg.createCanvas().setColorBackground(color.BLACK);
m.root = m.canvas.createGroup();
m.update();
return m;
},

update: func() {
# create a group for the image
var svg_symbols = me.root.createChild("group", "svgfile");

# parse the SVG file
canvas.parsesvg(svg_symbols, me.file);

# resize the image so that it can be fully seen (35%)
svg_symbols.setScale(0.35);

},
}; # end of CanvasApplication

var SVGMapPreview= {
new: func(x,y,svg) {
var m = CanvasApplication.new(x:x, y:y, file:svg);
return m;
},

};

var preview= SVGMapPreview.new(x:400, y:400, svg:"Nasal/canvas/map/Images/boeingND.svg");

print("SVGPreviewer loaded ...!");
</syntaxhighlight>

== Basic example ==

For loading a SVG file onto a Canvas we first need to create a Canvas instance (See [[Howto:Add_a_2D_canvas_instrument_to_your_aircraft]]). Afterwards we can load a SVG by just using the function ''canvas.parsesvg'' from the Canvas API, also the API now supports retrieving elements by id which enables the following simple code snippet for changing the text and color in an instrument:

<syntaxhighlight lang="php">
# Create a group for the parsed elements
var eicas = my_canvas.createGroup();

# Parse an SVG file and add the parsed elements to the given group
canvas.parsesvg(eicas, "Aircraft/C-130J/Instruments/EICAS.svg");

# Get a handle to the element called "ACAWS_10" inside the parsed
# SVG file...
var msg = eicas.getElementById("ACAWS_10");

# ... and change it's text and color
msg.setText("THE NEW API IS COOL!");
msg.setColor(1,0,0);
</syntaxhighlight>

Also the API now supports retrieving elements by id which enables the following simple code snippet for changing the text and color in an instrument:
You can lookup any type of element you want and modify them how you want (Add transformations, change colors/texts/coordinates etc.). You can also lookup an parent element and afterwards some of is child elements. By this you can use the same id multiple times but are still able to get access to every element (eg. Engine 1/Dial N1, Engine 2/Dial N1, etc.).

The result will look somehow like in the following image. The screen on the left side has been created by using the code snippet above and the screen on the right side is just a statically rendered version of the EICAS:

[[File:Canvas SVG demo.png|380px|left|thumb|Simple EICAS example (Notice our warning message)]]

== Supported SVG features ==

The SVG file used for this demo has been created using [http://inkscape.org Inkscape]. Using paths (also with linestipple/dasharray), text, groups and cloning is supported, but don't try to use more advanced features like gradients, as the SVG parser doesn't interpret every part of the SVG standard. (You can always have a look at the {{fgdata source|path=Nasal/canvas/svg.nas|text=implementation}} and also improve it if you want ;-) )

{{note|Support for SVG circle and ellipse has been added to "next" branch in 12/2018 and is expected to be officially available in release 2019.1}}

== Known Limitations ==
NOTE: As of 08/2012, the Canvas system also provides support for raster images, however the SVG parser has not yet been extended to also support raster images via the "image" tag (see the implementation for SVG text->Canvas.Text handling for details).

* https://developer.mozilla.org/en-US/docs/SVG/Tutorial/SVG_Image_Tag
* http://www.w3.org/TR/SVG/struct.html#ImageElement

Shapes are also currently not exposed to Nasal, you'll typically want to use Inkscape's "simplify" option. Basic shapes like Line, Polygon, Rect, RoundedRect, Ellipse and Arc are available through the VGU Utility Library and could be implemented in Nasal directly.
{{FGCquote
|Learnt the hard way that SVG parsing (for ''svg_path'' in ''AA.symbol'') in FG doesn't recognize ''<circle>'', ''<ellipse>'', etc., so I opened my hand-coded SVG in Inkscape and used ''Path->Simplify'' (which ostensibly converts shapes to paths) to convert it to a code compatible with FG.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213304#p213304
|title=<nowiki>Re: Get objects to show up on Map/Radar</nowiki>
|author=<nowiki>RevHardt</nowiki>
|date=<nowiki>Tue Jun 24</nowiki>
}}
}}

{{FGCquote
|Referring to the {{gitorious source|proj=fg|repo=canvas-hackers-fgdata|commit=7d249ce9556d52fb7ae066775023087fbd4daa2f|view=commit|text=gitorious discussion about having a styleable SVGSymbol class}} - that is something that will be hard to support/integrate with pre-defined styling unless we patch svg.nas to accept a list of optional SVG attributes that are mapped to a transformation/rewrite-callback so that SVG attributes can be dynamically "rewritten" by the parser based on looking up a certain id (e.g. "background-color") and changing CSS stuff there.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=209061#p209061
|title=<nowiki>MapStructure styling</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun May 11</nowiki>
}}
}}

{{FGCquote
|This could then use id settings like "glideslope" and "localize" to make those elements accessible, the parser would check its lookup map if the current element matches any key, and if so applies the callback to rewrite the corresponding tag to transparently re-style things without having to modify the actual file. People wanting to change the representation would then merely need to copy the SVG file and ensure that they use the same IDs that are required by the layer's style
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=209061#p209061
|title=<nowiki>MapStructure styling</nowiki>
|author=<nowiki>Hooray</nowiki>
|date=<nowiki>Sun May 11</nowiki>
}}
}}

== Advanced usage ==

=== Font settings ===

By default every text element uses "LiberationFonts/LiberationMono-Bold.ttf" for rendering. If you want to use another font you can pass a function as an additional option to ''canvas.parsesvg'':

<syntaxhighlight lang="nasal">
# There are two arguments passed to the function. The first contains
# the font-family and the second one the font-weight attribute value
var font_mapper = func(family, weight)
{
if( family == "Ubuntu Mono" and weight == "bold" )
# We have to return the name of the font file, which has to be
# inside either the global Font directory inside fgdata or a
# Font directory inside the current aircraft directory.
return "UbuntuMono-B.ttf";

# If we don't return anything the default font is used
};

# Same as before...
canvas.parsesvg
(
eicas,
"Aircraft/C-130J/Instruments/EICAS.svg",
# ... but additionally with our font mapping function
{'font-mapper': font_mapper}
);
</syntaxhighlight>

== Complex Instruments ==
Complex instruments like an airliner's PFD, ND or EICAS display will typically need to retrieve dozens of handles to SVG elements, store them and animate them independently. Typically, you'll see code like the following snippet being used:

<syntaxhighlight lang="nasal">
var speedText = pfd.getElementById("speedText");
var markerBeacon = pfd.getElementById("markerBeacon");
var markerBeaconText = pfd.getElementById("markerBeaconText");
var machText = pfd.getElementById("machText");
var altText = pfd.getElementById("altText");
var selHdgText = pfd.getElementById("selHdgText");
var selAltPtr = pfd.getElementById("selAltPtr");
var fdX = pfd.getElementById("fdX");
var fdY = pfd.getElementById("fdY");
var curAlt1 = pfd.getElementById("curAlt1");
var curAlt2 = pfd.getElementById("curAlt2");
var curAlt3 = pfd.getElementById("curAlt3");
... and so on
</syntaxhighlight>

As you can see, it is generally a good idea to use identical names, for both, SVG elements and Nasal variables.

However, there's one important consideration here: Code like that is generally not suitable to work for multiple instances of an instruments. This may not seem important in the beginning, but normally each pilot will have their own PFD/ND screens, and their own set of switches to control each display. In addition, keeping such requirements in mind, helps to generalize and improve the design of your code.

So rather than having possibly dozens of free-standing Nasal variables dozens of getElementById() calls, you can save lots of time, typing and energy by using a Nasal hash (class) as your instrument container:

<syntaxhighlight lang="nasal">
var myPFD777 = {
new: func {
return {parents:[myPFD777] };
},
init: func(group) {
me.pfd = group;
me.symbols = {};
canvas.parsesvg(me.pfd, "Aircraft/747-400/Models/Cockpit/Instruments/ND/ND.svg", {'font-mapper': font_mapper});

foreach(var svg_element; ["wpActiveId","wpActiveDist","wind","gs","tas",
"hdg","dmeLDist","dmeRDist","vorLId","vorRId",
"eta","range","taOnly","status.wxr","status.wpt",
"status.sta","status.arpt"])
me.symbols[svg_element] = me.nd.getElementById(element);

}

};
</syntaxhighlight>

For a single instrument, this will be identical - but with the added advantage that all elements and canvas groups will not be saved as singleton/global variable, but as members of your myPFD777 class - that way, you will be easily able to support multiple instances of the same instrument.

If you have SVG elements that need some special processing, such as calling the updateCenter() during initialization, you can simply put those inside a separate vector:

<syntaxhighlight lang="nasal">
# load elements from vector image, and create instance variables using identical names, and call updateCenter() on each
# anything that needs updatecenter called, should be added to the vector here
# but do watch our for naming conflicts with other member fields, simply rename SVG IDs if necessary
foreach(var element; ["rotateComp","windArrow","selHdg",
"curHdgPtr","staFromL","staToL",
"staFromR","staToR","compass"] )
me.symbols[element] = me.nd.getElementById(element).updateCenter();

</syntaxhighlight>

Bottom line being: 1) less code, 2) less typing, 3) better maintainable, 4) more future-proof

To port existing code (such as the 744 EICAS/PFD) accordingly, here's what you'll want to do:
* make sure that the SVG element's ID is indeed unique, also within the namespace of your hash/class, to avoid naming conflicts (if the ID is not unique, either introduce a sub namespace/hash, or simply open the SVG file and rename it)
* search/replace occurences of the old variable name and prepend a me. prefix, e.g. '''altitudeFt''' becomes '''me.altitudeFt'''
* remove/comment the free-standing '''var altitudeFt = {};''' line and replace it by adding the SVG element ID to the vector of the foreach loop

[[Category:Canvas]]
[[Category:Howto]]

[[Category:Canvas SVG]]

FlightGear Newsletter May 2022

2022-05-30T14:04:00Z

Erik: Add an WS30 update

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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 ==
[[File:Fgfs-20220528191253.png|thumb|WS30 Vector coastline data]]

==   World Scenery 3.0 ==
One of the major issues with the WS30 rendering is reducing the blockiness of the landclass texture. This is particularly apparent around the coastlines, where there is a very clear separation from water and land. For some time Stuart has been trying to find a way to overlay openstreetmap coastline vector data, but without much success. Scott recently provided the idea of writing the vector data to a higher resolution texture, and then mixing that with the landclass texture.
Some changes where pushed with a simple implementation of his idea. In this case the overlay texture is 2048x2048 for each WS30 LoD tile. So approximately 1m resolution. The texture is built at runtime from the existing WS30 data extracted from openstreetmap. The texture uses a couple of channels to indicate a possible beach shelving into water, and a shader mixes this and applies some noise to vary how much of a beach is actually shown

Apart from improving the general quality, there are some interesting further areas of development if anyone is interested:

* The shader could be used to show more/less beach depending on the tide....
* This technique should be used for water bodies such as lakes, which currently suffer the same blockiness problem. There is waterbody information in osm that is much better than what we are generating in the landclass texture at 25m resolution.
* This might be an interesting alternative for rivers, as it could be used to render sand-banks etc.

==Related Software tools and projects ==
AeromatiC++ has been updated to version 3.3.20 in the JSBSim repository. The most important changes are in the propeller code which now generates tables which get quite close to published numbers. Propeller configurations generated by AeromatiC++ are now finally usable with convidence. Another notable update is that configuration files which are entered in metric units will now use metric units in the configuration files too. A smaller change is the option to put the aerodynamics section into a separate file by specifying --split as a command line option, and adding --fgfs as a command line option generates a rudimentary FlightGear -set file.

*

==In the hangar==



===Updated aircraft===
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes, all liveries are now high resolution and the livery system was updated to have separate liveries for the Fokker F27, Fokker 50 and Fokker 60 and an added dirtmap which can be controlled using the configuration dialog and which is set at a random level at startup.
{| class="wikitable"
|+
![[File:F50flightclose.png|thumb|KLM Cityhopper livery]]
![[File:F27 mk100.jpg|thumb|Fokker F27 Display Team]]
![[File:F60 mtu.jpg|thumb|Fokker 60 Utility]]
|}



==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|2022 05]]

FlightGear Newsletter May 2022

2022-05-28T20:27:26Z

Erik: /* Related Software tools and projects */

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==Related Software tools and projects ==
AeromatiC++ has been updated to version 3.3.20 in the JSBSim repository. The most important changes are in the propeller code which now generates tables which get quite close to published numbers. Propeller configurations generated by AeromatiC++ are now finally usable with convidence. Another notable update is that configuration files which are entered in metric units will now use metric units in the configuration files too. A smaller change is the option to put the aerodynamics section into a separate file by specifying --split as a command line option, and adding --fgfs as a command line option generates a rudimentary FlightGear -set file.

==In the hangar==



===Updated aircraft===
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes, all liveries are now high resolution and the livery system was updated to have separate liveries for the Fokker F27, Fokker 50 and Fokker 60 and an added dirtmap which can be controlled using the configuration dialog and which is set at a random level at startup.
{| class="wikitable"
|+
![[File:F50flightclose.png|thumb|KLM Cityhopper livery]]
![[File:F27 mk100.jpg|thumb|Fokker F27 Display Team]]
![[File:F60 mtu.jpg|thumb|Fokker 60 Utility]]
|}



==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|2022 05]]

FlightGear Newsletter May 2022

2022-05-28T20:20:12Z

Erik: /* Related Software tools and projects */

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==Related Software tools and projects ==
AeromatiC++ has been updated to version 3.3.20 in the JSBSim repository. The most important changes are in the propeller code which now generates tables which get quite close to published numbers. Propeller configurations generated by AeromatiC++ are now finally usable with convidence. Another notable update is that configuration files which are entered in metric units will now use metric units in the configuration files too. A smaller change it the option to put the aerodynamics section into a separate file by specifying --split as a command line option, and adding --fgfs as a command line option generates a rudimentary FlightGear -set file.

==In the hangar==



===Updated aircraft===
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes, all liveries are now high resolution and the livery system was updated to have separate liveries for the Fokker F27, Fokker 50 and Fokker 60 and an added dirtmap which can be controlled using the configuration dialog and which is set at a random level at startup.
{| class="wikitable"
|+
![[File:F50flightclose.png|thumb|KLM Cityhopper livery]]
![[File:F27 mk100.jpg|thumb|Fokker F27 Display Team]]
![[File:F60 mtu.jpg|thumb|Fokker 60 Utility]]
|}



==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|2022 05]]

FlightGear Newsletter May 2022

2022-05-28T13:23:01Z

Erik: Mention the new AeromatiC++ release

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==Related Software tools and projects ==
AeromatiC++ has been updated to version 3.3.20 in the JSBSim repository. The most important changes are in the propeller code which now generates tables which get quite close to published numbers. Propeller configurations generated by AeromatiC++ are now finally usable with convidence. Another notable update is that configuration files which are entered in metric units will now use metric units in the configuration files too. A smaller change it the option to put the aerodynamics section into a separate file by specifying --split as a command line option.

==In the hangar==



===Updated aircraft===
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes, all liveries are now high resolution and the livery system was updated to have separate liveries for the Fokker F27, Fokker 50 and Fokker 60 and an added dirtmap which can be controlled using the configuration dialog and which is set at a random level at startup.
{| class="wikitable"
|+
![[File:F50flightclose.png|thumb|KLM Cityhopper livery]]
![[File:F27 mk100.jpg|thumb|Fokker F27 Display Team]]
![[File:F60 mtu.jpg|thumb|Fokker 60 Utility]]
|}



==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|2022 05]]

File:F5cockpitwide.png

2022-05-15T12:20:40Z

Erik: Erik uploaded a new version of File:F5cockpitwide.png

=={{int:filedesc}}==
{{Information
|description={{en|1=Own wide angle screen shot of Fokker 50 cockpit in FG 1.9.1}}
|date=2012-06-04
|source={{own}}
|author=[[User:Openflight|Openflight]]
|permission=
|other_versions=
|other_fields=
}}

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

FlightGear Newsletter May 2022

2022-05-13T07:12:09Z

Erik: /* Updated aircraft */

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==In the hangar==



===Updated aircraft===
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes, all liveries are now high resolution and the livery system was updated to have separate liveries for the Fokker F27, Fokker 50 and Fokker 60 and an added dirtmap which can be controlled using the configuration dialog and which is set at a random level at startup.
{| class="wikitable"
|+
![[File:F50flightclose.png|thumb|KLM Cityhopper livery]]
![[File:F27 mk100.jpg|thumb|Fokker F27 Display Team]]
![[File:F60 mtu.jpg|thumb|Fokker 60 Utility]]
|}



==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|2022 05]]

File:Fokker50 fokker.jpg

2022-05-11T05:53:48Z

Erik: Erik uploaded a new version of File:Fokker50 fokker.jpg

=={{int:filedesc}}==
{{Information
|description={{en|1=Screenshot of [[Fokker 50]]}}
|date=
|source=
|author=
|permission=
|other_versions=
|other_fields=
}}

[[Category:Screenshots of airliners]]

FlightGear Newsletter May 2022

2022-05-10T18:50:24Z

Erik: /* Updated aircraft */

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==In the hangar==



===Updated aircraft===
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes, all liveries are now high resolution and the livery system was updated to have separate liveries for the Fokker F27, Fokker 50 and Fokker 60.
{| class="wikitable"
|+
![[File:F50flightclose.png|thumb|KLM Cityhopper livery]]
![[File:F27 mk100.jpg|thumb|Fokker F27 Display Team]]
![[File:F60 mtu.jpg|thumb|Fokker 60 Utility]]
|}



==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|2022 05]]

File:F60 mtu.jpg

2022-05-10T18:49:43Z

Erik:

Fokker 60 Utility

File:F27 mk100.jpg

2022-05-10T18:37:59Z

Erik:

Fokker F27 Display team

FlightGear Newsletter May 2022

2022-05-10T14:07:41Z

Erik: /* Updated aircraft */

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==In the hangar==



===Updated aircraft===
[[File:F50flightclose.png|thumb|Fokker 50 in KLM Cityhopper livery]]Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes.



==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|2022 05]]

FlightGear Newsletter May 2022

2022-05-10T14:06:52Z

Erik:

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==In the hangar==



===Updated aircraft===
[[File:F50flightclose.png|thumb|Fokker 50 in KLM Cityhopper livery]]
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes.




==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|2022 05]]

FlightGear Newsletter May 2022

2022-05-10T14:06:00Z

Erik: Add the updated Fokker 50

{{User:Skybike/Template:Newsletter-header-translate|2022-05}}
{{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==






==In the hangar==




[[File:F50flightclose.png|thumb|Fokker 50 in KLM Cityhopper livery]]
Development of the Fokker 50 model has started again. Almost 90% of the 3d mesh has been reworked, the cockpit has been updated, the lighting panel is now functional and the Fokker 60 and Fokker F27 mk100 Friendship have been added to the package. The FDM has also undergone some changes.




==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|2022 05]]

Fokker 50/info

2022-05-10T14:02:49Z

Erik:

<includeonly>{{infobox aircraft
| name = Fokker 50
| hangar = fgaddon
| aircraft = fokker50
| image = Fokker50.jpg
| alt = Fokker 50 in Magic Bird livery
| image2 = F50cockpitnormal.png
| alt2 = Fokker F27 in Golden Knights livery
| type = Airliner
| config = High wing aircraft
| propulsion = Turboprop aircraft/Twin-engine aircraft
| manufacturer = Fokker
| authors = Erik Hofman/Charlie Andrews
| fdm = JSBSim
| fgname = fokker50
| status-fdm = 4
| status-systems = 2
| status-cockpit = 3
| status-model = 5
| forumtid = 634
| liverydbid = 7
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Fokker 50]].
[[Category:Aircraft infobox documentation]]
</noinclude>

File:Fokker50.jpg

2022-05-10T14:02:13Z

Erik: Erik uploaded a new version of File:Fokker50.jpg

=={{int:filedesc}}==
{{Information
|description={{en|1=Screenshot of [[Fokker 50]]}}
|date=
|source=
|author=
|permission=
|other_versions=
|other_fields=
}}

[[Category:Screenshots of airliners]]

Fokker 50/info

2022-05-10T13:59:46Z

Erik:

<includeonly>{{infobox aircraft
| name = Fokker 50
| hangar = fgaddon
| aircraft = fokker50
| image = Fokker50.jpg
| alt = Fokker 50 in VLM livery
| image2 = F50cockpitnormal.png
| alt2 = Fokker F27 in Golden Knights livery
| type = Airliner
| config = High wing aircraft
| propulsion = Turboprop aircraft/Twin-engine aircraft
| manufacturer = Fokker
| authors = Erik Hofman/Charlie Andrews
| fdm = JSBSim
| fgname = fokker50
| status-fdm = 4
| status-systems = 2
| status-cockpit = 3
| status-model = 5
| forumtid = 634
| liverydbid = 7
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Fokker 50]].
[[Category:Aircraft infobox documentation]]
</noinclude>

File:F50cockpitnormal.png

2022-05-10T13:55:45Z

Erik: /* Licensing */

=={{int:filedesc}}==
{{Information
|description={{en|1=Fokker F27 Frienship}}
|date=2022-05-10
|source={{own}}
|author=[[User:Openflight|Openflight]]
|permission=
|other_versions=
|other_fields=
}}

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

File:F50cockpitnormal.png

2022-05-10T13:54:55Z

Erik: Erik uploaded a new version of File:F50cockpitnormal.png

=={{int:filedesc}}==
{{Information
|description={{en|1=Own screenshot of Fokker F50 cockpit in FG 1.9.1}}
|date=2012-06-04
|source={{own}}
|author=[[User:Openflight|Openflight]]
|permission=
|other_versions=
|other_fields=
}}

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

File:F5cockpitwide.png

2022-05-10T13:51:52Z

Erik: Erik uploaded a new version of File:F5cockpitwide.png

File:F50flightclose.png

2022-05-10T13:49:55Z

Erik: Erik uploaded a new version of File:F50flightclose.png

=={{int:filedesc}}==
{{Information
|description={{en|1=Own screenshot of Fokker 50 in flight (FG 1.9.1)}}
|date=2012-06-04
|source={{own}}
|author=[[User:Openflight|Openflight]]
|permission=
|other_versions=
|other_fields=
}}

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

File:Fokker50 KLM.jpg

2022-05-10T13:46:54Z

Erik: Erik uploaded a new version of File:Fokker50 KLM.jpg

== Summary ==
{{File information
|Description = [[Fokker 50]] in KLM Cityhopper livery.
|Source ={{own}}
|Date =
|Author =[[User:Erik|Erik]]
}}

[[Category:Screenshots of aircraft]]
[[Category:Screenshot of the month/2021-02]]
[[Category:Screenshots at high settings]]
[[Category:Screenshots at high settings/2021]]
[[Category:Screenshots at high settings/sotm]]
[[Category:Fokker 50 screenshots]]

File:Fokker DrI.jpg

2022-03-27T12:54:43Z

Erik: Erik uploaded a new version of File:Fokker DrI.jpg

Screenshot of Fokker Dr.I

User talk:Erik

2022-03-26T10:44:02Z

Erik: /* Upload wizard */

== Upload wizard ==

Hi Erik,

I noticed that you didn't use the [[Special:UploadWizard|upload wizard]] when uploading some files recently. Any specific reason for that, or was it by accident? Using the wizard ensures all the fields (description, categories, license) are complete, which your recent files now lack (e.g., [[:File:Pc7mkx.jpg]]).

Thanks!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:11, 28 February 2022 (UTC)

: It's because the wiki user interface is really counter intuitive. At times I really hate it.
I'm still not sure this is the correct way tot respond.

Pilatus PC-9M

2022-03-26T10:40:19Z

Erik: Use the correct way to add a youtube video

{{:{{PAGENAME}}/info}}
Pilatus PC-9M is a single-engine, low-wing tandem-seat turboprop training aircraft designed by Pilatus Aircraft in Switzerland.
{|
|__TOC__
|}

== Performance Data ==

Maximum Speed: 368 mph

Cruise Speed: 343 mph

Rate of climb: 4,090 ft/min

Service Ceiling: 37,992 ft

Stall Speed Gear/Flaps Up: 88 mph, Gear/Flaps Down: 77 mph

Range: 990 mi

== Aircraft help ==
{| class="keytable"
! Key !! Function
|-
| {{key press|C}} || Toggle canopy
|-
| {{key press|E}} || Eject
|-
| {{key press|L}} || Toggle landing lights
|-
| {{key press|M}} || Nose wheel steering
|-
| {{key press|Ctrl|B}} || Toggle air brake
|-
| {{key press|Ctrl|A}} || Toggle autopilot altitude lock
|-
| {{key press|Ctrl|G}} || Toggle autopilot glide slope lock
|-
| {{key press|Ctrl|H}} || Toggle autopilot heading lock
|-
| {{key press|Ctrl|N}} || Toggle nav1 lock
|-
| {{key press|Ctrl|O}} || A/P engage/disengage
|-
| {{key press|Ctrl|S}} || Toggle auto throttle arm
|-
| {{key press|F11}} || Pop up autopilot dialog
|-
| {{key press|F12}} || Radio stack
|}

Click on engine panel to Start/Run/Abort or use Autostart in menu

== Liveries ==
* Bulgarian Air Force 664
* Croatian Air Force 051
* Croatian Air Force 057 "Wings of Storm"
* Irish Air Corps 264
* Mexican Air Force HB-HRI
* Pilatus Factory Demonstrator HB-HPJ
* Royal Air Force British Aerospace ZG969
* Royal Air Force British Aerospace ZK119
* Royal Air Force of Oman
* Royal Australian Air Forces A23-032 4th Squadron
* Royal Australian Air Forces A23-020 76th Squadron
* Royal Australian Air Forces A23-067 "Roulettes"
* Royal Canadian Air Force 123
* Slovenian Air Force 64
* Swiss Air Force C-412 "Patrouille Suisse"
<youtube>tysVaIi-An8</youtube>

== Development status/Issues/Todo ==

Development status - IN DEVELOPMENT

* Detailed 3D model & textures
* Pilot models
* Ejection seats
* External animations
* Lights
* Particle system
* Crash detect system

Issues

* None

Todo

* Cockpit textures
* Authentic instruments
{| class="wikitable"
|+
!
!External
!Cockpit
|-
|PC-7
|[[File:PC-7 extenal view.jpg|thumb|Pilatus PC-7 external view]]
|[[File:PC-7 Cockpti view.jpg|thumb|Pilatus PC-7 cockpit view]]
|-
|PC-7 Mk II
|[[File:PC-7mk II external view.jpg|thumb|Pilatus PC-7mk II external view]]
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-7 MKX
|[[File:PC-7 MKX external view.jpg|thumb|Pilatus PC-7 MKX external view]]
|[[File:PC-7 MKX cockpit view.jpg|thumb|Pilatus PC-7 MKX cockpit view]]
|-
|PC-9/A
|
{| class="wikitable"
|-
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|}
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-9M
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|[[File:PC-9M cockpit view.jpg|thumb|Pilatus PC-9M cockpit view]]
|-
|T-6
|[[File:T-6 external view.jpg|thumb|Beechcraft T-6 external view]]
|[[File:T-6 cockpit view.jpg|thumb|Beechcraft T-6 cockpit view]]
|-
|PC-21
|[[File:PC-21 external view.jpg|thumb|Pilatus PC-21 external view]]
|[[File:PC-21 cockpit view.jpg|thumb|Pilatus PC-21 cockpit view]]
|}

== External links ==
* [http://www.pilatus-aircraft.com Pilatus Aircraft]
* [http://en.wikipedia.org/wiki/Pilatus_PC-9 Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=10341 FlightGear Forum]

{{Pilatus Aircraft}}

Pilatus PC-9M

2022-03-26T10:32:08Z

Erik: Replace a missing video

{{:{{PAGENAME}}/info}}
Pilatus PC-9M is a single-engine, low-wing tandem-seat turboprop training aircraft designed by Pilatus Aircraft in Switzerland.
{|
|__TOC__
|}

== Performance Data ==

Maximum Speed: 368 mph

Cruise Speed: 343 mph

Rate of climb: 4,090 ft/min

Service Ceiling: 37,992 ft

Stall Speed Gear/Flaps Up: 88 mph, Gear/Flaps Down: 77 mph

Range: 990 mi

== Aircraft help ==
{| class="keytable"
! Key !! Function
|-
| {{key press|C}} || Toggle canopy
|-
| {{key press|E}} || Eject
|-
| {{key press|L}} || Toggle landing lights
|-
| {{key press|M}} || Nose wheel steering
|-
| {{key press|Ctrl|B}} || Toggle air brake
|-
| {{key press|Ctrl|A}} || Toggle autopilot altitude lock
|-
| {{key press|Ctrl|G}} || Toggle autopilot glide slope lock
|-
| {{key press|Ctrl|H}} || Toggle autopilot heading lock
|-
| {{key press|Ctrl|N}} || Toggle nav1 lock
|-
| {{key press|Ctrl|O}} || A/P engage/disengage
|-
| {{key press|Ctrl|S}} || Toggle auto throttle arm
|-
| {{key press|F11}} || Pop up autopilot dialog
|-
| {{key press|F12}} || Radio stack
|}

Click on engine panel to Start/Run/Abort or use Autostart in menu

== Liveries ==
* Bulgarian Air Force 664
* Croatian Air Force 051
* Croatian Air Force 057 "Wings of Storm"
* Irish Air Corps 264
* Mexican Air Force HB-HRI
* Pilatus Factory Demonstrator HB-HPJ
* Royal Air Force British Aerospace ZG969
* Royal Air Force British Aerospace ZK119
* Royal Air Force of Oman
* Royal Australian Air Forces A23-032 4th Squadron
* Royal Australian Air Forces A23-020 76th Squadron
* Royal Australian Air Forces A23-067 "Roulettes"
* Royal Canadian Air Force 123
* Slovenian Air Force 64
* Swiss Air Force C-412 "Patrouille Suisse"
<iframe width="560" height="315" src="https://www.youtube.com/embed/tysVaIi-An8" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

== Development status/Issues/Todo ==

Development status - IN DEVELOPMENT

* Detailed 3D model & textures
* Pilot models
* Ejection seats
* External animations
* Lights
* Particle system
* Crash detect system

Issues

* None

Todo

* Cockpit textures
* Authentic instruments
{| class="wikitable"
|+
!
!External
!Cockpit
|-
|PC-7
|[[File:PC-7 extenal view.jpg|thumb|Pilatus PC-7 external view]]
|[[File:PC-7 Cockpti view.jpg|thumb|Pilatus PC-7 cockpit view]]
|-
|PC-7 Mk II
|[[File:PC-7mk II external view.jpg|thumb|Pilatus PC-7mk II external view]]
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-7 MKX
|[[File:PC-7 MKX external view.jpg|thumb|Pilatus PC-7 MKX external view]]
|[[File:PC-7 MKX cockpit view.jpg|thumb|Pilatus PC-7 MKX cockpit view]]
|-
|PC-9/A
|
{| class="wikitable"
|-
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|}
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-9M
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|[[File:PC-9M cockpit view.jpg|thumb|Pilatus PC-9M cockpit view]]
|-
|T-6
|[[File:T-6 external view.jpg|thumb|Beechcraft T-6 external view]]
|[[File:T-6 cockpit view.jpg|thumb|Beechcraft T-6 cockpit view]]
|-
|PC-21
|[[File:PC-21 external view.jpg|thumb|Pilatus PC-21 external view]]
|[[File:PC-21 cockpit view.jpg|thumb|Pilatus PC-21 cockpit view]]
|}

== External links ==
* [http://www.pilatus-aircraft.com Pilatus Aircraft]
* [http://en.wikipedia.org/wiki/Pilatus_PC-9 Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=10341 FlightGear Forum]

{{Pilatus Aircraft}}

Pilatus PC-9M

2022-03-26T10:26:50Z

Erik: Fix a typo

{{:{{PAGENAME}}/info}}
Pilatus PC-9M is a single-engine, low-wing tandem-seat turboprop training aircraft designed by Pilatus Aircraft in Switzerland.
{|
|__TOC__
|}

== Performance Data ==

Maximum Speed: 368 mph

Cruise Speed: 343 mph

Rate of climb: 4,090 ft/min

Service Ceiling: 37,992 ft

Stall Speed Gear/Flaps Up: 88 mph, Gear/Flaps Down: 77 mph

Range: 990 mi

== Aircraft help ==
{| class="keytable"
! Key !! Function
|-
| {{key press|C}} || Toggle canopy
|-
| {{key press|E}} || Eject
|-
| {{key press|L}} || Toggle landing lights
|-
| {{key press|M}} || Nose wheel steering
|-
| {{key press|Ctrl|B}} || Toggle air brake
|-
| {{key press|Ctrl|A}} || Toggle autopilot altitude lock
|-
| {{key press|Ctrl|G}} || Toggle autopilot glide slope lock
|-
| {{key press|Ctrl|H}} || Toggle autopilot heading lock
|-
| {{key press|Ctrl|N}} || Toggle nav1 lock
|-
| {{key press|Ctrl|O}} || A/P engage/disengage
|-
| {{key press|Ctrl|S}} || Toggle auto throttle arm
|-
| {{key press|F11}} || Pop up autopilot dialog
|-
| {{key press|F12}} || Radio stack
|}

Click on engine panel to Start/Run/Abort or use Autostart in menu

== Liveries ==
* Bulgarian Air Force 664
* Croatian Air Force 051
* Croatian Air Force 057 "Wings of Storm"
* Irish Air Corps 264
* Mexican Air Force HB-HRI
* Pilatus Factory Demonstrator HB-HPJ
* Royal Air Force British Aerospace ZG969
* Royal Air Force British Aerospace ZK119
* Royal Air Force of Oman
* Royal Australian Air Forces A23-032 4th Squadron
* Royal Australian Air Forces A23-020 76th Squadron
* Royal Australian Air Forces A23-067 "Roulettes"
* Royal Canadian Air Force 123
* Slovenian Air Force 64
* Swiss Air Force C-412 "Patrouille Suisse"

{{#ev:vimeo|108250500}}

== Development status/Issues/Todo ==

Development status - IN DEVELOPMENT

* Detailed 3D model & textures
* Pilot models
* Ejection seats
* External animations
* Lights
* Particle system
* Crash detect system

Issues

* None

Todo

* Cockpit textures
* Authentic instruments
{| class="wikitable"
|+
!
!External
!Cockpit
|-
|PC-7
|[[File:PC-7 extenal view.jpg|thumb|Pilatus PC-7 external view]]
|[[File:PC-7 Cockpti view.jpg|thumb|Pilatus PC-7 cockpit view]]
|-
|PC-7 Mk II
|[[File:PC-7mk II external view.jpg|thumb|Pilatus PC-7mk II external view]]
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-7 MKX
|[[File:PC-7 MKX external view.jpg|thumb|Pilatus PC-7 MKX external view]]
|[[File:PC-7 MKX cockpit view.jpg|thumb|Pilatus PC-7 MKX cockpit view]]
|-
|PC-9/A
|
{| class="wikitable"
|-
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|}
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-9M
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|[[File:PC-9M cockpit view.jpg|thumb|Pilatus PC-9M cockpit view]]
|-
|T-6
|[[File:T-6 external view.jpg|thumb|Beechcraft T-6 external view]]
|[[File:T-6 cockpit view.jpg|thumb|Beechcraft T-6 cockpit view]]
|-
|PC-21
|[[File:PC-21 external view.jpg|thumb|Pilatus PC-21 external view]]
|[[File:PC-21 cockpit view.jpg|thumb|Pilatus PC-21 cockpit view]]
|}

== External links ==
* [http://www.pilatus-aircraft.com Pilatus Aircraft]
* [http://en.wikipedia.org/wiki/Pilatus_PC-9 Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=10341 FlightGear Forum]

{{Pilatus Aircraft}}

Pilatus PC-9M

2022-03-26T09:47:26Z

Erik: Add screenshots for all variants

{{:{{PAGENAME}}/info}}
Pilatus PC-9M is a single-engine, low-wing tandem-seat turboprop training aircraft designed by Pilatus Aircraft in Switzerland.
{|
|__TOC__
|}

== Performance Data ==

Maximum Speed: 368 mph

Cruise Speed: 343 mph

Rate of climb: 4,090 ft/min

Service Ceiling: 37,992 ft

Stall Speed Gear/Flaps Up: 88 mph, Gear/Flaps Down: 77 mph

Range: 990 mi

== Aircraft help ==
{| class="keytable"
! Key !! Function
|-
| {{key press|C}} || Toggle canopy
|-
| {{key press|E}} || Eject
|-
| {{key press|L}} || Toggle landing lights
|-
| {{key press|M}} || Nose wheel steering
|-
| {{key press|Ctrl|B}} || Toggle air brake
|-
| {{key press|Ctrl|A}} || Toggle autopilot altitude lock
|-
| {{key press|Ctrl|G}} || Toggle autopilot glide slope lock
|-
| {{key press|Ctrl|H}} || Toggle autopilot heading lock
|-
| {{key press|Ctrl|N}} || Toggle nav1 lock
|-
| {{key press|Ctrl|O}} || A/P engage/disengage
|-
| {{key press|Ctrl|S}} || Toggle auto throttle arm
|-
| {{key press|F11}} || Pop up autopilot dialog
|-
| {{key press|F12}} || Radio stack
|}

Click on engine panel to Start/Run/Abort or use Autostart in menu

== Liveries ==
* Bulgarian Air Force 664
* Croatian Air Force 051
* Croatian Air Force 057 "Wings of Storm"
* Irish Air Corps 264
* Mexican Air Force HB-HRI
* Pilatus Factory Demonstrator HB-HPJ
* Royal Air Force British Aerospace ZG969
* Royal Air Force British Aerospace ZK119
* Royal Air Force of Oman
* Royal Australian Air Forces A23-032 4th Squadron
* Royal Australian Air Forces A23-020 76th Squadron
* Royal Australian Air Forces A23-067 "Roulettes"
* Royal Canadian Air Force 123
* Slovenian Air Force 64
* Swiss Air Force C-412 "Patrouille Suisse"

{{#ev:vimeo|108250500}}

== Development status/Issues/Todo ==

Development status - IN DEVELOPMENT

* Detailed 3D model & textures
* Pilot models
* Ejection seats
* External animations
* Lights
* Particle system
* Crash detect system

Issues

* None

Todo

* Cockpit textures
* Authentic instruments
{| class="wikitable"
|+
!
!External
!Cocpkit
|-
|PC-7
|[[File:PC-7 extenal view.jpg|thumb|Pilatus PC-7 external view]]
|[[File:PC-7 Cockpti view.jpg|thumb|Pilatus PC-7 cockpit view]]
|-
|PC-7 Mk II
|[[File:PC-7mk II external view.jpg|thumb|Pilatus PC-7mk II external view]]
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-7 MKX
|[[File:PC-7 MKX external view.jpg|thumb|Pilatus PC-7 MKX external view]]
|[[File:PC-7 MKX cockpit view.jpg|thumb|Pilatus PC-7 MKX cockpit view]]
|-
|PC-9/A
|
{| class="wikitable"
|-
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|}
|[[File:PC-7 Mk II cockpit view.jpg|thumb|Pilatus PC-7 Mk II cockpit view]]
|-
|PC-9M
|[[File:PC-9M external view.jpg|thumb|Pilatus PC-9M external view]]
|[[File:PC-9M cockpit view.jpg|thumb|Pilatus PC-9M cockpit view]]
|-
|T-6
|[[File:T-6 external view.jpg|thumb|Beechcraft T-6 external view]]
|[[File:T-6 cockpit view.jpg|thumb|Beechcraft T-6 cockpit view]]
|-
|PC-21
|[[File:PC-21 external view.jpg|thumb|Pilatus PC-21 external view]]
|[[File:PC-21 cockpit view.jpg|thumb|Pilatus PC-21 cockpit view]]
|}

== External links ==
* [http://www.pilatus-aircraft.com Pilatus Aircraft]
* [http://en.wikipedia.org/wiki/Pilatus_PC-9 Wikipedia]
* [http://forum.flightgear.org/viewtopic.php?f=4&t=10341 FlightGear Forum]

{{Pilatus Aircraft}}

File:PC-7 MKX cockpit view.jpg

2022-03-26T09:46:39Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-7 MKX cockpit view}}
|date=2022-03-26 10:16:08
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-7 Mk II cockpit view.jpg

2022-03-26T09:44:56Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-7 Mk II cockpit view}}
|date=2022-03-26 10:41:39
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-21 cockpit view.jpg

2022-03-26T09:40:29Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-21 cockpit view}}
|date=2022-03-26 10:17:26
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-21 external view.jpg

2022-03-26T09:39:43Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-21 external view}}
|date=2022-03-26 10:17:43
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:T-6 cockpit view.jpg

2022-03-26T09:39:05Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Beechcraft T-6 cockpit view}}
|date=2022-03-26 10:17:04
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:T-6 external view.jpg

2022-03-26T09:38:10Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Beechcraft T-6 external view}}
|date=2022-03-26 10:16:49
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-9M cockpit view.jpg

2022-03-26T09:37:25Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-9M cockpit view}}
|date=2022-03-26 10:14:26
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-9M external view.jpg

2022-03-26T09:36:44Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-9M external view}}
|date=2022-03-26 10:14:08
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-7 MKX external view.jpg

2022-03-26T09:35:52Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-7 MKX external view}}
|date=2022-03-26 10:16:26
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-7mk II external view.jpg

2022-03-26T09:29:57Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-7mk II external view}}
|date=2022-03-26 10:15:36
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

Pilatus PC-9M

2022-03-26T09:27:38Z

Erik:

File:PC-7 Cockpti view.jpg

2022-03-26T09:23:27Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-7 cockpit view}}
|date=2022-03-26 10:14:58
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-7 extenal view.jpg

2022-03-26T09:22:31Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Pilatus PC-7 external view}}
|date=2022-03-26 10:15:16
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:PC-9M-cockpit.png

2022-03-25T14:31:41Z

Erik: Erik uploaded a new version of File:PC-9M-cockpit.png

Cockpit screenshot.

[[Category:Screenshots of cockpits]]

File:Ercoupe.jpg

2022-03-24T11:33:42Z

Erik: Erik uploaded a new version of File:Ercoupe.jpg

{{File information}}

[[Category:Screenshots of aircraft]]
[[Category:Screenshots of scenery]]

File:Ercoupe-cockpit.jpg

2022-03-24T11:32:31Z

Erik: Erik uploaded a new version of File:Ercoupe-cockpit.jpg

== Summary ==
{{File information
|description =
|Source =
|Date =
|Author =
}}

[[Category:Screenshots of cockpits]]

File:PC-9M-cockpit.png

2022-03-20T09:25:02Z

Erik: Erik uploaded a new version of File:PC-9M-cockpit.png

Cockpit screenshot.

[[Category:Screenshots of cockpits]]

File:PC-9.png

2022-03-20T09:18:49Z

Erik: Erik uploaded a new version of File:PC-9.png

Pilatus PC-9M

[[Category:Splash screens]]

File:PC-9 exterior.png

2022-03-19T12:47:05Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PC-9M, reworked 3d with the latest shaders applied}}
|date=2022-03-19
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

File:Pc-9m.jpg

2022-03-19T12:41:54Z

Erik: Uploaded own work with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=PC-9M with the latest shaders applied}}
|date=2022-03-19 13:38:21
|source={{own}}
|author=[[User:Erik|Erik]]
|permission=
|other versions=
}}

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

[[Category:Pilatus PC-9 screenshots]]

FlightGear Newsletter February 2022

2022-02-21T13:21:03Z

Erik: /* In the hangar */

{{User:Skybike/Template:Newsletter-header-translate|2022-02}}
{{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 ==

== FlightGear 2020.3.12 released ==
Bug-fix release 2020.3.12 is now available, containing small bug-fixes in many areas. You can find the Changelog [[Changelog 2020.3#2020.3.12|here]]

Included in this release is a back-port of the generic combined ALS procedural lights and Compositor lights update which allows aircraft developers to easily add all the light effects for a single light for all renderers (classic pre-ALS sprite lights, ALS procedural lights and Compositor scenery illuminating lights) with a single call. More information can be found in the [[Howto:Add aircraft lights#Combined ALS procedural lights and Compositor lights|wiki]]. By including this in version 2020.3.12 this code is forward and backward compatible between FlightGear releases.

{{Disclaimer|id=final-fixed-function-release}}




== In the hangar ==




The Pilatus PC-9M and it's variants have undergone a big overhaul adding the brand new PC-7 MKX and pulling in the PC-21 in the process. Besides a lot of small 3d model changes, the structure is optimized by sharing more 3d objects and animations are improved. There are also some small 3d cockpit improvements implemented.
{|
![[File:Pc7mkx cockpit.jpg|thumb]]
![[File:Pc7mkx.jpg|thumb]]
|}



== 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|2022 02]]