FlightGear wiki - User contributions [en]

Carrier over MP

2026-04-14T11:21:39Z

Gijs: /* FlightGear 2.0.0 and later */ fix links

'''Carrier over MP''' is available in [[FlightGear]] 2.0.0 and later and makes it possible to command the [[Howto: Carrier|Nimitz]] and other [[aircraft carrier]]s. Other pilots on the [[Howto: Multiplayer|multiplayer network]] can ''elect'' to be able to see and land on the carrier controlled by the MP carrier player.

== Installation ==
===FlightGear 2.0.0 and later===
{{Note|It is not enough that you can see carriers in AI mode. You have to have the MPCarrier package installed to be able to see multiplayer carriers}}
This can easily be accomplished by using the [[FlightGear Qt launcher]] and downloading the MP Carrier package. Downloading from here will also mean that you will automatically be prompted when updates to the package are available.

[[File:FlightGear FGAddon MPCarrier.png|thumb|Screenshot of the FlightGear Launcher with the MP Carrier package selected|center]]

Alternatively, you can download directly from the {{fgaddon source |path=Aircraft/MPCarrier |text=FGAddon SVN}}. You will not be prompted when updates are available if you manually download from SVN.

===FlightGear 1.9.1===
{{Caution|This section refers to a version of FlightGear released in 2009. As a result, its instructions are out of date. Please refer to the "FlightGear 2.0.0 and later" section for up to date instructions.}}
The download for the [http://www.gidenstam.org/FlightGear/misc/Carrier_over_MP/MPCarrier_fgfs1.9.1.tar.gz MPCarrier aircraft archive] is available here: http://www.gidenstam.org/FlightGear/misc/Carrier_over_MP/

# Unpack the archive into <tt>data/Aircraft</tt>. For windows users, you can use 7zip and apply it twice (one to unzip, one to untar), until you've got the MPCarrier folder. Once MPCarrier in your Aircraft directory, you will find a new "aircraft" called 'nimitz' in your aircraft list.
# Make sure that the AI scenario nimitz_demo is active.
# To see a mp carrier, set the property: /sim/mp-carriers/nimitz-callsign (see below "important")
# Optional: To get a MPCarrier dialog entry in the Network menu. Apply the changes in mpcarrier_menubar.diff to FG_ROOT/gui/menubar.xml. The diff is for FlightGear/CVS. However, the structure of menubar.xml is so simple that I expect almost anyone could figure out how to add the menu entry :)

==Commander/Captain of the Carrier==
===Starting FlightGear ===
Command the Nimitz:
% fgfs --aircraft=nimitz
Command the Eisenhower:
% fgfs --aircraft=eisenhower

(same for Clemenceau and Vinson).

Command the Nimitz for MP operation:
% fgfs --aircraft=nimitz --callsign='Nimitz7' --multiplay=...

===Commanding the Carrier ===
Here are some principal tips:
*First see the aircraft help. Press '?'.
*To change orientation and position of the carrier (apart from using the rudder and speed, but that take a long time to cross ocean :) ), you can use the properties. You need to change the properties of the ai-carrier you are driving, e.g. for the Nimitz,find the /ai/models/carrier[i] that got Nimitz as name. Use the [[Property_browser]] to do so:
** In /ai/models/carrier[i]/position/ you can change lat, and lon to put it where you want (note that specifying lon/lat on the command line or in menu "Location->Position Aircaft in Air" will not have an effect).
** In /ai/models/carrier[i]/orientation you can make it face wind. Facing wind is important (with real weather fetch) to make the FLOLS green on approach.
*Set speed using PgUp/PgDown in manual control.
*To have a better sync between the pilots using the Nimitz, consider keeping a speed of 0 so that there's no drift between pilots.

==Pilot Using the Carrier==

=== On 2024.1 and later===

Things will work without any special configuration.

Flightgear will automatically enable the appropriate matching AI scenario when an MP carrier appears.

====Latching carriers====

By default Flightgear uses Nasal to periodically change the AI carrier's velocity to make it approximately follow the MP carrier.

One can instead force the AI carrier to exactly follow the position and orientation of the MP carrier (done in C++ in each frame), by checking '''Always latch MP and AI carrier''' in the '''Multiplayer Settings''' dialogue (menu '''Multiplayer/Multiplayer Settings''').

This can work much better but requires that MP motion is smooth, e.g. by using [[Real Time manual|Real Time]] or [[Simple-time]] - see menu '''File/Time Mode'''.

For more information, see: {{flightgear file|docs-mini/README-mp-carriers.md}}

===On 2020.3 and earlier ===

NB: You need to know which callsign and which carrier model to use.

Make sure to enable the AI scenario for the corresponding carrier (e.g. nimitz_demo if the model is the Nimitz).

====From the Launcher====
The easiest way to configure your FlightGear session for an MP carrier is to use the Launcher like in the picture (the model is the Vinson and the callsign is OPFOR21 in the example). [[File:MP carrier settings in launcher.png|thumb|In the "Settings" tab under "Additional Settings" provide the necessary command-line arguments]]

==== From the Command Line====
It is also possible to select MP carrier players from the command line using the following --prop: argument (change "nimitz" in 2 places to the carrier actually in use):
% fgfs --ai-scenario=nimitz_demo --prop:/sim/mp-carriers/nimitz-callsign=<callsign of the player commanding mp-nimitz> --multiplay=.....

For the Vinson it could e.g. be:
% fgfs --ai-scenario=vinson_demo --prop:/sim/mp-carriers/vinson-callsign=MP-029X --multiplay=.....

There is no need that the callsign reflects the TACAN setting - it is just a possible pattern do make it easier for others to use. There is no need to specify the --multiplay option either, if you are using the FlightGear launcher.

====Within the Session====
An alternative way to enable MP control of a carrier when on the multiplayer network use the MP carrier dialog available from Multiplayer->"MPCarrier selection" to select which MP carrier players you wish to see. A pre-requisite is that you already have the parameters set-up as per above.

[[File:MPCarrier-dialog.png|thumb|center|The MPCarrier selection dialog. The user 'Nimitz' is currently selected as the controller of the carrier Nimitz.]]

====Important====

As a pilot you have to run by the books:
*Have the MPCarrier downloaded (The fact that you see the carrier when running AI scenarios is not enough proof that you actually have the MPCarrier. Try to find it in the aircraft dialog. If it is there, then you are good).
*You need to set the --prop:/... correct (note the carrier model name in the string before "-callsign"). This ensures that MPCarriers won't interfer with the normal AI scenarios.
*You need to have the corresponding AI scenario activated.
*In the AI scenarios you can find the carrier from 30+ nm with TACAN. In MP you might find it only from ca. 15+nm (as of 2020.1 version).

[[Category:Multiplayer]]

Template:News

2026-03-23T13:58:29Z

Gijs: 2024.1.5

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }} | FlightGear {{#time: Y"年"F | {{{date|last month}}} | zh }}通讯（英文）]] （[[FlightGear Newsletter|所有历史通讯]]）
}}
{{Localized Release Announcement |date=22-03-2026 |version=2024.1.5}}
{{Localized Release Announcement |date=21-01-2026 |version=2024.1.4}}
{{Localized Release Announcement |date=02-11-2025 |version=2024.1.3}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Template:Current release

2026-03-23T13:57:38Z

Gijs: 2024.1.5

<includeonly>{{#switch: {{{1|}}}
| cr = 2024.1
| crd = 27 February 2025
| nr = 2024.1.6
| nrd = 

| full = 2024.1.5
| fulldate = 22 March 2026

| #default = {{error|No argument given|current release}}
}}</includeonly><noinclude>
{{Informative template|1=
== Goal ==
This template is used internally by {{tl|GitStatus}} to display:
# the current release
# the release date of the current release
# the next release
# the number of days until the next release. Leave empty or comment if unknown
# the full version of the newest release and its release date

This template should be updated with every new release, including bugfix releases.

== Usage ==
{{obr}}'''current release'''{{!}}data{{cbr}}

; data : Dictates what data is returned. This parameter is mandatory. Value may be one of:
:*'''cr''': Current release
:*'''crd''': Release date of current release
:*'''nr''': Next release
:*'''nrd''': Days until the next release

== Examples ==
{{obr}}current release{{!}}cr{{cbr}}
{{current release|cr}}

== Related template ==
* {{tl|GitStatus}}

== See also ==
* [[Release plan]]

}}

[[Category:Git templates]]
</noinclude>

Mooney M20M Bravo

2026-03-04T08:57:43Z

Gijs: Small wiki formatting changes, improved categories

[[File:Mooney-M20M-preview.png|thumb|Mooney M20M Bravo in FlightGear]]

The '''Mooney M20M Bravo''' is a high-performance turbocharged single-engine piston [[aircraft]] produced by Mooney International Corporation. It is part of the Mooney M20 family and is known for its high cruise speed, efficient airframe, and distinctive vertical tail design.

This page documents the '''[[FlightGear]] implementation of the Mooney M20M Bravo''', an open-source aircraft addon currently under development.

== Overview ==

* Aircraft type: Single-engine piston
* Engine: Lycoming TIO-540-AF1B
* Developer: Philips
* [[Flight dynamics model]]: [[JSBSim]]
* Development status: Early development
* Source code: {{Github url|philip2012|Mooney-M20M}}

== FlightGear Implementation ==

The FlightGear Mooney M20M Bravo project is an open-source aircraft developed using the JSBSim flight dynamics model. The project follows a structured development approach focused on establishing a stable aircraft architecture before implementing detailed systems and performance tuning.

Current development focuses on:

* Stable aircraft loading in FlightGear
* Correct aircraft directory structure
* Model integration
* Initial JSBSim flight dynamics configuration

Future development will include:

* Accurate flight dynamics tuning
* Engine and turbocharger simulation
* Cockpit instrumentation
* Aircraft systems implementation

== Development ==

The project is developed as a community addon for FlightGear. The aircraft source files and development history are maintained in a public GitHub repository.

Repository:

{{Github url|philip2012|Mooney-M20M}}

== References ==

* {{wikipedia|Mooney M20}}

[[Category:Piston aircraft‎]]
[[Category:Retractable gear aircraft‎]]
[[Category:Single-engine aircraft]]
[[Category:Tractor aircraft‎]]
[[Category:Tricycle landing gear aircraft‎]]

Template:Current release

2026-01-23T08:00:25Z

Gijs: 2024.1.4

<includeonly>{{#switch: {{{1|}}}
| cr = 2024.1
| crd = 27 February 2025
| nr = 2024.1.5
| nrd = 

| full = 2024.1.4
| fulldate = 21 January 2026

| #default = {{error|No argument given|current release}}
}}</includeonly><noinclude>
{{Informative template|1=
== Goal ==
This template is used internally by {{tl|GitStatus}} to display:
# the current release
# the release date of the current release
# the next release
# the number of days until the next release. Leave empty or comment if unknown
# the full version of the newest release and its release date

This template should be updated with every new release, including bugfix releases.

== Usage ==
{{obr}}'''current release'''{{!}}data{{cbr}}

; data : Dictates what data is returned. This parameter is mandatory. Value may be one of:
:*'''cr''': Current release
:*'''crd''': Release date of current release
:*'''nr''': Next release
:*'''nrd''': Days until the next release

== Examples ==
{{obr}}current release{{!}}cr{{cbr}}
{{current release|cr}}

== Related template ==
* {{tl|GitStatus}}

== See also ==
* [[Release plan]]

}}

[[Category:Git templates]]
</noinclude>

Template:Lockheed

2026-01-19T20:45:13Z

Gijs: Remove broken link

{{Navbox
| name = Lockheed
| title = {{LangSwitch
| de = [[:Category:Lockheed|Lockheed]] Flugzeuge
| en = [[:Category:Lockheed|Lockheed]] aircraft
| fr = Aéronefs [[:Category:Lockheed|Lockheed]]
| zh = [[:Category:Lockheed|洛克希德公司]]飞机
}}
| listclass = hlist

| group1 = {{LangSwitch
| de = Ziviles Flugzeuge
| en = Civilian aircraft
| fr = Aéronefs civil
| zh = 民用飞机
}}
| list1 =
* [[Lockheed Model 10 Electra|Model 10 Electra]]
* {{LangSwitch
| de = [[:de:Lockheed Constellation|Constellation]]
| en = [[Lockheed Constellation|Constellation]]
}}
* {{LangSwitch
| de = [[:de:Lockheed L-1011-500|L1011-500]]
| en = [[Lockheed L-1011-500|L1011-500]]
}}
| group2 = {{LangSwitch
| de = Militärisches Flugzeuge
| en = Military aircraft
| fr = Aéronefs militaire
| zh = 军用飞机
}}
| list2 =
* {{LangSwitch
| de = [[:de:Lockheed C-130 Hercules|C-130]]
| en = [[Lockheed C-130 Hercules|C-130]]
}}
* [[Lockheed Martin C-130J Super Hercules|C-130J]]
* {{LangSwitch
| de = [[:de:General Dynamics F-16 Fighting Falcon|F-16]]
| en = [[General Dynamics F-16 Fighting Falcon|F-16]]
| fr = [[:fr:General Dynamics F-16|F-16]]
}}
* [[F-16CJ]]
* [[Lockheed Martin F-22 Raptor|F-22]]
* [[Lockheed Martin F-35B Lightning II|F-35]]
* {{LangSwitch
| en = [[F-80 Shooting Star|F-80]]
| fr = [[:fr:F-80 Shooting Star|F-80]]
}}
* [[Lockheed F-104 Starfighter|F-104]]
* {{LangSwitch
| en = [[Lockheed F-117 Nighthawk|F-117]]
| fr = [[:fr:Lockheed F-117 Nighthawk|F-117]]
}}
* P-38([[Lockheed P-38 Lightning|1]]/[[Lockheed-P38|2]])
* SR-71([[Lockheed SR-71 Blackbird|1]]/[[Lockheed SR-71|2]])
* U-2([[Lockheed U-2|1]]/[[Lockheed U-2S|2]])
}}<includeonly>{{main other|[[Category:Lockheed]]}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This navigation template links together Lockheed aircraft.

Adding this template to a page in the article namespace will automatically add [[:Category:Lockheed]] to that page.

== Usage ==
Put this line before the categories and the language links at the bottom of the article.

{{obr}}'''Lockheed'''{{cbr}}

}}

[[Category:Manufacturer navigation templates]]
</noinclude>

FlightGear hangars

2026-01-19T12:15:09Z

Gijs: Remove FGMembers per the policy

Aircraft in FlightGear are often distributed from a hangar. The official FlightGear hangar is called [[FGAddon]] and it contains hundreds of aircraft at different stages of development (including aircraft from up to 20 years ago). Many aircraft are also distributed via 3rd-party hangars.

== Licensing ==

The [[FGAddon]] hangar is distributed using the GPLv2+ licensing terms - see the official [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document]. Third party hangars are free to license their content as they wish.

{{caution|If licensing violations are found in a 3rd party hangar - including copying images, sounds, 3D objects or any other content that cannot be legally copied, or any non-legal licensing combinations - the FlightGear developers reserve the right to remove all mentions of that hangar from the official FlightGear web infrastructure (wiki, forum, mailing lists, etc.). The advertisement of illegal content via the official infrastructure could lead to legal problems for the FlightGear developers.}}

== Official FGAddon hangar ==
The [[FGAddon|FGAddon hangar]] is the official FlightGear hangar.

=== Aircraft downloads ===
[[File:FGAddon logo.png|270px|right|link=FGAddon]]

All official release aircraft can now be individually downloaded and updated with FlightGear itself. This is a nice way to browse new aircraft and make sure your favorites are always kept up to date.

=== Aircraft development ===
The [[FGAddon]] version controlled repository contains in-development aircraft as well as aircraft tagged for FlightGear 3.4 and higher stable releases.

* {{fgaddon aircraft source|text=FGAddon Hangar}} The Subversion version controlled repository for the official FlightGear aircraft on the SourceForge infrastructure, see [[FGAddon]] for details.
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Old fgdata Hangar}} The Gitorious archive of the official aircraft, migrated to the [https://archive.org/ Internet Archive] for archival and history preservation purposes. Aircraft were migrated to [[FGAddon]] in September 2014. For further details see the [[FlightGear Newsletter September 2014#Aircraft moved to SVN|September 2014 newsletter announcement]] and the [http://forum.flightgear.org/viewtopic.php?f=28&t=24045 announcement topic on the forum]

=== Liveries ===
* [http://liveries.flightgear.org FlightGear Livery Database]

== Third party sites ==
=== Aircraft catalogues ===
If a hangar provides a [[hangar catalog|catalog URL]] file (catalog.xml), it can be added to the FlightGear QtLauncher to display all the aircraft of that hangar. You add the URL to the <code>catalog.xml</code> on the ''Add-ons'' page in the ''Aircraft hangars'' section.

For details on how to create your own <code>catalog.xml</code> file, see [[Hangar catalog]].

=== Aircraft hangars ===
These are links where you can download individual planes manually.

{| class="wikitable sortable"
|-
! Hangar
! Category
! Description
! [[Hangar catalog|Catalog URL]]
|-
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar]
|
| With U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships and ZF free balloon and additional craft at [http://github.com/andgi?tab=repositories Anders' aircraft repositories at GitHub].
|
|-
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]
|
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.
|
|-
| Bermuda Triangle
| [[:Category:Bermuda Triangle|Category]]
| A hypothetical hangar used to categorize temporarily or permanently lost aircraft.
|
|-
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]
| [[:Category:Buckaroo's hangar|Category]]
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (& a YASim intro).
|
|-
| [http://www.daveshangar.org/ Dave's Hangar]
| [[:Category:Dave's hangar|Category]]
|
| [http://www.daveshangar.org/catalog.xml catalog.xml]
|-
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]
|
| Developing Pipistrel aircraft.
|
|-
| [https://sites.google.com/view/fgukhangar/flightgear-uk-home-page/hangar FlightGear UK - FGUK Hangar]
| [[:Category:FGUK hangar|Category]]
| UK based group improving, mainly European, aircraft and scenery for FG. Weekly MP FlightNights. A lot of helicopters are in the "[https://sites.google.com/view/fgukhangar/flightgear-uk-home-page/hangar/rotary-wing Rotary Wing]" section (November 2020). Over 60 Open Source aircraft so far. [https://forum.fguk.me/ Friendly community forum]
|
|-
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]
|
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.
|
|-
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]
|
| Aermacchi MB339 Frecce Tricolori.
|
|-
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]
| [[:Category:Helijah hangar|Category]]
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].
|
|-
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]
|
| Scenarios, skins, film inspired aerospace vehicles.
|
|-
| [https://github.com/HerbyW HerbyW Hanger]
| [[:Category:HerbyW's hangar|Category]]
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]
|-
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]
|
| Misc. projects.
|
|-
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]
|
| Spanish site.
|
|-
| [http://horizonflightgearhangar.yolasite.com/ Horizon FlightGear Hangar]
|
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.
|
|-
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
|
|
|
|-
| [http://marc-kraus.de/ Lake of Constance Hangar]
| [[:Category:Lake of Constance hangar|Category]]
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.
|
|-
| [http://longfly.square7.ch Longfly's Hangar]
|
|
|
|-
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]
|
|-
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]
|
| Blog, CRJ-200.
|
|-
| [https://github.com/Octal450?tab=repositories Octal450 Hanger]
| [[:Category:Octal450 hangar|Category]]
| High Quality Airliners
| [http://static.djgummikuh.de/octal450/catalog.xml catalog.xml]
|-
| [http://opredflag.com/ Operation Red Flag Hangar]
|
| Flightgear Flight Sim Military Community
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]
|-
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]
| [[:Category:PAF hangar|Category]]
| [http://pattenflightgear.wifeo.com/cessna-citationx.php Cessna Citation X], [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...
|
|-
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]
|
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures...
|
|-
| [http://presteshangar.wikidot.com/start Prestes Hangar]
| [[:Category:Prestes hangar|Category]]
| Many Brazilian aircraft articles.
|
|-
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]
|
| BN-2 Islander, Giant Marshmallow Man.
|
|-
|[https://gitlab.com/fg_shfsn/hangar ShFsn's Hangar]
|
|Various Soviet and Russian aircrafts updated and/or maintained by ShFsn (Tu-144D, Tu-154B-2, An-24B, MiG-15bis, MiG-29, Su-27; as of 2023-11)
|[https://gitlab.com/fg_shfsn/hangar/-/raw/main/catalog.xml catalog.xml]
|-
|[http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]
|
|Newest bluebird version.
|[http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]
|-
|[http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]
|
|A6M2 "Zero", J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.
|
|-
|[http://vicmar.weebly.com/ VicMar]
|
|Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.
|
|-
|[http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]
|
|Douglas DC-8.
|
|}

===Old Hangars===
These are old or abandoned aircraft hangars.

{| class="wikitable sortable"
|-
! Hangar
!Description
!Status
|-
| [https://web.archive.org/http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff (Web Archive link)]
| A-10, A-6
| Dead link as of unknown.
|-
|<s>[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]</s>{{dead link|2017-01-02}}
|Land, Sea, Air.
|Dead link as of 2017-01-02.
|-
|<s>{{gitorious source|text=Airbus Aircraft Development Git}}</s>{{dead link|2018-08-05}}
|A320, A330, A340-300, A380 - various authors, see the projects under <code>airbus-aircraft</code>.
| Dead link as of 2018-08-05.
|-
|[https://web.archive.org/web/20101202031445/http://www.sol2500.net:80/flightgear/aircraft.html DFaber Hangar (Web Archive link)]
|Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more.
|Dead link as of 2012-04.
|-
|<s>[http://thefancyflightgearhangar.blogspot.com The Fancy FlightGear Hangar]</s>
|A few well made aircraft.
|Dead download links as of 2020-06.
|-
| [https://gitlab.com/femboywings-fgfs/ Fboy Wings]
| [[Tupolev Tu-144|Tu-144D]].
| Outdated as of 2023-11.
|-
|<s>[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]</s>{{dead link|2012-08}}
|Blog format.
|Seems to be replaced by advertisement blog (2020-06).
|-
|<s>[https://sites.google.com/site/grtuxhangar GRTux Hangar]</s>{{dead link|2024-10}}
|28+ aircraft and add-ons; you need to mail to GRTux for download.
| Dead link as of 2024-10.
|-
| <s>[https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]</s>{{dead link|2024-10}}
| JA-37, scenario.
| Dead link as of 2024-10.
|-
|[https://web.archive.org/http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar (Web Archive link)]
|Classic aircraft.
|Dead link as of 2015-09.
|-
|[https://web.archive.org/web/20160616195014/http://theomegahangar.flymerlion.org/ Omega Hangar (Web Archive link)]
|Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway.
|Dead link as of 2017-01-02.
|-
|[https://web.archive.org/http://pjedvaj.wordpress.com/ pjedvaj's Hangar (Web Archive link)]
|PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130.
|Dead link as of 2018-07-24.
|-
|[https://web.archive.org/web/20180201073847/http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar (Web Archive link)]
|Models & liveries.
| Dead link as of 2020-06
|-
|<s>[https://sites.google.com/site/sydshangar/ Syd's Google Hangar]</s>{{dead link|2024-10}}
|"Newer 2.0 versions."
|Dead link as of 2024-10.
|-
|[https://m-selig.ae.illinois.edu/apasim/fgfs-models.html UIUC Hangar]
|For FGFS 0.7.8.
|Old aircraft FDMs with no 3D models.
|}

===Livery/Scenery hangars===
*<s>[http://AAliveries.yolasite.com/ AA Liveries]</s>{{dead link|2015-01}} Another livery site
*[http://berwickskins.yolasite.com/ Berwick-skins]
*<s>[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]</s> {{dead link|2017-02}}
*[http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
*[http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]
*[http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)
*<s>[http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]</s>{{dead link|2020-06}}
*<s>[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]</s>{{dead link|2012-04}} (5+ liveries & mods)
*<s>[https://planepainter.yolasite.com/ The Planepainter]</s>{{dead link|2012-04}} (Liveries, Scenery)
*<s>[http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]</s>{{dead link|2020-06}}
*[http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian; many download links broken (2020-06), but some are still working)
*[http://www.fgau.org/ FlightGear Australia/FGAU.org] Australian scenery development.

=== Other FlightGear repositories/mirrors===
*[http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]
*[http://www.unitedfreeworld.com/flightgear-downloads-add-ons/ Unitedfreeworld] (scenery, plane models, and livery) - New owners of the Unitedfreeworld domain have reuploaded all prior work released by xsaint, as of September 2018.

==Related content==
*[[Aircraft]] - [[Helicopter]] - [[Vehicle]]
*[[Hangar catalog]]
*[[Table of models]]

==References==
{{Appendix}}

[[Category:Lists]]
[[ca:Hangars de FlightGear]]
[[es:Hangares_Flightgear]]
[[fr:FlightGear hangars]]
[[pl:FlightGear hangars]]

Template talk:VOTE

2026-01-14T09:07:29Z

Gijs: /* Forum template */ new section

== Forum template ==

Hi,

Since this will always be forum topics, it's best to use [[:Template:forum link]] and only fill in the forum topic id on the POTM template, like:

<pre>{{VOTE
|forumid = 44006
}}</pre>

The VOTE template should then be something like:

<pre>
{| style="width:100%"
| align="center" | [[File:Vote-forum_1920x1024.png|90px]]
| <div style="text-align:left;">'''{{forum link |t={{{forumid}}} |noicon=yes |text={{LangSwitch
| en = Take part in voting for the new screenshot of the month!
| fa = در انتخاب ماهی ماه جدید شرکت کنید!
| fr = Participez à l'élection de la nouvelle capture du mois!
| pl = Weź udział w wyborze nowego zdjęcia miesiąca!
| zh = 参与评选本月最佳照片！
| lang = {{{lang|}}}
}}}}'''</div>
|}
</pre>
This will also ensure that the link remains operational whenever we move the forum to a different domain.

Cheers,

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:07, 14 January 2026 (UTC)

Base Package Assembly

2026-01-09T09:44:09Z

Gijs: Considered for deletion

{{Delete
|reason=Outdated now that aircraft have been split from FGData years ago
|year=2026
|month=1
|day=9}}

{{Project Issues}}

== Objective ==
{{FGCquote
|To move forward with restructuring the FGData repository, some discussion is needed on how different groups of people use the system.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33492344/
|title=<nowiki>[Flightgear-devel] FGData splitting / assembling the base package</nowiki>
|author=<nowiki>James Turner</nowiki>
|date=<nowiki>2015-02-25</nowiki>
}}
}}

{{FGCquote
|Would it be perhaps beneficial if the people engaged in this discussion created a wiki page with structured checklist of all known problems and issues? Then those suggesting a different solution could check and state how their solution would solve (or ignore) those issues. It would make it easier (I hope) to concentrate on the relative merits of various proposals.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33501145/
|title=<nowiki>Re: [Flightgear-devel] FGData splitting / assembling the base
package</nowiki>
|author=<nowiki>Edheldil</nowiki>
|date=<nowiki>2015-02-27</nowiki>
}}
}}

== Status ==
{{FGCquote
|I am going to commence reducing FGDATA this weekend. The reasons for that 
action have been discussed here and on the forum in epic detail, so I won't 
repeat them. 
 
The result will be a new and much smaller git repository and it will only 
have the c172p and the ufo remaining. 
 
To avoid any unnecessary extra work, I will temporarily remove all 
contributors with write access except 2 or three admins on Friday afternoon 
(Central European Time Zone). 

|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33546900/
|title=<nowiki>[Flightgear-devel] FGData size reduction</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2015-03-05</nowiki>
}}
}}

{{FGCquote
|Next, I'll do a initial commit of the base package aircraft to fgaddon/svn. 
Following that, I create a new git repo for a smaller git fgdata and push 
it to sourceforge. 
Finally, we re-add contributors with push permission. 
 
If anything goes wrong, the original fgdata will remain intact and can 
serve as a fallback.
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33546900/
|title=<nowiki>[Flightgear-devel] FGData size reduction</nowiki>
|author=<nowiki>Torsten Dreyer</nowiki>
|date=<nowiki>2015-03-05</nowiki>
}}
}}

Howto:Translate FlightGear

2026-01-09T09:05:14Z

Gijs: Links, templates and formatting

[[FlightGear]] supports localization, that is, showing the user interface in the user's native language rather than in English.

This page will help you '''translate FlightGear''' to a new language or improve the existing translations.

== What can be translated ==

The following parts of the simulator can be translated:
* the menus, splash screens, startup tips and the text shown when the <code>--help</code> [[Command line|command-line]] option is used (FlightGear 2.7.0 and later)
* the shortcut file on Linux systems (FlightGear 2017.1 and later)
* the man pages (FlightGear 2017.3 and later)
* [[FlightGear Qt launcher|the built-in launcher]] (FlightGear 2018.3 and later)

== How to translate ==

# Determine the two letter ISO 639-1 language code for the language you want to translate FlightGear to. A list can be found on the [https://www.loc.gov/standards/iso639-2/php/code_list.php Library of Congress Web site].
# Check whether your language already has a subdirectory below {{fgdata source |path=Translations |text=the Translations directory}}. If it does not, ask on the development mailing for the empty translation files to be created for you. (It's better to do this than to copy an existing translation, as this will avoid you accidentally including unwanted data; besides, rules for plural forms must be added {{fgmeta-python source| path = src/flightgear/meta/i18n/__init__.py | text = in FGMeta-Python}} and {{flightgear source| path = src/Translations/LanguageInfo.cxx | text = in FlightGear}}).
# Open the .XLF files in the subdirectory of your language and translate the English strings in them. You can edit the .XLF files in a text editor (such as Notepad++ or GEdit) but you can also use translation tools such as Qt Linguist or any XLIFF editor. Using a structured tool is recommended because it can track the translation state (flagging untranslated strings) and most tools include helpers to partially automate the translation process.
# Start FlightGear to test your translation (for the -Qt.xlf file, you won't see any change unless you rebuild FlightGear with the file in the expected place). By default, the simulator will select the locale of your operating system as the language to use; you can explicitly select a language using the command-line option <code>--language=language code</code> (alternatively, on Unix-like systems, you can set the <code>LANG</code> environment variable as in <code>LANG=fr_FR.UTF-8 fgfs ...</code>).
# Submit your updated .XLF files for inclusion via the development mailing list or a GitLab merge request.

There are two XLF files in each language subdirectory : FlightGear-nonQt.xlf is for the core simulator strings (startup messages, in-sim menus, command line options help, tips, weather scenarios...), and FlightGear-Qt.xlf is for the built-in launcher.

Note that the user interface might have not full Unicode support (some special/accented characters might not be shown): should you encounter such a location, please write to the flightgear-devel [[mailing list]] at {{Mailing list e-mail address|flightgear-devel}}.

== How to translate the shortcut file ==

Open [{{flightgear url|path=package/org.flightgear.FlightGear.desktop}} the FlightGear <code>.desktop</code> file] and translate the ''GenericName'', ''Comment'' and ''Keywords'' keys (add the ''GenericName[xx]'', ''Comment[xx]'' and ''Keywords[xx]'' keys, where ''xx'' is the two letter ISO 639-1 code of the language).

== How to translate the man pages ==

# Determine the two letter ISO 639-1 language code for the language you want to translate the man pages to.
# Check whether your language already has a subdirectory below [{{flightgear url|path=man}} the man pages directory]. If it does not, create an empty directory in it named after the language code, then copy <code>man1</code> and <code>man5</code> from the man pages directory to the directory of your language.
# Edit [{{flightgear url|path=man/CMakeLists.txt}} man/CMakeLists.txt] and add the instruction <code>add_subdirectory(xx)</code> in the <code>if(NOT WIN32)</code> block (where ''xx'' is the language code).
# Edit <code>man/xx/man1/CMakeLists.txt</code> and <code>man/xx/man5/CMakeLists.txt</code>: on the last row, set the installation directory (<code>DESTINATION</code>), respectively, to <code>${CMAKE_INSTALL_MANDIR}/xx/man1</code> and <code>${CMAKE_INSTALL_MANDIR}/xx/man5</code>.
# Open the man pages in the subdirectory of your language and translate them.

== Using QtLinguist to translate XLF Files ==

One can use QtLinguist (application from the Qt package) to translate XLIFF files. Install Qt package from the Qt home page (https://www.qt.io/download). Opening QtLinguist will show default translation environment. Open XLF file and start translating. The interface is divided into four main sections:

* Context - this is a grouping of the strings to translate. Defined by the developer. Icon beside the group show translation status. Everything should be in the end with the green check sign.
* Strings - strings in the selected group. Select string to translate it
* Sources and Forms - additional information about location of the translated string in the source code (not always visible and with correct information)
* Source text - the main place where translation occurs. Translate here selected strings.

One have to translate the original strings into the target language. Icon beside the original text in the 'Strings' section will show status. Green check mark when everything is correct. Yellow question mark, when the translation is in place but it it not marked as "verified". Untranslated strings are marked with the grey question mark. Sometimes QtLinguist displays exclamation mark - this shows that the translated text does not conform to the original text e.g. original text ends with the punctuation but the translated text not. Buttons (and keyboard shortcuts) on the main toolbar area helps with the strings matching. When the text is translated and you're comfortable with the style/meaning etc. you select green check mark button. It marks the translation as translated-verified. So this is the expected end state for this.

[[File:Qt Linquist.png|700px|frameless]]

Reference:
* [https://doc.qt.io/qt-5/qtlinguist-index.html Qt Linguist manual]
* [https://doc.qt.io/qt-5/linguist-translators.html Qt Linguist for translators guide]

== Related content ==

* [[Translation requests]]

[[Category:Howto|Translate FlightGear]]

Little navmap Add-on

2025-12-29T14:55:58Z

Gijs: Small cleanup

{{Incomplete}}

{{Infobox Software
| title = Little Navmap Add-on
| logo = Fgaddonslogo202x89.png
| image = LMN menu2.png
| alt = Little Navmap addon settings window
| developedby = Sławek Mikuła (slawekmikula)
| initialrelease =
| latestrelease =
| writtenin = Nasal, Canvas
| developmentstatus = 100%
| type = Addon
| platform = Tested on FG version 2024.1.3
| license = [[GNU General Public License]] v2
| website = https://github.com/slawekmikula/flightgear-addon-littlenavmap
}}

The '''Little Navmap''' extension allows [[FlightGear]] to send real-time data to the [https://albar965.github.io/littlenavmap.html Little Navmap] software so that it can plot the aircraft's position on its map.

Little Navmap is a free and open-source flight planner, navigation tool, mobile map, airport search system, and airport information provider. It is compatible with Windows 7/8/10/11, macOS (High Sierra 10.13 or later), and Linux (64-bit only).

[[File:LNM interface.jpg|center|thumb|Little Navmap software interface]]

== How does it work? ==

FlightGear exports its data in real time via a UDP network connection to a gateway program called FGconnect. FGconnect then relays the data to the Little Navmap software, also via a UDP network connection.

Thus, the Navmap map displays the aircraft's movement in real time in three dimensions.

[[File:LMN Datas.png|center|thumb|Little Navmap displays the data sent by FlightGear.]]

== Installation ==

===Installing the add-on===
The installation of this add-on is done as follows:

# [https://github.com/slawekmikula/flightgear-addon-littlenavmap Download] the latest version of the Little Navmap add-on and extract it to a local folder.
# In the launcher, open the "'''Add-ons'''" tab. Click the "'''Add'''" button in the "'''''Add-on Folders'''''" section and select the folder extracted in step 1 (or add the following option in the command line: <code>--addon=/path/to/little-navmap-addon</code>).
# Click on '''"Fly!'''".

=== Installing Python ===

[https://www.python.org/downloads/ Download Python] and perform a default installation.

=== Installing FGconnect ===

The FGconnect module consists of Python scripts and provides the link between the FlightGear and Little Navmap software.

# Download the latest version of [https://github.com/Em-Ant/fgconnect FGconnect] .
# Unzip the downloaded archive into a local folder that does not require elevated user rights (e.g., /home/my_user or c:\users\my_profile).
# Open a terminal window and navigate to this directory. It contains, among other things, the fgconnect.py file (Python script).
# Create a Python virtual environment there:<code>python3 -m venv venv</code>
# Activate this environment:<code>.\vev\scripts\activate</code>
# Install the Python modules required by FGconnect: <code>pip3 install wxpython</code>and<code>pip3 install xmltodict</code>

== Preliminary checks ==

Before configuring anything, check that your operating system is not using the following network ports;

* 5400: This is the port used by FlightGear's HTTP server.
* 7755: This is the default port used by FlightGear to send its data to Little Navmap.
* 51968: This is the port used by Little Navmap to receive data from FlightGear.

To help you determine if these ports are in use, open a terminal (or console) window and run the following command:

* '''Linux / Mac''' :<code>netstat -an | grep <n° port></code>
* '''Windows''' :<code>netstat -an | findstr <n° port></code>

If the ports are free, these orders should not return anything.

== Use ==

Launch FlightGear.

'''The new " Little Navmap''' " menu appears in the menu bar displayed at the top:

[[File:FGFS Barre de menus.png|center|frame|FlightGear Menu Bar]]

Selecting it opens the Little Navmap dialog box:

[[File:LMN menu1.png|center|frame|Little Navmap dialog box main menu]]

Click on button 1 to configure the extension:

[[File:LMN menu2.png|center|frame|Little Navmap settings menu]]

'''Verify that the " Enable export''' " checkbox is active.

If Little Navmap and FlightGear are running on the same machine, leave the default settings.

If Little Navmap and FlightGear are on different machines, replace " '''localhost''' " with the IP address of the machine where Little Navmap is running.

Confirm the configuration by clicking on '''Save''' then '''Close''' .

From the terminal window, once the virtual Python environment has launched, run:<code>.\venv\scripts\python fgconnect.py -s</code>{{Note|The developer of this FGconnect module indicates in his release note <ref>[https://gitlab.com/tgasiba/fgconnect/-/blob/master/readme.txt?ref_type=heads Note de version de FGconnect par son auteur Tiago Gasiba]</ref> that he has only tested it on MacOS and that it should work under Windows and Linux.

On Windows, I found in a forum <ref>[https://forum.flightgear.org/viewtopic.php?f=89&t=38535&p=417657&hilit=fgconnect.py#p417657 Post du forum relatif au script fgconnect.py]</ref> that I needed to modify the fgconnect.py file and add the following after the IMPORT line 15:

<syntaxhighlight lang="python">
sys.path.append(os.path.dirname(__file__))
</syntaxhighlight>

Of course, after making a backup of the original script.}}

Open the Little Navmap software. In the '''Tools''' menu , click on " '''''Connect to Flight Simulator...''''' " and then go to the " '''''Remote/Network''''' " tab. If FlightGear and Little Navmap are running on the same machine, leave the default settings and click the '''Connect''' button .

Alternatively, replace '''''localhost''''' with the IP address where FGconnect and FlightGear are running. Then click '''connect''' .

== Afterwards... ==

At this stage, the FlightGear and Little Navmap software communicate. FlightGear sends real-time data relating to the aircraft: its type, registration, magnetic heading, true heading, position, speed, altitude, etc.

Little Navmap takes this data and reflects the situation on its map.

This allows you to visualize the route followed in relation to the flight plan.

{{Appendix}}

[[Category:FlightGear addons]]
[[Category:Nasal software]]
[[Category:Canvas GUI]]

[[fr:Little navmap Add-on]]

User talk:Rominet/Sandbox

2025-12-23T10:11:15Z

Gijs: /* String substitution */ new section

== String substitution ==

Hi,

I've added [[Module:String]] and [[Module:Ustring]] ;-) Enjoy!

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 10:11, 23 December 2025 (UTC)

Module:Ustring

2025-12-23T10:10:03Z

Gijs: Created page with "require('strict') return setmetatable({}, { __index = function(t, k) local what = mw.ustring[k] if type(what) ~= "function" then return what end return function(frame) local fargs = frame.args local fargsused = { tag = true } local args = {} local str_i = 1 while fargs['s' .. str_i] do fargsused['s' .. str_i] = true args[str_i] = fargs['s' .. str_i] str_i = str_i + 1 end for i, v in ipairs(fargs) do fargsused[i] = true..."

require('strict')
return setmetatable({}, {
__index = function(t, k)
local what = mw.ustring[k]
if type(what) ~= "function" then
return what
end
return function(frame)
local fargs = frame.args
local fargsused = { tag = true }
local args = {}
local str_i = 1
while fargs['s' .. str_i] do
fargsused['s' .. str_i] = true
args[str_i] = fargs['s' .. str_i]
str_i = str_i + 1
end
for i, v in ipairs(fargs) do
fargsused[i] = true
args[i + str_i - 1] = tonumber(v) or v:gsub("^\\", "", 1)
end
if not fargs.tag then
return (what(unpack(args))) -- Outside parens truncate to first result avoiding tail call
end
local tagargs = {}
for x, y in pairs(fargs) do
if not fargsused[x] then tagargs[x] = y end
end
return frame:extensionTag{name = fargs.tag, content = what(unpack(args)), args = tagargs}
end
end
})

Module:String

2025-12-23T10:08:17Z

Gijs: Created page with "--[[ This module is intended to provide access to basic string functions. Most of the functions provided here can be invoked with named parameters, unnamed parameters, or a mixture. If named parameters are used, Mediawiki will automatically remove any leading or trailing whitespace from the parameter. Depending on the intended use, it may be advantageous to either preserve or remove such whitespace. Global options ignore_errors: If set to 'true' or 1, any error c..."

--[[

This module is intended to provide access to basic string functions.

Most of the functions provided here can be invoked with named parameters,
unnamed parameters, or a mixture. If named parameters are used, Mediawiki will
automatically remove any leading or trailing whitespace from the parameter.
Depending on the intended use, it may be advantageous to either preserve or
remove such whitespace.

Global options
ignore_errors: If set to 'true' or 1, any error condition will result in
an empty string being returned rather than an error message.

error_category: If an error occurs, specifies the name of a category to
include with the error message. The default category is
[Category:Errors reported by Module String].

no_category: If set to 'true' or 1, no category will be added if an error
is generated.

Unit tests for this module are available at Module:String/tests.
]]

local str = {}

--[[
len

This function returns the length of the target string.

Usage:
{{#invoke:String|len|target_string|}}
OR
{{#invoke:String|len|s=target_string}}

Parameters
s: The string whose length to report

If invoked using named parameters, Mediawiki will automatically remove any leading or
trailing whitespace from the target string.
]]
function str.len( frame )
local new_args = str._getParameters( frame.args, {'s'} );
local s = new_args['s'] or '';
return mw.ustring.len( s )
end

--[[
sub

This function returns a substring of the target string at specified indices.

Usage:
{{#invoke:String|sub|target_string|start_index|end_index}}
OR
{{#invoke:String|sub|s=target_string|i=start_index|j=end_index}}

Parameters
s: The string to return a subset of
i: The fist index of the substring to return, defaults to 1.
j: The last index of the string to return, defaults to the last character.

The first character of the string is assigned an index of 1. If either i or j
is a negative value, it is interpreted the same as selecting a character by
counting from the end of the string. Hence, a value of -1 is the same as
selecting the last character of the string.

If the requested indices are out of range for the given string, an error is
reported.
]]
function str.sub( frame )
local new_args = str._getParameters( frame.args, { 's', 'i', 'j' } );
local s = new_args['s'] or '';
local i = tonumber( new_args['i'] ) or 1;
local j = tonumber( new_args['j'] ) or -1;

local len = mw.ustring.len( s );

-- Convert negatives for range checking
if i < 0 then
i = len + i + 1;
end
if j < 0 then
j = len + j + 1;
end

if i > len or j > len or i < 1 or j < 1 then
return str._error( 'String subset index out of range' );
end
if j < i then
return str._error( 'String subset indices out of order' );
end

return mw.ustring.sub( s, i, j )
end

--[[
This function implements that features of {{str sub old}} and is kept in order
to maintain these older templates.
]]
function str.sublength( frame )
local i = tonumber( frame.args.i ) or 0
local len = tonumber( frame.args.len )
return mw.ustring.sub( frame.args.s, i + 1, len and ( i + len ) )
end

--[[
match

This function returns a substring from the source string that matches a
specified pattern.

Usage:
{{#invoke:String|match|source_string|pattern_string|start_index|match_number|plain_flag|nomatch}}
OR
{{#invoke:String|pos|s=source_string|pattern=pattern_string|start=start_index
|match=match_number|plain=plain_flag|nomatch=nomatch_output}}

Parameters
s: The string to search
pattern: The pattern or string to find within the string
start: The index within the source string to start the search. The first
character of the string has index 1. Defaults to 1.
match: In some cases it may be possible to make multiple matches on a single
string. This specifies which match to return, where the first match is
match= 1. If a negative number is specified then a match is returned
counting from the last match. Hence match = -1 is the same as requesting
the last match. Defaults to 1.
plain: A flag indicating that the pattern should be understood as plain
text. Defaults to false.
nomatch: If no match is found, output the "nomatch" value rather than an error.

If invoked using named parameters, Mediawiki will automatically remove any leading or
trailing whitespace from each string. In some circumstances this is desirable, in
other cases one may want to preserve the whitespace.

If the match_number or start_index are out of range for the string being queried, then
this function generates an error. An error is also generated if no match is found.
If one adds the parameter ignore_errors=true, then the error will be suppressed and
an empty string will be returned on any failure.

For information on constructing Lua patterns, a form of [regular expression], see:

* https://www.lua.org/manual/5.1/manual.html#5.4.1
* https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Patterns
* https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Ustring_patterns

]]
-- This sub-routine is exported for use in other modules
function str._match( s, pattern, start, match_index, plain, nomatch )
if s == '' then
return str._error( 'Target string is empty' );
end
if pattern == '' then
return str._error( 'Pattern string is empty' );
end
start = tonumber(start) or 1
if math.abs(start) < 1 or math.abs(start) > mw.ustring.len( s ) then
return str._error( 'Requested start is out of range' );
end
if match_index == 0 then
return str._error( 'Match index is out of range' );
end
if plain_flag then
pattern = str._escapePattern( pattern );
end

local result
if match_index == 1 then
-- Find first match is simple case
result = mw.ustring.match( s, pattern, start )
else
if start > 1 then
s = mw.ustring.sub( s, start );
end

local iterator = mw.ustring.gmatch(s, pattern);
if match_index > 0 then
-- Forward search
for w in iterator do
match_index = match_index - 1;
if match_index == 0 then
result = w;
break;
end
end
else
-- Reverse search
local result_table = {};
local count = 1;
for w in iterator do
result_table[count] = w;
count = count + 1;
end

result = result_table[ count + match_index ];
end
end

if result == nil then
if nomatch == nil then
return str._error( 'Match not found' );
else
return nomatch;
end
else
return result;
end
end
-- This is the entry point for #invoke:String|match
function str.match( frame )
local new_args = str._getParameters( frame.args, {'s', 'pattern', 'start', 'match', 'plain', 'nomatch'} );
local s = new_args['s'] or '';
local start = tonumber( new_args['start'] ) or 1;
local plain_flag = str._getBoolean( new_args['plain'] or false );
local pattern = new_args['pattern'] or '';
local match_index = math.floor( tonumber(new_args['match']) or 1 );
local nomatch = new_args['nomatch'];

return str._match( s, pattern, start, match_index, plain, nomatch )
end

--[[
pos

This function returns a single character from the target string at position pos.

Usage:
{{#invoke:String|pos|target_string|index_value}}
OR
{{#invoke:String|pos|target=target_string|pos=index_value}}

Parameters
target: The string to search
pos: The index for the character to return

If invoked using named parameters, Mediawiki will automatically remove any leading or
trailing whitespace from the target string. In some circumstances this is desirable, in
other cases one may want to preserve the whitespace.

The first character has an index value of 1.

If one requests a negative value, this function will select a character by counting backwards
from the end of the string. In other words pos = -1 is the same as asking for the last character.

A requested value of zero, or a value greater than the length of the string returns an error.
]]
function str.pos( frame )
local new_args = str._getParameters( frame.args, {'target', 'pos'} );
local target_str = new_args['target'] or '';
local pos = tonumber( new_args['pos'] ) or 0;

if pos == 0 or math.abs(pos) > mw.ustring.len( target_str ) then
return str._error( 'String index out of range' );
end

return mw.ustring.sub( target_str, pos, pos );
end

--[[
str_find

This function duplicates the behavior of {{str_find}}, including all of its quirks.
This is provided in order to support existing templates, but is NOT RECOMMENDED for
new code and templates. New code is recommended to use the "find" function instead.

Returns the first index in "source" that is a match to "target". Indexing is 1-based,
and the function returns -1 if the "target" string is not present in "source".

Important Note: If the "target" string is empty / missing, this function returns a
value of "1", which is generally unexpected behavior, and must be accounted for
separatetly.
]]
function str.str_find( frame )
local new_args = str._getParameters( frame.args, {'source', 'target'} );
local source_str = new_args['source'] or '';
local target_str = new_args['target'] or '';

if target_str == '' then
return 1;
end

local start = mw.ustring.find( source_str, target_str, 1, true )
if start == nil then
start = -1
end

return start
end

--[[
find

This function allows one to search for a target string or pattern within another
string.

Usage:
{{#invoke:String|find|source_str|target_string|start_index|plain_flag}}
OR
{{#invoke:String|find|source=source_str|target=target_str|start=start_index|plain=plain_flag}}

Parameters
source: The string to search
target: The string or pattern to find within source
start: The index within the source string to start the search, defaults to 1
plain: Boolean flag indicating that target should be understood as plain
text and not as a Lua style regular expression, defaults to true

If invoked using named parameters, Mediawiki will automatically remove any leading or
trailing whitespace from the parameter. In some circumstances this is desirable, in
other cases one may want to preserve the whitespace.

This function returns the first index >= "start" where "target" can be found
within "source". Indices are 1-based. If "target" is not found, then this
function returns 0. If either "source" or "target" are missing / empty, this
function also returns 0.

This function should be safe for UTF-8 strings.
]]
function str.find( frame )
local new_args = str._getParameters( frame.args, {'source', 'target', 'start', 'plain' } );
local source_str = new_args['source'] or '';
local pattern = new_args['target'] or '';
local start_pos = tonumber(new_args['start']) or 1;
local plain = new_args['plain'] or true;

if source_str == '' or pattern == '' then
return 0;
end

plain = str._getBoolean( plain );

local start = mw.ustring.find( source_str, pattern, start_pos, plain )
if start == nil then
start = 0
end

return start
end

--[[
replace

This function allows one to replace a target string or pattern within another
string.

Usage:
{{#invoke:String|replace|source_str|pattern_string|replace_string|replacement_count|plain_flag}}
OR
{{#invoke:String|replace|source=source_string|pattern=pattern_string|replace=replace_string|
count=replacement_count|plain=plain_flag}}

Parameters
source: The string to search
pattern: The string or pattern to find within source
replace: The replacement text
count: The number of occurences to replace, defaults to all.
plain: Boolean flag indicating that pattern should be understood as plain
text and not as a Lua style regular expression, defaults to true
]]
function str.replace( frame )
local new_args = str._getParameters( frame.args, {'source', 'pattern', 'replace', 'count', 'plain' } );
local source_str = new_args['source'] or '';
local pattern = new_args['pattern'] or '';
local replace = new_args['replace'] or '';
local count = tonumber( new_args['count'] );
local plain = new_args['plain'] or true;

if source_str == '' or pattern == '' then
return source_str;
end
plain = str._getBoolean( plain );

if plain then
pattern = str._escapePattern( pattern );
replace = mw.ustring.gsub( replace, "%%", "%%%%" ); --Only need to escape replacement sequences.
end

local result;

if count ~= nil then
result = mw.ustring.gsub( source_str, pattern, replace, count );
else
result = mw.ustring.gsub( source_str, pattern, replace );
end

return result;
end

--[[
simple function to pipe string.rep to templates.
]]

function str.rep( frame )
local repetitions = tonumber( frame.args[2] )
if not repetitions then
return str._error( 'function rep expects a number as second parameter, received "' .. ( frame.args[2] or '' ) .. '"' )
end
return string.rep( frame.args[1] or '', repetitions )
end

--[[
escapePattern

This function escapes special characters from a Lua string pattern. See [1]
for details on how patterns work.

[1] https://www.mediawiki.org/wiki/Extension:Scribunto/Lua_reference_manual#Patterns

Usage:
{{#invoke:String|escapePattern|pattern_string}}

Parameters
pattern_string: The pattern string to escape.
]]
function str.escapePattern( frame )
local pattern_str = frame.args[1]
if not pattern_str then
return str._error( 'No pattern string specified' );
end
local result = str._escapePattern( pattern_str )
return result
end

--[[
Helper function that populates the argument list given that user may need to use a mix of
named and unnamed parameters. This is relevant because named parameters are not
identical to unnamed parameters due to string trimming, and when dealing with strings
we sometimes want to either preserve or remove that whitespace depending on the application.
]]
function str._getParameters( frame_args, arg_list )
local new_args = {};
local index = 1;
local value;

for i,arg in ipairs( arg_list ) do
value = frame_args[arg]
if value == nil then
value = frame_args[index];
index = index + 1;
end
new_args[arg] = value;
end

return new_args;
end

--[[
Helper function to handle error messages.
]]
function str._error( error_str )
local frame = mw.getCurrentFrame();
local error_category = frame.args.error_category or 'Errors reported by Module String';
local ignore_errors = frame.args.ignore_errors or false;
local no_category = frame.args.no_category or false;

if str._getBoolean(ignore_errors) then
return '';
end

local error_str = 'String Module Error: ' .. error_str .. '';
if error_category ~= '' and not str._getBoolean( no_category ) then
error_str = '[[Category:' .. error_category .. ']]' .. error_str;
end

return error_str;
end

--[[
Helper Function to interpret boolean strings
]]
function str._getBoolean( boolean_str )
local boolean_value;

if type( boolean_str ) == 'string' then
boolean_str = boolean_str:lower();
if boolean_str == 'false' or boolean_str == 'no' or boolean_str == '0'
or boolean_str == '' then
boolean_value = false;
else
boolean_value = true;
end
elseif type( boolean_str ) == 'boolean' then
boolean_value = boolean_str;
else
error( 'No boolean value found' );
end
return boolean_value
end

--[[
Helper function that escapes all pattern characters so that they will be treated
as plain text.
]]
function str._escapePattern( pattern_str )
return mw.ustring.gsub( pattern_str, "([%(%)%.%%%+%-%*%?%[%^%$%]])", "%%%1" );
end

return str

FlightGear wiki:Village pump

2025-11-12T13:58:25Z

Gijs: /* Default text in Template:Repo link */

__NEWSECTIONLINK__
{{Archives|[[/Archive 2012|2012]]|[[/Archive 2013|2013]]|[[/Archive 2014|2014]]|[[/Archive 2015|2015]]|[[/Archive 2016|2016]]|[[/Archive 2017|2017]]|[[/Archive 2018|2018]]|[[/Archive 2019|2019]]|[[/Archive 2020|2020]]|[[/Archive 2021|2021]]|[[/Archive 2022|2022]]}}
{{shortcut|FGW:VP}}

Welcome to the '''Village Pump'''. This page is used to discuss the technical issues, operations and guidelines of the [[FlightGear wiki]].

Please [{{fullurl:{{FULLPAGENAME}}|action=edit&section=new}} add new topics] to the '''bottom''' of this page.

Old discussions should be moved to a [[FlightGear wiki:Village pump/Archive YEAR]]. These discussions can then be moved to a relevant talk page if appropriate.

__TOC__

== MediaWiki updated to 1.39.6 ==

We have updated MediaWiki to its latest LTS version 1.39.6 today. Although we've tested the update, chances are that we've missed certain scenarios or features. Please report any issues that you may encounter.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:31, 30 January 2024 (UTC)

== Embedded YouTube videos broken ==

It seems that the [[mw:Extension:EmbedVideo|EmbedVideo extension]] was removed at some point. Consequently, pages such as [[Howto:Creating FlightGear Promo Videos]] are broken. At present, the best replacements seems to be [[mw:Extension:EmbedVideo_(fork)|a fork]] and [[mw:Extension:YouTube|Extension:YouTube]].

—'''''[[User:Red Leader|Red Leader]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 19:21, 30 January 2024 (UTC)

: Hi,
: Thanks for the report. It was introduced by today's update, but should be fixed now.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 21:21, 30 January 2024 (UTC)

:: Confirmed, thanks. And I’d completely forgotten about {{[[Template:Wikipedia|wikipedia]]}}. 😅
:: '''''[[User:Red Leader|Red Leader]]''''' ([[User talk:Red Leader|talk]], [[Special:Contributions/Red Leader|contribs]]) 21:57, 30 January 2024 (UTC)

== Forum registration problem ==

Hello,
I would like to register on the forum, but I tried several times without success. I sent an email to the administrator some time ago, but it seems to have been lost. I don't know what to do, is there somebody here who could help? Please tell me if you need additional information.
Thanks very much in advance. [[User:Kestrel|Kestrel]] ([[User talk:Kestrel|talk]]) 13:14, 25 March 2024 (UTC)

: Hi,
: That's unfortunate! You can find my email address at https://forum.flightgear.org/contact.php Please try again if you've done that before, I'll actively monitor the address for any incoming messages, and let me know if you don't get a reply.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 15:01, 25 March 2024 (UTC) (forum admin)

== Sidebar link for "Build server" is broken ==

Hello,

Just wanted to bring to someones attention that the URL for "Build server" currently 404s. Not sure if this resource still exists or if its URL has changed.

Cheers!
-Joshua

: Hi Joshua,
: The URL is still correct, but the build server is temporarily down due to a server failure. It's being worked on, so should be back up "soon".
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 12:29, 3 September 2024 (UTC)

== FlightGear Wikipedia article image needs correctly sourced Flightgear wiki screenshot ==
https://en.wikipedia.org/wiki/FlightGear

The image used for the Flightgear Wikipedia article appears to have been deleted, because it was sourced from the following Flightgear-wiki screenshot page:

[[:File:Bo 105 over Sint Marteen.png]]

which referred to an imgur link instead of the following thread, which gives a CC license based on a google search of the file name:

https://forum.flightgear.org/viewtopic.php?f=88&t=32163&start=0

Discussion on Wikipedia:

https://en.wikipedia.org/wiki/Wikipedia:Files_for_discussion/2024_December_7#File:FlightGear_Flight_Sim_Bo_105_over_Sint_Marteen.png

> ''Subsequent comments should be made on the appropriate discussion page (such as the file's talk page or in a [https://en.wikipedia.org/wiki/Wikipedia:Deletion_review deletion review]).''

The person who uploaded it, or someone from the wiki, should ideally fix the FlightGear wiki page, and do a deletion review for the Wikipedia file. The file may have been used in multiple pages since screenshots are uncommon on Wikipedia due to proprietary apps. Feel free to remove this comment once it's taken care of. Good luck

== Issues with three templates ==

Hi,

The [[Template:Fgmeta_commit|fgmeta commit]] template appears to be broken. It used to work in the first ''Note'' [[Scripted_Compilation_on_Linux_Debian/Ubuntu#For_the_curious:_the_SSH_way|here]] (see the URL).

Also, I tried to use [[Template:Repo_link#Site:_Generic]] to create a link to the [https://gitlab.kitware.com/cmake/cmake.git CMake repo], but didn't manage: IIRC, the link text was empty.

Finally, [[Template:Fgmeta_source]] doesn't seem to to what the doc. says for ''simplepath'': with
<pre><nowiki>{{fgmeta source
| path = download_and_compile.sh
| simplepath = 1
}}</nowiki></pre>

the link text starts with a slash, so I used
<pre><nowiki>{{fgmeta source
| path = download_and_compile.sh
| text = download_and_compile.sh
}}</nowiki></pre>
which is of course more redundant.

Thanks for considering! :-)

[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

: Good catch. I need to look into that one. I may not have coded the commit part of GitLab into the master {{tl|repo_link}} template.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:41, 13 March 2025 (UTC)

:: All fixed. It was quite simple - the {{tl|fgmeta_source}} template was missing the <code>proj</code> parameter. I've also fixed {{tl|fgmeta_clone}}.

:: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 15:53, 13 March 2025 (UTC)

::: Thanks for the reply and fixes, Bugman! (And sorry for the delay, I didn't see any notification...) I see the first item is indeed addressed. Regarding the second item, well, I see no place where I'd really want to use this now on the d&c page, so didn't test it. As for the third one, I still get <code>/download_and_compile.sh</code> in the Preview when I try the above {{tl|fgmeta_source}} snippet with <code>simplepath = 1</code>.

::: I looked at {{tl|fgmeta_clone}} too; it looks nice but seems to default to the <code>git://</code> protocol. Would it be possible to make it default to using <code>https://</code>? Thanks again. :-)

::: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

:::: Not a problem. For the <code>simplepath</code> parameter, that is the designed behaviour in the {{tl|repo link}} template. In most cases our repositories have complex directory structures and the desired output is the absolute file path, removing the protocol and URL parts of the path. Do you wish to simply have the file name there? No one had asked for that before, so I never added an option for that. In the case of the source repositories, you often want to remove the first part of the absolute path so that for example in SimGear, {{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|simplepath=1}} (<nowiki>{{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|simplepath=1}}</nowiki>) would be shown as {{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|text=scene/util/QuadTreeBuilder.hxx}} (<nowiki>{{simgear source|path=simgear/scene/util/QuadTreeBuilder.hxx|text=scene/util/QuadTreeBuilder.hxx}}</nowiki>. This is not scriptable in MediaWiki so I left it all for the text parameter.

:::: For the protocol, I have now added the <code>protocol</code> parameter. E.g. <nowiki>{{fgmeta clone | protocol = https}}</nowiki>. That will give <code>{{fgmeta clone | protocol = https}}</code> (as of today generated as <code><nowiki>git clone https://gitlab.com/flightgear/fgmeta.git</nowiki></code>).

:::: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 08:51, 24 March 2025 (UTC)

::::: Thanks Bugman, I've updated the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|download_and_compile.sh page]] to use <code><nowiki>{{fgmeta clone | protocol = https}}</nowiki></code> as you proposed; it works great. For the link to download_and_compile.sh, I can continue to use <code><nowiki>{{fgmeta source | path = download_and_compile.sh | text = download_and_compile.sh}}</nowiki></code>, no problem.

::::: As far as I'm concerned, everything is resolved here, so this thread/section can be deleted if someone wants to “clean up”.

::::: ''Other subject:'' the only remaining thing is that I didn't receive any notification, neither for your replies here nor for the January changes by [[User:Jebba|Jebba]] to the [[Scripted_Compilation_on_Linux_Debian/Ubuntu|download_and_compile.sh page]] that is on my watchlist. I used to receive email notifications for these things years ago, haven't changed my preferences regarding this and don't see any setting that would explain why I don't receive these notifications anymore. Maybe email sending by the wiki software is not quite well configured according to current standards (SPF, DKIM, DMARC)?

::::: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

== Improve the 'simgear clone', 'flightgear clone' and 'fgdata clone' templates ==

Hi,

In order to improve [[Fedora_Packages_and_Compiling]], it would be nice to have the <code><nowiki>{{simgear clone}}</nowiki></code>, <code><nowiki>{{flightgear clone}}</nowiki></code> and <code><nowiki>{{fgdata clone}}</nowiki></code> templates on par with <code><nowiki>{{fgmeta clone}}</nowiki></code> (support for the <code>protocol</code> parameter, etc.). I tried

<nowiki>{{simgear clone | protocol = https | opt = --single-branch --branch release/2024.1 | post = simgear}}</nowiki>

but it doesn't seem to work, as the preview shows this:

<nowiki>git clone --single-branch --branch release/2024.1 git://gitlab.com simgear</nowiki>

(ditto with <code>flightear clone</code> and <code>fgdata clone</code>). Thanks in advance :-)

[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

: I needed a while to work out the best strategy for these changes. I've now gone through all of the {{tl|repo link}} cloning subtemplates listed on {{tl|repo link/doc related}} and added the <code>project</code> parameter to the templates and the optional <code>protocol</code> parameter. These changes were required as the <code>gl</code> section of the {{tl|repo_link}} template is constructed differently to the <code>sf</code> section. I've also updated the git cloning documentation {{tl|repo link/doc git clone}}. I hope this covers everything you need.

: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 07:48, 1 April 2025 (UTC)

:: Thanks a lot, Bugman, this works great! Your changes allowed me to perform [https://wiki.flightgear.org/w/index.php?title=Fedora_Packages_and_Compiling&type=revision&diff=141687&oldid=141513 this edit] in [[Fedora_Packages_and_Compiling]]. The only remaining <code>git clone</code> command written in full on that page is for FG's fork of OpenSceneGraph at GitLab. I understand that choosing a proper name for an applicable <code><nowiki>{{... clone}}</nowiki></code> template probably requires some careful thinking... ;-)

:: [[User:Rominet|Rominet]] ([[User talk:Rominet|talk]])

== Default text in Template:Repo link ==

Hi,

The default ''text'' in {{tl|Repo link}} gives somewhat pleasant link texts such as
flightgear/flightgear/src/Scripting/NasalSys.cxx
when the ''site'' is <code>sourceforge</code>, however the result looks like a bug for other sites (though I understand this may be as intended). To be clear, the URLs are correct but the default link texts look weird because they start with the unqualified site name rather than the fully-qualified domain name. For instance,
{{obr}}fgmeta source{{cbr}}
yields {{repo link
| site = {{project infrastructure|abbrev}}
| cmd{{#if:||NULL}} = {{{cmd}}}
| opt{{#if:||NULL}} = {{{opt}}}
| protocol{{#if:||NULL}} = {{{protocol}}}
| login{{#if:||NULL}} = {{{login}}}
| type{{#if:||NULL}} = {{{type}}}
| proj = flightgear
| repo = fgmeta
| branch{{#if:||NULL}} = {{{b}}}
| tag{{#if:||NULL}} = {{{tag}}}
| path{{#if:||NULL}} = {{{1}}}
| commit{{#if:||NULL}} = {{{c}}}
| line{{#if:||NULL}} = {{{l}}}
| view{{#if:||NULL}} = {{{v}}}
| text{{#if:||NULL}} = {{{t}}}
| pre{{#if:||NULL}} = {{{pre}}}
| post{{#if:||NULL}} = {{{post}}}
| simplepath{{#if:||NULL}} = {{{simplepath}}}
| full{{#if:||NULL}} = {{{full}}}
}} rather than [https://gitlab.com/flightgear/fgmeta gitlab.com/flightgear/fgmeta/next]. I suggest to replace <code>gitlab</code> with <code>gitlab.com</code> in the default text (where the HTML comment says “Site advertising”) and do the same for <code>github</code>.

Note: the Gitorious web site doesn't exist anymore, maybe that should be removed from the template?

Thanks for considering; I can do the replacement if you wish.

[[User:Rominet|Rominet]] ([[User talk:Rominet|talk]]) 10:38, 12 November 2025 (UTC)

: Sounds sensible, so please go ahead!
: Regarding Gitorious, it may be nice to link to an archived version of the repos, such as https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://gitorious.org/flightgear/fgdata.git&visit_type=git Altough this only makes sense for repos or branches that are not part of our current GitLab...
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 13:58, 12 November 2025 (UTC)

Frequently asked questions

2025-11-10T09:45:25Z

Gijs: Update links and info

Thank you for your interest in [[FlightGear]]! This '''FAQ''' lists some of the most commonly asked questions. Please create a topic at {{forum link|text=our forum}} if you cannot find the answer on your problem(s).

== Distribution ==
=== Where can I get FlightGear? ===
The official download page is {{project infrastructure|website|link=no|urn=download/}}. Precompiled binaries and disk images are available for Windows and MacOS, and most Linux users will find that most distributions have a packaged version of FlightGear (the package name could be <tt>fgfs</tt> or <tt>flightgear</tt>.)

=== How do I install FlightGear on Linux? ===
Many distributions include FlightGear in their repositories. In addition, in the {{project infrastructure|website|urn=download/|text=Download Center}} you will also find '''AppImage''', which will run on almost any modern distribution. If you can't find a packaged version for you, consider [[Building FlightGear - Linux|downloading and compiling from sources]].

=== Where can I find the latest development source code? ===
The latest development code is available for everyone through our [[FlightGear and Git|Git repository]].

=== Where do I get the scenery? What is available? ===
While the base package only comes with scenery for the San Francisco Bay area, you can currently fly just about anywhere in the world. Currently [[TerraSync]] is the best option: it downloads the latest scenery while flying. See its page for usage information.

=== Where can I get additional planes? ===
The latest official [[aircraft]] can be downloaded and installed with a single click through the aircraft tab in the built-in launcher (see [[FlightGear Qt launcher]]). Some other aircraft can be found in 3rd party [[FlightGear hangars]] (see [[:Howto:Install_aircraft]]).

=== How current is the data in FlightGear compared to the real world? ===
We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the <tt>[[$FG ROOT]]/Navaids/</tt> and <tt>[[$FG ROOT]]/Airports/</tt> directories.

=== Why don't you charge money for this? ===
FlightGear can be downloaded for free from many locations including [https://www.flightgear.org/download the FlightGear website]. We encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

Occasionally you may see FlightGear for sale on auction sites or commercial websites under some other name. This can be done quite legitimately as long as the terms of the license are upheld and might be worth the cost if some value-added features such as additional scenery, aircraft or after-sale support are included. Unfortunately, most cases seen to date appear to be just someone trying to make money selling something that is free and providing no real added value.

If you would like to support official project infrastructure, such as download servers or domain registrations, you are invited to [https://www.flightgear.org/donate make an optional donation].

=== How can I get started with FlightGear? ===
There's no better place than the page [[New to FlightGear]]!

== Compiling ==
=== How do I compile FlightGear from source? ===
See [[Building FlightGear]]. There are explanations to compile in Windows, Linux and even scripts to automatically download and compile the whole thing.

=== Why won't FlightGear compile? ===
Well, that depends. First make sure you are using the appropriate versions of FlightGear, [[SimGear]], plib, zlib. If any of the packages are out of sync with the others, compilation may fail. See also [[Building FlightGear]]

The {{project infrastructure|website|urn=download/|text=FlightGear Downloads page}} should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly.

If your problems persist, ask in the {{forum link|text=FlightGear forum}}, on [[IRC]] or subscribe to our FlightGear-Users [[mailing list]] and let us know what problem you're having.

=== What is SimGear, and why do I need it? ===
[[SimGear]] is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear — it is not needed to run precompiled binaries. Note: When compiling FlightGear it is very important to have the matching version of SimGear.

== Configuring and running ==
=== How do I start FlightGear? ===
The easiest way is using [[FlightGear Qt launcher|Qt Launcher]]. Otherwise, you can run it from the command line, with the [[Command line options|proper options]].

=== How do I install new scenery? ===
If you really don't want to/can't use [[TerraSync]], the scenery archive files (ie. w100n30.tar.gz) should be decompressed into the Scenery/Terrain directory in your [[$FG_ROOT]]. More at [[Howto: Install scenery]].

=== How do I setup my joystick(s)? ===
FlightGear supports wonderfully many joysticks/yokes out of the box. However if you're having problems see [[Input device]].

=== What is fgfsrc? What format should my personal .fgfsrc file be in? ===
[[Fgfsrc|.fgfsrc]] is a file that can contain a list of [[Command line options]] with one option per line. The file is not an XML file. Note that also Windows installations have this file.

=== How do I get to see options, help etc? ===
You probably can not see the main menu. To make it show press {{key press|F10}}.

== Flying ==
=== Why won't my engine(s) start? ===
Aircraft vary in their starting procedure. Some may have an auto-start sequence menu entry or instructions in the aircraft help menu (press {{key press|?}} key) and/or at [[Aircraft|the aircraft's wiki]]. Please consider reading the [[FlightGear Manual]], or see this [[New to FlightGear#Starting the engine|quick small guide]].

=== Where is the moving map? ===
In game, you can go into the menu "Equipment > [[Map]]", but there won't be any aeronautical chart. [[MPmap]] is an online map for multiplayer. Mapping provided by the OpenStreetMap project, is available through [[Phi#Map|Phi]] or [[JMapView]].

=== Where can I learn about instrument flying and navigation? ===
There is a nice article, [[Understanding navigation]], and a lot is very well explained into the [[FlightGear Manual]]. Other resources are:
* http://www.navfltsm.addr.com/ is a very good site for learning techniques for navigation.
* [http://www.av8n.com/how/ See How It Flies] a very nice book by John S. Denker, freely accessible online

=== What is the difference between Aileron and Rudder? ===
There is a bit of info on aileron vs. rudder in the very same book...

=== Is there support for multi-player flying? ===
Yes, sure we have it! See [[Howto: Multiplayer]]. Both the Windows and *nix versions of FlightGear are capable of multi-player flying on FlightGear servers. Also voice communication is supported, with [[FGCom]].

A map showing players aircraft online in real time is available as [[MPmap]].

=== Where are the best places to fly in FlightGear? ===
FlightGear scenery covers the whole world, but thanks to the FlightGear user community, certain airports and areas are more detailed than others. As a general idea:
* There are a lot of high-quality scenery models around Paris, France.
* EHAM Amsterdam Schiphol, EGKK London Gatwick and LFPG Paris Charles de Gaulle are some of the highest quality airports.
* LOWI Innsbruck is both developed in scenery and airport.
* TNCM St. Maarten is a popular destination, and the surrounding islands (Anguilla, St. Eustatius, Saba, St. Barthélemy, St. Kitts, and Nevis) are all well-modeled.

Furthermore, see [[Suggested Flights]], [[Suggested Airports]] and [[Suggested custom scenery]].

=== Where can I find airport info and aeronautical charts online? ===
See [[Getting aeronautical charts]].

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===
Yes. Check out the [[Bombable]] add on and the {{forum link|t=5742|title=Bombable}}. There are also third-party bombing scenarios for the [[A-10]] and other aircraft with armament, like the [[North American OV-10A Bronco]], [[General Dynamics F-16]] and [[F-117 Nighthawk]].

=== Flying issues ===

==== Why are my controls returning to a particular position? ====
There are several possibilities that can lead to this:
* If your aircraft's [[autopilot]] is enabled, it will take over (some of) your controls. Switch the autopilot off to regain control.
* Some laptops have an onboard gravity sensor that might be detected as a [[joystick]]. See how to solve that at [[Troubleshooting input devices#Controls returning to a particular position|Troubleshooting input devices]].

==== Why does my cockpit disappear when looking around? ====
Probably you're using a 2D-panel version of an aircraft. Be sure to pick the one with a 3D cockpit. Most of the aircraft now have it!

==== There are lots of other aircraft flying around ====
FlightGear has a so-called AI Traffic system. This system generates other, computer-controlled aircraft based on real flight plans to make the FlightGear world look more alive. To disable artificial traffic, go to menu "AI" > "Traffic and Scenario Settings" and uncheck the "Enable AI traffic" option.

If on the contrary you can't see any aircraft other than yours, consider [[AI Traffic|contributing to add traffic]] to your favourite place!

==== I can't make this plane fly straight, it keeps turning left! ====
Yes, FlightGear is a real flight simulator and simulates that too. Exactly, that's how real propeller aircraft behave. See [[Understanding Propeller Torque and P-Factor]].

Also, doublecheck your weight distribution. Try adding a 180lbs copilot and see if the turn goes away.

== Contributing ==
For anyone who's willing to contribute, we have dedicated to you the [[Portal:Developer|Developer portal]] and a [[Volunteer]] page that explains all the nice things you can do.

=== What language is FlightGear written in? ===
Mostly C++ with some supporting C code that's primarily contained within SimGear. For more details on the used languages:
* [https://www.openhub.net/p/flightgear/analyses/latest/languages_summary FlightGear programm]
* [https://www.openhub.net/p/simgear/analyses/latest/languages_summary SimGear]
* [https://www.openhub.net/p/flightgeardata/analyses/latest/languages_summary FlightGear data] (aircraft, sounds etc.)

As you seem to be interested in core development, you should really check out [[Howto:Start core development]].

=== How do I design a flight dynamics model for a new aircraft? ===
FlightGear supports various [[flight dynamics model]]s (FDMs), but just two of them are commonly used:
* [[JSBSim]]: see http://jsbsim.sf.net/.
* [[YASim]]: if you want a simpler FDM to work with, try your hand at YASim. For a guide on creating YASim aircraft, look in the FlightGear base package for <tt>[[$FG_ROOT]]/Docs/README.yasim</tt>.

See the [[Portal:Developer/Aircraft|Aircraft development portal]].

=== How do I design or modify a 2D panel? ===
See the <tt>[[$FG_ROOT]]/Docs/README.xmlpanel</tt> file on your computer.

=== How do I place objects, like buildings, into FlightGear? ===
The most up to date solution is using the UFO. See [[Howto:Place 3D objects with the UFO]]. The UFO will give you the interface to choose one of the available objects and place it to some grade of precision into FG world, and then export that data to be uploaded to the official scenery, or for personal use. For more, see the [[Portal:Developer/Scenery|Scenery development portal]].

=== Where can I learn 3D programming and how do I get involved? ===
If you'd like to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is ''desperately'' needed. Try to go easy on the triangles, so that your work will be enjoyed by as many people as possible. The most commonly used tools here are [[Blender]], [[AC3D]], [[Gimp]].

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good [[OpenGL]] book eventually. However, FlightGear uses [[OSG]], a high performance 3D graphics toolkit. To get started with 3D C++ coding, you can take a look at the OSG documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===
This process includes creating the airport layout in [[WorldEditor]], testing it (you might want to generate part of the scenery, but this is not mandatory) and then, if your data sources are GPL compatible, use [[WorldEditor]] to upload it to the gateway. The airport will be available in the next full rebuild of the scenery, unless you want to generate your own scenery. More at [[Howto:Make an airport]].

=== Can I generate my own scenery? ===
Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, [[TerraGear]]. The good news, though, is that once you have set everything up it's quite easy (although might be time consuming), and above all that you can easily share it.

== Problems ==
=== X doesn't work / is broken / is wrong / won't run ===
FlightGear is a very complex program. If you need help in general usage of the game you'll find it at the [[Portal:User|User portal]] and on the {{forum link|text=FlightGear forum}}.

If your problem is instead software crashes, you're getting errors, etc..., please consider following the indications in [[Troubleshooting problems]].

Some of the most common issues are however listed below. If you can't solve the problem on your own and need the help of someone, please remember that we're ''all'' here for fun, developers included, and that any help ''is'' an act of generosity. So try to be nice, even if the problem is frustrating you.

=== Unable to execute file: bin/Win32/fgrun.exe during installation ===
{{Out of date|category=section}}
Your system is missing the MSVC runtime libraries required by FlightGear.
Download and install the following vcredist_x86.exe:
* MSVC9 for FG2.4.0 (and earlier): http://www.microsoft.com/download/en/details.aspx?id=26368
* MSVC10 for FG2.6.0 (and later): http://www.microsoft.com/download/en/details.aspx?id=5555

=== What happened to the panel, keyboard, etc? ===
The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in [[XML]] files contained in the base package.

=== Why is FlightGear so slow? ===
If it seems just slow, see if you can fiddle with graphics settings here: [[Howto: Improve Framerates]].

If things are ''pathologically'' slow (i.e. ~1 frame per second), maybe 3D hardware acceleration is not activated. Make sure you have OpenGL libraries installed and [[Graphics drivers configuration|configured properly]] and make sure you have the latest drivers for your video card. Also, be ready because some cards are [[Problematic Video Cards|not well supported]].

=== How do I see the Frame Rate? ===
On the in-sim [[menu]] select "View" > "View Options", then check the box that says "Show frame rate".

=== How do I toggle 2D cockpit settings? ===
To show/hide the 2D panel, use the key combination {{Key press|Shift|P}}. To show/hide the HUD, press {{Key press|Shift|H}}. You can also enable the alternative HUD by pressing {{Key press|Shift|I}} (press {{Key press|I}} to return to the default one). Use the {{Key press|Shift|H}} key to adjust the brightness of the HUD.

=== Stuck upside down after "crash"? ===
In his infinite wisdom the FlightGear Grand Master decided that planes were too valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground. The quick answer is to reset the sim, via the <tt>File > Reset</tt> menu. This will place your aircraft back at its starting location.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why won't the latest versions of some aircraft work in my (older) version of FlightGear? ===
Often new aircraft development keeps pace with the latest FlightGear code development. New or newly modified aircraft may rely on files (such as new instrument files) or features, only available with newer versions of FlightGear. If you are stuck with an older version of FlightGear, you can try downloading an earlier version of the aircraft from the corresponding [[FlightGear_hangars#Official_hangars|official FlightGear aircraft hangar]].

=== When I start FlightGear I see an error mentioning "SQLite". What do I do? ===
Since FlightGear v2.10 (released in February 2013), the [[navdata cache]] was introduced to improve the FlightGear start times. This cache is a SQLite database that is a little fragile at times. If the database is corrupted FlightGear will refuse to start.

To fix this you simply need to delete the <code>[[$FG_HOME]]/navdata.cache</code> file. The first time FlightGear starts after deletion of the file the navdata cache will be rebuild. As this process is time consuming, FlightGear will take more time to start.

Some will resort to delete the entire <code>$FG_HOME</code> directory or even reinstall FlightGear. However neither is needed and may cause you to lose any custom preferences you have set up.

A further SQLite related problem indicator is the error message

<tt>
Sqlite error:attempt to write a readonly database (8) while running:
INSERT OR REPLACE INTO stat_cache (path, stamp) VALUES (?,?)
</tt>

In this case a previously started FlightGear instance might still be running and locking the navdata.cache file. Check for a running fgfs process and terminate it.

=== My aircraft has grey windows? ===
The problem of opaque grey/gray windows that cannot be seen through is most often due to a version mismatch between the FlightGear program and the aircraft. Or it could be due to a window effect that is not compatible with the [[Project Rembrandt|Rembrandt]] or [[ALS]] rendering systems. The technical cause is that the renderer and declared effect for the window are incompatible. Some solutions include:

* If you are using a stable FlightGear release, please download the aircraft from the [[FlightGear_hangars#Official_hangars|official FlightGear hangars]] matching your FlightGear version.
* If you are using a cutting-edge [[FlightGear Build Server|nightly build]] or a [[Building FlightGear|version controlled copy of FlightGear]], or you wish to use a cutting-edge aircraft, please see [[FGAddon#Obtaining aircraft]].
* If you are using an aircraft from one of the [[FlightGear_hangars#Unofficial_sites|3rd party hangars]], it is best to contact the original aircraft author or the person in charge of the 3rd party hangar.
* If you are using [[Project Rembrandt|Rembrandt]], try turning this rendering system off. Aircraft that use <code>model-default.eff</code> for the windows (at the simple expense of doing nothing) rather than <code>model-transparent.eff</code>, <code>model-combined-transparent.eff</code> or <code>glass.eff</code> (which instruct Rembrandt to not use deferred rendering for the glass) will have grey windows when using Rembrandt.

=== My screen becomes completely red right after starting FlightGear ===
The red screen is the visualization of the "Redout" effect. If it occurs right after starting FlightGear, it might be caused by a problem with scenery loading. FlightGear loads scenery on the fly and if scenery cannot be loaded, eg. due to network problems, there might be no ground for the aircraft to be located on. As a result, the aircraft falls through the non existing ground starting to tumble. This in turn causes the readout effect. For verifying the problem you should start your flight in KSFO, whose scenery is already included in the base package.

== The FAQ ==
=== Who do I contact if I have comments about this FAQ? ===
Add your comment to this FAQ's [[Talk:Frequently asked questions|discussion page]].

=== How old is this document? ===
Check its [{{fullurl:{{PAGENAME}}|action=history}} history].

=== What other important documentation should I read? ===
* [[FlightGear manual]]
* [[New to FlightGear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.

== Contributing ==

=== Content Protection ===
{{See also|FlightGear Plugins}} DRM
{{Cleanup}}

Every once in a while, the question comes up if it is legal to provide closed source plug-in to FlightGear (more exact OSG file reader plug-in). The only need to keep code close is the prevention of reverse engineering. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/27996073/
|title = <nowiki> [Flightgear-devel] Content protection for modders? </nowiki>
|author = <nowiki> Paul Guhl </nowiki>
|date = Aug 25th, 2011
|added = Aug 25th, 2011
|script_version = 0.37
}}</ref><ref>Soitanen (Aug 28th, 2014). {{forum link|title=Re: Encrypted aircraft dynamics|p=217378}}</ref><ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/34559749/
|title = <nowiki> [Flightgear-devel] External FDM to protect propriety data in a GPL
eviirenment </nowiki>
|author = <nowiki> Alan Teeder </nowiki>
|date = Oct 21st, 2015
|added = Oct 21st, 2015
|script_version = 0.37
}}</ref>

FlightGear in its current form is a product of numerous people working voluntarily on a joint effort to create an open and extensible flight simulator platform. Your very idea of introducing DRM, is against all principles of open source in general.

You're free to create a non-GPL plane for FG - that's data from the perspective of the sim and doesn't trigger the license. You can sell that without ever allowing to re-distribute the source code. You're required to stay clear of a few things (you can't use Generic instruments, Nasal libs,...) but that should be doable. You can charge license fees for such a plane, and nobody may legally re-distribute it.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074186/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Thorsten Renk </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

the data is parsed from the XML into dynamic look up tables (IE. STL). The only resources used beyond that needed to make the FDM function is the overhead of pulling the data out of the XML into memory. That would have to happen no matter what form the data was in.
Although there may be better ways to store the data than XML if you are unconcerned about human interaction with the data. I think that making the data human readable/editable is the main point of using XML. It may be overly verbose but it works and there are standard libraries for reading/parsing XML files so this makes using it for data input fairly simple. This benefits both FlightGear and JSBSim in terms of limiting the complexity of handling configuration data. In addition there are a limited number of standardied formats for this type of thing such as JSON and all of those that are human readable/editable have many of the same issues as XML.
Full function FDMs are complex and understanding the XML used to configure a complex FDM is a very minor issue and anyone who actually understands a full function FDM will have very few issues with the XML part of this.<ref>hvengel (Aug 28th, 2014). {{forum link|title=Re: Encrypted aircraft dynamics|p=217408}}</ref>

FG itself is OpenSource, so whatever protection scheme we may code in, anyone is free to remove (and that's quite legal). It'd be a no-brainer to generate a no-copyright-protection version of FG and distribute it on which your content just runs without the key (or whatever). Given that people usually succeed in cracking DRM schemes in the absence of an open source code, trying to do this with the source code open for anyone seems just a waste of time. Second, whatever format OSG reads, before it arrives at the renderer, it's bound to be an array of vertices. The renderer needs this, there's no decryption at the GLSL stage. So chances are that since we run on *Open*GL, again anyone who really wants can write out an unencrypted format.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074186/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Thorsten Renk </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

as FlightGear is open source, it is incredibly simple to add some code to access the 3D scene graph and extract the full aircraft model (scripts excluded, though they could be reverse engineered). The information is just sitting there, fully visible, and ready to be picked off the OSG branch like a big juicy peach. I could probably write this code in half a day, but converting into AC3D format, PNG textures, etc. to recreate a new copy of the aircraft would take a little longer. If FlightGear was closed source, it would be much harder to write OSG extractor code, but nevertheless still doable.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35076297/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = May 10th, 2016
|added = May 10th, 2016
|script_version = 0.39
}}</ref>

We have support for catalogs and external hangars for precisely this reason. We obviously want to encourage GPL aircraft, but not every aircraft developer wishes, or is able to, release their work under the GPL. FlightGear both respects and supports that option. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35076199/
|title = <nowiki> Re: [Flightgear-devel] botom line: if i don't my aircraft to be
subject to GPL FGAddon clauses </nowiki>
|author = <nowiki> Stuart Buchanan </nowiki>
|date = May 10th, 2016
|added = May 10th, 2016
|script_version = 0.39
}}</ref>

You could certainly run the FDM model externally and use one of the many Network I/O options in FlightGear to pass data back and forth. Quite a few research projects have done this in the past to use FlightGear as a visualiation tool. By extension you could do the same for scripting - have the scripting run externally and interact with FlightGear via one of these protocols.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35076187/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Stuart Buchanan </nowiki>
|date = May 10th, 2016
|added = May 10th, 2016
|script_version = 0.39
}}</ref>

if you actually try to charge 100$ for a FG plane, you won't find too many customers... because FG is mainly popular in the OpenSource community. If you make it too cumbersome with DRM schemes, maybe someone will try to circumvent it just as a matter of principle (people do this for sport...) - but across multiple platforms, it's actually not easy to make this not an annoyance for the user.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074186/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Thorsten Renk </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

The thing to keep in mind is that no matter what your source format is (dll, encrypted+signed, binary, etc.), ultimately your model mesh and textures and logical structure are read into internal OSG class structures. Once that has process has completed so the model can be rendered on screen, a person could call the appropriate write*File() function to save out your model's subtree into any of the supported formats. The only thing that is needed is access to the FlightGear source code to insert the function call in a strategic location. Ultimately, you can't completely protect your content work if you don't also completely control the situation at the application source code level. And this is a classic copy protection hacking strategy, insert the magic in the code after the distribution format has been authenticated/loaded/decoded and then write it out in a 'decrypted' format. People do it all the time, even with proprietary code. The value of the target usually determines how hard they are willing to work to steal it.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074534/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Curtis Olson </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.38
}}</ref>

Adding support for DRM to FlightGear is not going to happen - Nasal scripts are provided in plain text format by default (similar to JavaScript), while obfuscation is of course possible - it doesn't make any sense in the context of FlightGear as an open source project.

Also, scripts can be easily shared and run by users just by exchanging or copying them.

Even if you were to dump intermediate Nasal bytecode to an object file and execute this using the Nasal VM, there would be no way of enforcing DRM.

Of course, FlightGear being open source, you could also just add support for DSOs/plugins to a fork of FlightGear and base all your work on this fork - on the other hand, your modifications would still need to be made available.

there's is a way to make legal closed-source add-ons: You can write all your "secret" c++ as an external application, and let that communicate with FlightGear via sockets. This should work reasonably well. But I don't expect that you'll get many customers. First of all, at least on Linux, nobody is keen to run binary blobs, which could easily wipe out your home directory while you are toying around in FlightGear. And then, there's so much Free aircraft development going on, with a lot of momentum, that you'll probably always be behind. And those developers have close ties to the (or are) FlightGear coders, so they have the advantage that they can change the FlightGear code to their liking, at any time. They can change the interface at will, and you have to catch up ... and deal with customer complaints, who suddenly sit on a broken binary blob that doesn't work with the last FlightGear release. And finally, this socket approach works only via property system, and that's open for inspection to anyone (apart from the recently added semi-secret vector property garbage).

FlightGear has no provision to load aircraft from shared libraries. You can distribute your aircraft under a proprietary license, like Vitos does, but not as a shared library. It would take a lot of work to change FlightGear so it can load aircraft from shared libraries. Who would do that work and why would anyone do that when their time could be spent improving free software? And why would the core developers of FlightGear accept such a "contribution"?<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35073736/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Ludovic Brenta </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

Realistically, if you want to sell a commercial aircraft, your customer base is going to be Flight Sim X, X-Plane, Prepar3D. You're simply not going to get any traction in the FlightGear ecosystem. It's not built for it. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074166/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> geneb </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

Besides, OSG's scripting language support (lua) cannot access all the internals Nasal does, simply because there was no glue code implemented in FlightGear. So no properties for you and no access to internal function call which does Nasal provide. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074133/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Erik Hofman </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

You own copyright of your work even if you license it GPL, and you may develop your work further and release a more complete version under a commercial license if you like (that's a variant of dual licensing). The only way to not retain copyright of what you do is to transfer it to someone else or to relinquish it by releasing your work into public domain. If you create a 3d model for a FG aircraft and license it GPL, nobody prevents you from adapting and selling it for X-plane. In fact, you can sell it also for FG (but others may re-distribute it as they like once they buy it since it is GPL, so it may not be a too viable business model) <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35073832/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Thorsten Renk </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

Do other sims offer content encryption or content protection? For instance, I've been able to locate and test a blender plugin that can open up many MSFS aircraft models. How about xplane? It's been a *long* *long* time since I fiddled with their package, but at the time I was paying attention, all their 3d formats were open and well defined. Often the commercial sims will store things in their own binary formats, but in most cases these aren't encrypted and the end users figure these out pretty quickly -- so they can either edit the content or create new content with the same format. I wouldn't consider a binary format much of a content protection scheme ... especially in an open source project where the source to load and store the binary format is readily available. I understand the desire for content creators to not get "ripped off". But also understand that one of the main reasons that FlightGear can be successful is because we make all the source code and content open. If we didn't make everything open, then we wouldn't get nearly the same amount of volunteer contributions and high quality volunteer contributions is the critical reason why FlightGear has been so successful. If we were a closed off commercial outfit, who would want to pitch in and help someone else make money? But with everything open, you know that your contributions can be enjoyed equally by everyone else, just as much as you are enjoying everyone else's contributions. There are some low-lifes out there that try to make a profit on other people's work, and will gladly lie and misrepresent things to swindle as much money as possible from unsuspecting end users. But the truth is that these people have always existed, and will always exist. They are remarkably good and persistent at copying things ... going so far as to break copy protection schemes, reverse engineer hardware designs, copy the exact look of products (even including the logo.) This isn't a problem that is unique to the FlightGear project -- and it's something we would still face no matter how hard we worked to create copy protection schemes. If you designed a binary content format, someone will reverse engineer it. If you design an encryption scheme, someone will just modify the sim code to dump out the decrypted version after it's been loaded into memory by the proprietary decrypting plugin. (If not outright break the encryption scheme or steal your encryption keys.) In all these case, the content can still be easily copied, replicated, sold, etc. The best scheme I've seen is something that has a node-lock key that will only run on a single PC (key'd to mac address, or processor id.) But this implies a more complicated 2 step install where the user must come back to you after installing the product, report their unique id, get a key, and then install that key before they are able to run. And the problem with all of this is that in an open source project, someone could simply compile a new version of the simulator that skips the key check or accepts a trivial key, or any key. I'm just thinking down various avenues here, but hopefully you can see that what seems like a simple request at first is actually quite complex and creates all kinds of down stream issues (both technically and with user support.) And at the end of the day, the bad guys can usually find work arounds anyway and aren't slowed down too much. When farmers grow crops, they have to put up with weeds. We can try reasonable things to minimie the weeds, but if you are too aggressive at killing the weeds and don't tolerate a single one, then you most likely end up killing much of your crop too. So it's my view that this is something we just have to put up with. We can try to take reasonable steps to minimize the problem, but we can't eliminate all the bad guys without harming all the good things about our project.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/27998023/
|title = <nowiki> Re: [Flightgear-devel] Content protection for modders? </nowiki>
|author = <nowiki> Curtis Olson </nowiki>
|date = Aug 25th, 2011
|added = Aug 25th, 2011
|script_version = 0.37
}}</ref>

Once you have distributed source code under the GPL you explicitely declared that it's everyones right to redistribute and modify it - as long as he/she doesn't distribute it under a different license But you, as the copyright holder, can change the license for new versions you haven't yet distributed under the GPL - as long as those modifications weren't made by others, i.e., as long as you are still the sole copyright holder (or you'd have to come to an agreement with the other contributors, but you can only ask nicely). You, as the sole copyright holder, also can distribute it under several licenses at once, e.g. the GPL and some propiratory li- cense (making it worth the money people may pay for it by faster bug fixes, only distributed to the paying customers etc.).<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35073990/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Jens Thoms Toerring </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

Another thing to consider is that distributing your aircraft as a .dll or .so doesn't hide or obfuscate your code and textures after they have been loaded into the simulator structures for rendering. The rest of FlightGear is open-source so it wouldn't take much effort to insert an OSG function call to save out the aircraft (models and textures) in some other common 3d format. There would be some loss in terms of the organiation of the source files, but even so, it would give someone who's intention is to copy or modify the work a place to start. All the xml config should be there for free in the property tree. The licensing of nasal (I believe) is written in a way that makes it difficult to distribute proprietary nasal code. So there would be some really significant challenges to making a FlightGear aircraft that is secure from modification, not to mention copying.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35073896/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Curtis Olson </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.37
}}</ref>

The key for an open source project is not if you can win a legal argument or not. Rather, it is to avoid any legal argument in the first place, and at all costs. Meaning to stay out of court. To use something like this safely in an open source project, I would suggest something along the following lines:
* Making your derivative product public, in full (but unlicensed, saying it is copyrighted material),
* Going to the owners of the original data product, giving them a link to your derivative product,
* Asking them to make a public statement that the derivative product can be licensed using the "GPLv2 or later version" licence,
* Make sure to ask them to identify the public derivative product as a link, and identify all its parts (to avoid them saying at a later date that you included bits of the protected material),

Any statement they make on the web can be backed up on the web archive ( http://web.archive.org/ ). To simplify the process, you could draft part of the statement detailing the derivative product in full, with all details. With this, there will no longer be any shades of grey! If they are happy to do this, then it is legally no problem to use (i.e. the grey situation has shifted to white). If they are not happy with your proposal, then they could turn around one day and sue (i.e. the grey situation has shifted to a clear black).<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/34561220/
|title = <nowiki> Re: [Flightgear-devel] External FDM to protect propriety data in a
GPL eviirenment </nowiki>
|author = <nowiki> Edward d'Auvergne </nowiki>
|date = Oct 22nd, 2015
|added = Oct 22nd, 2015
|script_version = 0.37
}}</ref>

The open-source world depends on license terms and copyrights and cooperation and trust to protect our work. We put up with a small subset of people who willing abuse those terms and hope that larger group peer pressure will keep the bad actors in check. Sometimes there is legal recourse, sometimes it is tough to do anything about it when problems span country boundaries (or when someone just wants to break the rules for their own self serving reasons.) My feeling though is in the long term, most people are honest and do wish to do the right thing, and the small group that is truly there to cause problems or just serve themselves at the expense of others will never endure as long as the larger group of people with good intentions. In the end, you have to make your own determination of how much effort you put into a model, versus how much money you could make selling it, versus the risk of someone copying and distributing it themselves, versus the legal costs to try to stop them.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35074534/
|title = <nowiki> Re: [Flightgear-devel] can i distribute my airplane as a shared
library, and what legislation issues would that ensue? </nowiki>
|author = <nowiki> Curtis Olson </nowiki>
|date = May 9th, 2016
|added = May 9th, 2016
|script_version = 0.38
}}</ref>

=== DRM workarounds ===
For one of my past projects I had to deal with a proprietary flight dynamics model. I initially used the ethernet interface so it could run as an external stand alone application. Then later I switched to a unix two-way pipe arrangement so I could have tighter synchroniation with the execution order, but still the external program was completely independent and stand alone. I'd love to make everything free and open-source, but this was a case where I didn't have a choice and it was something purchased from a 3rd party company with strict terms. I felt that two independent self sufficient programs (that could talk to each other and exchange information) created sufficient license separation to honor FlightGear's gpl license terms. <ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/34559783/
|title = <nowiki> Re: [Flightgear-devel] External FDM to protect propriety data in a
GPL eviirenment </nowiki>
|author = <nowiki> Curtis Olson </nowiki>
|date = Oct 21st, 2015
|added = Oct 21st, 2015
|script_version = 0.37
}}</ref>

For what it's worth, the "ExternalPipe" fdm was setup to cover much of the areas you have touched on. It's probably not exactly what you want but here was some of my logic in how/why I setup it up the way I did.
* Using a network interface adds some indeterminism ... sometimes network packets are delayed or stack up depending on what is going on with the machine so there isn't a guaranteed lockstep relationship between the simulator the the flight dynamics.
* Usually the network interface is good, but I observed times when it had extra delays in packets getting where they needed to go.
* As an alternative, I setup a pair of "named pipes". Pipes are a unix construct, they look like a file to the program, but what you write into them is collected and held for some other application to read out. Unfortunately these are not supported in windows. Pipes are single direction, thus the need for two of them for bi-directional communication. A pipe is really simple: you open it up like any other file, and one process writes into it; the other process reads from it. In between the OS can buffer some amount of information until the reader grabs it. You can use blocking reads (carefully) to ensure FlightGear and your external FDM run in exact lockstep.
* Pipes imply both processes will run on the same machine, a network interface would allow the processes to live on separate machines.
* The ExternalPipe interface supports a flexible property interface, so the external FDM process can send any name/value pairs it wishes to send and the interface will dutifully copy them into the FlightGear property tree. The FDM side can also send a list of property names it would like to receive in reply and the interface will dutifully send them over the outgoing pipe every frame. This was a nice addition, and there is plenty of bandwidth through a named pipe to do this in clear text, even with a lot of extra property values.

History: I used this as part of a project I did with ATC flight sim. They had their own proprietary flight dynamics applications that modeled specific aircraft in the code itself. These models had all the necessary source documentation and flight test data to satisfy FAA certification testing requirements of the final simulator. In addition, this external code modelled many of the aircraft systems for one of their high end sims. This required the ability to be flexible in what values were sent back and forth and enabled me to drive some instrument gauges directly from the external code.<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/31900851/
|title = <nowiki> Re: [Flightgear-devel] Feeding FlightGear data through the Protocol
Pipe </nowiki>
|author = <nowiki> Curtis Olson </nowiki>
|date = Jan 29th, 2014
|added = Jan 29th, 2014
|script_version = 0.37
}}</ref>

[[Category:FlightGear]]

[[de:FAQ]]
[[es:Preguntas frecuentes]]
[[fr:Foire aux questions]]
[[it:Domande frequenti]]
[[ja:FAQ]]
[[nl:veel gestelde vragen]]
[[pl:FAQ]]
[[pt:FAQ]]
[[pt-br:Perguntas_frequentes]]
[[sr:FAQ]]

Template:News

2025-11-02T16:40:20Z

Gijs: 2024.1.3

{{LangSwitch
| en = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archive]])
| de = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}|FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | de }}]] ([[:de:FlightGear Newsletter|Archiv]])
| es = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivo]])
| ca = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|Arxiu]])
| it = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archivio]])
| nl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archief]])
| pl = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|archiwum]])
| pt = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|arquivo]])
| ru = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }}]] ([[FlightGear Newsletter|архив]])
| zh = 
: [[FlightGear Newsletter {{#time: F Y | {{{date|last month}}} | en }} | FlightGear {{#time: Y"年"F | {{{date|last month}}} | zh }}通讯（英文）]] （[[FlightGear Newsletter|所有历史通讯]]）
}}
{{Localized Release Announcement |date=02-11-2025 |version=2024.1.3}}
{{Localized Release Announcement |date=18-09-2025 |version=2024.1.2}}
{{Localized Release Announcement |date=27-02-2025 |version=2024.1.1}}
<noinclude>


{{Informative template|1=
This template contains the news section as displayed on the [[Main Page]], for each single language.

== Usage ==
* Use no more than five news items (excluding the newsletter)
* Use short text lines
* Use present tense

== Related templates ==
* {{tl|Localized Release Announcement}}

}}

[[Category:Templates]]
</noinclude>

Template:GitStatus

2025-11-02T14:58:30Z

Gijs: Remove obsolete changelog links

{| cellspacing="5" width="100%"
| align="center" | {{LangSwitch
| en = 
'''Current release:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|en}}) '''Next release:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} from now)|}} See [[release plan]] for details.
| de = 
'''Aktuelle Version:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|de}}) '''Nächste Version:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} ab jetzt)|}} Siehe [[release plan|Release-Plan]] für weitere Einzelheiten.
| nl = 
'''Huidige versie:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|nl}}) '''Volgende versie:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} vanaf nu)|}} Zie [[release plan|vrijlating plan]] voor details.
| es = 
'''Lanzamiento actual:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|es}}) '''Próxima versión:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} a partir de ahora)|}} Ver [[release plan|plan de lanzamiento]] para más detalles.
| fr = 
'''Version actuelle:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|fr}}) '''Prochaine publication:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} à partir de maintenant)|}} Voir [[release plan|plan de libération]] pour les détails.
| pt = 
'''A versão atual:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|pt}}) '''Próximo lançamento:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} a partir de agora)|}} Ver [[release plan|plano de lançamento]] para mais detalhes.
| ru = 
'''Текущий релиз:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|ru}}) '''Следующий релиз:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} с этого момента)|}} См [[release plan|план выпуска]] Подробности
| pl = 
'''Aktualna wersja:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|pl}}) '''Następnie zwolnić:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} od teraz)|}} Zobacz szczegóły [[release plan|planu zwalniania]]
| sr = 
'''Тренутно издање:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|sr}}) '''Следеће издање:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} од сада)|}} Погледајте [[release plan|релеасе план]] за детаље
| sl = 
'''Trenutni javnost:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|sl}}) '''Naslednja objava:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} od zdaj)|}} Glej [[release plan|načrt javnost]] podrobnosti
| ca = 
'''Versió actual:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|ca}}) '''Següent versió:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} a partir d'ara)|}} Veure [[release plan|pla de llançament]] per a més detalls
| ja = 
'''現在のリリース:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|ja}}) '''次のリリース:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} 今から)|}} 詳細については、[[release plan|リリース計画]]を参照してください。
| fa = 
'''نسخه فعلی:''' [http://www.flightgear.org/download/ {{Current release|full}}] ({{#time:j M Y|{{Current release|fulldate}}|fa}}) '''نسخه بعدی:''' {{Current release|nr}} {{#if: {{Current release|nrd}}|({{Current release|nrd}} از هم اکنون)|}} دیدن طرح آزاد ([[release plan|اینجا]]) برای جزئیات
}}
|}<noinclude>
{{Informative template|1=
== Goal ==
This template displays information about the current release state of [[FlightGear]]. It display the current, date of that release, the next release, and the time until the next release.

== Usage ==
{{obr}}'''GitStatus'''{{cbr}}

== See also ==
* [[Release plan]]

}}

[[Category:Git templates]]

</noinclude>

Template:Current release

2025-11-02T14:56:11Z

Gijs: 2024.1.3

<includeonly>{{#switch: {{{1|}}}
| cr = 2024.1
| crd = 27 February 2025
| nr = 2024.1.4
| nrd = 

| full = 2024.1.3
| fulldate = 2 November 2025

| #default = {{error|No argument given|current release}}
}}</includeonly><noinclude>
{{Informative template|1=
== Goal ==
This template is used internally by {{tl|GitStatus}} to display:
# the current release
# the release date of the current release
# the next release
# the number of days until the next release. Leave empty or comment if unknown
# the full version of the newest release and its release date

This template should be updated with every new release, including bugfix releases.

== Usage ==
{{obr}}'''current release'''{{!}}data{{cbr}}

; data : Dictates what data is returned. This parameter is mandatory. Value may be one of:
:*'''cr''': Current release
:*'''crd''': Release date of current release
:*'''nr''': Next release
:*'''nrd''': Days until the next release

== Examples ==
{{obr}}current release{{!}}cr{{cbr}}
{{current release|cr}}

== Related template ==
* {{tl|GitStatus}}

== See also ==
* [[Release plan]]

}}

[[Category:Git templates]]
</noinclude>

Template:Infobox aircraft

2025-11-02T14:16:14Z

Gijs: Update download link to 2024

<includeonly>{{Infobox
| title = {{{name|{{LangSwitch
| ca = Aeronau desconeguda
| de = Unbekanntes Flugzeug
| en = Unknown Aircraft
| es = Avión desconocido
| fr = Aéronef Inconnu
| it = Aeromobile sconosciuto
| pl = Nieznany samolot
| ru = Неизвестный летательный аппарат
| th = เครื่องบินที่ไม่รู้จัก
| zh = 未知机型
}}
}}}
| above{{#if:{{{hangar|}}}||NULL}}
= {{hangar banner|{{{hangar}}}}}
| image = {{#if: {{{image|}}}
| [[File:{{{image}}}|300px|{{{alt|}}}]]
| [[Special:UploadWizard|{{LangSwitch
| ca = Cal una imatge
| de = Benötigt ein Bild
| en = Image requested
| es = Necesita una imagen
| it = Immagine richiesta
| pl = Brak obrazka
| th = ถ่ายรูปเครื่องบินนี้เลยสิ!
| zh = 需要图片
}}]] [[Category:Aircraft requiring a screenshot]]
}}
| caption = {{{alt|}}}
| image2 = {{#if: {{{image2|}}}
| [[File:{{{image2}}}{{!}}300px|{{{alt2|}}}]]
| [[Category:Aircraft requiring a cockpit screenshot]]
}}
| caption2 = {{{alt2|}}}
| label1 = {{LangSwitch
| ca = Tipus
| de = Typ
| en = Type
| es = Tipo
| fr = Type
| it = Tipo
| ja = て
| nl = Type
| pl = Typ
| pt = Tipo
| ru = Тип
| th = ชนิดเครื่องบิน
| zh = 类型
}}
| data1 = {{craft type|{{#titleparts:/{{{type|}}}|1|2}}}}{{craft type|{{#titleparts:/{{{type|}}}|1|3}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|4}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|5}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|6}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|7}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|8}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|9}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|10}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|11}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|12}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|13}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|14}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|15}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|16}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|17}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|18}}|pre=, <nowiki></nowiki>}}{{craft type|{{#titleparts:/{{{type|}}}|1|19}}|pre=, <nowiki></nowiki>}}
| label2 = {{LangSwitch
| ca = Configuració
| de = Konfiguration
| en = Configuration
| es = Configuración
| fi = Kokoonpanoon
| fr = Configuration
| it = Configurazione
| ja = 設定
| nl = Configuratie
| pl = Konfiguracja
| pt = Configuração
| ru = Конфигурация
| th = โครงสร้างของเครื่องบิน
| zh = 构型
}}
| data2 = {{craft configuration|{{#titleparts:/{{{config|}}}|1|2}}}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|3}}|pre=, <nowiki></nowiki>}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|4}}|pre=, <nowiki></nowiki>}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|5}}|pre=, <nowiki></nowiki>}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|6}}|pre=, <nowiki></nowiki>}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|7}}|pre=, <nowiki></nowiki>}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|8}}|pre=, <nowiki></nowiki>}}{{craft configuration|{{#titleparts:/{{{config|}}}|1|9}}|pre=, <nowiki></nowiki>}}
| label3 = {{LangSwitch
| ca = Propulsió
| de = Antrieb
| en = Propulsion
| es = Propulsión
| fr = Propulsion
| it = Propulsione
| ja = 推進
| nl = Aandrijving
| pl = Napęd
| pt = Propulsão
| ru = Движение
| th = เครื่องยนต์
| zh = 动力
}}
| data3 = {{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|2}}}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|3}}|pre=, <nowiki></nowiki>}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|4}}|pre=, <nowiki></nowiki>}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|5}}|pre=, <nowiki></nowiki>}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|6}}|pre=, <nowiki></nowiki>}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|7}}|pre=, <nowiki></nowiki>}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|8}}|pre=, <nowiki></nowiki>}}{{craft propulsion|{{#titleparts:/{{{propulsion|}}}|1|9}}|pre=, <nowiki></nowiki>}}
| label4 = {{LangSwitch
| ca = Fabricant
| de = Hersteller
| en = Manufacturer
| es = Fabricante
| fr = Constructeur
| it = Costruttore
| ja = メーカー
| nl = Fabrikant
| pl = Producent
| pt = Fabricante
| ru = Производитель
| th = ผู้ผลิต
| zh = 制造商
}}
| data4 = {{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|2}}}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|3}}|pre=, <nowiki></nowiki>}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|4}}|pre=, <nowiki></nowiki>}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|5}}|pre=, <nowiki></nowiki>}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|6}}|pre=, <nowiki></nowiki>}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|7}}|pre=, <nowiki></nowiki>}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|8}}|pre=, <nowiki></nowiki>}}{{craft manufacturer|{{#titleparts:/{{{manufacturer|}}}|1|9}}|pre=, <nowiki></nowiki>}}
| label5 = {{LangSwitch
| ca = Autor(s)
| de = Autor(en)
| en = Author(s)
| es = Autor(es)
| fr = Créateur(s)
| it = Autore/i
| pl = Autorzy
| ru = Автор(ы)
| th = ผู้สร้าง(ใน FlightGear)
| zh = 作者
}}
| data5 = {{#if: {{{devel-team|}}} | <div class="toccolours mw-collapsible mw-collapsed" style="padding: 0px; border: none">{{{devel-team}}}<div class="mw-collapsible-content">}}{{#if: {{{authors|{{{author1|}}}}}}
| {{#if: {{#titleparts:/{{{authors|}}}|1|3}} 
| {{#if: {{#titleparts:/{{{authors|}}}|1|2}} | * {{#titleparts:/{{{authors|}}}|1|2}} }}
| {{#if: {{{author1|}}}
| {{#if: {{{authors|}}}
| {{#if: {{#titleparts:/{{{authors|}}}|1|2}} | * {{#titleparts:/{{{authors|}}}|1|2}} }}
| {{#if: {{#titleparts:/{{{authors|}}}|1|2}} | {{#titleparts:/{{{authors|}}}|1|2}} }}
}}
| {{#if: {{#titleparts:/{{{authors|}}}|1|2}} | {{#titleparts:/{{{authors|}}}|1|2}} }}
}}
}}{{#if: {{#titleparts:/{{{authors|}}}|1|3}} | * {{#titleparts:/{{{authors|}}}|1|3}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|4}} | * {{#titleparts:/{{{authors|}}}|1|4}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|5}} | * {{#titleparts:/{{{authors|}}}|1|5}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|6}} | * {{#titleparts:/{{{authors|}}}|1|6}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|7}} | * {{#titleparts:/{{{authors|}}}|1|7}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|8}} | * {{#titleparts:/{{{authors|}}}|1|8}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|9}} | * {{#titleparts:/{{{authors|}}}|1|9}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|10}} | * {{#titleparts:/{{{authors|}}}|1|10}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|11}} | * {{#titleparts:/{{{authors|}}}|1|11}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|12}} | * {{#titleparts:/{{{authors|}}}|1|12}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|13}} | * {{#titleparts:/{{{authors|}}}|1|13}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|14}} | * {{#titleparts:/{{{authors|}}}|1|14}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|15}} | * {{#titleparts:/{{{authors|}}}|1|15}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|16}} | * {{#titleparts:/{{{authors|}}}|1|16}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|17}} | * {{#titleparts:/{{{authors|}}}|1|17}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|18}} | * {{#titleparts:/{{{authors|}}}|1|18}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|19}} | * {{#titleparts:/{{{authors|}}}|1|19}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|20}} | * {{#titleparts:/{{{authors|}}}|1|20}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|21}} | * {{#titleparts:/{{{authors|}}}|1|21}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|22}} | * {{#titleparts:/{{{authors|}}}|1|22}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|23}} | * {{#titleparts:/{{{authors|}}}|1|23}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|24}} | * {{#titleparts:/{{{authors|}}}|1|24}} }}{{#if: {{#titleparts:/{{{authors|}}}|1|25}} | * {{#titleparts:/{{{authors|}}}|1|25}} }}{{#if: {{{authors|}}} 
| {{#if: {{{author1|}}} | * {{{author1}}} }}
| {{#if: {{{author2|}}}
| {{#if: {{{author1|}}} | * {{{author1}}} }}
| {{#if: {{{author1|}}} | {{{author1}}} }}
}}
}}{{#if: {{{author2|}}} | * {{{author2}}} }}{{#if: {{{author3|}}} | * {{{author3}}} }}{{#if: {{{author4|}}} | * {{{author4}}} }}{{#if: {{{author5|}}} | * {{{author5}}} }}{{#if: {{{author6|}}} | * {{{author6}}} }}{{#if: {{{author7|}}} | * {{{author7}}} }}{{#if: {{{author8|}}} | * {{{author8}}} }}{{#if: {{{author9|}}} | * {{{author9}}} }}{{#if: {{{author10|}}} | * {{{author10}}} }}{{#if: {{{author11|}}} | * {{{author11}}} }}{{#if: {{{author12|}}} | * {{{author12}}} }}{{#if: {{{author13|}}} | * {{{author13}}} }}{{#if: {{{author14|}}} | * {{{author14}}} }}{{#if: {{{author15|}}} | * {{{author15}}} }}{{#if: {{{author16|}}} | * {{{author16}}} }}{{#if: {{{author17|}}} | * {{{author17}}} }}{{#if: {{{author18|}}} | * {{{author18}}} }}{{#if: {{{author19|}}} | * {{{author19}}} }}{{#if: {{{author20|}}} | * {{{author20}}} }}{{#if: {{{author21|}}} | * {{{author21}}} }}{{#if: {{{author22|}}} | * {{{author22}}} }}{{#if: {{{author23|}}} | * {{{author23}}} }}{{#if: {{{author24|}}} | * {{{author24}}} }}{{#if: {{{author25|}}} | * {{{author25}}} }}{{#if: {{{author26|}}} | * {{{author26}}} }}{{#if: {{{author27|}}} | * {{{author27}}} }}{{#if: {{{author28|}}} | * {{{author28}}} }}{{#if: {{{author29|}}} | * {{{author29}}} }}{{#if: {{{author30|}}} | * {{{author30}}} }}
| {{LangSwitch
| ca = Desconegut
| de = Unbekannt
| en = Unknown
| es = Desconocido
| fr = Inconnu
| it = Sconosciuto
| pl = Nieznani
| ru = Неизвестен
| th = ไม่ทราบ
| zh = 未知
}}
}}{{#if: {{{devel-team|}}} | </div></div>}}
| label6 = FDM
| data6 = {{#if: {{{fdm|}}}
| {{FDM link|{{#titleparts:/{{{fdm|}}}|1|2}}}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|3}}|pre=, <nowiki></nowiki>}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|4}}|pre=, <nowiki></nowiki>}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|5}}|pre=, <nowiki></nowiki>}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|6}}|pre=, <nowiki></nowiki>}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|7}}|pre=, <nowiki></nowiki>}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|8}}|pre=, <nowiki></nowiki>}}{{FDM link|{{#titleparts:/{{{fdm|}}}|1|9}}|pre=, <nowiki></nowiki>}}
| {{LangSwitch
| ca = Desconegut
| de = Unbekannt
| en = Unknown
| es = Desconocido
| fr = Inconnu
| it = Sconosciuto
| pl = Nieznany
| ru = Неизвестен
| th = ไม่ทราบ
| zh = 未知
}}
}}
| label7 = --aircraft=
| data7 = {{#if: {{{fgname|}}}
| {{#if: {{#titleparts:/{{{fgname|}}}|1|2}} | <tt>{{#titleparts:/{{{fgname|}}}|1|2}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|3}} | <tt> {{#titleparts:/{{{fgname|}}}|1|3}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|4}} | <tt> {{#titleparts:/{{{fgname|}}}|1|4}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|5}} | <tt> {{#titleparts:/{{{fgname|}}}|1|5}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|6}} | <tt> {{#titleparts:/{{{fgname|}}}|1|6}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|7}} | <tt> {{#titleparts:/{{{fgname|}}}|1|7}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|8}} | <tt> {{#titleparts:/{{{fgname|}}}|1|8}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|9}} | <tt> {{#titleparts:/{{{fgname|}}}|1|9}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|10}} | <tt> {{#titleparts:/{{{fgname|}}}|1|10}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|11}} | <tt> {{#titleparts:/{{{fgname|}}}|1|11}}</tt>}}{{#if: {{#titleparts:/{{{fgname|}}}|1|12}} | <tt> {{#titleparts:/{{{fgname|}}}|1|12}}</tt>}}
}}{{#if: {{{fgname1|}}}
| {{#if: {{{fgname|}}}
| <tt> {{{fgname1}}}</tt>
| <tt>{{{fgname1}}}</tt>
}}
}}{{#if: {{{fgname2|}}} | <tt> {{{fgname2}}}</tt>}}{{#if: {{{fgname3|}}} | <tt> {{{fgname3}}}</tt>}}{{#if: {{{fgname4|}}} | <tt> {{{fgname4}}}</tt>}}{{#if: {{{fgname5|}}} | <tt> {{{fgname5}}}</tt>}}{{#if: {{{fgname6|}}} | <tt> {{{fgname6}}}</tt>}}{{#if: {{{fgname7|}}} | <tt> {{{fgname7}}}</tt>}}{{#if: {{{fgname8|}}} | <tt> {{{fgname8}}}</tt>}}{{#if: {{{fgname9|}}} | <tt> {{{fgname9}}}</tt>}}{{#if: {{{fgname10|}}} | <tt> {{{fgname10}}}</tt>}}
| label8 = {{LangSwitch
| ca = Estat
| de = Stand
| en = Status
| es = Estado
| fr = Etat
| it = Stato
| ja = ステータス
| nl = Status
| pl = Status
| pt = Situação
| ru = Статус
| th = คะแนนความละเอียด
| zh = 开发状况
}}
| data8 = {{#if: {{{status-fdm|}}}
| {{#ifexpr: {{#expr: {{{status-fdm|}}}+{{{status-systems|}}}+{{{status-cockpit|}}}+{{{status-model|}}} }} > 17
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus#Estat general|Producció avançada]]
| de = [[De/Flugzeugbewertung#Gesamtwertung|Fortgeschrittene Produktion]]
| en = [[Aircraft rating system#Overall status|Advanced production]]
| es = [[Aircraft rating system#Overall status|Producción avanzada]]
| fr = [[Fr/Aircraft status indication#Statut global|Production avancée]]
| pl = [[Aircraft rating system#Overall status|Zaawansowana produkcja]]
| ru = [[Aircraft rating system#Overall status|Продвинутый релиз]]
}}
[[Category:Aircraft status: Advanced production]]
| {{#ifexpr: {{#expr: {{{status-fdm|}}}+{{{status-systems|}}}+{{{status-cockpit|}}}+{{{status-model|}}} }} > 15
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus#Estat general|Producció]]
| de = [[De/Flugzeugbewertung#Gesamtwertung|Produktion]]
| en = [[Aircraft rating system#Overall status|Production]]
| es = [[Aircraft rating system#Overall status|Producción]]
| fr = [[Fr/Aircraft status indication#Statut global|Production]]
| pl = [[Aircraft rating system#Overall status|Produkcja]]
| ru = [[Aircraft rating system#Overall status|Релиз]]
}}
[[Category:Aircraft status: Production]]
| {{#ifexpr: {{#expr: {{{status-fdm|}}}+{{{status-systems|}}}+{{{status-cockpit|}}}+{{{status-model|}}} }} > 11
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus#Estat general|Producció primerenca]]
| de = [[De/Flugzeugbewertung#Gesamtwertung|Frühe Produktion]]
| en = [[Aircraft rating system#Overall status|Early production]]
| es = [[Aircraft rating system#Overall status|Producción temprana]]
| fr = [[Fr/Aircraft status indication#Statut global|Production précoce]]
| pl = [[Aircraft rating system#Overall status|Wczesna produkcja]]
| ru = [[Aircraft rating system#Overall status|Пре-релиз]]
}}
[[Category:Aircraft status: Early production]]
| {{#ifexpr: {{#expr: {{{status-fdm|}}}+{{{status-systems|}}}+{{{status-cockpit|}}}+{{{status-model|}}} }} > 8
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus#Estat general|Beta]]
| de = [[De/Flugzeugbewertung#Gesamtwertung|Beta]]
| en = [[Aircraft rating system#Overall status|Beta]]
| fr = [[Fr/Aircraft status indication#Statut global|Bêta]]
| pl = [[Aircraft rating system#Overall status|Beta]]
| ru = [[Aircraft rating system#Overall status|Бета-версия]]
}}
[[Category:Aircraft status: Beta]]
| {{#ifexpr: {{#expr: {{{status-fdm|}}}+{{{status-systems|}}}+{{{status-cockpit|}}}+{{{status-model|}}} }} < 9
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus#Estat general|Alfa]]
| de = [[De/Flugzeugbewertung#Gesamtwertung|Alpha]]
| en = [[Aircraft rating system#Overall status|Alpha]]
| fr = [[Fr/Aircraft status indication#Statut global|Alpha]]
| pl = [[Aircraft rating system#Overall status|Alfa]]
| ru = [[Aircraft rating system#Overall status|Альфа-версия]]
}}
[[Category:Aircraft status: Alpha]]
|
}}
}}
}}
}}
}}
| {{#if:{{{status|}}}
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus|{{{status}}}]]
| de = [[De/Flugzeugbewertung|{{{status}}}]]
| en = [[Aircraft rating system|{{{status}}}]]
| fr = [[Fr/Aircraft status indication|{{{status}}}]]
}}
| {{LangSwitch
| ca = [[Ca/Sistema de qualificació d'aeronaus|Desconegut]]
| de = [[De/Flugzeugbewertung|Unbekannt]]
| en = [[Aircraft rating system|Unknown]]
| es = [[Aircraft rating system|Desconocido]]
| fr = [[Fr/Aircraft status indication|Inconnu]]
| pl = [[Aircraft rating system|Nieznany]]
| ru = [[Aircraft rating system|Неизвестен]]
}}
}}
}}
| label9 = &emsp;FDM
| data9 = {{#if:{{{status-fdm|}}}
| [[File:stars-{{{status-fdm}}}.png|link={{LangSwitch
| ca = Ca/Sistema de qualificació d'aeronaus#Flight Dynamics Model (FDM)
| de = De/Flugzeugbewertung#Flight Dynamics Model (FDM)
| en = Aircraft rating system#Flight Dynamics Model (FDM)
| fr = Fr/Aircraft status indication#Modèle de vol dynamique
}}
]]
}}
| label10 = &emsp;{{LangSwitch
| ca = Sistemes
| de = Systeme
| en = Systems
| es = Sistemas
| fr = Systèmes
| it = Sistemi
| pl = Systemy
| ru = Системы
| th = ระบบที่ใช้งานได้
| zh = 系统
}}
| data10 = {{#if:{{{status-systems|}}}
| [[File:stars-{{{status-systems}}}.png|link={{LangSwitch
| ca = Ca/Sistema de qualificació d'aeronaus#Sistemes
| de = De/Flugzeugbewertung#Systeme
| en = Aircraft rating system#Systems
| fr = Fr/Aircraft status indication#Systèmes
}}
]]
}}
| label11 = &emsp;{{LangSwitch
| ca = Cabina de pilotatge
| de = Cockpit
| en = Cockpit
| es = Cabina de vuelo
| fi = Ohjaamo
| fr = Cockpit
| it = Cabina di pilotaggio
| ja = コックピット
| nl = Cockpit
| pl = Kokpit
| pt = Cabine de pilotagem
| ru = Кабина
| sl = Pilotska kabina
| th = ห้องนักบินและปุ่มต่างๆ
| zh = 驾驶舱
}}
| data11 = {{#if:{{{status-cockpit|}}}
| [[File:stars-{{{status-cockpit}}}.png|link={{LangSwitch
| ca = Ca/Sistema de qualificació d'aeronaus#Cabina de pilotatge
| de = De/Flugzeugbewertung#Cockpit
| en = Aircraft rating system#Cockpit
| fr = Fr/Aircraft status indication#Cockpit
}}
]]
}}
| label12 = &emsp;{{LangSwitch
| ca = Model
| de = Modell
| en = Model
| es = Modelo
| fr = Modèle
| it = Modello
| ru = Модель
| th = แบบจำลอง
| zh = 模型
}}
| data12 = {{#if:{{{status-model|}}}
| [[File:stars-{{{status-model}}}.png|link={{LangSwitch
| ca = Ca/Sistema de qualificació d'aeronaus#Model exterior
| de = De/Flugzeugbewertung#Äußeres Modell
| en = Aircraft rating system#External Model
| fr = Fr/Aircraft status indication#Modèle externe
}}
]]
}}
| label13 = {{LangSwitch
| ca = Suporta
| de = Unterstützt
| en = Supports
| es = Soporta
| fr = Soutien
| it = Supporta
| pl = Wsparcie
| ru = Поддерживает
| th = คุณลักษณะที่สนับสนุน
| zh = 支持功能
}}
| data13 = {{Ready|{{#titleparts:/{{{ready|}}}|1|2}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|3}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|4}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|5}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|6}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|7}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|8}}}} {{Ready|{{#titleparts:/{{{ready|}}}|1|9}}}}
| label20 = {{LangSwitch
| ca = Desenvolupament
| de = Entwicklung
| en = Development
| es = Desarrollo
| fr = Développement
| it = Sviluppo
| ja = 開発
| nl = Ontwikkeling
| pl = Rozwój
| pt = Desenvolvimento
| ru = Разработка
| th = ที่พัฒนา
| zh = 开发
}}
| data20 = {{#if: {{{devel-hangar|}}}
| &emsp;
| {{#if: {{{devel-website|}}}
| &emsp;
| {{#if: {{{devel-repo|}}}
| &emsp;
| {{#if: {{{development|}}}
| &emsp;
| {{#switch: {{{hangar|none}}}
| bermuda
| none =
| #default = &emsp;
}}
}}
}}
}}
}}
| label21 = &emsp;{{LangSwitch
| ca = Hangar
| de = Hangar
| en = Hangar
| es = Hangar
| fr = Hangar
| it = Hangar
| ru = Ангар
| th = หน่วยงาน ("Hangar")
| zh = 机库
}}
| data21 = {{hangar banner|{{{devel-hangar|}}}|size=180px}}
| label22 = &emsp;{{LangSwitch
| ca = Lloc web
| de = Webseite
| en = Website
| es = Página web
| fr = Site Internet
| it = Sito Web
| ja = ウェブサイト
| nl = Website
| pl = Strona internetowa
| pt = Website
| ru = Веб-сайт
| th = เว็บไซต์ของหน่วยงาน
| zh = 网站
}}
| data22 = {{#if: {{{devel-website|}}}
| [[File:Applications-internet 32x32.png | 30px | {{LangSwitch
| ca = El lloc web de desenvolupament de {{{name|}}}.
| de = Die Webseite für die Entwicklungen von {{{name|}}}.
| en = The website for the {{{name|}}} developments.
| es = La página web para los desarrollos de {{{name|}}}.
| fr = Le site internet des développements de {{{name|}}}.
| it = Il sito Web di sviluppo di {{{name|}}}.
| pl = Strona internetowa dotycząca rozwoju: {{{name|}}}.
| th = เว็บไซต์ของผู้ที่พัฒนา {{{name|}}}
}} | link={{{devel-website}}}
]]
| {{#switch: {{{hangar|}}}
| aucafly
| buckaroo
| bulldogrs
| dave
| fgaddon
| fguk
| helijah
| herbyw
| lake of constance
| paf
| prestes =
[[File:Applications-internet 32x32.png | 30px | {{LangSwitch
| ca = El lloc web de desenvolupament de {{{name|}}}.
| de = Die Webseite für die Entwicklungen von {{{name|}}}.
| en = The website for the {{{name|}}} developments.
| es = La página web para los desarrollos de {{{name|}}}.
| fr = Le site internet des développements de {{{name|}}}.
| it = Il sito Web di sviluppo di {{{name|}}}.
| pl = Strona internetowa dotycząca rozwoju: {{{name|}}}.
| th = เว็บไซต์ของผู้ที่พัฒนา {{{name|}}}
| zh = 用于开发{{{name|}}}的网站
}} | link={{#switch: {{{hangar|}}}
| aucafly = https://aucafly.wordpress.com/
| buckaroo = http://www.buckarooshangar.com/flightgear/
| bulldogrs = https://bulldogrs.wordpress.com/
| dave = http://www.daveshangar.org/
| fgaddon = {{fullurl:FGAddon}}
| fguk = http://fguk.eu/index.php/hangar
| helijah = {{LangSwitch
| en = http://helijah.free.fr/flightgear/hangaren.htm
| fr = http://helijah.free.fr/flightgear/hangar.htm
}}
| herbyw = https://github.com/HerbyW
| lake of constance = http://www.marc-kraus.de
| paf = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-p-a-f-paf-team-hangar
| prestes = http://presteshangar.wikidot.com/{{{aircraft|}}}
}}
]]
}}
}}
| label23 = &emsp;{{LangSwitch
| ca = Repositori
| de = Repository
| en = Repository
| es = Repositorio
| fr = Référentiel
| it = Repository
| ja = レポジトリ
| nl = Repository
| pl = Repozytorium
| pt = Repositório
| ru = Репозиторий
| zh = 代码仓库
}}
| data23 = {{#if:{{{devel-repo|{{{development|}}}}}}
| [[File:Preferences-system 32x32.png | 30px | {{LangSwitch
| ca = El repositori de desenvolupament de {{{name|}}}.
| de = Die Entwicklungs-Repository des {{{name|}}}.
| en = The development repository of the {{{name|}}}.
| es = El Repositorio de desarrollo de {{{name|}}}.
| fr = Le référentiel de développement du {{{name|}}}.
| it = Il repository di sviluppo di {{{name|}}}.
| pl = Repozytorium programistyczne {{{name|}}}.
| th = Repository ที่ใช้พัฒนา {{{name|}}}
}} | link={{{devel-repo|{{{development|}}}}}}
]]
| {{#switch: {{{hangar|}}}
| aucafly
| bulldogrs
| emilianh
| fgaddon
| herbyw
| JMaverick16
| Octal450 =
[[File:Preferences-system 32x32.png | 30px | {{LangSwitch
| ca = El repositori de desenvolupament de {{{name|}}}.
| de = Die Entwicklungs-Repository des {{{name|}}}.
| en = The development repository of the {{{name|}}}.
| es = El Repositorio de desarrollo de {{{name|}}}.
| fr = Le référentiel de développement du {{{name|}}}.
| it = Il repository di sviluppo di {{{name|}}}.
| pl = Repozytorium programistyczne {{{name|}}}.
| th = Repository ที่ใช้พัฒนา {{{name|}}}
}} | link={{#switch: {{{hangar|}}}
| aucafly = {{github url|proj=aucafly|repo={{{aircraft|}}}}}
| bulldogrs = {{github url|proj=aucafly|repo={{{aircraft|}}}}}
| emilianh = {{gitlab url|user=emilianh|repo={{{aircraft|}}}}}
| fgaddon = {{fgaddon aircraft url|{{{aircraft|}}}}}
| herbyw = {{github url|user=HerbyW|repo={{{aircraft|}}}}}
| JMaverick16 = {{github url|user=JMaverick16|repo={{{aircraft|}}}}}
| Octal450 = {{github url|user=Octal450|repo={{{aircraft|}}}}}
}}
]]
}}
}}
| label30 = {{LangSwitch
| ca = Descàrrega
| de = Herunterladen
| en = Download
| es = Descargar
| fr = Télécharger
| it = Download
| ja = ダウンロード
| pl = Pobieranie
| ru = Загрузка
| th = ดาวน์โหลด
| zh = 下载地址
}}
| data30 = {{#if: {{{download|{{{hangar|}}}}}}
| {{#switch: {{{download|{{{hangar|none}}}}}}
| bermuda
| prestes
| none =
| #default = [[File:Folder-downloads 32x32.png | 30px | {{#switch: {{{hangar|fgaddon}}}
| fgaddon = {{LangSwitch
| ca = Descàrrega del paquet d'aeronau {{{name|}}} per la versió actual estable ({{current release|cr}}).
| de = Lade das Flugzeug-Paket des {{{name|}}} für die aktuelle stabile Version ({{current release|cr}}) herunter.
| en = Download the {{{name|}}} aircraft package for the current stable release ({{current release|cr}}).
| es = Descargar el paquete de avion {{{name|}}} para la versión estable actua ({{current release|cr}}).
| fr = Téléchargez le paquet de l'avion {{{name|}}} pour la version stable actuelle ({{current release|cr}}).
| it = Scarica il pacchetto dell'aeromobile {{{name|}}} per la versione stabile corrente ({{current release|cr}}).
| pl = Pobierz pakiet samolotu {{{name|}}} dla aktualnej wersji stabilnej ({{current release|cr}}).
| th = ดาวน์โหลดเครื่องบิน {{{name|}}} สำหรับรุ่นปัจจุบัน({{current release|cr}})
}}
| fgdata = {{LangSwitch
| ca = L'UFO ve com a part del paquet base.
| de = Das UFO ist bereits im Basispaket enthalten.
| en = The UFO comes as part of the base package.
| es = El UFO está incluido en el paquete básico.
| it = L'UFO è parte del pacchetto di base.
| pl = UFO jest częścią pakietu podstawowego.
| th = UFO จะมาพร้อมกับโปรแกรมอยู่แล้ว
}}
| #default = {{LangSwitch
| ca = Descàrrega del paquet de l'aeronau.
| de = de = Lade das Flugzeug-Paket herunter.
| en = Download the aircraft package.
| es = Descargar el paquete de avion.
| fr = Téléchargez le paquet de l'avion.
| it = Scarica il pacchetto dell'aeromobile.
| pl = Pobierz pakiet samolotu.
| th = ดาวน์โหลดเครื่องบิน
}}
}} | link={{#if:{{{download|}}}
| {{{download}}}
| {{#switch: {{{hangar|}}}
| aucafly = {{github zip file|proj=aucafly|repo={{{aircraft|}}}|full=1}}
| buckaroo = http://www.buckarooshangar.com/flightgear/models/{{{aircraft|}}}.zip
| bulldogrs = {{github zip file|proj=aucafly|repo={{{aircraft|}}}|full=1}}
| dave = http://www.daveshangar.org/
| emilianh = {{gitlab zip file|user=emilianh|repo={{{aircraft|}}}|tag=latest|full=1}}
| fgaddon = https://mirrors.ibiblio.org/flightgear/ftp/Aircraft-2024/{{{aircraft|}}}.zip
| fgdata = https://sourceforge.net/projects/flightgear/files/
| fguk = http://fguk.eu/index.php/hangar
| helijah = {{LangSwitch
| en = http://helijah.free.fr/flightgear/hangaren.htm
| fr = http://helijah.free.fr/flightgear/hangar.htm
}}
| herbyw = {{github zip file|user=HerbyW|repo={{{aircraft|}}}|full=1}}
| lake of constance = http://www.marc-kraus.de
| Octal450 = {{github zip file|user=Octal450|repo={{{aircraft|}}}|full=1}}
| paf = http://equipe-flightgear.forumactif.com/t835-hangar-de-la-p-a-f-paf-team-hangar#14330
}}
}}]]
}}
}}
| label31 = {{LangSwitch
| ca = Lliurees
| de = Livree
| en = Liveries
| es = Libreas
| fr = Livrée
| it = Livree
| pl = Malowania
| ru = Ливреи
| th = ลวดลาย
| zh = 涂装
}}
| data31{{#if:{{{liverydbid|}}}||NULL}}
= [[File:Applications-graphics 32x32.png | 30px | {{LangSwitch
| ca = Navegueu per la Base de Dades de Lliurees de FlightGear per al {{{name|}}}.
| de = Durchsuchen Sie die FlightGear Livree Datenbank für die {{{name|}}}.
| en = Browse the FlightGear livery database for the {{{name|}}}.
| es = Navegar por la FlightGear base de datos de libreas para {{{name|}}}.
| fr = Parcourez la base de données de livrée de FlightGear pour le {{{name|}}}.
| it = Sfoglia il database livree di FlightGear per il {{{name|}}}.
| pl = Przejrzyj bazę malowań FlightGear dla {{{name|}}}.
| th = ดูลายสายการบินสำหรับ {{{name|}}}
}} | link=https://liveries.flightgear.org/aircraft.php?id={{{liverydbid|}}}&display=2 ]]
| label32 = {{LangSwitch
| ca = Fòrum
| de = Forum
| en = Forum
| fr = Forum
| it = Forum
| pl = Forum
| ru = Форум
| zh = 论坛
}}
| data32{{#if:{{{forumtid|}}}||NULL}}
= {{forum link
| title = {{{name|}}}
| size = 30px
| t = {{{forumtid}}}
| onlyicon = yes
}}
| label40 = {{LangSwitch
| ca = Llicència
| de = Lizenz
| en = License
| es = Licencia
| fr = Licence
| it = Licenza
| ja = ライセンス
| pl = Licencja
| pt = Licença
| ru = Лицензия
| th = ลิขสิทธิ์
| zh = 授权
}}
| data40 = {{#if:{{{licence|{{{license|}}}}}}
| {{license|{{{licence|{{{license}}}}}}}}
| {{#switch: {{{hangar|}}}
| aucafly = {{license|GPLv3+}}
| bulldogrs = {{license|GPLv3+}}
| dave = {{license|CC BY-NC-SA 4.0}}
| fgaddon = {{license|GPLv2+}}
| herbyw = {{license|GPLv2+}}
| prestes = {{license|Unknown}}
}}
}}
| data41 = {{#if:{{{licence|{{{license|}}}}}}
| {{#switch: {{{license|{{{licence|GPLv2+}}}}}}
| GPL | GPL2 | GPLv2 | GPLv2+ =
| #default =
{{non-GPL2
| width = 100%
| product =
{{#switch: {{{craft|aircraft}}}
| aircraft =
{{LangSwitch
| ca = Aquesta aeronau
| de = Dieses Flugzeug
| en = This aircraft
| es = Este avión
| fr = Cet aéronef
| it = Quest'aeromobile
| pl = Ten samolot
| th = เครื่องบินนี้
}}
| spacecraft =
{{LangSwitch
| ca = Aquest vehicle espacial
| de = Dieses Raumschiff
| en = This spacecraft
| es = Esta nave espacial
| fr = Cet véhicule spatial
| it = Questo veicolo spaziale
| pl = Ten statek kosmiczny
| th = ยานอวกาศนี้
}}
| vehicle =
{{LangSwitch
| ca = Aquest vehicle
| de = Dieses Fahrzeug
| en = This vehicle
| es = Este vehículo
| fr = Cet véhicule
| it = Questo veicolo
| pl = Ten pojazd
| th = รถยนต์นี้
}}
| seacraft =
{{LangSwitch
| ca = Aquesta embarcació
| de = Dieses Wasserfahrzeug
| en = This seacraft
| es = Esta moto acuática
| fr = Cette embarcation
| it = Quest'imbarcazione
| pl = Ten statek morski
| th = ยานพาหนะนี้
}}
}}
| meaning =
{{LangSwitch
| ca = parts no es poden reutilitzar en els repositoris oficials de FlightGear
| de = Teile davon nicht im offiziellen FlightGear-Repositorys wiederverwendet werden dürfen
| en = parts cannot be reused in the official FlightGear repositories
| es = partes no pueden ser reutilizados en los repositorios oficiales de FlightGear
| fr = des parties ne peuvent pas être réutilisées dans les dépôts officiel de FlightGear
| it = delle sue parti non possono essere riutilizzate nei repository ufficiali di FlightGear
| pl = części nie mogą być ponownie użyte w oficjalnych repozytoriach FlightGear
| th = ไม่สามารถนำทั้งหมด หรือส่วนใดส่วนหนึ่ง มาใช้ใน FGAddon ได้
}}
}}
}}
| {{#switch: {{{hangar|}}}
| aucafly
| bulldogrs
| prestes
| dave =
{{non-GPL2
| width = 100%
| product =
{{#switch: {{{craft|aircraft}}}
| aircraft =
{{LangSwitch
| ca = Aquesta aeronau
| de = Dieses Flugzeug
| en = This aircraft
| es = Este avión
| fr = Cet aéronef
| it = Quest'aeromobile
| pl = Ten statek powietrzny
| th = เครื่องบินนี้
}}
| spacecraft =
{{LangSwitch
| ca = Aquest vehicle espacial
| de = Dieses Raumschiff
| en = This spacecraft
| es = Esta nave espacial
| fr = Cet véhicule spatial
| it = Questo veicolo spaziale
| pl = Ten statek kosmiczny
| th = ยานอวกาศนี้
}}
| vehicle =
{{LangSwitch
| ca = Aquest vehicle
| de = Dieses Fahrzeug
| en = This vehicle
| es = Este vehículo
| fr = Cet véhicule
| it = Questo veicolo
| pl = Ten pojazd
| th = รถยนต์นี้
}}
| seacraft =
{{LangSwitch
| ca = Aquesta embarcació
| de = Dieses Wasserfahrzeug
| en = This seacraft
| es = Esta moto acuática
| fr = Cette embarcation
| it = Quest'imbarcazione
| pl = Ten statek morski
| th = ยานพาหนะนี้
}}
}}
| meaning =
{{LangSwitch
| ca = parts no es poden reutilitzar en els repositoris oficials de FlightGear
| de = Teile davon nicht im offiziellen FlightGear-Repositorys wiederverwendet werden dürfen
| en = parts cannot be reused in the official FlightGear repositories
| es = partes no pueden ser reutilizados en los repositorios oficiales de FlightGear
| fr = des parties ne peuvent pas être réutilisées dans les dépôts officiel de FlightGear
| it = delle sue parti non possono essere riutilizzate nei repository ufficiali di FlightGear
| pl = części nie mogą być ponownie użyte w oficjalnych repozytoriach FlightGear
| th = ไม่สามารถนำทั้งหมด หรือส่วนใดส่วนหนึ่ง มาใช้ใน FGAddon ได้
}}
}}
}}
}}
| label42 = {{LangSwitch
| en = Wikipedia
| fr = Wikipédia
| ru = Википедия
| th = วิกิพีเดีย
| zh = 维基百科
}}
| data42 = {{#if: {{{wikipedia|}}}
| {{#if: {{#titleparts:/{{{wikipedia|}}}|1|2}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|2}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|3}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|3}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|4}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|4}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|5}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|5}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|6}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|6}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|7}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|7}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|8}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|8}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|9}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|9}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|10}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|10}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|11}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|11}} }} }}{{#if: {{#titleparts:/{{{wikipedia|}}}|1|12}} | {{wikipedia|{{#titleparts:/{{{wikipedia|}}}|1|12}} }} }}
}}
| data60 = {{#ifeq: {{{navbar|}}}
| 1
| <div style="text-align: right; width: 300px">{{navbar|:{{#titleparts: {{PAGENAME}} | | {{{navbarlevel|-1}}}}}/info|mini=1}}</div>
}}
}}{{#if: {{{image}}} | | [[Category:Image requested]]}}{{#switch: {{{hangar|}}}
| aucafly = [[Category:AUCAFLY hangar]]
| bermuda = [[Category:Bermuda Triangle]]
| buckaroo = [[Category:Buckaroo's hangar]]
| bulldogrs = [[Category:Bulldog RS hangar]]
| dave = [[Category:Dave's hangar]]
| fgaddon = [[Category:FGAddon hangar]]
| fgdata = [[Category:FGData hangar]]
| fguk = [[Category:FGUK hangar]]
| grtux = [[Category:GRTux hangar]]
| helijah = [[Category:Helijah hangar]]
| herbyw = [[Category:HerbyW's hangar]]
| JMaverick16 = [[Category:JMaverick16 hangar]]
| lake of constance = [[Category:Lake of Constance hangar]]
| Octal450 = [[Category:Octal450 hangar]]
| paf = [[Category:PAF hangar]]
| prestes = [[Category:Prestes hangar]]
| #default = [[Category:Unknown hangar]]
}}{{#switch: {{{devel-hangar|}}}
| aucafly = [[Category:AUCAFLY hangar]]
| buckaroo = [[Category:Buckaroo's hangar]]
| bulldogrs = [[Category:Bulldog RS hangar]]
| dave = [[Category:Dave's hangar]]
| fgaddon = [[Category:FGAddon hangar]]
| fgdata = [[Category:FGData hangar]]
| fguk = [[Category:FGUK hangar]]
| grtux = [[Category:GRTux hangar]]
| helijah = [[Category:Helijah hangar]]
| herbyw = [[Category:HerbyW's hangar]]
| lake of constance = [[Category:Lake of Constance hangar]]
| Octal450 = [[Category:Octal450 hangar]]
| paf = [[Category:PAF hangar]]
| prestes = [[Category:Prestes hangar]]
}}{{#switch: {{{craft|aircraft}}}
| aircraft = [[Category:All aircraft]]
| spacecraft = [[Category:All spacecraft]]
| vehicle = [[Category:All vehicles]]
| seacraft = [[Category:All seacraft]]
}}</includeonly><noinclude>
{{Informative template|1=
== Goal ==
This infobox is used to summarize the key points of an aircraft, spacecraft, vehicle, or seacraft. The focus is on FlightGear – the template is not designed to replicate the content of the corresponding Wikipedia article. If a graphic is present – either a hangar logo or screenshot – the infobox will be set to a width of 300 px.

== Usage ==
For instructions on how to use this template in a translation-friendly way, please see the [[#Translations - using subpages]] section below.
{{obr}}'''infobox aircraft'''
{{!}} ''name'' =
{{!}} ''hangar'' =
{{!}} ''aircraft'' =
{{!}} ''image'' =
{{!}} ''alt'' =
{{!}} ''image2'' =
{{!}} ''alt2'' =
<nowiki></nowiki>
{{!}} ''type'' =
{{!}} ''config'' =
{{!}} ''propulsion'' =
{{!}} ''manufacturer'' =
<nowiki></nowiki>
{{!}} ''authors'' =
{{!}} ''author1'' =
...
{{!}} ''author30'' =
{{!}} ''devel-team'' =
{{!}} ''fdm'' =
{{!}} ''fgname'' =
{{!}} ''fgname1'' =
...
{{!}} ''fgname10'' =
<nowiki></nowiki>
{{!}} ''status-fdm'' =
{{!}} ''status-systems'' =
{{!}} ''status-cockpit'' =
{{!}} ''status-model'' =
{{!}} ''status'' =
<nowiki></nowiki>
{{!}} ''ready'' =
{{!}} ''devel-hangar'' =
{{!}} ''devel-website'' =
{{!}} ''devel-repo'' =
{{!}} ''download'' =
{{!}} ''liverydbid'' =
{{!}} ''forumtid'' =
<nowiki></nowiki>
{{!}} ''license'' =
{{!}} ''note'' =
{{!}} ''craft'' =
{{!}} ''wikipedia'' =
{{!}} ''navbar'' =
{{!}} ''navbarlevel'' =
{{cbr}}

All parameters are optional.

=== Basic data ===
{{caution|For multi-part parameters using <code>/</code> separators, these are limited by the constraints of the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23titleparts Mediawiki <code>#titleparts:</code> function]. Therefore a maximum of 25 elements and 255 characters are allowed. Links, URLs, or underscores are not supported, so a number of alternative numbered parameters are provided. If you have other requirements, please discuss this on the [[{{TALKPAGENAME}}|discussion page]].}}

; name: The name of the aircraft. This will be displayed at the top of the infobox.

; hangar: The optional aircraft hangar. This adds the hangar logo at 300 px or text and a link for the hanger, automatically creates development repository and download links for hangars which support this, and adds a hangar specific category to the article. This can currently be one of {{param||fgaddon}}, {{param||buckaroo}}, {{param||fguk}}, {{param|helijah}}, {{param|herbyw}}, {{param|lake of constance}}, {{param|paf}}.

; aircraft: The name of the aircraft in the hangar. This is only used if the {{param|hangar}} parameter is supplied. For [[FGAddon]], this corresponds to the aircraft directory in <code>[[$FG_AIRCRAFT]]/Aircraft/<aircraft-dir></code>. For other hangars, this is currently unused.

; image: Screenshot of the aircraft without the <code>File:</code> or <code>Image:</code> prefix. The graphic will be set to a width of 300 px.

; alt: Caption for the screenshot.

; image2: Additional screenshot without the <code>File:</code> or <code>Image:</code> prefix (''preferably a cockpit screenshot''). The graphic will be set to a width of 300 px.

; alt2: Caption for the second screenshot.

; type: The type of aircraft, spacecraft, vehicle, or seacraft. Although this can be any text, special parameter values, independent of capitalisation, will be associated with a category. This will result in the automatic addition of a internal wiki link to the category in the infobox as well as appending the category to the article. See the [[#Craft types|Craft types]] section below for a table of values. Multiple values for the parameter can be supplied when each type is separated by <code>/</code>. For example <code>{{!}} type = Civil utility aircraft/Military utility aircraft</code>.

; config: The configuration of the aircraft, spacecraft, vehicle, or seacraft. Although this can be any text, special parameter values, independent of capitalisation, will be associated with a category. This will result in the automatic addition of a internal wiki link to the category in the infobox as well as appending the category to the article. See the [[#Craft configurations|Craft configurations]] section below for a table of values. Multiple values for the parameter can be supplied when each configuration is separated by <code>/</code>. For example <code>{{!}} config = Biplane aircraft/Delta-wing aircraft</code>.

; propulsion: The aircraft, spacecraft, vehicle, or seacraft propulsion. Although this can be any text, special parameter values, independent of capitalisation, will be associated with a category. This will result in the automatic addition of a internal wiki link to the category in the infobox as well as appending the category to the article. See the [[#Craft propulsion|Craft propulsion]] section below for a table of values. Multiple values for the parameter can be supplied when each value is separated by <code>/</code>. For example <code>{{!}} propulsion = Twin-engined aircraft/Propeller aircraft</code>.

; manufacturer: The aircraft, spacecraft, vehicle, or seacraft manufacturer. Although this can be any text, special parameter values, independent of capitalisation, will be associated with a category. This will result in the automatic addition of a internal wiki link to the category in the infobox as well as appending the category to the article. See the [[#Craft manufacturer|Craft manufacturer]] section below for a table of values. Multiple values for the parameter can be supplied when each value is separated by <code>/</code>. For example <code>{{!}} manufacturer = Boeing/Rockwell</code>.

; authors: The list of aircraft authors. The special slash character <code>/</code> can be used to separate authors, for example: <code>{{!}} fgname = me/you</code>, resulting in each author being placed on a separate line. The <code>/</code> character cannot be used within a single author element so instead the <code>,</code> or <code>&</code> separating characters should be used.

; author{1-30}: Optional aircraft authors to add to the list. These should be given in order from {{param|author1}} upwards. This bypasses the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23titleparts Mediawiki <code>#titleparts:</code> function], allowing for the author name to be a link.

; devel-team: The optional name of the development team. If this parameter is supplied, then the author list will be packed into a collapsible element that is, by default, not shown but has a <code>[Expand]</code> link to see the authors.

; fdm: The [[Flight Dynamics Model]] of the aircraft. If one of the values of {{param|JSBSim}}, {{param|YASim}}, {{param|UIUC}}, or {{param|LaRCsim}} are supplied, independent of capitalisation, then an automatic link to the corresponding wiki page will be created. Multiple values for the parameter can be supplied when each type is separated by <code>/</code>, for example <code>{{!}} type = UIUC/YASim/JSBSim/magic carpet</code>.

; fgname: The name(s) of the aircraft to use when launching FlightGear from the command line. If multiple aircraft in different <code>*-set.xml</code> files are available, each name should be separated by the slash character <code>/</code>. For example <code>{{!}} fgname = dhc6/dhc6F/dhc6S</code>

; fgname{1-10}: An alternative way to specify the fgname, if the [https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions#.23titleparts Mediawiki <code>#titleparts:</code> function] is problematic. This is necessary if there are underscores in the name.

; status-fdm: The [[Aircraft rating system#Flight Dynamics Model .28FDM.29|status of the Flight Dynamics Model]]. For details, please [[#Aircraft status|see below]].

; status-systems: The [[Aircraft rating system#Systems|status of the systems]] For details, please [[#Aircraft status|see below]].

; status-cockpit: The [[Aircraft rating system#Cockpit|status of the cockpit]] For details, please [[#Aircraft status|see below]].

; status-model: The [[Aircraft rating system#External Model|status of the external model]] For details, please [[#Aircraft status|see below]].

; status: The fall-back status text, if none of the other {{param|status-*}} parameters are set. This corresponds to the old [[Aircraft rating system]].

; ready: Add icons to display certain capabilities supported by the aircraft. Please see the [[#Ready icons]] section below for details.

; devel-hangar: The hangar where aircraft developments occur. This is similar to the {{param|hangar}} parameter, and will add the hangar banner to the infobox. The aim is to point readers to the hangar responsible for the current developments, so as to minimise duplicated developments.

; devel-website: The URL for the development website.

; devel-repo: The URL for the development repository. If the {{param|hangar}} parameter is supplied, the development link may be automatically created. Note that hardcoded URLs should be avoided where ever possible and the [[:Category:Repository link templates|family of repository link templates]] should be used instead.

; development: Depreciated. This has been replaced by the {{param|devel-repo}} parameter.

; download: The URL for downloading the aircraft. If the {{param|hangar}} parameter is supplied, the download link may be automatically created. For repository snapshots, please avoid hardcoded URLs and instead use the [[:Category:Repository link templates|family of repository link templates]].

; liverydbid: The [[FlightGear livery database|livery database]] ID of the aircraft.

; forumtid: The {{forum link|text=FlightGear forum}} topic ID for the aircraft. This is the number after the <code>t=</code> part of the URL.

; license: Also {{param|licence}}. This will add licensing information to the infobox. Please see the [[#Licensing]] section below for a list of special values.

; note: A special note to show within a {{tl|note}} message box at the end of the aircraft infobox.

; craft: The craft type, defaulting to {{param||aircraft}}. This can be one of {{param||aircraft}}, {{param||spacecraft}}, {{param||vehicle}}, or {{param||seacraft}}. This will be used to add one of the categories [[:Category:All aircraft]], [[:Category:All spacecraft]], [[:Category:All vehicles]], or [[:Category:All seacraft]] to the page.

; wikipedia: The Wikipedia article corresponding to the craft. This is implemented via the {{tl|wikipedia}} template. If there are separate Wikipedia articles for variants included with the aircraft, the Wikipedia articles can be separated with a slash <code>/</code>. This will likely not work if Wikipedia article titles contain slashes.

; navbar: If this is set to {{param||1}}, a {{tl|navbar}} element will be added to the very end of infobox. This is very useful when using [[#Translations - using subpages|subpages]]. It will have the form of <code>{{navbar|{{PAGENAME}}|mini=1}}</code>. Note that the navbar will point to pages of the form <code>{{obr}}PAGENAME{{cbr}}/info</code>, excluding the language code part of the page name.

; navbarlevel: This is used if the {{param|navbar}} parameter is set. It allows for <code>/</code> characters in the base PAGENAME. If a single slash is present, then this should be set to {{param||-2}}.

; float: A parameter reserved solely for template developers. This corresponds to the {{tl|Infobox}} {{param|float}} parameter.

{{craft type/doc}}

{{craft configuration/doc}}

{{craft propulsion/doc}}

{{craft manufacturer/doc}}

=== Aircraft status ===
Instead of a custom {{param|status}} text, you can use the [[aircraft rating system]]. The overall status is auto-calculated and will be displayed. If you use the aircraft rating system, the {{param|status}} parameter will be ignored.

See [[Aircraft rating system]] for instructions on how to rate your aircraft.

=== Ready icons ===
Several icons are available for highlighting certain capabilities of the aircraft. Separate them with the slash character <code>/</code>, for example <code>{{!}} ready = airrefuel/bombable</code>. The allowed values are:

{{ready/doc table}}

This is implemented using the {{tl|ready}} template.

=== Translations - using subpages ===
When using this template in an article, the use of subpage organisation is recommended for facilitating translations.

==== Transclusion of the subpage ====

Instead of transcluding this template directly into the article, the subpage <code>{{obr}}{{mediawiki|Help:Magic_words#Page_names|PAGENAME}}{{cbr}}/info</code> can be created. Using the example of the [[de Havilland Canada DHC-6 Twin Otter]], to the very start of the article simply add:

{{obr}}:{{obr}}{{mediawiki|Help:Magic_words#Page_names|PAGENAME}}{{cbr}}/info{{cbr}}

For translations, e.g. [[De/de Havilland Canada DHC-6 Twin Otter]] and [[Fr/de Havilland Canada DHC-6 Twin Otter]], a different syntax is needed to strip out the language prefix from the page name. The text to copy and paste to the top of the article is:

{{obr}}:{{obr}}#{{mediawiki|Help:Extension:ParserFunctions##titleparts|titleparts}}:{{obr}}PAGENAME{{cbr}}{{!}}{{!}}2{{cbr}}/info{{cbr}}

==== Subpage structure ====

Then create your <code>{{obr}}PAGENAME{{cbr}}/info</code> multi-language page with, for the example of [[de Havilland Canada DHC-6 Twin Otter/info]] (also see the [[#de Havilland Canada DHC-6 Twin Otter|DHC-6 example]] below):

<includeonly>{{obr}}infobox aircraft
{{!}} name = de Havilland Canada DHC-6 Twin Otter
{{!}} hangar = fgaddon
{{!}} aircraft = dhc6
{{!}} image = Dhc6-splash1.jpg
{{!}} alt = {{obr}}LangSwitch
{{!}} de = Die DHC-6 Twin Otter im Flug
{{!}} en = The DHC-6 Twin Otter in flight
{{!}} fr = Le DHC-6 Twin Otter en vol
{{cbr}}
{{!}} image2 = Twin Otter - interior shadows.jpg
{{!}} alt2 = {{obr}}LangSwitch
{{!}} de = Cockpit des Twin Otter mit Innenbeschattung
{{!}} en = Cockpit of the Twin Otter with interior shading
{{!}} fr = Cockpit du Twin Otter avec un ombrage intérieur
{{cbr}}
{{!}} type = Civil utility aircraft/Military utility aircraft/Seaplanes and flying boat
{{!}} config = High wing aircraft/Fixed gear aircraft/Tricycle landing gear aircraft
{{!}} propulsion = Twin-engine aircraft/Propeller aircraft
{{!}} manufacturer = de Havilland Canada
{{!}} authors = Syd Adams (Initial model)/Christian Thiriot (3D, Textures)/Bo Lan (Nasal, FDM, Systems)/Jonathan Schellhase (3D, Nasal, Systems, Sound, misc)/others (see below)
{{!}} devel-team = {{obr}}LangSwitch
{{!}} de = DHC-6 Twin Otter Entwicklungsteam
{{!}} en = DHC-6 Twin Otter team
{{!}} fr = L'équipe du DHC-6 Twin Otter
{{cbr}}
{{!}} fdm = YASim
{{!}} fgname = dhc6/dhc6F/dhc6S
{{!}} status-fdm = 4
{{!}} status-systems = 4
{{!}} status-cockpit = 5
{{!}} status-model = 5
{{!}} ready = checklist/tutorials/rembrandt
{{!}} liverydbid = 57
{{!}} forumtid = 21965
{{!}} navbar = 1
{{cbr}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[[[de Havilland Canada DHC-6 Twin Otter]]]].
[[[[:Category:Aircraft infobox documentation]]]]
</noinclude>

The <code><includeonly></code> tags prevent the <code>{{obr}}PAGENAME{{cbr}}/info</code> pages from being scattered throughout the [[:Category:Controllable craft]] subcategories (by temporarily removing or deleting a character in the initial tag, the infobox can be previewed). The <code><noinclude></code> tags means that only the <code>{{obr}}PAGENAME{{cbr}}/info</code> page will be added to the [[:Category:Aircraft infobox documentation]] category.

Note the use of the {{param|navbar}} parameter. This is allows the <code>{{obr}}PAGENAME{{cbr}}/info</code> subpage to be easily accessed from the main article.

==== Full translation ====

For a full translation of the aircraft infobox, a number of templates on top of this one need to be translated:

* <div class="plainlinks">[{{fullurl:Template:{{PAGENAME}}|action=edit}} Edit this template]<div>
* <div class="plainlinks">[{{fullurl:Template:Craft type|action=edit}} Edit Template:Craft_type]</div>
* <div class="plainlinks">[{{fullurl:Template:Craft configuration|action=edit}} Edit Template:Craft_configuration]</div>
* <div class="plainlinks">[{{fullurl:Template:Craft propulsion|action=edit}} Edit Template:Craft_propulsion]</div>
* <div class="plainlinks">[{{fullurl:Template:Craft manufacturer|action=edit}} Edit Template:Craft_manufacturer]</div>
* <div class="plainlinks">[{{fullurl:Template:hangar banner|action=edit}} Edit Template:Hangar_banner]</div>

=== Licensing ===

If the {{param|license}} or {{param|licence}} parameter has one of the special values listed in the following table, a link to the licensing information will be automatically created.

{{license/doc table}}

This is implemented via the {{tl|license}} template.

== Examples ==

Apart from the examples below, see the [[Special:WhatLinksHere/Template:infobox aircraft|articles using this template]] to learn how to use it.

=== Empty template ===

{{obr}}Infobox aircraft{{cbr}}

{{infobox aircraft|float=none}}

=== Base package aircraft ===

==== Cessna 172P Skyhawk ====
This is an example for the [[Cessna 172P]] article, specifically in the [[Cessna 172P/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Cessna 172P Skyhawk
{{!}} hangar = fgdata
{{!}} image = c172p-thumbnail.jpg
{{!}} type = Civil aircraft/Civil utility aircraft
{{!}} config = High wing aircraft/Fixed gear aircraft
{{!}} propulsion = Propeller aircraft/Single-engine aircraft
{{!}} manufacturer = Cessna
{{!}} authors = David Megginson/Gilberto Agostinho/Wayne Bragg/Juan Vera del Campo/onox/Fernando Barbosa/Daniel Dubreuil/Jonathan Schellhase/Israel Hernandez/Tuomas Kuosmanen/Anders Gidenstam/Waldo Kitty/algefaen
{{!}} devel-team = C172P development team
{{!}} fdm = JSBSim
{{!}} fgname = c172p
{{!}} status-fdm = 4
{{!}} status-systems = 5
{{!}} status-cockpit = 5
{{!}} status-model = 4
{{!}} ready = dualcontrol/tutorials/checklist
{{!}} devel-repo = {{obr}}github url{{!}}user=Juanvvc{{!}}repo=c172p-detailed{{cbr}}
{{!}} download = {{obr}}github zip file{{!}}user=Juanvvc{{!}}repo=c172p-detailed{{!}}full=1{{cbr}}
{{!}} liverydbid = 70
{{!}} forumtid = 25157
{{!}} note = This is the default FlightGear aircraft and is distributed as part of the base package.
{{!}} wikipedia = Cessna 172
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Cessna 172P Skyhawk
| hangar = fgdata
| image = c172p-thumbnail.jpg
| type = Civil aircraft/Civil utility aircraft
| config = High wing aircraft/Fixed gear aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Cessna
| authors = David Megginson/Gilberto Agostinho/Wayne Bragg/Juan Vera del Campo/onox/Fernando Barbosa/Daniel Dubreuil/Jonathan Schellhase/Israel Hernandez/Tuomas Kuosmanen/Anders Gidenstam/Waldo Kitty/algefaen
| devel-team = C172P development team
| fdm = JSBSim
| fgname = c172p
| status-fdm = 4
| status-systems = 5
| status-cockpit = 5
| status-model = 4
| ready = dualcontrol/tutorials/checklist
| devel-repo = {{github url|user=Juanvvc|repo=c172p-detailed}}
| download = {{github zip file|user=Juanvvc|repo=c172p-detailed|full=1}}
| liverydbid = 70
| forumtid = 25157
| note = This is the default FlightGear aircraft and is distributed as part of the base package.
| wikipedia = Cessna 172
| navbar = 1
| float = none
}}

=== Official FGAddon hangar ===

==== Space Shuttle ====
This is an example for the [[Space Shuttle]] article, specifically in the [[Space Shuttle/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Space Shuttle
{{!}} hangar = fgaddon
{{!}} aircraft = SpaceShuttle
{{!}} image = Shuttle FG01.jpg
{{!}} alt = Space Shuttle <nowiki>''Atlantis''</nowiki> in orbit
{{!}} image2 = Shuttle_Cockpit.jpg
{{!}} alt2 = Space Shuttle cockpit (April 2015)
{{!}} type = Spaceplane/Glider aircraft/Hypersonic aircraft
{{!}} config = Delta-wing aircraft
{{!}} authors = Thorsten Renk (flight dynamics)/Richard Harrison (cockpit and avionics)/Chris Kuhn (cockpit)/NASA/japreja (3D)/HerbyW (3D)
{{!}} devel-team = Shuttle development team
{{!}} fdm = JSBSim
{{!}} fgname = SpaceShuttle/SpaceShuttle-orbit/SpaceShuttle-launch/SpaceShuttle-entry/SpaceShuttle-approach/SpaceShuttle-TAEM
{{!}} status-fdm = 4
{{!}} status-systems = 4
{{!}} status-cockpit = 2
{{!}} status-model = 3
{{!}} devel-website = https://sourceforge.net/projects/fgspaceshuttledev/
{{!}} devel-repo = {{obr}}[[Template:sourceforge url|sourceforge url]]{{!}}proj=fgspaceshuttledev{{!}}repo=code{{!}}branch=development{{cbr}}
{{!}} forumtid = 25747
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Space Shuttle
| hangar = fgaddon
| aircraft = SpaceShuttle
| image = Shuttle FG01.jpg
| alt = Space Shuttle ''Atlantis'' in orbit
| image2 = Shuttle_Cockpit.jpg
| alt2 = Space Shuttle cockpit (April 2015)
| type = Spaceplane/Glider aircraft/Hypersonic aircraft
| config = Delta-wing aircraft
| authors = Thorsten Renk (flight dynamics)/Richard Harrison (cockpit and avionics)/Chris Kuhn (cockpit)/NASA/japreja (3D)/HerbyW (3D)
| devel-team = Shuttle development team
| fdm = JSBSim
| fgname = SpaceShuttle/SpaceShuttle-orbit/SpaceShuttle-launch/SpaceShuttle-entry/SpaceShuttle-approach/SpaceShuttle-TAEM
| status-fdm = 4
| status-systems = 4
| status-cockpit = 2
| status-model = 3
| devel-website = https://sourceforge.net/projects/fgspaceshuttledev/
| devel-repo = {{sourceforge url|proj=fgspaceshuttledev|repo=code|branch=development}}
| forumtid = 25747
| navbar = 1
| float = none
}}

==== de Havilland Canada DHC-6 Twin Otter ====
This is an example for the [[de Havilland Canada DHC-6 Twin Otter]] article, specifically in the [[de Havilland Canada DHC-6 Twin Otter/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = de Havilland Canada DHC-6 Twin Otter
{{!}} hangar = fgaddon
{{!}} aircraft = dhc6
{{!}} image = Dhc6-splash1.jpg
{{!}} alt = {{obr}}LangSwitch
{{!}} de = Die DHC-6 Twin Otter im Flug
{{!}} en = The DHC-6 Twin Otter in flight
{{!}} fr = Le DHC-6 Twin Otter en vol
{{cbr}}
{{!}} image2 = Twin Otter - interior shadows.jpg
{{!}} alt2 = {{obr}}LangSwitch
{{!}} de = Cockpit des Twin Otter mit Innenbeschattung
{{!}} en = Cockpit of the Twin Otter with interior shading
{{!}} fr = Cockpit du Twin Otter avec un ombrage intérieur
{{cbr}}
{{!}} type = Civil utility aircraft/Military utility aircraft/Seaplanes and flying boat
{{!}} config = High wing aircraft/Monoplane aircraft/Fixed gear aircraft/Tricycle landing gear aircraft
{{!}} propulsion = Twin-engine aircraft/Propeller aircraft
{{!}} manufacturer = de Havilland Canada
{{!}} authors = Syd Adams (Initial model)/Christian Thiriot (3D, Textures)/Bo Lan (Nasal, FDM, Systems)/Jonathan Schellhase (3D, Nasal, Systems, Sound, misc)/others (see below)
{{!}} devel-team = {{obr}}LangSwitch
{{!}} de = DHC-6 Twin Otter Entwicklungsteam
{{!}} en = DHC-6 Twin Otter team
{{!}} fr = L'équipe du DHC-6 Twin Otter
{{cbr}}
{{!}} fdm = YASim
{{!}} fgname = dhc6/dhc6F/dhc6S
{{!}} status-fdm = 4
{{!}} status-systems = 4
{{!}} status-cockpit = 5
{{!}} status-model = 5
{{!}} ready = checklist/tutorials/rembrandt
{{!}} liverydbid = 57
{{!}} forumtid = 21965
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = de Havilland Canada DHC-6 Twin Otter
| hangar = fgaddon
| aircraft = dhc6
| image = Dhc6-splash1.jpg
| alt = {{LangSwitch
| de = Die DHC-6 Twin Otter im Flug
| en = The DHC-6 Twin Otter in flight
| fr = Le DHC-6 Twin Otter en vol
}}
| image2 = Twin Otter - interior shadows.jpg
| alt2 = {{LangSwitch
| de = Cockpit des Twin Otter mit Innenbeschattung
| en = Cockpit of the Twin Otter with interior shading
| fr = Cockpit du Twin Otter avec un ombrage intérieur
}}
| type = Civil utility aircraft/Military utility aircraft/Seaplanes and flying boat
| config = High wing aircraft/Monoplane aircraft/Fixed gear aircraft/Tricycle landing gear aircraft
| propulsion = Twin-engine aircraft/Propeller aircraft
| manufacturer = de Havilland Canada
| authors = Syd Adams (Initial model)/Christian Thiriot (3D, Textures)/Bo Lan (Nasal, FDM, Systems)/Jonathan Schellhase (3D, Nasal, Systems, Sound, misc)/others (see below)
| devel-team = {{LangSwitch
| de = DHC-6 Twin Otter Entwicklungsteam
| en = DHC-6 Twin Otter team
| fr = L'équipe du DHC-6 Twin Otter
}}
| fdm = YASim
| fgname = dhc6/dhc6F/dhc6S
| status-fdm = 4
| status-systems = 4
| status-cockpit = 5
| status-model = 5
| ready = checklist/tutorials/rembrandt
| liverydbid = 57
| forumtid = 21965
| navbar = 1
| float = none
}}

==== Piper Seneca II ====
This is an example for the [[Piper PA34-200T Seneca II]] article, specifically in the [[Piper PA34-200T Seneca II/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Piper PA34-200T Seneca II
{{!}} hangar = fgaddon
{{!}} aircraft = SenecaII
{{!}} image = Piper_SenecaII.jpg
{{!}} type = Civil aircraft/Civil utility aircraft
{{!}} propulsion = Twin-engine aircraft
{{!}} manufacturer = Piper
{{!}} authors = Torsten Dreyer
{{!}} fdm = JSBSim
{{!}} fgname = SenecaII
{{!}} status-fdm = 5
{{!}} status-systems = 5
{{!}} status-cockpit = 4
{{!}} status-model = 3
{{!}} ready = tutorials
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Piper PA34-200T Seneca II
| hangar = fgaddon
| aircraft = SenecaII
| image = Piper_SenecaII.jpg
| type = Civil aircraft/Civil utility aircraft
| propulsion = Twin-engine aircraft
| manufacturer = Piper
| authors = Torsten Dreyer
| fdm = JSBSim
| fgname = SenecaII
| status-fdm = 5
| status-systems = 5
| status-cockpit = 4
| status-model = 3
| ready = tutorials
| navbar = 1
| float = none
}}

==== Follow me ====
This is an example for the [[Follow me]] article, specifically in the [[Follow me/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Follow me
{{!}} hangar = fgaddon
{{!}} aircraft = followme
{{!}} image = Follow_me.jpg
{{!}} type = Automobile/Utility vehicle
{{!}} authors = Gijs de Rooy
{{!}} fdm = JSBSim
{{!}} fgname = followme
{{!}} status-fdm = 4
{{!}} status-systems = 2
{{!}} status-cockpit = 3
{{!}} status-model = 4
{{!}} forumtid = 858
{{!}} craft = vehicle
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Follow me
| hangar = fgaddon
| aircraft = followme
| image = Follow_me.jpg
| type = Automobile/Utility vehicle
| authors = Gijs de Rooy
| fdm = JSBSim
| fgname = followme
| status-fdm = 4
| status-systems = 2
| status-cockpit = 3
| status-model = 4
| craft = vehicle
| forumtid = 858
| navbar = 1
| float = none
}}

==== Wright Flyer ====
This is an example for the [[Wright Flyer]] article, specifically in the [[Wright Flyer/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Wright Flyer
{{!}} hangar = fgaddon
{{!}} aircraft = wrightFlyer1903
{{!}} image = 1903 Wright Flyer.jpg
{{!}} alt = The ''Wright Flyer'' on the ground.
{{!}} type = First airplane/Experimental aircraft
{{!}} config = Biplane aircraft/Canard aircraft
{{!}} propulsion = Propeller aircraft
{{!}} manufacturer = Wright brothers
{{!}} authors = Jim Wilson (3D model)
{{!}} author1 = Prof. <nowiki>[http://www.ae.illinois.edu/directory/profile/m-selig Michael Selig]</nowiki> (UIUC FDM)
{{!}} author2 = Erik Hofman (JSBSim FDM)
{{!}} fdm = UIUC/JSBSim
{{!}} fgname = wrightFlyer1903/wrightFlyer1903-jsbsim
{{!}} status = Production
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Wright Flyer
| hangar = fgaddon
| aircraft = wrightFlyer1903
| image = 1903 Wright Flyer.jpg
| alt = The ''Wright Flyer'' on the ground.
| type = First airplane/Experimental aircraft
| config = Biplane aircraft/Canard aircraft
| propulsion = Propeller aircraft
| manufacturer = Wright brothers
| authors = Jim Wilson (3D model)
| author1 = Prof. [http://www.ae.illinois.edu/directory/profile/m-selig Michael Selig] (UIUC FDM)
| author2 = Erik Hofman (JSBSim FDM)
| fdm = UIUC/JSBSim
| fgname = wrightFlyer1903/wrightFlyer1903-jsbsim
| status = Production
| navbar = 1
| float = none
}}

==== Farman IV ====
This is an example for the [[Farman IV]] article, specifically in the [[Farman IV/info]] subpage.
{{obr}}infobox aircraft
{{!}} name = Farman IV
{{!}} hangar = fgaddon
{{!}} aircraft = Farman-IV
{{!}} image = Farman-IV.jpg
{{!}} type = Historical aircraft/Military aircraft
{{!}} config = Biplane aircraft
{{!}} propulsion = Propeller aircraft/Twin-engine piston aircraft
{{!}} manufacturer = Farman
{{!}} authors = Emmanuel Baranger (3D, FDM)
{{!}} fdm = YASim
{{!}} fgname = farman-IV
{{!}} status-fdm = 2
{{!}} status-systems = 1
{{!}} status-cockpit = 1
{{!}} status-model = 4
{{!}} devel-hangar = helijah
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Farman IV
| hangar = fgaddon
| aircraft = Farman-IV
| image = Farman-IV.jpg
| type = Historical aircraft/Military aircraft
| config = Biplane aircraft
| propulsion = Propeller aircraft/Twin-engine piston aircraft
| manufacturer = Farman
| authors = Emmanuel Baranger (3D, FDM)
| fdm = YASim
| fgname = farman-IV
| status-fdm = 2
| status-systems = 1
| status-cockpit = 1
| status-model = 4
| devel-hangar = helijah
| navbar = 1
| float = none
}}

==== Boeing-Sikorsky RAH-66 Comanche ====
This is an example for the [[Boeing-Sikorsky RAH-66 Comanche]] article, specifically in the [[Boeing-Sikorsky RAH-66 Comanche/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Boeing-Sikorsky RAH-66 Comanche
{{!}} hangar = fgaddon
{{!}} aircraft = rah-66
{{!}} image = RAH-66 splash.png
{{!}} image2 = rah-66-cockpit.png
{{!}} type = Helicopter/Military helicopter/Military reconnaissance aircraft/Attack aircraft
{{!}} manufacturer = Boeing/Sikorsky
{{!}} author1 = {{obr}}[[Template:usr|usr]]{{!}}pjedvaj{{!}}Petar Jedvaj{{cbr}}
{{!}} author2 = Edin Hozic
{{!}} author3 = Stephen Madeira
{{!}} author4 = Gary Brown
{{!}} fdm = YASim
{{!}} fgname = rah-66
{{!}} status-fdm = 4
{{!}} status-systems = 2
{{!}} status-cockpit = 3
{{!}} status-model = 5
{{!}} forumtid = 14908
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Boeing-Sikorsky RAH-66 Comanche
| hangar = fgaddon
| aircraft = rah-66
| image = RAH-66 splash.png
| image2 = rah-66-cockpit.png
| type = Helicopter/Military helicopter/Military reconnaissance aircraft/Attack aircraft
| manufacturer = Boeing/Sikorsky
| author1 = {{usr|pjedvaj|Petar Jedvaj}}
| author2 = Edin Hozic
| author3 = Stephen Madeira
| author4 = Gary Brown
| fdm = YASim
| fgname = rah-66
| status-fdm = 4
| status-systems = 2
| status-cockpit = 3
| status-model = 5
| forumtid = 14908
| navbar = 1
| float = none
}}

=== Aucafly hangar ===

==== Aucafly T1 ====
This is an example for the [[Aucafly T1]] article.

{{obr}}infobox aircraft
{{!}} name = Aucafly T1
{{!}} hangar = aucafly
{{!}} aircraft = AUCAFLYT1
{{!}} image = Aucafly T1.png
{{!}} alt = Aucafly T1 leaving San Francisco International Airport
{{!}} type = Civil aircraft/Fictional aircraft
{{!}} propulsion = Propeller aircraft
{{!}} manufacturer = Aucafly
{{!}} authors = Ausdkunst/D-Echo (FDM)
{{!}} fdm = YASim
{{!}} fgname = aucaflyt1
{{!}} status-fdm = 0
{{!}} status-systems = 2
{{!}} status-cockpit = 2
{{!}} status-model = 2
{{!}} devel-website = https://aucafly.wordpress.com/2016/06/07/t1-world-premiere/
{{!}} craft = vehicle
{{cbr}}

{{infobox aircraft
| name = Aucafly T1
| hangar = aucafly
| aircraft = AUCAFLYT1
| image = Aucafly T1.png
| alt = Aucafly T1 leaving San Francisco International Airport
| type = Civil aircraft/Fictional aircraft
| propulsion = Propeller aircraft
| manufacturer = Aucafly
| authors = Ausdkunst/D-Echo (FDM)
| fdm = YASim
| fgname = aucaflyt1
| status-fdm = 0
| status-systems = 2
| status-cockpit = 2
| status-model = 2
| devel-website = https://aucafly.wordpress.com/2016/06/07/t1-world-premiere/
| craft = vehicle
| float = none
}}

=== Buckaroo's hangar ===

==== Velocity XL RG ====
This is an example for the [[Velocity XL RG]] article, specifically in the [[Velocity XL RG/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Velocity XL RG
{{!}} hangar = buckaroo
{{!}} aircraft = Velocity_XL_RG
{{!}} image = Velocity-XL-RG.jpg
{{!}} alt = Velocity XL RG in flight
{{!}} image2 = Velocity-XL-RG cabin 01.jpg
{{!}} alt2 = Velocity XL RG cabin
{{!}} type = Civil aircraft/Civil utility aircraft
{{!}} config = Canard aircraft/Pusher aircraft
{{!}} propulsion = Propeller aircraft/Single-engine aircraft
{{!}} manufacturer = Velocity
{{!}} authors = Gary Neely
{{!}} fdm = YASim
{{!}} fgname = Velocity-XL-RG
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Velocity XL RG
| hangar = buckaroo
| aircraft = Velocity_XL_RG
| image = Velocity-XL-RG.jpg
| alt = Velocity XL RG in flight
| image2 = Velocity-XL-RG cabin 01.jpg
| alt2 = Velocity XL RG cabin
| type = Civil aircraft/Civil utility aircraft
| config = Canard aircraft/Pusher aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Velocity
| authors = Gary Neely
| fdm = YASim
| fgname = Velocity-XL-RG
| navbar = 1
| float = none
}}

=== Dave's hangar ===

==== McDonnell F-4 Phantom II ====
This is an example for the [[McDonnell F-4 Phantom II]] article, specifically in the [[McDonnell F-4 Phantom II/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = McDonnell Douglas F-4 Phantom II
{{!}} hangar = dave
{{!}} image = F4N.JPG
{{!}} type = Military aircraft/Interceptor aircraft/Fighter aircraft/Bomber aircraft
{{!}} manufacturer = McDonnell/McDonnell Douglas
{{!}} authors = Dave Culp
{{!}} fdm = JSBSim
{{!}} fgname = F-4N
{{!}} download = http://www.daveshangar.org/aircraft/F-4N.tar.gz
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = McDonnell Douglas F-4 Phantom II
| hangar = dave
| image = F4N.JPG
| type = Military aircraft/Interceptor aircraft/Fighter aircraft/Bomber aircraft
| manufacturer = McDonnell/McDonnell Douglas
| authors = Dave Culp
| fdm = JSBSim
| fgname = F-4N
| download = http://www.daveshangar.org/aircraft/F-4N.tar.gz
| navbar = 1
| float = none
}}

=== Emilian H's hangar ===

==== IAR 80 ====
This is an example for the [[IAR 80]] article, specifically in the [[IAR 80/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = IAR 80
{{!}} hangar = emilianh
{{!}} aircraft = IAR80
{{!}} image = Iar80-flight.jpg
{{!}} alt = The IAR 80 in its the default livery.
{{!}} image2 = Iar80-cockpit-dusk.jpg
{{!}} alt2 = The IAR 80's cockpit as dusk
{{!}} type = Fighter aircraft
{{!}} config = Low wing aircraft
{{!}} propulsion = Propeller aircraft/Single-engine aircraft
{{!}} manufacturer = Industria Aeronautică Română (IAR)
{{!}} authors = Emilian Huminiuc (3D model, textures, YASim FDM)/Ron Jensen (JSBSim FDM)
{{!}} fdm = YASim/JSBSim
{{!}} fgname = IAR80-YASim
{{!}} status-fdm = 5
{{!}} status-systems = 4
{{!}} status-cockpit = 5
{{!}} status-model = 5
{{!}} license = CC-BY-NC-ND 4.0/GPLv2
{{!}} note = The JSBSim FDM is in beta
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = IAR 80
| hangar = emilianh
| aircraft = IAR80
| image = Iar80-flight.jpg
| alt = The IAR 80 in its the default livery.
| image2 = Iar80-cockpit-dusk.jpg
| alt2 = The IAR 80's cockpit as dusk
| type = Fighter aircraft
| config = Low wing aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Industria Aeronautică Română (IAR)
| authors = Emilian Huminiuc (3D model, textures, YASim FDM)/Ron Jensen (JSBSim FDM)
| fdm = YASim/JSBSim
| fgname = IAR80-YASim
| status-fdm = 5
| status-systems = 4
| status-cockpit = 5
| status-model = 5
| license = CC-BY-NC-ND 4.0/GPLv2
| note = The JSBSim FDM is in beta
| navbar = 1
| float = none
}}

=== HerbyW's hangar ===

==== Space Shuttle (FG Space Program) ====
This is an example for the [[Space Shuttle (FG Space Program)]] article, specifically in the [[Space Shuttle (FG Space Program)/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Shuttle
{{!}} hangar = herbyw
{{!}} aircraft = shuttle
{{!}} image = Atlantis.png
{{!}} alt = Shuttle ''Atlantis''
{{!}} type = Spaceplane
{{!}} config = Delta-wing aircraft
{{!}} authors = HerbyW (FDM)/Firefly (3D)/Original Project Jon S. Berndt
{{!}} fdm = JSBSim
{{!}} fgname = shuttle/shuttle-Atlantis/shuttle-Columbia/shuttle-Launcher
{{!}} status-fdm = 2
{{!}} status-systems = 1
{{!}} status-cockpit = 0
{{!}} status-model = 3
{{!}} ready = rembrandt
{{!}} craft = spacecraft
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Shuttle
| hangar = herbyw
| aircraft = shuttle
| image = Atlantis.png
| alt = Shuttle ''Atlantis''
| type = Spaceplane
| config = Delta-wing aircraft
| authors = HerbyW (FDM)/Firefly (3D)/Original Project Jon S. Berndt
| fdm = JSBSim
| fgname = shuttle/shuttle-Atlantis/shuttle-Columbia/shuttle-Launcher
| status-fdm = 2
| status-systems = 1
| status-cockpit = 0
| status-model = 3
| ready = rembrandt
| craft = spacecraft
| navbar = 1
| float = none
}}

=== Lake of Constance hangar ===

==== Boeing 707-420 ====
This is an example for the [[Boeing 707-420]] article, specifically in the [[Boeing 707-420/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Boeing 707-420/430
{{!}} hangar = lake of constance
{{!}} image = Splash707-420.png
{{!}} alt = {{LangSwitch
{{!}} de = Splash Screen der Boeing 707-420/430
{{!}} en = The 707-420/430's splash screen
}}
{{!}} type = Airliner/Military tanker aircraft
{{!}} config = Low wing aircraft/Monoplane aircraft/Retractable gear aircraft/Tricycle landing gear aircraft
{{!}} propulsion = Quadjet
{{!}} manufacturer = Boeing
{{!}} fdm = JSBSim
{{!}} authors = {{LangSwitch
{{!}} de = Marc Kraus - Lake of Constance Hangar/Original von Innis Cunningham
{{!}} en = Marc Kraus - Lake of Constance Hangar/Original model by Innis Cunningham
}}
{{!}} fgname = 707/707-TT/EC-137D
{{!}} status-fdm = 4
{{!}} status-systems = 5
{{!}} status-cockpit = 5
{{!}} status-model = 5
{{!}} ready = tutorials/checklist/rembrandt/airrefuel
{{!}} download = http://www.marc-kraus.de
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Boeing 707-420/430
| hangar = lake of constance
| image = Splash707-420.png
| alt = {{LangSwitch
| de = Splash Screen der Boeing 707-420/430
| en = The 707-420/430's splash screen
}}
| type = Airliner/Military tanker aircraft
| config = Low wing aircraft/Monoplane aircraft/Retractable gear aircraft/Tricycle landing gear aircraft
| propulsion = Quadjet
| manufacturer = Boeing
| fdm = JSBSim
| authors = {{LangSwitch
| de = Marc Kraus - Lake of Constance Hangar/Original von Innis Cunningham
| en = Marc Kraus - Lake of Constance Hangar/Original model by Innis Cunningham
}}
| fgname = 707/707-TT/EC-137D
| status-fdm = 4
| status-systems = 5
| status-cockpit = 5
| status-model = 5
| ready = tutorials/checklist/rembrandt/airrefuel
| download = http://www.marc-kraus.de
| navbar = 1
| float = none
}}

=== PAF hangar ===

==== Douglas C-47 Skytrain ====
This is an example for the [[Douglas C-47 Skytrain]] article, specifically in the [[Douglas C-47 Skytrain/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Douglas DC-3 C-47
{{!}} hangar = paf
{{!}} image = Dc-3-splash.png
{{!}} type = Airliner/Military transport aircraft
{{!}} config = Low wing aircraft
{{!}} propulsion = Twin-engine piston aircraft
{{!}} manufacturer = Douglas
{{!}} authors = PAF team (FDM, Hydraulic, Electric, Dual Control, Instruments, 3D)/Emmanuel Baranger (Exterior & interior 3D model)
{{!}} status-fdm = 4
{{!}} status-systems = 4
{{!}} status-cockpit = 4
{{!}} status-model = 4
{{!}} fdm = YASim/JSBSim
{{!}} fgname = dc-3-jsbsim (wheels)/dc-3-yasim (wheels)/dc-3A (Amphibius)/dc-3-copilot/dc-3-psg1/dc-3-psg2/dc-3-psg3/dc-3-psg4
{{!}} ready = dualcontrol/tutorials
{{!}} devel-website = <nowiki>http://equipe-flightgear.forumactif.com/t756-douglas-dc-3-c-47-part-2-2</nowiki>
{{!}} download = <nowiki>http://clement.delhamaide.free.fr/PAF/Douglas-Dc3.tar.gz</nowiki>
{{!}} liverydbid = 76
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Douglas DC-3 C-47
| hangar = paf
| image = Dc-3-splash.png
| type = Airliner/Military transport aircraft
| config = Low wing aircraft
| propulsion = Twin-engine piston aircraft
| manufacturer = Douglas
| authors = PAF team (FDM, Hydraulic, Electric, Dual Control, Instruments, 3D)/Emmanuel Baranger (Exterior & interior 3D model)
| status-fdm = 4
| status-systems = 4
| status-cockpit = 4
| status-model = 4
| fdm = YASim/JSBSim
| fgname = dc-3-jsbsim (wheels)/dc-3-yasim (wheels)/dc-3A (Amphibius)/dc-3-copilot/dc-3-psg1/dc-3-psg2/dc-3-psg3/dc-3-psg4
| ready = dualcontrol/tutorials
| devel-website = http://equipe-flightgear.forumactif.com/t756-douglas-dc-3-c-47-part-2-2
| download = http://clement.delhamaide.free.fr/PAF/Douglas-Dc3.tar.gz
| liverydbid = 76
| navbar = 1
| float = none
}}

=== Prestes hangar ===

==== Boeing 707-400 ====
This is an example for the [[Boeing 707-400]] article, specifically in the [[Boeing 707-400/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Boeing 707-400
{{!}} hangar = prestes
{{!}} aircraft = boeing-707-400
{{!}} image = 707-400.png
{{!}} alt = Lufthanse 707-400
{{!}} image2 = 707-400b.png
{{!}} alt2 = The VARIG 707-400 PAX
{{!}} type = Airliner
{{!}} config = Low wing aircraft
{{!}} propulsion = Jet aircraft/Four-engine aircraft
{{!}} manufacturer = Boeing
{{!}} authors = Isaias V. Prestes/Innis Cunningham/Erik Hofman (FDM)
{{!}} fdm = JSBSim
{{!}} fgname = 707-400
{{!}} status = Alpha
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Boeing 707-400
| hangar = prestes
| aircraft = boeing-707-400
| image = 707-400.png
| alt = Lufthanse 707-400
| image2 = 707-400b.png
| alt2 = The VARIG 707-400 PAX
| type = Airliner
| config = Low wing aircraft
| propulsion = Jet aircraft/Four-engine aircraft
| manufacturer = Boeing
| authors = Isaias V. Prestes/Innis Cunningham/Erik Hofman (FDM)
| fdm = JSBSim
| fgname = 707-400
| status = Alpha
| navbar = 1
| float = none
}}

=== Lost aircraft ===

==== C-17 Globemaster III ====
This is an example for the [[C-17 Globemaster III]] article, specifically in the [[C-17 Globemaster III/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = C-17 Globemaster III
{{!}} hangar = bermuda
{{!}} image = C17inflight.png
{{!}} type = Military transport aircraft/Strategic aircraft/Tactical airlifter
{{!}} config = High wing aircraft
{{!}} propulsion = Jet aircraft/Four-engine aircraft
{{!}} manufacturer = McDonnell Douglas/Boeing
{{!}} authors = Jon Bourgeois (FDM)/Adam Fothergill (3D)
{{!}} fdm = JSBSim
{{!}} fgname = C-17
{{!}} status = Not released yet
{{!}} note = The <nowiki>[http://cid-4501304d324ef633.office.live.com/self.aspx/.Public/C-17/C-17%2020100418.zip original download link]</nowiki> is dead.
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = C-17 Globemaster III
| hangar = bermuda
| image = C17inflight.png
| type = Military transport aircraft/Strategic aircraft/Tactical airlifter
| config = High wing aircraft
| propulsion = Jet aircraft/Four-engine aircraft
| manufacturer = McDonnell Douglas/Boeing
| authors = Jon Bourgeois (FDM)/Adam Fothergill (3D)
| fdm = JSBSim
| fgname = C-17
| status = Not released yet
| note = The [http://cid-4501304d324ef633.office.live.com/self.aspx/.Public/C-17/C-17%2020100418.zip original download link] is dead.
| navbar = 1
| float = none
}}

=== No hangar ===

==== Pipistrel Virus SW ====
This is an example for the [[Pipistrel Virus SW]] article, specifically in the [[Pipistrel Virus SW/info]] subpage.

{{obr}}infobox aircraft
{{!}} name = Pipistrel Virus SW
{{!}} image = Pipistrel Virus SW.png
{{!}} type = Civil aircraft/Civil utility aircraft
{{!}} propulsion = Propeller aircraft/Single-engine aircraft
{{!}} manufacturer = Pipistrel
{{!}} author1 = {{obr}}usr{{!}}Nick R{{cbr}}
{{!}} fdm = JSBSim
{{!}} fgname = virus-sw
{{!}} status = Development
{{!}} devel-repo = {{obr}}[[Template:github url|github url]]{{!}}user=Nick-R9{{!}}repo=pipistrel-virus-sw{{cbr}}
{{!}} download = <nowiki>http://www.fgpipistrel.org/downloads/</nowiki>
{{!}} navbar = 1
{{cbr}}

{{infobox aircraft
| name = Pipistrel Virus SW
| image = Pipistrel Virus SW.png
| type = Civil aircraft/Civil utility aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = Pipistrel
| author1 = {{usr|Nick R}}
| fdm = JSBSim
| fgname = virus-sw
| status = Development
| devel-repo = {{github url|user=Nick-R9|repo=pipistrel-virus-sw}}
| download = http://www.fgpipistrel.org/downloads/
| navbar = 1
| float = none
}}

}}

[[Category:Infobox templates|Aircraft]]
</noinclude>

User talk:Correcaminos

2025-10-27T09:03:21Z

Gijs: /* System freezes and crashed */ new section

{{Template:Welcome to the wiki|realName=|name=Correcaminos}}

-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 08:25, 27 October 2025 (UTC)

== System freezes and crashed ==

Hi,
{{cquote|After some minutes, the system may even freeze and crash|[[Hardware recommendations]]}}
This should not happen. Please open an issue in our issue tracker if you can reproduce this so we can try to fix the problem: https://gitlab.com/flightgear/flightgear/-/issues/new

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 09:03, 27 October 2025 (UTC)

Zeppelin LZ 121 Nordstern

2025-10-13T08:21:56Z

Gijs: Also use keypress template for modifier keys, like Ctrl

{{:{{PAGENAME}}/info}}

''Nordstern'' was the second of two small passenger airships built by Luftschiffbau Zeppelin in 1919 and 1920. ''Nordstern'' was designed to carry about 25 passengers on a Friedrichshafen - Berlin - Stockholm route but this route was never opened. The older sister ship LZ 120 ''Bodensee'' did run a regular passenger service between Friedrichshafen and Berlin during autumn 1919. In compliance with the terms of the peace treaty after WW I both airships were grounded early in 1920. ''Nordstern'' was handed over to France in 1921 where she remained in (sparse) service with the french military until 1926 under the name ''Méditerranée''. ''Bodensee'' was handed over to Italy and remained in service there until 1928 under the name ''Esperia''.

== Important controls / keys ==

=== Aerodynamic flight controls ===

* Rudder
* Elevator

In the most recent versions (FlightGear release 2024.1.1 and higher) there is a hidden crew "autopilot" system providing a virtual helmsman and elevator man. It can be activated by setting the properties
/crew/helmsman/enabled
/crew/elevatorman/enabled
to 1 (e.g. using the property browser). The helmsman is directed by the heading bug on the magnetic compass while the target altitude for the elevator man is set by the property
/crew/elevatorman/altitude-cmd-ft

Currently both channels use true references to guide their control rather than those provided by the aircraft instrumentation.

=== Engine controls ===

The side engines (engine 0 and 1) can be reversed by stopping the engine and starting it in the other direction.

* {{Key press|R}} - Switch the running direction for the selected engine(s). The engine(s) have to be stopped before switching direction.
* {{Key press|Shift|1}} - Select the port side engine (engine 0).
* {{Key press|Shift|2}} - Select the starboard side engine (engine 1).
* {{Key press|~}} - Select all engines.

The engines are Maybach MB IVa high altitude engines that can easily be oversped on lower altitudes due to their construction - their rated output of 245 hp @ 1400 RPM is reached well before the throttle is fully open up to an altitude of 1800 m. At emergency power engine speed may go up to 1460 RPM.

In the most recent versions (FlightGear release 2024.1.1 and higher) there is a hidden crew "autopilot" system providing virtual engine
men. It can be activated by setting the property

/crew/machinists/enabled

to 1.0. The throttle controls then set the desired RPMs instead of the normal low-level throttle controls.

=== Gas valve controls ===

* {{Key press|F}}/{{Key press|f}} - Open/close the gas valves of the fore gas cells.
* {{Key press|G}}/{{Key press|g}} - Open/close the gas valves of the aft gas cells.

Rigid airships like ''Nordstern'' take-off light in a static maneuver and normally land in balance to slightly heavy in a static maneuver. The primary use for the gas valves is to reduce static lightness when needed.

=== Ballast controls ===

* {{Key press|w}} - Show current on-ground weight. Only works when on the ground.
* {{Key press|W}} - Weigh off to neutral by adding/removing ballast. Takes about 10 seconds and is only applicable when on the ground.
* {{Key press|e}}/{{Key press|d}} - Shift trim ballast fore/aft.
* {{Key press|E}}/{{Key press|D}} - Drop one quick-release (a.k.a. emergency) ballast bag fore/aft. There are 6 bags fore and 4 aft.
* {{Key press|Ctrl|W}} - Refill the quick-release ballast bags from the trim ballast.

Use the "Fuel and payload" dialog to replenish the ballast tanks. Realistically this can only be done while moored.

[[File:Nordstern-elevator-station.jpg|thumb|600px|center|''Nordstern'''s elevator control station. The black toggles release emergency ballast, while the red toggles control the maneuvering gas valves. Below are the pitch inclinometers, the altimeter and, to the right, the variometer.]]

=== Ground crew / Mooring mast ===

* {{Key press|Y}} - Release mooring mast connection or wire.
* {{Key press|U}} - Attach mooring wire. Only possible when close to a mooring mast.
* {{Key press|y}}/{{Key press|u}} - Play out/winch in mooring wire.
* Alt + click on terrain - Place the mooring mast.

The real ''Nordstern'' never used a mooring mast. All ground handling was done manually with the ground crew manning yaw lines fore and aft and, once within reach, holding on to the handling rails on the control car and the aft engine car.

[[File:Nordstern.jpg|thumb|600px|center|The control car of ''Nordstern''.]]

[[File:Nordstern-interior.jpg|thumb|600px|center|The interior of ''Nordstern'''s control car.]]

== Installation and Dependencies ==

* LZ 121 Nordstern (Development version for [http://github.com/andgi/FlightGear-Nordstern FG/git], click "Download ZIP".)

This aircraft depends on instruments from some other aircraft. Install a matching version of these too. They need to be installed in the same Aircraft/(<each aircraft directory>) directory for FlightGear to find the files.

* [[ZLT-NT]]

== Known problems ==

* The anachronistic mast truck is invisible in 2.10.0. The problem has been fixed in subsequent versions of FlightGear.

* Under some conditions at low or negative airspeed the airship can suffer from undamped yaw oscillations. This seems to be an interaction between the added mass simulation and the dynamic aerodynamic coefficients. (old)

* Real weather fetch sometimes cause NaN problems.

* Before FlightGear 2016.1.1 the mooring force calculations were sensitive to long frame times (i.e. very low fps), which could cause FlightGear to crash during startup or make the airship start in a bad state.
'''Workaround''': Try setting /sim/max-simtime-per-frame to 0.1 seconds or less. This can be done in preferences.xml by modifying the line
<max-simtime-per-frame>1.0</max-simtime-per-frame>
to
<max-simtime-per-frame>0.1</max-simtime-per-frame>

== External links ==

* [http://www.gidenstam.org/FlightGear/Airships/ Download page with other lighter-than-air aircraft for FlightGear.] Requires the LTA support available in FlightGear 1.9.0 or later. '''Note: The most up to date version of the Zeppelin LZ 121 Nordstern is available in FlightGear/git.'''

{{Aerostat}}

[[Category:Historical aircraft]]
[[Category:Airships]]

Goodyear K-Type Airship

2025-10-13T08:20:35Z

Gijs: /* Gas and Envelope */ also use keypress template for modifier keys, like Ctrl

{{:{{PAGENAME}}/info}}

The Goodyear K-Type airship, designated ZNP-K in the US Navy, was the main maritime patrol airship for the US Navy during World War 2. The non-rigid airships (a.k.a. blimps) were 75 to 79 meters long, had a volume of about 404000 to 425000 ft^3 (11500 to 12000 m^3) and were powered by two Pratt & Whitney R-1340 or Curtis-Wright R-975 engines fitted on outriggers on the control car. The prototype was the K-2 which first flew in December 1938. A total of 133 K-Type airships were built during the war, the last, K-135, was delivered in April 1944.

== Important controls / keys ==

=== Aerodynamic flight controls ===

* Rudder (Aileron input is also transferred to the rudder for convenience.)
* Elevator (The elevator trim is seldom used see below for pitch trim.)

==== Crew support ====

You can get some support from the crew for the rudder and elevator control which are controlled in the property directories ''/crew/rudder-pilot/'' and ''/crew/elevator-pilot/''.
In each there is an ''enabled'' property (0.0 is off and 1.0 is on) and a control property:
* in the elevator-pilot the property is ''altitude-cmd-ft''; and
* in the rudder-pilot the property is ''heading-magnetic-cmd-deg''.

=== Engine controls ===

The US Navy ZNP-K airship (from K-9 and later) has two Pratt and Whitney R-1340-AN2 radial engines with fixed pitch propellers.

* Throttle (PgUp/PgDn) - Increase/decrease engine RPM and power.
* Mixture levers (M/m) - Leaner/richer mixture.

==== Crew support ====

You can get some support from the crew for the engines which are controlled in the property directory ''/crew/mechanic/''.
There is an ''enabled'' property (0.0 is off and 1.0 is on) and with it 1.0 (ON) the normal throttles give the desired RPM (in 550 - 2250) of the engines.

=== Gas and Envelope ===

* {{Key press|Q}}/{{Key press|q}} - Open/close the damper (air intake) for the fore ballonet.
* {{Key press|Ctrl|Q}} - Open forward ballonet air valve (air outlet). Closes on key release.
* {{Key press|A}}/{{Key press|a}} - Open/close the damper (air intake) for the aft ballonet.
* {{Key press|Ctrl|A}} - Open aft ballonet air valve (air outlet). Closes on key release.
* {{Key press|F}}/{{Key press|f}} - Open/close the gas valve.
* {{Key press|R}} - Pull the rip cord to quickly deflate the envelope. Do NOT use in midair.

The fore and aft ballonets (air-filled bags inside the envelope) serve two purposes: (i) by inflating/deflating they maintain the pressure differential and volume of the envelope when the gas changes volume; and (ii) the trim of the airship can be changed by the relative inflation of the ballonets. While the required envelope pressure dictate the total volume of the ballonets the airship can be trimmed by having one ballonet more or less inflated than the other.

==== Envelop pressure management ====
When the airship rises the gas in the envelope expands and consequently the total volume of the ballonets has to decrease or the envelope pressure will increase. There are pressure relief valves that automatically open when the pressure in the ballonet exceeds a set limit (which is lower than that of the gas relief valve to prevent gas being valved before both ballonets are empty) but the prudent airship pilot would rather use the manual ballonet valves than rely on the relief valves.

When the airship descends the increasing ambient pressure causes the gas in the envelope to contract and to maintain the envelope pressure above the ambient pressure the total volume of the ballonets has to increase. The pilot has to set the ballonet controls for inflation. Monitor the gas pressure gauge!

==== Pitch trim ====
On the US Navy ZNP-K airship pitch trimming is done via the relative inflation of the fore/aft ballonets rather than with the elevator trim. Shifting air between the ballonets moves the center of gravity.

* To trim towards nose heavy - set the fore ballonet valve for inflation and/or the aft for deflation.
* To trim towards tail heavy - set the aft ballonet valve for inflation and/or the fore for deflation.

If the airship is above ''pressure height'', i.e. the altitude where the lifting gas occupies the entire volume of the envelope, the ballonets are empty and cannot be used for pitch trimming (and the simulated airship is likely to go badly out of trim). Ascending above pressure height also result in loss of lifting gas, beware of losing too much or you will be unable to maintain the envelope pressure when descending to the ground again.

'''Center of gravity range'''
FIXME.

=== Ballast ===

The US Navy ZNP-K airship normally carries no ballast for inflight adjustment. Use on ground only.

* {{Key press|w}} - Show current on-ground weight. Only works when on the ground.
* {{Key press|W}} - Weigh off to 1000lbs heavy by adding/removing ballast. Takes about 10 seconds and is only applicable when on the ground.

=== Ground crew / Mooring mast ===

The US Navy ZNP-K airship currently uses the non-period mast truck from the [[Zeppelin NT]]. In actual service either mobile tripod masts towed by tractors or fixed stick masts where used.

* {{Key press|Y}} - Release mooring mast connection or wire.
* {{Key press|U}} - Attach mooring wire. Only possible when close to a mooring mast.
* {{Key press|y}}/{{Key press|u}} - Play out/winch in mooring wire.
* Alt + click on terrain - Place the mooring mast.

When landing to a stationary mast (which is the usual case in FlightGear), approach straight into the wind and land short of the mast and taxi up to it under as precise control as possible. The US Navy ZNP-K is not very manoeuvrable at low speed so special care is required. In real life it would land into the hands of a ground handling party and once stationary a mobile mast would be moved up to the nose of the ship and connected to the mooring attachment there.

The mooring mast is visible over the multiplayer network. It is also possible for other pilots using ZNP-K, Zeppelin NT or Nordstern airships to dock with your mast.

== Cockpit and instruments ==

FIXME.

== Handling instructions ==

'''Disclaimer:''' These instructions are derived only from common sense together with certain available documentation and have no connection whatsoever to any instructions for the real ZNP-K airships.

FIXME.

== Installation and Dependencies ==

* US Navy ZNP-K (Development version for [http://github.com/andgi/FlightGear-ZNP-K FG/git], click "Download ZIP".)

This aircraft depends on instruments from some other aircraft. Install a matching version of these too.

* [[ZLT-NT]]
* [[Short Empire]]

== Known problems ==

* If the airship is in a sufficiently heavy state when FlightGear starts it might crash at the mast. In particular this may happen at high altitude airports. Initializing with a significantly reduced amount of fuel and payload may help.

== External links ==

* [http://www.gidenstam.org/FlightGear/Airships/ Download page with other lighter-than-air aircraft for FlightGear.] Requires the LTA support available in FlightGear 1.9.0 or later. '''Note: The most up to date version of the US Navy ZNP-K airship is available [http://github.com/andgi/FlightGear-ZNP-K here] for FlightGear/git.'''

{{Aerostat}}

Template:Current release

2025-09-18T21:25:15Z

Gijs: 2024.1.2

<includeonly>{{#switch: {{{1|}}}
| cr = 2024.1
| crd = 27 February 2025
| nr = 2024.1.3
| nrd = 

| full = 2024.1.2
| fulldate = 18 September 2025

| #default = {{error|No argument given|current release}}
}}</includeonly><noinclude>
{{Informative template|1=
== Goal ==
This template is used internally by {{tl|GitStatus}} to display:
# the current release
# the release date of the current release
# the next release
# the number of days until the next release. Leave empty or comment if unknown
# the full version of the newest release and its release date

This template should be updated with every new release, including bugfix releases.

== Usage ==
{{obr}}'''current release'''{{!}}data{{cbr}}

; data : Dictates what data is returned. This parameter is mandatory. Value may be one of:
:*'''cr''': Current release
:*'''crd''': Release date of current release
:*'''nr''': Next release
:*'''nrd''': Days until the next release

== Examples ==
{{obr}}current release{{!}}cr{{cbr}}
{{current release|cr}}

== Related template ==
* {{tl|GitStatus}}

== See also ==
* [[Release plan]]

}}

[[Category:Git templates]]
</noinclude>

MediaWiki:Email-blacklist

2025-09-09T19:45:11Z

Gijs: Fix pre

# <pre>
# Email addresses matching this list will be blocked from registering or sending emails
# This list affects only this wiki; refer also to the global block list.
# For documentation see https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:SpamBlacklist
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts inside email addresses

.*cosmicbridge\.site
.*cosmiccluster\.store
.*cosmiccrest\.site
.*dnsabr\.com
.*dns-cloud\.net
.*echocosmos\.online
.*spambog\.ru

#</pre>

MediaWiki:Email-blacklist

2025-09-09T19:42:43Z

Gijs: Add spam emails

# <pre>
# Email addresses matching this list will be blocked from registering or sending emails
# This list affects only this wiki; refer also to the global block list.
# For documentation see https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:SpamBlacklist
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts inside email addresses

#</pre> 

.*cosmicbridge\.site
.*cosmiccluster\.store
.*cosmiccrest\.site
.*dnsabr\.com
.*dns-cloud\.net
.*echocosmos\.online
.*spambog\.ru

GitLab

2025-09-02T14:45:07Z

Gijs: /* Merge request */ use {{flightgear source}}

'''GitLab''' is an open source hosting infrastructure provider. Since January 2025, it hosts several [[Git]] version control repositories of [[FlightGear]] that were previously hosted on [[SourceForge]].

== Development ==

=== Merge request ===
First, open the repository you want to change and fork the project using the ''Fork'' button.

Clone your forked repository to your computer, add the original upstream repository
git remote add upstream {{flightgear source |type = git |full = 1}}
Then to update your repo with changes from original repo (example with next branch) :
git pull --rebase upstream next
Go to the branch you want to change, then from it, create a new branch for your MR.
git checkout -b my_new_feature
Create your commits on this branch, and push to your origin repository.

Once done, on Gitlab, on your repo, it will propose you to create a Merge Request.

=== pre-commit ===
When opening a merge request in GitLab, a [https://pre-commit.com/ pre-commit] hook is run. Assuming <code>origin</code> is the name of the Git remote for the official repository you'd like to contribute to, you can test your changes locally with:
git diff --name-only origin/next | xargs -r pre-commit run --files
This changes/fixes your working directory so you can commit, check or reset the changes.

{{Note|The <code>pre-commit run</code> command will immediately show the changes if you pass it the <code>--show-diff-on-failure</code> option.}}

Sample output of the <code>pre-commit run</code> command:

<pre>
fix end of files.........................................................Failed
- hook id: end-of-file-fixer
- exit code: 1
- files were modified by this hook

Fixing src/AIModel/AIConstants.hxx
Fixing src/ATC/ATCController.hxx

trim trailing whitespace.................................................Failed
- hook id: trailing-whitespace
- exit code: 1
- files were modified by this hook

Fixing src/Airports/groundnetwork.cxx
Fixing src/AIModel/AIAircraft.cxx
Fixing src/AIModel/AIConstants.hxx
Fixing src/ATC/ATCController.cxx
Fixing src/ATC/trafficcontrol.cxx
Fixing src/ATC/ATCController.hxx
Fixing src/AIModel/AIFlightPlanCreate.cxx
Fixing src/ATC/GroundController.cxx

codespell................................................................Failed
- hook id: codespell
- exit code: 65

src/AIModel/AIFlightPlan.hxx:53: nam ==> name
src/AIModel/AIFlightPlan.hxx:53: nam ==> name
src/ATC/ApproachController.cxx:91: exsists ==> exists
src/Airports/groundnetwork.cxx:183: backard ==> backward
src/ATC/ATCController.hxx:43: acknowlegde ==> acknowledge
src/ATC/trafficcontrol.cxx:76: existant ==> existent
src/ATC/trafficcontrol.cxx:105: paramater ==> parameter
src/ATC/trafficcontrol.cxx:213: paramater ==> parameter
src/ATC/GroundController.cxx:158: acknowlegde ==> acknowledge
src/ATC/GroundController.cxx:537: maintanance ==> maintenance

yamlfmt..............................................(no files to check)Skipped
clang-format.............................................................Failed
- hook id: clang-format
- files were modified by this hook
reuse lint-file..........................................................Failed
- hook id: reuse-lint-file
- exit code: 1

src/ATC/ApproachController.cxx: no license identifier
src/ATC/trafficcontrol.hxx: no license identifier
src/ATC/TowerController.cxx: no license identifier
src/ATC/trafficcontrol.hxx: no copyright notice
src/ATC/trafficcontrol.cxx: no license identifier
test_suite/unit_tests/AI/TestSuite.cxx: no license identifier
src/ATC/GroundController.cxx: no license identifier
src/ATC/atc_mgr.cxx: no license identifier
src/ATC/atc_mgr.cxx: no copyright notice
</pre>

==References==

*[https://gitlab.com/flightgear FlightGear GitLab website]
*{{wikipedia |Gitlab |GitLab wikipedia article}}

[[Category:Hosting infrastructure]]

FGQCanvas

2025-07-30T17:54:34Z

Gijs: /* Usage */Update source url to GitLab

{{Canvas Navigation}} 
[[File:FGQCanvas Boeing 747-400 PFD and ND.png|thumb|FGQCanvas window showing the PFD, ND and EICAS of the [[Boeing 747-400]].]]

'''FGQCanvas''' is a Qt-based remote [[canvas]] application for [[FlightGear]]. This app can connect to a FlightGear instance which has the built-in HTTP server enabled and display any canvas in real-time at any resolution and/or relative positioning.

== Usage ==
See {{flightgear source
| path = utils/fgqcanvas/README.md
| pre = $FLIGHTGEAR_SRC
}} for instructions on how to use FGQCanvas.

# Launch FlightGear with <code>--httpd=8080</code>.
# Launch FGQCanvas.
# Follow the on-screen instructions.

== Background ==
{{See also|FGCanvas}}
James has spent some of his time since FSWeekend 2016 figuring out how he might drive some ‘real’ CDU hardware from the in-aircraft CDU options, and went for a slightly ambitious approach: he's written an analogue of [[FGPanel]] for the [[canvas]].

Analogue is actually not quite correct - unlike FGpanel this connects at the view level (canvas properties), it doesn’t run the canvas ‘model’ locally, since that would be very tough ([[Nasal]] + whole [[property tree]] needed).

This distinction was unimportant for the canvas up until now, but it’s going to become important he expects.
This was prompted by his intention to buy something like this: http://www.flightdecksolutions.com/components/b737ng/b737ng-mipmain/fds-b737ng-pro-mx-cdu-color-vga/
Which means James needs the CDU screen running on its own screen/device nicely.

And he already wrote a page-based Canvas CDU over a year ago, it’s just sitting on Gijs’ hard-drive awaiting being merged.

This is currently proof-of-concept quality, but already works quite nicely:

* uses a websocket to send an entire property sub-tree (a canvas, but in principle could be anything) to another process / machine
* render the canvas at arbitrary sie/resolution
* it’s ten source files and very simple code

It looks like this:
(see the [http://fgfs.goneabitbursar.com/screenshots/remote-canvas-nd.png linked image])<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=300990#p300990
|title = <nowiki> </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Dec 10th, 2016
|added = Dec 10th, 2016
|script_version = 0.40
}}</ref>

== Status ==
James is very happy with this approach so far, since any Canvas display can be trivially run out-of-process, remotely on an Android tablet, Raspberry Pi, iPhone or whatever. (he is hoping to make an app available on the Play store and App store, but one thing at a time). The 777 ND and lower EICAS pages work and look great at larger sizes. James also investigated using a binary protocol for doing the mirroring, current one is an optimised JSON protocol but swapping in a binary protocol is very doable in the future.<ref>{{cite web
|url = https://forum.flightgear.org/viewtopic.php?p=300990#p300990
|title = <nowiki> </nowiki>
|author = <nowiki> zakalawe </nowiki>
|date = Dec 10th, 2016
|added = Dec 10th, 2016
|script_version = 0.40
}}</ref>

This has prompted James to look at some more fundamental pieces of the Canvas, because there are some things the Canvas / Map layer do which are not very performance-friendly, especially the symbol-caching / texture-atlasing can be managed better on the rendering-client side. (Plus all the overhead that comes from doing lots of work in Nasal) The system would benefit from some knowledge about screen-space pixel size, so that each per-frame change in heading / aircraft position does not cause every symbol and route-path element to be recomputed in cartesian space and then re-transmitted over the mirror-socket. (But, even doing that, and with a software rendering, it’s still fast - computers are really quick….)<ref>{{cite web
|url = https://sourceforge.net/p/flightgear/mailman/message/35543715/
|title = <nowiki> [Flightgear-devel] Announcement: Remote canvas </nowiki>
|author = <nowiki> James Turner </nowiki>
|date = Dec 10th, 2016
|added = Dec 10th, 2016
|script_version = 0.40
}}</ref>

== References ==
{{Appendix}}

Volunteer

2025-07-27T19:50:45Z

Gijs: /* Submitting bugs to the Bug Tracker */ use template link

{{Volunteer Intro}}

== Media ==
=== Screenshots ===
Another easy way for getting started contributing is to create nice FlightGear screenshots. You can upload these to the wiki where they can then be used to illustrate articles and to highlight articles via the [[:Category:Picture of the week|picture of the week]] on the main page.

[[Howto: Make nice screenshots]] provides some tips on how to create stunning shots, while [[Help:Upload]] discusses how to upload screenshots to the wiki.

=== Videos ===
Many users like to capture their flights in FlightGear as a video, YouTube for example is an excellent way for sharing such videos with fellow FlightGear users. YouTube videos can also be directly embedded in forum postings and wiki articles.

=== Screencasts (video tutorials) ===
Creating FlightGear related video tutorials is another excellent way for getting started contributing.

== Documentation ==

{{forum|72|FlightGear Documentation}}

=== FAQ-Maintainers ===
The FlightGear project is looking for people who are willing to help maintain the FAQ which, given the constant development of the project, is chronically out of date. If you you would like to get involved, follow the {{forum link|text=forum}} to stay current on the latest news, problems, and of course on what questions are asked more frequently, and simply start editing the [[FAQ|wiki FAQ]].

=== Maintaining the wiki ===
You can easily [[Special:UserLogin|register an account]] and help [[Portal:Wiki|improve the wiki]], and provide your help in reviewing articles, fixing their look and readability, updating them and adding what you think is missing, for example many articles could be greatly improved just by adding a handful of relevant screenshots for illustration purposes. Proof reading of existing articles is also greatly appreciated.

Registering takes less than 10 seconds. After registration, you'll have to confirm your registration by clicking on the link sent to you by email.

=== Translating the wiki and FlightGear ===
You can also help localize the wiki by [[Help:Translate|translating]] important articles into different languages. Please see the [[translation requests]].

Also, FlightGear itself can be easily translated by updating the files in [[$FG_ROOT]]/Translations. For details please see [[Howto: Translate FlightGear|Translating FlightGear]].

=== Wiki article writers ===
Various aspects of FlightGear are currently not yet sufficiently documented, and available documentation is often not really suitable to be used by non-developers. This results in users being unaware of the wide range of features and possibilities that FlightGear supports already.

As an "article writer" you should be able to document your own experiences with FlightGear in a clear and concise style, so that others can easily follow your instructions in order to make use of the less known features of FlightGear. These articles don't need to be very comprehensive, they shall only provide users with easy to follow instructions on how to achieve something, and possibly some caveats and hints.

* [[:Category:Volunteer: Writing]]

=== Contributing to "The Manual" ===
The wiki is not the only documentation here, of course. FlightGear comes with a set of illustrated documentation, notably [[FlightGear Manual|"The Manual"]]. If you are a skilled writer and a little bit familiar with LaTex, your help would be really welcome. More on this at "The Manual" wiki page. You'll find the source code in the {{getstart source|text=Getstart repository}}.

=== Documentation Editors/Reviewers ===
{{Main article|Howto:Write a FlightGear Review}}
The documentation that comes with FlightGear base package is lacking, terse or simply inaccurate (outdated), due to the advances in FlightGear's code. You should check the current documentation and identify areas for improvement, by directly making corresponding suggestions for augmentations, or even writing new help documents altogether, while staying current with the mailing list.

Smaller corrections shall be sent by email to the developer mailing list, preferably in unified diff format (for patch to work). Alternatively, small text files can also be sent directly to the mailing list, more complex modifications should be only made available by uploading them to a webpage and linking to the corresponding files from your emails. Please consider trying [http://kdiff3.sourceforge.net/ KDiff3], a GUI frontend to the diff and patch utilities that works on several platforms (also Windows).

If you intend to redo a major part of the current documentation, first discuss this with the developers, to avoid documenting code that may also be under development or deprecation.

== Development ==
=== Creating interactive tutorials ===
FlightGear has a built-in [[Tutorials|tutorial]] system that is based on its scripting language [[Nasal]], this system is very flexible and can be used for creating interactive tutorials (or even missions) for use in FlightGear itself, in other words these tutorials run directly in the simulator.

Creating new tutorials, or updating and improving existing ones, is another great way for getting more familiar with FlightGear. For details please see [[Tutorials]].

=== Providing patches for aircraft's -set.xml status fields ===
One way you could easily contribute would be to submit patches to HEAD setting the "status" flag on each aircraft accurately. While it will require learning a bit about SCM, and XML, that would be a fine contribution. For a details on how the status should be arrived at see [[Aircraft status indication]].

=== Creating Scenery Models ===
The FlightGear project maintains a steadily growing repository of [http://scenemodels.flightgear.org 3D models] for adding some eye-candy to the scenery. The world has always enough room left for your [http://scenemodels.flightgear.org/contribute.php contribution]. Please take the time to investigate what is already there and enjoy populating your favourite area.

Note that you don't have to create any models yourself. You can simply [[Howto: Place 3D objects with the UFO|place existing models using the UFO]]. For example, placing objects in the scenery with the [[UFO]] and submitting them to the database is pretty straightforward and takes very little time. Even an hour spent doing this makes a difference.

If anyway you'd like to [[Modeling - Getting Started|test your modeling skills]], here some suggestions:
* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

It would be helpful if people would model the area they are interested in. Generally contributions are going to be from FlightGear users who find scenery lacking in some area and choose to improve it. You are encouraged to research your own area for airport, navaid and scenery information, to contribute the data or dive right in to airport and scenery design.

=== Making airports ===
Sometimes you'd like to populate your favourite airport with objects, but you find it has a wrong layout or that it doesn't exist at all! So, you'll want to [[Howto:Make an airport|make or improve that layout]], which can be done with [[WED]]. Remember that we're maintaining an open (GPL) airport database in common with X-Plane simulator.

Other than just fix the look, you might want to add interactive details like [[AI Traffic]] and maybe update navaids and comm frequencies. We need people to go over paper lists and airport diagrams for countries that don't publish air navigation data free online (i.e. almost everyone but the U.S.) and fill in the blanks in our navaid and airport databases (''note: especially for the last part, see the website of the current maintainer: [https://gateway.x-plane.com/ X-Plane Scenery Gateway]''.)

To be sure the airport you're interested in is not already being worked on, check the [[Airports under construction]] article. Also, note that since we switched to a newer format for the airport database, there are many airports that need to be converted from the older (810) format to the newer (850). All the info is in [[Howto:Make an airport]].

=== Contributing to the scenery terrain ===
We need people to collect geodata to give us more accurate roads, rivers, etc., especially outside the U.S. and Europe. Note that since we're now allowed to use OpenStreetMap data for this, you might consider contributing to that project too. With time, more and more features will be imported from OSM, beginning with roads and rails, and going on with power lines and antennas and whatnot.

The first step into this is learning how to [[Using TerraGear|use TerraGear]]. Remember that all the data you plan to use must be GPL compatible. You might also consider editing some of that source data and contribute it to the Scenery Project that would make good use of it!

=== Core development ===
If you actually happen to be a C++ programmer and know Git, consider contributing to [[Howto:Start core development|core development]].

{{CppBind Ideas}}

== Other ==
=== Submitting bugs to the Bug Tracker ===
Bugs can be reported to {{tickets|the issue tracker}} (select the respective project, or <code>flightgear</code> if unsure). Reporting bugs accurately helps make bug fixing significantly easier for the developers. Another thing that is very helpful, is reviewing posted bug reports and see if you can reproduce/confirm them on your system.

=== Artwork Creators/Contributors ===
FlightGear itself would not be possible without the contribution of various types of artwork:
* Aircraft developers need photographs, images and sounds to realistically model a particular aircraft.
* The splash screen displayed when loading the simulator can be personalized, and you can [[Howto: Create custom splash screens|create one for your favourite aircraft]].
* Sound recordings of aircraft are also very valuable - particularly engine sounds for unusual aircraft.

In general, you can find requests and post your offers of this kind in the Developers forum, but you can also browse [[:Category:Aircraft by status|existing aircraft projects]] and see if there's anything you'd like to improve.

=== Pre-Release Testers ===
Prior to a release, release candidates are provided to the community. By directly providing feedback about your experiences with FlightGear's development code, you will become a crucial part of the development process and you will basically serve as quality control for FlightGear, your experiences will determine whether FlightGear's development code is ready for a next official release or not. See the [[Release plan]] to find out when release candidates will be distributed.

Note: If you are interested in actually doing development for FlightGear, make sure to check out the [[Portal:Developer|Developer section]].

=== Hosting a multiplayer server ===
If you have access to an Unix based server, another good opportunity for contributing would be to set up a multiplayer server for use with FlightGear, for details please check out [[Howto: Set up a multiplayer server]].

=== Tell us if FlightGear works with your hardware ===
You can help fellow FlightGear users by telling us if FlightGear works with your hardware. Please see [[FlightGear Hardware Recommendations]], [[Problematic Video Cards]] and [[Notebooks known to run FlightGear]].

=== Participate in the FlightGear Forums ===
If you haven't done so already, please consider registering at the {{forum link|text=FlightGear forum}}, this is a very simple thing to do, but it makes it very easy to obtain and provide help and other support within the FlightGear community.

Taking extra care in your posting to avoid requiring the attention of the moderators is in some ways also a contribution. Doing so helps self-police the forums so that the moderators can spend their time doing constructive development.

=== Check out the FlightGear Chat channel ===
{{Main article|FlightGear IRC channel}}
To talk to fellow FlightGear users in realtime, you may want to check out the IRC chat channel.
This is also an excellent way for getting and providing community help, or for getting the latest news about FlightGear.

=== Tell us about your own ideas and feature requests for improving FlightGear ===
If you think you have a good idea or feature request for improving FlightGear, the FlightGear forums and the IRC channel are also an excellent way for getting feedback.

Another new way for posting feature requests and making suggestions is provided at http://flightgear-bugs.googlecode.com

=== Help us write the FlightGear Newsletter ===
The FlightGear newsletter is a community driven newsletter that is created and edited using the wiki. All FlightGear users are invited to contribute to the newsletter. The only thing that is required is a wiki account, which is free and easy to register.

Please feel free to add news about your own FlightGear related projects, or projects started by others to the newsletter.

You can find the draft of next month's newsletter at: [[Next newsletter]]

Just tracking the forums, mailing lists or the IRC channel should provide you with plenty of opportunities for things that could be added to the newsletter. One simple thing for getting started - even without writing anything - is uploading screen shots showing recent FlightGear developments for use in the FlightGear newsletter.

=== Reviews ===
Another thing that can be easily done is reviewing FlightGear (or just certain parts of it, like for example scenery and/or aircraft) and submit your reviews to some of the flight simulation portals. Of course, you can also directly write your reviews using the FlightGear wiki, see: [[FlightGear Reviews]].

[[Category:Contribution requests]]
[[Category:Community]]

[[es:Tener a bien]]
[[fr:Volontaires]]

Template:Simgear file

2025-07-23T08:34:43Z

Gijs: Update to Gitlab

[https://gitlab.com/flightgear/simgear/-/blob/{{#if: {{{r|}}} 
| {{{r}}}/{{{1|}}}{{#if: {{{l|}}} 
| #L{{{l}}}
}} {{#if: {{{t|}}} | {{{t}}}] | {{#if: {{{nopath|}}} | | simgear/ }}{{{1|}}}] ({{{r}}}{{#if: {{{l|}}} | , line {{{l}}} }}) }}
| next/{{{1|}}}{{#if: {{{l|}}} 
| #L{{{l}}}
}} {{#if: {{{t|}}} | {{{t}}}] | {{#if: {{{nopath|}}} | | simgear/ }}{{{1|}}}]{{#if: {{{l|}}} |  (line {{{l}}}) }} }}
}}<noinclude>
{{Informative template|1=
__NOTOC__ {{depreciated|The newer {{tl|simgear source}} template provides far greater functionality and should be used instead. This is not a subtemplate of the master {{tl|repo link}} template.}}
== Goal ==
This template can be used when linking to source files or directories in the [[SimGear]] repository.

== Usage ==
{{obr}}'''simgear file'''{{!}}''path''{{!}}''l=''{{!}}''t=''{{!}}''r=''{{!}}''nopath=''{{cbr}}

Both parameters are optional.

; path: What follows after <code>/tree/</code> in the URL. Can be the path to a file or a directory. If empty, the link will point to the root of the SimGear repository.

; l: A line number. This should just be a single number, as SourceForge does not support multiple line numbers.
: {{inote|This parameter will not work if the linked file is of a certain file type, such as <code>.nas</code>. However, this is to do with SourceForge, not the template.}}

; r: A commit reference. Usually the SHA-1 commit ID (which can be abbreviated), but it can also be a tag or a branch name. If empty, the link will point to the '''next''' branch.

; t: Text to show as the URL's label instead of file path.

; nopath: Strips off the <code>fgdata/</code> part of the URL label, leaving just the contents of the '''path''' parameter.
: {{inote|The '''t''' parameter will override this parameter.}}

== Examples ==
=== No parameters given ===
{{obr}}simgear file{{cbr}}
{{simgear file}}

=== Path given ===
{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx}}

=== Path and a commit reference given ===
{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}r=release/2.12.0{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|r=release/2.12.0}}

{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}r=4f94c2{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|r=4f94c2}}

{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}r=4f94c22241e5ef90026fd087168b24a13ee5ef9b{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|r=4f94c22241e5ef90026fd087168b24a13ee5ef9b}}

=== Line parameter given ===
{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}l=5{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|l=5}}

{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}r=4f94c2{{!}}l=5{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|r=4f94c2|l=5}}

=== Custom label given ===
{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}t=Canvas.cxx{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|t=Canvas.cxx}}

=== Nopath parameter given ===
{{obr}}simgear file{{!}}simgear/canvas/Canvas.cxx{{!}}nopath=1{{cbr}}
{{simgear file|simgear/canvas/Canvas.cxx|nopath=1}}

== Related templates ==
{{repo link/doc related}}

}}

[[Category:Repository link templates]]
</noinclude>

Talk:Flight Dynamics Model

2025-07-21T17:58:10Z

Gijs:

Hello, I have been a Flightgear user for many years and I am very satisfied with it. I would like to alert you to a problem with the operation of a model that is close to my heart, the proposed Mirage III E, whose aerodynamic qualities do not correspond at all to the real model in terms of acceleration, maneuverability, stall/landing speed. I have no idea if I am in the right place to raise this issue, but I cannot find any other way to talk about it.

{{unsigned|13:28, 21 July 2025‎|Pierre}}

: Hi Pierre,
: Our support forum is the primary location for questions like this: {{forum url}} Please open a topic there.
: [[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 17:58, 21 July 2025 (UTC)
: PS: Please sign your comments on wiki talk pages with <code><nowiki>~~~~</nowiki></code> to add your name and the date.

Template:Openradar source

2025-07-17T11:23:46Z

Gijs: OpenRadar is still on SourceForge

{{repo link
| site = sf
| cmd{{#if:{{{cmd|}}}||NULL}} = {{{cmd}}}
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type{{#if:{{{type|}}}||NULL}} = {{{type}}}
| proj = flightgear
| repo = openradar
| branch = {{{branch|{{{b|master}}}}}}
| tag{{#if:{{{tag|}}}||NULL}} = {{{tag}}}
| path{{#if:{{{path|{{{f|{{{1|}}}}}}}}}||NULL}} = {{{path|{{{f|{{{1}}}}}}}}}
| commit{{#if:{{{commit|{{{c|}}}}}}||NULL}} = {{{commit|{{{c}}}}}}
| line{{#if:{{{line|{{{l|}}}}}}||NULL}} = {{{line|{{{l}}}}}}
| view{{#if:{{{view|{{{v|}}}}}}||NULL}} = {{{view|{{{v}}}}}}
| text{{#if:{{{text|{{{t|}}}}}}||NULL}} = {{{text|{{{t}}}}}}
| pre{{#if:{{{pre|}}}||NULL}} = {{{pre}}}
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| simplepath{{#if:{{{simplepath|}}}||NULL}} = {{{simplepath}}}
| full{{#if:{{{full|}}}||NULL}} = {{{full}}}
}}<noinclude>

{{repo link/doc git source
| label = OpenRadar
| repo = openradar
| branch = master
| examples =
=== No parameters ===
{{obr}}openradar source{{cbr}}
{{openradar source}}

=== File ===
{{obr}}openradar source
{{!}} path = src/org/flightgear/fgfsclient/FGFSConnection.java
{{cbr}}

{{openradar source
| path = src/org/flightgear/fgfsclient/FGFSConnection.java
}}

=== File and a branch ===
{{obr}}openradar source
{{!}} path = src/org/flightgear/fgfsclient/FGFSConnection.java
{{!}} branch = Combobox
{{cbr}}

{{openradar source
| path = src/org/flightgear/fgfsclient/FGFSConnection.java
| branch = Combobox
}}

=== File and a tag ===
{{obr}}openradar source
{{!}} path = src/org/flightgear/fgfsclient/FGFSConnection.java
{{!}} tag = 150331_AFTER_PROJECT_CLEANUP
{{cbr}}

{{openradar source
| path = src/org/flightgear/fgfsclient/FGFSConnection.java
| tag = 150331_AFTER_PROJECT_CLEANUP
}}

=== File and a commit ===
{{obr}}openradar source
{{!}} path = src/org/flightgear/fgfsclient/FGFSConnection.java
{{!}} commit = 9ffbfb
{{cbr}}

{{openradar source
| path = src/org/flightgear/fgfsclient/FGFSConnection.java
| commit = 9ffbfb
}}

{{obr}}openradar source
{{!}} path = src/org/flightgear/fgfsclient/FGFSConnection.java
{{!}} commit = 9ffbfbd629f51aa4800d9d7d0f0c8a1d11c8a79a
{{cbr}}

{{openradar source
| path = src/org/flightgear/fgfsclient/FGFSConnection.java
| commit = 9ffbfbd629f51aa4800d9d7d0f0c8a1d11c8a79a
}}

=== File and line number ===
{{obr}}openradar source
{{!}} path = data/aircraftCodes.txt
{{!}} line = 41
{{cbr}}

{{openradar source
| path = data/aircraftCodes.txt
| line = 41
}}

{{obr}}openradar source
{{!}} path = de.knewcleus.openradar/data/aircraftCodes.txt
{{!}} commit = 8d24b6
{{!}} line = 5
{{cbr}}

{{openradar source
| path = de.knewcleus.openradar/data/aircraftCodes.txt
| commit = 8d24b6
| line = 5
}}

=== Custom label given ===
{{obr}}openradar source
{{!}} path = data/aircraftCodes.txt
{{!}} text = The newest aircraft codes
{{cbr}}

{{openradar source
| path = data/aircraftCodes.txt
| text = The newest aircraft codes
}}

=== Full path ===
{{obr}}openradar source
{{!}} path = src/org/flightgear/fgfsclient/FGFSConnection.java
{{!}} commit = 9ffbfbd629f51aa4800d9d7d0f0c8a1d11c8a79a
{{!}} full = 1
{{cbr}}

{{openradar source
| path = src/org/flightgear/fgfsclient/FGFSConnection.java
| commit = 9ffbfbd629f51aa4800d9d7d0f0c8a1d11c8a79a
| full = 1
}}

=== Aliased parameters ===
This is for https://sourceforge.net/p/flightgear/openradar/ci/150331_AFTER_PROJECT_CLEANUP/tree/src/org/flightgear/fgfsclient/FGFSConnection.java.

{{obr}}openradar source
{{!}} f = src/org/flightgear/fgfsclient/FGFSConnection.java
{{!}} b = 150331_AFTER_PROJECT_CLEANUP
{{!}} full = 1
{{cbr}}.

{{openradar source
| f = src/org/flightgear/fgfsclient/FGFSConnection.java
| b = 150331_AFTER_PROJECT_CLEANUP
| full = 1
}}.

=== Numbered parameters ===
This is for https://sourceforge.net/p/flightgear/openradar/ci/150331_AFTER_PROJECT_CLEANUP/tree/src/org/flightgear/fgfsclient/FGFSConnection.java.

{{obr}}openradar source {{!}} src/org/flightgear/fgfsclient/FGFSConnection.java {{!}} b = 150331_AFTER_PROJECT_CLEANUP {{!}} full = 1 {{cbr}}.

{{openradar source | src/org/flightgear/fgfsclient/FGFSConnection.java | b = 150331_AFTER_PROJECT_CLEANUP | full = 1 }}.

}}</noinclude>

FlightGear

2025-07-15T20:03:40Z

Gijs: Cleanup, remove outdated content

{{Infobox Software
|title = FlightGear Flight Simulator
|logo = FlightGear logo.png
|logosize = 200px
|image = Boeing 777-200ER cockpit.jpg
|alt = The cockpit of the [[Boeing 777-200ER]]
|developedby = FlightGear developers & contributors
|initialrelease = July 17, 1997
|latestrelease = {{current release|full}} ({{#time: j F Y |{{current release|fulldate}}}})
|writtenin = C/C++/Nasal
|os = Windows, macOS, Linux, and FreeBSD
|platform = Cross-platform
|developmentstatus = Active (1996-present)
|type = Flight simulator
|license = [[GNU General Public License]]
|website = http://www.flightgear.org/
}}
[[File:OV10A-NASA-in-action.jpg|thumb|right|270px|NASA [[OV-10]] in FlightGear 1.0]]
'''FlightGear Flight Simulator''' (often shortened to '''FlightGear''' or '''FGFS''') is a sophisticated, free, and completely open-source flight simulator framework, created by volunteers. FlightGear is released under the terms of the [[GNU General Public License]]. FlightGear is mostly written in the C and C++ programming languages.

Increasingly detailed and realistic versions of FlightGear have been released every year since the project was started in 1996.

The latest public release is [https://www.flightgear.org/download available as a free download], with easy to install packages for a variety of operating systems including Microsoft Windows, macOS, and Linux.

== History ==
{{main article|FlightGear History}}

FlightGear development started with an online proposal in 1996, using custom 3D graphics code. Development of an [[OpenGL]] based version was spearheaded by Curtis Olson starting in 1997. Many people have contributed to the project in the years since its inception.

FlightGear incorporated other open-source resources, including the [[LaRCsim]] flight model from NASA, and freely available elevation data. The first working binaries, using OpenGL for 3D graphic code, came out in 1997. Enthusiastic development of newer versions for several years resulted in progressively more stable and advanced versions. By 2001, the team was releasing new beta versions regularly, and by 2005, the maturity of software lead to more widespread reviews, and increased popularity. 2007 marked a formal transition out of beta development with the release of version 1.0.0, ten years after FlightGear's first release in 1997.

[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]

In 2008, version 1.9.0 of FlightGear included a major change from [[PLIB]] to [[OSG]], which caused the temporarily loss of some features like 3D clouds and shadows, while newly added features, such as particles, imparted another degree of realism to the simulation.

== Software ==

The simulation engine in FlightGear is called [[SimGear]]. It is used both as an end-user application and in academic and research environments, for the development and pursuit of flight simulation ideas.

This customizability of FlightGear is illustrated by the wide range of aircraft models that are available in FlightGear, from [[:Category:Gliders|glider]]s to [[Helicopter]]s, and from [[:Category:Airliners|airliners]] to [[Military aircraft|fighter jets]]. These aircraft models have been contributed by many different people.

The FlightGear aircraft in general use one of two main flight data models [[JSBSim]] and [[YAsim]]. Currently only one terrain engine is used, TerraGear. Weather effects include 3D clouds, lighting effects, and time of day.

=== Flight Dynamics Models ===
[[Flight Dynamics Models]] (FDM) are how the flight for an aircraft is simulated in the program. FlightGear uses a variety of internally written and imported flight model projects. Any aircraft must be programmed to use one of these models. Currently FlightGear is the only flight graphical flight simulator all the FDM are used for, and UIUC and YASim were developed specifically for FlightGear.

Early version used a FDM based on [[LaRCsim]] by NASA, which was replaced with more flexible FDM.

* [[JSBSim]] - the default flight dynamics model software since 2000.
* [[YASim]] - another FDM using different calculation method. Introduced starting in 0.7.9 in 2002.
* [[UIUC]] - developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, also made use of LaRCsim. Once being widely used, it is nowadays longer included in FlightGear by default.
* FlightGear can also be setup to render using inputs from an external FDM source, such as from [[MATLAB]].
* Other custom FDM for a specific aircraft type have been written, such as for lighter than air aircraft.

=== Aircraft ===
{{Main article|Table of models}}

FlightGear started out with one aircraft included in NASA's LaRCsim, a Navion, which was replaced by a [[Cessna 172]] by 2000. UIUC as well as JSBsim development brought several more aircraft with them, as did the development of YASim which have since become the main FDM used in FG. Over 400 aircraft in more than 900 unique liveries, are available for version 2.12, although only a few are included in the base package.

[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]

=== Scenery ===
{{Main article|Scenery}}
FlightGear's [[world scenery]] project contains elevation and landclass data of the entire world. Objects -like terminals, windmills and bridges- are collected in the [[FlightGear Scenery Database|Scenery Database]].

=== Networking and multi-display ===
Several networking options allow FlightGear to communicate with other instances of FlightGear. A [[Howto:Multiplayer|multiplayer]] protocol is available for using FlightGear on a local network in a multi aircraft environment. This could be used for formation flight or [[ATC|control tower]] simulation. Multiplayer was soon expanded to allow playing over the internet. Other features include a Google maps based moving up that allows users to observe where other players are.

Several instances of FlightGear can be synchronized to allow for a multi-monitor environment. If all instances are running at the same frame rate consistently, it is possible to get good and tight synchronization between displays.

==Applications and usages==
{{Main article|Professional and educational FlightGear users}}
FlightGear has been used and is being used in a wide range of projects in academia, industry (including NASA) and home-built cockpits.

== External links ==
{{Main article|Links}}
* [https://www.flightgear.org Official website]
* {{forum link|text=Forum}}
* {{tickets|Bug tracker}}
* [https://www.flightgear.org/blog/proposal-1-0/ Original FlightGear proposal]
* {{Wikipedia|FlightGear}}

[[Category:FlightGear]]

[[ca:FlightGear]]
[[de:FlightGear]]
[[es:FlightGear]]
[[fr:FlightGear]]
[[it:FlightGear]]
[[nl:FlightGear]]
[[pl:FlightGear]]
[[pt:FlightGear]]
[[pt-br:FlightGear]]
[[ru:FlightGear]]

GitLab

2025-07-15T15:01:32Z

Gijs: Use standard heading levels

'''GitLab''' is an open source hosting infrastructure provider. Since January 2025, it hosts several [[Git]] version control repositories of [[FlightGear]] that were previously hosted on [[SourceForge]].

== Development ==

=== pre-commit ===
When opening a merge request in GitLab, a [https://pre-commit.com/ pre-commit] hook is run. Assuming <code>origin</code> is the name of the Git remote for the official repository you'd like to contribute to, you can test your changes locally with:
git diff --name-only origin/next | xargs -r pre-commit run --files
This changes/fixes your working directory so you can commit, check or reset the changes.

{{Note|The <code>pre-commit run</code> command will immediately show the changes if you pass it option <code>--show-diff-on-failure</code>.}}

Sample output of the <code>pre-commit run</code> command:

<pre>
fix end of files.........................................................Failed
- hook id: end-of-file-fixer
- exit code: 1
- files were modified by this hook

Fixing src/AIModel/AIConstants.hxx
Fixing src/ATC/ATCController.hxx

trim trailing whitespace.................................................Failed
- hook id: trailing-whitespace
- exit code: 1
- files were modified by this hook

Fixing src/Airports/groundnetwork.cxx
Fixing src/AIModel/AIAircraft.cxx
Fixing src/AIModel/AIConstants.hxx
Fixing src/ATC/ATCController.cxx
Fixing src/ATC/trafficcontrol.cxx
Fixing src/ATC/ATCController.hxx
Fixing src/AIModel/AIFlightPlanCreate.cxx
Fixing src/ATC/GroundController.cxx

codespell................................................................Failed
- hook id: codespell
- exit code: 65

src/AIModel/AIFlightPlan.hxx:53: nam ==> name
src/AIModel/AIFlightPlan.hxx:53: nam ==> name
src/ATC/ApproachController.cxx:91: exsists ==> exists
src/Airports/groundnetwork.cxx:183: backard ==> backward
src/ATC/ATCController.hxx:43: acknowlegde ==> acknowledge
src/ATC/trafficcontrol.cxx:76: existant ==> existent
src/ATC/trafficcontrol.cxx:105: paramater ==> parameter
src/ATC/trafficcontrol.cxx:213: paramater ==> parameter
src/ATC/GroundController.cxx:158: acknowlegde ==> acknowledge
src/ATC/GroundController.cxx:537: maintanance ==> maintenance

yamlfmt..............................................(no files to check)Skipped
clang-format.............................................................Failed
- hook id: clang-format
- files were modified by this hook
reuse lint-file..........................................................Failed
- hook id: reuse-lint-file
- exit code: 1

src/ATC/ApproachController.cxx: no license identifier
src/ATC/trafficcontrol.hxx: no license identifier
src/ATC/TowerController.cxx: no license identifier
src/ATC/trafficcontrol.hxx: no copyright notice
src/ATC/trafficcontrol.cxx: no license identifier
test_suite/unit_tests/AI/TestSuite.cxx: no license identifier
src/ATC/GroundController.cxx: no license identifier
src/ATC/atc_mgr.cxx: no license identifier
src/ATC/atc_mgr.cxx: no copyright notice
</pre>

==References==

*[https://gitlab.com/flightgear FlightGear GitLab website]
*{{wikipedia |Gitlab |GitLab wikipedia article}}

[[Category:Hosting infrastructure]]

Howto:Install scenery

2025-07-11T10:41:42Z

Gijs: Major revision, update, cleanup

{{installing}}

A default installation of [[FlightGear]] comes with a limited set of [[scenery]] to keep initial download sizes small. It includes the region around the featured airport for each release (Iceland since FlightGear 2020.1), and the area containing the airport used by the [[Cessna 172P]] tutorials (Hawaii, including PHTO). When [[TerraSync]] is enabled (by default as of FlightGear 2024.1.2), additional scenery is automatically downloaded, installed and updated for whichever location around the globe a user visits.

This article explains '''how to manually install scenery''' for people with limited internet access, and how to install [[Howto:Install scenery#Custom scenery|custom sceneries]] that are not available through TerraSync. If you locate yourself at an airport and see nothing but water, you probably did not install that scenery area (correctly).

== Scenery types ==
There are four scenery types, in increasing level of detail:

; World scenery 2
: Reasonable level of detail global scenery, with objects such as landmarks and airport buildings. Has not been updated since 2013.
; TerraSync scenery
: World scenery 2 terrain with constantly updated scenery objects added by fellow FlightGear users to the [[Scenery Objects Database|scenery objects database]], and worldwide [[OSM2City 1st Worldbuild|OpenStreetMap-based buildings]]. Most of the terrain and airport layouts have not been updated since 2013.
; [[World Scenery 3.0|World scenery 3]]
: Experimental scenery with updated terrain, airports and objects.
; Custom scenery
: Non-official scenery covering all the way from small areas to very large areas, often with a high level of detail and up-to-date terrain and airports.

<gallery mode="packed">
File:SOTM-Sept17.jpg|Hawaii scenery - "weeping wall" waterfalls at Mount Waialeale on the island of Kauai, near PHLI
File:SOTM_2019-06_Ice_and_fire_by_vnts.jpg|Sicily scenery - the [[volcanos|volcano]] Etna snowcapped in winter with a low level eruption, near LICC
File:Bell_412_in_Iceland_(Flightgear_2019.x).jpg|Iceland scenery - having [[:Category:Screenshots_of_overlays|overlays]] enabled shows extremely high 3d detail like small rocks, plants, or individual grass blades
File:SOTM-Mar19.jpg|Madrid scenery with [[Areas_populated_with_osm2city_scenery|OSM2City output]] for Spain
</gallery>

== Obtaining scenery ==
=== World scenery 2 ===

[[File:Worldscenery-text.jpg|thumb|World scenery tiles]]

World scenery 2 is available in tiles of 1 by 1 degree. To find an airport's coordinates and corresponding tile:

# Go to the Wikipedia page for the airport in question (e.g., {{wikipedia|Honolulu International Airport}}, PHNL).
# Find the co-ordinates (often at the top or right and side, marked with a small globe). For PHNL these are 21 N 157 W.
# Round the coordinates to their nearest multiple of 10. Round up for Southern and Western hemisphere coordinates, and round down for Northern and Eastern coordinates, as illustrated by the image. PHNL yields w160n20, while 21 N 157 E would yield e150n20. clarifies this rule.

Scenery tiles can be downloaded from [https://www.flightgear.org/download/mirror/ these mirrors]. On most of them the latest scenery can be found under <tt>/Scenery-v2.12</tt>.

=== TerraSync scenery ===
{{Main article|TerraSync}}

The [[TerraSync]] scenery is automatically downloaded and synchronized as needed while FlightGear is running when the built in TerraSync utility is enabled. As an alternative, especially suited for users with limited internet speeds, scenery can be prefetched before starting a flight via the [[TerraMaster]] tool.

==== Downloading with TerraMaster ====

{{Main article|TerraMaster}}

[[File:TerraMaster r32 - Global view.png|thumb|TerraSync scenery in TerraMaster]]

TerraMaster is a stand alone scenery manager that can download and synchronize TerraSync scenery. It also makes it easier to maintain and get a good overview of downloaded TerraSync scenery. It is a cross platform graphical application written in Java.

TerraMaster allows the FlightGear user to manage scenery tiles easily, selecting which tiles to download, synchronize or delete, and viewing the downloaded/not yet downloaded tiles at a glance. TerraMaster is highly recommended not only for managing scenery tiles easily especially if you are downloading and managing scenery from a computer that does not have FlightGear installed. The downloaded tiles are put into a folder which can then be loaded by FlightGear.

=== World scenery 3 ===
{{Main article|World Scenery 3.0}}

=== Custom scenery ===

Custom scenery is available for certain specific areas. They are distributed separately either due to being only part of a single landmass that has not been re-built completely, being work-in-progress, waiting to be integrated to Terrasync, their license, or because their level of detail is not suitable for low-end machines.

* [[Suggested Airports/Scenery]] for a list of custom scenery projects and an update on state of well developed areas.
* [[Project3000#Download_the_software_and_shared_models|Project 3000]] for buildings and objects for 4000+ airports.
* [[Earthview#Installing_and_using_customized_textures|Earthview high resolution]] texture packs. Earthview is Flightgear's orbital renderer capable of handling large view distances without numerical problems. People using high altitude and space craft should select the texture pack that their GPU can handle - [[Earthview#Requirements|depends]] mainly on GPU memory (VRAM).

<gallery mode="packed">
File:Asia.jpg|[[Earthview]] orbital renderer at high sun - with high resolution texture packs installed.
File:SOTM_2019-04_Space_Sauna_by_GinGin.jpg|Earthview orbital renderer at low sun showing light from cities. The [[Space_Shuttle|Space Shuttle]] shows the glow from the heat of hypersonic re-entry.
</gallery>

== Installing world and custom scenery ==

Always install scenery outside the <code>[[$FG_ROOT]]</code> directory. See [[#Technical details]] below for an explanation.

{{caution|'''Do not mix scenery''' types in the '''same directory'''. It may cause problems like custom scenery being overwritten by the TerraSync or TerraMaster utilities, TerraMaster getting locked etc.}}

=== GNU/Linux ===
If you are under a Linux operation system and you are not using a graphical interface to extract the tar archive, you can use one of the two following set of commands in a shell terminal.

<syntaxhighlight lang="shell">
cd SceneryDirectory
tar -xvzf input_file.tgz
</syntaxhighlight>

or

<syntaxhighlight lang="shell">
tar -xvzf 'input_file.tgz' -C SceneryDirectory
</syntaxhighlight>

<code>input_file.tgz</code> should be substituted with the filename of the archive to be extracted (the filename should be completed with the full pathname or any other valid method so that the shell could find the correct archive).

=== Windows ===

Simply unpack the downloaded scenery into a directory of choice, using software like [http://www.winzip.com/ Winzip] or [http://www.7-zip.org 7-zip]. Once done, append this directory to <code>[[$FG_SCENERY]]</code> (in the launcher, this can be done under Add-ons > Additional scenery folders).

=== macOS ===

Unpack the .tgz file either by double-clicking it and moving the resulting <code>wXXXnXX</code> folder to the Scenery folder described in the next line, or on the command line:

<syntaxhighlight lang="shell">
tar -xvzf 'input_file.tgz' -C /Applications/FlightGear.app/Contents/Resources/data/Scenery
</syntaxhighlight>

== Technical details ==
=== Scenery lookup and $FG_SCENERY ===

FlightGear determines what scenery to use by looking at the [[Environment variables|environment variable]] (setting) <code>[[$FG SCENERY]]</code>. There can be more than one scenery path in the variable, for example one path to to TerraSync scenery and one path to custom scenery. Scenery can be overlapping and a tile will be loaded from the first path in <code>$FG SCENERY</code> from which it is available.

Should the paths in <code>$FG_SCENERY</code> not be valid, FlightGear falls back to <code>[[$FG ROOT]]/Scenery</code>.

=== Directories and configuring $FG_SCENERY ===

Mixing scenery types is almost universally a bad idea, and is unsupported. Also note that the scenery packaged with the base package/windows installer may not be the latest scenery.

For this reason it is better to extract downloaded scenery files into a new folder, which we for the sake of this exercise will call <code>$FOOBAR/Scenery</code>.
In this directory, create two subdirectories: <code>/Objects</code> and <code>/Terrain</code>. You should untar individual files into the <code>/Terrain</code> folder.

Then you should set up $FG_SCENERY to use the new path:

* In the [[Qt launcher]]:
*: Add the $FOOBAR/Scenery folder to Add-ons > Additional scenery folders.
* On POSIX Clients
*: <code>set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY</code>
* Via a command line option
*: <code>--fg-scenery="$FOOBAR/Scenery"</code>

=== Directory structure ===
==== Terrain ====

The Scenery directory will show the following (scenery is shown for completeness and for easy reference to above):

<tt>
* Scenery/
** Terrain/
*** w130n30/
** Objects/
*** w130n30/</tt>

If you download a scenery module called <code>w90n40.tgz</code> and extract it in <code>Scenery</code>, the result will resemble something like the following:

<tt>
* Scenery/
** Terrain/
*** w09n40/
*** w130n30/
** Objects/
*** w09n40/
*** w130n30/</tt>

Note that the directory structure is already present in the tar archive, starting from the Scenery directory. Note that you have to extract the tar archive in the Scenery directory, not in the <code>$FG_ROOT</code> directory, because the Scenery directory is not present in the archive.

==== Objects ====

Objects and models can be found at the [[FlightGear Scenery Object Database]].

These objects are included in each scenery release, but as the object database is more frequently updated than the terrain, one may want to occasionally update the <code>Object</code> subdirectory from the scenery objects database between scenery releases.

Another option is to download or update the scenery on-demand by using the built in TerraSync utility described above.

Objects are really part of the scenery and can be found in the <code>Scenery</code> directory under <code>$FG ROOT</code>.

<tt>
* Scenery/
** Objects/
*** w130n30/</tt>

Any objects should be installed under the <code>Scenery/Objects</code> directory.

==== Models ====

Replaces the former <code>$FG_ROOT/Models</code>; stores all the shared objects.

<tt>
* Scenery/
** Models/
*** Airport/</tt>

==== Airports ====

{{Main article|About Scenery/Airports}}

As of FlightGear 2.4.0, this directory is used to extract airport data (like runway usage and parking spots) from.

The directory tree might look somewhat overwhelming, but it simply follows the <code>Airports/[I]/[C]/[A]/</code> style.
<tt>
* Scenery/
** Airports/
*** K/
**** S/
***** F/
</tt>

== Video tutorials (2020.x) ==

{{#ev:youtube|TNN_AZhaHPU|480px||Scenery installation for Flightgear 2020.x by Parnikkapore. Note this is recorded on a non-gaming laptop, and certain settings are not turned up very high.}}
{{#ev:youtube|YxWV4wk_dHw|480px||Terramaster tutorial for Flightgear by FGUK - 2017 but still valid in 2020.}}

== Related content ==

* [[Scenery FAQ]]

[[Category:Scenery]]

[[ar:Howto:Install_scenery]]
[[de:Howto:Install_scenery]]
[[es:Instalación de escenarios]]
[[fr:Installer une scène]]
[[it:Come fare:Installare scenari]]
[[nl:Scenery installeren]]
[[PL:Instalowanie scenerii]]
[[pt:Instalando Cenário]]

Virtual airlines

2025-07-03T09:14:32Z

Gijs: Remove airlines/alliances that have been defunct for years

A '''virtual airline''' (VA) is a dedicated hobby organization that uses flight simulation to model the operations of an airline. Virtual airlines generally have a presence on the internet, similar to a real airline. There are over 100 virtual airlines of significance currently active in the internet (supporting a number of flightsims), with thousands of participants involved at any one time each using different simulator platforms.

== Purpose ==
Virtual airlines were started to give a sense of purpose to activities conducted within a flight simulator. This basic premise has evolved over time, along with available technology, to provide increasing levels of immersion but always with the same core purpose. When combined with increasingly powerful personal computers, advancing flight simulation software, and communications networks, virtual airlines are often able to provide compelling, realistic, experiences similar to operations inside a real airline. Virtual airlines also provide an avenue for members to gain access to additional content, such as aircraft and scenery, for use with their simulator. The appeal varies; for younger members, virtual airlines provide a sandbox environment where they can experience the corporate environment of commercial business in the airline industry, without the risk of financial loss. These organizations also provide an outlet for those who are interested in aviation but unable to fly themselves in real life due to financial, health, or other reasons.
Most of all, its one step closer to enthusiasts feeling more involved in an airline environment and share their interests with others.
Virtual Airlines also benefit the flight simulator community by providing valuable services such as ATC, events, and general help and knowledge.

== Common elements ==
There are several elements that are common across many virtual airlines:
* A website as the focal point of the community
* Internet forum where discussion and social interaction can occur
* Customized livery that users can download together with aircraft and install in their flight simulator
* Route schedules for members to fly in their simulators
* Multiplayer events, often on a game network such as VATSIM or IVAO
* Less common elements include:
** An Online database for recording and reporting flights and membership statistics
** Dedicated game server hosting to provide private areas for members to complete flights
** Award, rank and recognition systems
** Voice over Internet Protocol servers for members to communicate freely by voice

== Virtual airlines ==
{{Virtual airline summary
|name = Charter Aviation
|established = November 2013
|logo =
|status = Active
|has-atc = Only if you want
|callsign = CHTxxxx
|history = Charter Aviation is a virtual charter service airline. Any aircraft, any route, anytime. Any aircraft you can sim, any route you want to take it, anytime you want to fly. We're the guys who get the aircraft where they need to be.
|fleet =
* Any and all aircraft
|main-hub = EGLL
|hubs =
* CYEG - Edmonton
* CYOW - Ottawa
* CYVR - Vancouver
* EDDB - Berlin
* EGLL - Heathrow
* EIDW - Dublin
* FAJS - Oliver Reginald Tambo
* KBOS - Boston Logan
* KSFO - San Francisco
* LFPO - Paris Orly
* LYBE - Belgrade Nikola Tesla
* PHNL - Honolulu
* RJAN - Niijima
* SBGR - Guarulhos Sao Paulo Brazil
* UUDD - Domodedovo Moscow
* YSSY - Sydney
|map =
|website = http://www.charterva.com
|forum =
|registration = http://www.charterva.com
}}

{{Virtual airline summary
|name = Voxy Virtual Airlines
|established = Sep 2011
|logo = Voxy_va.png
|status = Active
|callsign = VOXxxxx (x = number)
|history =
Re-branded to Dravion Airlines and focused on regional flights in Ukraine (Aug 2014).

Re-branded again in to Voxy Airlines and it primarily serves as and flies under the name of other airlines it has contracted (sep 2018).

Voxy Airlines primarily paid to operate and maintain aircraft used on flights that are scheduled, marketed, and priced by a partner mainline.
|fleet =
* Airbus A350-900XWB
* Airbus A300-600ST
* Tupolev Tu-134B
* Ilyushin Il-76MD
|main-hub = UKKE
}}

{{Virtual airline summary
|name = Worldwide Airways Virtual
|established = September 2016
|logo = Worldwide Airways logo.png
|status = Active and Looking For Pilots
|callsign = WWAxxxx
|history = Worldwide Airways is an international Virtual Airline offering realistic, professional and exciting flights! Fly over the world, to a large selection of beautiful destinations; with modern aircraft and of course, fly online for more fun, and professionalism!
|fleet =
*Boeing 747-8i
*Boeing 757-200
*Boeing 777-300ER
*Airbus A318
*Airbus A320
*Airbus A330-303
*Airbus A340-313X
*Airbus A350-900XWB
*Airbus A380-800
*Concorde
|main-hub = KSFO
|hubs = LFPG; KSFO
|website = https://worldcargoairwaysvirtual.jimdo.com/
|forum =
}}

{{Virtual airline summary|name=Air Odisha|main-hub=Bhubaneswar|established=January 2025|status=Looking for pilots|hubs=Delhi, Mumbai, Bhubaneswar|fleet=A350-900, A350-1000, 787-10, 787-9, 737-700, ATR 72-600, A320neo|callsign=Odisha|website=https://air-odisha.mystrikingly.com/|logo=[[File:Screenshot 2025-03-23 193504.png|thumb|Logo of Air Odisha]]}}

== Virtual Air Forces ==
{{Virtual airline summary
|name = The European Air Force
|established = June 2011
|logo = Eaf-bl11.png
|status = Active
|has-atc = Has ATC
|callsign = EAFxxx, LCG-XXX
|fleet =
* F-16CJ
* F/A-18
* C-130
* E-3B
|main-hub = [[Ramstein Air Base]] (ETAR)
|hubs =
|map =
|website = https://www.facebook.com/groups/flyeaf/
|forum = On our group.
}}

{{Virtual airforce summary
|name = Operation Red Flag (OPRF)
|established = November 21st, 2015
|logo = OPRF.png
|niche = Paramilitary
|status = Active
|history = Founded as KSUU Crew over friendly dogfights in the F-14B over the skies of Travis Air Force Base, OPRF slowly took over training and patrol duties in the south-western United States on behalf of the USAF. OPRF has fought all over the world gaining prestige and recognition, from the Alps to the Himalayas, from North Korea to Georgia to Alaska, in an ever-expanding fleet of fighters and support aircraft. Member pilots get to learn the knowledge, skills and tactics that define the fighter pilot and are engaged in monthly major events and regular training.
|has-atc = No
|callsign = {Your callsign}; OPFORxx; ORFxxxx
|fleet =
Fighters:
* F-14A/B
* F-15C/D
* F-16 (all versions)
* M2000-5
* Saab 37 Viggen (all versions)
* MiG-21-bis
* MiG-23MLD
Attack/Bombers:
* A-10
* B-1B
* Jaguar GR.1
Tankers/Transport/Spec Ops:
* KC-137R and variants
* KC-10A
* KDC-10-40
* KMD-11
* A330 MRTT variants (Voyager KC2/KC3, KC-30A)
* C-130J
* SR-71 and variants
* MQ-9 (all versions)
Helicopters:
* CH-53E
* SH-60J and UH-60J
* UH-1 and variants
|main-base = [[Nellis Air Force Base]] (KLSV), [[Aviano Air Base]] (LIPA)
|bases = See: [http://opredflag.com/pages/log_map here] for reference
|map =
|website = http://opredflag.com/
https://discord.gg/SmGFnJN
|forum = http://opredflag.com/forums
|fgforum = https://forum.flightgear.org/viewtopic.php?f=10&t=28057
}}

{{Virtual airline summary
|name = Team Militare "36° Stormo virtuale"
|established = September 2012
|logo =
|status = Currently Inactive
|has-atc = No.
|callsign = {Your callsign}, FGIT-xx
|fleet =
* Panavia Tornado
* F-16/F-16CJ
* Mirage 2000
* EF2000/Eurofighter Typhoon
* F-14B
* AC-130
|main-hub = [[Base aerea di Gioia del Colle]] (LIBV)
|hubs = LIBN, LICZ, LIRA, LIPS, LIPI.
|map =
|website = [http://flightgearitalia.forumcommunity.net/?f=8269638 Team Militare]
|forum = On our group.
}}

{{Virtual airforce summary|name=First Air Force|logo=1stAF.png|main-base=[[Tyndall Air Force Base]] (KPAM)|established=June 6th 2024|status=Active|fleet=Fighters : F-35 A, F-15 C&D, F-16 C

UAV : RQ4-B, MQ-9

Tanker: KC135, KC130|has-atc=Yes, 1stAF (Openradar)|website=https://1staf.org
https://discord.gg/firstairforce|history=The First Air Force in FlightGear was established as a virtual group inspired by the real-world First Air Force. Created to emulate its mission and operations, the group became a hub for aviation enthusiasts, achieving prominence as one of the most active and dedicated communities during the summer of 2024.|bases=[[Tyndall Air Force Base]] (KPAM)|callsign={Your callsign} , CONRXX, 325thFW, REDFOR|forum=https://1staf.org/forums}}

[[Category:Virtual airlines]]

File:Screenshot 2025-03-23 193504.png

2025-05-12T08:00:58Z

Gijs: Gijs moved page File:Screenshot 2025-03-23 193504.png to File:Air Odisha logo.png: More descriptive file name

#REDIRECT [[File:Air Odisha logo.png]]

File:Air Odisha logo.png

2025-05-12T08:00:58Z

Gijs: Gijs moved page File:Screenshot 2025-03-23 193504.png to File:Air Odisha logo.png: More descriptive file name

=={{int:filedesc}}==
{{Information
|description={{en|1=This is the logo of the Bhubaneswar-based virtual airline Air Odisha}}
|date=2025-05-11
|source={{own}}
|author=[[User:AirOdishaCEO|AirOdishaCEO]]
|permission=
|other versions=
}}

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

Template:Repo link

2025-05-07T09:06:25Z

Gijs: Default GitLab branches to next

<noinclude>{{caution|This template, via its [[Template:repo link/doc related|subtemplates]], is used by many pages. Therefore modifications will propagate throughout the FlightGear wiki and have a large effect. Changes should be carefully tested on a [[Template:repo link/sandbox|/sandbox]] subpage or as a user subpage before being implemented here.}}</noinclude>{{#if: {{{cmd|}}}
| {{strip whitespace|{{{cmd}}}}} <nowiki></nowiki>{{#if: {{{opt|}}} | {{{opt}}} <nowiki></nowiki>}}
}}{{#ifeq: {{{full|}}} | 1 | |[}}{{#switch: {{{site|{{project infrastructure|abbrev}}}}}
| s
| sf
| sourceforge = {{{protocol|https}}}://{{#switch: {{{type|git web}}} 
| git | svn = {{#if: {{{login|}}} | {{{login}}}@}}
}}{{#switch: {{{type|git web}}}  | git web = sourceforge.net
| git = git.code.sf.net
| svn web = sourceforge.net
| svn = svn.code.sf.net
}}/{{#if: {{{user|}}} 
| u/{{{user}}}
| p/{{{proj|flightgear}}}
}}/{{{repo|flightgear}}}/{{#switch: {{{type|git web}}} 
| git
| git web =
{{#switch: {{{type|git web}}}
| git = 
| git web = {{#switch: {{{view|}}}
| rss =
| #default =
ci/{{{commit|{{#if: {{{tag|}}}
| {{{tag}}}
| {{{branch|next}}}
}}}}}/
}}{{#switch: {{{view|}}} 
| tree = tree/
| log = log/?path{{=}}
| rss = feed/
| commit =
| #default ={{#if: {{{path|}}}
| tree/
| {{#if: {{{commit|}}}
|
| tree/
}}
}}
}}{{#switch: {{{view|}}}
| rss =
| commit =
| #default ={{#if: {{{path|}}} 
| {{{path|}}}{{#if: {{{line|}}} | #l{{{line}}} }}
}}
}}{{#ifeq: {{{view|}}} | raw
| ?format=raw
}}
}} {{#if: {{{text|}}}
| {{{text}}}
| {{#ifeq: {{{full|}}} | 1 
| 
| {{#if: {{{pre|}}}
| {{{pre}}}
| {{#if: {{{simplepath|}}}
| 
| {{{user|{{{proj|flightgear}}}}}}/{{{repo|flightgear}}}{{#ifeq: {{{view|}}} | rss | 
| /{{{commit|{{{tag|{{{branch|next}}}}}}}}}
}}
}}
}}{{#switch: {{{view|tree}}}
| rss =
| #default =
{{#if: {{{path|}}} 
| {{#if: {{{simplepath|}}} | | /}}{{{path}}}
}}{{#if: {{{line|}}} | #l{{{line}}}}}
}}{{#if: {{{pre|}}} 
| {{#if: {{{commit|}}}
|<nowiki></nowiki> (commit {{{commit}}})
| {{#if: {{{tag|}}}
|<nowiki></nowiki> (tag {{{tag}}})
| {{#if: {{{branch|}}}
|<nowiki></nowiki> (branch {{{branch}}})
}}
}}
}}
}}{{#switch: {{{view|}}} 
| tree =
| log = <nowiki></nowiki> log view
| commit = <nowiki></nowiki> commit view
| rss = <nowiki></nowiki> RSS feed
| #default ={{#if: {{{path|}}}
|
| {{#if: {{{commit|}}}
|<nowiki></nowiki> commit view
}}
}}
}}
}}
}}
| svn
| svn web =
{{#switch: {{{type|}}}
| svn = 
| svn web = {{#switch: {{{view|}}}
| rss =
| #default =
{{{commit|HEAD}}}/{{#switch: {{{view|}}} 
| tree = tree/
| log = log/?path{{=}}
| rss =
| commit =
| #default ={{#if: {{{tag|{{{branch|{{{path|}}}}}}}}}
| tree/
| {{#if: {{{commit|}}}
|
| tree/
}}
}}
}}
}}
}}{{#switch: {{{view|}}}
| commit =
| rss = feed/
| #default ={{#switch: {{{type|}}}
| svn = {{{tag|{{{branch|trunk}}}}}}{{#if: {{{path|}}} | /{{{path}}} }}{{#if: {{{commit|}}} | @r{{{commit}}} }}
| svn web = {{#if: {{{tag|{{{branch|{{{path|}}}}}}}}} 
| {{{tag|{{{branch|trunk}}}}}}{{#if: {{{path|}}}
| /{{{path}}}{{#if: {{{line|}}} | #l{{{line}}} }}
}}
| {{#if: {{{commit|}}} | | trunk}}
}}
}}
}} {{#if: {{{text|}}}
| {{{text}}}
| {{#ifeq: {{{full|}}} | 1 
| 
| {{#if: {{{pre|}}}
| {{{pre}}}
| {{#if: {{{simplepath|}}}
| 
| {{{user|{{{proj|flightgear}}}}}}/{{{repo|flightgear}}}{{#switch: {{{view|}}}
| rss =
| commit =
| #default = {{#if: {{{tag|{{{branch|{{{path|}}}}}}}}}
| /{{{tag|{{{branch|trunk}}}}}}
}}
}}
}}
}}{{#switch: {{{view|}}}
| rss =
| #default =
{{#if: {{{path|}}} 
| {{#if: {{{simplepath|}}} | | /}}{{{path}}}
}}{{#if: {{{line|}}} | #l{{{line}}}}}{{#if: {{{commit|}}} | @r{{{commit}}}}} 
}}{{#switch: {{{view|}}} 
| tree =
| log = <nowiki></nowiki> log view
| commit = <nowiki></nowiki> commit view
| rss = <nowiki></nowiki> RSS feed
| #default ={{#if: {{{tag|{{{branch|{{{path|}}}}}}}}}
|
| {{#if: {{{commit|}}}
|<nowiki></nowiki> commit view
}}
}}
}}
}}
}}
}}
| gh
| gith
| github = {{{protocol|https}}}://github.com{{#if: {{{user|{{{proj|}}}}}} | {{#if: {{{repo|}}}
| {{#if: {{{user|}}} 
| /{{{user}}}
| {{#if: {{{proj|}}} | /{{{proj|}}}}}
}}{{#if: {{{repo|}}} | /{{{repo|}}}}}{{#switch: {{{type|git web}}} 
| git = .git
| git web = {{#if: {{{view|{{{commit|{{{tag|{{{branch|{{{path|}}}}}}}}}}}}}}}
| /{{{view|tree}}}/{{{commit|{{{tag|{{{branch|master}}}}}}}}}{{#if: {{{path|}}} | /{{{path}}}}}{{#if: {{{line|}}} | #L{{{line}}} }} 
}}
| zip = /archive/{{{commit|{{{tag|{{{branch|master}}}}}}}}}.zip
| tracker = /issues{{#if: {{{number|}}} | /{{{number}}}}}
| wiki = /wiki{{#if: {{{path|}}} | /{{{path}}}}}
}}
}}}} {{#if: {{{text|}}}
| {{{text}}}
| {{#ifeq: {{{full|}}} | 1
| 
| {{#if: {{{user|{{{proj|}}}}}}
| {{#if: {{{repo|}}}
| {{#if: {{{pre|}}}
| {{{pre}}}
| {{#if: {{{simplepath|}}}
| 
| github/{{{user|{{{proj|}}}}}}/{{{repo|}}}{{#if: {{{view|{{{commit|{{{tag|{{{branch|}}}}}}}}}}}}
| /{{{commit|{{{tag|{{{branch|master}}}}}}}}}
}}
}}
}}{{#switch: {{{type|git web}}} 
| git web =
{{#if: {{{path|}}} | /{{{path}}}}}{{#if: {{{line|}}} | #L{{{line}}}}} {{#switch: {{{view|tree}}} 
| blob =
| blame = <nowiki></nowiki> blame view
| commit = <nowiki></nowiki> commit view
| commits = <nowiki></nowiki> history view
| raw = <nowiki></nowiki> raw view
| tree =
}}
| zip = <nowiki></nowiki> zip file
}}
}}
| GitHub website
}}
}}
}}
| gl
| gitl
| gitlab = {{{protocol|https}}}://gitlab.com{{#if: {{{user|{{{proj|}}}}}} | {{#if: {{{repo|}}}
| {{#if: {{{user|}}} 
| /{{{user}}}
| /{{{proj|}}}
}}{{#if: {{{repo|}}} | /{{{repo|}}}}}{{#switch: {{{type|git web}}} 
| git = .git
| git web = {{#if: {{{view|{{{commit|{{{tag|{{{branch|{{{path|}}}}}}}}}}}}}}}
| /{{{view|blob}}}/{{{commit|{{{tag|{{{branch|next}}}}}}}}}{{#if: {{{path|}}} | /{{{path}}}}}{{#if: {{{line|}}} | #L{{{line}}} }} 
}}
| zip = /repository/archive.zip{{#if: {{{commit|{{{tag|{{{branch|next}}}}}}}}}
| ?ref={{{commit|{{{tag|{{{branch|next}}}}}}}}}
}}
}}
}}}} {{#if: {{{text|}}}
| {{{text}}}
| {{#ifeq: {{{full|}}} | 1
| 
| {{#if: {{{user|{{{proj|}}}}}}
| {{#if: {{{repo|}}}
| {{#if: {{{pre|}}}
| {{{pre}}}
| {{#if: {{{simplepath|}}}
| 
| gitlab/{{{user|{{{proj|}}}}}}/{{{repo|}}}/{{{commit|{{{tag|{{{branch|next}}}}}}}}}
}}
}}{{#switch: {{{type|git web}}} 
| git web =
{{#if: {{{path|}}} | /{{{path}}}}}{{#if: {{{line|}}} | #L{{{line}}}}} {{#switch: {{{view|tree}}} 
| tree =
}}
| zip = <nowiki></nowiki> zip file
}}
}}
| GitLab website
}}
}}
}}
| g
| go
| gito
| gitorious = {{{protocol|https}}}://gitorious.org{{#if: {{{proj|}}} | {{#if: {{{repo|}}}
| {{#if: {{{proj|}}} | /{{{proj}}}}}{{#if: {{{repo|}}} | /{{{repo}}}}}{{#switch: {{{type|git web}}} 
| git = .git
| git web = ?p={{{proj|fg}}}:{{{repo|flightgear}}}.git;a={{#if: {{{view|}}} 
| {{#switch: {{{view|}}}
| raw = blob_plain
| #default = {{{view|summary}}}
}}
| {{#if: {{{path|}}} | blob
| {{#if: {{{commit|{{{mr|}}}}}}
| commit
| {{#if: {{{branch|{{{tag|}}}}}}
| shortlog
| summary
}}
}}
}}
}}{{#if: {{{path|}}} | {{;}}f={{{path|}}}}}{{#if: {{{commit|{{{tag|{{{branch|{{{mr|}}}}}}}}}}}} 
| {{#if: {{{view|}}}
| {{#switch: {{{view|}}}
| blob | raw | tree = {{;}}hb=
| #default = {{;}}h=
}}
| {{#if: {{{path|}}}
| {{;}}hb=
| {{;}}h=
}}
}}
}}{{#if: {{{mr|}}}
| refs/merge-requests/{{{mr}}} 
| {{#if: {{{commit|}}}
| {{{commit}}} 
| {{#if: {{{tag|}}}
| refs/tags/{{{tag}}}
| {{#if: {{{branch|}}}
| refs/heads/{{{branch}}}
}}
}}
}}
}}{{#if: {{{line|}}} |#l{{{line}}}}} 
}}
}}}} {{#if: {{{text|}}}
| {{{text}}}
| {{#ifeq: {{{full|}}} | 1
| 
| {{#if: {{{proj|}}}
| {{#if: {{{repo|}}}
| {{#if: {{{pre|}}}
| {{{pre}}}
| {{#if: {{{simplepath|}}}
| 
| gitorious/{{{proj|}}}/{{{repo|}}}/{{#if: {{{mr|}}}
| merge-requests/{{{mr}}}
| {{{commit|{{{tag|{{{branch|HEAD}}}}}}}}}
}}
}}
}}{{#if: {{{path|}}} | /{{{path}}}}}{{#if: {{{line|}}} | #l{{{line}}}}} 
}}
| Gitorious website
}}
}}
}}
| #default = {{{protocol|https}}}://{{#if: {{{login|}}} | {{{login}}}@}}{{{site|flightgear.org}}}/{{#if: {{{user|}}} 
| {{{user}}}
| {{{proj|}}}
}}{{#if: {{{repo|}}} | /{{{repo}}} }}{{#switch: {{{type|git web}}} 
| git =
| git web = <big style="color:red">Generic git web interface is not implemented for {{tl|repo link}}</big>
| svn = /{{{branch|trunk}}}{{#if: {{{path|}}} | /{{{path}}}}}
| svn web = <big style="color:red">Generic svn web interface is not implemented for {{tl|repo link}}</big>
}}
}}{{#ifeq: {{{full|}}} | 1 | |]}}{{#if: {{{post|}}} | <nowiki></nowiki> {{{post}}}}}<noinclude>

{{repo link/doc}}

</noinclude>

Instrumentation

2025-05-07T09:05:09Z

Gijs: Update source links to GitLab

FlightGear's built-in '''Instrumentation system''' simulates basic instruments used in many aircraft and provide their output as [[Property|Properties]] to be used e.g. for [[Howto:Animate models|animating]] 3D instruments or [[Canvas]] instruments.

This article is meant to provide an overview over the instrumentation modules available and their configuration.

=== General configuration ===
The instrumentation modules to be available to an aircraft can be selected by the aircraft developer using an instrumentation XML configuration file. This file is called from the [[Aircraft-set.xml]]:<syntaxhighlight lang="xml">
<sim>
<instrumentation>
<path>Systems/my-aircraft-instrumentation.xml</path>
</instrumentation>
</sim>
</syntaxhighlight>A generic configuration file to be copied and customised can be found in Aircraft/Generic/generic-instrumentation.xml.

===== Common Elements =====
Instrument Root Path: typically '''/instrumentation/name[number]/''' e.g. '''/instrumentation/adf[1]/''' for the second ADF.

Electric Power Path (where applicable): typically '''/systems/electrical/outputs/name[number]''' e.g. '''/systems/electrical/outputs/comm[0]''' for the first comm radio.
{| class="wikitable"
|name
|typically used for the instrument's root path and, where applicable, electric power path
|-
|number
|used to differentiate between multiple objects using the same name.
|}
All instruments that inherit '''AbstractInstrument''' additionally accept the following config settings:
{| class="wikitable"
|power-supply
|custom property to be used as the electric power path
|-
|minimum-supply-volts
|minimum electric voltage at which the instrument works
|}

=== Instrument Modules ===

====[[ADF|ADF (Automatic Direction Finder)]]====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/adf.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/adf.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
This instrument simulates an [[ADF|Automatic Direction Finder]] used for navigating using [[NDB|Non-Directional Beacons]].

'''Configuration'''<syntaxhighlight lang="xml">
<adf>
<name>adf</name>
<number>0</number>
</adf>
</syntaxhighlight>

====[[Airspeed|Airspeed Indicator]]====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/airspeed_indicator.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/airspeed_indicator.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<airspeed-indicator>
<name>airspeed-indicator</name>
<number>0</number>
<total-pressure>/systems/pitot/total-pressure-inhg</total-pressure>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<has-overspeed-indicator>0</has-overspeed-indicator>
<pressure-alt-source>/instrumentation/altimeter/pressure-alt-ft</pressure-alt-source>
<ias-limit>248.0</ias-limit>
<mach-limit>0.48</mach-limit>
<alt-threshold>13200</alt-threshold>
</airspeed-indicator>
</syntaxhighlight>

*Total Pressure: see [[FGproperties/Systems/Pitot]]
*Static Pressure: see [[FGproperties/Systems/static]]
*see also: {{Repo link|repo=fgdata|pre=$FG_ROOT|path=Docs/README.airspeed-indicator}}

====[[Altimeter]]====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/altimeter.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/altimeter}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<altimeter>
<name>altimeter</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
<quantum>0</quantum>
<tau>0</tau>
</altimeter>
</syntaxhighlight>

*Static Pressure: see [[FGproperties/Systems/static]]
*Quantum: TODO
* Tau: TODO

====[[Attitude indicator|Attitude Indicator (suction-powered)]]====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/attitude_indicator.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/attitude_indicator.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator>
<name>attitude-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.5</minimum-vacuum>
<limits>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</limits>
<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</attitude-indicator>
</syntaxhighlight>

* Note, the <code><minimum-vacuum></code>, <code><gyro></code> and <code><limits></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.
*Suction: see [[Aircraft systems#Vacuum]]

====Attitude Indicator (Electric)====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/attitude_indicator_electric.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/attitude_indicator_electric.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<attitude-indicator-electric>
<name>attitude-indicator</name>
<number>0</number>


<config>
<spin-thresh>0.8</spin-thresh> 
<max-roll-error-deg>40.</max-roll-error-deg>
<max-pitch-error-deg>12.0</max-pitch-error-deg>
</config>
</attitude-indicator-electric>
</syntaxhighlight>

==== Clock ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/clock.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/clock.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<clock>
<name>clock</name>
<number>0</number>
</clock>
</syntaxhighlight>

==== Comm Radio ====
{| class="wikitable"
|Source File
|{{Repo link|site=gitlab|proj=flightgear|repo=flightgear|branch=next|path=src/Instrumentation/commradio.cxx}}
|-
|Header File
|{{Repo link|site=gitlab|proj=flightgear|repo=flightgear|branch=next|path=src/Instrumentation/commradio.hxx}}
|-
|extends
|{{Repo link|site=gitlab|proj=flightgear|repo=flightgear|branch=next|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<comm-radio>
<name>comm</name>
<number>0</number>
<eight-point-three>0</eight-point-three>
<full-duplex>0</full-duplex>
</comm-radio>

</syntaxhighlight>

* <code>eight-point-three</code>: Setting this to <code>1</code> (true) enables a simulation of the newer 8.33 kHz frequency raster
* <code>full-duplex</code>: set this to <code>1</code> to enable full duplex mode. In half-duplex mode, receiving will be disabled if <code>ptt</code> property is <code>1</code>. (Introduced in 2024.1 with default=1; after that default=0, so this usually is not needed to be set manually)
* see also [[Kx165]]

==== DCL GPS ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/dclgps.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/dclgps.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Information (from Source Code)'''<syntaxhighlight lang="c++">
// dclgps.cxx - a class to extend the operation of FG's current GPS
// code, and provide support for a KLN89-specific instrument. It
// is envisioned that eventually this file and class will be split
// up between current FG code and new KLN89-specific code and removed.
</syntaxhighlight>

==== [[Distance measuring equipment|DME (Distance Measuring Equipment)]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/dme.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/dme.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<dme>
<name>dme</name>
<number>0</number>
</dme>
</syntaxhighlight>

==== [[Global Positioning System|GPS (Global Positioning System)]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/gps.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/gps.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gps>
<name>gps</name>
<number>0</number>
</gps>
</syntaxhighlight>

==== GSDI/GSDA (Ground Speed Drift Angle Indicator) ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/gsdi.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/gsdi.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<gsdi>
<name>gsdi</name>
<number>0</number>
</gsdi>
</syntaxhighlight>This instrument configuration is not included in generic-instrumentation.xml. See the [[EC130]] for an aircraft implementing this instrument.

==== [[Avionics and instruments#Directional Gyro|Heading Indicator (Directional Gyro)]] ====

This is a realistic and highly configrable directional gyro based heading indicator. It can be either electrical or
suction driven and supports the gyro based errors like precession drift and transport wander.

{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/heading_indicator_dg.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/heading_indicator_dg.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}

'''Configuration'''

By default, the instrument is electrically driven and powered by '''/systems/electrical/outputs/DG[number]''' (for backwards-compatibility reasons)
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
</heading-indicator-dg>
</syntaxhighlight>

Like with most other electrically driven instruments you can explicitely set the power source:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<power-supply>/systems/electrical/outputs/heading-indicator</power-supply>
<minimum-supply-volts>12.0</minimum-supply-volts>
</heading-indicator-dg>
</syntaxhighlight>

To make it vacuum driven instead:
<syntaxhighlight lang="xml">
<heading-indicator-dg>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
<minimum-vacuum>4.0</minimum-vacuum> 
</heading-indicator-dg>
</syntaxhighlight>

You can optionally configure the instruments error behaviour and limits (to disable, set accordingly).
The defaults given in c++ are for demonstration and not realistic so these might be better:
<syntaxhighlight lang="xml">
<limits>
<yaw-limit-rate>11.5</yaw-limit-rate> 
<g-limit-lower>-0.8</g-limit-lower> 
<g-limit-upper>1.8</g-limit-upper> 
<yaw-error-factor>0.033</yaw-error-factor> 
<g-error-factor>0.033</g-error-factor> 
<g-limit-tumble-factor>1.5</g-limit-tumble-factor> 
<g-node>/accelerations/pilot-gdamped</g-node> 
<g-filter-time>10.0</g-filter-time> 
<yaw-rate-source>/orientation/yaw-rate-degps</yaw-rate-source> 
</limits>
<gyro>
<minimum-spin-norm>0.8</minimum-spin-norm> 
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
<heading-source>/orientation/heading-deg</heading-source> 
</syntaxhighlight>

The instrument has a built-in damping filter for the g-node, so spikes do not trigger tumbling. If tuning this is not sufficient, you can specify a custom source property.

'''Runtime configuration'''
The limits and gyro config are exposed to the instruments propoerty tree and can be changed at runtime.

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>caged-flag</code>
|Make the gyro caged. Use this to quickly stop tumbling (or prevent it in the first instance).
|-
|<code>align-deg</code>
|Should be used by the instruments model to rotate the disc, countering instrument errors.
|-
|<code>latitude-nut-setting</code>
|Set to the factory setting. At the nut's latitutde (<code>-90</code> to <code>90</code>) the precession by earths rotation is countered by a small weight on the gimbal.
|}

====[[Avionics and instruments#Directional Gyro|Heading Indicator (Electric Flux-Gate Compass)]]====
The flux-gate heading indicator always points to magnetic north automatically.

{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/heading_indicator_fg.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/heading_indicator_fg.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator-fg>
<name>heading-indicator-fg</name>
<number>0</number>
</heading-indicator-fg>

</syntaxhighlight>

* Powered by '''/systems/electrical/outputs/heading-indicator-fg[number]'''

==== Heading Indicator (Suction-Driven) ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/heading-indicator.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/heading-indicator.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<heading-indicator>
<name>heading-indicator</name>
<number>0</number>
<suction>/systems/vacuum/suction-inhg</suction>
</heading-indicator>
</syntaxhighlight>

The following proerties are also exposed for runtime configuration:
{| class="wikitable"
|<code>offset-deg</code>
|Read/write; Gyro drift is reflected in this property, and can be countered by altering the value. If not initialized at instrument init time, will be synced to "/environment/magnetic-variation-deg" automatically.
|}

* Note, this is an unrealistic/simple instrument. For better realism options, you should use the "Heading Indicator (Directional Gyro)", see above.

* Suction: see [[Aircraft systems#Vacuum]]

==== King KR 87 Digital ADF (Automatic Direction Finder) ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/kr_87.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/kr_87.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<KR-87>
<name>kr-87</name>
<number>0</number>
</KR-87>
</syntaxhighlight>

==== [[Avionics and instruments#Compass|Magnetic Compass]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/mag_compass.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/mag_compass.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<magnetic-compass>
<name>magnetic-compass</name>
<number>0</number>

<deviation>
<table>
<entry>
<ind>0</ind>
<dep>1</dep>
</entry>
<entry>
<ind>30</ind>
<dep>3</dep>
</entry>

<entry>
<ind>330</ind>
<dep>-2</dep>
</entry>
</table>
</deviation>
</magnetic-compass>
</syntaxhighlight>

* Deviation Table: This can be used to simulate [[Avionics and instruments#Magnetic deviation|Magnetic deviation]], e.g. to reflect what's written on a textured deviation card next to the compass. Can also be a property that is beeing read and dynamically calculated (<code><deviation>/instrumentation/magnetic-compass/deviation-deg</deviation></code>), for example to implement powered avionics influencing the magnetic field.

By default the compass simulates a fixed axis compass disc pitched at 0°. A pitched compass disc has an additional reading error.
The compass property tree exposes a <code>/instrumentation/magnetic-compass/pitch-offset-deg</code> prop that can be set to a fixed pitch angle to simulate pitched mounts or manually pitchable compass casings. By dynamically calculating the property, you can offset the plane's <code>/orientation-pitch-deg</code>, essentially nulling the effect. By adding some filters you can simulate a freely pitchable compass disc for a constrained pitch angle; that is: a compass disc mounted on a pivot-pin bearing (like most modern compasses feature). For an example see the [https://github.com/c172p-team/c172p/blob/a8bc43674af51cfe093c03ae21e2e84467b456fb/Systems/instruments.xml#L599-L802 filter implementation from the C172p].

The instrument exposes <code>pitch-deg</code> and <code>roll-deg</code> properties to simulate pitching and rolling of the compass disc based on flight forces and fluid viscosity.
You can use them in your 3D-models animation configs.

The damping can be adjusted by setting it in the instrumentation.xml config:
<code><fluid-viscosity type="double">8.2</fluid-viscosity></code> (8.2 mm²/s is the value of kerosene and should be good in most cases).

==== [[Radio beacons#Marker beacons|Marker Beacon]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/marker_beacon.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/marker_beacon.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<marker-beacon>
<name>marker-beacon</name>
<number>0</number>
</marker-beacon>
</syntaxhighlight>

==== [[Ground proximity warning system|MK-VIII]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/mk_viii.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/mk_viii.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<mk-viii>
<name>mk-viii</name>
<number>0</number>
</mk-viii>
</syntaxhighlight>For more information, see [[Ground proximity warning system]].

==== Master Reference Gyro ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/mrg.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/mrg.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<master-reference-gyro>
<name>master-reference-gyro</name>
<number>0</number>
</master-reference-gyro>
</syntaxhighlight>for more information, see [https://scottbouch.com/mcfs/lightningt5t55/docs/ap101b-1003-5-6-15a-part1-chap7-al2-nov84-instruments.pdf Lightning T Mk.5 Instruments PDF, p. 4f.]

==== Navigation Radio ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/navradio.cxx}},{{flightgear source|path=src/Instrumentation/newnavradio.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/navradio.hxx}},{{flightgear source|path=src/Instrumentation/newnavradio.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<nav-radio>
<name>nav</name>
<number>0</number>
</nav-radio>
</syntaxhighlight>

==== Radar Altimeter ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/rad_alt.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/rad_alt.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<radar-altimeter>
<name>radar-altimeter</name>
<number>0</number>
<update-interval-sec>0.1</update-interval-sec>
</radar-altimeter>
</syntaxhighlight>

==== [[Avionics and instruments#Turn Coordinator|Slip/Skid Ball]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/slip_skid_ball.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/slip_skid_ball.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<slip-skid-ball>
<name>slip-skid-ball</name>
<number>0</number>
</slip-skid-ball>

</syntaxhighlight>

==== [[Tactical Air Navigation|TACAN]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/tacan.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/tacan.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<tacan>
<name>tacan</name>
<number>0</number>
</tacan>
</syntaxhighlight>

==== [[Traffic alert and collision avoidance system|TCAS]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/tcas.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/tcas.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
For '''configuration''', see [[Traffic alert and collision avoidance system#Instrument List]]

==== [[Transponder]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/transponder.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/transponder.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<transponder>
<name type="string">transponder</name>
<number type="int">0</number>
<minimum-supply-volts type="double">8.0</minimum-supply-volts>
<mode type="int">1</mode>
<auto-ground type="string">/gear/gear/wow</auto-ground>
<encoder-path type="string">/instrumentation/altimeter</encoder-path>
<airspeed-path type="string">/instrumentation/airspeed-indicator/indicated-speed-kt</airspeed-path>
<mach-path type="string">/instrumentation/airspeed-indicator/indicated-mach</mach-path>
<kt70-compatibility type="bool">0</kt70-compatibility>
</transponder>
</syntaxhighlight>

* Mode
** 0 = Mode A
** 1 = Mode C
** 2 = Mode S
* Auto-Ground: Set property to be used to detect when the ground-bit (mode-S only) should be set
* Encoder/Airspeed/Mach Path: Set instrument properties to feed the transponder
* '''for more information, see [[Transponder]].'''

==== [[Avionics and instruments#Turn Coordinator|Turn Indicator]] ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/turn_indicator.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/turn_indicator.hxx}}
|-
|extends
|{{flightgear source|path=src/Instrumentation/AbstractInstrument.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<turn-indicator>
<name>turn-indicator</name>
<number>0</number>

<gyro>
<spin-up-sec>180.0</spin-up-sec> 
<spin-down-sec>300.0</spin-down-sec> 
</gyro>
</turn-indicator>
</syntaxhighlight>

* Note, the <code><gyro></code> sections are optional. The defaults given in c++ are for demonstration and not realistic.

==== Vertical Speed Indicator (VSI) ====
{| class="wikitable"
|Source File
|{{flightgear source|path=src/Instrumentation/vertical_speed_indicator.cxx}}
|-
|Header File
|{{flightgear source|path=src/Instrumentation/vertical_speed_indicator.hxx}}
|-
|extends
|{{simgear source|path=simgear/structure/subsystem_mgr.hxx}}
|}
'''Configuration'''<syntaxhighlight lang="xml">
<vertical-speed-indicator>
<name>vertical-speed-indicator</name>
<number>0</number>
<static-pressure>/systems/static/pressure-inhg</static-pressure>
</vertical-speed-indicator>
</syntaxhighlight>

* Static Pressure: see [[FGproperties/Systems/static]]

UIUC

2025-05-07T07:52:33Z

Gijs: Add note about removal from FlightGear

'''UIUC''' is the name of a [[flight dynamics model]] for [[FlightGear]] flight simulator. It was developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign in the early 2000s. Due to lack of usage, UIUC support has been removed from FlightGear after version 2024.1.

== History ==
UIUC made use of [[LaRCsim]] and was originally developed for the Smart Icing System Project. It was also developed for the accurate simulation of stalls.

Many aircraft were worked on for FlightGear with UIUC, although many were not GPL or not maintained. Some aircraft were maintained well enough to survive until FlightGear 1.0.0 in 2008. Over the years, they've been expanded with new models, and sometimes converted to other FDMs.

Some UIUC v-1 aircraft include:
* a4-v1-nl
* airwaveXtreme150-v1-nl
* asw20-v1-nl
* beech99-v1
* fkdr1-v1-nl
* marchetti-v1
* ornithopter
* sopwithCamel-v1-nl
* sopwithCamel-v2-nl
* wrightFlyer1903-v1-nl

== External links ==
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html Official website]
* [http://www.ae.illinois.edu/m-selig/apasim/flightsim/docs-mini/README.uiuc.html UIUC Readme (2002)]

{{FDM}}

[[Category:Flight Dynamics Model]]

LaRCsim

2025-05-07T07:51:40Z

Gijs: Add note about removal from FlightGear

'''LaRCsim''' is a [[Flight Dynamics Model]] (FDM) developed at {{wikipedia|NASA}} and used by a wide range of projects. LaRCsim was the default FDM of [[FlightGear]] until 2000. The code provided the starting point for the [[UIUC]] FDM. Due to lack of usage, LaRCsim support has been removed from FlightGear after version 2024.1.

== External links ==
* https://ntrs.nasa.gov/citations/19950023906
* http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html
* http://www.flightgear.org/Docs/Flight/LaRCsim/LaRCsim-notes/LaRCsim-notes.html
* http://www.albatross-uav.org/index.php/LaRCSim_Architecture
* http://www.princeton.edu/~stengel/MAE331.html

{{FDM}}

[[Category:Flight Dynamics Model]]

[[pt:LaRCsim]]

Category:Articles considered for deletion as of April 2025

2025-04-29T12:51:51Z

Gijs: Created page with "Category:Articles considered for deletion as of 2025"

[[Category:Articles considered for deletion as of 2025]]

TerraGear scenery build server

2025-04-29T12:51:28Z

Gijs: Considered for deletion: obsolete with WS3

{{Delete
|reason=Obsolete with World Scenery 3
|day=29
|month=4
|year=2025}}

{{FGCquote
|terragear tools are not exactly the most robust :) Building them can be a challenge, and getting useful output is just as hard.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=224616#p224616
|title=<nowiki>Re: Terragear, compilation errors-warnings</nowiki>
|author=<nowiki>psadro_gm</nowiki>
|date=<nowiki>Sun Nov 16</nowiki>
}}
}}

{{FGCquote
|I run genapts850 on linux 64bit with no problem. I've got a new machine, now and Windows 64 running on a virtual machine, but I haven't done any development work on Windows for 18 years now. It's really not very high on the priority list, as the world scenery is also generated on linux.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=167433#p167433
|title=<nowiki>Re: TerraGear GUI</nowiki>
|author=<nowiki>psadro_gm</nowiki>
|date=<nowiki>Wed Sep 26</nowiki>
}}
}}

{{FGCquote
|Remember, Terragear was never intended to used by an end user. It was designed to be run on a Linux server. It's been almost 3 years since I've started looking at this code. It took almost a full year of hacking on it before I was confident enough to commit changes. 
It is not user friendly. It was once my intention to make it easier to use and add features. Over time, it became obvious that this was optimistic. Bug fixes pretty much takes all of my time. 
 
That's not to say that I can't imagine an easy to use toolchain, unfortunately, we just don't have the resources to work toward this goal. If anyone is interested, I could help explain how the tools work, and how the code works.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=195883#p195883
|title=<nowiki>Re: Terragear for beginners</nowiki>
|author=<nowiki>psadro_gm</nowiki>
|date=<nowiki>Sun Dec 08</nowiki>
}}
}}

{{FGCquote
|User friendliness, and support for windows, 32 bit, etc have dropped to very low priority, as the server that Martin uses when generating the official scenery is well known to me. 
 
Hence, this is the reason we went to the web page setup. There was also some ideas for a VM, but that would still require a 64 bit host.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=224616#p224616
|title=<nowiki>Re: Terragear, compilation errors-warnings</nowiki>
|author=<nowiki>psadro_gm</nowiki>
|date=<nowiki>Sun Nov 16</nowiki>
}}
}}

{{FGCquote
|If you feel something is poorly designed, and should be done differently, go ahead and try to improve it. If others can be convinced of the merit, it most likely will become the 'new way'. So many examples of this in the past 4 years of development. 
 
advanced weather, random buildings, Rembrandt, ALS, canvas and OSGEarth. These are features that at one point, someone said - I wish FG could do xxx. Then, they sat down, and figured out HOW FG could do it.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=199226#p199226
|title=<nowiki>Re: Why are cockpits so integrated with planes?</nowiki>
|author=<nowiki>psadro_gm</nowiki>
|date=<nowiki>Wed Jan 29</nowiki>
}}
}}

[[File:TerraGear-Build-Server-Workflow.png|950px|TerraGear Build Server Workflow when using [[TerraGear GUI]] over SSH]]

Reeed's concept is more like this:
[[File:TerraGear build server concept map.png||Schematic of a possible setup for TG GUI or a web interface to access TerraGear services provided by a build server]]

{{Stub}}



[[File:TerraGear-GUI-Remote-Mode.png|thumb|Prototyping a remote mode for [[TerraGear]] as part of [[TerraGear GUI]]]]

{{Template:Non-stable|version=4.x|progress=40}}

{{infobox subsystem
|image = TerraGear-BuildServer-Prototype.png
|name =TerraGear Build Server
|started= 02/2014
|description = Build Server for TerraGear
|status = prototyping

|maintainers = looking for volunteers
|developers = looking for volunteers (since 02/2014),
}}

* Last update 02/2014
* Looking for people familiar with [[TerraGear]]
* Looking for people who are familiar with Linux, virtualization

= News =
{{See also|TerraGear BOINC}}

As part of working on a long-standing feature request, namely having a central shared [[TerraGear scenery build server]], saiarcot895 has created Linux packages for Debian/Ubuntu (deb/ppa) to install precompiled TerraGear binaries. This now greatly simplifies installing TerraGear, because people no longer need to manually set up a complete Linux build environment and all SimGear/TerraGear dependencies. Everything is now done in an automated fashion.

{{Note|To test the precomiled packages on a debian/wheezy based distro: edit '''/etc/apt/sources.list.d/sources.list''' and add the TG repo provided by saiarcot895:
<pre>
deb http://128.61.105.135/apt/wheezy main
deb http://128.61.105.135/apt/wheezy contrib
deb http://128.61.105.135/apt/wheezy non-free
</pre>
On Ubuntu Precise and Quantal the repo paths can be put in a new list file, create '''/etc/apt/sources.list.d/saiarcot895-terragear.wheezy.list''' and insert the the following. The format needs to be
<pre>
deb http://128.61.105.135/apt wheezy main
deb http://128.61.105.135/apt wheezy contrib
deb http://128.61.105.135/apt wheezy non-free
</pre>
Next, run '''apt-get update''' and then '''apt-get install terragear''' as root:
<pre>
# apt-get update && apt-get install terragear
</pre>
}}
Note:
This only installs the Terragear tool chain and not the GUI or any src. It by default installs it in /usr/bin folder unlike saiarcot895's download_and_install.sh (link may be broken [http://www.ggbhydropower.fr/flightgear/download_and_compile_tg.sh]) which installs everything including the GUI and src, wherever you want to put it.

[[File:TerraGear-hgtchop-VM.png|thumb|TerraGear hgtchop running in a 64bit TurnKeyLinux VM using saiarcot895's debian/wheezy packages]]
Next, we're hoping to use this to install TerraGear on a public server for which people can ask for remote shell access (SSH). People interested in exploring this, should be getting in touch via the forum or the wiki.

Obviously, users will still need to be familiar with TerraGear, but they may benefit from reduced bandwidth restrictions and/or more horsepower in comparison to running TerraGear locally (e.g. one user offered to contribute hosting on a 32gb RAM and 8-core server). So this could be a great opportunity for people to run scripted/unattended jobs, without having to go through the hassle of downloading/building/installing and configuring TerraGear.
But so far, being familiar with TerraGear and Linux is going to be a prerequisite still.

Once that is working, we'll investigate making the setup reproducible by using TurnKeyLinux. Once we have a working TKL distro, we can install a full TG setup in just a few minutes by downloading an ISO file and installing it in a VM (VMWare/VirtualBox). This would basically allow people to easily download/install TerraGear locally, either installed next to their OS, or as a virtual machine.

[[File:F-jjth-tggui-prototype.jpg|thumb|Web-based TerraGear GUI prototype developed by F-JJTH in 03/2014]]

The long term idea is to hook up [[TerraGear GUI]] to it, so that the GUI front-end talks to TerraGear across SSH.

This is currently still a use-case for which TG wasn't designed for, and the TG developers mentioned already on the forums that there may be some roadblocks ahead, so everything here is still highly experimental. But ultimately we hope to provide a front-end to a Linux-based TerraGear VM, either by reusing [[TerraGear GUI]] or by coming up with a custom web-based front-end (please get in touch if you can help with this!).

If you're interested in helping or learning more, please get in touch via the forum or via [[TerraGear scenery build server]].

= Problem =
Honestly compiling TerraGear could be the biggest issue

The main trouble is in compiling TerraGear and the fact it doesn't always play nicely. I think the fact the tutorial on the wiki is segmented doesn't help either - it's far easier to put all your elevation data in one folder, all your shapefiles in another folder, your airport data in another folder and then start running the process.

Many people (esp Windows users) have reported problems getting TerraGear tools to run. This is probably a significant factor limiting community contribution to FG custom scenery.

A 'build server' is one solution to this problem -- a server that accepts public-contributed shapefiles, builds the tile in an automated process (using the latest bugfixed TerraGear tools), then provides a way for the user to download the resulting .btg files to check his work.

I thought of a ready to use vm that contains the necessary tools (terragear) + a python script that connects to a server, downloads the needed data / scripts and starts compiling the scenery.
After the task is done the data would be uploaded back to the server.

The server could run a python script too, that manages the connected compile slaves. The script could take the compile slave capabilities (disk io, processors, line bandwidth) into account and assign tasks based on this to the slave.

All that is needed is someone to take the time setting up a Linux distro that comes with TerraGear and all required tools pre-built and pre-configured, using SuseStudio this isn't too complicated (the TG process however is, so you may need help from experienced TG users such as statto et al), this would get you a downloadable ISO file (CD/DVD or a USB boot image), which could in turn be installed by people, either on a dedicated box (or in a dual boot setup), or simply within vmware/virtualbox.

Finally, we could add a web frontend (perl,php or python) so that people could upload their own scenery to be built.

Let's pool our know-how and resources together and aim to setup a scenery build server!

{{FGCquote
|I run windows, and have followed the winding toolchain trail to a brick wall. TerraGear for windows is apparently abandoned, broken, or obsolete.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214155#p214155
|title=<nowiki>Is it possible to create a new airport in Windows?</nowiki>
|author=<nowiki>Kabuki</nowiki>
|date=<nowiki>Sat Jul 05</nowiki>
}}
}}

{{FGCquote
|What's the best option for me? Install some VM software and learn to use that so I can do fake linux? Or, run Ubuntu only for the sake of TerraGear? Or maybe create some airport data and hand it off to someone who can use TerraGear?
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=214155#p214155
|title=<nowiki>Is it possible to create a new airport in Windows?</nowiki>
|author=<nowiki>Kabuki</nowiki>
|date=<nowiki>Sat Jul 05</nowiki>
}}
}}

= Background =
For what it's worth, the primary bottleneck for scenery generation is disk I/O -- reading and writing files. There is a computational aspect, but on the whole it's disk IO that will limit things.

Back in the day when I was cranking out the world scenery myself, I had a cluster of linux machines running in parallel -- all talking to an nfs server -- I thought it was a pretty slick setup at the time, but I'm sure a fast single modern PC could outperform the cluster of 20-25 PC's I was using at the time.

Compiling a detailed area of 3 square degrees across only takes a couple hours running on a not-very-powerful server. Admittedly that's not that large of an area, but I've never found the build process to be unreasonable, though I only work with small batches.

= Objective =
This is an idea that has been repeatedly brought up on the FG forums (see references below). The idea is to make it easier for people to build scenery, by providing a scenery build service (server actually) where people can upload their scenery to be built and get their scenery compiled remotely, without needing to be intimately familiar with TerraGear and without requiring TerraGear to be installed locally.
This should also make it easier for people to use TerraGear, without having to build it from source.

= Virtualization =
Scenery compilation is demanding, so setting up a VM on a powerful system with scenery compilation tools would be a good idea. This might come in handy for people whose system is not as powerful and enable them to contribute to scenery building without requiring a powerful computer.

= Plan / Status (03/2014) =

The first step would probably be finding someone familiar with installing/setting up TG on Linux, and then also someone familiar with virtualization, so that a Linux distro like TurnkeyLinux can be set up with TerraGear - from that point on, everything should be fairly straightforward actually, assuming that we have someone willing to work on a web-interface -or API- to expose TerraGear as a web service, e.g. using Python, Php, Ruby or Perl - in fact, one could even use Nasal for this

Hooray is probably not going to work on this anytime soon, but is willing to help work out the details to get this started, so if you're interested in helping, please do get in touch!

One of the most straightforward ways to proceed here, would be just setting up TerraGear and using SSH/SCP to interact with the service - obviously, that would require either setting up accounts for each user, or setting up a shared/trusted account - in turn, this could then be supported by Gijs' [[TerraGear GUI]] - i.e. kinda like a "remote operating" mode that works over SSH - that would allow us to reuse the existing GUI, without having to come up with a new WebService API.

Qt has various APIs to handle SSH, e.g. see: http://doc.qt.digia.com/qtcreator-extending/utils-sshconnection.html

* Download & Install Virtualbox {{Done}}
* Download TurnKeyLinux {{Done}}
* Set up new VM {{Done}}
* Read up on [http://www.turnkeylinux.org/tkldev TKLDev] {{Progressbar|20}}
* Install SimGear in Headless mode [[Building_using_CMake#SimGear_Build_Options]] {{Done}}
* Install TerraGear inside the VM using the [[Building FlightGear - Debian#TerraGear]] script {{Done}}
* Investigate packaing SimGear headless (saiarcot895) {{Done}}
* Investigate packaging TerraGear as a deb/ppa (saiarcot895 ) {{Done}}
* Use [[Using TerraGear]] to come up with a test script {{Progressbar|20}}
* Get in touch with Gijs to patch [[TerraGear GUI]] to support operating over SSH {{Not done}}
* Get in touch with people volunteering hosting {{Not done}}
* Get in touch with the TerraGear guys (psadro_gm & papillon81) to help optimize TerraGear for server-focused operation {{Not done}}
* Investigate clustering options, i.e. via distcc {{Not done}}

= Feedback =
* Yes, that would indeed be interesting, with a small web interface to interact with the user. Always wanted to do it, never found the time...
* Certainly sounds interesting, would mean I could build scenery while away from home which would be a huge bonus for me, as I spend most my time on my laptop!
* There's certainly interest in this sort of thing, and I am pretty sure you'd get to see a number of feature requests for such a thing.
* The neat thing about a VM image (i.e. VirtualBox-based) would be that it could not only be provided as a server, but that it would also be possible to create a bootable "live CD/DVD" - so that people could easily run and install this things locally.
* I think that using virtualization is an excellent opportunity here to simplify participating in FG development, if we had "live CDs" for most criticial FG processes, we'd surely have more people able to contribute.
* Though, I am really not sure if starting with TerraGear is the simplest approach to pursue, I think there are several potential pitfalls - especially given that it is currently being worked on, but also due it not really being the most intuitive piece of software in the FG eco system. For people without solid TG experience, this will be pretty challenging.
* If you're just looking to get started, you might just as well look into creating VM images to set up a multiplayer server (fgms), this is well documented in the wiki.Even today, many people find it not so easy to set up everything properly. So having a VM image to easily run fgms might be a nice practice to get started? And you'd surely gather valuable experience for your TerraGear image, too.
* just trying the concept by coming up with a fully virtualized setup of fgms might be another option, that should be much easier to accomplish, but would be a nice exercise to see how things can be deployed, configured and run - sort of like a "beta test" to gather more experience with virtualizing FG related software.
* The neat thing about this whole VM-based approach is that everything would be neatly encapsulated - so that would also make it possible to run several VMs at once (i.e. a fgms & terragear servers at once) while still controlling everything from the central host system, this could even be done using a simple GUI to easily configure and control all VMs.
* If you manage to get this working, it would surely be a significant contribution - especially once people actually start supporting it to simplify things even further.
* For example, the "TerraGear GUI" could be changed to support a "remote mode" where a build server can be used, so that scenery is built remotely. In the same sense, a web frontend could also be provided to allow people to easily use the server.
* A QGIS/GRASS plugin might be another interesting option.

= Crowd-compilation =
{{Merge|TerraGear BOINC}}
* A way to distribute work to a bunch of vm scenery bulding servers would be nice. Something people willing to help and with some extra disk space could run on their system in the normal downtime to share computing power to the scenery generating effort.
* Yes, we also talked about this last year, it seems there are some SSH-based solutions available, i.e. they would use standard "scp" to copy stuff via ssh to a remote location. If I remember correctly, we also looked for a Python-based solution so that the TerraGear GUI could be modified accordingly.
* I understand that generating the scenery from the raw data takes quite some CPU time. How about creating a BOINC project which could harness the idle CPU-power of many users to assist with this job?
* Actually I dont have a clue about this (generating scenery) and I think there're many others like me out there. So a BOINC-Project would be a way to contribute to FG really ease! I would join this.

== BOINC ==
{{Merge|TerraGear BOINC}}
{{DeQuote}}

{{FGCquote
|1= For what it's worth, the primary bottleneck for scenery generation is disk I/O -- reading and writing files. There is a computational aspect, but on the whole it's disk IO that will limit things.
Back in the day when I was cranking out the world scenery myself, I had a cluster of linux machines running in parallel -- all talking to an nfs server -- I thought it was a pretty slick setup at the time, but I'm sure a fast single modern PC could outperform the cluster of 20-25 PC's I was using at the time.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=144405#p144405
| title = <nowiki>Re: Create a </nowiki>
| author = <nowiki>curt</nowiki>
| date = Dec 9th, 2011
| added = Dec 9th, 2011
| script_version = 0.23
}}
}}

{{FGCquote
|1= I understand that generating the scenery from the raw data takes quite some CPU time.

How about creating a [http://boinc.berkeley.edu/ BOINC] project which could harness the idle CPU-power of many users to assist with this job?
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=144361#p144361
| title = <nowiki>Create a BOINC project for scenery generation?</nowiki>
| author = <nowiki>sgofferj</nowiki>
| date = Dec 9th, 2011
| added = Dec 9th, 2011
| script_version = 0.23
}}
}}
{{FGCquote
|1= The only alternative to do it more quickly, in my opinion, would be using a distributed architecture - e.g. BOINC - or a cluster of servers.)
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=225099#p225099
| title = <nowiki>Re: Howto create the parking positions</nowiki>
| author = <nowiki>elgaton</nowiki>
| date = Nov 21st, 2014
| added = Nov 21st, 2014
| script_version = 0.23
}}
}}
{{FGCquote
|1= when our main scenery resource will be gone in a couple of weeks, we will have a hard time to create a new world scenery. Generating the entire world was a job that ran continuously for days - if not weeks, even on a powerful machin with almost unlimited resources. As we have to re-think the entire process anyway, I just had the idea to use our users resources for that, probably by using something like BOINC: https://boinc.berkeley.edu/trac/wiki/AppIntro We sure need to do many tweaks within the tool-chain, but I can't think of any reason why this should not work. Does anybody have experience with BOINC or alike?
|2= {{cite web
| url = http://sourceforge.net/p/flightgear/mailman/message/34666765/
| title = <nowiki>[Flightgear-devel] Continous, Distributed Generation of Terrain</nowiki>
| author = <nowiki>Torsten Dreyer</nowiki>
| date = Dec 3rd, 2015
| added = Dec 3rd, 2015
| script_version = 0.23
}}
}}

{{FGCquote
|1= we could adopt an even simpler approach:

<ol style="list-style-type: decimal"># improve the existing tools (and add new ones) to support regenerating a single tile without depending on the surrounding ones;
# expand the FlightGear Scenery Database webforms, if needed, to allow any FG user to submit improvements that can not be done via the Airport Gateway or OSM;
# periodically grab all improvements from OSM/the Airport Gateway via their APIs;
# regenerate the single tiles using a distributed system like BOINC (see [[TerraGear scenery build server|this page on the wiki]]);
# publish the scenery via HTTP (from a single website or a network of mirrors).

|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=236906#p236906
| title = <nowiki>Re: Google code colse there doors</nowiki>
| author = <nowiki>elgaton</nowiki>
| date = Mar 26th, 2015
| added = Mar 26th, 2015
| script_version = 0.23
}}
}}

{{FGCquote
|1= I thought of a ready to use vm that contains the necessary tools (terragear) + a python script that connects to a server, downloads the needed data / scripts and starts compiling the scenery.

After the task is done the data would be uploaded back to the server.
The server could run a python script too, that manages the connected compile slaves. The script could take the compile slave capabilities (disk io, processors, line bandwidth) into account and assign tasks based on this to the slave.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=144459#p144459
| title = <nowiki>Re: Create a </nowiki>
| author = <nowiki>ot-666</nowiki>
| date = Dec 10th, 2011
| added = Dec 10th, 2011
| script_version = 0.23
}}
}}

Also in that case, a BOINC project would help because then for a million IOs there are a million PCs doing each 1 IO at the same time instead of 1 PC queueing up a million IOs ^^.
But automatizing the whole process a little bit could also help. As I mentioned in another thread, I have 10MBit/s sym inet, a fairly powerful server which runs 24/7 and has RAIDs (IO-speed!) and now I upgraded my workstation also. If it's a BOINC project or just an automated script which pulls the stuff and goes through the workflow, I would be happy to contribute to the rendering of the scenery. Just familiarizing myself with geospatial sciences, getting into various GIS programs and doing the process by hand is a dealbreaker for me. I just don't have the time to get into all this in depth, unfortunately.

Maybe it actually would be a good idea for the Terragear people to concentrate on toolchain and workflow for a moment and come up with something that in basic can work fairly automatically. That would for sure be an investment into the future, because toolchains and workflows which need extensive manual intervention not only eat up resources unnecessarily but also include inherent risks for the whole project because these kinds of manual operations require specific knowledge which is incorporated in persons. If the persons leave the project for what reason ever, the whole project is in jeopardy.

= Remastering =
Also note that when we looked into this last year, we found a number of Linux distributions that are specifically designed to support "re-mastering", i.e. you can create a custom Linux distribution just by setting everything up as needed, and then create a bootable live CD automatically (i.e. scripted or GUI based) 100% based on the running "live session".

Basically, this would allow you to download such a distro's ISO image, then install it into a VM - set up everything as needed, and create a completely new ISO/VM image based on your customizations.

Note that you can do all of this easily using the free SuseSTUDIO service provided by OpenSUSE. This is a completely web-driven wizard to create OpenSUSE-based live CD/DVD images, completely set up and customized to your own needs.

You can even test and run the images remotely, but you can obviously also download the images once things are working.
It is also possible to set up "projects" - so that several people can work together.

= Approach =
Use a remastered linux distribution (i.e. using http://www.susestudio.com/ ), which already contains TerraGear and all required tools/dependencies in a pre-built and pre-configured fashion.

= Concerns and open issues =
* Another thing worth keeping in mind is compatibility, i.e. 32 bit vs. 64 bit OS. In the case of TG, 64 bit architectures offer theoretical benefits, regarding memory use - OTOH, many people these days are still running 32 bit OS.

= References =
* http://forum.flightgear.org/viewtopic.php?f=5&t=8735
* http://forum.flightgear.org/viewtopic.php?f=5&t=14163
* http://forum.flightgear.org/viewtopic.php?f=5&t=14592
* http://forum.flightgear.org/viewtopic.php?f=5&t=21501&p=195685#p195654

[[Category:Scenery enhancement]]
[[Category:TerraGear]]

Howto:Install aircraft

2025-04-29T12:47:23Z

Gijs: /* Manual installation process */ remove reference to old website

{{installing}}

The preferred option to install the latest official [[aircraft]] is through the ''Aircraft'' tab in the [[FlightGear Qt launcher|built-in launcher]], as explained in the following video. The remainder of this article describes the manual process, only to be performed when you don't use the aircrafts from the official FGAddon hangar.

{{#ev:youtube|a-UIrw7nEy4}}

== Manual installation process ==

=== Linux ===
(Ubuntu 12.04)
# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside <tt>/usr/share/games/flightgear/</tt>. For example, use <tt>/home/{YourUserName}/FlightGear/CustomAircraft</tt>.
# Extract your aircraft file into the folder (the one you created above)
#: unzip XXXXX.zip
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>/home/{YourUserName}/FlightGear/CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

Now, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== Macintosh OS X ===

# Download the aircraft
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is somewhere you can find easily, For example, use <code>/Users/{YourUserName}/Aircraft</code>.
# Extract your aircraft file into the folder (the one you created above)
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <code>/Users/{YourUserName}/Aircraft</code>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

Now, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear. This method is preferred over modifying FGData as it allows you to more easily access the aircrafts files, as well as having the benefit of persisting across FG updates, saving the hassle of having to redownload and install your aircraft each time you update FlightGear.

=== Windows ===
# Download an aircraft and save it on your desktop.
# Unzip the file using a file archiver, for example the open source file archiver [http://www.7-zip.org/ 7-Zip].
# Create a directory to store your aircraft if you have not already done so. Make sure this directory is outside your <tt>[[$FG_ROOT]]</tt> directory. For example, use <tt>C:\Users\{YourUserName}\FlightGear\CustomAircraft</tt>.
# Move the unzipped folder (usually the aircraft's name) to your that aircraft directory.
# Start up FlightGear with Launcher. In Launcher, go to the ''Add-ons'' tab. In the ''Additional aircraft folders'' section, click the ''Add'' button and select the main folder for additional aircrafts (in our case <tt>C:\Users\{YourUserName}\FlightGear\CustomAircraft</tt>). Now your plane should appear on the list of planes, otherwise restart FlightGear.

Now, you just need to unzip the next downloaded aircraft in the same directory and it should already be visible on FlightGear.

=== From the command line ===
Launching FlightGear from the command line, use the <code>--fg-aircraft=path</code> option, which in our case can be: <code>--fg-aircraft=/home/{YourUserName}/FlightGear/CustomAircraft</code>.

== When installing an aircraft fails ==
=== Rename aircraft folder ===
If FlightGear fails to start with the new aircraft you have installed, or if it starts but the aircraft is invisible you might have to rename the folder where the aircraft files are.
This issue is most often encountered when downloading a .zip file from some online git repository. In those cases you will most likely end up with a folder name of the following form MyZippedRepo-[branch]. In this case you should rename the folder to be just '''MyZippedRepo'''.

If the above doesn't work, or for other cases, check for a readme file and have a look there for instructions.

Otherwise open the aircraft-set.xml file and search in it for paths containing '''Aircraft/AircraftFolderName'''. The name of the folder should match '''AircraftFolderName'''.

For instance if in the imaginary-set.xml you would find an instance like this:
<syntaxhighlight lang="xml">
<splash-texture>Aircraft/MyCreation/splash1.png</splash-texture>
</syntaxhighlight>
that means that you should rename the folder where imaginary-set.xml is to '''MyCreation'''.

=== XML files with wrong encoding ===
If you start FlightGear with the new plane you installed and there is no cockpit or exterior, this may be because the XML files are in the wrong encoding.

To fix this on Linux try this:
<syntaxhighlight lang="bash">
$ cd path/to/aircraft/directory/
$ find . -name "*.xml" -print | xargs sed -i 's/<?xml version="1.0" encoding="UTF-8"?>/<?xml version="1.0" encoding="ISO-8859-1"?>/g'
</syntaxhighlight>

If any of the methods above do not work, ask around on the [[Howto:Multiplayer#Multiplayer chat|multiplayer chat]], [[FlightGear IRC channel|IRC]] or on the {{forum link|f=11|text=forum}}.

== Choosing aircraft ==
If you are looking for information to decide what aircraft to download, try:
* [[Aircraft]]
* [[Helicopter]]
* [[Vehicle]]
* [[Table of models]]
External links to third party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions. If you happen to use an older version of FlightGear, look for older aircraft in the links section.

==Video tutorial by the community==
{{#ev:youtube|OiqGjc8W880|480px||Tutorial on downloading and installing aircraft from Github pages by PINTO. Adding manually downloaded aircraft folders in the [[FlightGear_Qt_launcher|qt-launcher]] is pretty much the same for non-github downloads too. Aircraft are often developed on Github. This shows you to the download Github versions of aircraft that are not in FGAddon yet for whatever reason, and the latest work-in-progress state of some aircraft in FGAddon for testing and feedback. (September 2019)}}

== Related content ==
* [[Installing Scenery]]

[[Category:Howto|Install aircraft]]

[[de:Howto:Flugzeuge Installieren]]
[[es:Cómo:Instalar_aviones]]
[[fr:Howto Installer un avion]]
[[pl:Instalowanie_samolotów]]

User talk:Zeppelin

2025-04-19T11:41:05Z

Gijs: /* Getting support */ new section

{{Template:Welcome to the wiki|realName=|name=Zeppelin}}

-- [[User:New user message|New user message]] ([[User talk:New user message|talk]]) 17:05, 17 April 2025 (UTC)

== Getting support ==

Hi and welcome!

I see you've added a support question to your [[User:Zeppelin|user page]]. Please know that the wiki is not the right place for such questions, as it is primarily meant for documentation. Our support forum is the much better place: {{forum url}}. There you will also be able to get into contact with the Zeppelin's developer, so please open a topic on the forum.

[[User:Gijs|Gijs]] ([[User talk:Gijs|talk]]) 11:41, 19 April 2025 (UTC)

Template:FlightGearVendors

2025-03-22T15:24:10Z

Gijs: Remove link and reference to DVDs that are no longer available

<noinclude>
{{Informative template|1=
== Goal ==
This template provides a single text that can be used on articles about a vendor that appears to use several names for his (or our) product.

== Usage ==
Create an article with the name of the product as title and add the following (and only the following) content to it:
<pre>
{{FlightGearVendors}}
</pre>
}}

[[Category:Templates]]
</noinclude><includeonly>As many people are aware, there is a "new" flight simulator product that is being widely and actively marketed at the moment - '''{{PAGENAME}}''' (also promoted as '''ProFlightSimulator''', '''FlightSimPro''', '''Earth Flight Sim''', '''FlightProSim''', '''Real Flight Simulator'''). This product is a direct copy of a really old and outdated version of the freely-available [[FlightGear]] flight simulator for which the FlightGear project does not provide support. {{PAGENAME}} goes to extreme measures to hide the fact that they are simply copying an old version of FlightGear and reselling it under a different name, unsupported by the FlightGear community and without any visible value added to the outdated version of FlightGear. In some cases they have tried to turn the tables and say that FlightGear is ripping them off and pirating their work. This has caused some confusion for many people. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a [[FAQ]].

FlightGear is an open-source flight simulator that was started in 1996. It is released as so called 'open source' under the [[GNU General Public License]] v2, and as such, it is free to download, use, modify and distribute with few restrictions. It has been developed with the collaboration of a large number of individuals over more than 15 years. FlightGear can be downloaded at no cost from https://www.flightgear.org.

=== Review of {{PAGENAME}} ===
{{PAGENAME}} is a commercial product very heavily based on FlightGear. Investigation by a number of FlightGear developers has found no difference between this and the FlightGear v1.9.1 release (which is an '''outdated''' version of FlightGear, released almost half a decade ago) other than a change of name. {{PAGENAME}} is in no way endorsed or supported by the core FlightGear development team or the FlightGear user community in general.

Given the similarities between {{PAGENAME}} and the old version of FlightGear, we would recommend that prospective buyers download the latest FlightGear version for free and satisfy themselves that the old re-branded FlightGear version distributed under the name {{PAGENAME}} provides worthwhile value for money before purchasing it. Even if you are certain that you want to run FlightGear v1.9.1, you can still download this freely from the web, without having to spend any money.

It may also be worth noting, that their sample screenshots also show some pictures obviously taken from Microsoft Flight Simulator X, which becomes obvious when paying attention to the blue glass cockpit screen backgrounds.

=== What are the differences between the two? ===
As far as we have been able to make out, the only difference between FlightGear v1.9.1 and {{PAGENAME}} is a change in name throughout the software, and the fact that you have to pay for it, as well as aggressive marketing tactics, misrepresenting the offered download package as something that it clearly isn't.

=== Legal or illegal? ===
The [[GNU GPL]] license, under which FlightGear is released, allows reselling under certain terms. The main issue that FlightGear developers have is the misleading marketing tactics used by pro flight sim that target unsuspecting users who aren't yet familiar with FlightGear. This is primarily an ethical, not a legal issue.

=== Is it legal to sell a copy of FlightGear, whether re-branded or not? ===
Yes, provided the seller is in compliance with a number of conditions detailed in the GPL.

=== Has {{PAGENAME}} paid any money to FlightGear for the rights to the program? ===
No. No such payment is required, as FlightGear is GPL software. No such payment has been offered, no such payment has been made. Any claims by {{PAGENAME}} that they support the FlightGear project are entirely wishful thinking on their part.

=== Why do the FlightGear developers allow this? ===
The freedom to modify and enhance FlightGear is a core part of the project, and of open-source in general. Restricting the modifications that are allowed and what people can do with the software goes against that ethos.

=== Is there any relationship between the makers of {{PAGENAME}} and the FlightGear Project? ===
No.

=== Has {{PAGENAME}} contributed to the FlightGear project at all? ===
No.

=== I have purchased {{PAGENAME}}. Can I get a refund? ===
That is something you will have to take up with the distributors of {{PAGENAME}}. They guarentee a 60 day money back trial period, though some that have purchased FlightProSim have had trouble getting a refund and claim that FlightProSim did not respond to their requests for a refund. If you are having difficulty getting {{PAGENAME}} to cooperate and refund your purchase, you may want to call your credit card company or eWallet processor (ClickBank, PayPal, Skrill) and cancel the transaction. It may also help to get in touch with the corresponding affiliate program (e.g. commission junction, clickbank, click2pay etc) and report the product as being what it is (linking back to this project statement to help clarify the situation).

=== This whole situation makes me upset! What can I do? ===
First of all, the main problem here is the marketing tactics used by {{PAGENAME}} which exhibit very dubious ethical values. The FlightGear development teams feels the best way to combat this problem is through positive FlightGear marketing and by honestly pointing out that {{PAGENAME}} is simply an outdated rebranding of an already free flight sim called FlightGear.

We want all of you to stay positive, to be honest and to be fair!

If you want to help combat misleading marketing, let's all get the word out about FlightGear. FlightGear doesn't have the kind of advertising budget that the {{PAGENAME}} guys do. We need you!!! Please post wherever you can on web sites, forums, blogs, facebook, etc. We don't mind if someone chooses to buy {{PAGENAME}}, in fact that's great, as long as they have complete information in advance and aren't being misled by a slimy sales pitch that sounds too good to be true.

So let's get the word out and try to make sure that {{PAGENAME}} has to market to an "educated" audience!
=== Community Feedback ===
{{FGCquote
|Just another mug who got scammed by them a week or so ago, as my wife bought PFS Deluxe version as a download for my Xmas present. Cost her about £48 ($77).
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=199216#p199216
|title=<nowiki>Re: proflightsimulator.com</nowiki>
|author=<nowiki>Bimbobaggings</nowiki>
|date=<nowiki>Wed Jan 29</nowiki>
}}
}}

{{FGCquote
|I am one of the poor gullible suckers who got scammed by "ProFlightSimulator"
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=184254#p184254
|title=<nowiki>Re: proflightsimulator.com</nowiki>
|author=<nowiki>drbob01</nowiki>
|date=<nowiki>Tue May 28</nowiki>
}}
}}

{{FGCquote
|, I almost got scammed by VirtualPilot 3D. I'm glad I found this forum.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=169026#p169026
|title=<nowiki>FlightGear Launch Control 1.6.2 question</nowiki>
|author=<nowiki>researchcapt</nowiki>
|date=<nowiki>Sun Oct 21</nowiki>
}}
}}
{{FGCquote
|Maybe we scammed PFS purchasers should form our own club, ready for the future scammed buyers.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=199216#p199216
|title=<nowiki>Re: proflightsimulator.com</nowiki>
|author=<nowiki>Bimbobaggings</nowiki>
|date=<nowiki>Wed Jan 29</nowiki>
}}
}}

{{FGCquote
|It's a marketing scam - the language on the site, the affiliates program, the advice on creating review sites, and the fact he's doing the same thing for many other GPL projects, all point to this. He doesn't care about his victims - ripping them off is profitable for him.
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=102087#p102087
|title=<nowiki>Re: proflightsimulator.com</nowiki>
|author=<nowiki>zakalawe</nowiki>
|date=<nowiki>Sat Nov 13</nowiki>
}}
}}
[[Category:FlightGear vendors]]
</includeonly>

SourceForge

2025-03-21T12:25:41Z

Gijs: Remove repositories that are now hosted on Gitlab

'''SourceForge''' is an open source infrastructure provider that is currently used to host some of the [[FlightGear]] infrastructure. In January 2025, most of the source repositories were moved to [[GitLab]], from where they are mirrored to SourceForge.

The following version control repositories are currently hosted on SourceForge:

* [[FGAddon]]: {{fgaddon url}}
* [[OpenRadar]]: {{openradar url}}
* SceneryWeb: {{sceneryweb url}}

SourceForge also provides:

* The file download area: https://sourceforge.net/projects/flightgear/files/
* All of the mailing lists: https://sourceforge.net/p/flightgear/mailman/

== References ==

* [https://sourceforge.net SourceForge website]
* {{wikipedia |SourceForge|SourceForge Wikipedia article}}

[[Category:Hosting infrastructure]]

FlightGear Git: core developers

2025-03-21T11:08:23Z

Gijs: Update to Gitlab

{{Git}}
Anyone contributing to the core of [[FlightGear]], like C and C++ code, is a '''core developer'''. This article helps those in setting up a correct workflow, to ease the inclusion of their work into the simulator.

== Preparations ==
The in this section described steps are only required once, at the initialization of your development environment.

=== Cloning the repositories ===
The first thing to do as a prospective developer is to [https://gitlab.com/users/sign_up register at GitLab] if you have not already done so. This will enable you to publish your edits and have them incorporated into the main project.

After logging in, you can create a personal "clone" of the various FlightGear repositories. These clones are where you will be working in, without touching the main repositories. To create a clone, navigate to the respective repository on https://gitlab.com/flightgear and click the Fork button. In general the default name is fine, but you can change it to whatever you like. GitLab will now clone the repository. Depending on the size of the repository (especially fgdata is a large one), this can take some time.

=== Obtaining the source ===
Before you can start editing, you first need to retrieve the source code to your computer. For FlightGear you will need [[SimGear]], [[FlightGear]] and fgdata. The first two are covered by this article, the latter is explained in [[FlightGear Git: data developers#Obtaining the data]].

# Create a directory on your computer where you'll be storing the source code.
# Change into that folder.
# Clone the repositories with the following commands. This will create subfolders and put all the contents of the repositories in there.
#:<code>{{repo link
| site = gl
| cmd = git clone
| proj = flightgear
| repo = flightgear
| type = git
| full = 1
}}</code>
#:<code>{{repo link
| site = gl
| cmd = git clone
| proj = flightgear
| repo = simgear
| type = git
| full = 1
}}</code>

== Building the simulator ==
Now that you've set up a development environment and obtained source and data, the next step is to build FlightGear from that source. There are several articles that can help you there. They are all listed at [[Building FlightGear]].

== Making edits ==
It is recommended to split your new clones into separate local branches for your work. For instance, if you're working on a new radio code and performance improvements, you might create two branches named "radio" and "performance". To do this, run the following commands:
:<code>git checkout next</code>
:<code>git checkout -b <branch name></code>
Then you can make your changes to the new local branch(es), which will make merge requests easier for both yourself and committers. To switch in between branches, simply use
:<code>git checkout <branch name></code>

Re-build FlightGear (and if necessary SimGear) after making changes, to confirm that everything works as expected.

== Publishing edits ==
To push local updates to your clones on GitLab, perform the following steps:
# Switch to the branch that contains your edits:
#:<code>git checkout <branch name></code>
# List all the changed files:
#:<code>git status -- .</code>
# Now it's time to commit the changed files.
#* If you want to commit all changed files, run the following and type your commit message.
#*: <code>git commit -a</code>
#* If you only want to commit a selection of files, run the following:
#*: <code>git add <path/to/file></code> (for single files)
#*: <code>git add --all <path/to/folder></code> (to add all files within a certain folder)
#*: <code>git rm <path/to/file></code> (to remove files that you've removed)
#: Followed by
#:: <code>git commit -m "<commit message>"</code>
# Check if everything went fine, by loading Gitk:
#: <code>gitk</code>
# Finally, push the commit to your clone on GitLab with the following command. Replace <code>YourUID</code> with your GitLab account and <code>YourClone</code> with the name of your clone:
#: <code>git push git@gitlab.om:YourUID/YourClone.git</code>

== Requesting edits to be merged ==
# Click the "Request merge" button on your clone page.
# Once again write a short summary (could be the same as used with git commit), but this time, also write an explanation of your merge request (what does it do?). Make sure you set the target repository correctly, target branch to next and source branch to the local branch with your updates.
# Tick the box in front of your commit and click the "Create merge request" button.
# Everyone can see the pending request, but in order to make sure that your request gets looked at, you may contact a contributor.

Creating merge requests using this method literally means merging an entire branch into the main repository; this may not be desirable for some situations, such as small changes that only require one little commit. There's a neat method to only push certain commits to a merge request discussed by Anders Gidenstam [http://forum.flightgear.org/viewtopic.php?f=4&t=10392&start=45#p115747 on the FlightGear Forums].

[[Category:Git]]

Template:Sceneryweb source

2025-03-21T10:34:27Z

Gijs: Sceneryweb is still on SourceForge

{{repo link
| site = sf
| cmd{{#if:{{{cmd|}}}||NULL}} = {{{cmd}}}
| opt{{#if:{{{opt|}}}||NULL}} = {{{opt}}}
| protocol{{#if:{{{protocol|}}}||NULL}} = {{{protocol}}}
| login{{#if:{{{login|}}}||NULL}} = {{{login}}}
| type{{#if:{{{type|}}}||NULL}} = {{{type}}}
| proj = flightgear
| repo = sceneryweb
| branch = {{{branch|{{{b|master}}}}}}
| tag{{#if:{{{tag|}}}||NULL}} = {{{tag}}}
| path{{#if:{{{path|{{{f|{{{1|}}}}}}}}}||NULL}} = {{{path|{{{f|{{{1}}}}}}}}}
| commit{{#if:{{{commit|{{{c|}}}}}}||NULL}} = {{{commit|{{{c}}}}}}
| line{{#if:{{{line|{{{l|}}}}}}||NULL}} = {{{line|{{{l}}}}}}
| view{{#if:{{{view|{{{v|}}}}}}||NULL}} = {{{view|{{{v}}}}}}
| text{{#if:{{{text|{{{t|}}}}}}||NULL}} = {{{text|{{{t}}}}}}
| pre{{#if:{{{pre|}}}||NULL}} = {{{pre}}}
| post{{#if:{{{post|}}}||NULL}} = {{{post}}}
| simplepath{{#if:{{{simplepath|}}}||NULL}} = {{{simplepath}}}
| full{{#if:{{{full|}}}||NULL}} = {{{full}}}
}}<noinclude>

{{repo link/doc git source
| label = SceneryWeb
| repo = sceneryweb
| branch = master
| examples =
=== No parameters ===
{{obr}}sceneryweb source{{cbr}}
{{sceneryweb source}}

=== File ===
{{obr}}sceneryweb source
{{!}} path = WWW/scenemodels/submission/index.php
{{cbr}}

{{sceneryweb source
| path = WWW/scenemodels/submission/index.php
}}

=== File and a branch ===
{{obr}}sceneryweb source
{{!}} path = WWW/scenemodels/submission/index.php
{{!}} branch = master
{{cbr}}

{{sceneryweb source
| path = WWW/scenemodels/submission/index.php
| branch = master
}}

=== File and a tag ===
{{obr}}sceneryweb source
{{!}} path = WWW/scenemodels/submission/index.php
{{!}} tag = before-server-move
{{cbr}}

{{sceneryweb source
| path = WWW/scenemodels/submission/index.php
| tag = before-server-move
}}

=== File and a commit ===
{{obr}}sceneryweb source
{{!}} path = WWW/scenemodels/submission/index.php
{{!}} commit = c633c4
{{cbr}}

{{sceneryweb source
| path = WWW/scenemodels/submission/index.php
| commit = c633c4
}}

{{obr}}sceneryweb source
{{!}} path = WWW/scenemodels/submission/index.php
{{!}} commit = c633c463e77c945c923a7d8694b3636f7b69470a
{{cbr}}

{{sceneryweb source
| path = WWW/scenemodels/submission/index.php
| commit = c633c463e77c945c923a7d8694b3636f7b69470a
}}

=== File and line number ===
{{obr}}sceneryweb source
{{!}} path = WWW/mapserver/AirportsXML.py
{{!}} line = 60
{{cbr}}

{{sceneryweb source
| path = WWW/mapserver/AirportsXML.py
| line = 60
}}

=== Custom label given ===
{{obr}}sceneryweb source
{{!}} path = Apache/fgmapserver.conf
{{!}} text = The newest FlightGear map server Apache configuration file
{{cbr}}

{{sceneryweb source
| path = Apache/fgmapserver.conf
| text = The newest FlightGear map server Apache configuration file
}}

=== Full path ===
{{obr}}sceneryweb source
{{!}} path = WWW/scenemodels/submission/index.php
{{!}} commit = c633c463e77c945c923a7d8694b3636f7b69470a
{{!}} full = 1
{{cbr}}

{{sceneryweb source
| path = WWW/scenemodels/submission/index.php
| commit = c633c463e77c945c923a7d8694b3636f7b69470a
| full = 1
}}

=== Aliased parameters ===
This is for https://sourceforge.net/p/flightgear/sceneryweb/ci/before-server-move/tree/WWW/scenemodels/submission/index.php.

{{obr}}sceneryweb source
{{!}} f = WWW/scenemodels/submission/index.php
{{!}} b = before-server-move
{{!}} full = 1
{{cbr}}.

{{sceneryweb source
| f = WWW/scenemodels/submission/index.php
| b = before-server-move
| full = 1
}}.

=== Numbered parameters ===
This is for https://sourceforge.net/p/flightgear/sceneryweb/ci/before-server-move/tree/WWW/scenemodels/submission/index.php.

{{obr}}sceneryweb source {{!}} WWW/scenemodels/submission/index.php {{!}} b = before-server-move {{!}} full = 1 {{cbr}}.

{{sceneryweb source | WWW/scenemodels/submission/index.php | b = before-server-move | full = 1 }}.

}}</noinclude>