<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.flightgear.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Catalanoic</id>
	<title>FlightGear wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.flightgear.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Catalanoic"/>
	<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/Special:Contributions/Catalanoic"/>
	<updated>2026-05-19T04:20:54Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.6</generator>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User_talk:Mrics&amp;diff=120774</id>
		<title>User talk:Mrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User_talk:Mrics&amp;diff=120774"/>
		<updated>2019-10-28T21:09:46Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Articoli importanti in italiano */ new section&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Welcome to the wiki}}&lt;br /&gt;
&lt;br /&gt;
== Articoli importanti in italiano ==&lt;br /&gt;
&lt;br /&gt;
Ciao, ho visto che sai come scrivere in italiano, vorrei chiederti che se mai hai tempo, puoi [[Translation requests|tradurre alcuni degli articoli contrassegnati come importanti]] da questo wiki in italiano. Non c'è fretta, è un lavoro a lungo termine. Grazie mile! --[[User:Catalanoic|Catalanoic]] ([[User talk:Catalanoic|talk]]) 17:09, 28 October 2019 (EDT)&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=User_talk:Mrics&amp;diff=120773</id>
		<title>User talk:Mrics</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=User_talk:Mrics&amp;diff=120773"/>
		<updated>2019-10-28T21:06:29Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: Created page with &amp;quot;{{Welcome to the wiki}}&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Welcome to the wiki}}&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Pt/Changelog_2.6.0&amp;diff=120675</id>
		<title>Pt/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Pt/Changelog_2.6.0&amp;diff=120675"/>
		<updated>2019-10-12T12:55:07Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
FlightGear 2.6.0 ChangeLog&lt;br /&gt;
&lt;br /&gt;
O time de desenvolvimento do [[FlightGear]] está feliz por anunciar o lançamento da versão 2.6.0 do Flightgear, o simulador grátis de código aberto. &lt;br /&gt;
Essa norva versão contém novas características, melhorias e correções de bugs. Os mais notáveis aperfeiçoamentos em relação à versão 2.4.0 incluem menor tempo para carregar aeronaves IA, ajustes gráficos mais fáceis, inteligência artificial mais sofisticada e melhor usabilidade.&lt;br /&gt;
&lt;br /&gt;
Fundado em 1997, o projeto Flightgear é desenvolvido por um grupo global de voluntários, unidos pela compartilhada ambição de criar o simulador de vôo o mais realista possível que seja livre para usar, modificar e distribuir. O Flightgear é usado em todo o mundo por entusiastas, pesquisadores em universidades, e para exibições interativas em museus.&lt;br /&gt;
&lt;br /&gt;
FLightgear possui mas de 400 aeronaves, um banco de dados de cenário de todo o mundo, um ambiente multiplayer global, modelos detalhados do céu, um sistema aberto e flexível de modelagem de aeronaves, várias opções de rede, suporte a múltiplos displays, uma poderosa linguagem de scripting e arquitetura aberta. E o melhor, ao ter seu código fonte aberto, o simulador é propriedade de toda a comunidade, e todos são encorajados a distribuí-lo.&lt;br /&gt;
&lt;br /&gt;
Faça o download do Flightgear v2.6.0 de graça em [http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Voe livre!&lt;br /&gt;
&lt;br /&gt;
=== Algumas das maiores mudanças são: ===&lt;br /&gt;
&lt;br /&gt;
'''Operações de Aeronaves:'''&lt;br /&gt;
* Em aeroportos selecionados, o Flightgear pode automaticamente iniciar na posição apropriada baseado no tipo e tamanho na sua aeronave.&lt;br /&gt;
* Em aeroportos que suportam essa funcionalidade, um display visual da rota de taxiamento no solo o guia para a pista de decolagem ativa, seguindo o caminho correto.&lt;br /&gt;
&lt;br /&gt;
'''Sistema IA (Inteligência Artificial)'''&lt;br /&gt;
* Para reduzir os &amp;quot;engasgos&amp;quot; durante o carregamento de modelos 3D e visando tirar maior vantagem dos processadores de múltiplos núcleos, as aeronaves dos jogadores e de IA agora são carregadas em segundo plano.&lt;br /&gt;
* Para reduzir mais ainda os tempos de carregamento, apenas as partes atualmente visiveis das aeronaves são carregadas do disco.&lt;br /&gt;
* Aeronaves de IA e de jogadores no modo multiplayer não são mais objetos silenciosos, eles podem produzir sons assim como sua própria aeronave.&lt;br /&gt;
&lt;br /&gt;
'''Tráfego de Aeronaves IA'''&lt;br /&gt;
* Muitos novos e mais recentes esquemas de pintura (liveries) para aeronaves IA. Mais de 80 linhas aéreas agoram povoam os céus virtuais.&lt;br /&gt;
* A distância em que as aeronaves IA são mostradas é agora configurável, permitindo ao usuário ajustar o Flightgear para melhor performance.&lt;br /&gt;
* Os pilotos de aeronaves IA receberam treinamento de pouso e agora fazem a aproximação de modo mais realístico, além de liberarem a pista de pouso quando possível.&lt;br /&gt;
* O simulador agora atribui uma posição de estacionamento livre ao iniciar.&lt;br /&gt;
&lt;br /&gt;
'''Dinâmicas de Vôo'''&lt;br /&gt;
* O modelo de dinâmica de vôo JSBSim recebeu uma notável inspeção.&lt;br /&gt;
&lt;br /&gt;
'''Ambiente'''&lt;br /&gt;
* O pacote &amp;quot;Clima Local&amp;quot; foi melhor integrado ao núcleo do Flightgear, e foi renomeado para, &amp;quot;Clima Avançado&amp;quot;. Novas técnicas de renderização permitem núvens mais detalhados sem impactar a performance. Núvens muito altas são renderizadas de modo mais realístico, e todas as núvens se movem com o vendo, também sem impactar a performance.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* Novo sistema de replay. Controles estilo &amp;quot;video-player&amp;quot;, incluindo câmera lenta e fast forward. Pilotos agora podem controlar a aeronave a qualquer momento durante o replay. Ótimo para treinar certas fases do vôo, como a aproximação, quantas vezes quiser.&lt;br /&gt;
* [[Formalizando o Status da Aeronave|Avaliação do Status da Aeronave]] é mostrada no Flightgear Launcher, permitindo que você veja rapidamente a qualidade do modelo 3D, modelo dinâmico de vôo, sistemas e cockpit para a aeronave selecionada.&lt;br /&gt;
* Configurações multiplayer agora podem ser acessadas dentro do simulador. Você pode escolher seu callsign, selecionar um servidor de multiplayer e conectar, tudo dentro do simulador.&lt;br /&gt;
* Download automático de cenário agora ainda mais fácil de usar. Simplesmente selecione a pasta onde quer salvar o cenário e ative essa opção.&lt;br /&gt;
* Efeitos gráficos individuais agora podem ser configurados dentro da janela de Configurações de Renderização (Rendering Settings), permitindo que você faça ajustes finos na performance ou qualidade visual do Flightgear, de dentro do simulador.&lt;br /&gt;
* A simulação da propagação dos sinais de rádio começou e fará a recepção das mensagens da Torre de Controle de Tráfego Aéreo (ATC) e de navaids (apoio a navegação) mais realistas no futuro.&lt;br /&gt;
* Um novo conjunto de opções facilita a criação de setups de com vários monitores (com opções de zoom).&lt;br /&gt;
* Um novo monitor de performance mostra o tempo despendido em cada subsistema.&lt;br /&gt;
&lt;br /&gt;
'''Destaque de aeronaves novas ou melhoradas'''&lt;br /&gt;
* [[A-26 Invader]]: melhorias no cockpit.&lt;br /&gt;
* [[Boeing 777-200ER]]: muitas novas e melhoradas características, incluindo o piloto automático, displays de instrumentos e animações.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: melhorias no cockpit.&lt;br /&gt;
&lt;br /&gt;
'''Infraestrutura de Projeto'''&lt;br /&gt;
* O CMake agora é o sistema de build oficial no Linux, Mac e Windows.&lt;br /&gt;
&lt;br /&gt;
'''Efeitos Visuais'''&lt;br /&gt;
* O mar agora é mais realístico. As ondas de alinham com o vento, e espuma aparece com ventos fortes.&lt;br /&gt;
* Encostas íngremes agora são rochosas.&lt;br /&gt;
* Pistas de pouso e decolagem ficam molhadas com a chuva.&lt;br /&gt;
* Para ajudar desenvolvedores de aeronaves, um único shader combinando componentes bump-map, especular, reflexão e mapeamento de luz está disponível.&lt;br /&gt;
&lt;br /&gt;
'''Outros'''&lt;br /&gt;
* Mais joysticks e pedais de leme são compatíveis, incluindo o Logitech WingMan Interceptor, o Saitek Pro Combat Rudder Pedals e o Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], software leve para renderizar painéis de instrumentos 2D, agora incluso como parte do lançamento.&lt;br /&gt;
&lt;br /&gt;
'''Correções de Bugs'''&lt;br /&gt;
* Veja [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 nosso bugtracker] para uma extensa lista de bugs que foram corrigidos para este lançamento.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* Versão 64bit restaurada e sua instalação integrada ao instalador principal fgsetp&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[es:Changelog 2.6.0]]&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Br/Changelog_2.6.0&amp;diff=120674</id>
		<title>Br/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Br/Changelog_2.6.0&amp;diff=120674"/>
		<updated>2019-10-12T12:53:30Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
{{Draft|changelog|''Não deve ser (ainda) visto como documento oficial''.}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
FlightGear 2.6.0 ChangeLog&lt;br /&gt;
&lt;br /&gt;
O time de desenvolvimento do [[FlightGear]] está feliz por anunciar o lançamento da versão 2.6.0 do Flightgear, o simulador grátis de código aberto. &lt;br /&gt;
Essa norva versão contém novas características, melhorias e correções de bugs. Os mais notáveis aperfeiçoamentos em relação à versão 2.4.0 incluem menor tempo para carregar aeronaves IA, ajustes gráficos mais fáceis, inteligência artificial mais sofisticada e melhor usabilidade.&lt;br /&gt;
&lt;br /&gt;
Fundado em 1997, o projeto Flightgear é desenvolvido por um grupo global de voluntários, unidos pela compartilhada ambição de criar o simulador de vôo o mais realista possível que seja livre para usar, modificar e distribuir. O Flightgear é usado em todo o mundo por entusiastas, pesquisadores em universidades, e para exibições interativas em museus.&lt;br /&gt;
&lt;br /&gt;
FLightgear possui mas de 400 aeronaves, um banco de dados de cenário de todo o mundo, um ambiente multiplayer global, modelos detalhados do céu, um sistema aberto e flexível de modelagem de aeronaves, várias opções de rede, suporte a múltiplos displays, uma poderosa linguagem de scripting e arquitetura aberta. E o melhor, ao ter seu código fonte aberto, o simulador é propriedade de toda a comunidade, e todos são encorajados a distribuí-lo.&lt;br /&gt;
&lt;br /&gt;
Faça o download do Flightgear v2.6.0 de graça em [http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Voe livre!&lt;br /&gt;
&lt;br /&gt;
=== Algumas das maiores mudanças são: ===&lt;br /&gt;
&lt;br /&gt;
'''Operações de Aeronaves:'''&lt;br /&gt;
* Em aeroportos selecionados, o Flightgear pode automaticamente iniciar na posição apropriada baseado no tipo e tamanho na sua aeronave.&lt;br /&gt;
* Em aeroportos que suportam essa funcionalidade, um display visual da rota de taxiamento no solo o guia para a pista de decolagem ativa, seguindo o caminho correto.&lt;br /&gt;
&lt;br /&gt;
'''Sistema IA (Inteligência Artificial)'''&lt;br /&gt;
* Para reduzir os &amp;quot;engasgos&amp;quot; durante o carregamento de modelos 3D e visando tirar maior vantagem dos processadores de múltiplos núcleos, as aeronaves dos jogadores e de IA agora são carregadas em segundo plano.&lt;br /&gt;
* Para reduzir mais ainda os tempos de carregamento, apenas as partes atualmente visiveis das aeronaves são carregadas do disco.&lt;br /&gt;
* Aeronaves de IA e de jogadores no modo multiplayer não são mais objetos silenciosos, eles podem produzir sons assim como sua própria aeronave.&lt;br /&gt;
&lt;br /&gt;
'''Tráfego de Aeronaves IA'''&lt;br /&gt;
* Muitos novos e mais recentes esquemas de pintura (liveries) para aeronaves IA. Mais de 80 linhas aéreas agoram povoam os céus virtuais.&lt;br /&gt;
* A distância em que as aeronaves IA são mostradas é agora configurável, permitindo ao usuário ajustar o Flightgear para melhor performance.&lt;br /&gt;
* Os pilotos de aeronaves IA receberam treinamento de pouso e agora fazem a aproximação de modo mais realístico, além de liberarem a pista de pouso quando possível.&lt;br /&gt;
* O simulador agora atribui uma posição de estacionamento livre ao iniciar.&lt;br /&gt;
&lt;br /&gt;
'''Dinâmicas de Vôo'''&lt;br /&gt;
* O modelo de dinâmica de vôo JSBSim recebeu uma notável inspeção.&lt;br /&gt;
&lt;br /&gt;
'''Ambiente'''&lt;br /&gt;
* O pacote &amp;quot;Clima Local&amp;quot; foi melhor integrado ao núcleo do Flightgear, e foi renomeado para, &amp;quot;Clima Avançado&amp;quot;. Novas técnicas de renderização permitem núvens mais detalhados sem impactar a performance. Núvens muito altas são renderizadas de modo mais realístico, e todas as núvens se movem com o vendo, também sem impactar a performance.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* Novo sistema de replay. Controles estilo &amp;quot;video-player&amp;quot;, incluindo câmera lenta e fast forward. Pilotos agora podem controlar a aeronave a qualquer momento durante o replay. Ótimo para treinar certas fases do vôo, como a aproximação, quantas vezes quiser.&lt;br /&gt;
* [[Formalizando o Status da Aeronave|Avaliação do Status da Aeronave]] é mostrada no Flightgear Launcher, permitindo que você veja rapidamente a qualidade do modelo 3D, modelo dinâmico de vôo, sistemas e cockpit para a aeronave selecionada.&lt;br /&gt;
* Configurações multiplayer agora podem ser acessadas dentro do simulador. Você pode escolher seu callsign, selecionar um servidor de multiplayer e conectar, tudo dentro do simulador.&lt;br /&gt;
* Download automático de cenário agora ainda mais fácil de usar. Simplesmente selecione a pasta onde quer salvar o cenário e ative essa opção.&lt;br /&gt;
* Efeitos gráficos individuais agora podem ser configurados dentro da janela de Configurações de Renderização (Rendering Settings), permitindo que você faça ajustes finos na performance ou qualidade visual do Flightgear, de dentro do simulador.&lt;br /&gt;
* A simulação da propagação dos sinais de rádio começou e fará a recepção das mensagens da Torre de Controle de Tráfego Aéreo (ATC) e de navaids (apoio a navegação) mais realistas no futuro.&lt;br /&gt;
* Um novo conjunto de opções facilita a criação de setups de com vários monitores (com opções de zoom).&lt;br /&gt;
* Um novo monitor de performance mostra o tempo despendido em cada subsistema.&lt;br /&gt;
&lt;br /&gt;
'''Destaque de aeronaves novas ou melhoradas'''&lt;br /&gt;
* [[A-26 Invader]]: melhorias no cockpit.&lt;br /&gt;
* [[Boeing 777-200ER]]: muitas novas e melhoradas características, incluindo o piloto automático, displays de instrumentos e animações.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: melhorias no cockpit.&lt;br /&gt;
&lt;br /&gt;
'''Navegação'''&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
'''Infraestrutura de Projeto'''&lt;br /&gt;
* O CMake agora é o sistema de build oficial no Linux, Mac e Windows.&lt;br /&gt;
&lt;br /&gt;
'''Melhorias de Cenário'''&lt;br /&gt;
* Cenário detalhado disponível para várias áreas da Europa, baseado nos dados CORINE.&lt;br /&gt;
&lt;br /&gt;
'''Efeitos Visuais'''&lt;br /&gt;
* O mar agora é mais realístico. As ondas de alinham com o vento, e espuma aparece com ventos fortes.&lt;br /&gt;
* Encostas íngremes agora são rochosas.&lt;br /&gt;
* Pistas de pouso e decolagem ficam molhadas com a chuva.&lt;br /&gt;
* Para ajudar desenvolvedores de aeronaves, um único shader combinando componentes bump-map, especular, reflexão e mapeamento de luz está disponível.&lt;br /&gt;
* O céu é agora mais realístico devido à um melhorado shader da cúpula celeste.&lt;br /&gt;
&lt;br /&gt;
'''Outros'''&lt;br /&gt;
* Mais joysticks e pedais de leme são compatíveis, incluindo o Logitech WingMan Interceptor, o Saitek Pro Combat Rudder Pedals e o Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], software leve para renderizar painéis de instrumentos 2D, agora incluso como parte do lançamento.&lt;br /&gt;
&lt;br /&gt;
'''Correções de Bugs'''&lt;br /&gt;
* Veja [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 our bugtracker] para uma extensa lista de bugs que foram corrigidos para este lançamento.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* Versão 64bit restaurada e sua instalação integrada ao instalador principal fgsetp&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ro/Changelog_2.6.0&amp;diff=120673</id>
		<title>Ro/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ro/Changelog_2.6.0&amp;diff=120673"/>
		<updated>2019-10-12T12:53:04Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
FlightGear 2.6.0 ChangeLog&lt;br /&gt;
&lt;br /&gt;
Echipa de dezvoltare [[FlightGear]] este încântată să anunțe publicarea versiunii 2.6.0 a simulatorului de zbor, liber, open-source, FlightGear.&lt;br /&gt;
Această nouă versiune conține multe aspecte captivante, noutăți și corectări.&lt;br /&gt;
Îmbunătățirile majore față de v2.4.0 includ&lt;br /&gt;
timp de încărcare scurtat pentru avioanele AI, reglaj mai ușor al opțiunilor de afișare, AI mai sofisticat și ergonomie mai bună.&lt;br /&gt;
&lt;br /&gt;
Fondat în 1997, FlightGear este dezvoltat de către un grup internațional de voluntari, aduși laolaltă de ambiția comună de a crea cel mai realistic simulator de zbor, care poate fi folosit, modificat și distribuit în mod liber. FlightGear este folosit în întreaga lume de către împătimiții de simulatoare de zbor, pentru cercetare în mediul universitar și pentru exponate interactive în muzee.&lt;br /&gt;
&lt;br /&gt;
FlightGear prezintă mai mult de 400 de aparate de zbor, o bază de date a terenului întregii lumi, un mediu multiplayer global, modelare detaliată a cerului, un sistem flexibil și deschis de modelare a aparatelor de zbor, variate opțiuni de conectare în rețea, suport multi-afișaj, un limbaj de scriptare puternic și o arhitectură deschisă. Mai mult decât atât, datorită faptului că este open-source, simulatorul este deținut de către comunitate și toți sunt încurajați să-și aducă contribuția.&lt;br /&gt;
&lt;br /&gt;
Descărcați FlightGear v2.6.0 liber de la [http://www.flightgear.org FlightGear.org].&lt;br /&gt;
&lt;br /&gt;
FlightGear - Zboară liber!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Some of the major changes include: ===&lt;br /&gt;
&lt;br /&gt;
'''Aircraft operations:'''&lt;br /&gt;
* At selected airports, FlightGear can automatically start at an appropriate parking spot based on the size and type of your aircraft. &lt;br /&gt;
* At airports which support this feature, a visual display of the taxi route on the ground guides you to the active runway, while following the correct taxiways.&lt;br /&gt;
&lt;br /&gt;
'''AI system'''&lt;br /&gt;
* To reduce stuttering during model loading and take further advantage of multi-core CPUs, MP and AI aircraft models are now loaded in a background thread.&lt;br /&gt;
* To reduce load times still further, only the parts of the aircraft currently visible are loaded from disk. &lt;br /&gt;
* AI and multiplayer aircraft are no longer silent objects, they can produce sounds just like the main aircraft.&lt;br /&gt;
&lt;br /&gt;
'''AI Traffic'''&lt;br /&gt;
* Many new and updated AI aircraft and liveries. Over 80 airlines now populate the virtual skies.&lt;br /&gt;
* The range at which AI aircraft are displayed is now configurable, allowing you to tune FlightGear for best performance.&lt;br /&gt;
* AI controlled pilots have received extensive landing training and now make a more realistic approach and vacate the runway when able.&lt;br /&gt;
* The simulator now assigns an available parking position on startup.&lt;br /&gt;
&lt;br /&gt;
'''Flight dynamics'''&lt;br /&gt;
* The JSBSim flight dynamics model received a major overhaul.&lt;br /&gt;
&lt;br /&gt;
'''Environment'''&lt;br /&gt;
* The Local Weather package has been further integrated with the FlightGear core, and has been renamed &amp;quot;Advanced Weather&amp;quot;. New rendering techniques allow more detailed clouds with no performance impact. High altitude clouds are rendered more realistically, and clouds move with the wind without impacting performance.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* New replay system. Video-player like controls, including slow motion and fast forward. Pilots can now take over the aircraft at any time during a replay. Great for training particular flight phases such as approach over and over again.&lt;br /&gt;
* [[Formalizing Aircraft Status|Aircraft status ratings]] are displayed in the FlightGear launcher, allowing you to see at a glance the FDM, model, systems and cockpit quality for rated aircraft.&lt;br /&gt;
* Multiplayer settings can be accessed in-sim.  You can now choose your callsign, select an MP server and connect within the simulator.&lt;br /&gt;
* Automatic scenery download is now even easier to use. Simply select the scenery directory to download to, and switch it on.&lt;br /&gt;
* Individual graphics effects can now be configured from within the Rendering Settings dialog, allowing you to fine-tune the performance of FlightGear within the sim.&lt;br /&gt;
* The simulation of radio signal propagation has started and will make the reception of ATC messages and navigation aids more realistic in the future.&lt;br /&gt;
* A new set of options makes it easier to create seamless and zoomable multi screen setups.&lt;br /&gt;
* A new performance monitor shows the time spent in each subsystem.&lt;br /&gt;
&lt;br /&gt;
'''Highlighted new and improved aircraft'''&lt;br /&gt;
* [[A-26 Invader]]: cockpit improvements.&lt;br /&gt;
* [[Boeing 777-200ER]]: many additional and updated features, including autopilot, instrument displays and animations.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: cockpit improvements.&lt;br /&gt;
&lt;br /&gt;
'''Navigation'''&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
'''Project infrastructure'''&lt;br /&gt;
* CMake is now the official build system on Linux, Mac and Windows.&lt;br /&gt;
&lt;br /&gt;
'''Scenery improvements'''&lt;br /&gt;
* Detailed scenery is available for various areas in Europe, based on the CORINE data set.&lt;br /&gt;
&lt;br /&gt;
'''Visual effects'''&lt;br /&gt;
* The sea now looks more realistic. Waves align with the wind, and foam appears at high wind speed.&lt;br /&gt;
* Steep slopes now appear rocky.&lt;br /&gt;
* Runways now appear wet during rain showers.&lt;br /&gt;
* To help aircraft developers, a single shader combining bump-map, specular, reflection and light mapping components is now available. &lt;br /&gt;
&lt;br /&gt;
'''Other'''&lt;br /&gt;
* Additional joysticks and rudder pedals are supported out-of-the-box, including the Logitech WingMan Interceptor, Saitek Pro Combat Rudder Pedals and Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], lightweight software to render 2D instrument panels, is now included as part of the release.&lt;br /&gt;
&lt;br /&gt;
'''Bug fixes'''&lt;br /&gt;
* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 our bugtracker] for an extensive list of the bugs fixed in this release.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* 64bit version restored and its installation integrated in the main fgsetup installer&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Nl/Changelog_2.6.0&amp;diff=120672</id>
		<title>Nl/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Nl/Changelog_2.6.0&amp;diff=120672"/>
		<updated>2019-10-12T12:52:42Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br/&amp;gt;&lt;br /&gt;
Het FlightGear team presenteert met trots de v2.6.0 release van FlightGear, dé gratis, opensource flight simulator.&lt;br /&gt;
Deze nieuwe versie bevat veel nieuwe functies, verbeteringen en bugfixes. Belangrijke verbeteringen ten opzichte van v2.4.0 zijn onder andere een korte AI laadtijd, eenvoudiger in te stellen graphics, geavenceerdere robot vliegtuigen en verbeterde bruikbaarheid.&lt;br /&gt;
&lt;br /&gt;
Opgericht in 1997, FlightGear wordt ontwikkeld door een wereldwijde groep van vrijwillgers, bijeengebracht door een gedeelde ambitie om de meest realistische flight simulator te ontwikkelen, die gratis te gebruiken is en vrij kan worden aangepast en verspreidt. FlightGear wordt over de hele wereld gebruikt door flight simulator enthousiastelingen, universiteiten en interactieve tentoonstellingen in musea.&lt;br /&gt;
&lt;br /&gt;
Er zijn meer dan 400 vliegtuigen beschikbaar voor FlightGear, een wereld omvattende database, multiplayer omgeving, gedetailleerde weergave van de lucht, een flexibel en open systeem om vliegtuigen te ontwikkelen, verscheidene netwerk opties, ondersteuning voor meerdere beeldschermen, een krachtige scripting taal en een open opzet. Maar het beste van alles is dat de simulator eigendom is van de gemeenschap en iedereen welkom is om bij te dragen.&lt;br /&gt;
&lt;br /&gt;
Download FlightGear v2.6.0 gratis van[http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Fly Free!&lt;br /&gt;
&lt;br /&gt;
=== Enkele van de belangrijkste wijzigingen: ===&lt;br /&gt;
&lt;br /&gt;
'''Vliegtuig operaties:'''&lt;br /&gt;
* Op een aantal vliegvelden kan FlightGear automatisch een gate uitkiezen, afhankelijk van het formaat en type van je vliegtuig.&lt;br /&gt;
* Vliegveld die deze functie ondersteunen kunnen je door middel van een zwevende lijn via een correcte taxi route naar de huidige startbaan leiden.&lt;br /&gt;
&lt;br /&gt;
'''AI systeem'''&lt;br /&gt;
* Multiplay en robot vliegtuigen worden geladen in een achtergrond thread om schokkerige beelden te voorkomen tijden het laden van modelen en om meer gebruik te maken van multi-core CPUs.&lt;br /&gt;
* Om laadtijden nog meer te verkorten worden alleen onderdelen die ook echt zichtbaar zijn geladen.&lt;br /&gt;
* Robot en multiplay vleigtuigen zijn niet langer zwijgende objecten, ze kunnen nu net zulke geluiden produceren als je eigen vliegtuig.&lt;br /&gt;
&lt;br /&gt;
'''Robot verkeer'''&lt;br /&gt;
* Veel nieuwe en betere robot vliegtuigen en liveries. Meer dan 80 luchtvaartmaatschappijen bevolken nu de virtuele lucht.&lt;br /&gt;
* De afstand waarop robot vliegtuigen zichtbaar zijn is nu in te stellen, zodat je FlightGear's prestaties nog beter kunt aanpassen.&lt;br /&gt;
* Robot piloten hebben uitgebreide training gekregen om realistischere naderingen te maken en de landingsbaan te verlaten zodra dat mogelijk is.&lt;br /&gt;
* De simulator plaatst niet langer twee vliegtuigen bij één gate.&lt;br /&gt;
&lt;br /&gt;
'''Vlucht modellen'''&lt;br /&gt;
* Het JSBSim vlucht model heeft een aantal belangijke updates gekregen.&lt;br /&gt;
&lt;br /&gt;
'''Omgeving'''&lt;br /&gt;
* Het &amp;quot;Local Weather&amp;quot; systeem is verder geintegreerd met de FlightGear core en heet nu &amp;quot;Advanced Weather&amp;quot;. Nieuwe weergave technieken maken het mogelijk om gedetaileerdere wolken weer te geven met dezelfde prestaties. Wolken op grote hoogte zien er realistischer uit en bewegen mee met de wind zonder invleod op de prestaties.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* Nieuwe herhaal systeem met videorecorder-achtige besturing inclusief slow motion en vooruitspoelen. Piloten kunnen op elk moment de controle over het vliegtuig overnemen; ideaal om bepaalde delen van een vlucht, zoals naderingen, herhaaldelijk te oefenen.&lt;br /&gt;
* De FlightGear Wizard geeft nu van een aantal vliegtuigen de status weer. Je kunt in één oogopslag zien hoe compleet de FDM, model, system en cockpit van een vliegtuig zijn.&lt;br /&gt;
* Multiplayer opties zijn nu direct in de simulator aan te passen. Zo kun je je callsign en server wijzigen of offline gaan.&lt;br /&gt;
* Je kunt nu gemakkelijker dan ooit automatisch scenery downloaden. Je hoeft enkel de map waar alles naar toe gedownload wordt te kiezen en het systeem aan te zetten.&lt;br /&gt;
* Invidivuele grafische effecten kunnen in het Rendering Settings venster aangepast worden, waardoor je de prestaties van FlightGear eenvoudig kunt verbeteren.&lt;br /&gt;
* The simulation of radio signal propagation has started and will make the reception of ATC messages and navigation aids more realistic in the future.&lt;br /&gt;
* Een nieuw setje instellingen maakt het makkelijker om naadloos meerder schermen aan elkaar te koppelen.&lt;br /&gt;
* Een prestatiemeter toont de tijd die elk systeem gebruikt.&lt;br /&gt;
&lt;br /&gt;
'''Opvallende nieuwe en verbeterde vleigtuigen'''&lt;br /&gt;
* [[A-26 Invader]]: cockpit verbeteringen.&lt;br /&gt;
* [[Boeing 777-200ER]]: veel extra en verbeterede functionaliteiten, waaronder de automatische pilot, instrumenten en animaties.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: cockpit verbeteringen.&lt;br /&gt;
&lt;br /&gt;
'''Project infrastructuur'''&lt;br /&gt;
* CMake is nu het officiële build systeem voor Linux, Mac en Windows.&lt;br /&gt;
&lt;br /&gt;
'''Grafische effecten'''&lt;br /&gt;
* De zee ziet er nu realistischer uit. Golven richten zich naar de wind en bij hoge windsnelheden zijn schuimkoppen zichtbaar.&lt;br /&gt;
* Steile hellingen zien er rotsachtig uit.&lt;br /&gt;
* Startbanen worden nat tijdens regenbuien.&lt;br /&gt;
* Om ontwikkelaars van vliegtuigen te helpen is er één enkele shader beschikbaar die bumpmap, reflecties en lightmaps combineerd.&lt;br /&gt;
&lt;br /&gt;
'''Overig'''&lt;br /&gt;
* Extra joysticks en pedalen worden out-of-the-box ondersteunt, onderandere de Logitech WingMan Interceptor, Saitek Pro Combat Rudder Pedals en Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], een licht gewicht programme om 2D instrumentenpanelen te tonen, is bij de release inbegrepen.&lt;br /&gt;
&lt;br /&gt;
'''Bug fixes'''&lt;br /&gt;
* Zie [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 onze bug tracker] voor een uitgebreide lijst van opgeloste problemen in deze versie.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* De 64 bits versie is opnieuw beschikbaar en de installie is geintegreerd in de fgsetup installateur.&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[es:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ro/Changelog_2.6.0&amp;diff=120671</id>
		<title>Ro/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ro/Changelog_2.6.0&amp;diff=120671"/>
		<updated>2019-10-12T12:51:58Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
FlightGear 2.6.0 ChangeLog&lt;br /&gt;
&lt;br /&gt;
Echipa de dezvoltare [[FlightGear]] este încântată să anunțe publicarea versiunii 2.6.0 a simulatorului de zbor, liber, open-source, FlightGear.&lt;br /&gt;
Această nouă versiune conține multe aspecte captivante, noutăți și corectări.&lt;br /&gt;
Îmbunătățirile majore față de v2.4.0 includ&lt;br /&gt;
timp de încărcare scurtat pentru avioanele AI, reglaj mai ușor al opțiunilor de afișare, AI mai sofisticat și ergonomie mai bună.&lt;br /&gt;
&lt;br /&gt;
Fondat în 1997, FlightGear este dezvoltat de către un grup internațional de voluntari, aduși laolaltă de ambiția comună de a crea cel mai realistic simulator de zbor, care poate fi folosit, modificat și distribuit în mod liber. FlightGear este folosit în întreaga lume de către împătimiții de simulatoare de zbor, pentru cercetare în mediul universitar și pentru exponate interactive în muzee.&lt;br /&gt;
&lt;br /&gt;
FlightGear prezintă mai mult de 400 de aparate de zbor, o bază de date a terenului întregii lumi, un mediu multiplayer global, modelare detaliată a cerului, un sistem flexibil și deschis de modelare a aparatelor de zbor, variate opțiuni de conectare în rețea, suport multi-afișaj, un limbaj de scriptare puternic și o arhitectură deschisă. Mai mult decât atât, datorită faptului că este open-source, simulatorul este deținut de către comunitate și toți sunt încurajați să-și aducă contribuția.&lt;br /&gt;
&lt;br /&gt;
Descărcați FlightGear v2.6.0 liber de la [http://www.flightgear.org FlightGear.org].&lt;br /&gt;
&lt;br /&gt;
FlightGear - Zboară liber!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Some of the major changes include: ===&lt;br /&gt;
&lt;br /&gt;
'''Aircraft operations:'''&lt;br /&gt;
* At selected airports, FlightGear can automatically start at an appropriate parking spot based on the size and type of your aircraft. &lt;br /&gt;
* At airports which support this feature, a visual display of the taxi route on the ground guides you to the active runway, while following the correct taxiways.&lt;br /&gt;
&lt;br /&gt;
'''AI system'''&lt;br /&gt;
* To reduce stuttering during model loading and take further advantage of multi-core CPUs, MP and AI aircraft models are now loaded in a background thread.&lt;br /&gt;
* To reduce load times still further, only the parts of the aircraft currently visible are loaded from disk. &lt;br /&gt;
* AI and multiplayer aircraft are no longer silent objects, they can produce sounds just like the main aircraft.&lt;br /&gt;
&lt;br /&gt;
'''AI Traffic'''&lt;br /&gt;
* Many new and updated AI aircraft and liveries. Over 80 airlines now populate the virtual skies.&lt;br /&gt;
* The range at which AI aircraft are displayed is now configurable, allowing you to tune FlightGear for best performance.&lt;br /&gt;
* AI controlled pilots have received extensive landing training and now make a more realistic approach and vacate the runway when able.&lt;br /&gt;
* The simulator now assigns an available parking position on startup.&lt;br /&gt;
&lt;br /&gt;
'''Flight dynamics'''&lt;br /&gt;
* The JSBSim flight dynamics model received a major overhaul.&lt;br /&gt;
&lt;br /&gt;
'''Environment'''&lt;br /&gt;
* The Local Weather package has been further integrated with the FlightGear core, and has been renamed &amp;quot;Advanced Weather&amp;quot;. New rendering techniques allow more detailed clouds with no performance impact. High altitude clouds are rendered more realistically, and clouds move with the wind without impacting performance.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* New replay system. Video-player like controls, including slow motion and fast forward. Pilots can now take over the aircraft at any time during a replay. Great for training particular flight phases such as approach over and over again.&lt;br /&gt;
* [[Formalizing Aircraft Status|Aircraft status ratings]] are displayed in the FlightGear launcher, allowing you to see at a glance the FDM, model, systems and cockpit quality for rated aircraft.&lt;br /&gt;
* Multiplayer settings can be accessed in-sim.  You can now choose your callsign, select an MP server and connect within the simulator.&lt;br /&gt;
* Automatic scenery download is now even easier to use. Simply select the scenery directory to download to, and switch it on.&lt;br /&gt;
* Individual graphics effects can now be configured from within the Rendering Settings dialog, allowing you to fine-tune the performance of FlightGear within the sim.&lt;br /&gt;
* The simulation of radio signal propagation has started and will make the reception of ATC messages and navigation aids more realistic in the future.&lt;br /&gt;
* A new set of options makes it easier to create seamless and zoomable multi screen setups.&lt;br /&gt;
* A new performance monitor shows the time spent in each subsystem.&lt;br /&gt;
&lt;br /&gt;
'''Highlighted new and improved aircraft'''&lt;br /&gt;
* [[A-26 Invader]]: cockpit improvements.&lt;br /&gt;
* [[Boeing 777-200ER]]: many additional and updated features, including autopilot, instrument displays and animations.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: cockpit improvements.&lt;br /&gt;
&lt;br /&gt;
'''Navigation'''&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
'''Project infrastructure'''&lt;br /&gt;
* CMake is now the official build system on Linux, Mac and Windows.&lt;br /&gt;
&lt;br /&gt;
'''Scenery improvements'''&lt;br /&gt;
* Detailed scenery is available for various areas in Europe, based on the CORINE data set.&lt;br /&gt;
&lt;br /&gt;
'''Visual effects'''&lt;br /&gt;
* The sea now looks more realistic. Waves align with the wind, and foam appears at high wind speed.&lt;br /&gt;
* Steep slopes now appear rocky.&lt;br /&gt;
* Runways now appear wet during rain showers.&lt;br /&gt;
* To help aircraft developers, a single shader combining bump-map, specular, reflection and light mapping components is now available. &lt;br /&gt;
&lt;br /&gt;
'''Other'''&lt;br /&gt;
* Additional joysticks and rudder pedals are supported out-of-the-box, including the Logitech WingMan Interceptor, Saitek Pro Combat Rudder Pedals and Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], lightweight software to render 2D instrument panels, is now included as part of the release.&lt;br /&gt;
&lt;br /&gt;
'''Bug fixes'''&lt;br /&gt;
* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 our bugtracker] for an extensive list of the bugs fixed in this release.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* 64bit version restored and its installation integrated in the main fgsetup installer&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Fr/Changelog_2.6.0&amp;diff=120670</id>
		<title>Fr/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Fr/Changelog_2.6.0&amp;diff=120670"/>
		<updated>2019-10-12T12:51:52Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
==Liste des amélioration de FlightGear v2.6.0==&lt;br /&gt;
&lt;br /&gt;
L'équipe de développement de FlightGear a le plaisir d'annoncer la sortie de la version 2.6.0 de FlightGear, le simulateur de vol libre et gratuit. Cette nouvelle version contient de nombreuses et passionnantes nouvelles fonctionnalités. Les évolutions majeures par rapport à la version 2.4.0 comprennent des temps de chargement réduits pour les avions gérés par le système d'intelligence artificielle (avions qui deviennent également plus sophistiqués), des performances graphiques plus facilement personnalisables et une plus grande facilité d'utilisation.&lt;br /&gt;
&lt;br /&gt;
Créé en 1997, FlightGear est développé par un groupe de volontaires du monde entier, dont l'ambition commune est de créer le simulateur de vol le plus réaliste possible, libre d'utilisation, de modification et de distribution. FlightGear est utilisé dans le monde entier par des amateurs de simulation de vol, des unités de recherche dans les universités ou pour des expositions interactives dans des musées.&lt;br /&gt;
&lt;br /&gt;
FlightGear propose plus de 400 avions, une base de données de scènes mondiale, une modélisation détaillée du ciel, un système de modélisation ouvert pour les avions, différentes options de connectivité réseau, la prise en charge du multi-écrans, un langage de script puissant et une architecture ouverte. Encore mieux, étant libre, le simulateur est la propriété d'une communauté à laquelle chacun est encouragé à contribuer.&lt;br /&gt;
&lt;br /&gt;
Téléchargez FlightGear v2.6.0 gratuitement à partir de http://www.flightgear.org&lt;br /&gt;
&lt;br /&gt;
FlightGear - Le vol libre !&lt;br /&gt;
&lt;br /&gt;
=== Quelques unes des principales évolutions : ===&lt;br /&gt;
&lt;br /&gt;
'''Utilisation des aéronefs:'''&lt;br /&gt;
* Sur certains aéroports, FlightGear peut démarrer automatiquement à un point de parking approprié en fonction de la taille et du type de votre aéronef.&lt;br /&gt;
&lt;br /&gt;
'''Système d'intelligence artificielle (AI)'''&lt;br /&gt;
* Pour réduire la latence durant le chargement des modèles d'aéronefs et améliorer l'utilisation des CPU multi-coeurs, les modèles d'avions multijoueurs et AI sont dorénavant chargés dans un processus en fond de tâche.&lt;br /&gt;
* Pour réduire encore plus la charge, seules les parties de l'avion réellement visibles sont chargées depuis le disque.&lt;br /&gt;
* Les aéronefs &amp;quot;AI&amp;quot; et multijoueurs ne sont désormais plus des objets silencieux ! Ils peuvent produire des sons juste tout comme les aéronefs classiques.&lt;br /&gt;
&lt;br /&gt;
'''Trafic AI'''&lt;br /&gt;
* Nombreux avions &amp;quot;AI&amp;quot; nouveaux ou mis à jour, ainsi que leurs livrées. Plus de 80 compagnies se côtoient dorénavant dans nos cieux virtuels.&lt;br /&gt;
* La distance à laquelle les aéronefs AI sont visibles est désormais configurable, vous permettant d'adapter FlightGear pour une meilleure performance.&lt;br /&gt;
* Les pilotes d'aéronefs &amp;quot;AI&amp;quot; ont reçu un entraînement poussé à l'atterrissage et peuvent dorénavant réaliser des approches plus réalistes et libérer les pistes dès que possible ;-)&lt;br /&gt;
* Le simulteur attribue dorénavant les positions de parking disponibles au démarrage.&lt;br /&gt;
&lt;br /&gt;
'''Dynamique de vol'''&lt;br /&gt;
* Le modèle de dynamique de vol JSBSim a fait l'objet d'évolutions majeures.&lt;br /&gt;
&lt;br /&gt;
'''Environnement'''&lt;br /&gt;
* Le paquet logiciel &amp;quot;Local Weather&amp;quot; a été intégré de manière plus complète dans le coeur de FlightGear et a été renommé &amp;quot;Avanced Weather&amp;quot; (météorologie avancée). Des nouvelles techniques de rendu permettent d'obtenir des nuages plus détaillés sans impact sur la performance. Les nuages de haute altitude sont restitués de manière plus réaliste et les nuages évoluent avec le vent, toujours sans impact sur la performance.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* Nouveau système de rejeu. Des contrôles semblables à ceux d'un lecteur vidéo, comprenant le ralenti et la lecture accélérée. Les pilotes peuvent maintenant reprendre main sur l'avion à l'importe quel moment du rejeu. Ceci est particulièrement appréciable pour s'entraîner encore et encore sur des phases particulières du vol, comme l'approche.&lt;br /&gt;
* [[Formalizing Aircraft Status|Les informations du statut des aéronefs]] sont dorénavant affichées dans le lanceur de FlightGear, vous permettant d'un coup d'oeil de visualiser la qualité du modèle de vol, du modèle du 3D, des systèmes et du cockpit.&lt;br /&gt;
* Les paramètres multijoueurs peuvent être accédés directement depuis le simulateur. Vous pouvez dorénavant choisir votre indicatif, votre serveur multijoueurs et vous connecter directement depuis le simulaleur.&lt;br /&gt;
* Le téléchargement automatique des scènes est maintenant encore plus simple : il suffit de choisir le répertoire de destination où les scènes seront téléchargées, puis d'activer le téléchargement.&lt;br /&gt;
* Des effets graphiques individuels peuvent être configurés à partir du menu &amp;quot;Rendering Settings&amp;quot; dialog, vous permettant d'ajuster les performances de FlightGear directement depuis le simulateur.&lt;br /&gt;
* La simulation de propagation des signaux radio a débuté et permettra de rendre la réception des messages du contrôle aérien et de la navigation plus réalistes dans le futur.&lt;br /&gt;
* Un nouveau jeu d'options permet de faciliter la configuration d'écrans multiples et zoomables.&lt;br /&gt;
* Un nouveau moniteur de performances permet de montrer le temps passé dans chaque sous-système.&lt;br /&gt;
&lt;br /&gt;
'''Aéronefs nouveaux ou améliorés à tester impérativement !'''&lt;br /&gt;
* [[A-26 Invader]] : améliorations du cockpit.&lt;br /&gt;
* [[Boeing 777-200ER]] : de nombreuses fonctions nouvelles ou améliorées, comme le pilote automatique et les animations.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]].&lt;br /&gt;
* [[Polikarpov I16]] : améliorations du cockpit.&lt;br /&gt;
&lt;br /&gt;
'''Infrastructure du projet'''&lt;br /&gt;
* CMake est dorénavant le système de compilation officiel du système sur Linux, Mac et Windows.&lt;br /&gt;
&lt;br /&gt;
'''Effets visuels'''&lt;br /&gt;
* La mer a dorénavant une apparence plus réaliste. Les vagues sont alignées avec le vent et de l'écume apparaît lorsque le vent forcit !&lt;br /&gt;
* Les falaises ont maintenant une apparence rocheuse.&lt;br /&gt;
* Les pistes apparaissent mouillées durant les averses de pluie.&lt;br /&gt;
* Afin d'aider les développeurs d'avions, un shader unique combinant les effets &amp;quot;bump-map&amp;quot;, &amp;quot;specular&amp;quot;, &amp;quot;reflection&amp;quot; et &amp;quot;light mapping&amp;quot; est maintenant disponible. &lt;br /&gt;
&lt;br /&gt;
'''Autres'''&lt;br /&gt;
* De nouveaux joysticks et palonniers sont pris en charge nativement, dont : Logitech WingMan Interceptor, Saitek Pro Combat Rudder Pedals et Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], un petit logiciel permettant de restituer des panneaux d'instruments 2D est dorénavant inclus à chaque version.&lt;br /&gt;
&lt;br /&gt;
'''Correction d'anomalies'''&lt;br /&gt;
* Consulter [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 notre outil de suivi d'anomalies] pour la liste exhaustive des anomalies corrigées dans cette version.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* La version 64 bits a été restaurée et son installation intégrée dans l'installateur principal fgsetup.&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[es:Changelog 2.6.0]]&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Nl/Changelog_2.6.0&amp;diff=120669</id>
		<title>Nl/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Nl/Changelog_2.6.0&amp;diff=120669"/>
		<updated>2019-10-12T12:51:46Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
Het FlightGear team presenteert met trots de v2.6.0 release van FlightGear, dé gratis, opensource flight simulator.&lt;br /&gt;
Deze nieuwe versie bevat veel nieuwe functies, verbeteringen en bugfixes. Belangrijke verbeteringen ten opzichte van v2.4.0 zijn onder andere een korte AI laadtijd, eenvoudiger in te stellen graphics, geavenceerdere robot vliegtuigen en verbeterde bruikbaarheid.&lt;br /&gt;
&lt;br /&gt;
Opgericht in 1997, FlightGear wordt ontwikkeld door een wereldwijde groep van vrijwillgers, bijeengebracht door een gedeelde ambitie om de meest realistische flight simulator te ontwikkelen, die gratis te gebruiken is en vrij kan worden aangepast en verspreidt. FlightGear wordt over de hele wereld gebruikt door flight simulator enthousiastelingen, universiteiten en interactieve tentoonstellingen in musea.&lt;br /&gt;
&lt;br /&gt;
Er zijn meer dan 400 vliegtuigen beschikbaar voor FlightGear, een wereld omvattende database, multiplayer omgeving, gedetailleerde weergave van de lucht, een flexibel en open systeem om vliegtuigen te ontwikkelen, verscheidene netwerk opties, ondersteuning voor meerdere beeldschermen, een krachtige scripting taal en een open opzet. Maar het beste van alles is dat de simulator eigendom is van de gemeenschap en iedereen welkom is om bij te dragen.&lt;br /&gt;
&lt;br /&gt;
Download FlightGear v2.6.0 gratis van[http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Fly Free!&lt;br /&gt;
&lt;br /&gt;
=== Enkele van de belangrijkste wijzigingen: ===&lt;br /&gt;
&lt;br /&gt;
'''Vliegtuig operaties:'''&lt;br /&gt;
* Op een aantal vliegvelden kan FlightGear automatisch een gate uitkiezen, afhankelijk van het formaat en type van je vliegtuig.&lt;br /&gt;
* Vliegveld die deze functie ondersteunen kunnen je door middel van een zwevende lijn via een correcte taxi route naar de huidige startbaan leiden.&lt;br /&gt;
&lt;br /&gt;
'''AI systeem'''&lt;br /&gt;
* Multiplay en robot vliegtuigen worden geladen in een achtergrond thread om schokkerige beelden te voorkomen tijden het laden van modelen en om meer gebruik te maken van multi-core CPUs.&lt;br /&gt;
* Om laadtijden nog meer te verkorten worden alleen onderdelen die ook echt zichtbaar zijn geladen.&lt;br /&gt;
* Robot en multiplay vleigtuigen zijn niet langer zwijgende objecten, ze kunnen nu net zulke geluiden produceren als je eigen vliegtuig.&lt;br /&gt;
&lt;br /&gt;
'''Robot verkeer'''&lt;br /&gt;
* Veel nieuwe en betere robot vliegtuigen en liveries. Meer dan 80 luchtvaartmaatschappijen bevolken nu de virtuele lucht.&lt;br /&gt;
* De afstand waarop robot vliegtuigen zichtbaar zijn is nu in te stellen, zodat je FlightGear's prestaties nog beter kunt aanpassen.&lt;br /&gt;
* Robot piloten hebben uitgebreide training gekregen om realistischere naderingen te maken en de landingsbaan te verlaten zodra dat mogelijk is.&lt;br /&gt;
* De simulator plaatst niet langer twee vliegtuigen bij één gate.&lt;br /&gt;
&lt;br /&gt;
'''Vlucht modellen'''&lt;br /&gt;
* Het JSBSim vlucht model heeft een aantal belangijke updates gekregen.&lt;br /&gt;
&lt;br /&gt;
'''Omgeving'''&lt;br /&gt;
* Het &amp;quot;Local Weather&amp;quot; systeem is verder geintegreerd met de FlightGear core en heet nu &amp;quot;Advanced Weather&amp;quot;. Nieuwe weergave technieken maken het mogelijk om gedetaileerdere wolken weer te geven met dezelfde prestaties. Wolken op grote hoogte zien er realistischer uit en bewegen mee met de wind zonder invleod op de prestaties.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* Nieuwe herhaal systeem met videorecorder-achtige besturing inclusief slow motion en vooruitspoelen. Piloten kunnen op elk moment de controle over het vliegtuig overnemen; ideaal om bepaalde delen van een vlucht, zoals naderingen, herhaaldelijk te oefenen.&lt;br /&gt;
* De FlightGear Wizard geeft nu van een aantal vliegtuigen de status weer. Je kunt in één oogopslag zien hoe compleet de FDM, model, system en cockpit van een vliegtuig zijn.&lt;br /&gt;
* Multiplayer opties zijn nu direct in de simulator aan te passen. Zo kun je je callsign en server wijzigen of offline gaan.&lt;br /&gt;
* Je kunt nu gemakkelijker dan ooit automatisch scenery downloaden. Je hoeft enkel de map waar alles naar toe gedownload wordt te kiezen en het systeem aan te zetten.&lt;br /&gt;
* Invidivuele grafische effecten kunnen in het Rendering Settings venster aangepast worden, waardoor je de prestaties van FlightGear eenvoudig kunt verbeteren.&lt;br /&gt;
* The simulation of radio signal propagation has started and will make the reception of ATC messages and navigation aids more realistic in the future.&lt;br /&gt;
* Een nieuw setje instellingen maakt het makkelijker om naadloos meerder schermen aan elkaar te koppelen.&lt;br /&gt;
* Een prestatiemeter toont de tijd die elk systeem gebruikt.&lt;br /&gt;
&lt;br /&gt;
'''Opvallende nieuwe en verbeterde vleigtuigen'''&lt;br /&gt;
* [[A-26 Invader]]: cockpit verbeteringen.&lt;br /&gt;
* [[Boeing 777-200ER]]: veel extra en verbeterede functionaliteiten, waaronder de automatische pilot, instrumenten en animaties.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: cockpit verbeteringen.&lt;br /&gt;
&lt;br /&gt;
'''Project infrastructuur'''&lt;br /&gt;
* CMake is nu het officiële build systeem voor Linux, Mac en Windows.&lt;br /&gt;
&lt;br /&gt;
'''Grafische effecten'''&lt;br /&gt;
* De zee ziet er nu realistischer uit. Golven richten zich naar de wind en bij hoge windsnelheden zijn schuimkoppen zichtbaar.&lt;br /&gt;
* Steile hellingen zien er rotsachtig uit.&lt;br /&gt;
* Startbanen worden nat tijdens regenbuien.&lt;br /&gt;
* Om ontwikkelaars van vliegtuigen te helpen is er één enkele shader beschikbaar die bumpmap, reflecties en lightmaps combineerd.&lt;br /&gt;
&lt;br /&gt;
'''Overig'''&lt;br /&gt;
* Extra joysticks en pedalen worden out-of-the-box ondersteunt, onderandere de Logitech WingMan Interceptor, Saitek Pro Combat Rudder Pedals en Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], een licht gewicht programme om 2D instrumentenpanelen te tonen, is bij de release inbegrepen.&lt;br /&gt;
&lt;br /&gt;
'''Bug fixes'''&lt;br /&gt;
* Zie [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 onze bug tracker] voor een uitgebreide lijst van opgeloste problemen in deze versie.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* De 64 bits versie is opnieuw beschikbaar en de installie is geintegreerd in de fgsetup installateur.&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[es:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Es/Changelog_2.6.0&amp;diff=120668</id>
		<title>Es/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Es/Changelog_2.6.0&amp;diff=120668"/>
		<updated>2019-10-12T12:51:25Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
'''Available in:''' [[:nl:Changelog 2.6.0|Nederlands]], [[Changelog 2.6.0|English]], [[:es:Changelog 2.6.0|Español]] [[:fr:Changelog 2.6.0|Français]], [[:pt:Changelog 2.6.0|Português]], [[:ro:Changelog 2.6.0|Română]]&lt;br /&gt;
==FlightGear 2.6.0 ChangeLog- relación de cambios==&lt;br /&gt;
&lt;br /&gt;
El equipo de desarrollo de [[FlightGear]] se complace en anunciar el lanzamiento de FlightGear v2.6.0, el simulador de vuelo, libre y de código abierto.&lt;br /&gt;
Esta nueva versión incluye muchas características nuevas muy interesantes, mejoras y correcciones de errores. Las principales mejoras respecto a v2.4.0 son:&lt;br /&gt;
reduce los tiempos de carga de aviones AI, ajuste de gráficos más fácil, aviones IA más sofisticados y una mejor usabilidad.&lt;br /&gt;
&lt;br /&gt;
Fundado en 1997, FlightGear es desarrollado por un grupo de voluntarios en todo el mundo, reunidos por una ambición compartida de crear&lt;br /&gt;
el simulador de vuelo más realista posible, libre de usar, modificar y distribuir. FlightGear es utilizado en todo el mundo&lt;br /&gt;
por los entusiastas de simulación de vuelo de escritorio, para la investigación en universidades y para exhibiciones interactivas en museos.&lt;br /&gt;
&lt;br /&gt;
FlightGear cuenta con más de 400 aviones, una base de datos de escenarios de todo el mundo, un entorno multi-jugador mundial, modelado detallado del cielo, un sistema de modelado de aviones abierto y flexible, variadas opciones de red, compatibilidad con múltiples pantallas, un lenguaje de scripting muy potente y una arquitectura abierta. Y lo mejor de todo, al ser de código abierto, el simulador es propiedad de la comunidad y todos están invitados a contribuir.&lt;br /&gt;
&lt;br /&gt;
Descarga libremente FlightGear v2.6.0 en [FlightGear.org http://www.flightgear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vuela en libertad!&lt;br /&gt;
&lt;br /&gt;
=== Algunos de los cambios más importantes incluyen: ===&lt;br /&gt;
&lt;br /&gt;
''' Operaciones de aeronaves:'''&lt;br /&gt;
* En los aeropuertos seleccionados, FlightGear puede comenzar automáticamente en un lugar de estacionamiento adecuado en función del tamaño y tipo de la aeronave.&lt;br /&gt;
* En los aeropuertos que soportan esta función, una presentación visual de la ruta de rodaje en el suelo te lleva a la pista activa, mientras siguas las vías de rodaje adecuadas.&lt;br /&gt;
&lt;br /&gt;
'''Sistema AI de inteligencia artificial'''&lt;br /&gt;
* Para reducir los cortes durante la carga del modelo y obtener mayor ventaja de  la CPUs multi-core, ahora las aeronaves MP y los modelos de aviones AI se cargan en un subproceso en segundo plano.&lt;br /&gt;
* Para reducir los tiempos de carga aún más, sólo se cargan desde el disco las partes de la aeronave actualmente visibles.&lt;br /&gt;
* Las aeronaves AI y aviones MP ya no son objetos silenciosos, estos pueden producir sonidos al igual que el avión principal.&lt;br /&gt;
&lt;br /&gt;
'''Trafico AI'''&lt;br /&gt;
* Muchos aviones AI nuevos y libreas actualizados. Más de 80 aerolíneas llenan los cielos virtuales.&lt;br /&gt;
* Ahora es configurable la distancia a la que se muestran los aviones AI, lo que te permite ajustar FlightGear para un mejor rendimiento.&lt;br /&gt;
* Los pilotos controlados por AI han recibido una formación extensa en aterrizajes y ahora hacer una aproximación más realista y abandonan la pista cuando les sea posible.&lt;br /&gt;
* El simulador ahora asigna una posición de aparcamiento disponible al inicio.&lt;br /&gt;
&lt;br /&gt;
'''Dinámica de vuelo'''&lt;br /&gt;
* El modelo de dinámica de vuelo JSBSim ha recibido una revisión importante.&lt;br /&gt;
&lt;br /&gt;
'''Metereología'''&lt;br /&gt;
* El paquete de Metereología Local se ha integrado en mayor medida con el núcleo de FlightGear, y ha pasado a denominarse &amp;quot;Metereología Avanzada&amp;quot;. Las nuevas técnicas de representación permiten las nubes más detalladas, sin impacto en el rendimiento. Las nubes de gran altitud se hacen más realistas, y las nubes se mueven con el viento sin afectar el rendimiento.&lt;br /&gt;
&lt;br /&gt;
'''Interfaz'''&lt;br /&gt;
* Nuevo sistema de repetición. Con controles de tipo reproductor de video, incluyendo cámara lenta y avance rápido. Los pilotos pueden ahora hacerse cargo de la aeronave en cualquier momento durante la reproducción. Perfecto para entrenar una y otra vez determinadas fases de vuelo como la aproximación.&lt;br /&gt;
* [[Formalizing Aircraft Status|La valoración del estado de las aeronaves]] se muestra en el programa de lanzamiento de FlightGear, lo que te permite de un vistazo ver el FDM, la calidad del modelo, los sistemas y la cabina de los aviones valorados.&lt;br /&gt;
* Se puede acceder desde dentro del SIM a los ajustes multijugador. Ahora puedes elegir tu indicativo de llamada, seleccionar y conectarte a un servidor MP desde el simulador.&lt;br /&gt;
* La descarga automática de escenarios es ahora aún más fácil de usar. Sólo tienes que seleccionar el directorio de escenario donde descargar, y encenderlo.&lt;br /&gt;
* Los efectos gráficos individuales ahora pueden ser configurados dentro del cuadro de diálogo &amp;quot;Rendering Settings&amp;quot;, lo que permite ajustar el rendimiento de FlightGear desde el SIM.&lt;br /&gt;
* La simulación de la propagación de la señal de radio ha comenzado y la recepción de mensajes ATC y ayudas a la navegación se hará más realista en el futuro.&lt;br /&gt;
* Un nuevo conjunto de opciones hace que sea más fácil crear configuraciones multi-pantalla sin costuras y con zoom.&lt;br /&gt;
* El nuevo monitor de rendimiento muestra el tiempo consumido en cada subsistema.&lt;br /&gt;
&lt;br /&gt;
'''Aviones destacados nuevos y mejorados'''&lt;br /&gt;
* [[A-26 Invader]]: mejora de cabina.&lt;br /&gt;
* [[Boeing 777-200ER]]: muchas características actualizadas adicionales, entre ellas el piloto automático, tableros de instrumentos y animaciones.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: mejora de cabina.&lt;br /&gt;
&lt;br /&gt;
'''Navegación'''&lt;br /&gt;
* &lt;br /&gt;
&lt;br /&gt;
'''Infraestructura del proyecto'''&lt;br /&gt;
* CMake es ahora el sistema constructor oficial en Linux, Mac y Windows.&lt;br /&gt;
&lt;br /&gt;
'''Efectos visuales'''&lt;br /&gt;
* El mar ahora se ve más realista. Las olas se alinean con el viento y aparece espuma con vientos fuertes.&lt;br /&gt;
* Las pendientes pronunciadas ahora aparecen rocosas.&lt;br /&gt;
* Ahora las pistas aparecen mojadas durante la lluvia.&lt;br /&gt;
* Para ayudar a los desarrolladores de aeronaves, ya está disponible un sombreador que combina mapeado de choque, especular, reflexiones y mapeado de luces.&lt;br /&gt;
&lt;br /&gt;
'''Otros'''&lt;br /&gt;
* Soporte total para nuevas palancas de control y pedales, incluyendo el Logitech WingMan Interceptor, los pedales de combate Saitek Pro y el Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], el liviano software para crear paneles de instrumentos en 2D, está ahora incluido como una parte de la publicación.&lt;br /&gt;
&lt;br /&gt;
'''Corrección de errores'''&lt;br /&gt;
* En [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 nuestro bugtracker] se puede ver una extensa lista de los errores corregidos en esta versión.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* Restaurada la versión de 64 bits y su instalación  está integrada en el programa de instalación principal fgsetup&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;br /&gt;
[[pt:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=It/Changelog_3.0&amp;diff=120667</id>
		<title>It/Changelog 3.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=It/Changelog_3.0&amp;diff=120667"/>
		<updated>2019-10-12T12:49:02Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 3.0|https://www.flightgear.org/news/flightgear-v3-0-released/}}&lt;br /&gt;
{{draft|translated changelog|This changelog is currently being translated for the FlightGear 3.0 release.&lt;br /&gt;
We encourage people to help by translating the changelog and appreciate all contributions, however please keep in mind that this translation is not yet final!&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{Changelog 3.0}}&lt;br /&gt;
Il team di sviluppo di FlightGear è lieto di annunciare il rilascio della versione 3.0 di FlightGear, il simulatore di volo libero e open source. Questa nuova versione include svariate ed entusiasmanti novità, miglioramenti e correzioni di errori. In primo piano troviamo l'integrazione delle comunicazioni vocali FGCom direttamente dal simulatore, miglioramenti sul rendering del terreno, caricamento degli scenari più veloce e miglioramenti sull'usabilità.  Questa versione coincide anche col rilascio di FlightGear World Scenery 2.0: scenari di gran lunga migliori che coprono tutto il pianeta e incorporano informazioni dettagliate sulle strade e sui terreni con OpenStreetMap da varie fonti.&lt;br /&gt;
&lt;br /&gt;
In 4 anni dal rilascio di FlightGear V2.0.0 nel Febbraio del 2010, FlightGear è migliorato in maniera esponenziale: &lt;br /&gt;
* Il sistema di rendering Rembrandt fornisce illuminazione e ombre in real-time.&lt;br /&gt;
* Modellamento del cielo migliorato, inclusa nebbia e basso livello di opacità, linee di terminazione.&lt;br /&gt;
* Grandi miglioramenti sul rendering del terreno, con terreni specifici per regione, edifici casuali, effetti con shader e un piazzamento di oggetti e alberi più realistico.&lt;br /&gt;
* Simulazione avanzata del tempo atmosferico, inclusi sistema dei fronti meteorologici, termiche, portanza e formazione di nuvole basata sui versanti delle montagne.&lt;br /&gt;
* Caricamento terreni &amp;quot;al volo&amp;quot; incorporato - nessun bisogno di caricare il terreno prima del volo.&lt;br /&gt;
* Client multiplayer con comunicazioni vocali che permettono agli utenti di entrare e uscire in sessioni multiplayer direttamente dall'interno del simulatore.&lt;br /&gt;
* Miglioramenti nell'interfaccia di configurazione del joystick e della mappa.&lt;br /&gt;
* Sistema di rendering 2D completamento scriptabile che permette la creazione di UI complesse, strumenti del cockpit e molto altro.&lt;br /&gt;
&lt;br /&gt;
Fondato nel 1997, FlightGear è sviluppato da un gruppo di volontari provenienti da tutto il mondo, riuniti dall'ambizione condivisa di creare il simulatore di volo più realistico possibile che sia inoltre liberamente utilizzabile, modificabile e distribuibile. FlightGear viene utilizzato in tutto il mondo da appassionati della simulazione di volo, nella ricerca universitaria e nell'allestimento di mostre interattive nei musei. &lt;br /&gt;
&lt;br /&gt;
FlightGear conta più di 400 velivoli, una base di dati contenente l'intero scenario mondiale, un ambiente multiplayer, una modellazione dettagliata del cielo, un sistema di modellazione degli aerei flessibile e aperto, svariate opzioni di rete, il supporto per schermi multipli, un potente linguaggio di scripting e un'architettura aperta. Ma soprattutto, essendo open-source, il simulatore è di proprietà della comunità e chiunque è incoraggiato a contribuire.&lt;br /&gt;
&lt;br /&gt;
Scarica FlightGear v3.0 gratuitamente da [http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola liberamente!&lt;br /&gt;
&lt;br /&gt;
=== Principali miglioramenti in questa versione ===&lt;br /&gt;
&lt;br /&gt;
'''Modelli degli aerei'''&lt;br /&gt;
* Tutti i modelli di alianti hanno ora variometri ad energia totale.&lt;br /&gt;
&lt;br /&gt;
'''Environment Rendering'''&lt;br /&gt;
* Il colore del mare più realistico con l'utilizzo di una mappa globale dei mari per renderizzare l'oceano profondo con un colore diverso.&lt;br /&gt;
* Migliorate texture per gli edifici casuali&lt;br /&gt;
* Miglioramenti all'Atmospheric Light Scattering (ALS):&lt;br /&gt;
** modifiche significative per un aspetto più naturale di bassa visibilità o strato di nebbia che ora includono variazioni di altidudine&lt;br /&gt;
** il rendering dell'atmosfera al di sotto dello strato più basso di nebbia ora prende in considerazione l'effettiva visibilità in alto &amp;lt;sup&amp;gt;[ [[what?]] ]&amp;lt;/sup&amp;gt;, migliorando la sfocatura dell'orizzonte&lt;br /&gt;
** la linea dell'orizzonte è ora renderizzata con variazioni angolari che simulano le differenti altezze degli strati di aria molto lontani nell'atmosfera&lt;br /&gt;
** lo shader ''wake'' che renderizza le onde generate dalle navi è stato portato all'ALS&lt;br /&gt;
&lt;br /&gt;
'''Performance'''&lt;br /&gt;
* Tempi di caricamento del terreno migliorati rimandando il caricamento degli oggetti all'interno dello scenario&lt;br /&gt;
&lt;br /&gt;
''' Usabilità '''&lt;br /&gt;
* Il tasto Tab è usato per cambiare modalità del mouse: controllo aereo, controllo della telecamera, standby&lt;br /&gt;
* TerraSync è preconfigurato, nessuna configurazione dall'utente richiesta&lt;br /&gt;
* FGCom, il client di comunicazione vocale multiplayer è ora integrato in FlightGear&lt;br /&gt;
&lt;br /&gt;
''' Internazionalizzazione '''&lt;br /&gt;
* Traduzione in Italiano del manuale di FlightGear.&lt;br /&gt;
&lt;br /&gt;
''' Scenario '''&lt;br /&gt;
* Scenery 2.0 è stato rilasciato con dati di altitudine, strade e terreno migliorati.&lt;br /&gt;
* Dati di navigazione aggiornati&lt;br /&gt;
* Aggiunte definizioni di texture regionali per Scandinavia, Corsica e l'isola dell'Ascensione.&lt;br /&gt;
&lt;br /&gt;
'''Canvas System'''&lt;br /&gt;
&lt;br /&gt;
Il sistema completamente scriptabile di rendering 2D di FlightGear ha migliorato, tra le altre cose, le API per creare mappe e display di navigazione.&lt;br /&gt;
Non c'è più bisogno di essere programmatori esperti per aggiungere un display di navigazione ad un aereo: può essere fatto semplicemente copiando e incollando 30 righe di testo e personalizzando alcune proprietà. Il backend MapStructure gestisce in modo efficiente l'aggiornamento di tutti i layer del display di navigazione in maniera trasparente.&lt;br /&gt;
&lt;br /&gt;
'''Nasal Scripting'''&lt;br /&gt;
* Ricerche spaziali complesse più veloci &amp;lt;sup&amp;gt;[ [[what?]] ]&amp;lt;/sup&amp;gt;&lt;br /&gt;
* Binding HTTP&lt;br /&gt;
* Nuova libreria Nasal per implementare strumenti per l'elevazione specializzati. La libreria per il momento supporta variometri ad energia totale, Netto, Super Netto (Relative) and variometri Speed Command.&lt;br /&gt;
&lt;br /&gt;
'''Documentazione'''&lt;br /&gt;
* Documenti PDF/LaTeX del funzionamento interno del motore Nasal (codice C) sono stati aggiungi a $FG_ROOT/Docs.&lt;br /&gt;
* La traduzione italiana del manuale di Flightgear è ora disponibile.&lt;br /&gt;
&lt;br /&gt;
'''Nuovi aerei e aerei migliorati in primo piano'''&lt;br /&gt;
* [[Robin DR400 Dauphin|Robin DR400 Dauphin 180ch]]&lt;br /&gt;
* CAP10C&lt;br /&gt;
* Boeing 707&lt;br /&gt;
* North American P-51D&lt;br /&gt;
* Boeing 777&lt;br /&gt;
&lt;br /&gt;
'''Altro'''&lt;br /&gt;
* Ulteriori joystick e pedaliere supportati:&lt;br /&gt;
** Logitech Flight System G940 (joystick, pedaliera e manetta)&lt;br /&gt;
&lt;br /&gt;
'''Risoluzione di bug'''&lt;br /&gt;
&lt;br /&gt;
* Vedere [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D3.0 il nostro bugtracker] per una lunga, ma incompleta, lista dei bug risolti in questa versione.&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Es/Changelog_3.0&amp;diff=120666</id>
		<title>Es/Changelog 3.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Es/Changelog_3.0&amp;diff=120666"/>
		<updated>2019-10-12T12:48:58Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 3.0|https://www.flightgear.org/news/flightgear-v3-0-released/}}&lt;br /&gt;
{{Changelog 3.0}}&lt;br /&gt;
El equipo de desarrollo de FlightGear se complace en anunciar el lanzamiento de FlightGear v3.0, el simulador de vuelo, libre y de código abierto. Esta nueva versión incluye muchas características nuevas muy interesantes, mejoras y correcciones de errores.&lt;br /&gt;
 &lt;br /&gt;
Resaltando en esta publicación la inclusión la integración del cliente de comunicaciones de voz FGCom dentro del simulador, renderizado de terreno mejorado, carga de escenarios más rápida, y usabilidad mejorada. Esta publicación coincide también con el lanzamiento del Escenario Mundial 2.0 datos de escenarios mejorados másivamente cubriendo la totalidad del planeta e incorporando las carreteras de OpenStreetMap y detallada información de fuentes variadas.&lt;br /&gt;
&lt;br /&gt;
En los 4 años desde que fue publicada la versión V2.0.0 en Febrero de 2010, FlightGear se ha desarrollado enormemente:&lt;br /&gt;
* El sistema de renderizado Rembrandt ofrece sombras e iluminación en tiempo real.&lt;br /&gt;
* Mejora del modelado del cielo incluyendo niebla, bruma de bajo nivel y líneas de terminación.&lt;br /&gt;
* Mejora masiva del renderizado del terreno, con regiones específicas, edificios aleatorios, efectos de sombreado y una colocación más realista de árboles y objetos.&lt;br /&gt;
* Simulación meteorológica avanzada, incluyendo los sistemas frontales, térmicas, elevación y formación de nubes basadas en las crestas de las montañas.&lt;br /&gt;
* Incorporada la carga del terreno &amp;quot;sobre la marcha&amp;quot; - sin necesidad de cargar el terreno antes de tu vuelo.&lt;br /&gt;
* Clientes multijugador y de comunicaciones de voz integrados permiten a los usuarios unirse y dejar las sesiones multijugador &amp;quot;sobre la marcha&amp;quot;.&lt;br /&gt;
* Mejoras el la usabilidad incluyendo interfaz de usuario para la configuración del joystick y mapa.&lt;br /&gt;
* Un sistema completamente basado en código de renderizado 2D que permite la fácil creación de interfaces de usuario complejas, instrumentos con pantallas de cristal y mucho más.&lt;br /&gt;
&lt;br /&gt;
Fundado en 1997, FlightGear es desarrollado por un grupo de voluntarios en todo el mundo, reunidos por una ambición compartida para crear&lt;br /&gt;
el simulador de vuelo más realista posible, libre para usar, modificar y distribuir. FlightGear es utilizado en todo el mundo&lt;br /&gt;
por entusiastas de la simuladción de vuelo en escritorio, para la investigación en las universidades y para las exhibiciones interactivas en museos.&lt;br /&gt;
&lt;br /&gt;
FlightGear cuenta con más de 400 aviones, una base de datos de escenarios de todo el mundo, un entorno multi-jugador, un detallado modelado del cielo, un sistema de modelado de aviones abierto y flexible, muchas opciones de red, compatibilidad con múltiples pantallas, un lenguaje de programación propio de gran alcance y una arquitectura abierta. Lo mejor de todo, al ser de código abierto, el simulador es propiedad de la comunidad y todos están invitados a contribuir.&lt;br /&gt;
&lt;br /&gt;
Descarga libremente FlightGear v2.10 desde [http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vuela Libre!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Cambios importantes en esta versión: ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Modelaje de Aeronaves'''&lt;br /&gt;
* Todos los modelos de planeadores ahora tienen variómetros de Energía total compensada.&lt;br /&gt;
&lt;br /&gt;
'''Renderizado del Medio Ambiente'''&lt;br /&gt;
* El color del mar es más realista, utilizando un mapa global del mar que se utiliza para representar el océano poco profundo en un color diferente.&lt;br /&gt;
* Mejoras en las texturas de los edificios aleatorios.&lt;br /&gt;
* Mejoras en la dispersión de luz atmosférica (ALS), incluyendo:&lt;br /&gt;
** Trabajo significativo en una apariencia más natural de la neblina baja o capa de niebla que ahora incluye las variaciones de altitud&lt;br /&gt;
** La representación de la atmósfera más allá de la capa de niebla más baja toma ahora en cuenta la visibilidad en altura real, lo que nos lleva a un horizonte borroso&lt;br /&gt;
** La línea del horizonte está ahora representada con variaciones angulares, simulando diferentes extensiones verticales de las capas de aire muy lejanas en la atmósfera&lt;br /&gt;
** El efecto de sombreado de generacion de olas por un buque ha sido portado al sistema ALS (dispersión de luz atmosférica)&lt;br /&gt;
&lt;br /&gt;
'''Rendimiento'''&lt;br /&gt;
* Los tiempos de carga del terreno mejoran mediante el aplazamiento de la carga de objetos dentro del escenario.&lt;br /&gt;
&lt;br /&gt;
'''Usabilidad'''&lt;br /&gt;
* La tecla Tab se usa para los modos de ciclo del ratón: control de la aeronave, vista de control, y reposo&lt;br /&gt;
* TerraSync está pre-configurado y funciona tal cual, sin configuración de usuario requerida&lt;br /&gt;
* FGCom, el cliente de comunicaciones de voz multijugador está ahora integrado dentro de FlightGear&lt;br /&gt;
&lt;br /&gt;
'''Internacionalización'''&lt;br /&gt;
* Traducción al Italiano del Manual de FlightGear.&lt;br /&gt;
&lt;br /&gt;
'''Escenarios'''&lt;br /&gt;
* El Escenario 2.0 ya está disponible, con la mejora de las elevaciones, con datos de carretera y terreno.&lt;br /&gt;
* Actualización de los datos de navegación&lt;br /&gt;
* Definiciones de textura regionales, añadidas para Escandinavia, Córcega y la Isla de Ascensión.&lt;br /&gt;
&lt;br /&gt;
'''Sistema Canvas'''&lt;br /&gt;
&lt;br /&gt;
El sistema de renderizado 2D completamente programable de FlightGear ahora incluye las APIs mejoradas para la creación de mapas y pantallas de navegación entre muchas otras mejoras.&lt;br /&gt;
Ya no es necesario que la gente tenga experiencia de programación para agregar una pantalla de navegacion para sus aviones, ahora se puede hacer todo al copiar y pegar 30 líneas de texto y personalizar una serie de propiedades. El marco llamado MapStructure maneja la actualización eficaz de todas las capas transparentes de la pantalla de navegación.&lt;br /&gt;
&lt;br /&gt;
'''Código Nasal'''&lt;br /&gt;
* Búsquedas espaciales más rápidas y complejas&lt;br /&gt;
* Enlaces HTTP&lt;br /&gt;
* Una nueva biblioteca Nasal se ha añadido para la implementación de los instrumentos especializados en planeadores. La biblioteca es compatible actualmente con instrumentos de compensación total Varios y Netto, Súper Neto (también llamado Relative) y los variómetros Speed Command.&lt;br /&gt;
&lt;br /&gt;
'''Documentación'''&lt;br /&gt;
* PDF/LaTeX docs of the internals of the Nasal engine (C code) have been added to $FG_ROOT/Docs.&lt;br /&gt;
* An Italian translation of the FlightGear Manual is now available.&lt;br /&gt;
&lt;br /&gt;
'''Documentación'''&lt;br /&gt;
* Documentos en PDF/LaTeX de las partes internas del motor Nasal (código C), se han añadido a $FG_ROOT/Docs.&lt;br /&gt;
* Ahora está disponible una traducción al Italiano del Manual de FlightGear.&lt;br /&gt;
&lt;br /&gt;
'''Aeronaves destacadas, aviones nuevos y mejorados'''&lt;br /&gt;
* [[Robin DR400 Dauphin|Robin DR400 Dauphin 180ch]]&lt;br /&gt;
* CAP10C&lt;br /&gt;
* [[Boeing 707|Boeing_707-420]]&lt;br /&gt;
* North American P-51D&lt;br /&gt;
* Boeing 777&lt;br /&gt;
&lt;br /&gt;
'''Otros'''&lt;br /&gt;
* Joysticks adicionales y pedales de timón son compatibles &amp;quot;fuera de la caja&amp;quot;:&lt;br /&gt;
** Logitech Flight System G940 (palanca de mando, pedales y acelerador)&lt;br /&gt;
&lt;br /&gt;
'''Corrección de errores'''&lt;br /&gt;
&lt;br /&gt;
* Consulta [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone% nuestro rastreador de errores 3.0] para obtener una amplia lista, aunque incompleta, de los errores solucionados en esta versión. &lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 3.0]]&lt;br /&gt;
[[fr:Changelog 3.0]]&lt;br /&gt;
[[pt:Changelog 3.0]]&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Changelog_3.0&amp;diff=120665</id>
		<title>Ca/Changelog 3.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Changelog_3.0&amp;diff=120665"/>
		<updated>2019-10-12T12:48:56Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 3.0|https://www.flightgear.org/news/flightgear-v3-0-released/}}&lt;br /&gt;
{{Changelog 3.0}}&lt;br /&gt;
L'equip de desenvolupament de FlightGear es complau anunciar el llançament de FlightGear v3.0, el simulador de vol, lliure i de codi obert. Aquesta nova versió inclou moltes característiques noves molt interessants, millores i correccions d'errors.&lt;br /&gt;
 &lt;br /&gt;
Ressaltant en aquesta publicació la inclusió la integració del client de comunicacions de veu FGCom dins del simulador, renderitzat de terreny millorat, càrrega d'escenaris més ràpida, i usabilitat millorada. Aquesta publicació coincideix també amb el llançament de l'Escenari Mundial 2.0 en dades d'escenaris millorats massivament cobrint la totalitat del planeta i incorporant les carreteres d'OpenStreetMap i detallada informació de fonts variades.&lt;br /&gt;
&lt;br /&gt;
En els 4 anys des que va ser publicada la versió V2.0.0 al febrer de 2010, FlightGear s'ha desenvolupat enormement:&lt;br /&gt;
* El sistema de renderitzat Rembrandt ofereix ombres i il·luminació en temps real.&lt;br /&gt;
* Millora del modelatge del cel incloent boira, boira de baix nivell i línies de terminació.&lt;br /&gt;
* Millora massiva del renderitzat del terreny, amb regions específiques, edificis aleatoris, efectes d'ombreig i una col·locació més realista d'arbres i objectes.&lt;br /&gt;
* Simulació meteorològica avançada, incloent els sistemes frontals, tèrmiques, elevació i formació de núvols basats en les crestes de les muntanyes.&lt;br /&gt;
* Incorporada la càrrega del terreny &amp;quot;sobre la marxa&amp;quot; - sense necessitat de carregar el terreny abans del teu vol.&lt;br /&gt;
* Clients multijugador i de comunicacions de veu integrats permeten als usuaris unir-se i deixar les sessions multijugador &amp;quot;sobre la marxa&amp;quot;.&lt;br /&gt;
* Millores de la usabilitat incloent interfície d'usuari per a la configuració del joystick i mapa.&lt;br /&gt;
* Un sistema completament basat en codi de renderitzat 2D que permet la fàcil creació d'interfícies d'usuari complexes, instruments amb pantalles de cristall i molt més.&lt;br /&gt;
&lt;br /&gt;
Fundat en 1997, FlightGear és desenvolupat per un grup de voluntaris a tot el món, reunits per una ambició compartida per crear&lt;br /&gt;
el simulador de vol més realista possible, lliure per usar, modificar i distribuir. FlightGear és utilitzat a tot el món&lt;br /&gt;
per entusiastes de la simulació de vol en escriptori, per a la investigació a les universitats i per a les exhibicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 avions, una base de dades d'escenaris de tot el món, un entorn multi-jugador, un detallat modelatge del cel, un sistema de modelatge d'avions obert i flexible, moltes opcions de xarxa, compatibilitat amb múltiples pantalles, un llenguatge de programació propi de gran abast i una arquitectura oberta. El millor de tot, en ser de codi obert, el simulador és propietat de la comunitat i tots estan convidats a contribuir.&lt;br /&gt;
&lt;br /&gt;
Descàrrega lliurement FlightGear v3.0 des de [http://www.flightgear.org Flightgear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola Lliure!&lt;br /&gt;
&lt;br /&gt;
=== Canvis importants en aquesta versió: ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Modelatge d'Aeronaus'''&lt;br /&gt;
* Tots els models de planadors ara tenen variòmetres d'Energia total compensada.&lt;br /&gt;
&lt;br /&gt;
'''Renderitzadt de l'entorn'''&lt;br /&gt;
* El color del mar és més realista, utilitzant un mapa global del mar que s'utilitza per representar l'oceà poc profund en un color diferent.&lt;br /&gt;
* Millores en les textures dels edificis aleatoris.&lt;br /&gt;
* Millores en la dispersió de llum atmosfèrica (ALS), incloent:&lt;br /&gt;
** Treball significatiu en una aparença més natural de la boirina baixa o capa de boira que ara inclou les variacions d'altitud&lt;br /&gt;
** La representació de l'atmosfera més enllà de la capa de boira més baixa presa ara en compte la visibilitat en altura real, la qual cosa ens porta a un horitzó borrós&lt;br /&gt;
** La línia de l'horitzó està ara representada amb variacions angulars, simulant diferents extensions verticals de les capes d'aire molt llunyanes en l'atmosfera&lt;br /&gt;
** L'efecte d'ombreig de generació d'ones per un buc ha estat portat al sistema ALS (dispersió de llum atmosfèrica)&lt;br /&gt;
&lt;br /&gt;
'''Rendiment'''&lt;br /&gt;
* Els temps de càrrega del terreny milloren mitjançant l'ajornament de la càrrega d'objectes dins de l'escenari.&lt;br /&gt;
&lt;br /&gt;
'''Usabilitat'''&lt;br /&gt;
* La tecla Tab s'usa per a les modes de cicle del ratolí: control de l'aeronau, vista de control, i repòs&lt;br /&gt;
* TerraSync està pre-configurat i funciona igual, sense configuració d'usuari requerida&lt;br /&gt;
* FGCom, el client de comunicacions de veu multijugador està ara integrat dins de FlightGear&lt;br /&gt;
&lt;br /&gt;
'''Internacionalització'''&lt;br /&gt;
* Traducció a l'italià del Manual de FlightGear.&lt;br /&gt;
&lt;br /&gt;
'''Escenaris'''&lt;br /&gt;
* L'Escenari 2.0 ja està disponible, amb la millora de les elevacions, amb dades de carretera i terreny.&lt;br /&gt;
* Actualització de les dades de navegació&lt;br /&gt;
* Definicions de textura regionals, afegides per a Escandinàvia, Còrsega i l'Illa d'Ascensió.&lt;br /&gt;
&lt;br /&gt;
'''Sistema Canvas'''&lt;br /&gt;
&lt;br /&gt;
El sistema de renderitzat 2D completament programable de FlightGear ara inclou les APIs millorades per a la creació de mapes i pantalles de navegació entre moltes altres millores.&lt;br /&gt;
Ja no és necessari que la gent tingui experiència de programació per agregar una pantalla de navegació per als seus avions, ara es pot fer tot en copiar i enganxar 30 línies de text i personalitzar una sèrie de propietats. El marc anomenat MapStructure maneja l'actualització eficaç de totes les capes transparents de la pantalla de navegació.&lt;br /&gt;
&lt;br /&gt;
'''Codi Nasal'''&lt;br /&gt;
* Cerques espacials més ràpides i complexes&lt;br /&gt;
* Enllaços HTTP&lt;br /&gt;
* S'ha afegit una nova biblioteca Nasal per a la implementació dels instruments especialitzats en planadors. La biblioteca és compatible actualment amb instruments de compensació total Varis i Netto, Súper Net (també anomenat Relative) i els variòmetres Speed Command.&lt;br /&gt;
&lt;br /&gt;
'''Documentació'''&lt;br /&gt;
* S'han afegit documents PDF/LaTeX al motor intern del Nasal engine (codi C) a $FG_ROOT/Docs.&lt;br /&gt;
* Traducció a l'italià del Manual de FlightGear.&lt;br /&gt;
&lt;br /&gt;
'''Aeronaus destacades, avions nous i millorats'''&lt;br /&gt;
* [[Robin DR400 Dauphin|Robin DR400 Dauphin 180ch]]&lt;br /&gt;
* CAP10C&lt;br /&gt;
* [[Boeing 707|Boeing_707-420]]&lt;br /&gt;
* North American P-51D&lt;br /&gt;
* Boeing 777&lt;br /&gt;
&lt;br /&gt;
'''Altres'''&lt;br /&gt;
* Joysticks addicionals i els pedals de timó són compatibles &amp;quot;fora de la finestra&amp;quot;:&lt;br /&gt;
** Logitech Flight System G940 (palanca de comandament, pedals i accelerador)&lt;br /&gt;
&lt;br /&gt;
'''Correcció d'errors'''&lt;br /&gt;
&lt;br /&gt;
* Consulta [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=milestone% el nostre rastrejador d'errors v3.0] per obtenir una àmplia llista, encara que incompleta, dels errors solucionats en aquesta versió. &lt;br /&gt;
&lt;br /&gt;
[[en:Changelog 3.0]]&lt;br /&gt;
[[es:Changelog 3.0]]&lt;br /&gt;
[[fr:Changelog 3.0]]&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Fr/Changelog_3.0&amp;diff=120664</id>
		<title>Fr/Changelog 3.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Fr/Changelog_3.0&amp;diff=120664"/>
		<updated>2019-10-12T12:47:37Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 3.0|https://www.flightgear.org/news/flightgear-v3-0-released/}}&lt;br /&gt;
{{Changelog 3.0}}&lt;br /&gt;
L'équipe de développement de FlightGear est ravie de vous annoncer la sortie de FlightGear version 3.0, le simulateur de vol libre et gratuit. Cette version contient de nombreuses nouvelles fonctionnalités qui valent le détour, ainsi que des améliorations et des corrections d'anomalies. Les principales évolutions de cette version sont l'intégration du client de communications vocales [[FGCom]] au sein du simulateur, l'amélioration du rendu de terrain, un chargement plus rapide du terrain et une plus grande facilité d'utilisation. Cette version correspond également à la sortie de la version 2.01 des scènes mondiales de FlightGear - des scènes grandement améliorées couvrant l'ensemble de la planète et comprenant les données routières issues du projet OpenStreetMap et des informations de terrain détaillées issues de différentes sources.&lt;br /&gt;
&lt;br /&gt;
Depuis la sortie de FlightGear version 2.0.0 il y a exactement quatre ans, FlightGear a fortement développé :&lt;br /&gt;
* le système de rendu Rembrandt, qui offre des ombres et un éclairage rendus en temps réel&lt;br /&gt;
* une modélisation améliorée du ciel, comprenant le brouillard, et la brume proche du ciel&lt;br /&gt;
* un rendu du terrain grandement amélioré, avec un rendu du terrain particulier en fonction des régions, des bâtiments aléatoires, des effets de shader et un positionnement plus réaliste des objets et des arbres&lt;br /&gt;
* une simulation avancée des conditions météorologiques, comprenant des systèmes de fronts, de thermiques, d'ascendance et de formation des nuages se basant sur le relief des montagnes&lt;br /&gt;
* un chargement à la volée du terrain, inutile de charger le terrain avant votre vol&lt;br /&gt;
* un système multijoueurs intégré et des communications vocales permettant aux utilisateurs de rejoindre et quitter des sessions multijoueurs depuis le simulateur&lt;br /&gt;
* une plus grande facilité d'utilisation, avec une interface de configuration des joysticks intégrée, une carte&lt;br /&gt;
* un système de rendu en 2D sous forme de scripts, facilitant la création d'interfaces utilisateurs complexes, les cockpits entièrement numériques, et autres.&lt;br /&gt;
&lt;br /&gt;
Créé en 1997, FlightGear est développé par un groupe mondial de volontaires, rassemblés ensemble par l'ambition commune de créer le simulateur de vol le plus réaliste possible, libre et gratuit d'utilisation, de modification et de distribution. FlightGear est utilisé dans le monde entier par les amateurs de simulation de vol, pour la chercher dans les universités et pour les expositions interactives dans les musées.&lt;br /&gt;
&lt;br /&gt;
FlightGear comprend plus de 400 aéronefs, une base de données des scènes mondiale, un environnement multijoueurs, une modélisation détaillée du ciel, un système de modélisation des aéronefs flexible et ouvert, diverses options variées, une prise en compte des affichages multiples, un langage de script puissant et une architecture ouverte. Cerise sur le gâteau, étant un logiciel libre, le simulateur est la propriété de la communauté et chacun est invité à participer.&lt;br /&gt;
&lt;br /&gt;
Télécharger FlightGear v3.0 gratuitement à l'adresse [http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Volez en toute liberté !&lt;br /&gt;
&lt;br /&gt;
=== Améliorations principales de cette version ===&lt;br /&gt;
&lt;br /&gt;
'''Modélisation des aéronefs'''&lt;br /&gt;
* Tous les planeurs disposent maintenant de variomètres compensés d'énergie totale.&lt;br /&gt;
&lt;br /&gt;
'''Rendu de l'environnement'''&lt;br /&gt;
* La couleurs de la mer est plus réaliste, grâce à l'utilisation d'une carte globale de la mer pour rendre l'eau peu profonde d'une couleur différente.&lt;br /&gt;
* Amélioration des textures des bâtiments aléatoires&lt;br /&gt;
* Améliorations au rendu Atmospheric Light Scattering (ALS) comprenant :&lt;br /&gt;
** un travail significatif pour obtenir une apparence plus naturelle des couches de brume ou de brouillard prenant en compte les variations d'altitude&lt;br /&gt;
** le rendu de l'atmosphère sous la couche la plus basse du brouillard prend maintenant la visibilité correspondante en considération, ce qui entraîne un horizon diffus&lt;br /&gt;
** la ligne d'horizon est dorénavant rendue avec des variations angulaires, simulant différentes extensions verticales de couches d'air au loin dans l'atmosphère&lt;br /&gt;
** le shader des vagues offrant un rendu du sillage généré par un navire a été porté vers ALS&lt;br /&gt;
&lt;br /&gt;
'''Performance'''&lt;br /&gt;
* Le temps de chargement du terrain a été amélioré en différant le chargement des objets dans les scènes.&lt;br /&gt;
&lt;br /&gt;
'''Facilité d'utilisation'''&lt;br /&gt;
* La touche Tab est utilisée pour passer d'un mode de souris à l'autre : contrôle de l'aéronef, de la vue, neutre&lt;br /&gt;
* [[TerraSync]] est pré-configuré et fonctionne tel quel sans configuration nécessaire de la part de l'utilisateur&lt;br /&gt;
* [[FGCom]], le client de communication vocale multijoueurs est dorénavant intégré dans FlightGear&lt;br /&gt;
&lt;br /&gt;
''' Internationalisation '''&lt;br /&gt;
* Traduction en italien du manuel FlightGear.&lt;br /&gt;
&lt;br /&gt;
''' Scènes'''&lt;br /&gt;
* Les scènes version 2.01 sont dorénavant disponibles, améliorant la précision de l'élévation, des routes et du terrain&lt;br /&gt;
* Mise à jour des données de navigation&lt;br /&gt;
* Des définitions de textures régionales ont été ajoutée pour la Scandinavie, la Corse et l’île d'Ascension.&lt;br /&gt;
&lt;br /&gt;
'''Système Canvas'''&lt;br /&gt;
&lt;br /&gt;
{{lang|en|FlightGear's fully scriptable 2D rendering system now includes improved APIs for creating maps and navigation displays amongst many other improvements.&lt;br /&gt;
People no longer need to have programming experience to add a working ND to their aircraft, it can  now  be all done by copying and pasting 30 lines of text and customizing a few properties. The so called MapStructure back-end handles efficient updating of all ND layers transparently.}}&lt;br /&gt;
&lt;br /&gt;
'''Langage de script [[Nasal]]'''&lt;br /&gt;
* Des recherches spatiales complexes plus rapides&lt;br /&gt;
* Associations HTTP&lt;br /&gt;
* Une nouvelle librairie Nasal a été ajoutée pour prendre en charge des instruments de vol libre spécifiques. La librairie prend actuellement en charge les variomètres compensés d'énergie totale ainsi que les variomètres Netto, Super Netto (Relative) et de commande de vitesse.&lt;br /&gt;
&lt;br /&gt;
'''Documentation'''&lt;br /&gt;
* La documentation au format PDF/LaTeX des entrailles du moteur Nasal (en langage C) a été ajoutée à [[$FG_ROOT]]/Docs.&lt;br /&gt;
* Une traduction en italien du manuel FlightGear est dorénavant disponible.&lt;br /&gt;
&lt;br /&gt;
'''Aéronefs nouveaux à tester absolument : '''&lt;br /&gt;
* [[Robin DR400 Dauphin|Robin DR400 Dauphin 180ch]]&lt;br /&gt;
* CAP10C&lt;br /&gt;
* Boeing 707&lt;br /&gt;
* North American P-51D&lt;br /&gt;
* Boeing 777&lt;br /&gt;
&lt;br /&gt;
'''Autres : '''&lt;br /&gt;
* De nouveaux joysticks et palonniers sont prise en charge directement : &lt;br /&gt;
** Logitech Flight System G940 (joystick, pédalier et manettes)&lt;br /&gt;
&lt;br /&gt;
'''Correction d'anomalies'''&lt;br /&gt;
&lt;br /&gt;
* Consultez [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D3.0 notre outil de gestion d'anomalies] pour une liste étendue, bien qu'incomplète, des anomalies corrigées dans cette version.&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear changelogs|3.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Fr/FlightGear_Newsletter_July_2012&amp;diff=120663</id>
		<title>Fr/FlightGear Newsletter July 2012</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Fr/FlightGear_Newsletter_July_2012&amp;diff=120663"/>
		<updated>2019-10-12T12:39:14Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{newsletter}}&lt;br /&gt;
{{TOC_right|limit=2}}&lt;br /&gt;
&lt;br /&gt;
''Nous voudrions insister sur le fait que cette lettre d'information ne peut pas vivre sans les contributions des utilisateurs et développeurs de FlightGear. Il suffit d'ouvrir un compte sur ce wiki pour l'éditer et toutes les contribution sont les bienvenues. Si vous avez connaissance de nouveautés dans FlightGear ou dans un projet parent, comme les avions ou les terrains, vous êtes invité à les partager en éditant cette newsletter.''&lt;br /&gt;
&lt;br /&gt;
== À propos de la prochaine version ==&lt;br /&gt;
Le 17 Juillet, la branche pour la nouvelle version a été créée dans le dépôt [[Git]] hébergeant le code source et des données du simulateur. C'était la dernière étape majeure dans la feuille de route ([[Release Plan]]) avant la sortie de la nouvelle version 2.8.0 de FlightGear. Durant les deux prochaines semaines, nous allons travailler intensément à la correction des derniers bogues connus dans le code pour ensuite créer les paquetages pour les principales plate-formes. Vous pouvez nous aider à trouver des bogues, en testant les versions de test (release candidate) qui sont téléchargeables en bas [http://www.flightgear.org/download/ de cette page]. Les testeurs sont encouragés à signaler les bogues sur [http://code.google.com/p/flightgear-bugs/ notre outil de suivi d'anomalies].&lt;br /&gt;
&lt;br /&gt;
Pour savoir ce qui a changé depuis la dernière version (2.6.0), un journal des modifications est en cours d'écriture dans cet article : [[Changelog 2.8.0]].&lt;br /&gt;
&lt;br /&gt;
== FlightGear fête ses 15 ans avec un concours de captures d'écrans ==&lt;br /&gt;
Pour célébrer les 15 ans de FlightGear (le 17 juillet), un concours de capture d'écran a été organisé. À partir du 1er août, une période de deux semaines vote a commencé. Les gagnants seront annoncés le 18 août, en même temps que la sortie de FlightGear 2.8.0. Les captures d'écrans gagnantes seront utilisées pour promouvoir FlightGear auprès du grand public.&lt;br /&gt;
&lt;br /&gt;
Nous tenons à remercier les 37 participants qui ont soumis un total de 165 captures d'écrans. Votez pour vos favoris sur [http://flightgear.org/contest le site du concours] !&lt;br /&gt;
&lt;br /&gt;
Vous souhaitez en savoir plus sur l'histoire de FlightGear ? Lisez [[FlightGear History]].&lt;br /&gt;
&lt;br /&gt;
== Nouvelles du développement ==&lt;br /&gt;
=== Adoption du nouveau système de rendu 2D Canvas ===&lt;br /&gt;
&lt;br /&gt;
A compter de juillet 2012, les développeurs de FlightGear ont accepté d'adopter le nouveau système de rendu 2D [[Canvas]] développé par Tom qui est entièrement piloté par des propriétés et prend en charge tout l'affichage 2D par le biais l'arbre des propriétés de FlightGear (voir l'article [[Original Canvas Proposal]]). Initialement, l'idée était de remplacer le kit d'outils de l'interface graphique actuelle (PUI/PLIB, qui a montré de nombreuses limitations au fil du temps) pour utiliser une implémentation basée uniquement sur [[Canvas]], qui sera essentiellement implémentée dans l'espace de script Nasal et qui utilisera simplement le système Canvas comme interface de rendu. Les détails de l'implantation sont couverts en détail dans l'article [[Canvas_Widgets]].&lt;br /&gt;
Cette étape pourrait permettre à l'utilisateur final de personnaliser facilement l'interface graphique de FlightGear et son apparrence en créant des thèmes graphiques personnalisés (thèmes/skins) mais également en créant des widgets totalement nouveaux en utilisant un éditeur SVG comme Inkscape.&lt;br /&gt;
&lt;br /&gt;
Actuellement (juillet 2012), seul le dessin à l'intérieur d'un dialogue existant (PUI) est possible, mais l'idée est d'implanter progressivement la fonctionnalité actuelle en Nasal et de se débarrasser des fenêtres de dialogue PUI codées en dur. Seules quelques lignes de codes pour l'interaction souris/clavier avec Nasal resteront nécessaires.&lt;br /&gt;
&lt;br /&gt;
Contrairement à l'utilisation d'une interface graphique codée en dur (PUI, osgWidget, etc.), cette approche donnerait beaucoup plus de flexibilité et également les moyens de modifier et créer de nouvelles fenêtres, sans nécessiter de toucher au code de FlightGear.&lt;br /&gt;
&lt;br /&gt;
Avec le système Canvas, tout type de fenêtre serait possible, de telle sorte que des choses comme des sous-menus peuvent être conçues. Un autre avantage de l'approche Canvas est qu'elle s'appuie fortement sur l'arbre des propriétés de FlightGear et il est ainsi entièrement accessible depuis le code Nasal et également configurable avec les formats XML existants.&lt;br /&gt;
&lt;br /&gt;
Le but de démonstration des fenêtres Canvas est de montrer à quel point le nouveau système Canvas est puissant et flexible. c'est-à-dire que non seulement il peut être utilisé pour les scripts des aéronefs (instruments, MFD), mais aussi pour les scripts de l'interface graphique, ce qui veut dire que l'utilisation de ce système unifierait l'interface de rendu 2D (tout peut être géré par canvas), tout en réduisant la quantité de code C++ requise pour faire ce genre de chose, ce qui signifie que l'interface graphique pourrait être entièrement maintenue dans un espace de script, c'est-à-dire comme faisant partie du paquetage de base, par des personnes qui n'ont pas besoin de connaître le C++ - seuls des rudiments de Nasal seront nécessaires.&lt;br /&gt;
&lt;br /&gt;
Simplement, l'adoption du système Canvas pour de telles fins ou d'autres fins similaires signifierait que des tonnes de code C++ ancien/périmé pourront être supprimées et remplacées par une seule implantation homogène en C++, qui utiliserait du code C++/OSG moderne - ce qui veut dire également qu'OSG en lui-même peut faire plus d'hypothèse sur ce qui est rendu, de telle sore que plus d'optimisation (donc un meilleur taux de rafraîchissement d'images) soit obtenue facilement en utilisant des patrons et protocoles de code OSG, au lieu de bibliothèques anciennes/personnalisées/tierces qui devraient être insérées manuellement dans l'écosystème FG/SG/OSG.&lt;br /&gt;
&lt;br /&gt;
De plus, ce qui est intéressant à propos du système canvas, c'est qu'il est intégré de telle façon qu'il va continuer à fonctionner avec l'ancien code d'interface graphique toujours en place. En plus, toutes les fonctionnalités de l'interface actuelle (disposition, traitement XML), sont prises en charge implicitement grâce à la façon dont le système canvas est implémenté. Ceci est une étape essentielle pour l'implémentation d'une nouvelle librairie d'interface graphique en parallèle à PUI car, autrement, tout l'existant devrait être porté explicitement (soit dans l'espace C++ ou par la conversion de tonnes de fichiers XML). Globalement, le système canvas nous permettra d'obtenir tout cela sans effort, et cela signifiera aussi moins de code C++ dans l'arborescence des sources aussi, et donc une maintenance plus aisée.&lt;br /&gt;
&lt;br /&gt;
Enfin, quand la version autonome [[FGCanvas]] sera disponible, il sera possible de faire fonctionner l'interface en mode multi-fenêtré ou même dans des processus séparés.&lt;br /&gt;
&lt;br /&gt;
Egalement, en utilisant le système Canvas pour les fenêtres de dialogue, il sera possible de rendre les instruments d'un aéronef, comme les HUDs ou MFDs '''dans''' une fenêtre de dialogue.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|CIS8UyuJLgM}}&lt;br /&gt;
&lt;br /&gt;
Les plans futurs prévoient de réimplanter le HUD et le système de panneaux 2D actuels en utilisant le système Canvas . En plus, Le système canvas permettra la possibilité d'unifier incrémentalement le système de rendu 2D dans FlightGear dans les mois à venir. Voir [[Unifying the 2D rendering backend via canvas]]. En plus, le système canvas offre un nouveau niveau d'abstraction pour la création d'écrans de cartes mobiles dynamiques et totalement interactives, ainsi que les fenêtres pour générer des graphiques en utilisant les [[Canvas Maps]].&lt;br /&gt;
&lt;br /&gt;
=== Textures procédurales ===&lt;br /&gt;
Habituellement, les textures des modèles ou des scènes sont préparées à l'avance puis chargées et rendues par FlightGear. L'utilisation de textures procédurales permet de calculer les textures pour un rendu à l'intérieur du ''fragment shader'' plutôt que d'utiliser une texture prédéfinie. Le principal désavantage de ce procédé est qu'il a un coût plus important sur le nombre d'image par seconde. Cependant, contrairement aux textures prédéfinies qui montrent un certain degré de répétition (tuilage) sur des distances beaucoup plus larges que la taille de la texture, un calcul au sein du ''fragement shader''permet d'évaluer une fonction qui ne montre pas de tuilage et l'utilise comme base pour la texture finale. Dans le même temps, des détails comme la carte de hauteur du terrain (''terrain heightmap'') ou les variations de couleur à n'importe quelle échelle peuvent être générées.&lt;br /&gt;
&lt;br /&gt;
Comme les textures sont générées dynamiquement, il est aussi possible de laisser l'élévation et les courbes du terrain influencer le résultat (comme démontré actuellement avec les shaders d'effet de transition et de neige). L'utilisation des textures procédurales dans le shader du terrain afin de mélanger différentes textures et d'ajouter des effets environnementaux permet de rendre le terrain de FlightGear avec un niveau de détail jamais atteint. La génération dynamique de la texture permet de cacher les ''coutures'' entre deux types de terrains différents et de générer la rugosité du terrain à un haut niveau de détail. Elle permet aussi d'ajouter facilement l'effet la réflexion de la lumière induit par des mares d'eau peut être utilisée pour texturer en très haute résolution les types de sols présents dans les aéroports.&lt;br /&gt;
&lt;br /&gt;
[[File:Proc01.jpg|400px|Texturage de la carte d'altitude détaillée du terrain]]&lt;br /&gt;
[[File:Proc02.jpg|400px|Réduction des contrastes entre différents types de sols]]&lt;br /&gt;
[[File:Proc03.jpg|400px|Ajout dynamique de mares pour le terrain humide]]&lt;br /&gt;
[[File:Proc04.jpg|400px|Offre une texture d'aéroport avec une résolution de 5 mm par pixel]]&lt;br /&gt;
&lt;br /&gt;
(toutes les captures d'écrans ont été prises dans les scènes par défaut)&lt;br /&gt;
&lt;br /&gt;
== Dans le Hangar ==&lt;br /&gt;
En mai 2011, nous avons adopté un nouveau système de notation pour les aéronefs. A l'heure actuelle, seuls quelques appareils ont été notés, comme on peut le voir dans la liste 'hockenberry' mise en place sur [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&amp;amp;hl=en_US Google Docs]. Si vous êtes un développeur d'aéronef et que celui-ci ne figure pas sur cette liste, pensez à noter leurs statuts. Tout ce que vous devez savoir est écrit dans l'article [[Formalizing Aircraft Status]]. Si vous souhaitez simplement contribuer à FlightGear, ce serait également une excellente façon de commencer.&lt;br /&gt;
&lt;br /&gt;
=== Un nouveau hangar, celui de Lukas ===&lt;br /&gt;
Un nouveau hangar pour FlightGear a ouvert, celui de Lukas. Vous pourrez y trouver quelques livrées d'appareils ainsi que quelques projets scènes notamment des aéroports des Îles Baléares et Canaries. Le mieux est de jeter un coup d'oeil par vous-même dans [http://lukashangar.jimdo.com/ son hangar].&lt;br /&gt;
&lt;br /&gt;
== Le coin des scènes ==&lt;br /&gt;
=== Données du terrain de Manhattan ===&lt;br /&gt;
[[File:Manhattan v0 vs cs-osm.png|thumb|270px|Scènes personnalisées avec données linéaires OSM (gauche) par rapport à l'occupation des sols VMAP0.]]&lt;br /&gt;
Gijs a modifié à la main les contours du terrain de l'île de Manhattan à New York. Ces données sont maintenant disponibles sur [http://mapserver.flightgear.org/ le serveur de cartes]. Comparées aux données actuelles (VMAP0), ces données sont beaucoup plus fidèles à la réalité et montrent un niveau de détail plus élevé. Les améliorations les plus flagrantes sont l'ajout de parcs et des îles, dont Liberty Island.&lt;br /&gt;
&lt;br /&gt;
Ceux parmi vous qui savent utiliser [[TerraGear]] peuvent s'en servir pour construire Manhattan, pour les autres il faudra attendre la prochaine construction des scènes de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Outils ===&lt;br /&gt;
FlightGear l'a (encore) fait ! Pour la première fois dans l'histoire des simulateurs, il n'a jamais été aussi facile de contribuer a l'amélioration des scènes. Si vous avez déjà copié/collé une fois dans votre vie, alors vous serez capables de contribuer aux scènes de FG. Un copier/coller direct des nouvelles lignes d'objet au format STG dans un formulaire en ligne vous permet dorénavant de mettre à jour les objets des scènes du monde entier pour l'ensemble des utilisateurs de FlightGear qui utilisent Terrasync. L'ajout de votre adresse email au formulaire vous permet d'être tenu informé de la progression de la mise à jour. L'importation est généralement rapide (disons entre 24 et 72h), mais cela dépend de la charge de travail des (du) responsable(s) des scènes.&lt;br /&gt;
&lt;br /&gt;
Vous voulez essayer ? Cliquez [http://scenemodels.flightgear.org/submission/ ici], puis choisissez ''Mass import'', ou alors via le menu du site ''scenemodels'' (Contribute =&amp;gt; Mass shared object position insertion).&lt;br /&gt;
&lt;br /&gt;
Veuillez noter que :&lt;br /&gt;
* vous devez importer uniquement des nouveaux objets et non le fichier STG au complet sur lequel vous travaillez !&lt;br /&gt;
* N'ajoutez pas de modèles qui ne seraient pas présents dans la base de données ''scenemodels'' de FlightGear (ni d'OBJECT_SIGN ou d'OBJECT_STATIC) ;&lt;br /&gt;
* n'ajoutez pas de forêt ou d'autre élément lié aux données du terrain, car ces éléments doivent être générés en fonction des données du terrain. Les seuls arbres qui seront tolérés sont ceux qui sont ajoutés, par exemple, dans une scène d'aéroport ;&lt;br /&gt;
* les données dont vous demandez l'import doivent être basées sur l'élévation du terrain fourni par FlightGear/Terrasync et non sur des données de terrain que vous pourriez avoir compilé ou téléchargé vous-même, car sinon vos objets pourraient se retrouver flotter ou enterrés dans le terrain ;&lt;br /&gt;
* les importations sont limitées à 100 lignes par soumission (une petite pensée pour les pauvres responsables des scènes) ;&lt;br /&gt;
* l'importation est assez sensible sur la qualité des données en entrée, qui passent par pas mal de vérifications y compris humaines, avant d'être insérées ;&lt;br /&gt;
&lt;br /&gt;
La prochaine étape est l'outil d'import des modèles 3D. Il est terminé à 90%. Soyez patient, c'est un outil assez compliqué à finaliser.&lt;br /&gt;
&lt;br /&gt;
=== Serveur de cartographie ===&lt;br /&gt;
[[File:Mapserver - Update and Delete links.png|thumb|270px|Affichage des liens de mise à jour et de suppression d'objets sur Mapserver.]]&lt;br /&gt;
Quelques nouvelles du Mapserver, car nous n'avons pas parlé de cet outil très utile depuis un certain temps. Mapserver a été mis à jour ce mois-çi, la mise à jour la plus intéressante étant la possibilité de visionner les détails d'un objet et de le modifier/le supprimer directement à partir de la carte. Il n'a jamais été aussi simple de mettre à jour/supprimer un objet partagé directement à partir de la carte (voir la capture d'écran). Notez que vous devez avoir un facteur de zoom suffisant (&amp;gt;=16) pour apercevoir les flèches rouges, puis cliquer dessus. Remerciements à Martin, Julien et Gijs pour les mises à jour et les tests effectués sur cet outil. Pour l'utiliser, regardez [http://mapserver.flightgear.org/popmap/?lat=52.47492&amp;amp;lon=13.38199&amp;amp;zoom=16&amp;amp;layers=B00FFTTTTT ici].&lt;br /&gt;
&lt;br /&gt;
=== Mise à jour de la licence d'OpenStreetMap ===&lt;br /&gt;
Comme vous le savez probablement, le service cartographique en ligne [[OpenStreetMap]] change sa licence. Lorsque le changement de licence sera terminé, nous serons en mesure d'utiliser les données OSM dans les scènes officielles de FlightGear. Comme tous les contributeurs d'OSM n'ont pas accepté la nouvelle licence, les données issues de ces sources doivent être supprimées. Ce ''processus de rédaction'' devrait être terminé d'ici la fin juillet. Même si c'est un grand pas en avant, la licence n'a pas encore changé. Voir le blog OSM pour les mises à jours et les dernières informations sur le sujet:&lt;br /&gt;
http://blog.osmfoundation.org/&lt;br /&gt;
&lt;br /&gt;
== Nouvelles de la communauté ==&lt;br /&gt;
=== FlightGear sur Youtube ===&lt;br /&gt;
Fallen a revisité ses enregistrements vidéos ''à la vieille mode'' lors d'un vol entre l'aéroport international de San Francisco et le porte-avion USS Nimitz, mais l'a réalisé la nuit, avec le nouveau F-14 Tomcat mis à jour pour Rembrandt permettant de voir FlightGear sous de nouvelles lumières.&lt;br /&gt;
&lt;br /&gt;
FlightGear 2.8 de nuit avec Rembrandt&lt;br /&gt;
{{#ev:youtube|q951rsP0DBk}}&lt;br /&gt;
&lt;br /&gt;
=== Multijoueurs ===&lt;br /&gt;
Deux nouveaux serveurs multijoueurs ont été paramétrés :&lt;br /&gt;
* '''mpserver15.flightgear.org''' (''North Point, Hong Kong'')&lt;br /&gt;
: grace à Hazuki Amamiya&lt;br /&gt;
* '''mpserver16.flightgear.org''' (''Dallas, TX, USA'')&lt;br /&gt;
: grace à Rob Dosogne ([http://forum.flightgear.org/ucp.php?i=pm&amp;amp;mode=compose&amp;amp;u=9926 truthsolo])&lt;br /&gt;
: Héberge également une nouvelle page [http://mpserver16.flightgear.org/ Statut des serveurs].&lt;br /&gt;
&lt;br /&gt;
Ce texte fait exception à la licence générale de ce site, ce texte est disponible sous la licence GNU GPL v2.&lt;br /&gt;
&lt;br /&gt;
== Et enfin... ==&lt;br /&gt;
=== Contribuer ===&lt;br /&gt;
Une des nombreuses remarques exprimée dans les forums de FlightGear est &amp;quot;Je souhaiterais contribuer, mais je ne sais pas programmer et je n'ai pas le temps&amp;quot;. Malheureusement, il y a souvent une incompréhension qui fait que beaucoup d'utilisateurs imaginent qu'il est nécessaire de savoir programmer et de disposer de beaucoup de temps libre pour participer. En fait, il y a de très nombreuses façons de contribuer au projet sans avoir besoin d'écrire du code ou de passer des journées sur certaines tâches.&lt;br /&gt;
&lt;br /&gt;
Si vous avez besoin d'idées pour contribuer à FlightGear, vous pourriez jeter un oeil à cet article : [[Volunteer]].&lt;br /&gt;
&lt;br /&gt;
''Merci à Alexandre pour sa traduction  http://aviactu.info/ ''&lt;br /&gt;
''wikification réalisé par [lolalilo]&lt;br /&gt;
[[Category:FlightGear Newsletter]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Pt/Changelog_2.6.0&amp;diff=120662</id>
		<title>Pt/Changelog 2.6.0</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Pt/Changelog_2.6.0&amp;diff=120662"/>
		<updated>2019-10-12T12:34:56Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Changelog translation|FlightGear 2.6.0|http://www.flightgear.org/news/flightgear-v2-6-0-released/}}&lt;br /&gt;
FlightGear 2.6.0 ChangeLog&lt;br /&gt;
&lt;br /&gt;
O time de desenvolvimento do [[FlightGear]] está feliz por anunciar o lançamento da versão 2.6.0 do Flightgear, o simulador grátis de código aberto. &lt;br /&gt;
Essa norva versão contém novas características, melhorias e correções de bugs. Os mais notáveis aperfeiçoamentos em relação à versão 2.4.0 incluem menor tempo para carregar aeronaves IA, ajustes gráficos mais fáceis, inteligência artificial mais sofisticada e melhor usabilidade.&lt;br /&gt;
&lt;br /&gt;
Fundado em 1997, o projeto Flightgear é desenvolvido por um grupo global de voluntários, unidos pela compartilhada ambição de criar o simulador de vôo o mais realista possível que seja livre para usar, modificar e distribuir. O Flightgear é usado em todo o mundo por entusiastas, pesquisadores em universidades, e para exibições interativas em museus.&lt;br /&gt;
&lt;br /&gt;
FLightgear possui mas de 400 aeronaves, um banco de dados de cenário de todo o mundo, um ambiente multiplayer global, modelos detalhados do céu, um sistema aberto e flexível de modelagem de aeronaves, várias opções de rede, suporte a múltiplos displays, uma poderosa linguagem de scripting e arquitetura aberta. E o melhor, ao ter seu código fonte aberto, o simulador é propriedade de toda a comunidade, e todos são encorajados a distribuí-lo.&lt;br /&gt;
&lt;br /&gt;
Faça o download do Flightgear v2.6.0 de graça em [http://www.flightgear.org FlightGear.org]&lt;br /&gt;
&lt;br /&gt;
FlightGear - Voe livre!&lt;br /&gt;
&lt;br /&gt;
=== Algumas das maiores mudanças são: ===&lt;br /&gt;
&lt;br /&gt;
'''Operações de Aeronaves:'''&lt;br /&gt;
* Em aeroportos selecionados, o Flightgear pode automaticamente iniciar na posição apropriada baseado no tipo e tamanho na sua aeronave.&lt;br /&gt;
* Em aeroportos que suportam essa funcionalidade, um display visual da rota de taxiamento no solo o guia para a pista de decolagem ativa, seguindo o caminho correto.&lt;br /&gt;
&lt;br /&gt;
'''Sistema IA (Inteligência Artificial)'''&lt;br /&gt;
* Para reduzir os &amp;quot;engasgos&amp;quot; durante o carregamento de modelos 3D e visando tirar maior vantagem dos processadores de múltiplos núcleos, as aeronaves dos jogadores e de IA agora são carregadas em segundo plano.&lt;br /&gt;
* Para reduzir mais ainda os tempos de carregamento, apenas as partes atualmente visiveis das aeronaves são carregadas do disco.&lt;br /&gt;
* Aeronaves de IA e de jogadores no modo multiplayer não são mais objetos silenciosos, eles podem produzir sons assim como sua própria aeronave.&lt;br /&gt;
&lt;br /&gt;
'''Tráfego de Aeronaves IA'''&lt;br /&gt;
* Muitos novos e mais recentes esquemas de pintura (liveries) para aeronaves IA. Mais de 80 linhas aéreas agoram povoam os céus virtuais.&lt;br /&gt;
* A distância em que as aeronaves IA são mostradas é agora configurável, permitindo ao usuário ajustar o Flightgear para melhor performance.&lt;br /&gt;
* Os pilotos de aeronaves IA receberam treinamento de pouso e agora fazem a aproximação de modo mais realístico, além de liberarem a pista de pouso quando possível.&lt;br /&gt;
* O simulador agora atribui uma posição de estacionamento livre ao iniciar.&lt;br /&gt;
&lt;br /&gt;
'''Dinâmicas de Vôo'''&lt;br /&gt;
* O modelo de dinâmica de vôo JSBSim recebeu uma notável inspeção.&lt;br /&gt;
&lt;br /&gt;
'''Ambiente'''&lt;br /&gt;
* O pacote &amp;quot;Clima Local&amp;quot; foi melhor integrado ao núcleo do Flightgear, e foi renomeado para, &amp;quot;Clima Avançado&amp;quot;. Novas técnicas de renderização permitem núvens mais detalhados sem impactar a performance. Núvens muito altas são renderizadas de modo mais realístico, e todas as núvens se movem com o vendo, também sem impactar a performance.&lt;br /&gt;
&lt;br /&gt;
'''Interface'''&lt;br /&gt;
* Novo sistema de replay. Controles estilo &amp;quot;video-player&amp;quot;, incluindo câmera lenta e fast forward. Pilotos agora podem controlar a aeronave a qualquer momento durante o replay. Ótimo para treinar certas fases do vôo, como a aproximação, quantas vezes quiser.&lt;br /&gt;
* [[Formalizando o Status da Aeronave|Avaliação do Status da Aeronave]] é mostrada no Flightgear Launcher, permitindo que você veja rapidamente a qualidade do modelo 3D, modelo dinâmico de vôo, sistemas e cockpit para a aeronave selecionada.&lt;br /&gt;
* Configurações multiplayer agora podem ser acessadas dentro do simulador. Você pode escolher seu callsign, selecionar um servidor de multiplayer e conectar, tudo dentro do simulador.&lt;br /&gt;
* Download automático de cenário agora ainda mais fácil de usar. Simplesmente selecione a pasta onde quer salvar o cenário e ative essa opção.&lt;br /&gt;
* Efeitos gráficos individuais agora podem ser configurados dentro da janela de Configurações de Renderização (Rendering Settings), permitindo que você faça ajustes finos na performance ou qualidade visual do Flightgear, de dentro do simulador.&lt;br /&gt;
* A simulação da propagação dos sinais de rádio começou e fará a recepção das mensagens da Torre de Controle de Tráfego Aéreo (ATC) e de navaids (apoio a navegação) mais realistas no futuro.&lt;br /&gt;
* Um novo conjunto de opções facilita a criação de setups de com vários monitores (com opções de zoom).&lt;br /&gt;
* Um novo monitor de performance mostra o tempo despendido em cada subsistema.&lt;br /&gt;
&lt;br /&gt;
'''Destaque de aeronaves novas ou melhoradas'''&lt;br /&gt;
* [[A-26 Invader]]: melhorias no cockpit.&lt;br /&gt;
* [[Boeing 777-200ER]]: muitas novas e melhoradas características, incluindo o piloto automático, displays de instrumentos e animações.&lt;br /&gt;
* [[Douglas DC-3-C47|Douglas DC-3/C-47]]&lt;br /&gt;
* [[Polikarpov I16]]: melhorias no cockpit.&lt;br /&gt;
&lt;br /&gt;
'''Infraestrutura de Projeto'''&lt;br /&gt;
* O CMake agora é o sistema de build oficial no Linux, Mac e Windows.&lt;br /&gt;
&lt;br /&gt;
'''Efeitos Visuais'''&lt;br /&gt;
* O mar agora é mais realístico. As ondas de alinham com o vento, e espuma aparece com ventos fortes.&lt;br /&gt;
* Encostas íngremes agora são rochosas.&lt;br /&gt;
* Pistas de pouso e decolagem ficam molhadas com a chuva.&lt;br /&gt;
* Para ajudar desenvolvedores de aeronaves, um único shader combinando componentes bump-map, especular, reflexão e mapeamento de luz está disponível.&lt;br /&gt;
&lt;br /&gt;
'''Outros'''&lt;br /&gt;
* Mais joysticks e pedais de leme são compatíveis, incluindo o Logitech WingMan Interceptor, o Saitek Pro Combat Rudder Pedals e o Thrustmaster HOTAS Warthog.&lt;br /&gt;
* [[FGPanel]], software leve para renderizar painéis de instrumentos 2D, agora incluso como parte do lançamento.&lt;br /&gt;
&lt;br /&gt;
'''Correções de Bugs'''&lt;br /&gt;
* Veja [http://code.google.com/p/flightgear-bugs/issues/list?can=1&amp;amp;q=Milestone%3D2.6.0 nosso bugtracker] para uma extensa lista de bugs que foram corrigidos para este lançamento.&lt;br /&gt;
&lt;br /&gt;
'''Windows'''&lt;br /&gt;
* Versão 64bit restaurada e sua instalação integrada ao instalador principal fgsetp&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[en:Changelog 2.6.0]]&lt;br /&gt;
[[es:Changelog 2.6.0]]&lt;br /&gt;
[[nl:Changelog 2.6.0]]&lt;br /&gt;
[[fr:Changelog 2.6.0]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120609</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120609"/>
		<updated>2019-10-08T20:46:04Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes emocionants funcionalitats, millores i correccions d'errors.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir el temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil i fmod. Les seves funcionalitats són les mateixes que les funcions C/C++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Es/2019.1&amp;diff=120608</id>
		<title>Es/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Es/2019.1&amp;diff=120608"/>
		<updated>2019-10-08T20:45:50Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ayúdenos a traducir en otros idiomas.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
El equipo de desarrollo de FlightGear está encantado de anunciar la liberación de la versión 2019.1 de FlightGear, el simulador de vuelo libre y de código abierto. Esta nueva versión contiene muchas emocionantes funciones, mejoras y correcciones de errores.&lt;br /&gt;
&lt;br /&gt;
Fundado en 1997, FlightGear está desarrollado por un grupo mundial de voluntarios, reunidos por una ambición compartida de crear el simulador de vuelo más realista posible, libre de utilizar, modificar y distribuir. FlightGear se utiliza en todo el mundo por los aficionados a los simuladores de vuelos de sobremesa, para investigación en universidades y para exposiciones interactivas en museos.&lt;br /&gt;
&lt;br /&gt;
FlightGear cuenta con más de 400 aeronaves, una base de datos de escenario a nivel mundial, un entorno multijugador, modelización detallada del cielo, un sistema de modelado de aviones flexible y abierto, opciones de red variadas, soporte de visualización múltiple, un lenguaje de secuencias potente y una arquitectura abierta. Lo mejor de todo, al ser de código abierto, el simulador es propiedad de la comunidad y se invita a todos a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vuela libre!&lt;br /&gt;
== Tiempo ==&lt;br /&gt;
* Interpretación de METAR: cambia la visibilidad de CAVOK a 9.999,0 metros&lt;br /&gt;
* Solución para obtener el tiempo en directo&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* Se ha añadido la capacidad de configurar el tiempo de arranque y la aceleración de una turbina (parámetros &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtro &amp;lt;integrator&amp;gt; ahora se puede restablecer a 0.0 estableciendo la propiedad &amp;lt;trigger&amp;gt; a un valor negativo.&lt;br /&gt;
* Esquema de integración del filtro &amp;lt;integrator&amp;gt; ahora se puede elegir entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (trapezoidal), &amp;quot;ab2&amp;quot; 2º orden Adams-Bashforth y &amp;quot;ab3&amp;quot; 3º orden Adams-Bashforth&lt;br /&gt;
* Ahora se pueden utilizar las funciones &amp;lt;function&amp;gt;: floor, ceil y fmod. Sus funcionalidades son las mismas que las funciones C/C++ correspondientes.&lt;br /&gt;
* &amp;lt;function&amp;gt; ahora comprueba el número de sus argumentos.&lt;br /&gt;
* Nuevo sistema line_actuador del componente&lt;br /&gt;
* Corrección de errores de los cálculos de ángulos de Euler a FGMatrix33&lt;br /&gt;
* Exportar la densidad de combustible en el árbol de propiedades&lt;br /&gt;
* Se han añadido recortes cíclicos para componentes FCS&lt;br /&gt;
* Se ha corregido una regresión que ha evitado que la velocidad de giro de las ruedas acelere mientras que los engranajes se retiraban&lt;br /&gt;
* Se ha añadido la capacidad de controlar el factor de inversión de los motores de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Cambios de fricción del suelo (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Soporte para la caché de textura DDS&lt;br /&gt;
* LOD: Los intervalos de paisaje en blanco y en bruto son ahora deltas, para evitar que se superpongan valores por error del usuario.&lt;br /&gt;
* Permite controlar el corte de estrellas en tiempo de ejecución&lt;br /&gt;
* [[Compositor]]: Nuevo marco de renderizado experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; y &amp;quot;remove-aiobject&amp;quot; para añadir/quitar objetos al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaves ==&lt;br /&gt;
* El Boeing 777 recibió algunas actualizaciones:&lt;br /&gt;
** Puede ahorrar la cantidad de combustible entre las sesiones (permite otras funciones útiles),&lt;br /&gt;
** Las pilas de radio ahora son capaces de 8,33 kHz y puede almacenar las frecuencias entre las sesiones,&lt;br /&gt;
** Los diálogos y sistemas de diálogo de servicios de combustible, carga útil y tierra han recibido mucha atención,&lt;br /&gt;
** El 777 tiene ahora un sistema realista de fly-by-wire (FBW) realista,&lt;br /&gt;
** La fricción dinámica se ha reducido, haciendo que la acción de frenado sea más débil y, por tanto, sea más realista. Tenga en cuenta que es posible que necesite una configuración elevada del autofrenado a pistas cortas (&amp;lt;2000 m), especialmente cuando esté cargado con demasiada carga o en altitud&lt;br /&gt;
** Se ha añadido el nuevo rozamiento estático de YASim.&lt;br /&gt;
** Solicitar cualquier función nueva en el [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 tema oficial del 777 en los foros], tanto Octal450 como Isaak, dedican mucho tiempo a mejorar el 777, estamos abiertos a más propuestas :)&lt;br /&gt;
&lt;br /&gt;
== Otros ==&lt;br /&gt;
* Cambie el nombre de archivo de captura de pantalla para tener la hora de la fecha&lt;br /&gt;
* El menú del Mapa dibuja ahora los helipuertos&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Ca:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Changelog_2019.1&amp;diff=120607</id>
		<title>Changelog 2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Changelog_2019.1&amp;diff=120607"/>
		<updated>2019-10-08T20:44:52Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Available in: [[Changelog_2018.4|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Please help us translate in other languages!&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FlightGear development team is delighted to announce the v2019.1 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes.&lt;br /&gt;
&lt;br /&gt;
Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.&lt;br /&gt;
&lt;br /&gt;
FlightGear features more than 400 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky modeling, a flexible and open aircraft modeling system, varied networking options, multiple display support, a powerful scripting language, and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute. &lt;br /&gt;
&lt;br /&gt;
FlightGear - Fly Free!&lt;br /&gt;
&lt;br /&gt;
== Weather ==&lt;br /&gt;
* METAR interpretation: Change CAVOK visibility to 9999.0 metres&lt;br /&gt;
* Fix for getting live weather&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* Added the ability to set up the starter and acceleration times of a turbine (parameters &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* The &amp;lt;integrator&amp;gt; filter can now be reset to 0.0 by setting its &amp;lt;trigger&amp;gt; property to a negative value.&lt;br /&gt;
* The integration scheme of the &amp;lt;integrator&amp;gt; filter can now be chosen among &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoidal), &amp;quot;ab2&amp;quot; 2nd order Adams-BashForth and &amp;quot;ab3&amp;quot; 3rd order Adams-Bashforth&lt;br /&gt;
* The following functions can now be used in &amp;lt;function&amp;gt;: floor, ceil and fmod. Their functionalities are the same than the corresponding C/C++ functions.&lt;br /&gt;
* &amp;lt;function&amp;gt; now checks the number of its arguments.&lt;br /&gt;
* New system component linear_actuator&lt;br /&gt;
* Bug fix of Euler angles computations in FGMatrix33&lt;br /&gt;
* Export the fuel density to the property tree&lt;br /&gt;
* Added cyclic clipping for FCS components&lt;br /&gt;
* Fixed a regression which prevented the wheels rotation speed to slow down while the gears were retracted&lt;br /&gt;
* Added the ability to control the turbine engines spin down factor&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Yasim ground friction (stiction) changes&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Support for DDS Texture Cache&lt;br /&gt;
* LOD: The scenery ranges for bare and rough are now deltas, to avoid overlapping values by user error.&lt;br /&gt;
* Make star cutoff controllable at runtime&lt;br /&gt;
* [[Compositor]]: New experimental rendering framework&lt;br /&gt;
&lt;br /&gt;
== AI ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; and &amp;quot;remove-aiobject&amp;quot; for adding/removing objects to the AI subsystem.&lt;br /&gt;
&lt;br /&gt;
== Aircraft ==&lt;br /&gt;
* The Boeing 777 received some updates:&lt;br /&gt;
** You can save the amount of fuel between sessions (other useful functions will follow),&lt;br /&gt;
** The radio stacks are now 8.33 kHz capable and you can store the frequencies between sessions,&lt;br /&gt;
** The Fuel, Payload and Ground services dialogs and systems have received a lot of attention,&lt;br /&gt;
** The 777 has now a realistic Fly By Wire (FBW) system,&lt;br /&gt;
** Dynamic friction has been reduced, making braking action weaker and thus more realistic. Be aware that you might need a high autobrake setting on short runways (&amp;lt; 2000m), especially when heavy loaded or at altitude!&lt;br /&gt;
** The new YASim static friction has been added.&lt;br /&gt;
** Please request any new features on [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 the official 777 topic on the forums], both Octal450 and Isaak are spending quite a lot of time on improving the 777, we are open to feature requests :)&lt;br /&gt;
&lt;br /&gt;
== Misc ==&lt;br /&gt;
* Change screenshot filename to have date time&lt;br /&gt;
* Map dialog draws heliports now&lt;br /&gt;
&lt;br /&gt;
== Footnotes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ayúdenos a traducir en otros idiomas.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
El equipo de desarrollo de FlightGear está encantado de anunciar la liberación de la versión 2019.1 de FlightGear, el simulador de vuelo libre y de código abierto. Esta nueva versión contiene muchas emocionantes funciones, mejoras y correcciones de errores.&lt;br /&gt;
&lt;br /&gt;
Fundado en 1997, FlightGear está desarrollado por un grupo mundial de voluntarios, reunidos por una ambición compartida de crear el simulador de vuelo más realista posible, libre de utilizar, modificar y distribuir. FlightGear se utiliza en todo el mundo por los aficionados a los simuladores de vuelos de sobremesa, para investigación en universidades y para exposiciones interactivas en museos.&lt;br /&gt;
&lt;br /&gt;
FlightGear cuenta con más de 400 aeronaves, una base de datos de escenario a nivel mundial, un entorno multijugador, modelización detallada del cielo, un sistema de modelado de aviones flexible y abierto, opciones de red variadas, soporte de visualización múltiple, un lenguaje de secuencias potente y una arquitectura abierta. Lo mejor de todo, al ser de código abierto, el simulador es propiedad de la comunidad y se invita a todos a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vuela libre!&lt;br /&gt;
== Tiempo ==&lt;br /&gt;
* Interpretación de METAR: cambia la visibilidad de CAVOK a 9.999,0 metros&lt;br /&gt;
* Solución para obtener el tiempo en directo&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* Se ha añadido la capacidad de configurar el tiempo de arranque y la aceleración de una turbina (parámetros &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtro &amp;lt;integrator&amp;gt; ahora se puede restablecer a 0.0 estableciendo la propiedad &amp;lt;trigger&amp;gt; a un valor negativo.&lt;br /&gt;
* Esquema de integración del filtro &amp;lt;integrator&amp;gt; ahora se puede elegir entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (trapezoidal), &amp;quot;ab2&amp;quot; 2º orden Adams-Bashforth y &amp;quot;ab3&amp;quot; 3º orden Adams-Bashforth&lt;br /&gt;
* Ahora se pueden utilizar las funciones &amp;lt;function&amp;gt;: floor, ceil y fmod. Sus funcionalidades son las mismas que las funciones C/C++ correspondientes.&lt;br /&gt;
* &amp;lt;function&amp;gt; ahora comprueba el número de sus argumentos.&lt;br /&gt;
* Nuevo sistema line_actuador del componente&lt;br /&gt;
* Corrección de errores de los cálculos de ángulos de Euler a FGMatrix33&lt;br /&gt;
* Exportar la densidad de combustible en el árbol de propiedades&lt;br /&gt;
* Se han añadido recortes cíclicos para componentes FCS&lt;br /&gt;
* Se ha corregido una regresión que ha evitado que la velocidad de giro de las ruedas acelere mientras que los engranajes se retiraban&lt;br /&gt;
* Se ha añadido la capacidad de controlar el factor de inversión de los motores de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Cambios de fricción del suelo (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Soporte para la caché de textura DDS&lt;br /&gt;
* LOD: Los intervalos de paisaje en blanco y en bruto son ahora deltas, para evitar que se superpongan valores por error del usuario.&lt;br /&gt;
* Permite controlar el corte de estrellas en tiempo de ejecución&lt;br /&gt;
* [[Compositor]]: Nuevo marco de renderizado experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; y &amp;quot;remove-aiobject&amp;quot; para añadir/quitar objetos al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaves ==&lt;br /&gt;
* El Boeing 777 recibió algunas actualizaciones:&lt;br /&gt;
** Puede ahorrar la cantidad de combustible entre las sesiones (permite otras funciones útiles),&lt;br /&gt;
** Las pilas de radio ahora son capaces de 8,33 kHz y puede almacenar las frecuencias entre las sesiones,&lt;br /&gt;
** Los diálogos y sistemas de diálogo de servicios de combustible, carga útil y tierra han recibido mucha atención,&lt;br /&gt;
** El 777 tiene ahora un sistema realista de fly-by-wire (FBW) realista,&lt;br /&gt;
** La fricción dinámica se ha reducido, haciendo que la acción de frenado sea más débil y, por tanto, sea más realista. Tenga en cuenta que es posible que necesite una configuración elevada del autofrenado a pistas cortas (&amp;lt;2000 m), especialmente cuando esté cargado con demasiada carga o en altitud&lt;br /&gt;
** Se ha añadido el nuevo rozamiento estático de YASim.&lt;br /&gt;
** Solicitar cualquier función nueva en el [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 tema oficial del 777 en los foros], tanto Octal450 como Isaak, dedican mucho tiempo a mejorar el 777, estamos abiertos a más propuestas :)&lt;br /&gt;
&lt;br /&gt;
== Otros ==&lt;br /&gt;
* Cambie el nombre de archivo de captura de pantalla para tener la hora de la fecha&lt;br /&gt;
* El menú del Mapa dibuja ahora los helipuertos&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Ca:2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Es/2019.1&amp;diff=120606</id>
		<title>Es/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Es/2019.1&amp;diff=120606"/>
		<updated>2019-10-08T20:42:58Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: Created page with &amp;quot;{{changelogs|prev=2018.3|next=2019.2}} Disponible en: English, Chinese, Catalan.&amp;lt;br /&amp;gt;  Ayúdenos a traducir en otros idiomas....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ayúdenos a traducir en otros idiomas.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
El equipo de desarrollo de FlightGear está encantado de anunciar la liberación de la versión 2019.1 de FlightGear, el simulador de vuelo libre y de código abierto. Esta nueva versión contiene muchas emocionantes funciones, mejoras y correcciones de errores.&lt;br /&gt;
&lt;br /&gt;
Fundado en 1997, FlightGear está desarrollado por un grupo mundial de voluntarios, reunidos por una ambición compartida de crear el simulador de vuelo más realista posible, libre de utilizar, modificar y distribuir. FlightGear se utiliza en todo el mundo por los aficionados a los simuladores de vuelos de sobremesa, para investigación en universidades y para exposiciones interactivas en museos.&lt;br /&gt;
&lt;br /&gt;
FlightGear cuenta con más de 400 aeronaves, una base de datos de escenario a nivel mundial, un entorno multijugador, modelización detallada del cielo, un sistema de modelado de aviones flexible y abierto, opciones de red variadas, soporte de visualización múltiple, un lenguaje de secuencias potente y una arquitectura abierta. Lo mejor de todo, al ser de código abierto, el simulador es propiedad de la comunidad y se invita a todos a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vuela libre!&lt;br /&gt;
== Tiempo ==&lt;br /&gt;
* Interpretación de METAR: cambia la visibilidad de CAVOK a 9.999,0 metros&lt;br /&gt;
* Solución para obtener el tiempo en directo&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* Se ha añadido la capacidad de configurar el tiempo de arranque y la aceleración de una turbina (parámetros &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtro &amp;lt;integrator&amp;gt; ahora se puede restablecer a 0.0 estableciendo la propiedad &amp;lt;trigger&amp;gt; a un valor negativo.&lt;br /&gt;
* Esquema de integración del filtro &amp;lt;integrator&amp;gt; ahora se puede elegir entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (trapezoidal), &amp;quot;ab2&amp;quot; 2º orden Adams-Bashforth y &amp;quot;ab3&amp;quot; 3º orden Adams-Bashforth&lt;br /&gt;
* Ahora se pueden utilizar las funciones &amp;lt;function&amp;gt;: floor, ceil y fmod. Sus funcionalidades son las mismas que las funciones C/C++ correspondientes.&lt;br /&gt;
* &amp;lt;function&amp;gt; ahora comprueba el número de sus argumentos.&lt;br /&gt;
* Nuevo sistema line_actuador del componente&lt;br /&gt;
* Corrección de errores de los cálculos de ángulos de Euler a FGMatrix33&lt;br /&gt;
* Exportar la densidad de combustible en el árbol de propiedades&lt;br /&gt;
* Se han añadido recortes cíclicos para componentes FCS&lt;br /&gt;
* Se ha corregido una regresión que ha evitado que la velocidad de giro de las ruedas acelere mientras que los engranajes se retiraban&lt;br /&gt;
* Se ha añadido la capacidad de controlar el factor de inversión de los motores de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Cambios de fricción del suelo (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Soporte para la caché de textura DDS&lt;br /&gt;
* LOD: Los intervalos de paisaje en blanco y en bruto son ahora deltas, para evitar que se superpongan valores por error del usuario.&lt;br /&gt;
* Permite controlar el corte de estrellas en tiempo de ejecución&lt;br /&gt;
* [[Compositor]]: Nuevo marco de renderizado experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; y &amp;quot;remove-aiobject&amp;quot; para añadir/quitar objetos al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaves ==&lt;br /&gt;
* El Boeing 777 recibió algunas actualizaciones:&lt;br /&gt;
** Puede ahorrar la cantidad de combustible entre las sesiones (permite otras funciones útiles),&lt;br /&gt;
** Las pilas de radio ahora son capaces de 8,33 kHz y puede almacenar las frecuencias entre las sesiones,&lt;br /&gt;
** Los diálogos y sistemas de diálogo de servicios de combustible, carga útil y tierra han recibido mucha atención,&lt;br /&gt;
** El 777 tiene ahora un sistema realista de fly-by-wire (FBW) realista,&lt;br /&gt;
** La fricción dinámica se ha reducido, haciendo que la acción de frenado sea más débil y, por tanto, sea más realista. Tenga en cuenta que es posible que necesite una configuración elevada del autofrenado a pistas cortas (&amp;lt;2000 m), especialmente cuando esté cargado con demasiada carga o en altitud&lt;br /&gt;
** Se ha añadido el nuevo rozamiento estático de YASim.&lt;br /&gt;
** Solicitar cualquier función nueva en el [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 tema oficial del 777 en los foros], tanto Octal450 como Isaak, dedican mucho tiempo a mejorar el 777, estamos abiertos a más propuestas :)&lt;br /&gt;
&lt;br /&gt;
== Otros ==&lt;br /&gt;
* Cambie el nombre de archivo de captura de pantalla para tener la hora de la fecha&lt;br /&gt;
* El menú del Mapa dibuja ahora los helipuertos&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Ca:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Zh/2019.1&amp;diff=120605</id>
		<title>Zh/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Zh/2019.1&amp;diff=120605"/>
		<updated>2019-10-08T20:40:15Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
可用语言: [[Zh/2019.1|中文]]，[[Changelog_2018.4|English]], [[Ca/2019.1|Catalan]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
请协助我们将其翻译为更多语言!&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
作为FlightGear开发团队，我们很高兴地宣布，全新的FlightGear 2019.1版本即将推出。这个新版本包含许多令人兴奋的新功能、改善与错误修正。&lt;br /&gt;
&lt;br /&gt;
FlightGear项目启动于1997年，由怀着雄心壮志的全球志愿者团队共同开发，并成功地创造出了可以免费使用、修改和分发的，同时无比真实的飞行模拟器。 FlightGear被世界各地的广大模拟飞行爱好者所使用，也被广泛应用于大学研究和博物馆的互动展览等领域。&lt;br /&gt;
&lt;br /&gt;
FlightGear的特色包括其拥有的400多种机模、全球地景数据库、联机飞行功能、精细的大气建模、灵活开放的飞机建模系统、多种网络选项、多屏显示支持、强大的脚本语言和开放式架构。最重要的是，作为开源模拟器，它属于我们的社区，每个人都可以为之做出贡献。&lt;br /&gt;
&lt;br /&gt;
FlightGear - 自由飞翔!&lt;br /&gt;
&lt;br /&gt;
== 天气 ==&lt;br /&gt;
*  METAR解码：将CAVOK能见度改为9999.0米&lt;br /&gt;
* 修复无法获取实时天气的问题&lt;br /&gt;
&lt;br /&gt;
注：以下部分内容为机器翻译，欢迎各位志愿者参与到改进翻译的工作中！&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
*增加了设置涡轮机启动和加速时间的功能（参数&amp;lt;n1spinup&amp;gt;，&amp;lt;n2spinup&amp;gt;，&amp;lt;n1startrate&amp;gt;，&amp;lt;n2startrate&amp;gt;）。&lt;br /&gt;
*现在可以通过将&amp;lt;trigger&amp;gt;属性设置为负值来将&amp;lt;integrator&amp;gt;过滤器重置为0.0。&lt;br /&gt;
* &amp;lt;integrator&amp;gt;滤波器的积分方案现在可以选择“rect”（欧拉），“陷阱”（梯形），“ab2”二阶Adams-BashForth和“ab3”三阶Adams-Bashforth&lt;br /&gt;
*现在可以在&amp;lt;function&amp;gt;中使用以下函数：floor，ceil和fmod。它们的功能与相应的C / C ++功能相同。&lt;br /&gt;
* &amp;lt;function&amp;gt;现在检查其参数的数量。&lt;br /&gt;
*新系统组件linear_actuator&lt;br /&gt;
* 修复了FGMatrix33中Euler角度计算的错误&lt;br /&gt;
*将燃料密度输出到属性树&lt;br /&gt;
*为FCS组件添加了循环剪辑&lt;br /&gt;
*修正了一个回归，它可以防止车轮转速在齿轮缩回时减速&lt;br /&gt;
*增加了控制涡轮发动机减速因子的能力&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Yasim地面摩擦因数（静摩擦）变化&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
*支持DDS纹理缓存&lt;br /&gt;
* LOD：裸露和粗糙的风景范围改为改变量，以避免用户输入不正确的值。&lt;br /&gt;
*在运行时可以控制星星显示数量&lt;br /&gt;
*Compositor: 试验性的全新渲染框架&lt;br /&gt;
&lt;br /&gt;
== AI ==&lt;br /&gt;
* 更新fgcommands “add-aiobject”和“remove-aiobject”，用于向AI子系统添加/删除对象。&lt;br /&gt;
&lt;br /&gt;
==杂项==&lt;br /&gt;
*更改屏幕截图文件名为日期时间&lt;br /&gt;
*地图对话框现可绘制直升机场&lt;br /&gt;
&lt;br /&gt;
==脚注==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[EN:Changelog 2019.1]]&lt;br /&gt;
[[Ca:2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Changelog_2019.1&amp;diff=120604</id>
		<title>Changelog 2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Changelog_2019.1&amp;diff=120604"/>
		<updated>2019-10-08T20:40:03Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Available in: [[Changelog_2018.4|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Please help us translate in other languages!&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FlightGear development team is delighted to announce the v2019.1 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes.&lt;br /&gt;
&lt;br /&gt;
Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.&lt;br /&gt;
&lt;br /&gt;
FlightGear features more than 400 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky modeling, a flexible and open aircraft modeling system, varied networking options, multiple display support, a powerful scripting language, and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute. &lt;br /&gt;
&lt;br /&gt;
FlightGear - Fly Free!&lt;br /&gt;
&lt;br /&gt;
== Weather ==&lt;br /&gt;
* METAR interpretation: Change CAVOK visibility to 9999.0 metres&lt;br /&gt;
* Fix for getting live weather&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* Added the ability to set up the starter and acceleration times of a turbine (parameters &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* The &amp;lt;integrator&amp;gt; filter can now be reset to 0.0 by setting its &amp;lt;trigger&amp;gt; property to a negative value.&lt;br /&gt;
* The integration scheme of the &amp;lt;integrator&amp;gt; filter can now be chosen among &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoidal), &amp;quot;ab2&amp;quot; 2nd order Adams-BashForth and &amp;quot;ab3&amp;quot; 3rd order Adams-Bashforth&lt;br /&gt;
* The following functions can now be used in &amp;lt;function&amp;gt;: floor, ceil and fmod. Their functionalities are the same than the corresponding C/C++ functions.&lt;br /&gt;
* &amp;lt;function&amp;gt; now checks the number of its arguments.&lt;br /&gt;
* New system component linear_actuator&lt;br /&gt;
* Bug fix of Euler angles computations in FGMatrix33&lt;br /&gt;
* Export the fuel density to the property tree&lt;br /&gt;
* Added cyclic clipping for FCS components&lt;br /&gt;
* Fixed a regression which prevented the wheels rotation speed to slow down while the gears were retracted&lt;br /&gt;
* Added the ability to control the turbine engines spin down factor&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Yasim ground friction (stiction) changes&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Support for DDS Texture Cache&lt;br /&gt;
* LOD: The scenery ranges for bare and rough are now deltas, to avoid overlapping values by user error.&lt;br /&gt;
* Make star cutoff controllable at runtime&lt;br /&gt;
* [[Compositor]]: New experimental rendering framework&lt;br /&gt;
&lt;br /&gt;
== AI ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; and &amp;quot;remove-aiobject&amp;quot; for adding/removing objects to the AI subsystem.&lt;br /&gt;
&lt;br /&gt;
== Aircraft ==&lt;br /&gt;
* The Boeing 777 received some updates:&lt;br /&gt;
** You can save the amount of fuel between sessions (other useful functions will follow),&lt;br /&gt;
** The radio stacks are now 8.33 kHz capable and you can store the frequencies between sessions,&lt;br /&gt;
** The Fuel, Payload and Ground services dialogs and systems have received a lot of attention,&lt;br /&gt;
** The 777 has now a realistic Fly By Wire (FBW) system,&lt;br /&gt;
** Dynamic friction has been reduced, making braking action weaker and thus more realistic. Be aware that you might need a high autobrake setting on short runways (&amp;lt; 2000m), especially when heavy loaded or at altitude!&lt;br /&gt;
** The new YASim static friction has been added.&lt;br /&gt;
** Please request any new features on [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 the official 777 topic on the forums], both Octal450 and Isaak are spending quite a lot of time on improving the 777, we are open to feature requests :)&lt;br /&gt;
&lt;br /&gt;
== Misc ==&lt;br /&gt;
* Change screenshot filename to have date time&lt;br /&gt;
* Map dialog draws heliports now&lt;br /&gt;
&lt;br /&gt;
== Footnotes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120603</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120603"/>
		<updated>2019-10-08T20:38:34Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* JSBSim */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes emocionants funcionalitats, millores i correccions d'errors.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir el temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil i fmod. Les seves funcionalitats són les mateixes que les funcions C/C++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120602</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120602"/>
		<updated>2019-10-08T20:38:07Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* JSBSim */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes emocionants funcionalitats, millores i correccions d'errors.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir el temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil i fmod. Les seves funcionalitats són les mateixes que les funcions C/C ++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120601</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120601"/>
		<updated>2019-10-08T20:35:57Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes emocionants funcionalitats, millores i correccions d'errors.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir el temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil and fmod. Les seves funcionalitats són les mateixes que les funcions C/C ++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120600</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120600"/>
		<updated>2019-10-08T20:34:06Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Notes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes funcions, millores i correccions d'errors emocionants.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir el temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil and fmod. Les seves funcionalitats són les mateixes que les funcions C/C ++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[En:Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120599</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120599"/>
		<updated>2019-10-08T20:33:33Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Temps */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes funcions, millores i correccions d'errors emocionants.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir el temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil and fmod. Les seves funcionalitats són les mateixes que les funcions C/C ++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120598</id>
		<title>Ca/2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/2019.1&amp;diff=120598"/>
		<updated>2019-10-08T20:33:11Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: Created page with &amp;quot;{{changelogs|prev=2018.3|next=2019.2}} Disponible en: English, Chinese, Spanish.&amp;lt;br /&amp;gt;  Ajudeu-nos a traduir en altres idiomes...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Disponible en: [[Changelog 2019.1|English]], [[Zh/2019.1|Chinese]], [[Es/2019.1|Spanish]].&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ajudeu-nos a traduir en altres idiomes.&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
L’equip de desenvolupament de FlightGear està encantat d’anunciar l’alliberament de la versió 2019.1 de FlightGear, el simulador de vol lliure i de codi obert. Aquesta nova versió conté moltes funcions, millores i correccions d'errors emocionants.&lt;br /&gt;
&lt;br /&gt;
Fundat el 1997, FlightGear està desenvolupat per un grup mundial de voluntaris, reunits per una ambició compartida de crear el simulador de vol més realista possible, lliure d’utilitzar, modificar i distribuir. FlightGear s'utilitza en tot el món pels aficionats als simuladors de vols de sobretaula, per a recerca en universitats i per a exposicions interactives en museus.&lt;br /&gt;
&lt;br /&gt;
FlightGear compta amb més de 400 aeronaus, una base de dades d'escenari a nivell mundial, un entorn multijugador, modelització detallada del cel, un sistema de modelatge d’avions flexible i obert, opcions de xarxa variades, suport de visualització múltiple, un llenguatge de seqüències potent i una arquitectura oberta. El millor de tot, al ser de codi obert, el simulador és propietat de la comunitat i es convida a tothom a contribuir.&lt;br /&gt;
&lt;br /&gt;
FlightGear - Vola lliure!&lt;br /&gt;
&lt;br /&gt;
== Temps ==&lt;br /&gt;
* Interpretació de METAR: canvia la visibilitat de CAVOK a 9999,0 metres&lt;br /&gt;
* Solució per obtenir temps en directe&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* S'ha afegit la capacitat de configurar el temps d'arrencada i l'acceleració d'una turbina (paràmetres &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* El filtre &amp;lt;integrator&amp;gt; ara es pot restablir a 0.0 establint-ne la propietat &amp;lt;trigger&amp;gt; a un valor negatiu.&lt;br /&gt;
* Esquema d'integració del filtre &amp;lt;integrator&amp;gt; ara es pot triar entre &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoïdal), &amp;quot;ab2&amp;quot; 2n ordre Adams-BashForth i &amp;quot;ab3&amp;quot; 3r ordre Adams-Bashforth&lt;br /&gt;
* Ara es poden utilitzar les funcions &amp;lt;function&amp;gt;: floor, ceil and fmod. Les seves funcionalitats són les mateixes que les funcions C/C ++ corresponents.&lt;br /&gt;
* &amp;lt;function&amp;gt; ara comprova el nombre dels seus arguments.&lt;br /&gt;
* Nou sistema line_actuador del component&lt;br /&gt;
* Correcció d'errors dels càlculs d'angles d'Euler a FGMatrix33&lt;br /&gt;
* Exporta la densitat de combustible a l’arbre de propietats&lt;br /&gt;
* S'han afegit retalls cíclics per a components FCS&lt;br /&gt;
* S'ha corregit una regressió que ha evitat que la velocitat de gir de les rodes s'acceleri mentre que els engranatges es retiraven&lt;br /&gt;
* S'ha afegit la capacitat de controlar el factor d'inversió dels motors de la turbina&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Canvis de fricció del sòl (stiction) de Yasim&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Suport per a la memòria cau de textura DDS&lt;br /&gt;
* LOD: Els intervals de paisatge en blanc i en brut són ara deltes, per evitar que es superposin valors per error de l'usuari.&lt;br /&gt;
* Permet controlar el tall d’estrelles en temps d’execució&lt;br /&gt;
* [[Compositor]]: Nou marc de renderitzatge experimental&lt;br /&gt;
&lt;br /&gt;
== IA ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; i &amp;quot;remove-aiobject&amp;quot; per afegir/treure objectes al subsistema IA.&lt;br /&gt;
&lt;br /&gt;
== Aeronaus ==&lt;br /&gt;
* El Boeing 777 va rebre algunes actualitzacions:&lt;br /&gt;
** Podeu estalviar la quantitat de combustible entre les sessions (permet altres funcions útils),&lt;br /&gt;
** Les piles de ràdio ara són capaces de 8,33 kHz i podeu emmagatzemar les freqüències entre les sessions,&lt;br /&gt;
** Els diàlegs i sistemes de diàleg de serveis de combustible, càrrega útil i terra han rebut molta atenció,&lt;br /&gt;
** El 777 té ara un sistema realista de fly by wire (FBW) realista,&lt;br /&gt;
** La fricció dinàmica s'ha reduït, fent que l'acció de frenada sigui més feble i, per tant, sigui més realista. Tingueu en compte que és possible que necessiteu una configuració elevada de l'autofrenada a pistes curtes (&amp;lt;2000 m), especialment quan estigui carregat amb massa càrrega o en altitud&lt;br /&gt;
** S'ha afegit el nou fregament estàtic de YASim.&lt;br /&gt;
** Sol·liciteu qualsevol funció nova al [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 fil oficial del 777 als fòrums], tant Octal450 com Isaak, dediquen molt de temps a millorar el 777, estem oberts a més propostes :)&lt;br /&gt;
&lt;br /&gt;
== Altres ==&lt;br /&gt;
* Canvieu el nom de fitxer de captura de pantalla per tenir l'hora de la data&lt;br /&gt;
* El menú del Mapa dibuixa ara els heliports&lt;br /&gt;
&lt;br /&gt;
== Notes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[Changelog 2019.1]]&lt;br /&gt;
[[Es:2019.1]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Changelog_2019.1&amp;diff=120597</id>
		<title>Changelog 2019.1</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Changelog_2019.1&amp;diff=120597"/>
		<updated>2019-10-08T20:18:57Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{changelogs|prev=2018.3|next=2019.2}}&lt;br /&gt;
Available in: [[Changelog_2018.4|English]], [[Zh/2019.1|Chinese]], [[Ca/2019.1|Catalan]], [[Es/2019.1|Spanish]]..&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Please help us translate in other languages!&lt;br /&gt;
&lt;br /&gt;
----&amp;lt;noinclude&amp;gt;&lt;br /&gt;
[[Category:Undocumented templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FlightGear development team is delighted to announce the v2019.1 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes.&lt;br /&gt;
&lt;br /&gt;
Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.&lt;br /&gt;
&lt;br /&gt;
FlightGear features more than 400 aircraft, a worldwide scenery database, a multiplayer environment, detailed sky modeling, a flexible and open aircraft modeling system, varied networking options, multiple display support, a powerful scripting language, and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute. &lt;br /&gt;
&lt;br /&gt;
FlightGear - Fly Free!&lt;br /&gt;
&lt;br /&gt;
== Weather ==&lt;br /&gt;
* METAR interpretation: Change CAVOK visibility to 9999.0 metres&lt;br /&gt;
* Fix for getting live weather&lt;br /&gt;
&lt;br /&gt;
== JSBSim ==&lt;br /&gt;
* Added the ability to set up the starter and acceleration times of a turbine (parameters &amp;lt;n1spinup&amp;gt;, &amp;lt;n2spinup&amp;gt;, &amp;lt;n1startrate&amp;gt;, &amp;lt;n2startrate&amp;gt;).&lt;br /&gt;
* The &amp;lt;integrator&amp;gt; filter can now be reset to 0.0 by setting its &amp;lt;trigger&amp;gt; property to a negative value.&lt;br /&gt;
* The integration scheme of the &amp;lt;integrator&amp;gt; filter can now be chosen among &amp;quot;rect&amp;quot; (Euler), &amp;quot;trap&amp;quot; (Trapezoidal), &amp;quot;ab2&amp;quot; 2nd order Adams-BashForth and &amp;quot;ab3&amp;quot; 3rd order Adams-Bashforth&lt;br /&gt;
* The following functions can now be used in &amp;lt;function&amp;gt;: floor, ceil and fmod. Their functionalities are the same than the corresponding C/C++ functions.&lt;br /&gt;
* &amp;lt;function&amp;gt; now checks the number of its arguments.&lt;br /&gt;
* New system component linear_actuator&lt;br /&gt;
* Bug fix of Euler angles computations in FGMatrix33&lt;br /&gt;
* Export the fuel density to the property tree&lt;br /&gt;
* Added cyclic clipping for FCS components&lt;br /&gt;
* Fixed a regression which prevented the wheels rotation speed to slow down while the gears were retracted&lt;br /&gt;
* Added the ability to control the turbine engines spin down factor&lt;br /&gt;
&lt;br /&gt;
== Yasim ==&lt;br /&gt;
* Yasim ground friction (stiction) changes&lt;br /&gt;
&lt;br /&gt;
== 3D ==&lt;br /&gt;
* Support for DDS Texture Cache&lt;br /&gt;
* LOD: The scenery ranges for bare and rough are now deltas, to avoid overlapping values by user error.&lt;br /&gt;
* Make star cutoff controllable at runtime&lt;br /&gt;
* [[Compositor]]: New experimental rendering framework&lt;br /&gt;
&lt;br /&gt;
== AI ==&lt;br /&gt;
* fgcommands &amp;quot;add-aiobject&amp;quot; and &amp;quot;remove-aiobject&amp;quot; for adding/removing objects to the AI subsystem.&lt;br /&gt;
&lt;br /&gt;
== Aircraft ==&lt;br /&gt;
* The Boeing 777 received some updates:&lt;br /&gt;
** You can save the amount of fuel between sessions (other useful functions will follow),&lt;br /&gt;
** The radio stacks are now 8.33 kHz capable and you can store the frequencies between sessions,&lt;br /&gt;
** The Fuel, Payload and Ground services dialogs and systems have received a lot of attention,&lt;br /&gt;
** The 777 has now a realistic Fly By Wire (FBW) system,&lt;br /&gt;
** Dynamic friction has been reduced, making braking action weaker and thus more realistic. Be aware that you might need a high autobrake setting on short runways (&amp;lt; 2000m), especially when heavy loaded or at altitude!&lt;br /&gt;
** The new YASim static friction has been added.&lt;br /&gt;
** Please request any new features on [https://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=21870&amp;amp;p=350024 the official 777 topic on the forums], both Octal450 and Isaak are spending quite a lot of time on improving the 777, we are open to feature requests :)&lt;br /&gt;
&lt;br /&gt;
== Misc ==&lt;br /&gt;
* Change screenshot filename to have date time&lt;br /&gt;
* Map dialog draws heliports now&lt;br /&gt;
&lt;br /&gt;
== Footnotes ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Changes after 2018.3]]&lt;br /&gt;
[[Category:FlightGear changelogs]]&lt;br /&gt;
[[Zh:2019.1]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/FGAddon&amp;diff=120594</id>
		<title>Ca/FGAddon</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/FGAddon&amp;diff=120594"/>
		<updated>2019-10-06T10:41:10Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Obtenint aeronaus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
[[File:FGAddon logo.png|270px|right]]&lt;br /&gt;
&lt;br /&gt;
L'hangar oficial d'aeronaus '''FGAddon''' és un repositori de control de versions, allotjat a l'[https://sourceforge.net/projects/flightgear/ infraestructura SourceForge] de [[:ca:FlightGear|FlightGear]], i usat per al desenvolupament diari de les aeronaus del simulador.  FGAddon és un repositori de control de versions de {{wikipedia|Subversion|noicon=1|lang=ca}}. Aquestes aeronaus no formen part del paquet base (les aeronaus que s'inclouen al paquet base) — el [[Ca/Cessna 172P|Cessna 172P]] i l'[[UFO]] — es mantenen al repositori de [http://sourceforge.net/p/flightgear/fgdata FGData]), però apareixen amb cada versió estable a les [http://www.flightgear.org/download/ pàgines de descàrrega de FlightGear].&lt;br /&gt;
&lt;br /&gt;
El repositori de desenvolupament d'aeronaus FGAddon s’ha de considerar inestable.  Quan utilitzeu una versió estable de FlightGear, el millor és obtenir avions amb un número de versió coincident del programa base actual que apareix a les [http://www.flightgear.org/download/ pàgines de descàrrega de FlightGear].  Tanmateix, com les versions estables de FlightGear 3.4 en endavant estan etiquetats i presents al repositori de FGAddon, les eines de Subversion poden ser una manera convenient d’obtenir aeronaus individuals o tot l’hangar oficial d’aproximadament 500 avions.  També, si utilitzeu les [[FlightGear build server|últimes versions]] o una [[Building FlightGear|versió autocompilada de FlightGear]] dels [http://sourceforge.net/p/flightgear/_list/git repositoris de control de versions de Git] de FlightGear, utilitzant el FGAddon permet actualitzar l’avió a les últimes versions de desenvolupament.&lt;br /&gt;
&lt;br /&gt;
== Història ==&lt;br /&gt;
[[File:Image103.gif|thumb|Icona original de Win95]]&lt;br /&gt;
El projecte FlightGear va ser concebut el 8 d'abril de 1996 per David Murr, que va proposar un nou simulador de vol per ser desenvolupat per voluntaris&amp;lt;ref&amp;gt;David Murr (Apr 9, 1996).  FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J &amp;quot;A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@&amp;quot;].  Published on the rec.aviation.simulators newsgroup.&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (1996).  FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR &amp;quot;This truly is as real as it gets!&amp;quot; - a proposal for a new flight simulator - REVISION 2.0].&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (Oct 29, 1996).  FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, &amp;quot;The future of flight simulation is here&amp;quot;].  Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (Sep 11, 1998).  FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, &amp;quot;The future of flight simulation is here&amp;quot;].&amp;lt;/ref&amp;gt;.  Part dels objectius inicials van ser desenvolupar rutines gràfiques 2D i 3D per al simulador. No obstant això, aquesta va ser una tasca enorme que va acabar sense finalitzar a principis de 1997, ja que el desenvolupador principal, Eric Korpela, estava acabant la seva tesi. Per tant, a partir del 16 de maig de 1997, Curtis Olson va rellançar el desenvolupament amb un nou projecte basat en les biblioteques d'OpenGL, que permetria crear un simulador de vol funcional en un curt període de temps.&amp;lt;ref&amp;gt;Curtis Olson (Sep 28, 2015).  [http://forum.flightgear.org/viewtopic.php?f=42&amp;amp;t=27558&amp;amp;p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@].  Published on the FlightGear forum.&amp;lt;/ref&amp;gt;  Les primeres contribucions van ser de [[FlightGear CVS|repositoris de control de versions CVS de flightgear i simgear]] originals.&lt;br /&gt;
&lt;br /&gt;
A mesura que el projecte va créixer, també ho va fer la mida, la quantitat i la qualitat dels actius de FlightGear. Aquests actius no estaven organitzats i estaven dispersos per diferents parts d'Internet. Per tant, es va decidir que gran part d’aquest contingut de FlightGear es reuniria i s’emmagatzemaria de manera conjunta en un nou repositori CVS centralitzat anomenat fgdata, que es va crear el 22 d’octubre de 2000. Per permetre la redistribució legal d’aquests actius com a part de la distribució de FlightGear, s’adoptava una política de GPLv2.&lt;br /&gt;
&lt;br /&gt;
Al maig del 2010, el desenvolupament va ser interromput malauradament per ''&amp;quot;l'incident del cafè&amp;quot;'' que va resultar en la pèrdua del servidor domèstic de Curtis que allotjava tots els repositoris de FlightGear&amp;lt;ref&amp;gt;James Turner (May 20, 2010). [http://thread.gmane.org/gmane.games.flightgear.devel/60340/focus=60341 &amp;lt;nowiki&amp;gt;[Flightgear-devel]&amp;lt;/nowiki&amp;gt; Re: Flightgear git repositories (was Re: GIT or CVS - Confusion)] Published on the flightgear-devel mailing list.&amp;lt;/ref&amp;gt;.  Aquests esdeveniments van resultar en un [[FlightGear CVS|migració massiva de tots els repositoris CVS als repositoris de Git]].  A causa de problemes d’amplada de banda, es va decidir que els nous repositoris s’alternessin a la infraestructura de codi obert Gitorious.&lt;br /&gt;
&lt;br /&gt;
Amb el temps que el projecte va créixer, la mida i l'abast del repositori de fgdata es va multiplicar, principalment a causa del creixent nombre d’avions emmagatzemats a [[$FG_ROOT]]/Aircraft, de manera que una divisió era inevitable. Gijs de Rooy va organitzar un primer intent de separació i es va anunciar el 18 d’octubre de 2011&amp;lt;ref&amp;gt;Cedric Sodhi (Oct 18, 2011) [http://thread.gmane.org/gmane.games.flightgear.devel/66846 &amp;lt;nowiki&amp;gt;[Flightgear-devel]&amp;lt;/nowiki&amp;gt; FGData Split Completed - a.k.a Life after the Split] Published on the flightgear-devel mailing list.&amp;lt;/ref&amp;gt;.  Cada avió es va col·locar en el seu propi repositori de Git i tots els avions vinculats de nou a fgdata mitjançant un enfocament del submodul Git. No obstant això, aquest intent va fallar i va ser abandonat. A partir d'aquesta data fins a finals de 2014, el disseny de la divisió fgdata es va discutir a la llista de correu de desenvolupament i es va resumir a l'article wiki de [[FlightGear Git: splitting fgdata|FlightGear Git: dividint fgdata]].  En les etapes de planificació, els repositoris es coneixien com a fgdata-old dividint-se en [[FGData]] (també conegut com a fgdata-new) i FGAddon (també conegut com a flightgear-aircraft i fgaircraft).  Després de mitja dècada de planificació, es va decidir que la millor solució per al desenvolupament d’avions de FlightGear seria un únic repositori de Subversion centralitzat. Això facilitaria la gestió i el manteniment comunitari de l’avió, alhora que proporciona modularitat i descàrregues més petites i mides de repositoris locals més petits.&lt;br /&gt;
&lt;br /&gt;
A finals de 2014, Gitorious, el proveïdor de la infraestructura de codi obert per al codi font de FlightGear i els repositoris de dades, va anunciar que tancaria els seus serveis fins al maig de 2015 a causa de la seva adquisició per GitLab. Això va motivar la divisió de fgdata-old i un canvi a l'infraestructura de codi obert SourceForge per allotjar els repositoris VC. Altres parts de la infraestructura de FlightGear ja estaven allotjades per SourceForge, fent que el moviment fos natural.  Segellant l’acord, SourceForge va acceptar per escrit allotjar l’enorme col·lecció d’avions de FlightGear, la mida de la qual no té rival en cercles de codi obert. Avui en dia, el repositori SVN de FGAddon, juntament amb la major part de la infraestructura del projecte FlightGear, està allotjat a SourceForge.&lt;br /&gt;
&lt;br /&gt;
A l'agost de 2015, es va escriure un nou document de política de FlightGear per codificar els estàndards no escrits del projecte&amp;lt;ref&amp;gt;[http://www.flightgear.org/flightgear-policy-document/ FlightGear Policy Document and Roadmap], draft document.&amp;lt;/ref&amp;gt;.  Amb aquest document, la política de llicències dels avions de FlightGear allotjada a FGAddon ha estat actualitzada ed GPLv2-only a GPLv2+. Per combatre la proliferació de llicències, cal evitar complicacions mitjançant el treball d’una aeronau a una altra, i per la integritat i el bon projecte del FlightGear, es recomana que tot el contingut original (allotjat a FGAddon o en qualsevol altre lloc) sigui llicenciat amb GPLv2+.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
{{FGCquote&lt;br /&gt;
|1= The short summary is that we already were maintaining a well established presence on sourceforge. So after quite a bit of discussion, we decided to consolidate there. In addition, we had a perpetual complaint that the fgdata git repository was far too big for most people to initially download (1Gb+). Thus we split off most of the aircraft (expecting unbounded future growth potential) into an svn repository called fgaddon. Sourceforge supports both git and svn repositories. This puts a dependency on a central svn server for our fgaddon aircraft repository, but lightens the weight for anyone wanting to checkout a copy of everything (you don't need a copy of the entire development history, and a copy of every version ever created of every aircraft if you just want to have the latest versions.) Plus svn allows checking out subtrees (without needing the whole repository) so this can also serve as a potential JIT single aircraft service provider. Of course there are always multiple ways to solve every problem and of course every engineering decision has trade offs. Github is a nice provider, no doubt. I have been using them for a number of my own personal repositories. Git of course has ways to address many of the issues we have addressed, but of course everything has strengths and weaknesses.&lt;br /&gt;
|2= {{cite web&lt;br /&gt;
  | url    = http://sourceforge.net/p/flightgear/mailman/message/35054405/&lt;br /&gt;
  | title  = &amp;lt;nowiki&amp;gt;Re: [Flightgear-devel] FlightGear and GitHub&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  | author = &amp;lt;nowiki&amp;gt;Curtis Olson&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  | date   = Apr 30th, 2016&lt;br /&gt;
  | added   = Apr 30th, 2016&lt;br /&gt;
  | script_version = 0.25&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Obtenint aeronaus ==&lt;br /&gt;
&lt;br /&gt;
{{tip|Si esteu interessats a obtenir aeronaus per a llançaments de FlightGear estables i no teniu coneixement del control de versions, heu de visitar el [[Ca/Hangars de FlightGear|Hangars de FlightGear]] per descarregar-les.}}&lt;br /&gt;
{{caution|Si les versions de les aeronaus de FlightGear i FGAddon no coincideixen, poden aparèixer errors i el suport en versions no compatibles no serà efectuat per la comunitat de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
Amb accés a les eines Subversion (SVN), el repositori de control de versions de FGAddon pot ser una forma convenient d’obtenir avions per utilitzar-los dins d’una versió FlightGear específica directament des de la font oficial.  When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match.  The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user.&lt;br /&gt;
&lt;br /&gt;
=== Preparació ===&lt;br /&gt;
To use the FGAddon repository, the Subversion tools need to be installed:&lt;br /&gt;
* '''MS Windows''': Install one of the [https://subversion.apache.org/packages.html#windows many Subversion clients].  For example [https://sliksvn.com/download/ SlikSVN] is one of the best command line versions and the best for aircraft development, and [http://tortoisesvn.net/ TortoiseSVN] provides a user friendly graphical user interface (GUI) by integrating into Windows Explorer.&lt;br /&gt;
* '''Mac OS X''': Install the [https://subversion.apache.org/packages.html#osx official Subversion client].&lt;br /&gt;
* '''GNU/Linux''': Install the Subversion client via the package manager.  This will usually be in a package called &amp;lt;code&amp;gt;subversion-*.{rpm,deb}&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Directori de FGAddon ===&lt;br /&gt;
To know how to use the FGAddon repository, an understanding of the repository directory layout is essential.&lt;br /&gt;
* &amp;lt;code&amp;gt;/trunk&amp;lt;/code&amp;gt;:  This base directory is where the in-development versions of the aircraft are located.&lt;br /&gt;
* &amp;lt;code&amp;gt;/branches/release-x.y.z/&amp;lt;/code&amp;gt;:  These directories correspond to the specific stable FlightGear releases.&lt;br /&gt;
&lt;br /&gt;
The [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ web interface for the FGAddon repository] allows all of the aircraft to be browsed.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega ===&lt;br /&gt;
[[File:V22Osprey.jpg|thumb|200px|Aircraft to be downloaded]]&lt;br /&gt;
Firstly, choose an aircraft to download.  The [[Bell Boeing V-22 Osprey]] will be used in this example.&lt;br /&gt;
&lt;br /&gt;
==== Command line ====&lt;br /&gt;
&lt;br /&gt;
To download the aircraft for FlightGear 3.4, simply type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|branch=branches/release-3.4.0|path=Aircraft/V22-Osprey|post=}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
To obtain the in-development version, type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|path=Aircraft/V22-Osprey|post=}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If all of the ~500 aircraft from the repository are desired - beware that this will be a huge download of over 6 GB - use the following command:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|post=flightgear-fgaddon}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
When using a stable FlightGear release, for example FlightGear 2016.1, to obtain all of the FGAddon aircraft to match the installed FlightGear version, use:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|branch=branches/release-2016.1|post=flightgear-fgaddon}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==== GUI clients and TortoiseSVN ====&lt;br /&gt;
&lt;br /&gt;
When using one of the Subversion GUIs (graphical user interfaces), simply copy one of the above &amp;lt;code&amp;gt;https://&amp;lt;/code&amp;gt; URLs and use that in the GUI (each GUI is different, so see the relevant documentation for help).  For the unique TortoiseSVN tool, simply:&lt;br /&gt;
&lt;br /&gt;
* In Windows Explorer, create a new empty folder for the aircraft (or aircraft collection).&lt;br /&gt;
* In the new folder, right click and select &amp;lt;code&amp;gt;SVN Checkout...&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Copy and paste the URL, for example {{fgaddon source|path=Aircraft/V22-Osprey|type=svn|full=1}}, leave all other settings as they are, and import by clicking on &amp;lt;code&amp;gt;OK&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
For more details, see the [http://tortoisesvn.net/support.html TortoiseSVN documentation].  Note that there is an option to install the command line tools when installing TortoiseSVN.&lt;br /&gt;
&lt;br /&gt;
=== Flying ===&lt;br /&gt;
&lt;br /&gt;
To use the newly downloaded aircraft, please see the [[Howto:Install aircraft]] article, skipping the instructions for downloading and unzipping the aircraft.&lt;br /&gt;
&lt;br /&gt;
=== Updates ===&lt;br /&gt;
With a checked out copy of the &amp;lt;code&amp;gt;/trunk&amp;lt;/code&amp;gt; in-development version, the aircraft can be updated to the latest version using the command:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn up&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Aircraft development ==&lt;br /&gt;
&lt;br /&gt;
{{tip|The FlightGear community encourages aircraft development directly within FGAddon.}}&lt;br /&gt;
&lt;br /&gt;
=== Contact the original aircraft authors ===&lt;br /&gt;
&lt;br /&gt;
The first step for developing and advancing the aircraft of the official FlightGear hangar, or from one of the [[Flightgear_hangars#Aircraft_hangars|private hangars]] for that matter, is to make contact with the original aircraft author(s).  Their names can be found within the &amp;lt;code&amp;gt;*-set.xml&amp;lt;/code&amp;gt; file, within the &amp;lt;code&amp;gt;&amp;lt;authors&amp;gt;&amp;lt;/code&amp;gt; XML tag.  Often the contact email address will be listed in a README file or some other text file in the base aircraft directory.  If not, contact can sometimes be established via the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list].  Contacting the original authors is important to see if the aircraft is currently being actively developed, and if you can join in as part of the development team.&lt;br /&gt;
&lt;br /&gt;
=== SourceForge account ===&lt;br /&gt;
&lt;br /&gt;
To work on the official aircraft collection, a [https://sourceforge.net/user/registration/ SourceForge account] should first be set up.  This will allow to either directly commit to the FGAddon repository, if commit access has been been granted, or to work in as part of a SourceForge development team.  The registration process is lightning quick and the SourceForge developer infrastructure and developer services will be accessible in under a minute.&lt;br /&gt;
&lt;br /&gt;
=== Commit access ===&lt;br /&gt;
&lt;br /&gt;
Before obtaining commit access, an all-out effort to contact the original author(s) should be made to determine if the aircraft is actively being developed.  If this is unsuccessful, sign up for the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list] and ask for help there.  If the aircraft has a current maintainer, you will be directed as to how to proceed with development.  Otherwise ask if someone could volunteer to mentor you in the process of becoming an aircraft developer with full commit access.&lt;br /&gt;
&lt;br /&gt;
To obtain commit access, you will first need:&lt;br /&gt;
# To demonstrate your capabilities and development skills.&lt;br /&gt;
# To show that you understand the [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document]. &lt;br /&gt;
# To show an understanding of the GPL licensing issues, and that you can be trusted not to use copyrighted, non-GPL material.&lt;br /&gt;
# To earn the trust of the FlightGear community.&lt;br /&gt;
&lt;br /&gt;
These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.&lt;br /&gt;
&lt;br /&gt;
To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to proceed.  Depending on the [[#Development_scenarios|development scenario]], this maybe by merge request, file transfer, the primitive patch system, or any other convenient way.  Once you believe you have proven your capabilities and you are knowledgeable about GPL licensing issues, you should write a mail to the development mailing list asking if you can be granted commit access, providing your SourceForge username.&lt;br /&gt;
&lt;br /&gt;
=== FGAddon commitlog mailing list ===&lt;br /&gt;
&lt;br /&gt;
To follow all changes which occur in the FGAddon repository, subscribe to the dedicated [https://lists.sourceforge.net/lists/listinfo/flightgear-fgaddon-commitlogs Flightgear FGAddon commitlogs mailing list].  One email is sent per commit, as the commit is made.&lt;br /&gt;
&lt;br /&gt;
== Version control tools ==&lt;br /&gt;
&lt;br /&gt;
To access FGAddon and use it for aircraft development, the Subversion or SVN version control tools are needed.  Alternatively git-svn provides an interface for those who prefer the git version control tools.&lt;br /&gt;
&lt;br /&gt;
=== Subversion ===&lt;br /&gt;
&lt;br /&gt;
==== Set up ====&lt;br /&gt;
The FGAddon aircraft hangar is stored in a remote Subversion repository located on the SourceForge infrastructure, and therefore it is simplest to use the SVN tools for aircraft development and will cause the least problems.  See the [[#Preparation|Subversion installation section]] for setting up the tool chain.&lt;br /&gt;
&lt;br /&gt;
==== Repository checkout ====&lt;br /&gt;
The first step is to 'checkout' a copy of either the repository trunk or one of the aircraft in the trunk:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn co &amp;lt;url&amp;gt; &amp;lt;dir&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the relevant URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section.  This command will create a local subversion repository copy in the given &amp;lt;code&amp;gt;&amp;lt;dir&amp;gt;&amp;lt;/code&amp;gt; directory.  Note that this will only contain the part of the FGAddon repository specified in the URL.  This means that Subversion allows you to checkout either a single file all the way to the entire remote repository.&lt;br /&gt;
&lt;br /&gt;
==== Information and history ====&lt;br /&gt;
At any point to see information about the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn info&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the history of the checked out copy of the repository, type one of:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn log&lt;br /&gt;
svn log | less&lt;br /&gt;
svn log -v | less&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Daily usage ====&lt;br /&gt;
The main Subversion command you will be using is:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn add &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will register the file or directory &amp;lt;code&amp;gt;&amp;lt;path&amp;gt;&amp;lt;/code&amp;gt; within the local repository to allow it to later be 'committed' and sent to the remote repository.  To move or rename a file or directory, use:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn mv &amp;lt;path1&amp;gt; &amp;lt;path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This should be used rather than normal file moving/renaming so that the change is tracked in the local repository.  To remove a file from the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn rm &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current status of the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn st&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To update the local repository with changes in the remote repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn up&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Committing changes ====&lt;br /&gt;
All of the above operations only occur on the local repository copy - the remote FGAddon repository at SourceForge will know nothing of these changes.  To send all your changes to FGAddon, you need to commit the changes:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will open up an editor to allow you to write an informative commit log message.  When committing, it is best to make small modular commits so that each commit corresponds to a single purpose.  Note that you can only commit to FGAddon if you have [[#Commit access|commit access]].&lt;br /&gt;
&lt;br /&gt;
==== Branching ====&lt;br /&gt;
The concept of Subversion branching is currently only used in the FlightGear project for tagging the stable releases.  However if you are curious about branching, see the [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html Branching and Merging chapter of the Subversion manual], and the [https://www.orcaware.com/svn/wiki/Svnmerge.py svnmerge.py script] which can greatly simplify the process.&lt;br /&gt;
&lt;br /&gt;
=== Git-svn ===&lt;br /&gt;
&lt;br /&gt;
The git-svn tool is useful for those who are already familiar with using git repositories, or those who wish to have their own private aircraft development playground.  Git-svn provides a bridge between the remote FGAddon Subversion repository and a local git repository.  For those unfamiliar with git, the git-svn bridge together with the git repository is far more complicated to use than the native [[#Subversion|Subversion tools]].  For more information on using git, see [[Howto:Start using git]]. The following will assume that only a single aircraft will be stored in the local git repository.&lt;br /&gt;
&lt;br /&gt;
==== Set up ====&lt;br /&gt;
The git distributed version control system needs to first be [https://git-scm.com/downloads installed].&lt;br /&gt;
&lt;br /&gt;
==== Cloning a single aircraft ====&lt;br /&gt;
The first step is to 'clone' a copy of one of the aircraft in the remote Subversion trunk:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn clone &amp;lt;aircraft_url&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the relevant aircraft URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section.  The URL depends on your [[#Commit access|FGAddon commit access status]].  The clone command will create a local git repository containing solely the aircraft of interest, and initialise the git-svn bridge.&lt;br /&gt;
&lt;br /&gt;
==== Information and history ====&lt;br /&gt;
At any point to see information about the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn info&lt;br /&gt;
git branch -vva&lt;br /&gt;
git remote -v&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the history of the checked out copy of the repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Daily usage ====&lt;br /&gt;
The main git command you will be using is:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git add &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will register the file or directory &amp;lt;code&amp;gt;&amp;lt;path&amp;gt;&amp;lt;/code&amp;gt; within the local repository to allow it to later be 'committed' to the local git repository.  To move or rename a file or directory, use:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git mv &amp;lt;path1&amp;gt; &amp;lt;path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However note that git history is not as robust as svn history.  See the [[#Moving_or_renaming_files|git-svn file moving/renaming deficiency section]] for how to better perform this operation.  To remove a file from the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git rm &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current status of the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git status&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Committing changes ====&lt;br /&gt;
As git is a distributed version control system, changes are committed to the local git repository.&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git commit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will open up an editor to allow you to write an informative commit log message.  The commit is local and will not be sent to FGAddon.&lt;br /&gt;
&lt;br /&gt;
==== Dedicated FGAddon branch ====&lt;br /&gt;
In the examples above, only a single branch was assumed in the repository.  If interaction with a remote git repository or branching within the local git repository is desired, then a different strategy is required.  The reason being that the branch that synchronises with FGAddon must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn preserve a linear history].  This means only cherry-picking of the desired changes into that branch is allowed.&lt;br /&gt;
&lt;br /&gt;
In this example, two branches will be set up in the local git repository:&lt;br /&gt;
* &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt;:  This branch will be dedicated for FGAddon synchronisation and will preserve a linear history.&lt;br /&gt;
* &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt;:  A master branch for aircraft development, allowing for mergers and other non-linear history operations.&lt;br /&gt;
&lt;br /&gt;
Assuming a [[#Cloning_a_single_aircraft|newly cloned repository]], create the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git branch fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And switch to that branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FGAddon synchronisation can then be performed on this branch.  To pull in the developments from the master branch, use cherry-picking to apply a sequentially ordered list of commit hashes:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the list of commits to be sent to FGAddon prior to dcommitting, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And to see the changes as a single diff:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Synchronising ====&lt;br /&gt;
To send the changes to the remote FGAddon repository, firstly change to the dedicated &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure the local git-svn repository is up to date with all changes that have occurred in FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then push or dcommit the changes to FGAddon with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Deficiencies of git-svn ===&lt;br /&gt;
&lt;br /&gt;
{{warning|Performing a &amp;lt;code&amp;gt;git-svn clone&amp;lt;/code&amp;gt; of the &amp;lt;code&amp;gt;/trunk/&amp;lt;/code&amp;gt; or entire repository is not recommended, as the entire repository history will be downloaded, resulting in a huge local repository, as well as putting a large strain on the FlightGear open source infrastructure.}}&lt;br /&gt;
&lt;br /&gt;
It is important to understand that there are a number of operations in which git-svn is deficient.  In many cases, the svn tools should be used instead.&lt;br /&gt;
&lt;br /&gt;
==== Copying files between aircraft ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn does not maintain the file copying history normally present in a Subversion repository.}}&lt;br /&gt;
&lt;br /&gt;
The most important of these is the copying of content from other FGAddon aircraft.  In this case you will need FGAddon commit access and a local svn copy of the repository.  Firstly synchronise the repositories by dcommitting all changes back to FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the local svn repository, copy the file:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn cp Aircraft/&amp;lt;aircraft1&amp;gt;/&amp;lt;file_path1&amp;gt; Aircraft/&amp;lt;aircraft2&amp;gt;/&amp;lt;file_path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And commit the change:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Back in the local git-svn repository, pull in the new files:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the subversion tools avoids the FGAddon repository backend from significantly increasing in size, as [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html#svn.branchmerge.using.create svn copies are cheap].&lt;br /&gt;
&lt;br /&gt;
==== Moving or renaming files ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn does not always maintain the file moving or renaming history normally present in a Subversion repository.}}&lt;br /&gt;
&lt;br /&gt;
This problem stems from the fact that svn history is more robust than that of git.  The &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;git mv&amp;lt;/code&amp;gt; commands are not equivalent.  The subversion command stores the move history directly in the repository whereas git does not (git instead uses heuristic methods to try to detect history, after the commit).  The result of using git-svn is that often the move will not be detected and the FGAddon history will show one file or directory being deleted and another added.  This also causes the repository backend to increase in size, whereas &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; will not cause any significant size increase.  If you wish to have a better historical record in the FGAddon repository and be considerate to the repository backend, it is recommended that you temporarily switch to the subversion tools.  Firstly, synchronise the repositories:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the local svn repository, move or rename the file:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn mv Aircraft/&amp;lt;aircraft&amp;gt;/&amp;lt;file_path1&amp;gt; Aircraft/&amp;lt;aircraft&amp;gt;/&amp;lt;file_path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And commit the change:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Back in the local git-svn repository, pull in the changes with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Copying files within one aircraft ====&lt;br /&gt;
&lt;br /&gt;
Just as the &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; command stores the move information directly within the repository, so does &amp;lt;code&amp;gt;svn cp&amp;lt;/code&amp;gt; store the copy information.  Therefore if you would like to duplicate a text file and modify it, using the native Subversion tools instead of git-svn for this operation allows for the file history to be permanently preserved in the FGAddon repository.&lt;br /&gt;
&lt;br /&gt;
==== Subversion properties ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn currently only supports the &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property, all other properties are ignored and cannot be added, changed, or removed in a git-svn clone of the aircraft.}}&lt;br /&gt;
&lt;br /&gt;
Internally, Subversion identifies binary files using the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; repository property.  However as git-svn cannot set this property when using the &amp;lt;code&amp;gt;git add&amp;lt;/code&amp;gt; command, the result is that binary files will be treated as text.  Binary diffs will be seen when using &amp;lt;code&amp;gt;svn diff&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;git diff&amp;lt;/code&amp;gt;, and a binary diff will be shown in the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]] messages.  As this issue is not unique to git-svn, to work around this issue please see the [[#Binary diffs|binary diffs]] section.&lt;br /&gt;
&lt;br /&gt;
==== Protocols other than svn+ssh ====&lt;br /&gt;
&lt;br /&gt;
The command &amp;lt;code&amp;gt;git svn init&amp;lt;/code&amp;gt; replicates the entire history of an aircraft into a local repository.  As part of this process, it generates a git commit ID or hash for every Subversion revision. The problem is that the git commit ID depends on the protocol used to read from the Subversion repository (likely a git bug).   Hence:&lt;br /&gt;
&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
and&lt;br /&gt;
&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=https|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
will result in two different and incompatible git repositories, even though they contain the same data. The incompatibility is not immediately apparent but it will bite later. Suppose someone with read-only access to FGAddon uses the https method, then asks a FGAddon gatekeeper to commit their changes. The gatekeeper, naturally, uses svn+ssh, as this is the only protocol granting write permissions. When the gatekeeper tries to merge the contributor's https clone into their own svn+ssh clone, git will complain that the two repositories have no history in common, and flag every change as a conflict.&lt;br /&gt;
&lt;br /&gt;
Therefore, if you are planning to make any changes to an aircraft, be sure to use svn+ssh even if you do not yet have commit permissions on FGAddon. svn+ssh does not require write permissions, it only requires a SourceForge user ID.&lt;br /&gt;
&lt;br /&gt;
== FGAddon development concepts ==&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
To add a new aircraft to the FGAddon repository, the SVN tools are required.  If you encounter &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property problems when adding a new aircraft, see the [[#Mime-type problems|mime-type problems section]] for how to resolve the issue.  Or if you have a &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property problem, see the [[#Executable flag|executable flag problem section]].&lt;br /&gt;
&lt;br /&gt;
==== svn import ====&lt;br /&gt;
&lt;br /&gt;
{{warning|The &amp;lt;code&amp;gt;svn import&amp;lt;/code&amp;gt; command described herein will send all contents of the specified directory directly into FGAddon without warning and without a way to cancel the operation.  Therefore special care must be taken when specifying the directory to upload into FGAddon, as well as the target FGAddon directory.  See the [[#svn add|svn add]] section below for a safer way to add a new aircraft.}}&lt;br /&gt;
&lt;br /&gt;
The [http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import svn import] command is the easiest method to use and does not require a local copy of the repository to be checked out.  To start:&lt;br /&gt;
&lt;br /&gt;
# Create an empty local aircraft directory.&lt;br /&gt;
# Copy the aircraft files into this directory.&lt;br /&gt;
# Carefully check all files to make sure there are no hidden or temporary files that should not be uploaded to FGAddon.&lt;br /&gt;
&lt;br /&gt;
Assuming the Dead Simple Human Powered Airplane (DaSH PA or &amp;quot;DaSH&amp;quot;) aircraft as an example, located in the &amp;lt;code&amp;gt;DaSH/&amp;lt;/code&amp;gt; directory, on the command line run:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source&lt;br /&gt;
| cmd      = svn import DaSH/&lt;br /&gt;
| protocol = svn+ssh&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| type     = svn&lt;br /&gt;
| path     = Aircraft/DaSH/&lt;br /&gt;
| post     = -m \&lt;br /&gt;
| full     = 1&lt;br /&gt;
}}&lt;br /&gt;
    &amp;quot;Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=24495 .&amp;quot;&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name.  This will add all the files into FGAddon with commit log message with the summary line &amp;lt;code&amp;gt;Initial import of the DaSH human powered aircraft.&amp;lt;/code&amp;gt;, followed by a blank line, and then a detailed description pointing to the original location or discussion of the aircraft.  To see if the aircraft has been successfully added to the repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source&lt;br /&gt;
| cmd      = svn list&lt;br /&gt;
| protocol = svn+ssh&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| type     = svn&lt;br /&gt;
| path     = Aircraft/DaSH/&lt;br /&gt;
| full     = 1&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Or visit the {{fgaddon source|path=Aircraft|text=FGAddon web interface}}.  The aircraft can then be checked out as described in the [[#Development scenarios|Development scenarios section]].&lt;br /&gt;
&lt;br /&gt;
==== svn add ====&lt;br /&gt;
&lt;br /&gt;
If a local copy of the FGAddon trunk is present, then the &amp;lt;code&amp;gt;svn add&amp;lt;/code&amp;gt; command can be used instead.  This is far safer than the &amp;lt;code&amp;gt;svn import&amp;lt;/code&amp;gt; command, as the change can be double checked before committing.  In the &amp;lt;code&amp;gt;Aircraft/&amp;lt;/code&amp;gt; directory of the local repository, create the &amp;lt;code&amp;gt;DaSH/&amp;lt;/code&amp;gt; directory.  This can either be empty or contain all files of the initial aircraft.  Then on the command line, add the aircraft to the local repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn add DaSH/&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then double check the changes prior to committing:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn st&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And send the changes to FGAddon with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An editor, often vi&amp;lt;ref&amp;gt;[http://www.vim.org/docs.php Vim documentation]&amp;lt;/ref&amp;gt;, will open and the commit message can be composed.  Alternatively the commit log message can be specified on the command line with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -m &amp;quot;&amp;lt;subject_line&amp;gt;\n\n&amp;lt;detailed_description&amp;gt;&amp;quot;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Commit blocking by pre-commit hooks ===&lt;br /&gt;
&lt;br /&gt;
Sometimes when committing to FGAddon, the commit will be blocked the following will be printed out:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is due to the presence of two repository pre-commit hook scripts which check the quality of the commit, blocking it if a text file is set to a binary file mime-type or if the executable flag is set.  These scripts are simply to protect the repository and to keep it clean.&lt;br /&gt;
&lt;br /&gt;
==== Mime-type problems ====&lt;br /&gt;
&lt;br /&gt;
Sometimes when attempting to commit files to FGAddon using the SVN tools, the commit will be blocked with the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Sending        dash-set.xml&lt;br /&gt;
svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&lt;br /&gt;
Aborting the commit, the svn:mime-type property is labelling the following text&lt;br /&gt;
files as binary:&lt;br /&gt;
&lt;br /&gt;
  dash-set.xml:  svn:mime-type=application/xml&lt;br /&gt;
&lt;br /&gt;
Before committing, please remove this property by typing 'svn propdel svn:mime-&lt;br /&gt;
type file_name' for all affected files.  This will allow the text files to be&lt;br /&gt;
treated as text within the FGAddon repository.&lt;br /&gt;
&lt;br /&gt;
To avoid the svn:mime-type property being incorrectly set by your subversion&lt;br /&gt;
client, the subversion configuration file at $HOME/.subversion/config or&lt;br /&gt;
%appdata%\roaming\subversion\config should be edited and a new entry added to&lt;br /&gt;
[auto-props] for each affected file type.  In most cases, the problem is with&lt;br /&gt;
XML files being labelled as &amp;quot;application/xml&amp;quot; by a library called libmagic.  To&lt;br /&gt;
override this, add the following to the svn config file:&lt;br /&gt;
&lt;br /&gt;
*.xml = svn:mime-type=text/xml&lt;br /&gt;
&lt;br /&gt;
svn: E165001: Your commit message was left in a temporary file:&lt;br /&gt;
svn: E165001:    '/flightgear/repo_testing/svn-commit.tmp'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Despite messages about adding or sending files, no change will have occurred in the FGAddon repository.  This message is created by a repository pre-commit hook script which checks if the Subversion &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property is set on a list of known text files and, if the mime-type is set to a binary format, the commit is blocked.  The reason for this block is to protect the repository.  Newer SVN clients rely on a 3rd party library known as libmagic which will detect the aircraft XML files as the binary mime-type of &amp;lt;code&amp;gt;application/xml&amp;lt;/code&amp;gt;.  The result is that the XML files are treated as binary files in the repository.  This behaviour is completely undesirable, as changes cannot be followed on the [[#FGAddon commitlog mailing list|flightgear-fgaddon-commitlogs mailing list]] or in the repository history, and the size of the commits become orders of magnitude larger.  Therefore this buggy behaviour has been blocked for the protection of the FlightGear project.  To remove the problem, follow the instructions in the message and, using the command line tools, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propdel svn:mime-type &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Repeat this for each text file listed in the error message.  Then commit again, using the commit message saved in the &amp;lt;code&amp;gt;svn-commit.tmp&amp;lt;/code&amp;gt; file.  The message file name will be reported in the commit failure message, but check its contents first:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
cat svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And reperform the commit:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -F svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Subversion config file =====&lt;br /&gt;
&lt;br /&gt;
The automatic property setting of &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; can be controlled by modifying the Subversion &amp;lt;code&amp;gt;config&amp;lt;/code&amp;gt; file.  Firstly in the &amp;lt;code&amp;gt;[miscellany]&amp;lt;/code&amp;gt; section, make sure that the auto-properties are turned on:&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
enable-auto-props = yes&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the &amp;lt;code&amp;gt;[auto-props]&amp;lt;/code&amp;gt; section, add:&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
*.ac = svn:mime-type=text/plain&lt;br /&gt;
*.eff = svn:mime-type=text/xml&lt;br /&gt;
*.frag = svn:mime-type=text/plain&lt;br /&gt;
*.nas = svn:mime-type=text/plain&lt;br /&gt;
*.osgx = svn:mime-type=text/xml&lt;br /&gt;
*.svg = svn:mime-type=text/svg+xml&lt;br /&gt;
*.txt = svn:mime-type=text/plain&lt;br /&gt;
*.vert = svn:mime-type=text/plain&lt;br /&gt;
*.xhtml = svn:mime-type=text/xml&lt;br /&gt;
*.xml = svn:mime-type=text/xml&lt;br /&gt;
*.xsl = svn:mime-type=text/xml&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These are all the text files that the hook script will check that the mime-type is set to a text format, though new text files will likely be added in the future.  These additions can either be to the user configuration file located at &amp;lt;code&amp;gt;~/.subversion/config&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;%USERPROFILE%\AppData\Roaming\Subversion\config&amp;lt;/code&amp;gt; in Windows) or, if a user configuration file is not set, to the global configuration file at &amp;lt;code&amp;gt;/etc/subversion/config&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;%APPDATA%\Subversion\config&amp;lt;/code&amp;gt; in Windows).&lt;br /&gt;
&lt;br /&gt;
==== Executable flag ====&lt;br /&gt;
&lt;br /&gt;
Another blocking message when attempting to commit files to FGAddon using the SVN tools is:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Adding         dash-set.xml&lt;br /&gt;
Transmitting file data .svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&lt;br /&gt;
The svn:executable property is set on the files ['dash-set.xml'], aborting the&lt;br /&gt;
commit.&lt;br /&gt;
&lt;br /&gt;
The current policy is that no executable files are allowed in FGAddon.  Before&lt;br /&gt;
committing, please remove this property by typing 'svn propdel svn:executable&lt;br /&gt;
file_name' for all affected files.  Or to remove it recursively from all files&lt;br /&gt;
to be committed, in your aircraft directory type 'svn propdel svn:executable&lt;br /&gt;
-R'.&lt;br /&gt;
&lt;br /&gt;
To avoid the svn:executable property being set by your subversion client, on&lt;br /&gt;
GNU/Linux and Mac OS X systems simply make sure that the file's execute bit is&lt;br /&gt;
not set before adding the file to be committed.&lt;br /&gt;
&lt;br /&gt;
svn: E165001: Your commit message was left in a temporary file:&lt;br /&gt;
svn: E165001:    '/flightgear/repo_testing/svn-commit.tmp'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will probably only be seen on Mac OS X and GNU/Linux systems.  This message is printed by a pre-commit repository hook script that checks if the Subversion &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property is set and, if so, the commit is blocked.  This is a security measure, as no aircraft files should be executable.  To remove the problem, follow the instructions in the message and, using the command line tools, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propdel svn:executable -R&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then commit again, using the commit message saved in the &amp;lt;code&amp;gt;svn-commit.tmp&amp;lt;/code&amp;gt; file.  The message file name will be reported in the commit failure message, but check its contents first:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
cat svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And the reperform the commit:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -F svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Binary diffs ===&lt;br /&gt;
&lt;br /&gt;
{{warning|The incorrect setting or absence of the mime-type property on a binary file will result in a binary diff.}}&lt;br /&gt;
&lt;br /&gt;
When looking at the output of &amp;lt;code&amp;gt;svn diff&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;git diff&amp;lt;/code&amp;gt; if you are using git-svn) as well as when reading messages from the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]], you may see a large number of unrecognisable characters.  This is the result of what is known as a binary diff, showing the binary file differences as if it were text.  Although this is not a issue for the operation of the repository, the situation is an aesthetic problem which makes it more difficult to perform a review of the changes.&lt;br /&gt;
&lt;br /&gt;
To fix the problem, firstly the binary files with the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property missing need to be identified.  The following subversion command can be used:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propget svn:mime-type &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As it can be tedious checking each file individually, the following Python script simplifies and automates the process to identify all binary files with a mime-type issue:&lt;br /&gt;
&lt;br /&gt;
{{collapsible script&lt;br /&gt;
| type   = Python 2/3 script&lt;br /&gt;
| title  = Find binary files with no &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property set.&lt;br /&gt;
| intro  = The following script is based on blacklisting text files.  Hence false positives are to be expected, and the blacklists can be expanded as needed.&lt;br /&gt;
| lang   = python&lt;br /&gt;
| script =&lt;br /&gt;
#! /usr/bin/env python&lt;br /&gt;
&lt;br /&gt;
from os import getcwd, walk&lt;br /&gt;
from os.path import join, splitext&lt;br /&gt;
from re import search&lt;br /&gt;
from subprocess import PIPE, Popen&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
skip_txt_file_seg = [&lt;br /&gt;
    'authors',&lt;br /&gt;
    'copying',&lt;br /&gt;
    'licen',&lt;br /&gt;
    'readme'&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
skip_txt_ext = [&lt;br /&gt;
    'ac',&lt;br /&gt;
    'css',&lt;br /&gt;
    'dat',&lt;br /&gt;
    'eff',&lt;br /&gt;
    'frag',&lt;br /&gt;
    'html',&lt;br /&gt;
    'json',&lt;br /&gt;
    'log',&lt;br /&gt;
    'nas',&lt;br /&gt;
    'osgx',&lt;br /&gt;
    'svg',&lt;br /&gt;
    'tex',&lt;br /&gt;
    'txt',&lt;br /&gt;
    'vert',&lt;br /&gt;
    'xhtml',&lt;br /&gt;
    'xml',&lt;br /&gt;
    'xsl'&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
skip_bin_prop = [&lt;br /&gt;
    'application/octet-stream',&lt;br /&gt;
    'application/pdf',&lt;br /&gt;
    'application/postscript',&lt;br /&gt;
    'application/x-dosexec',&lt;br /&gt;
    'application/x-gzip',&lt;br /&gt;
    'application/zip',&lt;br /&gt;
    'audio/x-wav',&lt;br /&gt;
    'image/gif',&lt;br /&gt;
    'image/jpeg',&lt;br /&gt;
    'image/png',&lt;br /&gt;
    'image/vnd.adobe.photoshop',&lt;br /&gt;
    'image/tiff',&lt;br /&gt;
    'image/x-ms-bmp',&lt;br /&gt;
    'image/x-xcf',&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
# Walk through the directories.&lt;br /&gt;
for root, dirs, files in walk(getcwd()):&lt;br /&gt;
    # Loop over the files in the current directory.&lt;br /&gt;
    for file in files:&lt;br /&gt;
        # Skip known text files.&lt;br /&gt;
        skip = False&lt;br /&gt;
        for i in range(len(skip_txt_file_seg)):&lt;br /&gt;
            if search(skip_txt_file_seg[i], file.lower()):&lt;br /&gt;
                skip = True&lt;br /&gt;
        if skip:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # The file extension.&lt;br /&gt;
        file_path, ext = splitext(file)&lt;br /&gt;
        ext = ext[1:].lower()&lt;br /&gt;
&lt;br /&gt;
        # Skip known text file extensions.&lt;br /&gt;
        if ext in skip_txt_ext:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # The full file path.&lt;br /&gt;
        path = join(root, file)&lt;br /&gt;
&lt;br /&gt;
        # Query the file for svn:mime-type.&lt;br /&gt;
        cmd = 'svn propget svn:mime-type \&amp;quot;%s\&amp;quot;' % path&lt;br /&gt;
        pipe = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=PIPE, close_fds=False)&lt;br /&gt;
        props = []&lt;br /&gt;
        for line in pipe.stdout.readlines():&lt;br /&gt;
            props.append(line.strip())&lt;br /&gt;
&lt;br /&gt;
        # Byte array conversion (Python3).&lt;br /&gt;
        for i in range(len(props)):&lt;br /&gt;
            if hasattr(props[i], 'decode'):&lt;br /&gt;
                props[i] = props[i].decode()&lt;br /&gt;
&lt;br /&gt;
        # Skip binary svn:mime-type values.&lt;br /&gt;
        if len(props) and props[0] in skip_bin_prop:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # Printout.&lt;br /&gt;
        if not len(props):&lt;br /&gt;
            print(&amp;quot;%s&amp;quot; % path)&lt;br /&gt;
        else:&lt;br /&gt;
            print(&amp;quot;%s    svn:mime-type=%s&amp;quot; % (path, props[0]))&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==== Fixing the problem ====&lt;br /&gt;
&lt;br /&gt;
As [[#Subversion_properties|git-svn cannot set or change]] the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property, a [[#Repository_checkout|svn checkout copy]] of the aircraft is required.  The property can then be set to the default Subversion binary mime-type with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, the following set of shell commands can be used to automate the process:&lt;br /&gt;
{{collapsible script&lt;br /&gt;
| type   = Shell commands&lt;br /&gt;
| title  = Set specific &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; values on a set of known binary files.&lt;br /&gt;
| intro = These shell commands will work on GNU/Linux or Mac OS X systems (or on Windows if using cygwin, or if a find command line tool is installed).  The list of file types here are those most commonly found in FGAddon.  To set the property on a list of binary files, type (or copy and paste):&lt;br /&gt;
| lang   = bash&lt;br /&gt;
| script =&lt;br /&gt;
find -iname &amp;quot;*.wav&amp;quot; -exec svn propset svn:mime-type &amp;quot;audio/x-wav&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.bmp*&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/x-ms-bmp&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.gif&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/gif&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.jpg&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/jpeg&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.png*&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/png&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.psd&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/vnd.adobe.photoshop&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.tif&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/tiff&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.xcf&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/x-xcf&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.rgb*&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.au&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.*af&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.3ds&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.blend*&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.dds&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.od[gst]&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.onetoc2&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.xlsx&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.pdf&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/pdf&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.ps&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/postscript&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.gz&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/x-gzip&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.mdl&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/x-dosexec&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.zip&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/zip&amp;quot; {} \;&lt;br /&gt;
| conc = Other binary files can safely be set to &amp;lt;code&amp;gt;&amp;quot;application/octet-stream&amp;quot;&amp;lt;/code&amp;gt;, the Subversion default for binary files.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== SourceForge developer services ==&lt;br /&gt;
&lt;br /&gt;
The FlightGear project is hosted on the SourceForge open source infrastructure.  This developer services section will highlight some of the useful tools you can take advantage of.  SourceForge consists of two categories of services:&lt;br /&gt;
; Project infrastructure : The FlightGear project uses the project services of SourceForge.  These services are for standalone software projects.&lt;br /&gt;
; Developer infrastructure : These are services available to anyone with a SourceForge account, and are available via your SourceForge homepage and accessible to all.  This includes being able to create multiple version control repositories (svn, git, hg), wikis, forums, development teams, blogs, and ticket trackers (for bugs, support requests, tasks, etc.).&lt;br /&gt;
&lt;br /&gt;
Rather than creating a new project, any development for the FlightGear project should be based on the developer infrastructure.&lt;br /&gt;
&lt;br /&gt;
=== Developer git repository ===&lt;br /&gt;
&lt;br /&gt;
To set up your own remote git repository, here for developing the FGAddon fkdr1 aircraft:&lt;br /&gt;
* On your profile page at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/profile/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;, go to &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Add New&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Git&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set label to &amp;lt;code&amp;gt;fkdr1 FGAddon git-svn repository&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set the code path to &amp;lt;code&amp;gt;code-fkdr1&amp;lt;/code&amp;gt;.  The &amp;lt;code&amp;gt;code-*&amp;lt;/code&amp;gt; prefix is to differentiate this from the &amp;lt;code&amp;gt;forum-*&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;wiki-*&amp;lt;/code&amp;gt;, and other directories.&lt;br /&gt;
&lt;br /&gt;
The repository will be located at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/code-fkdr1/ci/master/tree/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Development teams ===&lt;br /&gt;
&lt;br /&gt;
If you and a group of friends would like to privately develop one of the FGAddon aircraft as a team, assuming that the you have contacted the original aircraft authors and the aircraft is not actively being developed, then you should create a SourceForge development team.  A team leader should be appointed to set this up under their SourceForge account.  Assuming you wish to develop the &amp;quot;ornithopter&amp;quot; aircraft, the steps are:&lt;br /&gt;
&lt;br /&gt;
* Go to &amp;lt;code&amp;gt;Personal tools&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;User Permissions&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Add a new group&amp;lt;/code&amp;gt; at the bottom.&lt;br /&gt;
* Set the name to &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt;, and save.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Add&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; group and add the SourceForge names of all your team members.&lt;br /&gt;
&lt;br /&gt;
After setting up a private repository in the team leader's account, as described below, then the development team should be set up for the repository.&lt;br /&gt;
&lt;br /&gt;
* Go to the repository under your SourceForge account.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Admin - &amp;lt;repository name&amp;gt;&amp;lt;/code&amp;gt;, then select &amp;lt;code&amp;gt;Permissions&amp;lt;/code&amp;gt;.&lt;br /&gt;
* In the &amp;lt;code&amp;gt;Write&amp;lt;/code&amp;gt; section, remove &amp;lt;code&amp;gt;Developer&amp;lt;/code&amp;gt; and add &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Save&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The development team will then have commit access to the private repository.&lt;br /&gt;
&lt;br /&gt;
=== Team communications ===&lt;br /&gt;
&lt;br /&gt;
To help with team development, the SourceForge infrastructure allows for multiple [https://sourceforge.net/p/forge/documentation/Discussion/ dedicated discussion forums] to be created.  This can either be within a SourceForge project or under a SourceForge users homepage.  This allows the team leader to create a forum dedicated solely to the development of the aircraft of interest.  Continuing with the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; example, the steps for the team leader are simple:&lt;br /&gt;
&lt;br /&gt;
* On your profile page at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/profile/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;, go to &amp;lt;code&amp;gt;Personal tools&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on the &amp;lt;code&amp;gt;Tools&amp;lt;/code&amp;gt; option in the left hand menu.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Discussion&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;Click to install&amp;lt;/code&amp;gt; section.&lt;br /&gt;
* Change the label to &amp;lt;code&amp;gt;Ornithopter forum&amp;lt;/code&amp;gt;, and the path to &amp;lt;code&amp;gt;forum-ornithopter&amp;lt;/code&amp;gt;, for example.  The &amp;lt;code&amp;gt;forum-*&amp;lt;/code&amp;gt; prefix is to differentiate this from the &amp;lt;code&amp;gt;code-*&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;wiki-*&amp;lt;/code&amp;gt;, and other directories.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Save&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
More details are given on the [https://sourceforge.net/p/forge/documentation/Discussion/ SourceForge Discussion documentation].&lt;br /&gt;
&lt;br /&gt;
== Development scenarios ==&lt;br /&gt;
&lt;br /&gt;
=== Individual developer ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer and will use the native Subversion tools.}}&lt;br /&gt;
&lt;br /&gt;
This is by far the simplest development scenario and should be used in most cases.  If you are using the command line Subversion client, you can checkout an individual aircraft with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| path     = Aircraft/wrightFlyer1903&lt;br /&gt;
| post     = &lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is your SourceForge user name.  Alternatively you can checkout all aircraft with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| post     = flightgear-fgaddon&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If you do not have commit access, type one of:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| path     = Aircraft/wrightFlyer1903&lt;br /&gt;
| post     = &lt;br /&gt;
}}&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| post     = flightgear-fgaddon&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
To use the new local svn repository, see the [[#Subversion|subversion instructions]].&lt;br /&gt;
&lt;br /&gt;
=== Individual developer (git-svn) ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer and will use the git-svn tools.}}&lt;br /&gt;
&lt;br /&gt;
This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum.  To clone the aircraft of choice into a new git repository, type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is your infrastructure user name and &amp;lt;code&amp;gt;&amp;lt;aircraft&amp;gt;&amp;lt;/code&amp;gt; is the directory name in the FGAddon repository. This is valid whether or not you have commit permissions.&lt;br /&gt;
&lt;br /&gt;
To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].&lt;br /&gt;
&lt;br /&gt;
==== Upload to Sourceforge ====&lt;br /&gt;
&lt;br /&gt;
To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure.  For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile.  Then add this as a remote:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username&amp;gt;|type=git|repo=code-&amp;lt;aircraft&amp;gt;}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
And send the master branch where developments are located with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git push --set-upstream origin master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The changes in the new repository will be visible via the web interface at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=&amp;lt;username&amp;gt;|repo=code-&amp;lt;aircraft&amp;gt;|branch=master}}}}}}| style=&amp;quot;color: blue&amp;quot;}}.&lt;br /&gt;
&lt;br /&gt;
=== Sending external git repository changes into FGAddon ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer with FGAddon commit access and wish to transfer the commits in a remote git repository into FGAddon using a temporary local git repository.}}&lt;br /&gt;
&lt;br /&gt;
Firstly clone the FGAddon aircraft into a local git-svn repository with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This will create a new local git repository linked to FGAddon via git-svn.  If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]].  Next, set up the remote git repository as a remote, and fetch it:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git remote add &amp;lt;name&amp;gt; &amp;lt;url&amp;gt;&lt;br /&gt;
git fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;url&amp;gt;&amp;lt;/code&amp;gt; is the URL of the remote git repository.  Finally make an ordered list of all hashes of the commits to be sent into FGAddon, from earliest to latest, and cherry-pick them into the git-svn master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the git-svn local repository should only have a single &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch and only consist of cherry-picking.  To see the changes queued for sending to FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then to send the changes to FGAddon, firstly pull in any remote changes, and send the commits:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The temporary local repository can then be deleted.&lt;br /&gt;
&lt;br /&gt;
=== Connecting an existing git repository to FGAddon ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer or team leader with FGAddon commit access and wish to connect a pre-existing remote git repository with FGAddon to send all changes back to FGAddon.}}&lt;br /&gt;
&lt;br /&gt;
If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools.  The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]].  Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;aircraft&amp;gt;&amp;lt;/code&amp;gt; is the aircraft directory name in FGAddon.  Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology).  However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels.&lt;br /&gt;
&lt;br /&gt;
Now fetch the current state from the remote FGAddon repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The downloaded SVN history is in the remote branch &amp;lt;code&amp;gt;remotes/git-svn&amp;lt;/code&amp;gt;.  To commit changes to SVN you need a local branch that tracks this remote branch.  Create a local &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch that you will use to commit updates:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git branch fgaddon remotes/git-svn&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After committing new stuff to the &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch, to push to FGAddon checkout the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch and update it from SVN in case someone else has touched the aircraft in the remote FGAddon repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cherry-pick the new commits from &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; to preserve a linear history:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the changes queued for sending to FGAddon as either commits or a diff, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If everything looks ok, dcommit the local commits on the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch to send them to the remote FGAddon SVN repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Switch back to the master branch for local development:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To get changes from upstream you can either just download them with&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or download them and rebase your &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch onto them:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Team development ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  All members of the team are acting as gatekeepers, and all commits are made directly to FGAddon, either using svn or git-svn.}}&lt;br /&gt;
&lt;br /&gt;
The simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon.  Communication and coordination between the team members can be performed using a [[#Team_communications|team leader organised SourceForge forum]] or using the [http://forum.flightgear.org/ FlightGear forum].  In this scenario, the team needs to take the initiative and everyone apply for FGAddon commit access.&lt;br /&gt;
&lt;br /&gt;
=== Private team development (git-svn) ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  One team leader is acting as the gatekeeper on a private git repository hosted on the in-house SourceForge infrastructure, using git-svn to push a fgaddon branch to FGAddon, with team members committing directly to the private git repository or making merge requests from their fork of the private repository.}}&lt;br /&gt;
&lt;br /&gt;
To keep everything in-house, the entire operation will be based on the official infrastructure and remote repositories under each user's SourceForge (SF) profile.  Note to the team leader - you must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn keep your git-svn history linear] (meaning that a [[#Dedicated_FGAddon_branch|dedicated FGAddon branch]] should be created and changes manually cherry-picked into this branch).  In the following, the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; aircraft will be used as an example.&lt;br /&gt;
&lt;br /&gt;
==== The team ====&lt;br /&gt;
&lt;br /&gt;
Firstly, the entire team should sign up for [[#SourceForge account|SourceForge accounts]].&lt;br /&gt;
&lt;br /&gt;
==== Team leader ====&lt;br /&gt;
&lt;br /&gt;
===== Private repository set up =====&lt;br /&gt;
&lt;br /&gt;
These steps are to be taken by the team leader.  In your SourceForge user profile, set up a [[#Developer_git_repository| git repository]] with the label &amp;lt;code&amp;gt;Ornithopter FGAddon git-svn repository&amp;lt;/code&amp;gt; and code path &amp;lt;code&amp;gt;code-ornithopter&amp;lt;/code&amp;gt;.  Then create a empty local git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ mkdir ornithopter&lt;br /&gt;
$ cd ornithopter&lt;br /&gt;
$ git init&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Link the empty repository to the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; aircraft directory in the remote FGAddon repository and pull it in with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/ornithopter|full=1}}&lt;br /&gt;
$ git svn fetch&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; with your SF user name.  Set up a special git-svn branch for FGAddon gatekeeping and dcommitting changes back to the repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch fgaddon remotes/git-svn&lt;br /&gt;
$ git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And pull in the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; from FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current local git-svn repository setup, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch -vva&lt;br /&gt;
$ git remote -v&lt;br /&gt;
$ git svn info &lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then return to the master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, set up the remote git repository as a remote:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username&amp;gt;|type=git|repo=code-ornithopter}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
And send the master branch to the remote git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git push -u origin master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the new set up:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch -vva&lt;br /&gt;
$ git remote -v&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The repository will be located at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=&amp;lt;username&amp;gt;|repo=code-ornithopter|branch=master}}}}}}| style=&amp;quot;color: blue&amp;quot;}}.  Note that the git-svn information stored in the &amp;lt;code&amp;gt;.git/svn&amp;lt;/code&amp;gt; directory will not be pushed to remote SoureForge repository, and therefore the link back to FGAddon will only be present in the local copy of the team leader.  The git-svn link can be re-established at a later point if necessary.&lt;br /&gt;
&lt;br /&gt;
===== Team setup =====&lt;br /&gt;
&lt;br /&gt;
Set up a [[#Development teams|dedicated development team and grant them access to the git-svn repository]].&lt;br /&gt;
&lt;br /&gt;
===== Pushing to FGAddon =====&lt;br /&gt;
&lt;br /&gt;
Committing to FGAddon is for the local git repository of the team leader.  History must be linear in the fgaddon branch, so cherry-picking is the way to go.  This is from the [[#Individual developer (git-svn)|Individual developer (git-svn)]] section.  In the local git repository, switch to the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pull in any changes which have occurred in FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the commits in the &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch which are not in the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch, type one of:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log HEAD..master&lt;br /&gt;
git log HEAD..master --pretty=oneline&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manually select the commits to be sent to FGAddon and cherry-pick them:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Or to cherry-pick a range of commits:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;^..&amp;lt;commit hash 8&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then check what is to be sent:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Send the changes to FGAddon, send the git &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch changes to the remote git repository, and switch back to the master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
git push&lt;br /&gt;
git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally merge in the git svn commits with their new hashes from the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch, and send it to the remote git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git merge fgaddon&lt;br /&gt;
git push&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Team members ====&lt;br /&gt;
&lt;br /&gt;
===== Working with the repository =====&lt;br /&gt;
&lt;br /&gt;
Each team member should make a clone of the private git repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{sourceforge source|cmd=git clone|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username_leader&amp;gt;|type=git|repo=code-ornithopter|post=ornithopter|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; with your SourceForge user name, and &amp;lt;code&amp;gt;&amp;lt;username_leader&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name of the team leader.&lt;br /&gt;
&lt;br /&gt;
===== Forking and merge requests =====&lt;br /&gt;
&lt;br /&gt;
Alternatively, each team member can fork the git repository under your SourceForge account:&lt;br /&gt;
* Go to {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge source|user=&amp;lt;username&amp;gt;|repo=code-ornithopter|branch=master|full=1}}}}}}| style=&amp;quot;color: blue&amp;quot;}}, where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name of the team leader.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Fork&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set the mount point to &amp;lt;code&amp;gt;code-ornithopter&amp;lt;/code&amp;gt; and change the label as you wish.&lt;br /&gt;
&lt;br /&gt;
Develop and push to your fork, then make merge requests by clicking on the &amp;lt;code&amp;gt;Request Merge&amp;lt;/code&amp;gt; button.&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear]]&lt;br /&gt;
&lt;br /&gt;
[[de:FGAddon]]&lt;br /&gt;
[[en:FGAddon]]&lt;br /&gt;
[[fr:FGAddon]]&lt;br /&gt;
[[nl:FGAddon]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Template:Warning&amp;diff=117672</id>
		<title>Template:Warning</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Template:Warning&amp;diff=117672"/>
		<updated>2019-03-23T23:17:51Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;border: 1px solid #f42; border-left-width: 10px; margin: 1em auto; width: {{{width|90%}}}; background-color: #ffe0d0; padding: 2px;&amp;quot;&lt;br /&gt;
| style=&amp;quot;padding-left:5px;&amp;quot;| '''&amp;lt;span class=&amp;quot;smallcaps&amp;quot; style=&amp;quot;font-variant:small-caps;&amp;quot;&amp;gt;{{LangSwitch&lt;br /&gt;
 | ca = Advertència&lt;br /&gt;
 | de = Warnung&lt;br /&gt;
 | en = Warning&lt;br /&gt;
 | es = Advertencia&lt;br /&gt;
 | fr = Avertissement&lt;br /&gt;
 | it = Avviso&lt;br /&gt;
 | nl = Waarschuwing&lt;br /&gt;
 | ru = Предупреждение&lt;br /&gt;
 | th = '''เดี๋ยวก่อน!'''&lt;br /&gt;
}}&amp;lt;/span&amp;gt;'''&amp;amp;ensp; {{{1|Add message}}}&lt;br /&gt;
|}&amp;lt;noinclude&amp;gt;{{Informative template |1=&lt;br /&gt;
__NOTOC__&lt;br /&gt;
== Goal ==&lt;br /&gt;
Use this template to add a warning when a virtual aircraft might crash or when real equipment or ones health might be jeopardized.&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
 {{obr}}'''warning'''{{!}}message{{!}}''width=''{{cbr}}&lt;br /&gt;
&lt;br /&gt;
; width : Width of the messagebox, preferably as a percentage of the width of the page content. Defaults to 90%.&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{warning|Dumping the fuel enroute may leave you unable to reach any airport.}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
{{warning|Dumping the fuel enroute may leave you unable to reach any airport.}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{warning|Dumping the fuel enroute may leave you unable to reach any airport.|width=30%}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
{{warning|Dumping the fuel enroute may leave you unable to reach any airport.|width=30%}}&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
Adding external links must be done like below. Specifically note the '''1{{=}}'''.&lt;br /&gt;
 {{obr}}'''warning'''{{!}}'''1='''message{{cbr}}&lt;br /&gt;
&lt;br /&gt;
== Related templates ==&lt;br /&gt;
=== Messagebox templates ===&lt;br /&gt;
* {{tl|caution}} &amp;amp;ndash; When there might be damages to the virtual aircraft or to real equipment&lt;br /&gt;
* {{tl|note}} &amp;amp;ndash; For important notes&lt;br /&gt;
* {{tl|tip}} &amp;amp;ndash; For helpful tips&lt;br /&gt;
&lt;br /&gt;
=== Inline italic templates ===&lt;br /&gt;
{{inote|If there is a need for a warning use a messagebox template instead.}}&lt;br /&gt;
* {{tl|icaution}}&lt;br /&gt;
* {{tl|inote}}&lt;br /&gt;
* {{tl|itip}}&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Messagebox templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/FGAddon&amp;diff=117671</id>
		<title>Ca/FGAddon</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/FGAddon&amp;diff=117671"/>
		<updated>2019-03-23T23:13:56Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
[[File:FGAddon logo.png|270px|right]]&lt;br /&gt;
&lt;br /&gt;
L'hangar oficial d'aeronaus '''FGAddon''' és un repositori de control de versions, allotjat a l'[https://sourceforge.net/projects/flightgear/ infraestructura SourceForge] de [[:ca:FlightGear|FlightGear]], i usat per al desenvolupament diari de les aeronaus del simulador.  FGAddon és un repositori de control de versions de {{wikipedia|Subversion|noicon=1|lang=ca}}. Aquestes aeronaus no formen part del paquet base (les aeronaus que s'inclouen al paquet base) — el [[Ca/Cessna 172P|Cessna 172P]] i l'[[UFO]] — es mantenen al repositori de [http://sourceforge.net/p/flightgear/fgdata FGData]), però apareixen amb cada versió estable a les [http://www.flightgear.org/download/ pàgines de descàrrega de FlightGear].&lt;br /&gt;
&lt;br /&gt;
El repositori de desenvolupament d'aeronaus FGAddon s’ha de considerar inestable.  Quan utilitzeu una versió estable de FlightGear, el millor és obtenir avions amb un número de versió coincident del programa base actual que apareix a les [http://www.flightgear.org/download/ pàgines de descàrrega de FlightGear].  Tanmateix, com les versions estables de FlightGear 3.4 en endavant estan etiquetats i presents al repositori de FGAddon, les eines de Subversion poden ser una manera convenient d’obtenir aeronaus individuals o tot l’hangar oficial d’aproximadament 500 avions.  També, si utilitzeu les [[FlightGear build server|últimes versions]] o una [[Building FlightGear|versió autocompilada de FlightGear]] dels [http://sourceforge.net/p/flightgear/_list/git repositoris de control de versions de Git] de FlightGear, utilitzant el FGAddon permet actualitzar l’avió a les últimes versions de desenvolupament.&lt;br /&gt;
&lt;br /&gt;
== Història ==&lt;br /&gt;
[[File:Image103.gif|thumb|Icona original de Win95]]&lt;br /&gt;
El projecte FlightGear va ser concebut el 8 d'abril de 1996 per David Murr, que va proposar un nou simulador de vol per ser desenvolupat per voluntaris&amp;lt;ref&amp;gt;David Murr (Apr 9, 1996).  FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J &amp;quot;A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@&amp;quot;].  Published on the rec.aviation.simulators newsgroup.&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (1996).  FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR &amp;quot;This truly is as real as it gets!&amp;quot; - a proposal for a new flight simulator - REVISION 2.0].&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (Oct 29, 1996).  FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, &amp;quot;The future of flight simulation is here&amp;quot;].  Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (Sep 11, 1998).  FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, &amp;quot;The future of flight simulation is here&amp;quot;].&amp;lt;/ref&amp;gt;.  Part dels objectius inicials van ser desenvolupar rutines gràfiques 2D i 3D per al simulador. No obstant això, aquesta va ser una tasca enorme que va acabar sense finalitzar a principis de 1997, ja que el desenvolupador principal, Eric Korpela, estava acabant la seva tesi. Per tant, a partir del 16 de maig de 1997, Curtis Olson va rellançar el desenvolupament amb un nou projecte basat en les biblioteques d'OpenGL, que permetria crear un simulador de vol funcional en un curt període de temps.&amp;lt;ref&amp;gt;Curtis Olson (Sep 28, 2015).  [http://forum.flightgear.org/viewtopic.php?f=42&amp;amp;t=27558&amp;amp;p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@].  Published on the FlightGear forum.&amp;lt;/ref&amp;gt;  Les primeres contribucions van ser de [[FlightGear CVS|repositoris de control de versions CVS de flightgear i simgear]] originals.&lt;br /&gt;
&lt;br /&gt;
A mesura que el projecte va créixer, també ho va fer la mida, la quantitat i la qualitat dels actius de FlightGear. Aquests actius no estaven organitzats i estaven dispersos per diferents parts d'Internet. Per tant, es va decidir que gran part d’aquest contingut de FlightGear es reuniria i s’emmagatzemaria de manera conjunta en un nou repositori CVS centralitzat anomenat fgdata, que es va crear el 22 d’octubre de 2000. Per permetre la redistribució legal d’aquests actius com a part de la distribució de FlightGear, s’adoptava una política de GPLv2.&lt;br /&gt;
&lt;br /&gt;
Al maig del 2010, el desenvolupament va ser interromput malauradament per ''&amp;quot;l'incident del cafè&amp;quot;'' que va resultar en la pèrdua del servidor domèstic de Curtis que allotjava tots els repositoris de FlightGear&amp;lt;ref&amp;gt;James Turner (May 20, 2010). [http://thread.gmane.org/gmane.games.flightgear.devel/60340/focus=60341 &amp;lt;nowiki&amp;gt;[Flightgear-devel]&amp;lt;/nowiki&amp;gt; Re: Flightgear git repositories (was Re: GIT or CVS - Confusion)] Published on the flightgear-devel mailing list.&amp;lt;/ref&amp;gt;.  Aquests esdeveniments van resultar en un [[FlightGear CVS|migració massiva de tots els repositoris CVS als repositoris de Git]].  A causa de problemes d’amplada de banda, es va decidir que els nous repositoris s’alternessin a la infraestructura de codi obert Gitorious.&lt;br /&gt;
&lt;br /&gt;
Amb el temps que el projecte va créixer, la mida i l'abast del repositori de fgdata es va multiplicar, principalment a causa del creixent nombre d’avions emmagatzemats a [[$FG_ROOT]]/Aircraft, de manera que una divisió era inevitable. Gijs de Rooy va organitzar un primer intent de separació i es va anunciar el 18 d’octubre de 2011&amp;lt;ref&amp;gt;Cedric Sodhi (Oct 18, 2011) [http://thread.gmane.org/gmane.games.flightgear.devel/66846 &amp;lt;nowiki&amp;gt;[Flightgear-devel]&amp;lt;/nowiki&amp;gt; FGData Split Completed - a.k.a Life after the Split] Published on the flightgear-devel mailing list.&amp;lt;/ref&amp;gt;.  Cada avió es va col·locar en el seu propi repositori de Git i tots els avions vinculats de nou a fgdata mitjançant un enfocament del submodul Git. No obstant això, aquest intent va fallar i va ser abandonat. A partir d'aquesta data fins a finals de 2014, el disseny de la divisió fgdata es va discutir a la llista de correu de desenvolupament i es va resumir a l'article wiki de [[FlightGear Git: splitting fgdata|FlightGear Git: dividint fgdata]].  En les etapes de planificació, els repositoris es coneixien com a fgdata-old dividint-se en [[FGData]] (també conegut com a fgdata-new) i FGAddon (també conegut com a flightgear-aircraft i fgaircraft).  Després de mitja dècada de planificació, es va decidir que la millor solució per al desenvolupament d’avions de FlightGear seria un únic repositori de Subversion centralitzat. Això facilitaria la gestió i el manteniment comunitari de l’avió, alhora que proporciona modularitat i descàrregues més petites i mides de repositoris locals més petits.&lt;br /&gt;
&lt;br /&gt;
A finals de 2014, Gitorious, el proveïdor de la infraestructura de codi obert per al codi font de FlightGear i els repositoris de dades, va anunciar que tancaria els seus serveis fins al maig de 2015 a causa de la seva adquisició per GitLab. Això va motivar la divisió de fgdata-old i un canvi a l'infraestructura de codi obert SourceForge per allotjar els repositoris VC. Altres parts de la infraestructura de FlightGear ja estaven allotjades per SourceForge, fent que el moviment fos natural.  Segellant l’acord, SourceForge va acceptar per escrit allotjar l’enorme col·lecció d’avions de FlightGear, la mida de la qual no té rival en cercles de codi obert. Avui en dia, el repositori SVN de FGAddon, juntament amb la major part de la infraestructura del projecte FlightGear, està allotjat a SourceForge.&lt;br /&gt;
&lt;br /&gt;
A l'agost de 2015, es va escriure un nou document de política de FlightGear per codificar els estàndards no escrits del projecte&amp;lt;ref&amp;gt;[http://www.flightgear.org/flightgear-policy-document/ FlightGear Policy Document and Roadmap], draft document.&amp;lt;/ref&amp;gt;.  Amb aquest document, la política de llicències dels avions de FlightGear allotjada a FGAddon ha estat actualitzada ed GPLv2-only a GPLv2+. Per combatre la proliferació de llicències, cal evitar complicacions mitjançant el treball d’una aeronau a una altra, i per la integritat i el bon projecte del FlightGear, es recomana que tot el contingut original (allotjat a FGAddon o en qualsevol altre lloc) sigui llicenciat amb GPLv2+.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
{{FGCquote&lt;br /&gt;
|1= The short summary is that we already were maintaining a well established presence on sourceforge. So after quite a bit of discussion, we decided to consolidate there. In addition, we had a perpetual complaint that the fgdata git repository was far too big for most people to initially download (1Gb+). Thus we split off most of the aircraft (expecting unbounded future growth potential) into an svn repository called fgaddon. Sourceforge supports both git and svn repositories. This puts a dependency on a central svn server for our fgaddon aircraft repository, but lightens the weight for anyone wanting to checkout a copy of everything (you don't need a copy of the entire development history, and a copy of every version ever created of every aircraft if you just want to have the latest versions.) Plus svn allows checking out subtrees (without needing the whole repository) so this can also serve as a potential JIT single aircraft service provider. Of course there are always multiple ways to solve every problem and of course every engineering decision has trade offs. Github is a nice provider, no doubt. I have been using them for a number of my own personal repositories. Git of course has ways to address many of the issues we have addressed, but of course everything has strengths and weaknesses.&lt;br /&gt;
|2= {{cite web&lt;br /&gt;
  | url    = http://sourceforge.net/p/flightgear/mailman/message/35054405/&lt;br /&gt;
  | title  = &amp;lt;nowiki&amp;gt;Re: [Flightgear-devel] FlightGear and GitHub&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  | author = &amp;lt;nowiki&amp;gt;Curtis Olson&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  | date   = Apr 30th, 2016&lt;br /&gt;
  | added   = Apr 30th, 2016&lt;br /&gt;
  | script_version = 0.25&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Obtenint aeronaus ==&lt;br /&gt;
&lt;br /&gt;
{{tip|Si esteu interessats a obtenir aeronaus per a llançaments de FlightGear estables i no teniu coneixement del control de versions, heu de visitar el [[Ca/Hangars de FlightGear|Hangars de FlightGear]] per descarregar-les.}}&lt;br /&gt;
{{caution|Si les versions de les aeronaus de FlightGear i FGAddon no coincideixen, poden aparèixer errors i el suport en versions no compatibles no serà efectuat per la comunitat de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
With access to the Subversion (SVN) tools, the FGAddon version control repository can be a convenient way for obtaining aircraft for using within a specific FlightGear version directly from the official source.  When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match.  The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user.&lt;br /&gt;
&lt;br /&gt;
=== Preparació ===&lt;br /&gt;
To use the FGAddon repository, the Subversion tools need to be installed:&lt;br /&gt;
* '''MS Windows''': Install one of the [https://subversion.apache.org/packages.html#windows many Subversion clients].  For example [https://sliksvn.com/download/ SlikSVN] is one of the best command line versions and the best for aircraft development, and [http://tortoisesvn.net/ TortoiseSVN] provides a user friendly graphical user interface (GUI) by integrating into Windows Explorer.&lt;br /&gt;
* '''Mac OS X''': Install the [https://subversion.apache.org/packages.html#osx official Subversion client].&lt;br /&gt;
* '''GNU/Linux''': Install the Subversion client via the package manager.  This will usually be in a package called &amp;lt;code&amp;gt;subversion-*.{rpm,deb}&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Directori de FGAddon ===&lt;br /&gt;
To know how to use the FGAddon repository, an understanding of the repository directory layout is essential.&lt;br /&gt;
* &amp;lt;code&amp;gt;/trunk&amp;lt;/code&amp;gt;:  This base directory is where the in-development versions of the aircraft are located.&lt;br /&gt;
* &amp;lt;code&amp;gt;/branches/release-x.y.z/&amp;lt;/code&amp;gt;:  These directories correspond to the specific stable FlightGear releases.&lt;br /&gt;
&lt;br /&gt;
The [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ web interface for the FGAddon repository] allows all of the aircraft to be browsed.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega ===&lt;br /&gt;
[[File:V22Osprey.jpg|thumb|200px|Aircraft to be downloaded]]&lt;br /&gt;
Firstly, choose an aircraft to download.  The [[Bell Boeing V-22 Osprey]] will be used in this example.&lt;br /&gt;
&lt;br /&gt;
==== Command line ====&lt;br /&gt;
&lt;br /&gt;
To download the aircraft for FlightGear 3.4, simply type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|branch=branches/release-3.4.0|path=Aircraft/V22-Osprey|post=}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
To obtain the in-development version, type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|path=Aircraft/V22-Osprey|post=}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If all of the ~500 aircraft from the repository are desired - beware that this will be a huge download of over 6 GB - use the following command:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|post=flightgear-fgaddon}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
When using a stable FlightGear release, for example FlightGear 2016.1, to obtain all of the FGAddon aircraft to match the installed FlightGear version, use:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|branch=branches/release-2016.1|post=flightgear-fgaddon}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==== GUI clients and TortoiseSVN ====&lt;br /&gt;
&lt;br /&gt;
When using one of the Subversion GUIs (graphical user interfaces), simply copy one of the above &amp;lt;code&amp;gt;https://&amp;lt;/code&amp;gt; URLs and use that in the GUI (each GUI is different, so see the relevant documentation for help).  For the unique TortoiseSVN tool, simply:&lt;br /&gt;
&lt;br /&gt;
* In Windows Explorer, create a new empty folder for the aircraft (or aircraft collection).&lt;br /&gt;
* In the new folder, right click and select &amp;lt;code&amp;gt;SVN Checkout...&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Copy and paste the URL, for example {{fgaddon source|path=Aircraft/V22-Osprey|type=svn|full=1}}, leave all other settings as they are, and import by clicking on &amp;lt;code&amp;gt;OK&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
For more details, see the [http://tortoisesvn.net/support.html TortoiseSVN documentation].  Note that there is an option to install the command line tools when installing TortoiseSVN.&lt;br /&gt;
&lt;br /&gt;
=== Flying ===&lt;br /&gt;
&lt;br /&gt;
To use the newly downloaded aircraft, please see the [[Howto:Install aircraft]] article, skipping the instructions for downloading and unzipping the aircraft.&lt;br /&gt;
&lt;br /&gt;
=== Updates ===&lt;br /&gt;
With a checked out copy of the &amp;lt;code&amp;gt;/trunk&amp;lt;/code&amp;gt; in-development version, the aircraft can be updated to the latest version using the command:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn up&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Aircraft development ==&lt;br /&gt;
&lt;br /&gt;
{{tip|The FlightGear community encourages aircraft development directly within FGAddon.}}&lt;br /&gt;
&lt;br /&gt;
=== Contact the original aircraft authors ===&lt;br /&gt;
&lt;br /&gt;
The first step for developing and advancing the aircraft of the official FlightGear hangar, or from one of the [[Flightgear_hangars#Aircraft_hangars|private hangars]] for that matter, is to make contact with the original aircraft author(s).  Their names can be found within the &amp;lt;code&amp;gt;*-set.xml&amp;lt;/code&amp;gt; file, within the &amp;lt;code&amp;gt;&amp;lt;authors&amp;gt;&amp;lt;/code&amp;gt; XML tag.  Often the contact email address will be listed in a README file or some other text file in the base aircraft directory.  If not, contact can sometimes be established via the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list].  Contacting the original authors is important to see if the aircraft is currently being actively developed, and if you can join in as part of the development team.&lt;br /&gt;
&lt;br /&gt;
=== SourceForge account ===&lt;br /&gt;
&lt;br /&gt;
To work on the official aircraft collection, a [https://sourceforge.net/user/registration/ SourceForge account] should first be set up.  This will allow to either directly commit to the FGAddon repository, if commit access has been been granted, or to work in as part of a SourceForge development team.  The registration process is lightning quick and the SourceForge developer infrastructure and developer services will be accessible in under a minute.&lt;br /&gt;
&lt;br /&gt;
=== Commit access ===&lt;br /&gt;
&lt;br /&gt;
Before obtaining commit access, an all-out effort to contact the original author(s) should be made to determine if the aircraft is actively being developed.  If this is unsuccessful, sign up for the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list] and ask for help there.  If the aircraft has a current maintainer, you will be directed as to how to proceed with development.  Otherwise ask if someone could volunteer to mentor you in the process of becoming an aircraft developer with full commit access.&lt;br /&gt;
&lt;br /&gt;
To obtain commit access, you will first need:&lt;br /&gt;
# To demonstrate your capabilities and development skills.&lt;br /&gt;
# To show that you understand the [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document]. &lt;br /&gt;
# To show an understanding of the GPL licensing issues, and that you can be trusted not to use copyrighted, non-GPL material.&lt;br /&gt;
# To earn the trust of the FlightGear community.&lt;br /&gt;
&lt;br /&gt;
These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.&lt;br /&gt;
&lt;br /&gt;
To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to proceed.  Depending on the [[#Development_scenarios|development scenario]], this maybe by merge request, file transfer, the primitive patch system, or any other convenient way.  Once you believe you have proven your capabilities and you are knowledgeable about GPL licensing issues, you should write a mail to the development mailing list asking if you can be granted commit access, providing your SourceForge username.&lt;br /&gt;
&lt;br /&gt;
=== FGAddon commitlog mailing list ===&lt;br /&gt;
&lt;br /&gt;
To follow all changes which occur in the FGAddon repository, subscribe to the dedicated [https://lists.sourceforge.net/lists/listinfo/flightgear-fgaddon-commitlogs Flightgear FGAddon commitlogs mailing list].  One email is sent per commit, as the commit is made.&lt;br /&gt;
&lt;br /&gt;
== Version control tools ==&lt;br /&gt;
&lt;br /&gt;
To access FGAddon and use it for aircraft development, the Subversion or SVN version control tools are needed.  Alternatively git-svn provides an interface for those who prefer the git version control tools.&lt;br /&gt;
&lt;br /&gt;
=== Subversion ===&lt;br /&gt;
&lt;br /&gt;
==== Set up ====&lt;br /&gt;
The FGAddon aircraft hangar is stored in a remote Subversion repository located on the SourceForge infrastructure, and therefore it is simplest to use the SVN tools for aircraft development and will cause the least problems.  See the [[#Preparation|Subversion installation section]] for setting up the tool chain.&lt;br /&gt;
&lt;br /&gt;
==== Repository checkout ====&lt;br /&gt;
The first step is to 'checkout' a copy of either the repository trunk or one of the aircraft in the trunk:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn co &amp;lt;url&amp;gt; &amp;lt;dir&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the relevant URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section.  This command will create a local subversion repository copy in the given &amp;lt;code&amp;gt;&amp;lt;dir&amp;gt;&amp;lt;/code&amp;gt; directory.  Note that this will only contain the part of the FGAddon repository specified in the URL.  This means that Subversion allows you to checkout either a single file all the way to the entire remote repository.&lt;br /&gt;
&lt;br /&gt;
==== Information and history ====&lt;br /&gt;
At any point to see information about the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn info&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the history of the checked out copy of the repository, type one of:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn log&lt;br /&gt;
svn log | less&lt;br /&gt;
svn log -v | less&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Daily usage ====&lt;br /&gt;
The main Subversion command you will be using is:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn add &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will register the file or directory &amp;lt;code&amp;gt;&amp;lt;path&amp;gt;&amp;lt;/code&amp;gt; within the local repository to allow it to later be 'committed' and sent to the remote repository.  To move or rename a file or directory, use:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn mv &amp;lt;path1&amp;gt; &amp;lt;path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This should be used rather than normal file moving/renaming so that the change is tracked in the local repository.  To remove a file from the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn rm &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current status of the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn st&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To update the local repository with changes in the remote repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn up&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Committing changes ====&lt;br /&gt;
All of the above operations only occur on the local repository copy - the remote FGAddon repository at SourceForge will know nothing of these changes.  To send all your changes to FGAddon, you need to commit the changes:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will open up an editor to allow you to write an informative commit log message.  When committing, it is best to make small modular commits so that each commit corresponds to a single purpose.  Note that you can only commit to FGAddon if you have [[#Commit access|commit access]].&lt;br /&gt;
&lt;br /&gt;
==== Branching ====&lt;br /&gt;
The concept of Subversion branching is currently only used in the FlightGear project for tagging the stable releases.  However if you are curious about branching, see the [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html Branching and Merging chapter of the Subversion manual], and the [https://www.orcaware.com/svn/wiki/Svnmerge.py svnmerge.py script] which can greatly simplify the process.&lt;br /&gt;
&lt;br /&gt;
=== Git-svn ===&lt;br /&gt;
&lt;br /&gt;
The git-svn tool is useful for those who are already familiar with using git repositories, or those who wish to have their own private aircraft development playground.  Git-svn provides a bridge between the remote FGAddon Subversion repository and a local git repository.  For those unfamiliar with git, the git-svn bridge together with the git repository is far more complicated to use than the native [[#Subversion|Subversion tools]].  For more information on using git, see [[Howto:Start using git]]. The following will assume that only a single aircraft will be stored in the local git repository.&lt;br /&gt;
&lt;br /&gt;
==== Set up ====&lt;br /&gt;
The git distributed version control system needs to first be [https://git-scm.com/downloads installed].&lt;br /&gt;
&lt;br /&gt;
==== Cloning a single aircraft ====&lt;br /&gt;
The first step is to 'clone' a copy of one of the aircraft in the remote Subversion trunk:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn clone &amp;lt;aircraft_url&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the relevant aircraft URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section.  The URL depends on your [[#Commit access|FGAddon commit access status]].  The clone command will create a local git repository containing solely the aircraft of interest, and initialise the git-svn bridge.&lt;br /&gt;
&lt;br /&gt;
==== Information and history ====&lt;br /&gt;
At any point to see information about the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn info&lt;br /&gt;
git branch -vva&lt;br /&gt;
git remote -v&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the history of the checked out copy of the repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Daily usage ====&lt;br /&gt;
The main git command you will be using is:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git add &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will register the file or directory &amp;lt;code&amp;gt;&amp;lt;path&amp;gt;&amp;lt;/code&amp;gt; within the local repository to allow it to later be 'committed' to the local git repository.  To move or rename a file or directory, use:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git mv &amp;lt;path1&amp;gt; &amp;lt;path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However note that git history is not as robust as svn history.  See the [[#Moving_or_renaming_files|git-svn file moving/renaming deficiency section]] for how to better perform this operation.  To remove a file from the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git rm &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current status of the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git status&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Committing changes ====&lt;br /&gt;
As git is a distributed version control system, changes are committed to the local git repository.&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git commit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will open up an editor to allow you to write an informative commit log message.  The commit is local and will not be sent to FGAddon.&lt;br /&gt;
&lt;br /&gt;
==== Dedicated FGAddon branch ====&lt;br /&gt;
In the examples above, only a single branch was assumed in the repository.  If interaction with a remote git repository or branching within the local git repository is desired, then a different strategy is required.  The reason being that the branch that synchronises with FGAddon must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn preserve a linear history].  This means only cherry-picking of the desired changes into that branch is allowed.&lt;br /&gt;
&lt;br /&gt;
In this example, two branches will be set up in the local git repository:&lt;br /&gt;
* &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt;:  This branch will be dedicated for FGAddon synchronisation and will preserve a linear history.&lt;br /&gt;
* &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt;:  A master branch for aircraft development, allowing for mergers and other non-linear history operations.&lt;br /&gt;
&lt;br /&gt;
Assuming a [[#Cloning_a_single_aircraft|newly cloned repository]], create the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git branch fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And switch to that branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FGAddon synchronisation can then be performed on this branch.  To pull in the developments from the master branch, use cherry-picking to apply a sequentially ordered list of commit hashes:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the list of commits to be sent to FGAddon prior to dcommitting, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And to see the changes as a single diff:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Synchronising ====&lt;br /&gt;
To send the changes to the remote FGAddon repository, firstly change to the dedicated &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure the local git-svn repository is up to date with all changes that have occurred in FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then push or dcommit the changes to FGAddon with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Deficiencies of git-svn ===&lt;br /&gt;
&lt;br /&gt;
{{warning|Performing a &amp;lt;code&amp;gt;git-svn clone&amp;lt;/code&amp;gt; of the &amp;lt;code&amp;gt;/trunk/&amp;lt;/code&amp;gt; or entire repository is not recommended, as the entire repository history will be downloaded, resulting in a huge local repository, as well as putting a large strain on the FlightGear open source infrastructure.}}&lt;br /&gt;
&lt;br /&gt;
It is important to understand that there are a number of operations in which git-svn is deficient.  In many cases, the svn tools should be used instead.&lt;br /&gt;
&lt;br /&gt;
==== Copying files between aircraft ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn does not maintain the file copying history normally present in a Subversion repository.}}&lt;br /&gt;
&lt;br /&gt;
The most important of these is the copying of content from other FGAddon aircraft.  In this case you will need FGAddon commit access and a local svn copy of the repository.  Firstly synchronise the repositories by dcommitting all changes back to FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the local svn repository, copy the file:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn cp Aircraft/&amp;lt;aircraft1&amp;gt;/&amp;lt;file_path1&amp;gt; Aircraft/&amp;lt;aircraft2&amp;gt;/&amp;lt;file_path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And commit the change:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Back in the local git-svn repository, pull in the new files:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the subversion tools avoids the FGAddon repository backend from significantly increasing in size, as [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html#svn.branchmerge.using.create svn copies are cheap].&lt;br /&gt;
&lt;br /&gt;
==== Moving or renaming files ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn does not always maintain the file moving or renaming history normally present in a Subversion repository.}}&lt;br /&gt;
&lt;br /&gt;
This problem stems from the fact that svn history is more robust than that of git.  The &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;git mv&amp;lt;/code&amp;gt; commands are not equivalent.  The subversion command stores the move history directly in the repository whereas git does not (git instead uses heuristic methods to try to detect history, after the commit).  The result of using git-svn is that often the move will not be detected and the FGAddon history will show one file or directory being deleted and another added.  This also causes the repository backend to increase in size, whereas &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; will not cause any significant size increase.  If you wish to have a better historical record in the FGAddon repository and be considerate to the repository backend, it is recommended that you temporarily switch to the subversion tools.  Firstly, synchronise the repositories:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the local svn repository, move or rename the file:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn mv Aircraft/&amp;lt;aircraft&amp;gt;/&amp;lt;file_path1&amp;gt; Aircraft/&amp;lt;aircraft&amp;gt;/&amp;lt;file_path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And commit the change:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Back in the local git-svn repository, pull in the changes with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Copying files within one aircraft ====&lt;br /&gt;
&lt;br /&gt;
Just as the &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; command stores the move information directly within the repository, so does &amp;lt;code&amp;gt;svn cp&amp;lt;/code&amp;gt; store the copy information.  Therefore if you would like to duplicate a text file and modify it, using the native Subversion tools instead of git-svn for this operation allows for the file history to be permanently preserved in the FGAddon repository.&lt;br /&gt;
&lt;br /&gt;
==== Subversion properties ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn currently only supports the &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property, all other properties are ignored and cannot be added, changed, or removed in a git-svn clone of the aircraft.}}&lt;br /&gt;
&lt;br /&gt;
Internally, Subversion identifies binary files using the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; repository property.  However as git-svn cannot set this property when using the &amp;lt;code&amp;gt;git add&amp;lt;/code&amp;gt; command, the result is that binary files will be treated as text.  Binary diffs will be seen when using &amp;lt;code&amp;gt;svn diff&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;git diff&amp;lt;/code&amp;gt;, and a binary diff will be shown in the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]] messages.  As this issue is not unique to git-svn, to work around this issue please see the [[#Binary diffs|binary diffs]] section.&lt;br /&gt;
&lt;br /&gt;
==== Protocols other than svn+ssh ====&lt;br /&gt;
&lt;br /&gt;
The command &amp;lt;code&amp;gt;git svn init&amp;lt;/code&amp;gt; replicates the entire history of an aircraft into a local repository.  As part of this process, it generates a git commit ID or hash for every Subversion revision. The problem is that the git commit ID depends on the protocol used to read from the Subversion repository (likely a git bug).   Hence:&lt;br /&gt;
&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
and&lt;br /&gt;
&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=https|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
will result in two different and incompatible git repositories, even though they contain the same data. The incompatibility is not immediately apparent but it will bite later. Suppose someone with read-only access to FGAddon uses the https method, then asks a FGAddon gatekeeper to commit their changes. The gatekeeper, naturally, uses svn+ssh, as this is the only protocol granting write permissions. When the gatekeeper tries to merge the contributor's https clone into their own svn+ssh clone, git will complain that the two repositories have no history in common, and flag every change as a conflict.&lt;br /&gt;
&lt;br /&gt;
Therefore, if you are planning to make any changes to an aircraft, be sure to use svn+ssh even if you do not yet have commit permissions on FGAddon. svn+ssh does not require write permissions, it only requires a SourceForge user ID.&lt;br /&gt;
&lt;br /&gt;
== FGAddon development concepts ==&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
To add a new aircraft to the FGAddon repository, the SVN tools are required.  If you encounter &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property problems when adding a new aircraft, see the [[#Mime-type problems|mime-type problems section]] for how to resolve the issue.  Or if you have a &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property problem, see the [[#Executable flag|executable flag problem section]].&lt;br /&gt;
&lt;br /&gt;
==== svn import ====&lt;br /&gt;
&lt;br /&gt;
{{warning|The &amp;lt;code&amp;gt;svn import&amp;lt;/code&amp;gt; command described herein will send all contents of the specified directory directly into FGAddon without warning and without a way to cancel the operation.  Therefore special care must be taken when specifying the directory to upload into FGAddon, as well as the target FGAddon directory.  See the [[#svn add|svn add]] section below for a safer way to add a new aircraft.}}&lt;br /&gt;
&lt;br /&gt;
The [http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import svn import] command is the easiest method to use and does not require a local copy of the repository to be checked out.  To start:&lt;br /&gt;
&lt;br /&gt;
# Create an empty local aircraft directory.&lt;br /&gt;
# Copy the aircraft files into this directory.&lt;br /&gt;
# Carefully check all files to make sure there are no hidden or temporary files that should not be uploaded to FGAddon.&lt;br /&gt;
&lt;br /&gt;
Assuming the Dead Simple Human Powered Airplane (DaSH PA or &amp;quot;DaSH&amp;quot;) aircraft as an example, located in the &amp;lt;code&amp;gt;DaSH/&amp;lt;/code&amp;gt; directory, on the command line run:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source&lt;br /&gt;
| cmd      = svn import DaSH/&lt;br /&gt;
| protocol = svn+ssh&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| type     = svn&lt;br /&gt;
| path     = Aircraft/DaSH/&lt;br /&gt;
| post     = -m \&lt;br /&gt;
| full     = 1&lt;br /&gt;
}}&lt;br /&gt;
    &amp;quot;Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=24495 .&amp;quot;&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name.  This will add all the files into FGAddon with commit log message with the summary line &amp;lt;code&amp;gt;Initial import of the DaSH human powered aircraft.&amp;lt;/code&amp;gt;, followed by a blank line, and then a detailed description pointing to the original location or discussion of the aircraft.  To see if the aircraft has been successfully added to the repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source&lt;br /&gt;
| cmd      = svn list&lt;br /&gt;
| protocol = svn+ssh&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| type     = svn&lt;br /&gt;
| path     = Aircraft/DaSH/&lt;br /&gt;
| full     = 1&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Or visit the {{fgaddon source|path=Aircraft|text=FGAddon web interface}}.  The aircraft can then be checked out as described in the [[#Development scenarios|Development scenarios section]].&lt;br /&gt;
&lt;br /&gt;
==== svn add ====&lt;br /&gt;
&lt;br /&gt;
If a local copy of the FGAddon trunk is present, then the &amp;lt;code&amp;gt;svn add&amp;lt;/code&amp;gt; command can be used instead.  This is far safer than the &amp;lt;code&amp;gt;svn import&amp;lt;/code&amp;gt; command, as the change can be double checked before committing.  In the &amp;lt;code&amp;gt;Aircraft/&amp;lt;/code&amp;gt; directory of the local repository, create the &amp;lt;code&amp;gt;DaSH/&amp;lt;/code&amp;gt; directory.  This can either be empty or contain all files of the initial aircraft.  Then on the command line, add the aircraft to the local repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn add DaSH/&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then double check the changes prior to committing:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn st&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And send the changes to FGAddon with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An editor, often vi&amp;lt;ref&amp;gt;[http://www.vim.org/docs.php Vim documentation]&amp;lt;/ref&amp;gt;, will open and the commit message can be composed.  Alternatively the commit log message can be specified on the command line with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -m &amp;quot;&amp;lt;subject_line&amp;gt;\n\n&amp;lt;detailed_description&amp;gt;&amp;quot;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Commit blocking by pre-commit hooks ===&lt;br /&gt;
&lt;br /&gt;
Sometimes when committing to FGAddon, the commit will be blocked the following will be printed out:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is due to the presence of two repository pre-commit hook scripts which check the quality of the commit, blocking it if a text file is set to a binary file mime-type or if the executable flag is set.  These scripts are simply to protect the repository and to keep it clean.&lt;br /&gt;
&lt;br /&gt;
==== Mime-type problems ====&lt;br /&gt;
&lt;br /&gt;
Sometimes when attempting to commit files to FGAddon using the SVN tools, the commit will be blocked with the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Sending        dash-set.xml&lt;br /&gt;
svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&lt;br /&gt;
Aborting the commit, the svn:mime-type property is labelling the following text&lt;br /&gt;
files as binary:&lt;br /&gt;
&lt;br /&gt;
  dash-set.xml:  svn:mime-type=application/xml&lt;br /&gt;
&lt;br /&gt;
Before committing, please remove this property by typing 'svn propdel svn:mime-&lt;br /&gt;
type file_name' for all affected files.  This will allow the text files to be&lt;br /&gt;
treated as text within the FGAddon repository.&lt;br /&gt;
&lt;br /&gt;
To avoid the svn:mime-type property being incorrectly set by your subversion&lt;br /&gt;
client, the subversion configuration file at $HOME/.subversion/config or&lt;br /&gt;
%appdata%\roaming\subversion\config should be edited and a new entry added to&lt;br /&gt;
[auto-props] for each affected file type.  In most cases, the problem is with&lt;br /&gt;
XML files being labelled as &amp;quot;application/xml&amp;quot; by a library called libmagic.  To&lt;br /&gt;
override this, add the following to the svn config file:&lt;br /&gt;
&lt;br /&gt;
*.xml = svn:mime-type=text/xml&lt;br /&gt;
&lt;br /&gt;
svn: E165001: Your commit message was left in a temporary file:&lt;br /&gt;
svn: E165001:    '/flightgear/repo_testing/svn-commit.tmp'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Despite messages about adding or sending files, no change will have occurred in the FGAddon repository.  This message is created by a repository pre-commit hook script which checks if the Subversion &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property is set on a list of known text files and, if the mime-type is set to a binary format, the commit is blocked.  The reason for this block is to protect the repository.  Newer SVN clients rely on a 3rd party library known as libmagic which will detect the aircraft XML files as the binary mime-type of &amp;lt;code&amp;gt;application/xml&amp;lt;/code&amp;gt;.  The result is that the XML files are treated as binary files in the repository.  This behaviour is completely undesirable, as changes cannot be followed on the [[#FGAddon commitlog mailing list|flightgear-fgaddon-commitlogs mailing list]] or in the repository history, and the size of the commits become orders of magnitude larger.  Therefore this buggy behaviour has been blocked for the protection of the FlightGear project.  To remove the problem, follow the instructions in the message and, using the command line tools, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propdel svn:mime-type &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Repeat this for each text file listed in the error message.  Then commit again, using the commit message saved in the &amp;lt;code&amp;gt;svn-commit.tmp&amp;lt;/code&amp;gt; file.  The message file name will be reported in the commit failure message, but check its contents first:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
cat svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And reperform the commit:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -F svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Subversion config file =====&lt;br /&gt;
&lt;br /&gt;
The automatic property setting of &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; can be controlled by modifying the Subversion &amp;lt;code&amp;gt;config&amp;lt;/code&amp;gt; file.  Firstly in the &amp;lt;code&amp;gt;[miscellany]&amp;lt;/code&amp;gt; section, make sure that the auto-properties are turned on:&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
enable-auto-props = yes&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the &amp;lt;code&amp;gt;[auto-props]&amp;lt;/code&amp;gt; section, add:&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
*.ac = svn:mime-type=text/plain&lt;br /&gt;
*.eff = svn:mime-type=text/xml&lt;br /&gt;
*.frag = svn:mime-type=text/plain&lt;br /&gt;
*.nas = svn:mime-type=text/plain&lt;br /&gt;
*.osgx = svn:mime-type=text/xml&lt;br /&gt;
*.svg = svn:mime-type=text/svg+xml&lt;br /&gt;
*.txt = svn:mime-type=text/plain&lt;br /&gt;
*.vert = svn:mime-type=text/plain&lt;br /&gt;
*.xhtml = svn:mime-type=text/xml&lt;br /&gt;
*.xml = svn:mime-type=text/xml&lt;br /&gt;
*.xsl = svn:mime-type=text/xml&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These are all the text files that the hook script will check that the mime-type is set to a text format, though new text files will likely be added in the future.  These additions can either be to the user configuration file located at &amp;lt;code&amp;gt;~/.subversion/config&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;%USERPROFILE%\AppData\Roaming\Subversion\config&amp;lt;/code&amp;gt; in Windows) or, if a user configuration file is not set, to the global configuration file at &amp;lt;code&amp;gt;/etc/subversion/config&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;%APPDATA%\Subversion\config&amp;lt;/code&amp;gt; in Windows).&lt;br /&gt;
&lt;br /&gt;
==== Executable flag ====&lt;br /&gt;
&lt;br /&gt;
Another blocking message when attempting to commit files to FGAddon using the SVN tools is:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Adding         dash-set.xml&lt;br /&gt;
Transmitting file data .svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&lt;br /&gt;
The svn:executable property is set on the files ['dash-set.xml'], aborting the&lt;br /&gt;
commit.&lt;br /&gt;
&lt;br /&gt;
The current policy is that no executable files are allowed in FGAddon.  Before&lt;br /&gt;
committing, please remove this property by typing 'svn propdel svn:executable&lt;br /&gt;
file_name' for all affected files.  Or to remove it recursively from all files&lt;br /&gt;
to be committed, in your aircraft directory type 'svn propdel svn:executable&lt;br /&gt;
-R'.&lt;br /&gt;
&lt;br /&gt;
To avoid the svn:executable property being set by your subversion client, on&lt;br /&gt;
GNU/Linux and Mac OS X systems simply make sure that the file's execute bit is&lt;br /&gt;
not set before adding the file to be committed.&lt;br /&gt;
&lt;br /&gt;
svn: E165001: Your commit message was left in a temporary file:&lt;br /&gt;
svn: E165001:    '/flightgear/repo_testing/svn-commit.tmp'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will probably only be seen on Mac OS X and GNU/Linux systems.  This message is printed by a pre-commit repository hook script that checks if the Subversion &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property is set and, if so, the commit is blocked.  This is a security measure, as no aircraft files should be executable.  To remove the problem, follow the instructions in the message and, using the command line tools, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propdel svn:executable -R&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then commit again, using the commit message saved in the &amp;lt;code&amp;gt;svn-commit.tmp&amp;lt;/code&amp;gt; file.  The message file name will be reported in the commit failure message, but check its contents first:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
cat svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And the reperform the commit:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -F svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Binary diffs ===&lt;br /&gt;
&lt;br /&gt;
{{warning|The incorrect setting or absence of the mime-type property on a binary file will result in a binary diff.}}&lt;br /&gt;
&lt;br /&gt;
When looking at the output of &amp;lt;code&amp;gt;svn diff&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;git diff&amp;lt;/code&amp;gt; if you are using git-svn) as well as when reading messages from the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]], you may see a large number of unrecognisable characters.  This is the result of what is known as a binary diff, showing the binary file differences as if it were text.  Although this is not a issue for the operation of the repository, the situation is an aesthetic problem which makes it more difficult to perform a review of the changes.&lt;br /&gt;
&lt;br /&gt;
To fix the problem, firstly the binary files with the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property missing need to be identified.  The following subversion command can be used:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propget svn:mime-type &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As it can be tedious checking each file individually, the following Python script simplifies and automates the process to identify all binary files with a mime-type issue:&lt;br /&gt;
&lt;br /&gt;
{{collapsible script&lt;br /&gt;
| type   = Python 2/3 script&lt;br /&gt;
| title  = Find binary files with no &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property set.&lt;br /&gt;
| intro  = The following script is based on blacklisting text files.  Hence false positives are to be expected, and the blacklists can be expanded as needed.&lt;br /&gt;
| lang   = python&lt;br /&gt;
| script =&lt;br /&gt;
#! /usr/bin/env python&lt;br /&gt;
&lt;br /&gt;
from os import getcwd, walk&lt;br /&gt;
from os.path import join, splitext&lt;br /&gt;
from re import search&lt;br /&gt;
from subprocess import PIPE, Popen&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
skip_txt_file_seg = [&lt;br /&gt;
    'authors',&lt;br /&gt;
    'copying',&lt;br /&gt;
    'licen',&lt;br /&gt;
    'readme'&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
skip_txt_ext = [&lt;br /&gt;
    'ac',&lt;br /&gt;
    'css',&lt;br /&gt;
    'dat',&lt;br /&gt;
    'eff',&lt;br /&gt;
    'frag',&lt;br /&gt;
    'html',&lt;br /&gt;
    'json',&lt;br /&gt;
    'log',&lt;br /&gt;
    'nas',&lt;br /&gt;
    'osgx',&lt;br /&gt;
    'svg',&lt;br /&gt;
    'tex',&lt;br /&gt;
    'txt',&lt;br /&gt;
    'vert',&lt;br /&gt;
    'xhtml',&lt;br /&gt;
    'xml',&lt;br /&gt;
    'xsl'&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
skip_bin_prop = [&lt;br /&gt;
    'application/octet-stream',&lt;br /&gt;
    'application/pdf',&lt;br /&gt;
    'application/postscript',&lt;br /&gt;
    'application/x-dosexec',&lt;br /&gt;
    'application/x-gzip',&lt;br /&gt;
    'application/zip',&lt;br /&gt;
    'audio/x-wav',&lt;br /&gt;
    'image/gif',&lt;br /&gt;
    'image/jpeg',&lt;br /&gt;
    'image/png',&lt;br /&gt;
    'image/vnd.adobe.photoshop',&lt;br /&gt;
    'image/tiff',&lt;br /&gt;
    'image/x-ms-bmp',&lt;br /&gt;
    'image/x-xcf',&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
# Walk through the directories.&lt;br /&gt;
for root, dirs, files in walk(getcwd()):&lt;br /&gt;
    # Loop over the files in the current directory.&lt;br /&gt;
    for file in files:&lt;br /&gt;
        # Skip known text files.&lt;br /&gt;
        skip = False&lt;br /&gt;
        for i in range(len(skip_txt_file_seg)):&lt;br /&gt;
            if search(skip_txt_file_seg[i], file.lower()):&lt;br /&gt;
                skip = True&lt;br /&gt;
        if skip:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # The file extension.&lt;br /&gt;
        file_path, ext = splitext(file)&lt;br /&gt;
        ext = ext[1:].lower()&lt;br /&gt;
&lt;br /&gt;
        # Skip known text file extensions.&lt;br /&gt;
        if ext in skip_txt_ext:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # The full file path.&lt;br /&gt;
        path = join(root, file)&lt;br /&gt;
&lt;br /&gt;
        # Query the file for svn:mime-type.&lt;br /&gt;
        cmd = 'svn propget svn:mime-type \&amp;quot;%s\&amp;quot;' % path&lt;br /&gt;
        pipe = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=PIPE, close_fds=False)&lt;br /&gt;
        props = []&lt;br /&gt;
        for line in pipe.stdout.readlines():&lt;br /&gt;
            props.append(line.strip())&lt;br /&gt;
&lt;br /&gt;
        # Byte array conversion (Python3).&lt;br /&gt;
        for i in range(len(props)):&lt;br /&gt;
            if hasattr(props[i], 'decode'):&lt;br /&gt;
                props[i] = props[i].decode()&lt;br /&gt;
&lt;br /&gt;
        # Skip binary svn:mime-type values.&lt;br /&gt;
        if len(props) and props[0] in skip_bin_prop:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # Printout.&lt;br /&gt;
        if not len(props):&lt;br /&gt;
            print(&amp;quot;%s&amp;quot; % path)&lt;br /&gt;
        else:&lt;br /&gt;
            print(&amp;quot;%s    svn:mime-type=%s&amp;quot; % (path, props[0]))&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==== Fixing the problem ====&lt;br /&gt;
&lt;br /&gt;
As [[#Subversion_properties|git-svn cannot set or change]] the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property, a [[#Repository_checkout|svn checkout copy]] of the aircraft is required.  The property can then be set to the default Subversion binary mime-type with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, the following set of shell commands can be used to automate the process:&lt;br /&gt;
{{collapsible script&lt;br /&gt;
| type   = Shell commands&lt;br /&gt;
| title  = Set specific &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; values on a set of known binary files.&lt;br /&gt;
| intro = These shell commands will work on GNU/Linux or Mac OS X systems (or on Windows if using cygwin, or if a find command line tool is installed).  The list of file types here are those most commonly found in FGAddon.  To set the property on a list of binary files, type (or copy and paste):&lt;br /&gt;
| lang   = bash&lt;br /&gt;
| script =&lt;br /&gt;
find -iname &amp;quot;*.wav&amp;quot; -exec svn propset svn:mime-type &amp;quot;audio/x-wav&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.bmp*&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/x-ms-bmp&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.gif&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/gif&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.jpg&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/jpeg&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.png*&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/png&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.psd&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/vnd.adobe.photoshop&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.tif&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/tiff&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.xcf&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/x-xcf&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.rgb*&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.au&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.*af&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.3ds&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.blend*&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.dds&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.od[gst]&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.onetoc2&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.xlsx&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.pdf&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/pdf&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.ps&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/postscript&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.gz&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/x-gzip&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.mdl&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/x-dosexec&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.zip&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/zip&amp;quot; {} \;&lt;br /&gt;
| conc = Other binary files can safely be set to &amp;lt;code&amp;gt;&amp;quot;application/octet-stream&amp;quot;&amp;lt;/code&amp;gt;, the Subversion default for binary files.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== SourceForge developer services ==&lt;br /&gt;
&lt;br /&gt;
The FlightGear project is hosted on the SourceForge open source infrastructure.  This developer services section will highlight some of the useful tools you can take advantage of.  SourceForge consists of two categories of services:&lt;br /&gt;
; Project infrastructure : The FlightGear project uses the project services of SourceForge.  These services are for standalone software projects.&lt;br /&gt;
; Developer infrastructure : These are services available to anyone with a SourceForge account, and are available via your SourceForge homepage and accessible to all.  This includes being able to create multiple version control repositories (svn, git, hg), wikis, forums, development teams, blogs, and ticket trackers (for bugs, support requests, tasks, etc.).&lt;br /&gt;
&lt;br /&gt;
Rather than creating a new project, any development for the FlightGear project should be based on the developer infrastructure.&lt;br /&gt;
&lt;br /&gt;
=== Developer git repository ===&lt;br /&gt;
&lt;br /&gt;
To set up your own remote git repository, here for developing the FGAddon fkdr1 aircraft:&lt;br /&gt;
* On your profile page at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/profile/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;, go to &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Add New&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Git&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set label to &amp;lt;code&amp;gt;fkdr1 FGAddon git-svn repository&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set the code path to &amp;lt;code&amp;gt;code-fkdr1&amp;lt;/code&amp;gt;.  The &amp;lt;code&amp;gt;code-*&amp;lt;/code&amp;gt; prefix is to differentiate this from the &amp;lt;code&amp;gt;forum-*&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;wiki-*&amp;lt;/code&amp;gt;, and other directories.&lt;br /&gt;
&lt;br /&gt;
The repository will be located at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/code-fkdr1/ci/master/tree/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Development teams ===&lt;br /&gt;
&lt;br /&gt;
If you and a group of friends would like to privately develop one of the FGAddon aircraft as a team, assuming that the you have contacted the original aircraft authors and the aircraft is not actively being developed, then you should create a SourceForge development team.  A team leader should be appointed to set this up under their SourceForge account.  Assuming you wish to develop the &amp;quot;ornithopter&amp;quot; aircraft, the steps are:&lt;br /&gt;
&lt;br /&gt;
* Go to &amp;lt;code&amp;gt;Personal tools&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;User Permissions&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Add a new group&amp;lt;/code&amp;gt; at the bottom.&lt;br /&gt;
* Set the name to &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt;, and save.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Add&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; group and add the SourceForge names of all your team members.&lt;br /&gt;
&lt;br /&gt;
After setting up a private repository in the team leader's account, as described below, then the development team should be set up for the repository.&lt;br /&gt;
&lt;br /&gt;
* Go to the repository under your SourceForge account.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Admin - &amp;lt;repository name&amp;gt;&amp;lt;/code&amp;gt;, then select &amp;lt;code&amp;gt;Permissions&amp;lt;/code&amp;gt;.&lt;br /&gt;
* In the &amp;lt;code&amp;gt;Write&amp;lt;/code&amp;gt; section, remove &amp;lt;code&amp;gt;Developer&amp;lt;/code&amp;gt; and add &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Save&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The development team will then have commit access to the private repository.&lt;br /&gt;
&lt;br /&gt;
=== Team communications ===&lt;br /&gt;
&lt;br /&gt;
To help with team development, the SourceForge infrastructure allows for multiple [https://sourceforge.net/p/forge/documentation/Discussion/ dedicated discussion forums] to be created.  This can either be within a SourceForge project or under a SourceForge users homepage.  This allows the team leader to create a forum dedicated solely to the development of the aircraft of interest.  Continuing with the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; example, the steps for the team leader are simple:&lt;br /&gt;
&lt;br /&gt;
* On your profile page at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/profile/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;, go to &amp;lt;code&amp;gt;Personal tools&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on the &amp;lt;code&amp;gt;Tools&amp;lt;/code&amp;gt; option in the left hand menu.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Discussion&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;Click to install&amp;lt;/code&amp;gt; section.&lt;br /&gt;
* Change the label to &amp;lt;code&amp;gt;Ornithopter forum&amp;lt;/code&amp;gt;, and the path to &amp;lt;code&amp;gt;forum-ornithopter&amp;lt;/code&amp;gt;, for example.  The &amp;lt;code&amp;gt;forum-*&amp;lt;/code&amp;gt; prefix is to differentiate this from the &amp;lt;code&amp;gt;code-*&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;wiki-*&amp;lt;/code&amp;gt;, and other directories.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Save&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
More details are given on the [https://sourceforge.net/p/forge/documentation/Discussion/ SourceForge Discussion documentation].&lt;br /&gt;
&lt;br /&gt;
== Development scenarios ==&lt;br /&gt;
&lt;br /&gt;
=== Individual developer ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer and will use the native Subversion tools.}}&lt;br /&gt;
&lt;br /&gt;
This is by far the simplest development scenario and should be used in most cases.  If you are using the command line Subversion client, you can checkout an individual aircraft with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| path     = Aircraft/wrightFlyer1903&lt;br /&gt;
| post     = &lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is your SourceForge user name.  Alternatively you can checkout all aircraft with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| post     = flightgear-fgaddon&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If you do not have commit access, type one of:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| path     = Aircraft/wrightFlyer1903&lt;br /&gt;
| post     = &lt;br /&gt;
}}&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| post     = flightgear-fgaddon&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
To use the new local svn repository, see the [[#Subversion|subversion instructions]].&lt;br /&gt;
&lt;br /&gt;
=== Individual developer (git-svn) ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer and will use the git-svn tools.}}&lt;br /&gt;
&lt;br /&gt;
This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum.  To clone the aircraft of choice into a new git repository, type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is your infrastructure user name and &amp;lt;code&amp;gt;&amp;lt;aircraft&amp;gt;&amp;lt;/code&amp;gt; is the directory name in the FGAddon repository. This is valid whether or not you have commit permissions.&lt;br /&gt;
&lt;br /&gt;
To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].&lt;br /&gt;
&lt;br /&gt;
==== Upload to Sourceforge ====&lt;br /&gt;
&lt;br /&gt;
To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure.  For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile.  Then add this as a remote:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username&amp;gt;|type=git|repo=code-&amp;lt;aircraft&amp;gt;}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
And send the master branch where developments are located with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git push --set-upstream origin master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The changes in the new repository will be visible via the web interface at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=&amp;lt;username&amp;gt;|repo=code-&amp;lt;aircraft&amp;gt;|branch=master}}}}}}| style=&amp;quot;color: blue&amp;quot;}}.&lt;br /&gt;
&lt;br /&gt;
=== Sending external git repository changes into FGAddon ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer with FGAddon commit access and wish to transfer the commits in a remote git repository into FGAddon using a temporary local git repository.}}&lt;br /&gt;
&lt;br /&gt;
Firstly clone the FGAddon aircraft into a local git-svn repository with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This will create a new local git repository linked to FGAddon via git-svn.  If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]].  Next, set up the remote git repository as a remote, and fetch it:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git remote add &amp;lt;name&amp;gt; &amp;lt;url&amp;gt;&lt;br /&gt;
git fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;url&amp;gt;&amp;lt;/code&amp;gt; is the URL of the remote git repository.  Finally make an ordered list of all hashes of the commits to be sent into FGAddon, from earliest to latest, and cherry-pick them into the git-svn master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the git-svn local repository should only have a single &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch and only consist of cherry-picking.  To see the changes queued for sending to FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then to send the changes to FGAddon, firstly pull in any remote changes, and send the commits:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The temporary local repository can then be deleted.&lt;br /&gt;
&lt;br /&gt;
=== Connecting an existing git repository to FGAddon ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer or team leader with FGAddon commit access and wish to connect a pre-existing remote git repository with FGAddon to send all changes back to FGAddon.}}&lt;br /&gt;
&lt;br /&gt;
If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools.  The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]].  Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;aircraft&amp;gt;&amp;lt;/code&amp;gt; is the aircraft directory name in FGAddon.  Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology).  However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels.&lt;br /&gt;
&lt;br /&gt;
Now fetch the current state from the remote FGAddon repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The downloaded SVN history is in the remote branch &amp;lt;code&amp;gt;remotes/git-svn&amp;lt;/code&amp;gt;.  To commit changes to SVN you need a local branch that tracks this remote branch.  Create a local &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch that you will use to commit updates:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git branch fgaddon remotes/git-svn&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After committing new stuff to the &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch, to push to FGAddon checkout the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch and update it from SVN in case someone else has touched the aircraft in the remote FGAddon repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cherry-pick the new commits from &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; to preserve a linear history:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the changes queued for sending to FGAddon as either commits or a diff, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If everything looks ok, dcommit the local commits on the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch to send them to the remote FGAddon SVN repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Switch back to the master branch for local development:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To get changes from upstream you can either just download them with&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or download them and rebase your &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch onto them:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Team development ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  All members of the team are acting as gatekeepers, and all commits are made directly to FGAddon, either using svn or git-svn.}}&lt;br /&gt;
&lt;br /&gt;
The simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon.  Communication and coordination between the team members can be performed using a [[#Team_communications|team leader organised SourceForge forum]] or using the [http://forum.flightgear.org/ FlightGear forum].  In this scenario, the team needs to take the initiative and everyone apply for FGAddon commit access.&lt;br /&gt;
&lt;br /&gt;
=== Private team development (git-svn) ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  One team leader is acting as the gatekeeper on a private git repository hosted on the in-house SourceForge infrastructure, using git-svn to push a fgaddon branch to FGAddon, with team members committing directly to the private git repository or making merge requests from their fork of the private repository.}}&lt;br /&gt;
&lt;br /&gt;
To keep everything in-house, the entire operation will be based on the official infrastructure and remote repositories under each user's SourceForge (SF) profile.  Note to the team leader - you must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn keep your git-svn history linear] (meaning that a [[#Dedicated_FGAddon_branch|dedicated FGAddon branch]] should be created and changes manually cherry-picked into this branch).  In the following, the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; aircraft will be used as an example.&lt;br /&gt;
&lt;br /&gt;
==== The team ====&lt;br /&gt;
&lt;br /&gt;
Firstly, the entire team should sign up for [[#SourceForge account|SourceForge accounts]].&lt;br /&gt;
&lt;br /&gt;
==== Team leader ====&lt;br /&gt;
&lt;br /&gt;
===== Private repository set up =====&lt;br /&gt;
&lt;br /&gt;
These steps are to be taken by the team leader.  In your SourceForge user profile, set up a [[#Developer_git_repository| git repository]] with the label &amp;lt;code&amp;gt;Ornithopter FGAddon git-svn repository&amp;lt;/code&amp;gt; and code path &amp;lt;code&amp;gt;code-ornithopter&amp;lt;/code&amp;gt;.  Then create a empty local git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ mkdir ornithopter&lt;br /&gt;
$ cd ornithopter&lt;br /&gt;
$ git init&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Link the empty repository to the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; aircraft directory in the remote FGAddon repository and pull it in with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/ornithopter|full=1}}&lt;br /&gt;
$ git svn fetch&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; with your SF user name.  Set up a special git-svn branch for FGAddon gatekeeping and dcommitting changes back to the repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch fgaddon remotes/git-svn&lt;br /&gt;
$ git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And pull in the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; from FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current local git-svn repository setup, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch -vva&lt;br /&gt;
$ git remote -v&lt;br /&gt;
$ git svn info &lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then return to the master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, set up the remote git repository as a remote:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username&amp;gt;|type=git|repo=code-ornithopter}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
And send the master branch to the remote git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git push -u origin master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the new set up:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch -vva&lt;br /&gt;
$ git remote -v&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The repository will be located at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=&amp;lt;username&amp;gt;|repo=code-ornithopter|branch=master}}}}}}| style=&amp;quot;color: blue&amp;quot;}}.  Note that the git-svn information stored in the &amp;lt;code&amp;gt;.git/svn&amp;lt;/code&amp;gt; directory will not be pushed to remote SoureForge repository, and therefore the link back to FGAddon will only be present in the local copy of the team leader.  The git-svn link can be re-established at a later point if necessary.&lt;br /&gt;
&lt;br /&gt;
===== Team setup =====&lt;br /&gt;
&lt;br /&gt;
Set up a [[#Development teams|dedicated development team and grant them access to the git-svn repository]].&lt;br /&gt;
&lt;br /&gt;
===== Pushing to FGAddon =====&lt;br /&gt;
&lt;br /&gt;
Committing to FGAddon is for the local git repository of the team leader.  History must be linear in the fgaddon branch, so cherry-picking is the way to go.  This is from the [[#Individual developer (git-svn)|Individual developer (git-svn)]] section.  In the local git repository, switch to the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pull in any changes which have occurred in FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the commits in the &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch which are not in the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch, type one of:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log HEAD..master&lt;br /&gt;
git log HEAD..master --pretty=oneline&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manually select the commits to be sent to FGAddon and cherry-pick them:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Or to cherry-pick a range of commits:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;^..&amp;lt;commit hash 8&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then check what is to be sent:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Send the changes to FGAddon, send the git &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch changes to the remote git repository, and switch back to the master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
git push&lt;br /&gt;
git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally merge in the git svn commits with their new hashes from the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch, and send it to the remote git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git merge fgaddon&lt;br /&gt;
git push&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Team members ====&lt;br /&gt;
&lt;br /&gt;
===== Working with the repository =====&lt;br /&gt;
&lt;br /&gt;
Each team member should make a clone of the private git repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{sourceforge source|cmd=git clone|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username_leader&amp;gt;|type=git|repo=code-ornithopter|post=ornithopter|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; with your SourceForge user name, and &amp;lt;code&amp;gt;&amp;lt;username_leader&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name of the team leader.&lt;br /&gt;
&lt;br /&gt;
===== Forking and merge requests =====&lt;br /&gt;
&lt;br /&gt;
Alternatively, each team member can fork the git repository under your SourceForge account:&lt;br /&gt;
* Go to {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge source|user=&amp;lt;username&amp;gt;|repo=code-ornithopter|branch=master|full=1}}}}}}| style=&amp;quot;color: blue&amp;quot;}}, where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name of the team leader.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Fork&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set the mount point to &amp;lt;code&amp;gt;code-ornithopter&amp;lt;/code&amp;gt; and change the label as you wish.&lt;br /&gt;
&lt;br /&gt;
Develop and push to your fork, then make merge requests by clicking on the &amp;lt;code&amp;gt;Request Merge&amp;lt;/code&amp;gt; button.&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear]]&lt;br /&gt;
&lt;br /&gt;
[[de:FGAddon]]&lt;br /&gt;
[[en:FGAddon]]&lt;br /&gt;
[[fr:FGAddon]]&lt;br /&gt;
[[nl:FGAddon]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/FGAddon&amp;diff=117670</id>
		<title>Ca/FGAddon</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/FGAddon&amp;diff=117670"/>
		<updated>2019-03-23T23:11:14Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Obtenint aeronaus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
[[File:FGAddon logo.png|270px|right]]&lt;br /&gt;
&lt;br /&gt;
L'hangar oficial d'aeronaus '''FGAddon''' és un repositori de control de versions, allotjat a l'[https://sourceforge.net/projects/flightgear/ infraestructura SourceForge] de [[:ca:FlightGear|FlightGear]], i usat per al desenvolupament diari de les aeronaus del simulador.  FGAddon és un repositori de control de versions de {{wikipedia|Subversion|noicon=1|lang=ca}}. Aquestes aeronaus no formen part del paquet base (les aeronaus que s'inclouen al paquet base) — el [[Cessna 172P]] i l'[[UFO]] — es mantenen al repositori de [http://sourceforge.net/p/flightgear/fgdata FGData]), però apareixen amb cada versió estable a les [http://www.flightgear.org/download/ pàgines de descàrrega de FlightGear].&lt;br /&gt;
&lt;br /&gt;
El repositori de desenvolupament d'aeronaus FGAddon s’ha de considerar inestable.  Quan utilitzeu una versió estable de FlightGear, el millor és obtenir avions amb un número de versió coincident del programa base actual que apareix a les [http://www.flightgear.org/download/ pàgines de descàrrega de FlightGear].  Tanmateix, com les versions estables de FlightGear 3.4 en endavant estan etiquetats i presents al repositori de FGAddon, les eines de Subversion poden ser una manera convenient d’obtenir aeronaus individuals o tot l’hangar oficial d’aproximadament 500 avions.  També, si utilitzeu les [[FlightGear build server|últimes versions]] o una [[Building FlightGear|versió autocompilada de FlightGear]] dels [http://sourceforge.net/p/flightgear/_list/git repositoris de control de versions de Git] de FlightGear, utilitzant el FGAddon permet actualitzar l’avió a les últimes versions de desenvolupament.&lt;br /&gt;
&lt;br /&gt;
== Història ==&lt;br /&gt;
[[File:Image103.gif|thumb|Icona original de Win95]]&lt;br /&gt;
El projecte FlightGear va ser concebut el 8 d'abril de 1996 per David Murr, que va proposar un nou simulador de vol per ser desenvolupat per voluntaris&amp;lt;ref&amp;gt;David Murr (Apr 9, 1996).  FlightGear proposal 1.0: [https://groups.google.com/forum/#!msg/rec.aviation.simulators/ny8HFBE5_T8/OdtIiGNGJc8J &amp;quot;A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@&amp;quot;].  Published on the rec.aviation.simulators newsgroup.&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (1996).  FlightGear proposal 2.0: [http://www.flightgear.org/proposal-2.0 FLIGHT GEAR &amp;quot;This truly is as real as it gets!&amp;quot; - a proposal for a new flight simulator - REVISION 2.0].&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (Oct 29, 1996).  FlightGear proposal 3.0: [http://www.flightgear.org/proposal-3.0 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0 - Wednesday, 10.30.96, &amp;quot;The future of flight simulation is here&amp;quot;].  Published on the [http://ftp.igh.cnrs.fr/pub/flightgear/www/old-stuff/flight-gear.9610 flight-gear@infoplane.com mailing list].&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;David Murr (Sep 11, 1998).  FlightGear proposal 3.0.1: [http://www.flightgear.org/proposal-3.0.1 FLIGHT GEAR FLIGHT SIMULATOR, revision 3.0.1 - Friday, Sep.11.98, &amp;quot;The future of flight simulation is here&amp;quot;].&amp;lt;/ref&amp;gt;.  Part dels objectius inicials van ser desenvolupar rutines gràfiques 2D i 3D per al simulador. No obstant això, aquesta va ser una tasca enorme que va acabar sense finalitzar a principis de 1997, ja que el desenvolupador principal, Eric Korpela, estava acabant la seva tesi. Per tant, a partir del 16 de maig de 1997, Curtis Olson va rellançar el desenvolupament amb un nou projecte basat en les biblioteques d'OpenGL, que permetria crear un simulador de vol funcional en un curt període de temps.&amp;lt;ref&amp;gt;Curtis Olson (Sep 28, 2015).  [http://forum.flightgear.org/viewtopic.php?f=42&amp;amp;t=27558&amp;amp;p=259048#p259021 Re: A PROPOSAL FOR A NEW FLIGHT SIMULATOR - home built!@].  Published on the FlightGear forum.&amp;lt;/ref&amp;gt;  Les primeres contribucions van ser de [[FlightGear CVS|repositoris de control de versions CVS de flightgear i simgear]] originals.&lt;br /&gt;
&lt;br /&gt;
A mesura que el projecte va créixer, també ho va fer la mida, la quantitat i la qualitat dels actius de FlightGear. Aquests actius no estaven organitzats i estaven dispersos per diferents parts d'Internet. Per tant, es va decidir que gran part d’aquest contingut de FlightGear es reuniria i s’emmagatzemaria de manera conjunta en un nou repositori CVS centralitzat anomenat fgdata, que es va crear el 22 d’octubre de 2000. Per permetre la redistribució legal d’aquests actius com a part de la distribució de FlightGear, s’adoptava una política de GPLv2.&lt;br /&gt;
&lt;br /&gt;
Al maig del 2010, el desenvolupament va ser interromput malauradament per ''&amp;quot;l'incident del cafè&amp;quot;'' que va resultar en la pèrdua del servidor domèstic de Curtis que allotjava tots els repositoris de FlightGear&amp;lt;ref&amp;gt;James Turner (May 20, 2010). [http://thread.gmane.org/gmane.games.flightgear.devel/60340/focus=60341 &amp;lt;nowiki&amp;gt;[Flightgear-devel]&amp;lt;/nowiki&amp;gt; Re: Flightgear git repositories (was Re: GIT or CVS - Confusion)] Published on the flightgear-devel mailing list.&amp;lt;/ref&amp;gt;.  Aquests esdeveniments van resultar en un [[FlightGear CVS|migració massiva de tots els repositoris CVS als repositoris de Git]].  A causa de problemes d’amplada de banda, es va decidir que els nous repositoris s’alternessin a la infraestructura de codi obert Gitorious.&lt;br /&gt;
&lt;br /&gt;
Amb el temps que el projecte va créixer, la mida i l'abast del repositori de fgdata es va multiplicar, principalment a causa del creixent nombre d’avions emmagatzemats a [[$FG_ROOT]]/Aircraft, de manera que una divisió era inevitable. Gijs de Rooy va organitzar un primer intent de separació i es va anunciar el 18 d’octubre de 2011&amp;lt;ref&amp;gt;Cedric Sodhi (Oct 18, 2011) [http://thread.gmane.org/gmane.games.flightgear.devel/66846 &amp;lt;nowiki&amp;gt;[Flightgear-devel]&amp;lt;/nowiki&amp;gt; FGData Split Completed - a.k.a Life after the Split] Published on the flightgear-devel mailing list.&amp;lt;/ref&amp;gt;.  Cada avió es va col·locar en el seu propi repositori de Git i tots els avions vinculats de nou a fgdata mitjançant un enfocament del submodul Git. No obstant això, aquest intent va fallar i va ser abandonat. A partir d'aquesta data fins a finals de 2014, el disseny de la divisió fgdata es va discutir a la llista de correu de desenvolupament i es va resumir a l'article wiki de [[FlightGear Git: splitting fgdata|FlightGear Git: dividint fgdata]].  En les etapes de planificació, els repositoris es coneixien com a fgdata-old dividint-se en [[FGData]] (també conegut com a fgdata-new) i FGAddon (també conegut com a flightgear-aircraft i fgaircraft).  Després de mitja dècada de planificació, es va decidir que la millor solució per al desenvolupament d’avions de FlightGear seria un únic repositori de Subversion centralitzat. Això facilitaria la gestió i el manteniment comunitari de l’avió, alhora que proporciona modularitat i descàrregues més petites i mides de repositoris locals més petits.&lt;br /&gt;
&lt;br /&gt;
A finals de 2014, Gitorious, el proveïdor de la infraestructura de codi obert per al codi font de FlightGear i els repositoris de dades, va anunciar que tancaria els seus serveis fins al maig de 2015 a causa de la seva adquisició per GitLab. Això va motivar la divisió de fgdata-old i un canvi a l'infraestructura de codi obert SourceForge per allotjar els repositoris VC. Altres parts de la infraestructura de FlightGear ja estaven allotjades per SourceForge, fent que el moviment fos natural.  Segellant l’acord, SourceForge va acceptar per escrit allotjar l’enorme col·lecció d’avions de FlightGear, la mida de la qual no té rival en cercles de codi obert. Avui en dia, el repositori SVN de FGAddon, juntament amb la major part de la infraestructura del projecte FlightGear, està allotjat a SourceForge.&lt;br /&gt;
&lt;br /&gt;
A l'agost de 2015, es va escriure un nou document de política de FlightGear per codificar els estàndards no escrits del projecte&amp;lt;ref&amp;gt;[http://www.flightgear.org/flightgear-policy-document/ FlightGear Policy Document and Roadmap], draft document.&amp;lt;/ref&amp;gt;.  Amb aquest document, la política de llicències dels avions de FlightGear allotjada a FGAddon ha estat actualitzada ed GPLv2-only a GPLv2+. Per combatre la proliferació de llicències, cal evitar complicacions mitjançant el treball d’una aeronau a una altra, i per la integritat i el bon projecte del FlightGear, es recomana que tot el contingut original (allotjat a FGAddon o en qualsevol altre lloc) sigui llicenciat amb GPLv2+.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
{{FGCquote&lt;br /&gt;
|1= The short summary is that we already were maintaining a well established presence on sourceforge. So after quite a bit of discussion, we decided to consolidate there. In addition, we had a perpetual complaint that the fgdata git repository was far too big for most people to initially download (1Gb+). Thus we split off most of the aircraft (expecting unbounded future growth potential) into an svn repository called fgaddon. Sourceforge supports both git and svn repositories. This puts a dependency on a central svn server for our fgaddon aircraft repository, but lightens the weight for anyone wanting to checkout a copy of everything (you don't need a copy of the entire development history, and a copy of every version ever created of every aircraft if you just want to have the latest versions.) Plus svn allows checking out subtrees (without needing the whole repository) so this can also serve as a potential JIT single aircraft service provider. Of course there are always multiple ways to solve every problem and of course every engineering decision has trade offs. Github is a nice provider, no doubt. I have been using them for a number of my own personal repositories. Git of course has ways to address many of the issues we have addressed, but of course everything has strengths and weaknesses.&lt;br /&gt;
|2= {{cite web&lt;br /&gt;
  | url    = http://sourceforge.net/p/flightgear/mailman/message/35054405/&lt;br /&gt;
  | title  = &amp;lt;nowiki&amp;gt;Re: [Flightgear-devel] FlightGear and GitHub&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  | author = &amp;lt;nowiki&amp;gt;Curtis Olson&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
  | date   = Apr 30th, 2016&lt;br /&gt;
  | added   = Apr 30th, 2016&lt;br /&gt;
  | script_version = 0.25&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Obtenint aeronaus ==&lt;br /&gt;
&lt;br /&gt;
{{tip|Si esteu interessats a obtenir aeronaus per a llançaments de FlightGear estables i no teniu coneixement del control de versions, heu de visitar el [[Ca/Hangars de FlightGear|Hangars de FlightGear]] per descarregar-les.}}&lt;br /&gt;
{{caution|Si les versions de les aeronaus de FlightGear i FGAddon no coincideixen, poden aparèixer errors i el suport en versions no compatibles no serà efectuat per la comunitat de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
With access to the Subversion (SVN) tools, the FGAddon version control repository can be a convenient way for obtaining aircraft for using within a specific FlightGear version directly from the official source.  When using the [[FlightGear Build Server|nightly builds]] or a [[Building FlightGear|version controlled copy of FlightGear]], the most up to date in-development versions of the aircraft should be used so the versions match.  The following describes how to use the official repository to obtain aircraft from the perspective of a FlightGear user.&lt;br /&gt;
&lt;br /&gt;
=== Preparació ===&lt;br /&gt;
To use the FGAddon repository, the Subversion tools need to be installed:&lt;br /&gt;
* '''MS Windows''': Install one of the [https://subversion.apache.org/packages.html#windows many Subversion clients].  For example [https://sliksvn.com/download/ SlikSVN] is one of the best command line versions and the best for aircraft development, and [http://tortoisesvn.net/ TortoiseSVN] provides a user friendly graphical user interface (GUI) by integrating into Windows Explorer.&lt;br /&gt;
* '''Mac OS X''': Install the [https://subversion.apache.org/packages.html#osx official Subversion client].&lt;br /&gt;
* '''GNU/Linux''': Install the Subversion client via the package manager.  This will usually be in a package called &amp;lt;code&amp;gt;subversion-*.{rpm,deb}&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Directori de FGAddon ===&lt;br /&gt;
To know how to use the FGAddon repository, an understanding of the repository directory layout is essential.&lt;br /&gt;
* &amp;lt;code&amp;gt;/trunk&amp;lt;/code&amp;gt;:  This base directory is where the in-development versions of the aircraft are located.&lt;br /&gt;
* &amp;lt;code&amp;gt;/branches/release-x.y.z/&amp;lt;/code&amp;gt;:  These directories correspond to the specific stable FlightGear releases.&lt;br /&gt;
&lt;br /&gt;
The [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/ web interface for the FGAddon repository] allows all of the aircraft to be browsed.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega ===&lt;br /&gt;
[[File:V22Osprey.jpg|thumb|200px|Aircraft to be downloaded]]&lt;br /&gt;
Firstly, choose an aircraft to download.  The [[Bell Boeing V-22 Osprey]] will be used in this example.&lt;br /&gt;
&lt;br /&gt;
==== Command line ====&lt;br /&gt;
&lt;br /&gt;
To download the aircraft for FlightGear 3.4, simply type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|branch=branches/release-3.4.0|path=Aircraft/V22-Osprey|post=}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
To obtain the in-development version, type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|path=Aircraft/V22-Osprey|post=}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If all of the ~500 aircraft from the repository are desired - beware that this will be a huge download of over 6 GB - use the following command:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|post=flightgear-fgaddon}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
When using a stable FlightGear release, for example FlightGear 2016.1, to obtain all of the FGAddon aircraft to match the installed FlightGear version, use:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co|branch=branches/release-2016.1|post=flightgear-fgaddon}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==== GUI clients and TortoiseSVN ====&lt;br /&gt;
&lt;br /&gt;
When using one of the Subversion GUIs (graphical user interfaces), simply copy one of the above &amp;lt;code&amp;gt;https://&amp;lt;/code&amp;gt; URLs and use that in the GUI (each GUI is different, so see the relevant documentation for help).  For the unique TortoiseSVN tool, simply:&lt;br /&gt;
&lt;br /&gt;
* In Windows Explorer, create a new empty folder for the aircraft (or aircraft collection).&lt;br /&gt;
* In the new folder, right click and select &amp;lt;code&amp;gt;SVN Checkout...&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Copy and paste the URL, for example {{fgaddon source|path=Aircraft/V22-Osprey|type=svn|full=1}}, leave all other settings as they are, and import by clicking on &amp;lt;code&amp;gt;OK&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
For more details, see the [http://tortoisesvn.net/support.html TortoiseSVN documentation].  Note that there is an option to install the command line tools when installing TortoiseSVN.&lt;br /&gt;
&lt;br /&gt;
=== Flying ===&lt;br /&gt;
&lt;br /&gt;
To use the newly downloaded aircraft, please see the [[Howto:Install aircraft]] article, skipping the instructions for downloading and unzipping the aircraft.&lt;br /&gt;
&lt;br /&gt;
=== Updates ===&lt;br /&gt;
With a checked out copy of the &amp;lt;code&amp;gt;/trunk&amp;lt;/code&amp;gt; in-development version, the aircraft can be updated to the latest version using the command:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn up&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Aircraft development ==&lt;br /&gt;
&lt;br /&gt;
{{tip|The FlightGear community encourages aircraft development directly within FGAddon.}}&lt;br /&gt;
&lt;br /&gt;
=== Contact the original aircraft authors ===&lt;br /&gt;
&lt;br /&gt;
The first step for developing and advancing the aircraft of the official FlightGear hangar, or from one of the [[Flightgear_hangars#Aircraft_hangars|private hangars]] for that matter, is to make contact with the original aircraft author(s).  Their names can be found within the &amp;lt;code&amp;gt;*-set.xml&amp;lt;/code&amp;gt; file, within the &amp;lt;code&amp;gt;&amp;lt;authors&amp;gt;&amp;lt;/code&amp;gt; XML tag.  Often the contact email address will be listed in a README file or some other text file in the base aircraft directory.  If not, contact can sometimes be established via the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list].  Contacting the original authors is important to see if the aircraft is currently being actively developed, and if you can join in as part of the development team.&lt;br /&gt;
&lt;br /&gt;
=== SourceForge account ===&lt;br /&gt;
&lt;br /&gt;
To work on the official aircraft collection, a [https://sourceforge.net/user/registration/ SourceForge account] should first be set up.  This will allow to either directly commit to the FGAddon repository, if commit access has been been granted, or to work in as part of a SourceForge development team.  The registration process is lightning quick and the SourceForge developer infrastructure and developer services will be accessible in under a minute.&lt;br /&gt;
&lt;br /&gt;
=== Commit access ===&lt;br /&gt;
&lt;br /&gt;
Before obtaining commit access, an all-out effort to contact the original author(s) should be made to determine if the aircraft is actively being developed.  If this is unsuccessful, sign up for the [https://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear development mailing list] and ask for help there.  If the aircraft has a current maintainer, you will be directed as to how to proceed with development.  Otherwise ask if someone could volunteer to mentor you in the process of becoming an aircraft developer with full commit access.&lt;br /&gt;
&lt;br /&gt;
To obtain commit access, you will first need:&lt;br /&gt;
# To demonstrate your capabilities and development skills.&lt;br /&gt;
# To show that you understand the [http://www.flightgear.org/flightgear-policy-document/ FlightGear policy document]. &lt;br /&gt;
# To show an understanding of the GPL licensing issues, and that you can be trusted not to use copyrighted, non-GPL material.&lt;br /&gt;
# To earn the trust of the FlightGear community.&lt;br /&gt;
&lt;br /&gt;
These easy to jump over hurdles are simply designed to protect against repository corruption or pollution of the repository with illegal content.&lt;br /&gt;
&lt;br /&gt;
To have your changes committed into the FGAddon repository, you should discuss and coordinate with the original aircraft author, or your mentor, for the best way to proceed.  Depending on the [[#Development_scenarios|development scenario]], this maybe by merge request, file transfer, the primitive patch system, or any other convenient way.  Once you believe you have proven your capabilities and you are knowledgeable about GPL licensing issues, you should write a mail to the development mailing list asking if you can be granted commit access, providing your SourceForge username.&lt;br /&gt;
&lt;br /&gt;
=== FGAddon commitlog mailing list ===&lt;br /&gt;
&lt;br /&gt;
To follow all changes which occur in the FGAddon repository, subscribe to the dedicated [https://lists.sourceforge.net/lists/listinfo/flightgear-fgaddon-commitlogs Flightgear FGAddon commitlogs mailing list].  One email is sent per commit, as the commit is made.&lt;br /&gt;
&lt;br /&gt;
== Version control tools ==&lt;br /&gt;
&lt;br /&gt;
To access FGAddon and use it for aircraft development, the Subversion or SVN version control tools are needed.  Alternatively git-svn provides an interface for those who prefer the git version control tools.&lt;br /&gt;
&lt;br /&gt;
=== Subversion ===&lt;br /&gt;
&lt;br /&gt;
==== Set up ====&lt;br /&gt;
The FGAddon aircraft hangar is stored in a remote Subversion repository located on the SourceForge infrastructure, and therefore it is simplest to use the SVN tools for aircraft development and will cause the least problems.  See the [[#Preparation|Subversion installation section]] for setting up the tool chain.&lt;br /&gt;
&lt;br /&gt;
==== Repository checkout ====&lt;br /&gt;
The first step is to 'checkout' a copy of either the repository trunk or one of the aircraft in the trunk:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn co &amp;lt;url&amp;gt; &amp;lt;dir&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the relevant URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section.  This command will create a local subversion repository copy in the given &amp;lt;code&amp;gt;&amp;lt;dir&amp;gt;&amp;lt;/code&amp;gt; directory.  Note that this will only contain the part of the FGAddon repository specified in the URL.  This means that Subversion allows you to checkout either a single file all the way to the entire remote repository.&lt;br /&gt;
&lt;br /&gt;
==== Information and history ====&lt;br /&gt;
At any point to see information about the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn info&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the history of the checked out copy of the repository, type one of:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn log&lt;br /&gt;
svn log | less&lt;br /&gt;
svn log -v | less&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Daily usage ====&lt;br /&gt;
The main Subversion command you will be using is:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn add &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will register the file or directory &amp;lt;code&amp;gt;&amp;lt;path&amp;gt;&amp;lt;/code&amp;gt; within the local repository to allow it to later be 'committed' and sent to the remote repository.  To move or rename a file or directory, use:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn mv &amp;lt;path1&amp;gt; &amp;lt;path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This should be used rather than normal file moving/renaming so that the change is tracked in the local repository.  To remove a file from the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn rm &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current status of the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn st&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To update the local repository with changes in the remote repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn up&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Committing changes ====&lt;br /&gt;
All of the above operations only occur on the local repository copy - the remote FGAddon repository at SourceForge will know nothing of these changes.  To send all your changes to FGAddon, you need to commit the changes:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will open up an editor to allow you to write an informative commit log message.  When committing, it is best to make small modular commits so that each commit corresponds to a single purpose.  Note that you can only commit to FGAddon if you have [[#Commit access|commit access]].&lt;br /&gt;
&lt;br /&gt;
==== Branching ====&lt;br /&gt;
The concept of Subversion branching is currently only used in the FlightGear project for tagging the stable releases.  However if you are curious about branching, see the [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.html Branching and Merging chapter of the Subversion manual], and the [https://www.orcaware.com/svn/wiki/Svnmerge.py svnmerge.py script] which can greatly simplify the process.&lt;br /&gt;
&lt;br /&gt;
=== Git-svn ===&lt;br /&gt;
&lt;br /&gt;
The git-svn tool is useful for those who are already familiar with using git repositories, or those who wish to have their own private aircraft development playground.  Git-svn provides a bridge between the remote FGAddon Subversion repository and a local git repository.  For those unfamiliar with git, the git-svn bridge together with the git repository is far more complicated to use than the native [[#Subversion|Subversion tools]].  For more information on using git, see [[Howto:Start using git]]. The following will assume that only a single aircraft will be stored in the local git repository.&lt;br /&gt;
&lt;br /&gt;
==== Set up ====&lt;br /&gt;
The git distributed version control system needs to first be [https://git-scm.com/downloads installed].&lt;br /&gt;
&lt;br /&gt;
==== Cloning a single aircraft ====&lt;br /&gt;
The first step is to 'clone' a copy of one of the aircraft in the remote Subversion trunk:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn clone &amp;lt;aircraft_url&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
For the relevant aircraft URL to use, you must chose one of the [[#Development_scenarios|development scenarios]] and find the URL in that section.  The URL depends on your [[#Commit access|FGAddon commit access status]].  The clone command will create a local git repository containing solely the aircraft of interest, and initialise the git-svn bridge.&lt;br /&gt;
&lt;br /&gt;
==== Information and history ====&lt;br /&gt;
At any point to see information about the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn info&lt;br /&gt;
git branch -vva&lt;br /&gt;
git remote -v&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the history of the checked out copy of the repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Daily usage ====&lt;br /&gt;
The main git command you will be using is:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git add &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will register the file or directory &amp;lt;code&amp;gt;&amp;lt;path&amp;gt;&amp;lt;/code&amp;gt; within the local repository to allow it to later be 'committed' to the local git repository.  To move or rename a file or directory, use:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git mv &amp;lt;path1&amp;gt; &amp;lt;path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However note that git history is not as robust as svn history.  See the [[#Moving_or_renaming_files|git-svn file moving/renaming deficiency section]] for how to better perform this operation.  To remove a file from the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git rm &amp;lt;path&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current status of the local repository, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git status&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Committing changes ====&lt;br /&gt;
As git is a distributed version control system, changes are committed to the local git repository.&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git commit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will open up an editor to allow you to write an informative commit log message.  The commit is local and will not be sent to FGAddon.&lt;br /&gt;
&lt;br /&gt;
==== Dedicated FGAddon branch ====&lt;br /&gt;
In the examples above, only a single branch was assumed in the repository.  If interaction with a remote git repository or branching within the local git repository is desired, then a different strategy is required.  The reason being that the branch that synchronises with FGAddon must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn preserve a linear history].  This means only cherry-picking of the desired changes into that branch is allowed.&lt;br /&gt;
&lt;br /&gt;
In this example, two branches will be set up in the local git repository:&lt;br /&gt;
* &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt;:  This branch will be dedicated for FGAddon synchronisation and will preserve a linear history.&lt;br /&gt;
* &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt;:  A master branch for aircraft development, allowing for mergers and other non-linear history operations.&lt;br /&gt;
&lt;br /&gt;
Assuming a [[#Cloning_a_single_aircraft|newly cloned repository]], create the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git branch fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And switch to that branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The FGAddon synchronisation can then be performed on this branch.  To pull in the developments from the master branch, use cherry-picking to apply a sequentially ordered list of commit hashes:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the list of commits to be sent to FGAddon prior to dcommitting, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And to see the changes as a single diff:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Synchronising ====&lt;br /&gt;
To send the changes to the remote FGAddon repository, firstly change to the dedicated &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure the local git-svn repository is up to date with all changes that have occurred in FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then push or dcommit the changes to FGAddon with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Deficiencies of git-svn ===&lt;br /&gt;
&lt;br /&gt;
{{warning|Performing a &amp;lt;code&amp;gt;git-svn clone&amp;lt;/code&amp;gt; of the &amp;lt;code&amp;gt;/trunk/&amp;lt;/code&amp;gt; or entire repository is not recommended, as the entire repository history will be downloaded, resulting in a huge local repository, as well as putting a large strain on the FlightGear open source infrastructure.}}&lt;br /&gt;
&lt;br /&gt;
It is important to understand that there are a number of operations in which git-svn is deficient.  In many cases, the svn tools should be used instead.&lt;br /&gt;
&lt;br /&gt;
==== Copying files between aircraft ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn does not maintain the file copying history normally present in a Subversion repository.}}&lt;br /&gt;
&lt;br /&gt;
The most important of these is the copying of content from other FGAddon aircraft.  In this case you will need FGAddon commit access and a local svn copy of the repository.  Firstly synchronise the repositories by dcommitting all changes back to FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the local svn repository, copy the file:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn cp Aircraft/&amp;lt;aircraft1&amp;gt;/&amp;lt;file_path1&amp;gt; Aircraft/&amp;lt;aircraft2&amp;gt;/&amp;lt;file_path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And commit the change:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Back in the local git-svn repository, pull in the new files:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Using the subversion tools avoids the FGAddon repository backend from significantly increasing in size, as [http://svnbook.red-bean.com/en/1.7/svn.branchmerge.using.html#svn.branchmerge.using.create svn copies are cheap].&lt;br /&gt;
&lt;br /&gt;
==== Moving or renaming files ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn does not always maintain the file moving or renaming history normally present in a Subversion repository.}}&lt;br /&gt;
&lt;br /&gt;
This problem stems from the fact that svn history is more robust than that of git.  The &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; and &amp;lt;code&amp;gt;git mv&amp;lt;/code&amp;gt; commands are not equivalent.  The subversion command stores the move history directly in the repository whereas git does not (git instead uses heuristic methods to try to detect history, after the commit).  The result of using git-svn is that often the move will not be detected and the FGAddon history will show one file or directory being deleted and another added.  This also causes the repository backend to increase in size, whereas &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; will not cause any significant size increase.  If you wish to have a better historical record in the FGAddon repository and be considerate to the repository backend, it is recommended that you temporarily switch to the subversion tools.  Firstly, synchronise the repositories:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the local svn repository, move or rename the file:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn mv Aircraft/&amp;lt;aircraft&amp;gt;/&amp;lt;file_path1&amp;gt; Aircraft/&amp;lt;aircraft&amp;gt;/&amp;lt;file_path2&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And commit the change:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Back in the local git-svn repository, pull in the changes with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Copying files within one aircraft ====&lt;br /&gt;
&lt;br /&gt;
Just as the &amp;lt;code&amp;gt;svn mv&amp;lt;/code&amp;gt; command stores the move information directly within the repository, so does &amp;lt;code&amp;gt;svn cp&amp;lt;/code&amp;gt; store the copy information.  Therefore if you would like to duplicate a text file and modify it, using the native Subversion tools instead of git-svn for this operation allows for the file history to be permanently preserved in the FGAddon repository.&lt;br /&gt;
&lt;br /&gt;
==== Subversion properties ====&lt;br /&gt;
&lt;br /&gt;
{{caution|Git-svn currently only supports the &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property, all other properties are ignored and cannot be added, changed, or removed in a git-svn clone of the aircraft.}}&lt;br /&gt;
&lt;br /&gt;
Internally, Subversion identifies binary files using the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; repository property.  However as git-svn cannot set this property when using the &amp;lt;code&amp;gt;git add&amp;lt;/code&amp;gt; command, the result is that binary files will be treated as text.  Binary diffs will be seen when using &amp;lt;code&amp;gt;svn diff&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;git diff&amp;lt;/code&amp;gt;, and a binary diff will be shown in the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]] messages.  As this issue is not unique to git-svn, to work around this issue please see the [[#Binary diffs|binary diffs]] section.&lt;br /&gt;
&lt;br /&gt;
==== Protocols other than svn+ssh ====&lt;br /&gt;
&lt;br /&gt;
The command &amp;lt;code&amp;gt;git svn init&amp;lt;/code&amp;gt; replicates the entire history of an aircraft into a local repository.  As part of this process, it generates a git commit ID or hash for every Subversion revision. The problem is that the git commit ID depends on the protocol used to read from the Subversion repository (likely a git bug).   Hence:&lt;br /&gt;
&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
and&lt;br /&gt;
&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=https|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
will result in two different and incompatible git repositories, even though they contain the same data. The incompatibility is not immediately apparent but it will bite later. Suppose someone with read-only access to FGAddon uses the https method, then asks a FGAddon gatekeeper to commit their changes. The gatekeeper, naturally, uses svn+ssh, as this is the only protocol granting write permissions. When the gatekeeper tries to merge the contributor's https clone into their own svn+ssh clone, git will complain that the two repositories have no history in common, and flag every change as a conflict.&lt;br /&gt;
&lt;br /&gt;
Therefore, if you are planning to make any changes to an aircraft, be sure to use svn+ssh even if you do not yet have commit permissions on FGAddon. svn+ssh does not require write permissions, it only requires a SourceForge user ID.&lt;br /&gt;
&lt;br /&gt;
== FGAddon development concepts ==&lt;br /&gt;
&lt;br /&gt;
=== New aircraft ===&lt;br /&gt;
&lt;br /&gt;
To add a new aircraft to the FGAddon repository, the SVN tools are required.  If you encounter &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property problems when adding a new aircraft, see the [[#Mime-type problems|mime-type problems section]] for how to resolve the issue.  Or if you have a &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property problem, see the [[#Executable flag|executable flag problem section]].&lt;br /&gt;
&lt;br /&gt;
==== svn import ====&lt;br /&gt;
&lt;br /&gt;
{{warning|The &amp;lt;code&amp;gt;svn import&amp;lt;/code&amp;gt; command described herein will send all contents of the specified directory directly into FGAddon without warning and without a way to cancel the operation.  Therefore special care must be taken when specifying the directory to upload into FGAddon, as well as the target FGAddon directory.  See the [[#svn add|svn add]] section below for a safer way to add a new aircraft.}}&lt;br /&gt;
&lt;br /&gt;
The [http://svnbook.red-bean.com/en/1.7/svn.tour.importing.html#svn.tour.importing.import svn import] command is the easiest method to use and does not require a local copy of the repository to be checked out.  To start:&lt;br /&gt;
&lt;br /&gt;
# Create an empty local aircraft directory.&lt;br /&gt;
# Copy the aircraft files into this directory.&lt;br /&gt;
# Carefully check all files to make sure there are no hidden or temporary files that should not be uploaded to FGAddon.&lt;br /&gt;
&lt;br /&gt;
Assuming the Dead Simple Human Powered Airplane (DaSH PA or &amp;quot;DaSH&amp;quot;) aircraft as an example, located in the &amp;lt;code&amp;gt;DaSH/&amp;lt;/code&amp;gt; directory, on the command line run:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source&lt;br /&gt;
| cmd      = svn import DaSH/&lt;br /&gt;
| protocol = svn+ssh&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| type     = svn&lt;br /&gt;
| path     = Aircraft/DaSH/&lt;br /&gt;
| post     = -m \&lt;br /&gt;
| full     = 1&lt;br /&gt;
}}&lt;br /&gt;
    &amp;quot;Initial import of the DaSH human powered aircraft.\n\nFor details see the forum thread at http://forum.flightgear.org/viewtopic.php?f=4&amp;amp;t=24495 .&amp;quot;&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name.  This will add all the files into FGAddon with commit log message with the summary line &amp;lt;code&amp;gt;Initial import of the DaSH human powered aircraft.&amp;lt;/code&amp;gt;, followed by a blank line, and then a detailed description pointing to the original location or discussion of the aircraft.  To see if the aircraft has been successfully added to the repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source&lt;br /&gt;
| cmd      = svn list&lt;br /&gt;
| protocol = svn+ssh&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| type     = svn&lt;br /&gt;
| path     = Aircraft/DaSH/&lt;br /&gt;
| full     = 1&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Or visit the {{fgaddon source|path=Aircraft|text=FGAddon web interface}}.  The aircraft can then be checked out as described in the [[#Development scenarios|Development scenarios section]].&lt;br /&gt;
&lt;br /&gt;
==== svn add ====&lt;br /&gt;
&lt;br /&gt;
If a local copy of the FGAddon trunk is present, then the &amp;lt;code&amp;gt;svn add&amp;lt;/code&amp;gt; command can be used instead.  This is far safer than the &amp;lt;code&amp;gt;svn import&amp;lt;/code&amp;gt; command, as the change can be double checked before committing.  In the &amp;lt;code&amp;gt;Aircraft/&amp;lt;/code&amp;gt; directory of the local repository, create the &amp;lt;code&amp;gt;DaSH/&amp;lt;/code&amp;gt; directory.  This can either be empty or contain all files of the initial aircraft.  Then on the command line, add the aircraft to the local repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn add DaSH/&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then double check the changes prior to committing:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn st&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And send the changes to FGAddon with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An editor, often vi&amp;lt;ref&amp;gt;[http://www.vim.org/docs.php Vim documentation]&amp;lt;/ref&amp;gt;, will open and the commit message can be composed.  Alternatively the commit log message can be specified on the command line with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -m &amp;quot;&amp;lt;subject_line&amp;gt;\n\n&amp;lt;detailed_description&amp;gt;&amp;quot;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Commit blocking by pre-commit hooks ===&lt;br /&gt;
&lt;br /&gt;
Sometimes when committing to FGAddon, the commit will be blocked the following will be printed out:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is due to the presence of two repository pre-commit hook scripts which check the quality of the commit, blocking it if a text file is set to a binary file mime-type or if the executable flag is set.  These scripts are simply to protect the repository and to keep it clean.&lt;br /&gt;
&lt;br /&gt;
==== Mime-type problems ====&lt;br /&gt;
&lt;br /&gt;
Sometimes when attempting to commit files to FGAddon using the SVN tools, the commit will be blocked with the following message:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Sending        dash-set.xml&lt;br /&gt;
svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&lt;br /&gt;
Aborting the commit, the svn:mime-type property is labelling the following text&lt;br /&gt;
files as binary:&lt;br /&gt;
&lt;br /&gt;
  dash-set.xml:  svn:mime-type=application/xml&lt;br /&gt;
&lt;br /&gt;
Before committing, please remove this property by typing 'svn propdel svn:mime-&lt;br /&gt;
type file_name' for all affected files.  This will allow the text files to be&lt;br /&gt;
treated as text within the FGAddon repository.&lt;br /&gt;
&lt;br /&gt;
To avoid the svn:mime-type property being incorrectly set by your subversion&lt;br /&gt;
client, the subversion configuration file at $HOME/.subversion/config or&lt;br /&gt;
%appdata%\roaming\subversion\config should be edited and a new entry added to&lt;br /&gt;
[auto-props] for each affected file type.  In most cases, the problem is with&lt;br /&gt;
XML files being labelled as &amp;quot;application/xml&amp;quot; by a library called libmagic.  To&lt;br /&gt;
override this, add the following to the svn config file:&lt;br /&gt;
&lt;br /&gt;
*.xml = svn:mime-type=text/xml&lt;br /&gt;
&lt;br /&gt;
svn: E165001: Your commit message was left in a temporary file:&lt;br /&gt;
svn: E165001:    '/flightgear/repo_testing/svn-commit.tmp'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Despite messages about adding or sending files, no change will have occurred in the FGAddon repository.  This message is created by a repository pre-commit hook script which checks if the Subversion &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property is set on a list of known text files and, if the mime-type is set to a binary format, the commit is blocked.  The reason for this block is to protect the repository.  Newer SVN clients rely on a 3rd party library known as libmagic which will detect the aircraft XML files as the binary mime-type of &amp;lt;code&amp;gt;application/xml&amp;lt;/code&amp;gt;.  The result is that the XML files are treated as binary files in the repository.  This behaviour is completely undesirable, as changes cannot be followed on the [[#FGAddon commitlog mailing list|flightgear-fgaddon-commitlogs mailing list]] or in the repository history, and the size of the commits become orders of magnitude larger.  Therefore this buggy behaviour has been blocked for the protection of the FlightGear project.  To remove the problem, follow the instructions in the message and, using the command line tools, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propdel svn:mime-type &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Repeat this for each text file listed in the error message.  Then commit again, using the commit message saved in the &amp;lt;code&amp;gt;svn-commit.tmp&amp;lt;/code&amp;gt; file.  The message file name will be reported in the commit failure message, but check its contents first:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
cat svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And reperform the commit:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -F svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Subversion config file =====&lt;br /&gt;
&lt;br /&gt;
The automatic property setting of &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; can be controlled by modifying the Subversion &amp;lt;code&amp;gt;config&amp;lt;/code&amp;gt; file.  Firstly in the &amp;lt;code&amp;gt;[miscellany]&amp;lt;/code&amp;gt; section, make sure that the auto-properties are turned on:&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
enable-auto-props = yes&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then in the &amp;lt;code&amp;gt;[auto-props]&amp;lt;/code&amp;gt; section, add:&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
*.ac = svn:mime-type=text/plain&lt;br /&gt;
*.eff = svn:mime-type=text/xml&lt;br /&gt;
*.frag = svn:mime-type=text/plain&lt;br /&gt;
*.nas = svn:mime-type=text/plain&lt;br /&gt;
*.osgx = svn:mime-type=text/xml&lt;br /&gt;
*.svg = svn:mime-type=text/svg+xml&lt;br /&gt;
*.txt = svn:mime-type=text/plain&lt;br /&gt;
*.vert = svn:mime-type=text/plain&lt;br /&gt;
*.xhtml = svn:mime-type=text/xml&lt;br /&gt;
*.xml = svn:mime-type=text/xml&lt;br /&gt;
*.xsl = svn:mime-type=text/xml&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These are all the text files that the hook script will check that the mime-type is set to a text format, though new text files will likely be added in the future.  These additions can either be to the user configuration file located at &amp;lt;code&amp;gt;~/.subversion/config&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;%USERPROFILE%\AppData\Roaming\Subversion\config&amp;lt;/code&amp;gt; in Windows) or, if a user configuration file is not set, to the global configuration file at &amp;lt;code&amp;gt;/etc/subversion/config&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;%APPDATA%\Subversion\config&amp;lt;/code&amp;gt; in Windows).&lt;br /&gt;
&lt;br /&gt;
==== Executable flag ====&lt;br /&gt;
&lt;br /&gt;
Another blocking message when attempting to commit files to FGAddon using the SVN tools is:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Adding         dash-set.xml&lt;br /&gt;
Transmitting file data .svn: E165001: Commit failed (details follow):&lt;br /&gt;
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:&lt;br /&gt;
&lt;br /&gt;
The svn:executable property is set on the files ['dash-set.xml'], aborting the&lt;br /&gt;
commit.&lt;br /&gt;
&lt;br /&gt;
The current policy is that no executable files are allowed in FGAddon.  Before&lt;br /&gt;
committing, please remove this property by typing 'svn propdel svn:executable&lt;br /&gt;
file_name' for all affected files.  Or to remove it recursively from all files&lt;br /&gt;
to be committed, in your aircraft directory type 'svn propdel svn:executable&lt;br /&gt;
-R'.&lt;br /&gt;
&lt;br /&gt;
To avoid the svn:executable property being set by your subversion client, on&lt;br /&gt;
GNU/Linux and Mac OS X systems simply make sure that the file's execute bit is&lt;br /&gt;
not set before adding the file to be committed.&lt;br /&gt;
&lt;br /&gt;
svn: E165001: Your commit message was left in a temporary file:&lt;br /&gt;
svn: E165001:    '/flightgear/repo_testing/svn-commit.tmp'&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This will probably only be seen on Mac OS X and GNU/Linux systems.  This message is printed by a pre-commit repository hook script that checks if the Subversion &amp;lt;code&amp;gt;svn:executable&amp;lt;/code&amp;gt; property is set and, if so, the commit is blocked.  This is a security measure, as no aircraft files should be executable.  To remove the problem, follow the instructions in the message and, using the command line tools, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propdel svn:executable -R&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then commit again, using the commit message saved in the &amp;lt;code&amp;gt;svn-commit.tmp&amp;lt;/code&amp;gt; file.  The message file name will be reported in the commit failure message, but check its contents first:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
cat svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And the reperform the commit:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn ci -F svn-commit.tmp&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Binary diffs ===&lt;br /&gt;
&lt;br /&gt;
{{warning|The incorrect setting or absence of the mime-type property on a binary file will result in a binary diff.}}&lt;br /&gt;
&lt;br /&gt;
When looking at the output of &amp;lt;code&amp;gt;svn diff&amp;lt;/code&amp;gt; (or &amp;lt;code&amp;gt;git diff&amp;lt;/code&amp;gt; if you are using git-svn) as well as when reading messages from the [[#FGAddon commitlog mailing list|FGAddon commitlog mailing list]], you may see a large number of unrecognisable characters.  This is the result of what is known as a binary diff, showing the binary file differences as if it were text.  Although this is not a issue for the operation of the repository, the situation is an aesthetic problem which makes it more difficult to perform a review of the changes.&lt;br /&gt;
&lt;br /&gt;
To fix the problem, firstly the binary files with the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property missing need to be identified.  The following subversion command can be used:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propget svn:mime-type &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As it can be tedious checking each file individually, the following Python script simplifies and automates the process to identify all binary files with a mime-type issue:&lt;br /&gt;
&lt;br /&gt;
{{collapsible script&lt;br /&gt;
| type   = Python 2/3 script&lt;br /&gt;
| title  = Find binary files with no &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property set.&lt;br /&gt;
| intro  = The following script is based on blacklisting text files.  Hence false positives are to be expected, and the blacklists can be expanded as needed.&lt;br /&gt;
| lang   = python&lt;br /&gt;
| script =&lt;br /&gt;
#! /usr/bin/env python&lt;br /&gt;
&lt;br /&gt;
from os import getcwd, walk&lt;br /&gt;
from os.path import join, splitext&lt;br /&gt;
from re import search&lt;br /&gt;
from subprocess import PIPE, Popen&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
skip_txt_file_seg = [&lt;br /&gt;
    'authors',&lt;br /&gt;
    'copying',&lt;br /&gt;
    'licen',&lt;br /&gt;
    'readme'&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
skip_txt_ext = [&lt;br /&gt;
    'ac',&lt;br /&gt;
    'css',&lt;br /&gt;
    'dat',&lt;br /&gt;
    'eff',&lt;br /&gt;
    'frag',&lt;br /&gt;
    'html',&lt;br /&gt;
    'json',&lt;br /&gt;
    'log',&lt;br /&gt;
    'nas',&lt;br /&gt;
    'osgx',&lt;br /&gt;
    'svg',&lt;br /&gt;
    'tex',&lt;br /&gt;
    'txt',&lt;br /&gt;
    'vert',&lt;br /&gt;
    'xhtml',&lt;br /&gt;
    'xml',&lt;br /&gt;
    'xsl'&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
skip_bin_prop = [&lt;br /&gt;
    'application/octet-stream',&lt;br /&gt;
    'application/pdf',&lt;br /&gt;
    'application/postscript',&lt;br /&gt;
    'application/x-dosexec',&lt;br /&gt;
    'application/x-gzip',&lt;br /&gt;
    'application/zip',&lt;br /&gt;
    'audio/x-wav',&lt;br /&gt;
    'image/gif',&lt;br /&gt;
    'image/jpeg',&lt;br /&gt;
    'image/png',&lt;br /&gt;
    'image/vnd.adobe.photoshop',&lt;br /&gt;
    'image/tiff',&lt;br /&gt;
    'image/x-ms-bmp',&lt;br /&gt;
    'image/x-xcf',&lt;br /&gt;
]&lt;br /&gt;
&lt;br /&gt;
# Walk through the directories.&lt;br /&gt;
for root, dirs, files in walk(getcwd()):&lt;br /&gt;
    # Loop over the files in the current directory.&lt;br /&gt;
    for file in files:&lt;br /&gt;
        # Skip known text files.&lt;br /&gt;
        skip = False&lt;br /&gt;
        for i in range(len(skip_txt_file_seg)):&lt;br /&gt;
            if search(skip_txt_file_seg[i], file.lower()):&lt;br /&gt;
                skip = True&lt;br /&gt;
        if skip:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # The file extension.&lt;br /&gt;
        file_path, ext = splitext(file)&lt;br /&gt;
        ext = ext[1:].lower()&lt;br /&gt;
&lt;br /&gt;
        # Skip known text file extensions.&lt;br /&gt;
        if ext in skip_txt_ext:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # The full file path.&lt;br /&gt;
        path = join(root, file)&lt;br /&gt;
&lt;br /&gt;
        # Query the file for svn:mime-type.&lt;br /&gt;
        cmd = 'svn propget svn:mime-type \&amp;quot;%s\&amp;quot;' % path&lt;br /&gt;
        pipe = Popen(cmd, shell=True, stdin=PIPE, stdout=PIPE, stderr=PIPE, close_fds=False)&lt;br /&gt;
        props = []&lt;br /&gt;
        for line in pipe.stdout.readlines():&lt;br /&gt;
            props.append(line.strip())&lt;br /&gt;
&lt;br /&gt;
        # Byte array conversion (Python3).&lt;br /&gt;
        for i in range(len(props)):&lt;br /&gt;
            if hasattr(props[i], 'decode'):&lt;br /&gt;
                props[i] = props[i].decode()&lt;br /&gt;
&lt;br /&gt;
        # Skip binary svn:mime-type values.&lt;br /&gt;
        if len(props) and props[0] in skip_bin_prop:&lt;br /&gt;
            continue&lt;br /&gt;
&lt;br /&gt;
        # Printout.&lt;br /&gt;
        if not len(props):&lt;br /&gt;
            print(&amp;quot;%s&amp;quot; % path)&lt;br /&gt;
        else:&lt;br /&gt;
            print(&amp;quot;%s    svn:mime-type=%s&amp;quot; % (path, props[0]))&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==== Fixing the problem ====&lt;br /&gt;
&lt;br /&gt;
As [[#Subversion_properties|git-svn cannot set or change]] the &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; property, a [[#Repository_checkout|svn checkout copy]] of the aircraft is required.  The property can then be set to the default Subversion binary mime-type with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; &amp;lt;file_name&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, the following set of shell commands can be used to automate the process:&lt;br /&gt;
{{collapsible script&lt;br /&gt;
| type   = Shell commands&lt;br /&gt;
| title  = Set specific &amp;lt;code&amp;gt;svn:mime-type&amp;lt;/code&amp;gt; values on a set of known binary files.&lt;br /&gt;
| intro = These shell commands will work on GNU/Linux or Mac OS X systems (or on Windows if using cygwin, or if a find command line tool is installed).  The list of file types here are those most commonly found in FGAddon.  To set the property on a list of binary files, type (or copy and paste):&lt;br /&gt;
| lang   = bash&lt;br /&gt;
| script =&lt;br /&gt;
find -iname &amp;quot;*.wav&amp;quot; -exec svn propset svn:mime-type &amp;quot;audio/x-wav&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.bmp*&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/x-ms-bmp&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.gif&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/gif&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.jpg&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/jpeg&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.png*&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/png&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.psd&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/vnd.adobe.photoshop&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.tif&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/tiff&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.xcf&amp;quot; -exec svn propset svn:mime-type &amp;quot;image/x-xcf&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.rgb*&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.au&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.*af&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.3ds&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.blend*&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.dds&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.od[gst]&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.onetoc2&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.xlsx&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/octet-stream&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.pdf&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/pdf&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.ps&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/postscript&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.gz&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/x-gzip&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.mdl&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/x-dosexec&amp;quot; {} \;&lt;br /&gt;
find -iname &amp;quot;*.zip&amp;quot; -exec svn propset svn:mime-type &amp;quot;application/zip&amp;quot; {} \;&lt;br /&gt;
| conc = Other binary files can safely be set to &amp;lt;code&amp;gt;&amp;quot;application/octet-stream&amp;quot;&amp;lt;/code&amp;gt;, the Subversion default for binary files.&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== SourceForge developer services ==&lt;br /&gt;
&lt;br /&gt;
The FlightGear project is hosted on the SourceForge open source infrastructure.  This developer services section will highlight some of the useful tools you can take advantage of.  SourceForge consists of two categories of services:&lt;br /&gt;
; Project infrastructure : The FlightGear project uses the project services of SourceForge.  These services are for standalone software projects.&lt;br /&gt;
; Developer infrastructure : These are services available to anyone with a SourceForge account, and are available via your SourceForge homepage and accessible to all.  This includes being able to create multiple version control repositories (svn, git, hg), wikis, forums, development teams, blogs, and ticket trackers (for bugs, support requests, tasks, etc.).&lt;br /&gt;
&lt;br /&gt;
Rather than creating a new project, any development for the FlightGear project should be based on the developer infrastructure.&lt;br /&gt;
&lt;br /&gt;
=== Developer git repository ===&lt;br /&gt;
&lt;br /&gt;
To set up your own remote git repository, here for developing the FGAddon fkdr1 aircraft:&lt;br /&gt;
* On your profile page at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/profile/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;, go to &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Add New&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Git&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set label to &amp;lt;code&amp;gt;fkdr1 FGAddon git-svn repository&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set the code path to &amp;lt;code&amp;gt;code-fkdr1&amp;lt;/code&amp;gt;.  The &amp;lt;code&amp;gt;code-*&amp;lt;/code&amp;gt; prefix is to differentiate this from the &amp;lt;code&amp;gt;forum-*&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;wiki-*&amp;lt;/code&amp;gt;, and other directories.&lt;br /&gt;
&lt;br /&gt;
The repository will be located at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/code-fkdr1/ci/master/tree/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=== Development teams ===&lt;br /&gt;
&lt;br /&gt;
If you and a group of friends would like to privately develop one of the FGAddon aircraft as a team, assuming that the you have contacted the original aircraft authors and the aircraft is not actively being developed, then you should create a SourceForge development team.  A team leader should be appointed to set this up under their SourceForge account.  Assuming you wish to develop the &amp;quot;ornithopter&amp;quot; aircraft, the steps are:&lt;br /&gt;
&lt;br /&gt;
* Go to &amp;lt;code&amp;gt;Personal tools&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;User Permissions&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Add a new group&amp;lt;/code&amp;gt; at the bottom.&lt;br /&gt;
* Set the name to &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt;, and save.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Add&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; group and add the SourceForge names of all your team members.&lt;br /&gt;
&lt;br /&gt;
After setting up a private repository in the team leader's account, as described below, then the development team should be set up for the repository.&lt;br /&gt;
&lt;br /&gt;
* Go to the repository under your SourceForge account.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Admin - &amp;lt;repository name&amp;gt;&amp;lt;/code&amp;gt;, then select &amp;lt;code&amp;gt;Permissions&amp;lt;/code&amp;gt;.&lt;br /&gt;
* In the &amp;lt;code&amp;gt;Write&amp;lt;/code&amp;gt; section, remove &amp;lt;code&amp;gt;Developer&amp;lt;/code&amp;gt; and add &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Save&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The development team will then have commit access to the private repository.&lt;br /&gt;
&lt;br /&gt;
=== Team communications ===&lt;br /&gt;
&lt;br /&gt;
To help with team development, the SourceForge infrastructure allows for multiple [https://sourceforge.net/p/forge/documentation/Discussion/ dedicated discussion forums] to be created.  This can either be within a SourceForge project or under a SourceForge users homepage.  This allows the team leader to create a forum dedicated solely to the development of the aircraft of interest.  Continuing with the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; example, the steps for the team leader are simple:&lt;br /&gt;
&lt;br /&gt;
* On your profile page at &amp;lt;span style=&amp;quot;color: blue&amp;quot;&amp;gt;&amp;lt;tt&amp;gt;&amp;lt;nowiki&amp;gt;https://sourceforge.net/u/&amp;lt;username&amp;gt;/profile/&amp;lt;/nowiki&amp;gt;&amp;lt;/tt&amp;gt;&amp;lt;/span&amp;gt;, go to &amp;lt;code&amp;gt;Personal tools&amp;lt;/code&amp;gt; -&amp;gt; &amp;lt;code&amp;gt;Admin&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Click on the &amp;lt;code&amp;gt;Tools&amp;lt;/code&amp;gt; option in the left hand menu.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Discussion&amp;lt;/code&amp;gt; in the &amp;lt;code&amp;gt;Click to install&amp;lt;/code&amp;gt; section.&lt;br /&gt;
* Change the label to &amp;lt;code&amp;gt;Ornithopter forum&amp;lt;/code&amp;gt;, and the path to &amp;lt;code&amp;gt;forum-ornithopter&amp;lt;/code&amp;gt;, for example.  The &amp;lt;code&amp;gt;forum-*&amp;lt;/code&amp;gt; prefix is to differentiate this from the &amp;lt;code&amp;gt;code-*&amp;lt;/code&amp;gt;, &amp;lt;code&amp;gt;wiki-*&amp;lt;/code&amp;gt;, and other directories.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Save&amp;lt;/code&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
More details are given on the [https://sourceforge.net/p/forge/documentation/Discussion/ SourceForge Discussion documentation].&lt;br /&gt;
&lt;br /&gt;
== Development scenarios ==&lt;br /&gt;
&lt;br /&gt;
=== Individual developer ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer and will use the native Subversion tools.}}&lt;br /&gt;
&lt;br /&gt;
This is by far the simplest development scenario and should be used in most cases.  If you are using the command line Subversion client, you can checkout an individual aircraft with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| path     = Aircraft/wrightFlyer1903&lt;br /&gt;
| post     = &lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is your SourceForge user name.  Alternatively you can checkout all aircraft with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| login    = &amp;lt;username&amp;gt;&lt;br /&gt;
| post     = flightgear-fgaddon&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
If you do not have commit access, type one of:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| path     = Aircraft/wrightFlyer1903&lt;br /&gt;
| post     = &lt;br /&gt;
}}&lt;br /&gt;
{{fgaddon co&lt;br /&gt;
| post     = flightgear-fgaddon&lt;br /&gt;
}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
To use the new local svn repository, see the [[#Subversion|subversion instructions]].&lt;br /&gt;
&lt;br /&gt;
=== Individual developer (git-svn) ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer and will use the git-svn tools.}}&lt;br /&gt;
&lt;br /&gt;
This is more complicated than using the native SVN tools, but can be useful without having FGAddon commit access, as multiple local commits can be made to be sent to the original aircraft authors or to the development mailing list/forum.  To clone the aircraft of choice into a new git repository, type:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is your infrastructure user name and &amp;lt;code&amp;gt;&amp;lt;aircraft&amp;gt;&amp;lt;/code&amp;gt; is the directory name in the FGAddon repository. This is valid whether or not you have commit permissions.&lt;br /&gt;
&lt;br /&gt;
To use the new local git repository, see the [[#Git-svn|git-svn instructions]] and [[#Deficiencies_of_git-svn|its deficiencies]].&lt;br /&gt;
&lt;br /&gt;
==== Upload to Sourceforge ====&lt;br /&gt;
&lt;br /&gt;
To share the local developments, the changes can be uploaded to a remote git repository on the SourceForge infrastructure.  For this, a [[#Developer_git_repository|developer git repository]] should first be set up under your SourceForge profile.  Then add this as a remote:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username&amp;gt;|type=git|repo=code-&amp;lt;aircraft&amp;gt;}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
And send the master branch where developments are located with:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git push --set-upstream origin master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The changes in the new repository will be visible via the web interface at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=&amp;lt;username&amp;gt;|repo=code-&amp;lt;aircraft&amp;gt;|branch=master}}}}}}| style=&amp;quot;color: blue&amp;quot;}}.&lt;br /&gt;
&lt;br /&gt;
=== Sending external git repository changes into FGAddon ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer with FGAddon commit access and wish to transfer the commits in a remote git repository into FGAddon using a temporary local git repository.}}&lt;br /&gt;
&lt;br /&gt;
Firstly clone the FGAddon aircraft into a local git-svn repository with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn clone|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
This will create a new local git repository linked to FGAddon via git-svn.  If the aircraft is new and not present in FGAddon, see the [[#New_aircraft|instructions for adding a new aircraft to FGAddon]].  Next, set up the remote git repository as a remote, and fetch it:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git remote add &amp;lt;name&amp;gt; &amp;lt;url&amp;gt;&lt;br /&gt;
git fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;url&amp;gt;&amp;lt;/code&amp;gt; is the URL of the remote git repository.  Finally make an ordered list of all hashes of the commits to be sent into FGAddon, from earliest to latest, and cherry-pick them into the git-svn master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the git-svn local repository should only have a single &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch and only consist of cherry-picking.  To see the changes queued for sending to FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then to send the changes to FGAddon, firstly pull in any remote changes, and send the commits:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The temporary local repository can then be deleted.&lt;br /&gt;
&lt;br /&gt;
=== Connecting an existing git repository to FGAddon ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  You are an individual developer or team leader with FGAddon commit access and wish to connect a pre-existing remote git repository with FGAddon to send all changes back to FGAddon.}}&lt;br /&gt;
&lt;br /&gt;
If a remote git repository containing a developed aircraft already exists, it is possible to connect it to the remote FGAddon repository using the git-svn tools.  The following uses the [[#Dedicated_FGAddon_branch|dedicated FGAddon branch technique]].  Firstly, set up the bridge to FGAddon using git-svn in the per-aircraft repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
{{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/&amp;lt;aircraft&amp;gt;|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Where &amp;lt;code&amp;gt;&amp;lt;aircraft&amp;gt;&amp;lt;/code&amp;gt; is the aircraft directory name in FGAddon.  Note that this step can be performed without commit access to FGAddon by using a read-only SVN URL instead, but then changes cannot be pushed back to FGAddon ([[#Synchronising|dcommitting]], as it is known in the git-svn terminology).  However, this allows upstream FGAddon changes to be integrated into the remote git repository, thus making it easy to prepare changes for submission for FGAddon inclusion using patches sent to the mailing list or sent via other channels.&lt;br /&gt;
&lt;br /&gt;
Now fetch the current state from the remote FGAddon repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The downloaded SVN history is in the remote branch &amp;lt;code&amp;gt;remotes/git-svn&amp;lt;/code&amp;gt;.  To commit changes to SVN you need a local branch that tracks this remote branch.  Create a local &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch that you will use to commit updates:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git branch fgaddon remotes/git-svn&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
After committing new stuff to the &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch, to push to FGAddon checkout the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch and update it from SVN in case someone else has touched the aircraft in the remote FGAddon repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Cherry-pick the new commits from &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; to &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; to preserve a linear history:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the changes queued for sending to FGAddon as either commits or a diff, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If everything looks ok, dcommit the local commits on the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch to send them to the remote FGAddon SVN repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Switch back to the master branch for local development:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To get changes from upstream you can either just download them with&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn fetch&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
or download them and rebase your &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch onto them:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Team development ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  All members of the team are acting as gatekeepers, and all commits are made directly to FGAddon, either using svn or git-svn.}}&lt;br /&gt;
&lt;br /&gt;
The simplest way to work as a team is for each developer to either have a [[#Individual developer|svn copy of FGAddon]] or a [[#Individual developer (git-svn)|git-svn copy of FGAddon]], and everyone commits directly to FGAddon.  Communication and coordination between the team members can be performed using a [[#Team_communications|team leader organised SourceForge forum]] or using the [http://forum.flightgear.org/ FlightGear forum].  In this scenario, the team needs to take the initiative and everyone apply for FGAddon commit access.&lt;br /&gt;
&lt;br /&gt;
=== Private team development (git-svn) ===&lt;br /&gt;
&lt;br /&gt;
{{Note|Development scenario:  One team leader is acting as the gatekeeper on a private git repository hosted on the in-house SourceForge infrastructure, using git-svn to push a fgaddon branch to FGAddon, with team members committing directly to the private git repository or making merge requests from their fork of the private repository.}}&lt;br /&gt;
&lt;br /&gt;
To keep everything in-house, the entire operation will be based on the official infrastructure and remote repositories under each user's SourceForge (SF) profile.  Note to the team leader - you must [https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#git-svn keep your git-svn history linear] (meaning that a [[#Dedicated_FGAddon_branch|dedicated FGAddon branch]] should be created and changes manually cherry-picked into this branch).  In the following, the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; aircraft will be used as an example.&lt;br /&gt;
&lt;br /&gt;
==== The team ====&lt;br /&gt;
&lt;br /&gt;
Firstly, the entire team should sign up for [[#SourceForge account|SourceForge accounts]].&lt;br /&gt;
&lt;br /&gt;
==== Team leader ====&lt;br /&gt;
&lt;br /&gt;
===== Private repository set up =====&lt;br /&gt;
&lt;br /&gt;
These steps are to be taken by the team leader.  In your SourceForge user profile, set up a [[#Developer_git_repository| git repository]] with the label &amp;lt;code&amp;gt;Ornithopter FGAddon git-svn repository&amp;lt;/code&amp;gt; and code path &amp;lt;code&amp;gt;code-ornithopter&amp;lt;/code&amp;gt;.  Then create a empty local git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ mkdir ornithopter&lt;br /&gt;
$ cd ornithopter&lt;br /&gt;
$ git init&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Link the empty repository to the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; aircraft directory in the remote FGAddon repository and pull it in with:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{fgaddon source|cmd=git svn init|protocol=svn+ssh|login=&amp;lt;username&amp;gt;|type=svn|path=Aircraft/ornithopter|full=1}}&lt;br /&gt;
$ git svn fetch&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; with your SF user name.  Set up a special git-svn branch for FGAddon gatekeeping and dcommitting changes back to the repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch fgaddon remotes/git-svn&lt;br /&gt;
$ git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
And pull in the &amp;lt;code&amp;gt;ornithopter&amp;lt;/code&amp;gt; from FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the current local git-svn repository setup, type:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch -vva&lt;br /&gt;
$ git remote -v&lt;br /&gt;
$ git svn info &lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then return to the master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, set up the remote git repository as a remote:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{sourceforge url|cmd=git remote add|opt=origin|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username&amp;gt;|type=git|repo=code-ornithopter}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
And send the master branch to the remote git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git push -u origin master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the new set up:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
$ git branch -vva&lt;br /&gt;
$ git remote -v&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The repository will be located at {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge url|user=&amp;lt;username&amp;gt;|repo=code-ornithopter|branch=master}}}}}}| style=&amp;quot;color: blue&amp;quot;}}.  Note that the git-svn information stored in the &amp;lt;code&amp;gt;.git/svn&amp;lt;/code&amp;gt; directory will not be pushed to remote SoureForge repository, and therefore the link back to FGAddon will only be present in the local copy of the team leader.  The git-svn link can be re-established at a later point if necessary.&lt;br /&gt;
&lt;br /&gt;
===== Team setup =====&lt;br /&gt;
&lt;br /&gt;
Set up a [[#Development teams|dedicated development team and grant them access to the git-svn repository]].&lt;br /&gt;
&lt;br /&gt;
===== Pushing to FGAddon =====&lt;br /&gt;
&lt;br /&gt;
Committing to FGAddon is for the local git repository of the team leader.  History must be linear in the fgaddon branch, so cherry-picking is the way to go.  This is from the [[#Individual developer (git-svn)|Individual developer (git-svn)]] section.  In the local git repository, switch to the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git checkout fgaddon&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pull in any changes which have occurred in FGAddon:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn rebase&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To see the commits in the &amp;lt;code&amp;gt;master&amp;lt;/code&amp;gt; branch which are not in the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch, type one of:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log HEAD..master&lt;br /&gt;
git log HEAD..master --pretty=oneline&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Manually select the commits to be sent to FGAddon and cherry-pick them:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 2&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 3&amp;gt;&lt;br /&gt;
...&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Or to cherry-pick a range of commits:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git cherry-pick &amp;lt;commit hash 1&amp;gt;^..&amp;lt;commit hash 8&amp;gt;&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then check what is to be sent:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git log git-svn..HEAD&lt;br /&gt;
git diff git-svn..HEAD&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Send the changes to FGAddon, send the git &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch changes to the remote git repository, and switch back to the master branch:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git svn dcommit&lt;br /&gt;
git push&lt;br /&gt;
git checkout master&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally merge in the git svn commits with their new hashes from the &amp;lt;code&amp;gt;fgaddon&amp;lt;/code&amp;gt; branch, and send it to the remote git repository:&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;bash&amp;quot;&amp;gt;&lt;br /&gt;
git merge fgaddon&lt;br /&gt;
git push&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Team members ====&lt;br /&gt;
&lt;br /&gt;
===== Working with the repository =====&lt;br /&gt;
&lt;br /&gt;
Each team member should make a clone of the private git repository:&lt;br /&gt;
{{#tag:syntaxhighlight|&lt;br /&gt;
$ {{sourceforge source|cmd=git clone|protocol=ssh|login=&amp;lt;username&amp;gt;|user=&amp;lt;username_leader&amp;gt;|type=git|repo=code-ornithopter|post=ornithopter|full=1}}&lt;br /&gt;
| lang = &amp;quot;sh&amp;quot;&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; with your SourceForge user name, and &amp;lt;code&amp;gt;&amp;lt;username_leader&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name of the team leader.&lt;br /&gt;
&lt;br /&gt;
===== Forking and merge requests =====&lt;br /&gt;
&lt;br /&gt;
Alternatively, each team member can fork the git repository under your SourceForge account:&lt;br /&gt;
* Go to {{#tag:span|{{#tag:tt|{{#tag:nowiki|{{sourceforge source|user=&amp;lt;username&amp;gt;|repo=code-ornithopter|branch=master|full=1}}}}}}| style=&amp;quot;color: blue&amp;quot;}}, where &amp;lt;code&amp;gt;&amp;lt;username&amp;gt;&amp;lt;/code&amp;gt; is the SourceForge user name of the team leader.&lt;br /&gt;
* Click on &amp;lt;code&amp;gt;Fork&amp;lt;/code&amp;gt;.&lt;br /&gt;
* Set the mount point to &amp;lt;code&amp;gt;code-ornithopter&amp;lt;/code&amp;gt; and change the label as you wish.&lt;br /&gt;
&lt;br /&gt;
Develop and push to your fork, then make merge requests by clicking on the &amp;lt;code&amp;gt;Request Merge&amp;lt;/code&amp;gt; button.&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:FlightGear]]&lt;br /&gt;
&lt;br /&gt;
[[de:FGAddon]]&lt;br /&gt;
[[en:FGAddon]]&lt;br /&gt;
[[fr:FGAddon]]&lt;br /&gt;
[[nl:FGAddon]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Template:Tip&amp;diff=117669</id>
		<title>Template:Tip</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Template:Tip&amp;diff=117669"/>
		<updated>2019-03-23T23:08:21Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;border: 1px solid #0c6; border-left-width: 10px; margin: 1em auto; width: {{{width|90%}}}; background-color: #e0ffe8; padding: 2px;&amp;quot;&lt;br /&gt;
| style=&amp;quot;padding-left:5px;&amp;quot;| '''&amp;lt;span class=&amp;quot;smallcaps&amp;quot; style=&amp;quot;font-variant:small-caps;&amp;quot;&amp;gt;{{LangSwitch&lt;br /&gt;
 | ca = Consell&lt;br /&gt;
 | de = Hinweis&lt;br /&gt;
 | en = Tip&lt;br /&gt;
 | es = Consejo&lt;br /&gt;
 | fr = Conseil&lt;br /&gt;
 | it = Suggerimento&lt;br /&gt;
}}&amp;lt;/span&amp;gt;'''&amp;amp;ensp; {{{1|Add message}}}&lt;br /&gt;
|}&amp;lt;noinclude&amp;gt;{{Informative template |1=&lt;br /&gt;
__NOTOC__&lt;br /&gt;
== Goal ==&lt;br /&gt;
Use this template to add a helpful tip.&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
 {{obr}}'''tip'''{{!}}message{{!}}''width=''{{cbr}}&lt;br /&gt;
&lt;br /&gt;
; width : Width of the messagebox, preferably as a percentage of the width of the page content. Defaults to 90%.&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{tip|If the main menu is hidden press {{key press|F10}}.}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
{{tip|If the main menu is hidden press {{key press|F10}}.}}&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{tip|If the main menu is hidden press {{key press|F10}}.|width=20%}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
{{tip|If the main menu is hidden press {{key press|F10}}.|width=20%}}&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
Adding external links must be done like below. Specifically note the '''1{{=}}'''.&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{note|1=You can add your screenshots to a forum post.  For instructions see [http://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=8873 this forum sticky].}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{tip|1=You can add your screenshots to a forum post.  For instructions see [http://forum.flightgear.org/viewtopic.php?f=19&amp;amp;t=8873 this forum sticky].}}&lt;br /&gt;
&lt;br /&gt;
== Related templates ==&lt;br /&gt;
=== Messagebox templates ===&lt;br /&gt;
* {{tl|warning}} &amp;amp;ndash; When a virtual aircraft might crash or when real equipment or ones health might be jeopardized&lt;br /&gt;
* {{tl|caution}} &amp;amp;ndash; When there might be damages to the virtual aircraft or to real equipment&lt;br /&gt;
* {{tl|note}} &amp;amp;ndash; For important notes&lt;br /&gt;
&lt;br /&gt;
=== Inline italic templates ===&lt;br /&gt;
{{inote|If there is a need for a warning use a messagebox template instead.}}&lt;br /&gt;
* {{tl|icaution}}&lt;br /&gt;
* {{tl|inote}}&lt;br /&gt;
* {{tl|itip}}&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Messagebox templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Translation_requests&amp;diff=117668</id>
		<title>Translation requests</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Translation_requests&amp;diff=117668"/>
		<updated>2019-03-23T23:01:31Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Open translation requests */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Warning|There is currently a SQL database bug that prevents non-latin characters from being in the page title.  If you edit the page, you will see &amp;quot;''A database query error has occurred. This may indicate a bug in the software.''&amp;quot;.  If you encounter this, please switch to ''mobile view'' to edit the page (see the links at the bottom of the page). Note that adding or editing external links will throw errors in mobile view.}}&lt;br /&gt;
&lt;br /&gt;
Please post your translation requests here, so that other people can more easily track what's going on, hopefully avoiding duplicate efforts.&lt;br /&gt;
&lt;br /&gt;
*How to translate is described here: [[Help:Translate]].&lt;br /&gt;
&lt;br /&gt;
== Currently work in progress ==&lt;br /&gt;
*Please see table below. &lt;br /&gt;
*Please add {{tl|BeingTranslated}} to articles that are being translated, remove this when you are finished.&lt;br /&gt;
*Please add {{tl|UpdateTranslation}} to articles that have an up-to-date English version but an out-of-date local version.&lt;br /&gt;
*Also look at [[:Category:Articles being translated]].&lt;br /&gt;
&lt;br /&gt;
== Open translation requests ==&lt;br /&gt;
Check out [[Special:Statistics]] for the most viewed pages:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align: center&amp;quot;&lt;br /&gt;
  ! [[#Language map|en]]&lt;br /&gt;
  ! [[#Language map|ar]] &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  ! [[#Language map|ca]] &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  ! [[#Language map|de]] &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  ! [[#Language map|el]] &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  ! [[#Language map|es]] &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  ! [[#Language map|fa]] &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  ! [[#Language map|fi]] &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  ! [[#Language map|fr]] &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  ! [[#Language map|it]] &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  ! [[#Language map|ja]] &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  ! [[#Language map|nl]] &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  ! [[#Language map|pl]] &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  ! [[#Language map|pt]] &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  ! [[#Language map|ru]] &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  ! [[#Language map|sl]] &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  ! [[#Language map|sr]] &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  ! [[#Language map|sv]] &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  ! [[#Language map|th]] &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  ! [[#Language map|zh]] &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|- style=&amp;quot;font-weight:bold&amp;quot;&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Help:Translate]]&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Help:Traduir}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Help:Übersetzen}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Help:Traducir}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Help:Traduire}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:Help:Tradurre}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Help:Vertalen}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pl:Pomoc:Tłumaczenie}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Help:Traduzir}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ru:Справка:Перевод}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:sv:Hjälp:Översättning}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Translate}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|- style=&amp;quot;font-weight:bold&amp;quot;&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Main Page]]&lt;br /&gt;
  || {{progressbar|90|10|link=:ar:Main_Page}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Portada}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Hauptseite}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=:el:Αρχική}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Portada}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|80|10|link=:fa:Persian}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fi:Etusivu}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Accueil}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:Pagina principale}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|80|10|link=:ja:トップページ}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Hoofdpagina}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pl:Strona główna}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Página principal}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ru:Заглавная страница}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|80|10|link=:sl:Main Page}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|80|10|link=:sr:Main Page}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Main Page}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|80|10|link=:th:Main Page}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:zh:首页}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Aircraft]]&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Aeronau}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Flugzeuge}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Aeronaves}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fi:Lentokoneet}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Avions}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:Aerei}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:nl:Luchtvaartuigen}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Aeronaves}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ru:Самолет}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Aircraft}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Altitude]]&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Altitud}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|90|10|link=:de:Flughöhe}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Altitud}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Altitude}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Vlieghoogte}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ru:Высота полёта}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Altitude}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Cessna 172P]]&lt;br /&gt;
  || {{progressbar|90|10|link=:ar:Cessna 172P}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Cessna 172P}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Cessna 172P}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|80|10|link=:es:Cessna 172P}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:fr:Cessna 172}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|90|10|link=:nl:Cessna 172}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ru:Cessna 172P}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Cessna 172P}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=:zh:Cessna 172P}}&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[FGAddon]]&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|40|10|link=:ca:FGAddon}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:de:FGAddon}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:FGAddon}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:FGAddon}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FGAddon}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[FlightGear]]&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:FlightGear}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:FlightGear}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:FlightGear}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:FlightGear}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:FlightGear}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:nl:FlightGear}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pl:FlightGear}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:FlightGear}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[FlightGear hangars]]&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Hangars de Flightgear}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|90|10|link=:es:Hangares_Flightgear}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|90|10|link=:fr:FlightGear hangars}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear hangars}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[FlightGear Launch Control]]&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:FlightGear Launch Control}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:FlightGear Launch Control}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:FlightGear Launch Control}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=FlightGear Launch Control}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Flying the helicopter]]&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Fliegen mit dem Helikopter}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Volando el helicoptero}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Piloter l'hélicoptère}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:Pilotare un elicottero}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Vliegen met de helicopter}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:pl:Lot śmigłowcem}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:pt:Voando de Helicóptero}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Flying the helicopter}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Frequently asked questions]]&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:FAQ}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Preguntas frecuentes}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Foire aux questions}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:Domande_frequenti}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:veel gestelde vragen}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pl:FAQ}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:pt:FAQ}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=:ru:ЧаВо}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Frequently asked questions}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Howto:Install scenery]]&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Szenerie installieren}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Instalación de escenarios}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Installer une scène}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:it:Come fare:Installare scenari}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Scenery_installeren}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=:pl:Instalowanie scenerii}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Instalando Cenário}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Install scenery}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Howto:Multiplayer]]&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Howto:Multiplayer}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Howto:Multijugador}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Howto:Multijoueur}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:it:Come fare:Multiplayer}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Howto:Multiplayer}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pl:Konfiguracja trybu multiplayer}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Tutorial de Multiplayer}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Howto:Multiplayer}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Help:Gallery of messagebox templates|Messagebox templates]] &amp;lt;!-- This row covers all the messagebox templates shown in the gallery! --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|20|10|link=:de:Help:Messagebox Vorlagengalerie}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|20|10|link=:fr:Help:Galerie de modèles de messagebox}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Help:Gallery of messagebox templates}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[New to FlightGear]]&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Nou a FlightGear}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:de:Neu bei FlightGear}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Nuevo en FlightGear}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Nouveau sur flightgear}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:it:Nuovo per FlightGear}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Nieuw bij FlightGear}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Novo no FlightGear}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=New to FlightGear}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:zh:FlightGear新手}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Portal:User]]&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:ca:Portal:Usuari}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Portal:Benutzer}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:es:Portal:Usuario}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:fr:Portal:Utilisateur}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:it:Portal:Utente}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Portal:Gebruiker}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:pl:Portal:Dla użytkowników}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Portal:User}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:zh:Portal:用户}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | {{obr}}[[Template:infobox aircraft#Full_translation|infobox aircraft]]{{cbr}}&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|10|10|link=Template:infobox aircraft#Full_translation}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | {{tl|Main page/Languages}}&lt;br /&gt;
  || {{progressbar|50|10|link=Template:Main_page/Languages}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=Template:Main_page/Languages}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=Template:Main_page/Languages}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=Template:Main_page/Languages}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=Template:Main_page/Languages}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Template:Main_page/Languages}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=Template:Main_page/Languages}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=Template:Main_page/Languages}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[TerraSync]]&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:de:TerraSync}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:es:TerraSync}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|50|10|link=:fr:TerraSync}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Terrasync}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=TerraSync}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | [[Troubleshooting problems]]&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:de:Problemlösung}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:es:Resolviendo_problemas}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:fr:Troubleshooting Problems}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:nl:Problemen oplossen}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|100|10|link=:pt:Resolvendo Problemas}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=Troubleshooting problems}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
  | style=&amp;quot;text-align: left&amp;quot; | New article&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- العربية --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Català --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Deutsch --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Ελληνικά --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Español --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- فارسی --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Suomi --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Français --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Italiano --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- 日本語 --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Nederlands --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Polski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Português --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Русский --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Slovenščina --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Српски / srpski --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- Svenska --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- ไทย --&amp;gt;&lt;br /&gt;
  || {{progressbar|0|10|link=}} &amp;lt;!-- 中文 --&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
* Please help to translate any pages that are not complete.  Carefully check the history of the article to be sure that someone else is not currently translating the article.&lt;br /&gt;
* For completed entries, please compare to the English version of the article to make sure that new content has been translated.&lt;br /&gt;
* English is the primary language of this wiki.  Content present in a translation but not in the English article will be, with time, deleted.  Always add new content to both the translation and the original English.&lt;br /&gt;
* A translated page must be linked to from all other translated pages.&lt;br /&gt;
* Help and keep this page up-to-date please (so to avoid double work).&lt;br /&gt;
&lt;br /&gt;
=== Language map ===&lt;br /&gt;
&lt;br /&gt;
Here is an alphabetically ordered language map:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align: center&amp;quot;&lt;br /&gt;
! ISO language code&lt;br /&gt;
! Name&lt;br /&gt;
! English name&lt;br /&gt;
|-&lt;br /&gt;
| en || English          || English&lt;br /&gt;
|-&lt;br /&gt;
| ar || العربية          || Arabic&lt;br /&gt;
|-&lt;br /&gt;
| ca || Català           || Catalan&lt;br /&gt;
|-&lt;br /&gt;
| de || Deutsch          || German&lt;br /&gt;
|-&lt;br /&gt;
| el || Ελληνικά         || Greek&lt;br /&gt;
|-&lt;br /&gt;
| es || Español          || Spanish&lt;br /&gt;
|-&lt;br /&gt;
| fa || فارسی            || Persian&lt;br /&gt;
|-&lt;br /&gt;
| fi || Suomi            || Finnish&lt;br /&gt;
|-&lt;br /&gt;
| fr || Français         || French&lt;br /&gt;
|-&lt;br /&gt;
| it || Italiano         || Italian&lt;br /&gt;
|-&lt;br /&gt;
| ja || 日本語           || Japanese&lt;br /&gt;
|-&lt;br /&gt;
| nl || Nederlands       || Dutch&lt;br /&gt;
|-&lt;br /&gt;
| pl || Polski           || Polish&lt;br /&gt;
|-&lt;br /&gt;
| pt || Português        || Portuguese&lt;br /&gt;
|-&lt;br /&gt;
| ru || Русский          || Russian&lt;br /&gt;
|-&lt;br /&gt;
| sl || Slovenščina      || Slovene&lt;br /&gt;
|-&lt;br /&gt;
| sr || Српски / srpski  || Serbian&lt;br /&gt;
|-&lt;br /&gt;
| sv || Svenska          || Swedish&lt;br /&gt;
|-&lt;br /&gt;
| th || ไทย              || Thai&lt;br /&gt;
|-&lt;br /&gt;
| zh || 中文             || Chinese&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
[[Category:Contribution requests]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=FlightGear_hangars&amp;diff=117667</id>
		<title>FlightGear hangars</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=FlightGear_hangars&amp;diff=117667"/>
		<updated>2019-03-23T23:00:30Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;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.&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{{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.}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Official FGAddon hangar ==&lt;br /&gt;
The [[FGAddon|FGAddon hangar]] is the official FlightGear hangar.&lt;br /&gt;
&lt;br /&gt;
=== Aircraft downloads ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=FGAddon]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Aircraft development ===&lt;br /&gt;
The [[FGAddon]] version controlled repository contains in-development aircraft as well as aircraft tagged for FlightGear 3.4 and higher stable releases.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=FGAddon Hangar}} The Subversion version controlled repository for the official FlightGear aircraft on the SourceForge infrastructure, see [[FGAddon]] for details.&lt;br /&gt;
* {{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&amp;amp;t=24045 announcement topic on the forum]&lt;br /&gt;
&lt;br /&gt;
=== Liveries ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database]&lt;br /&gt;
&lt;br /&gt;
== Third party sites ==&lt;br /&gt;
=== Aircraft catalogues ===&lt;br /&gt;
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.  See the [[hangar catalog]] page for all details on creating your own ''catalog.xml'' file.&lt;br /&gt;
&lt;br /&gt;
=== Aircraft hangars ===&lt;br /&gt;
These are links where you can download individual planes manually.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Description&lt;br /&gt;
! [[Hangar catalog|Catalog URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| 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].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Finished aircraft will be uploaded to FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Developing Pipistrel aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Scenarios, skins, film inspired aerospace vehicles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Misc. projects.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]&lt;br /&gt;
| Spanish site.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, scenario.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Blog, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Flightgear Flight Sim Military Community&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Many Brazilian aircraft articles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models &amp;amp; liveries.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Old Hangars ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Livery/Scenery hangars ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Other FlightGear repositories/mirrors ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Related content ==&lt;br /&gt;
* [[Table of models]]&lt;br /&gt;
* [[Aircraft]] - [[Helicopter]] - [[Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[ca:Hangars de FlightGear]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Fr/FlightGear_hangars&amp;diff=117666</id>
		<title>Fr/FlightGear hangars</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Fr/FlightGear_hangars&amp;diff=117666"/>
		<updated>2019-03-23T23:00:14Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{cleanup}}&lt;br /&gt;
&lt;br /&gt;
''Consultez les [[Links|Liens]] pour une liste complète de contenu relatif à FlightGear sur des sites externes''&lt;br /&gt;
&lt;br /&gt;
FlightGear propose des [[Fr/Avions|Avions]] ainsi que d'autres contenus présents sur des hangars tierces, certain étant compatible avec le GPL et incluant également les distributions officielles, tandis que d'autres sont indépendants. Certaines version d'avions requiert des kits particuliers du à leur version en développement afin d'être utilisable dans les dernières version de FlightGear. &lt;br /&gt;
&lt;br /&gt;
Alors attention à l'utilisation de ces liens! &lt;br /&gt;
&lt;br /&gt;
== Hangars officiels ==&lt;br /&gt;
=== Avions ===&lt;br /&gt;
Le Hangar d'aéronef officiel est [[Fr/FGAddon|FGAddon]].  Pour chaque version de FlightGear, ces avions sont marqués et des téléchargements officiels fournis:&lt;br /&gt;
&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-6/ FlightGear Official 3.6 Hangar]{{dead link}} (release [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|cancelled]])&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-4/ FlightGear Official 3.4 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-2/ FlightGear Official 3.2 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-0/ FlightGear Official 3.0 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-12/ FlightGear Official 2.12 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-2-10-filterable/ FlightGear Official 2.10 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-8/ FlightGear Official 2.8 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-6/ FlightGear Official 2.6 Hangar]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-4/ FlightGear Official 2.4 Hangar] (ancien site)&lt;br /&gt;
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ FlightGear Official 2.0 Hangar] (ancien site)&lt;br /&gt;
&lt;br /&gt;
==== Développement d’aéronef ====&lt;br /&gt;
Le dépôt de gestion de versions [[Fr/FGAddon|FGAddon]] contient les aéronefs en développement, ainsi que des avions marqués pour les versions de FlightGear dès 3.4.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=FGAddon Hangar}} Le dépôt de gestion de versions Subversion pour les aéronefs officielles FlightGear sur l'infrastructure SourceForge.  Voyez [[Fr/FGAddon|FGAddon]] pour plus de détails.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Old fgdata Hangar}} L'archive Gitorious des aéronefs officiel, migrés vers l'Internet Archive à fins d'archivage et de préservation de l'histoire.  Les aéronefs ont été migrés vers [[Fr/FGAddon|FGAddon]] en Septembre 2014.  Pour plus de détails, voir la [[FlightGear Newsletter September 2014#Aircraft moved to SVN|September 2014 newsletter announcement]] et l'[http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 annonce du topic sur le forum].&lt;br /&gt;
&lt;br /&gt;
=== Livrées ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database]&lt;br /&gt;
&lt;br /&gt;
== Sites non-officiels ==&lt;br /&gt;
=== Hangars à avions ===&lt;br /&gt;
* [http://fg-acjza.wix.com/hangar/ ACJZA Hangar] (Terre, Mer, Air)&lt;br /&gt;
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] avec [http://github.com/andgi aircraft repositories at GitHub].&lt;br /&gt;
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (Boeing 707-3J9C et 707-320C, 777-200LR).&lt;br /&gt;
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (&amp;amp; a YASim intro)&lt;br /&gt;
* [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)&lt;br /&gt;
* [http://fgnl.freehostia.com/ Gijs Hangar] (Aircraft, Liveries, Scenery, Vehicles)&lt;br /&gt;
* [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar] (JA-37, scenario)&lt;br /&gt;
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)&lt;br /&gt;
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (275+ avions originaux)&lt;br /&gt;
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (scenarios, skins, film inspirés de véhicules aérospatiaux) &lt;br /&gt;
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (misc. projects)&lt;br /&gt;
* [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.&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://www.theJabberwocky.net/ JWOCKY'S Flying Site] - où des choses étranges se produisent&lt;br /&gt;
* [http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar] (avions classiques)&lt;br /&gt;
* [http://marc-kraus.de/ Lake of Constance Hangar] Série d'avions de qualité signé Marc Kraus de Friedrichshafen Home de &amp;quot;The Dornier Museum&amp;quot;.&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flightgear.bplaced.de/ longfly's hangar] (pas seulement allemand!)&amp;lt;/s&amp;gt; {{dead link|2014-01}}&lt;br /&gt;
** &amp;lt;s&amp;gt;[http://flightgear.bplaced.de/filemanager/aircraft-list/index.html list of all aircrafts]&amp;lt;/s&amp;gt; (en développement) {{dead link|2014-01}}&lt;br /&gt;
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)&lt;br /&gt;
* [http://theomegahangar.flymerlion.org/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)&lt;br /&gt;
* [http://pattenflightgear.wifeo.com/avions.php  FG 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...) &lt;br /&gt;
* [http://pjedvaj.wordpress.com/ pjedvaj's Hangar] (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
* [http://presteshangar.wikidot.com/start Prestes Hangar] (many Brazilian aircraft articles)&lt;br /&gt;
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)&lt;br /&gt;
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (models &amp;amp; liveries)&lt;br /&gt;
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
* [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]  (newer 2.0 versions)&lt;br /&gt;
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)&lt;br /&gt;
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)&lt;br /&gt;
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]&lt;br /&gt;
* [http://www.fgpipistrel.org/ FG Pipistrel Hangar] Developing Pipistrel Aircraft&lt;br /&gt;
&lt;br /&gt;
=== Vieux hangars ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* {{gitorious source|text=Airbus Aircraft Development Git}} (A320, A330, A340-300, A380 - différents auteurs, voyez les projets sur &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, et more)&lt;br /&gt;
* [http://pagesperso-orange.fr/GRTux/tux/index-en.html GRTux Hangar] (28+ avions et add-ons) (dernière mise à jour en 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (quelques avions bien réalisés)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (format blog)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (pour FGFS 0.7.8, dernière mise à jour en 2002) &lt;br /&gt;
&lt;br /&gt;
=== Hangars de Livrées/Scenes ===&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
&lt;br /&gt;
=== Pages internet, blogs, etc. ===&lt;br /&gt;
* [http://www.jaunty.bplaced.net/flightgear/index.php A small FlightGear page]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.flightgeararg.com.ar/ Argentina Flightgear Community Portal]&amp;lt;/s&amp;gt;{{dead link|2013-01}}&lt;br /&gt;
* [http://daveshangar.blogspot.com/ Dave's Hangar Blog]&lt;br /&gt;
* [http://helldiversquadron.wordpress.com/ Helldiver Squadron Offensive Tactical Force Homepage]&lt;br /&gt;
* [http://djrick1.wix.com/grupofgbr Grupo FGBR Brazilian Portal] (Broken site - only accesible with flash player)&lt;br /&gt;
* [http://flightgearblog.blogspot.com/ FlightGear Blog] (dernier post en décembre 2008)&lt;br /&gt;
* [http://flightgear2009.blogspot.com/ FlightGear Brasil 2009]&lt;br /&gt;
* [http://geoffmclane.com/fg/index.htm FlightGear Build Centre]&lt;br /&gt;
* [http://www.flightgearcanada.ca/ FlightGear Canada] (Pour toute les canadiens de FlightGear)&lt;br /&gt;
* [http://flightgearcorner.tk The FlightGear Corner] (News, Downloads, Tutorials et plus)&lt;br /&gt;
* [http://www.fguk.eu/ FlightGear United Kingdom] &lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://www.emmerich-j.de/FGFS/index.html jomo's FlightGear Homepage]&lt;br /&gt;
* [http://flightgear.mxchange.org/ Quix0r's FlightGear Website] Simple tutorials and fgdata.bundle&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://tehwarlock.tk/ Tehwarlock Blog]&amp;lt;/s&amp;gt;{{dead link|2012-04}}&lt;br /&gt;
* [http://www.vivefg.org/ Vive FlightGear!] Avions, scenes, manuels et forum&lt;br /&gt;
&lt;br /&gt;
=== Autres dépositaire/mirroirs FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery)&lt;br /&gt;
&lt;br /&gt;
== Autres contenues ==&lt;br /&gt;
* [[Fr/Table_des_modèles|Table des modèles]]&lt;br /&gt;
* [[Fr/Avions|Avions]] - [[Fr/Helicoptere|Hélicoptère]] - [[Fr/Vehicules|Véhicules]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[ca:Hangars de FlightGear]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Es/Hangares_Flightgear&amp;diff=117665</id>
		<title>Es/Hangares Flightgear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Es/Hangares_Flightgear&amp;diff=117665"/>
		<updated>2019-03-23T23:00:01Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{cleanup}}&lt;br /&gt;
&lt;br /&gt;
: ''Para otro contenido distinto de aviones y libreas ver [[Links|Enlaces]]''&lt;br /&gt;
&lt;br /&gt;
FlightGear cuenta con [[aircraft|aeronaves]] y otro contenido disponible desde hangares de terceros, algunos de los cuales son compatibles con GPL y también están incluidos en distribuciones oficiales, mientras que otros son independientes. Las versiones de las aeronaves van desde las que requieren una versión de desarrollo a las compatibles con la última versión principal o a las que requieren una versión anterior.&lt;br /&gt;
&lt;br /&gt;
¡Ten cuidado con los links externos! &lt;br /&gt;
&lt;br /&gt;
== Hangares oficiales ==&lt;br /&gt;
=== Aeronaves ===&lt;br /&gt;
&lt;br /&gt;
==== Versiones estables ====&lt;br /&gt;
&lt;br /&gt;
El hangar oficial de aeronavees se conoce como [[FGAddon]. Para cada versión de Flightgear estas aeronaves son etiquetadas y se proporcionan descargas oficiales:&lt;br /&gt;
&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-6/ Hangar oficial FlightGear 3.6]{{dead link}} (versión [[FlightGear Newsletter November 2015#FlightGear v3.6 canceled|cancelada]])&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-4/ Hangar oficial FlightGear 3.4]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-2/ Hangar oficial FlightGear 3.2]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v3-0/ Hangar oficial FlightGear 3.0]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-12/ Hangar oficial FlightGear 2.12]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-2-10-filterable/ Hangar oficial FlightGear 2.10]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-8/ Hangar oficial FlightGear 2.8]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-6/ Hangar oficial FlightGear 2.6]&lt;br /&gt;
* [http://www.flightgear.org/download/aircraft-v2-4/ Hangar oficial FlightGear 2.4] (Sitio legal)&lt;br /&gt;
* [http://www.flightgear.org/Downloads/aircraft-2.0.0/ Hangar oficial FlightGear 2.0] (Sitio legal)&lt;br /&gt;
&lt;br /&gt;
==== Desarrollo de aeronaves ====&lt;br /&gt;
&lt;br /&gt;
El repositorio controlado de versiones [[FGAddon]] contiene aeronaves en desarrollo así como aeronaves etiquetadas para versiones estables de Flightgear 3.4 y superiores.&lt;br /&gt;
&lt;br /&gt;
* [{{fgaddon url}} FGAddon Hangar] El repositorio controlado de versiones Subversion para los aviones oficiales de Flightgear en la infraestructura de SourceForge, ver [[FGAddon]] para detalles.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Old fgdata Hangar}} La ubicación Gitorious de los aviones oficiales, migrada desde [https://archive.org/ Internet Archive] con fines de archivo y conservación de la historia. Los aviones fueron migrados a [[FGAddon]] en septiembre de 2014. Para más detalles ver el [[FlightGear Newsletter September 2014#Aircraft moved to SVN|anuncio del newsletter de septiembre de 2014]] y el anuncio [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045] en el foro.&lt;br /&gt;
&lt;br /&gt;
=== Libreas ===&lt;br /&gt;
* [http://liveries.flightgear.org Base de datos de libreas FlightGear]&lt;br /&gt;
&lt;br /&gt;
== Sitios de terceros ==&lt;br /&gt;
=== Hangares de aeronaves ===&lt;br /&gt;
* [http://www.gidenstam.org/FlightGear/Airships/ Anders Lighter-than-air Hangar] con estos y adicionales [http://github.com/andgi repositorios de aviones en GitHub].&lt;br /&gt;
* [http://andinogonthaeler.wordpress.com/ Andino's Hangar] (A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C).&lt;br /&gt;
* [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar] (Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81) (&amp;amp; a YASim intro)&lt;br /&gt;
* [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
&amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
* [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon] (para distribución [[Git]] y desarrollo de aviones FG | con [http://www.thejabberwocky.net/ forum] | Repositorios individuales de aeronaves)&lt;br /&gt;
* [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
* [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar] (FR) (Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more)Hangar&lt;br /&gt;
* [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine] (Aermacchi MB339 Frecce Tricolori)&lt;br /&gt;
* [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar] (275+ aviones originales, la mayoría de los cuales están mantenidos en [[FGAddon]])&lt;br /&gt;
* [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar] (escenarios, skins, vehículos aeroespaciales inspirados en películas) &lt;br /&gt;
* [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar] (varios proyectos)&lt;br /&gt;
* [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar] (español)&lt;br /&gt;
* [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar] Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; y ADFX-02 Morgan, un avión ficticio.&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar] (JA-37, escenario)&lt;br /&gt;
* [http://marc-kraus.de/ Lake of Constance Hangar] Quality Signature Series Aircrafts por Marc Kraus desde Friedrichshafen casa del Museo Dornier.&lt;br /&gt;
* [http://longfly.square7.ch longfly's hangar]&lt;br /&gt;
* [http://nickfg.blogspot.com/ Nick's FlightGear Hangar] (Blog, CRJ-200)&lt;br /&gt;
* [http://theomegahangar.flymerlion.org/ Omega Hangar] (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar] (Cap 10b, Robin DR400 JSBSim, Douglas DC-3 C47, Tecnam P92 Echo...)&lt;br /&gt;
* [http://pattenflightgear.wifeo.com/avions.php  FG 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...) &lt;br /&gt;
* [http://www.fgpipistrel.org/ FG Pipistrel Hangar] Desarrollando aviones Pipistrel&lt;br /&gt;
* [http://pjedvaj.wordpress.com/ pjedvaj's Hangar] (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
* [http://presteshangar.wikidot.com/start Prestes Hangar] (varios artículos de aviones brasileño)&lt;br /&gt;
* [http://riktov.synthasite.com/ Riktov's FlightGear Hangar] (BN-2 Islander, Giant Marshmallow Man)&lt;br /&gt;
* [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar] (modelos &amp;amp; libreas)&lt;br /&gt;
* [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
* [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]  (versiones más nuevas que 2.0)&lt;br /&gt;
* [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear] (A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11)&lt;br /&gt;
* [http://vicmar.weebly.com/ VicMar] (Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack)&lt;br /&gt;
* [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar: Douglas DC-8]&lt;br /&gt;
&lt;br /&gt;
=== Viejos hangares ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Tierra, Mar, Aire)&lt;br /&gt;
* {{gitorious source|text=Airbus Aircraft Development Git}} (A320, A330, A340-300, A380 - varios autores)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, y mar)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (unos pocos aviones bien hechos)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (formato blog)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (última actualización 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (avión clásico)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (para FGFS 0.7.8, última actualización 2002)&lt;br /&gt;
&lt;br /&gt;
=== Hangares libreas/escenarios ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Otro sitio de libreas&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* [http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Proyectos de escenarios, libreas)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ libreas &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (libreas, escenarios)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Vehiculos ===&lt;br /&gt;
* [http://ausdkunst.wix.com/kerdigarage Kerdigarage]&lt;br /&gt;
&lt;br /&gt;
=== Otros repositorios/espejos FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://www.unitedfreeworld.com/ Unitedfreeworld] (escenarios, modelos de avión y libreas)&lt;br /&gt;
&lt;br /&gt;
== Contenido relacionado ==&lt;br /&gt;
* [[Table of models|Tabla de modelos]]&lt;br /&gt;
* [[Aircraft|Avión]] - [[Helicopter|Helicóptero]] - [[Vehicle|Vehículo]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[ca:Hangars de FlightGear]]&lt;br /&gt;
[[en:Flightgear_hangars]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_Flightgear&amp;diff=117664</id>
		<title>Ca/Hangars de Flightgear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_Flightgear&amp;diff=117664"/>
		<updated>2019-03-23T22:59:43Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: Catalanoic moved page Ca/Hangars de Flightgear to Ca/Hangars de FlightGear: better&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Ca/Hangars de FlightGear]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117663</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117663"/>
		<updated>2019-03-23T22:59:42Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: Catalanoic moved page Ca/Hangars de Flightgear to Ca/Hangars de FlightGear: better&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
Si un hangar proporciona un fitxer de [[hangar catalog|catàleg URL]] (catalog.xml), es pot afegir al QtLauncher de FlightGear per mostrar tots els avions d'aquest hangar.  Vegeu la pàgina de [[hangar catalog|catàleg d'hangar]] per a tots els detalls sobre com crear el vostre propi fitxer ''catalog.xml''.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
Aquests són enllaços on podeu descarregar avions individuals manualment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Descripció&lt;br /&gt;
! [[hangar catalog|Catàleg URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| Amb U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships i ZF free balloon i aeronaus addicionals als [http://github.com/andgi?tab=repositories repositoris d’aeronaus d’Anders a GitHub].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C i 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Les aeronaus finalitzades seran pujades a FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Desenvolupament d'aeronaus Pipistrel.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| Distribució en [[Git]] i desenvolupament d'aeronaus per a FG {{!}} amb [http://www.thejabberwocky.net/ fòrum] {{!}} Repositoris d’aeronaus de forma individual. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, i altres.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| Més de 275 aeronaus, la majoria dels quals es mantenen a [[Ca/FGAddon|FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Escenaris, lliurees, vehicles aeroespacials inspirats en pel·lícules.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme amb Rembrandt i Multijugador.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Diversos projectes.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ El hangar de Horacio]&lt;br /&gt;
| Lloc web en castellà.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; i ADFX-02 Morgan, una aeronau ficticia.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| Aeronaus en alta qualitat incloent [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], i altres.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, escenaris.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Avions de qualitat Signature Series de Marc Kraus de Friedrichshafen, casa del Museu Dornier.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Bloc, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Comunitat de simulació de vol de combat de Flightgear&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Escenaris, textures terrestres... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Molts articles d’avions brasilers.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models i lliurees.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicòpter|Helicòpter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117662</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117662"/>
		<updated>2019-03-23T22:58:17Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
Si un hangar proporciona un fitxer de [[hangar catalog|catàleg URL]] (catalog.xml), es pot afegir al QtLauncher de FlightGear per mostrar tots els avions d'aquest hangar.  Vegeu la pàgina de [[hangar catalog|catàleg d'hangar]] per a tots els detalls sobre com crear el vostre propi fitxer ''catalog.xml''.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
Aquests són enllaços on podeu descarregar avions individuals manualment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Descripció&lt;br /&gt;
! [[hangar catalog|Catàleg URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| Amb U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships i ZF free balloon i aeronaus addicionals als [http://github.com/andgi?tab=repositories repositoris d’aeronaus d’Anders a GitHub].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C i 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Les aeronaus finalitzades seran pujades a FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Desenvolupament d'aeronaus Pipistrel.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| Distribució en [[Git]] i desenvolupament d'aeronaus per a FG {{!}} amb [http://www.thejabberwocky.net/ fòrum] {{!}} Repositoris d’aeronaus de forma individual. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, i altres.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| Més de 275 aeronaus, la majoria dels quals es mantenen a [[Ca/FGAddon|FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Escenaris, lliurees, vehicles aeroespacials inspirats en pel·lícules.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme amb Rembrandt i Multijugador.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Diversos projectes.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ El hangar de Horacio]&lt;br /&gt;
| Lloc web en castellà.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; i ADFX-02 Morgan, una aeronau ficticia.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| Aeronaus en alta qualitat incloent [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], i altres.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, escenaris.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Avions de qualitat Signature Series de Marc Kraus de Friedrichshafen, casa del Museu Dornier.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Bloc, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Comunitat de simulació de vol de combat de Flightgear&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Escenaris, textures terrestres... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Molts articles d’avions brasilers.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models i lliurees.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicòpter|Helicòpter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117661</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117661"/>
		<updated>2019-03-23T22:57:35Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Hangars d'aeronaus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
Si un hangar proporciona un fitxer de [[hangar catalog|catàleg URL]] (catalog.xml), es pot afegir al QtLauncher de FlightGear per mostrar tots els avions d'aquest hangar.  Vegeu la pàgina de [[hangar catalog|catàleg d'hangar]] per a tots els detalls sobre com crear el vostre propi fitxer ''catalog.xml''.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
Aquests són enllaços on podeu descarregar avions individuals manualment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Descripció&lt;br /&gt;
! [[hangar catalog|Catàleg URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| Amb U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships i ZF free balloon i aeronaus addicionals als [http://github.com/andgi?tab=repositories repositoris d’aeronaus d’Anders a GitHub].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C i 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Les aeronaus finalitzades seran pujades a FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Desenvolupament d'aeronaus Pipistrel.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| Distribució en [[Git]] i desenvolupament d'aeronaus per a FG {{!}} amb [http://www.thejabberwocky.net/ fòrum] {{!}} Repositoris d’aeronaus de forma individual. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, i altres.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| Més de 275 aeronaus, la majoria dels quals es mantenen a [[Ca/FGAddon|FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Escenaris, lliurees, vehicles aeroespacials inspirats en pel·lícules.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme amb Rembrandt i Multijugador.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Diversos projectes.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ El hangar de Horacio]&lt;br /&gt;
| Lloc web en castellà.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; i ADFX-02 Morgan, una aeronau ficticia.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| Aeronaus en alta qualitat incloent [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], i altres.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, escenaris.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Avions de qualitat Signature Series de Marc Kraus de Friedrichshafen, casa del Museu Dornier.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Bloc, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Comunitat de simulació de vol de combat de Flightgear&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Escenaris, textures terrestres... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Molts articles d’avions brasilers.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models i lliurees.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicòpter|Helicòpter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117660</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117660"/>
		<updated>2019-03-23T22:57:12Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Contingut relacionat */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
Si un hangar proporciona un fitxer de [[hangar catalog|catàleg URL]] (catalog.xml), es pot afegir al QtLauncher de FlightGear per mostrar tots els avions d'aquest hangar.  Vegeu la pàgina de [[hangar catalog|catàleg d'hangar]] per a tots els detalls sobre com crear el vostre propi fitxer ''catalog.xml''.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
Aquests són enllaços on podeu descarregar avions individuals manualment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Descripció&lt;br /&gt;
! [[hangar catalog|Catàleg URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| Amb U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships i ZF free balloon i aeronaus addicionals a [http://github.com/andgi?tab=repositories Els repositoris d’aeronaus d’Anders a GitHub].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C i 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Les aeronaus finalitzades seran pujades a FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Desenvolupament d'aeronaus Pipistrel.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| Distribució en [[Git]] i desenvolupament d'aeronaus per a FG {{!}} amb [http://www.thejabberwocky.net/ fòrum] {{!}} Repositoris d’aeronaus de forma individual. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, i altres.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| Més de 275 aeronaus, la majoria dels quals es mantenen a [[Ca/FGAddon|FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Escenaris, lliurees, vehicles aeroespacials inspirats en pel·lícules.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme amb Rembrandt i Multijugador.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Diversos projectes.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ El hangar de Horacio]&lt;br /&gt;
| Lloc web en castellà.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; i ADFX-02 Morgan, una aeronau ficticia.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| Aeronaus en alta qualitat incloent [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], i altres.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, escenaris.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Avions de qualitat Signature Series de Marc Kraus de Friedrichshafen, casa del Museu Dornier.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Bloc, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Comunitat de simulació de vol de combat de Flightgear&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Escenaris, textures terrestres... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Molts articles d’avions brasilers.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models i lliurees.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicòpter|Helicòpter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117659</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117659"/>
		<updated>2019-03-23T22:56:27Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Hangars d'aeronaus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
Si un hangar proporciona un fitxer de [[hangar catalog|catàleg URL]] (catalog.xml), es pot afegir al QtLauncher de FlightGear per mostrar tots els avions d'aquest hangar.  Vegeu la pàgina de [[hangar catalog|catàleg d'hangar]] per a tots els detalls sobre com crear el vostre propi fitxer ''catalog.xml''.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
Aquests són enllaços on podeu descarregar avions individuals manualment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Descripció&lt;br /&gt;
! [[hangar catalog|Catàleg URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| Amb U.S. Navy K-type, ''Nordstern'', Zeppelin NT, SSZero airships i ZF free balloon i aeronaus addicionals a [http://github.com/andgi?tab=repositories Els repositoris d’aeronaus d’Anders a GitHub].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C i 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Les aeronaus finalitzades seran pujades a FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Desenvolupament d'aeronaus Pipistrel.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| Distribució en [[Git]] i desenvolupament d'aeronaus per a FG {{!}} amb [http://www.thejabberwocky.net/ fòrum] {{!}} Repositoris d’aeronaus de forma individual. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, i altres.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| Més de 275 aeronaus, la majoria dels quals es mantenen a [[Ca/FGAddon|FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Escenaris, lliurees, vehicles aeroespacials inspirats en pel·lícules.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme amb Rembrandt i Multijugador.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Diversos projectes.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ El hangar de Horacio]&lt;br /&gt;
| Lloc web en castellà.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; i ADFX-02 Morgan, una aeronau ficticia.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| Aeronaus en alta qualitat incloent [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], i altres.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, escenaris.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Avions de qualitat Signature Series de Marc Kraus de Friedrichshafen, casa del Museu Dornier.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Bloc, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Comunitat de simulació de vol de combat de Flightgear&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Escenaris, textures terrestres... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Molts articles d’avions brasilers.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models i lliurees.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicopter|Helicopter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117658</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117658"/>
		<updated>2019-03-23T22:41:49Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Llocs de tercers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
Si un hangar proporciona un fitxer de [[hangar catalog|catàleg URL]] (catalog.xml), es pot afegir al QtLauncher de FlightGear per mostrar tots els avions d'aquest hangar.  Vegeu la pàgina de [[hangar catalog|catàleg d'hangar]] per a tots els detalls sobre com crear el vostre propi fitxer ''catalog.xml''.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
Aquests són enllaços on podeu descarregar avions individuals manualment.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Descripció&lt;br /&gt;
! [[hangar catalog|Catàleg URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| 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].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Finished aircraft will be uploaded to FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Developing Pipistrel aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Scenarios, skins, film inspired aerospace vehicles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Misc. projects.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]&lt;br /&gt;
| Spanish site.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, scenario.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Blog, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Flightgear Flight Sim Military Community&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Many Brazilian aircraft articles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models &amp;amp; liveries.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicopter|Helicopter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117657</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117657"/>
		<updated>2019-03-23T22:38:29Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Desenvolupament d'aeronaus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]] i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
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.  See the [[hangar catalog]] page for all details on creating your own ''catalog.xml'' file.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
These are links where you can download individual planes manually.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Description&lt;br /&gt;
! [[Hangar catalog|Catalog URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| 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].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Finished aircraft will be uploaded to FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Developing Pipistrel aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Scenarios, skins, film inspired aerospace vehicles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Misc. projects.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]&lt;br /&gt;
| Spanish site.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, scenario.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Blog, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Flightgear Flight Sim Military Community&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Many Brazilian aircraft articles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models &amp;amp; liveries.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicopter|Helicopter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117656</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117656"/>
		<updated>2019-03-23T22:38:06Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Desenvolupament d'aeronaus */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Antic hangar fgdata}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]]i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
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.  See the [[hangar catalog]] page for all details on creating your own ''catalog.xml'' file.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
These are links where you can download individual planes manually.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Description&lt;br /&gt;
! [[Hangar catalog|Catalog URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| 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].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Finished aircraft will be uploaded to FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Developing Pipistrel aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Scenarios, skins, film inspired aerospace vehicles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Misc. projects.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]&lt;br /&gt;
| Spanish site.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, scenario.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Blog, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Flightgear Flight Sim Military Community&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Many Brazilian aircraft articles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models &amp;amp; liveries.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicopter|Helicopter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117655</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117655"/>
		<updated>2019-03-23T22:37:10Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Hangar oficial FGAddon */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
L'[[Ca/FGAddon|hangar FGAddon]] és l’hangar oficial de FlightGear.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=Ca/FGAddon]]&lt;br /&gt;
&lt;br /&gt;
Ara, totes les aeronaus de llançament oficial es poden descarregar i actualitzar individualment amb el propi FlightGear. Aquesta és una bona manera de navegar per noves aeronaus i assegurar-vos que les vostres preferides sempre estiguin al dia.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
El repositori de control de versions de [[Ca/FGAddon|FGAddon]] conté aeronaus en desenvolupament i avions etiquetats per a FlightGear 3.4 i versions estables més noves.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=Hangar FGAddon}} El repositori controlat per la versió de Subversion per als avions oficials de FlightGear a la infraestructura de SourceForge, vegeu [[Ca/FGAddon|FGAddon]] per a més informació.&lt;br /&gt;
* {{gitorious source|proj=fg|repo=fgdata|path=Aircraft|view=tree|text=Old fgdata Hangar}} Els arxius de les aeronaus oficials a Gitorious van emigrar a [https://archive.org/ Internet Archive] per a fins de conservació d’arxius i d'història. Les aeronaus es van migrar a [[Ca/FGAddon|FGAddon]] el setembre del 2014. Per a més detalls, vegeu l'[[FlightGear Newsletter September 2014#Aircraft moved to SVN|anunci del butlletí de setembre de 2014]]i el [http://forum.flightgear.org/viewtopic.php?f=28&amp;amp;t=24045 fil d’anunci al fòrum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database] (Base de dades de lliurees d'aeronaus de FlightGear)&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
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.  See the [[hangar catalog]] page for all details on creating your own ''catalog.xml'' file.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
These are links where you can download individual planes manually.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Description&lt;br /&gt;
! [[Hangar catalog|Catalog URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| 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].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Finished aircraft will be uploaded to FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Developing Pipistrel aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Scenarios, skins, film inspired aerospace vehicles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Misc. projects.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]&lt;br /&gt;
| Spanish site.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, scenario.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Blog, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Flightgear Flight Sim Military Community&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Many Brazilian aircraft articles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models &amp;amp; liveries.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicopter|Helicopter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Template:Caution&amp;diff=117654</id>
		<title>Template:Caution</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Template:Caution&amp;diff=117654"/>
		<updated>2019-03-23T22:30:26Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{| cellspacing=&amp;quot;0&amp;quot; style=&amp;quot;border: 1px solid #FC2; border-left-width: 10px; margin: 1em auto; width: {{{width|90%}}}; background-color: #fdf8d8; padding: 2px;&amp;quot;&lt;br /&gt;
| style=&amp;quot;padding-left:5px;&amp;quot; | '''&amp;lt;span class=&amp;quot;smallcaps&amp;quot; style=&amp;quot;font-variant:small-caps;&amp;quot;&amp;gt;{{LangSwitch&lt;br /&gt;
 | ca = Precaució&lt;br /&gt;
 | de = Achtung&lt;br /&gt;
 | en = Caution&lt;br /&gt;
 | fr = Attention&lt;br /&gt;
 | it = Attenzione&lt;br /&gt;
 | nl = Let op&lt;br /&gt;
 | th = '''ระวัง'''&lt;br /&gt;
}}&amp;lt;/span&amp;gt;'''&amp;amp;ensp; {{{1|Add message}}}&lt;br /&gt;
|}&amp;lt;noinclude&amp;gt;{{Informative template |1=&lt;br /&gt;
__NOTOC__&lt;br /&gt;
== Goal ==&lt;br /&gt;
Use this template to add a caution when there might be damage to the virtual aircraft or to real equipment.&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
 {{obr}}'''caution'''{{!}}message{{!}}''width=''{{cbr}}&lt;br /&gt;
&lt;br /&gt;
; width : Width of the messagebox, preferably as a percentage of the width of the page content. Defaults to 90%.&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
 &amp;lt;nowiki&amp;gt;{{caution|Never apply full throttle instantly at take off in high performance tail-draggers.  You will ground loop and possibly crash.}}&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
{{caution|Never apply full throttle instantly at take off in high performance tail-draggers.  You will ground loop and possibly crash.}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre style=&amp;quot;white-space: pre-wrap;&amp;quot;&amp;gt;&amp;lt;nowiki&amp;gt;{{caution|Never apply full throttle instantly at take off in high performance tail-draggers.  You will ground loop and possibly crash.|width=50%}}&amp;lt;/nowiki&amp;gt;&amp;lt;/pre&amp;gt;&lt;br /&gt;
{{caution|Never apply full throttle instantly at take off in high performance tail-draggers.  You will ground loop and possibly crash.|width=50%}}&lt;br /&gt;
&lt;br /&gt;
== Known issues ==&lt;br /&gt;
Adding external links must be done like below. Specifically note the '''1{{=}}'''.&lt;br /&gt;
 {{obr}}'''caution'''{{!}}'''1='''message{{cbr}}&lt;br /&gt;
&lt;br /&gt;
== Related templates ==&lt;br /&gt;
=== Messagebox templates ===&lt;br /&gt;
* {{tl|warning}} &amp;amp;ndash; When a virtual aircraft might crash or when real equipment or ones health might be jeopardized&lt;br /&gt;
* {{tl|note}} &amp;amp;ndash; For important notes&lt;br /&gt;
* {{tl|tip}} &amp;amp;ndash; For helpful tips&lt;br /&gt;
&lt;br /&gt;
=== Inline italic templates ===&lt;br /&gt;
{{inote|If there is a need for a warning use a messagebox template instead.}}&lt;br /&gt;
* {{tl|icaution}}&lt;br /&gt;
* {{tl|inote}}&lt;br /&gt;
* {{tl|itip}}&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Messagebox templates]]&lt;br /&gt;
&amp;lt;/noinclude&amp;gt;&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
	<entry>
		<id>https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117653</id>
		<title>Ca/Hangars de FlightGear</title>
		<link rel="alternate" type="text/html" href="https://wiki.flightgear.org/w/index.php?title=Ca/Hangars_de_FlightGear&amp;diff=117653"/>
		<updated>2019-03-23T22:26:57Z</updated>

		<summary type="html">&lt;p&gt;Catalanoic: /* Llicència */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{BeingTranslated}}&lt;br /&gt;
Els avions de FlightGear sovint es distribueixen a partir d’un hangar.  L'hangar oficial de FlightGear s'anomena [[Ca/FGAddon|FGAddon]] i conté centenars d’avions en diferents etapes de desenvolupament (incloses les aeronaus des de fa fins a 20 anys). També es distribueixen molts avions mitjançant hangars de tercers.&lt;br /&gt;
&lt;br /&gt;
== Llicència ==&lt;br /&gt;
&lt;br /&gt;
El hangar de [[Ca/FGAddon|FGAddon]] es distribueix utilitzant els termes de llicència GPLv2+ - vegeu el [http://www.flightgear.org/flightgear-policy-document/ document de política de FlightGear] oficial.  Els hangars de tercers són lliures de llicenciar el contingut que desitgin.&lt;br /&gt;
&lt;br /&gt;
{{caution|Si es troben violacions de llicències en un hangar de tercers - incloent la còpia d'imatges, sons, objectes 3D o qualsevol altre contingut que no es pugui copiar legalment o qualsevol combinació de llicències no legals - els desenvolupadors de FlightGear es reserven el dret d'eliminar totes les mencions d'aquest hangar des de la infraestructura web oficial de FlightGear (wiki, fòrum, llistes de correu, etc.). L'anunci de continguts il·legals a través de la infraestructura oficial podria provocar problemes legals per als desenvolupadors de FlightGear.}}&lt;br /&gt;
&lt;br /&gt;
== Hangar oficial FGAddon ==&lt;br /&gt;
The [[FGAddon|FGAddon hangar]] is the official FlightGear hangar.&lt;br /&gt;
&lt;br /&gt;
=== Descàrrega d'aeronaus ===&lt;br /&gt;
[[File:FGAddon logo.png|270px|right|link=FGAddon]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Desenvolupament d'aeronaus ===&lt;br /&gt;
The [[Ca/FGAddon|FGAddon]] version controlled repository contains in-development aircraft as well as aircraft tagged for FlightGear 3.4 and higher stable releases.&lt;br /&gt;
&lt;br /&gt;
* {{fgaddon aircraft source|text=FGAddon Hangar}} The Subversion version controlled repository for the official FlightGear aircraft on the SourceForge infrastructure, see [[FGAddon]] for details.&lt;br /&gt;
* {{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&amp;amp;t=24045 announcement topic on the forum]&lt;br /&gt;
&lt;br /&gt;
=== Lliurees ===&lt;br /&gt;
* [http://liveries.flightgear.org FlightGear Livery Database]&lt;br /&gt;
&lt;br /&gt;
== Llocs de tercers ==&lt;br /&gt;
=== Catàlegs d'aeronaus ===&lt;br /&gt;
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.  See the [[hangar catalog]] page for all details on creating your own ''catalog.xml'' file.&lt;br /&gt;
&lt;br /&gt;
=== Hangars d'aeronaus ===&lt;br /&gt;
These are links where you can download individual planes manually.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable sortable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Hangar&lt;br /&gt;
! Description&lt;br /&gt;
! [[Hangar catalog|Catalog URL]]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.gidenstam.org/FlightGear/Airships/ Anders' Lighter-than-air Hangar] &lt;br /&gt;
| 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].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://andinogonthaeler.wordpress.com/ Andino's Hangar]&lt;br /&gt;
| An-124, A340-600HGW, MD80's, Boeing 707-3J9C and 707-320C.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.buckarooshangar.com/flightgear/ Buckaroo's Hangar]&lt;br /&gt;
| Velocity XL RG, Edgley Optica, Lockheed 1049H Constellation, Grumman Goose, McDonnell Douglas MD-81 (&amp;amp; a YASim intro).&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/D-ECHO/ D-ECHO's aircrafts in development]&lt;br /&gt;
| Finished aircraft will be uploaded to FGAddon.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.daveshangar.org/ Dave's Hangar]&lt;br /&gt;
|&lt;br /&gt;
| [http://www.daveshangar.org/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fgpipistrel.org/ FG Pipistrel Hangar]&lt;br /&gt;
| Developing Pipistrel aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/FGMEMBERS FGMEMBERS GitHub-based fork of FGAddon]&lt;br /&gt;
| For [[Git]] Distribution and development of FG aircraft {{!}} with [http://www.thejabberwocky.net/ forum] {{!}} Aircraft repositories individually. &amp;lt;!-- http://sourceforge.net/p/flightgear/mailman/message/34455221/ --&amp;gt;&lt;br /&gt;
| [http://static.djgummikuh.de/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.fguk.eu/index.php/hangar FGUK hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://charles.ingels.free.fr/flightgear/ French FlightGear Hangar]&lt;br /&gt;
| (FR) Aermacchi MB326, Dassault Mirage F1 Mikoyan Gurevitch Mig 31 Foxhound, and more.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hcilab.uniud.it/pan/downloads.html HCI Lab - University of Udine]&lt;br /&gt;
| Aermacchi MB339 Frecce Tricolori.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://helijah.free.fr/flightgear/hangar.htm Helijah FlightGear Hangar]&lt;br /&gt;
| 275+ original aircraft, the majority of which are maintained in [[FGAddon]].&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hhfgfs.weebly.com/index.html Hellcat's FlightGear Hangar]&lt;br /&gt;
| Scenarios, skins, film inspired aerospace vehicles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/HerbyW HerbyW Hanger]&lt;br /&gt;
| Antonov-MilMi-Iljushin-Followme all Rembrandt and Multiplayer support.&lt;br /&gt;
| [http://static.djgummikuh.de/Aircraft/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.hoerbird.net/aircrafts.html Hoerbird Hangar]&lt;br /&gt;
| Misc. projects.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.grafikavirtual.com/fgfs/ Horacio's Hangar]&lt;br /&gt;
| Spanish site.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://horizonflightgearhangar.yolasite.com/ Horizon Flightgear Hangar]&lt;br /&gt;
| Dabolim Naval Air Station (VAGO), Goa, India; Murray Bridge/Pallama Airfield (YMBD), Australia; and ADFX-02 Morgan, a fictional aircraft.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://github.com/it0uchpods?tab=repositories it0uchpods Hanger]&lt;br /&gt;
| High Quality Aircraft including [[IDG-A32X]], [[IDG-A33X]], [[IDG-MD-11X]], [[PA28-Warrior]], and more.&lt;br /&gt;
| [http://static.djgummikuh.de/it0uchpods/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/fghangar JOFH - Just Another Flightgear Hangar]&lt;br /&gt;
| JA-37, scenario.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://marc-kraus.de/ Lake of Constance Hangar]&lt;br /&gt;
| Quality Signature Series Aircrafts by Marc Kraus from Friedrichshafen home of The Dornier Museum.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://longfly.square7.ch Longfly's hangar]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://melbournemotorworks.wordpress.com/ Melbourne Motor Works]&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/ Michael Danilov Hangar]&lt;br /&gt;
| [[Tupolev Tu-144|Tu-144D]].&lt;br /&gt;
| [https://gitlab.com/mdanil/Tu-144_hangar/raw/master/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://nickfg.blogspot.com/ Nick's FlightGear Hangar]&lt;br /&gt;
| Blog, CRJ-200.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://opredflag.com/ Operation Red Flag Hangar]&lt;br /&gt;
| Flightgear Flight Sim Military Community&lt;br /&gt;
| [http://static.djgummikuh.de/OPRF/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf-paf-team-hangar#14330 PAF team Hangar]&lt;br /&gt;
| [[Mudry Cap10b|Cap 10b]], [[Robin DR400 Dauphin|Robin DR400 JSBSim]], [[Douglas C-47 Skytrain|Douglas DC-3 C47]], Tecnam P92 Echo...&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://pattenflightgear.wifeo.com/avions.php Patten's hangar]&lt;br /&gt;
| Alouette-2, DHC6-300, Robin DR400 JSBsim, Tecnam P92 Echo, CAP 10 C, CAP 10 B, Douglas DC3 C47-JSBsim, Sceneries, Ground textures... &lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://presteshangar.wikidot.com/start Prestes Hangar]&lt;br /&gt;
| Many Brazilian aircraft articles.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://riktov.synthasite.com/ Riktov's FlightGear Hangar]&lt;br /&gt;
| BN-2 Islander, Giant Marshmallow Man.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://digilander.libero.it/scighera_fg/index.html Scighera's Hangar]&lt;br /&gt;
| Models &amp;amp; liveries.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://seahorseCorral.org/flightgear_aircraft.html Stewart's SEA-horse Aircraft Hanger]&lt;br /&gt;
| Newest bluebird version.&lt;br /&gt;
| [http://www.seahorsecorral.org/FGMEMBERS/catalog.xml catalog.xml]&lt;br /&gt;
|-&lt;br /&gt;
| [https://sites.google.com/site/sydshangar/ Syd's Google Hangar ]&lt;br /&gt;
| Newer 2.0 versions.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://macflightgear.sourceforge.net/home/aircraft Tat's Aircraft for FlightGear]&lt;br /&gt;
| A6M2 &amp;quot;Zero&amp;quot;, J7W, Ki-84, T-4, HondaJet, OH-1, K5Y1, RV-6A, YS-11.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://vicmar.weebly.com/ VicMar]&lt;br /&gt;
| Yanagisawa Gen H-4, Stung Biker, Quad Bikes, SRN4, Water Skier, G2 Thunderpack, Martin Jetpack.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| [http://www.treborlogic.com/fgfs/hangar/ Yourgod's Hangar]&lt;br /&gt;
| Douglas DC-8.&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Hangars antics ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://croo.murgl.org/fgfs/index.html A-10 and A-6 stuff]&amp;lt;/s&amp;gt;&lt;br /&gt;
* &amp;lt;s&amp;gt;{{gitorious source|text=Airbus Aircraft Development Git}}&amp;lt;/s&amp;gt;{{dead link|2018-08-05}} (A320, A330, A340-300, A380 - various authors, see the projects under &amp;lt;code&amp;gt;airbus-aircraft&amp;lt;/code&amp;gt;)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://www.sol2500.net/flightgear/aircraft.html DFaber Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Eurofighter, PC-6, Bf 109, Beufighter, F4U, Ju 52, DH Mosquito, G. Albatross, F-86, and more)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://thefancyflightgearhangar.blogspot.com the fancy flight gear hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (a few well made aircraft)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://flier95-flightgear.blogspot.com/ Flier95's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-08}} (Blog format)&lt;br /&gt;
* [https://sites.google.com/site/grtuxhangar GRTux Hangar] (28+ aircraft and add-ons; you need to mail to GRTux for download) (last updated 2011)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://mysite.verizon.net/vzeuyecs/ Kent Esbenshade's Boneyard Hangar]&amp;lt;/s&amp;gt;{{dead link|2015-09}} (Classic aircraft)&lt;br /&gt;
* [http://www.ae.uiuc.edu/m-selig/apasim/Aircraft-uiuc.html UIUC Hangar] (for FGFS 0.7.8, last update 2002)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://fg-acjza.wix.com/hangar/ ACJZA Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Land, Sea, Air) (dead link as of 1/2/2017)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://theomegahangar.flymerlion.org/ Omega Hangar]&amp;lt;/s&amp;gt;{{dead link|2017-01-02}} (Embraer E-jet Family, A330-200, A320neo, CRJ-700 Full First Class, ATR-42-family, A321-series, Mobile Stairway)&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://pjedvaj.wordpress.com/ pjedvaj's Hangar]&amp;lt;/s&amp;gt;{{dead link|2018-07-24}} (PC-9M, PC-21, MiG-21bis, T-50, Harrier GR.1, F-35B, RAH-66, Su-25, Yak-130)&lt;br /&gt;
&lt;br /&gt;
=== Hangars de lliurees/escenaris ===&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://AAliveries.yolasite.com/ AA Liveries]&amp;lt;/s&amp;gt;{{dead link|2015-01}} Another livery site&lt;br /&gt;
* [http://berwickskins.yolasite.com/ Berwick-skins]&lt;br /&gt;
* &amp;lt;S&amp;gt;[http://dliveryhangar.synthasite.com/ Dodger4's Livery Hangar]&amp;lt;/s&amp;gt; (dead link as of 1/2/2017)&lt;br /&gt;
* [https://github.com/FGMEMBERS-TERRAGIT/terraGIT terraGIT] global scenery, new &amp;amp; updated airports 2016-10&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* [http://jchnd.blogspot.com/ JcHnd's Liveries for FlightGear]&lt;br /&gt;
* [http://lukashangar.jimdo.com/ Lukas' hangar] (Scenery projects, Liveries)&lt;br /&gt;
* [http://mojos-hangar.webs.com/ MOJO's Flightgear Livery Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt;[http://members.cox.net/scotsg8r/hangar/ N-SCOT's Hangar]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (5+ liveries &amp;amp; mods)&lt;br /&gt;
* &amp;lt;s&amp;gt;[https://planepainter.yolasite.com/ The Planepainter]&amp;lt;/s&amp;gt;{{dead link|2012-04}} (Liveries, Scenery)&lt;br /&gt;
* [http://simbabeathangar.webs.com/ Simbabeat's Livery Hangar]&lt;br /&gt;
* [http://victorhangar.blogspot.com/ Victor Hangar] (in Portuguese - Brazilian)&lt;br /&gt;
&lt;br /&gt;
=== Altres repositoris/miralls de FlightGear ===&lt;br /&gt;
* [http://hsotfhangar.wordpress.com/ HSOTF Official Hangar]&lt;br /&gt;
* &amp;lt;s&amp;gt; [http://www.unitedfreeworld.com/ Unitedfreeworld] (scenery, plane models, and livery) &amp;lt;/s&amp;gt; {{dead link|2018-06}}&lt;br /&gt;
&lt;br /&gt;
== Contingut relacionat ==&lt;br /&gt;
* [[Table of models|Taula de models]]&lt;br /&gt;
* [[Ca/Aeronau|Aeronau]] - [[Ca/Helicopter|Helicopter]] - [[Ca/Vehicle|Vehicle]]&lt;br /&gt;
&lt;br /&gt;
== Referències ==&lt;br /&gt;
{{Appendix}}&lt;br /&gt;
&lt;br /&gt;
[[Category:Lists]]&lt;br /&gt;
[[en:FlightGear hangars]]&lt;br /&gt;
[[es:Hangares_Flightgear]]&lt;br /&gt;
[[fr:FlightGear hangars]]&lt;/div&gt;</summary>
		<author><name>Catalanoic</name></author>
	</entry>
</feed>