FlightGear wiki - User contributions [en]

User:Axlerate

2019-09-07T13:03:43Z

Axlerate: Add

Hello.

I'm here for anti-vandalism work.

I also have an interest in fixing any grammatical errors around here.

I am also a friendly editor here, as I don't bite, probably to the vandals. (Hoping to become an admin here too!)

My general goal around here is to ensure that [[FlightGear Wiki]] is what it should be, a user-made encyclopedia, and not a playground for vandals.

I am open to all suggestions and tips for I am new to [[FlightGear Wiki]] and want to learn all that is possible on how things are run here.

Any questions, comments, suggestions, concerns, discussions, enquiries, etc,.? Post them on my talk page, or send them via email at dovewindsor@gmail.com.

[[Category:Users]]

Es/Recomendaciones de hardware

2019-09-07T09:55:10Z

Axlerate: Tidy

Estas '''recomendaciones de hardware para [[FlightGear]]''' están basadas en retroalimentaciones de la comunidad. Asegúrate de consultar otras fuentes antes de tomar decisiones serias enrelación al hardware del ordenador.

El rendimientod de FlightGear depende de tres componentes principales en tu computador: la CPU (procesarod), el cual realiza todos los cálculos; la tarjeta gráfica, la cual renderiza el aspecto visual de FlightGear; y la RAM (también conocida como memoria), la cual generalmente permite a FlightGear tener más información en funcionamiento (por carecer de una frase más técnica).

También puedes querer revisar el artículo [[Howto: Build a cheap FlightGear box]] sobre cómo construir tu propio equipo FlightGear basándote en servidores desmantelados y reacondicionados y también aprender acerca de cómo el proyecto FlightGear maneja el soporte a hardware antiguo en [[FlightGear and old Hardware]].

Ver también: [[FlightGear Benchmark]].

== Hardware recomendado para FlightGear 3.20+ ==
Generalmente, si quieres ver framerates en los 20's y por encima y ajustes gráficos medios/altos, lo cual es lo preferido típicamente, deberías tener un presupuesto de al menos $1000. La siguiente lista es hardware recomendado. No es requerido en ningún grado. Sin embargo, si vas a comprar un nuevo ordenador dedicado a FlightGear, es altamente recomendable que tengas un ordenador con al menos estos requisitos.
; Pantalla
* Una pantalla con una resolución de al menos 1024x768 a 32bpp (actualmente muchos diálogos GUI no se pueden ver de otra forma)
; Unidad de procesamiento gráfico
* Una tarjeta de video 3D (con chipset AMD o NVIDIA) con soporte para [[OpenGL]] 2.1 o superior y al menos 1024-2048 MB de memoria dedicada DDR3+ (preferido DDR5) VRAM (es decir 512 Mb VRAM mínimo). FlightGear requiere una tarjeta de video 3D acelerado por hardware '''OpenGL 2.1-compliant''' para correr a framerates razonables. Muchos PCs modernos tienen tarjetas 3D aceleradas por hardware. Si tu video FlightGear no corre suavemente mira [[Graphics drivers configuration]].
* Ver [[Supported Video Cards]] para encontrar una lista de tarjetas de video conocidas por funcionar con FlightGear.
* Las tarjetas con soporte operativo para GLSL/shader permitirán a FlightGear correr con más efectos visuales.
* Si vas a correr FlightGear en serio deberías [[Problematic Video Cards#Intel GMA|evitar las tarjetas Intel HD/GMA]] a todo coste. Éstas son chipsets integrados que solo proporcionan un soporte OpenGL/GLSL básico. Ver [[problematic video cards]] para una lista de tarjetas de video que pueden no funcionar correctamente.
; Procesador
* Al menos 2-4 Gb de memoria RAM '''libre''' (y más es mejor: al construir/comprar un sistema nuevo considerar 6-8 Gb como el mínimo absoluto en estos días). FlightGear usa más de 500 Mb de RAM por defecto. Si ha menos RAM libre disponible FlightGear sería ralentizado significativamente debido al swapping del sistema operativo.
* Al menos un procesador de cuatro núcleos con ~ 2GHz cada uno, arquitectura (y sistema operativo) de 64 bits recomendada (los procesadores de múltiples núcleos tienen beneficios para algunos componentes de FlightGear como el cargador de cuadrículas multiproceso). Al comprar un nuevo ordenador, hoy en día es una buen idea comprar al menos un computador con cuatro núcleos (es decir, i7).
; Disco de almacenamiento
* 5 Gb de espacio de disco duro para una instalación mínima, aproximadamente 10 Gb si quieres compilarlo tú mismo, más hasta 80 Gb para escenarios mundiales opcionales. Se requiere más espacio para aquellas personas que quieran comprobar el último paquete base de [[Git]]. La gente que use [[Scripted Compilation on Linux Debian/Ubuntu|compilación basada en script en Linux Debian/Ubuntu]], necesitará aproximadamente 30 Gb de espacio de disco en total.
; Dispositivos de entrada
* Un ratón de tres botones o un rato de dos botones con rueda de desplazamiento
* Un [[joystick]]/mando y/o pedales opcionales. Puerto de juegos o USB (compatible con HID), ver <tt>[[$FG_ROOT]]/Input</tt> para una lista de dispositivos de entrada conocidos por funcionar con FlightGear.
; Tarjeta de sonido
* Una tarjeta de sonido opcional, compatible con SoundBlaster, preferiblemente con soporte EAX.

== NVIDIA ==
Evita GPUs nVidia con bajos segundos números (x20, x40). Más segundos dígitos significa más núcleos CUDA.

El número de núcleos CUDA importa mucho más que unos pocos Mhz de frecuencia, pues puedes procesar más, en paralelo.
También vigila el ancho del bus, pues eso tiene un gran impacto en el procesamiento de datos. Cuantos más núcleos CUDA tenga mejor. Un GTX680 es mucho, mucho, mucho más importante que una CPU con tropecientos núcleos.

En caso de duda, opta por una generación más antigua de x60 (460 ó 560), incluso un 260 aportaría mucha más mejora que el 620. Básicamente, las tarjetas nVidia compilan GLSL shaders y núcleos OpenCL en los núcleos CUDA, por lo que más núcleos CUDA = más poder de shaders.

Cualquier GPU (y otro hardware) que tengas, antes de nada asegúrate de que está completamente soportada por tu sistema operativo.
Thorsten mencionó en otro hilo que compró un ordenador con una NVIDIA GTX670 que acabó no estando totalmente soportada por Linux, por lo que te sugiero que seas realmente prudente con esto.

== Portátiles ==
Si estás intersado en correr FlightGear en un portátil podrías querer también revisar [[Notebooks known to run FlightGear]]. No está recomendado usar un portátil normal si vas a volar a menudo en FlightGear.

== Componentes ==
Tu experiencia general en FlightGear depende de estos componentes:
*Tu '''CPU''', la cual hace todos los cálculos. Este componente no es tan importante como tu tarjeta gráfica. Sin embargo, deberías tener en mente que tu CPU es el cerebro de tu ordenador. Como se dijo anteriormente, se recomienda que compres una CPU que tenga al menos 4 núcleos.
*Tu '''tarjeta gráfica''', la cual renderiza los visuales de FlightGear. Este componente es extremadamente importante. Si tienes una CPU espectacular pero una tarjeta gráfica mediocre tu framerate será bajo. También se recomienda que compres una tarjeta gráfica relativamente nueva, pues las antiguas (incluso si es muy potente) son conocidas por causar problemas de renderizado.
*Tu (memoria) '''RAM''', la cual permite almacenamiento temporal de información. La memoria es probablemente la menos importante de los tres en relación al framerate. Sin embargo, cualquier cosa por debajo de 4 Gb de memoria se sabe que ha provocado roturas en FlightGear.

=== ¿Debería comprar un ordenador o construírmelo? ===
Generalmente se recomienda que te construyas tu propio ordenador. Tu dinero te llegará mucho más lejos. Sin embargo, también se recomienda que si te construyes tu propio ordenador, conozcas a alguien que sepa moverse con ordenadores. Comprar partes que ''piensas'' que pueden ser potentes pero que en realidad no lo son o, peor aún, no son compatibles, puede llevar a una decepción.

== Contenido relacionado ==
* [[Supported Video Cards]]
* [[Graphics drivers configuration]]
* [[Troubleshooting Problems]]

[[Category:Hardware|Recommendations]]
[[de:Hardwareempfehlungen]]
[[en:Hardware Recomendations]]
[[fr:Hardware Recommendations]]
[[pl:Wymagania systemowe‎]]

Es/Piloto automático

2019-09-07T09:53:36Z

Axlerate: Tidy

{{forum|46|Autopilot & Route Manager}}
{{Autoflight Navigation}}
[[File:Autopilot.jpg|thumb|270px|El diálogo de configuraciónd el piloto automático de FlightGear.]]
Un '''piloto automático''' ('''AP''') es un sistema mecánico, eléctrico o hidráulico usado para guiar un vehículo sin asistencia humana. Mucha gente entendiende un piloto automático referiéndose específicamente a una [[Es/Aeronaves|aeronave]], pero el sistema de auto-dirección de los barcos, botes, vehículos espaciales y misiles también se suele llama con éste término.

El piloto automático de una aeronave a veces es referido como "George".

== Piloto automático en FlightGear ==
Tenemos uno genérico y uno personalizado escritos para una determinada aeronave, el cual se supone que simula tipos/modelos particulares de piloto automático para una aeronave específica.

El genérico se pueden usar en aeronaves que no tienen implementado un piloto automático personalizado y parece funcionar razonablemente bien en la mayoría de aeronaves que usan [[JSBSim]]. Puedes activarlo con "Autopilot Settings" que puedes abrir usando la techa F11 o en la barra de menús usando el item "Autopilot".

En la vida real las aeronaves tienen sistemas de pilotos automáticos específicamente programados/personalizados para tratar con las características individuales de cada aeronave. Hasta cierta extensión, FlightGear tiene la posibilidad de simularlos también.

Por tanto, es posible escribir un <tt>autopilot.xml</tt> personalizado para sobreescribir la implementación de piloto automático genérico.
Este fichero de configuración de piloto automático personalizado puede ser gestionado bien mediante el diálogo estándar del piloto automático, puntos sensibles de un panel de cabina personalizado o una combinación de ambos.
También, es posible proporcionar implementaciones mejoradas o completamente nuevas del diálogo del piloto automático estándar para tratar con características específicas del piloto automático/aeronave (por ejemplo, ver el B1900D o Citation Bravo en Git/HEAD).
[[File:Navomatic-dialog.png|thumb|200px|Un Navomatic 400AP personalizado]]
[[File:Custom-autopilot-dialog.png|thumb|300px|Un diálogo de piloto automático personalizado]]

Sin embargo, algunas aeronaves en FlightGear solo proporcionan un medio de interacción con el piloto automático (es decir, el diálogo del piloto automático '''o''' puntos sensibles del panel).
Por ejemplo, los pilotos automáticos del [[Piper PA34-200T Seneca II|Seneca II]] y del [[Piper PA-24 Comanche|Piper Comanche]] solo pueden ser usados desde la cabina virtual usando puntos sensibles de panel personalizados. De hecho ésto es cada vez más el caso, pues la nuevas emulaciones de sistemas de pilotos automáticos se están implementando usando el lenguaje interpretado interno [[Nasal scripting language||Nasal]], el cual proporciona un diseño del sistema y funcionalidad mucho más flexibles, comparado con la forma relativamente estática de describir sistemas de piloto automático y sus modos relevantes usando solo el sistema de piloto automático configurable por [[XML]]. De hecho, para emular adecuadamente los sistemas de piloto automático más complejos que proporcionan soporte para modos de vuelo más abstractos, el uso de una combinación de controladores PID configurables mediante XML y Nasal probablemente sea la aproximación más prometedora.

En general, se puede considerar que es más complejo proporcionar implementaciones adecuadas del panel de la cabina que cablear las propiedades del piloto automático al diálogo GUI del piloto automático estándar, de tal forma que sin el piloto automático de una aeronave no parece funcionar adecuadamente usando los puntos sensibles del panel de la cabina, puedes querer intentar usar el diálogo GUI estándar en su lugar.

También, por favor ten en cuenta que no todas las combinaciones aeronave/piloto automático proporcionarn soporte completo a todas las características ofrecidas por el diálogo del piloto automático estándar. Esto puede ser debido al estado de acabado de una aeronave, pero también a limitaciones técnicas en ciertas aeronaves/pilotos automáticos, de tal forma que solo se proporcionen ciertos modos.
Esto también puede aplicar a paneles de aeronaves, que puede parecer que ofrecen funcionalidades que pueden no estar implementadas aún.

Adicionalmente, JSBSim también incorpora soporte para una implementación de piloto automático autónomo, que funcionan sin ninguna dependencia de FlightGear/Nasal.

Para más información sobre programar pilotos automáticos en FlightGear mira [[Autopilot Tuning Resources]] y http://www.flightgear.org/Docs/XMLAutopilot/.

== Ajustes del piloto automático ==
El diálogo de ajustes del AP se pueden encontrar en '''Autopilot > Autopilot Settings'''.

=== Control de rumbo ===
* '''Wings Level''': actívalo para mantener tu avión horizontal, normalmente usado para Go-Arounds.
* '''Heading bug:''' ubicado en la rosa de la brújula en tu panel de instrumentos, es un selector de rumbo móvil, los triángulos púrpura que están apuntando a tu rumbo de pista (283 para KSFO por defecto). Este selector se mueve alrededor de la rosa mediante la operación de selector de rumbo. Éste puede ser usado de varias formas. Al volar el avión a mano gira el selector a tu rumbo deseado. De esta forma tendrás un recordatorio visual constante. Si [[ATC|Control de Tráfico Áereo]] te da un nuevo rumbo mueve el selector de rumbo al nuevo rumbo y tendrás tu recordatorio visual.
* '''True heading:''' tu rumbo real según se muestra en la brújula (del [[Head-up display|HUD]]) y [[Multiplayer Howto|MP Map]].
* '''NAV1 CDI Course:''' usado para volar de VOR a VOR como en los viejos tiempos y usado por el [[ILS]].

=== Control de velocidad ===
* '''Speed with Throttle:''' la velocidad será regulada a la velocidad seleccionada mediante el control del acelerador.
* '''Speed with Pitch:''' tu avión será empujado hacia abajo o arriba para alcanzar la velocidad seleccionada. No se puede usar durante el despegue, aterrizaje o en vuelos a baja altitud. Hacerlo puede causar un accidente.

=== Control de cabeceo/altitud ===
* '''Vertical Speed:''' establece la velocidad vertical de ascenso. Habitualmente se usa en "pies por minuto"
* '''Pitch Hold:''' grados de cabeceo de tu avión. Usa un número negativo para bajar el morro.
* '''AoA Hold:''' el ángulo de ataque describe el ángulo de las alas comparado con la dirección del aire que les circunda. La sustentación del ala depende del AoA. Un AoA demasiado alto causará que el avión entre en pérdida.
* '''Altitude Hold:''' la altitud deseada de tu avión en pies (FL1=100 ft, FL25=2500 ft etc.).
* '''AGL Hold:''' la altitud sobre el terreno. Normalmente la altitud se da sobre el nivel del mar.
* '''NAV1 Glideslope:''' la senda vertical que dirige al avión desde el punto de intercepción hasta el nivel de la pista (usado solo con [[ILS]]).

=== Modo Flight Director ===
El flight director calcula y muestra los ángulos de cabeceo y alabeo adecuados requeridos para que la aeronave siga un camino seleccionado. Un ejemplo sencillo: si el avión está en vuelo nivelado, con un rumbo de 045 grados y a una altitud de 15000 pies, mantiendo una velocidad de 260 kts, las barras FD están centradas. Entonces el flight director se establece a un nuevo rumbo de 090 grados y una nueva altitud de 20000 pies. El avión tiene así que hacer un giro ascendente. El piloto tirará entonces de la columna de control mientras que rota el avión a la derecha. Cuando alcanza los ángulos de cabeceo y alabeo adecuados las barras FD se centrarán de nuevo y permanecerán centradas hasta que sea el momento de devolver el giro para nivelar las alas (cuando el rumbo comienza a acerque a 090). Cuando el avión se acerque a 20000 pies la barra de cabeceo bajará, dando así orden al piloto de que reduzca el cabeceo para nivelarse a la nueva altitud.

El FD se usa generalmente en conexión directa con el piloto automático, donde el FD gobierna el AP para poner el avión en la actitud necesaria para seguir una trayectoria. La combianción FD/AP se usa típicamente en aproximaciones con instrumentos bajas acopladas al piloto automático, (por debajo de 200 pies AGL) o aproximaciones instrumentales ILS CAT II y CAT III.

La forma exacta de mostrar el flight director varía con el tipo de instrumento, bien con forma de cruz o barras de comando.

== Gestor de ruta ==
{{main article | Route Manager}}
El gestor de ruta en FlightGear es algo así como un FMC (Flight Management Control/Computer) sencillo.
En FGFS puedes introducir una lista de puntos de ruta como ayudas a la navegación, puntos fijos y aeropuertos, a los cuales vuela la aeronave. También puedes añadir la altitud que debería tener la aeronave al pasar sobre cierto punto de ruta. Así que es posible dejar a la aeronave que vuele a lo largo de una cierta ruta.

De momento, no es posible añadir velocidades y otras restricciones.

== Ver también ==
[[Advanced Autopilot Tuning Tips]]

== Contenido relacionado ==
* [[Autopilot Configuration Reference]]
* [[Howto: Design an autopilot]] para un avión FlightGear

[[Category:Autoflight| ]]
[[en:Autopilot]]

De/FlightGear Newsletter Juli 2016

2019-09-07T09:51:48Z

Axlerate: Tidy

{{De/Newsletter-header|2016-07}}
<div style="border-bottom:3px double #BBB;">
{| width="100%" |
| valign="top" width="33%" |
{{Newsletter-cover-header|Neuigkeiten in der Entwicklung}}<br>
[[#ATC-pie Upgrade|ATC-pie Upgrade]]<br>
| valign="top" width="33%" |
{{Newsletter-cover-header|Im Hangar}}<br>
[[#Cessna 182S Skylane|Cessna 182S Skylane]]<br>
[[#ErAZ-762|ErAZ-762]]<br>
[[#MQ-9|MQ-9]]<br>
[[#Rewloola|Rewloola]]<br>
{{Newsletter-cover-header|Szenerie-Abteilung}}<br>
[[#Nachtlichter für EarthView|Nachtlichter für EarthView]]<br>
| valign="top" width="33%" |
{{Newsletter-cover-header|Mitarbeiten}}<br>
[[#Übersetzer gesucht|Übersetzer gesucht]]<br>
[[#FlightGear Logos|FlightGear Logos]]<br>
[[#Screenshots|Screenshots]]<br>
<small>[[#Screenshot des Monats|Screenshot des Monats]]</small>
|}</div>

== Neuigkeiten in der Entwicklung ==
=== ATC-pie Upgrade ===
[[File:ATC-pie-logo.png|90px|left|ATC-pie logo]]
Seit unserem letzen Post im [[de/FlightGear Newsletter Januar 2016#New ATC-pie release|Newsletter vom Januar]] wurde der Flugverkehrsüberwachungstower und Radar Simulator '''[[ATC-pie]]''' durch zwei grundlegende Funktionen erweitert. Die erste, die wir schon im Mai herausgegeben haben, erlaubt '''Lehrer-Schüler Verbindungen''' (''student-teacher connections''), bei uns Totorial-Reihen, in dnenen der Lehrer den Verkehr manipuliern, das Wetter verschlechtern oder gespeicherte Situaltionen abspielen kann, bei denen der Schüler so trainiert und/oder getestet werden soll.

Die zweite und ganz neue Funktion (diesen Monat hinzugefügt) ist der Einbau von '''Werkzeugen zur Bodenüberwachung''' (''ground control tools''). Es gibt zum Beispiel einen klick & schieb Taxi-Anweiser, der die Arbeit der Luftüberwachung erleichtern soll, wenn die Flughäfen GND anbieten. Die dazugehörige Spezialbereich-Funktion wurde ebenfalls hinzugefügt, spielbar allein oder zusammen mit anderen Spielern in anderen Spezialbereichen auf allen Flughäfen, bei denen ein ''[[De/Interaktiver Verkehr#Interaktiver Verkehr am Boden|Bodenverkehr]]'' existiert (oder selbst erstellt werden kann, oder einfach vom X-plane Gateway abgekupfert werden kann). Unten ist ein Bild vom ''Taxi Instruction Tool'' in Dubai zu sehen.

[[File:ATC-pie-screenshot-taxiInstructionTool.png|600px|Das ATC-pie taxi instruction tool in Dubai international Airport]]

== Im Hangar ==
=== Cessna 182S Skylane ===
Die '''[[Cessna 182S|Cessna 182S Skylane]]''' wurde jetzt offiziell veröffentlicht; sowohl im FGAddon, als auch auf {{github source|proj=HHS81|repo=c182s|text=unserem Entwicklerportal}}. Einige der Funktionen sind:
* verbessertes FDM, basierend auf der originalen Fluganleitung mit richtigen Richtgeschwindigkeiten, Steigraten, Gewicht & Balance, Treistoffverbrauch und TO/Landedistanz nach der Fluganleitung
* akkurates und detailliertes 3D Außenmodell, anpassbare Radausrüstung un wählbare verchromte Spinner, alles auf Grundlage des "uber-shader"
* fünf detaillierte Liveries (paintkits inklusive)
* akkurates und detaillierter 3d-Innenraum, mit detailliertem Panel und Steuerungen
* Schatten im Inneraum (nur ALS)
* Außen verschieden starker Schatten (nur ALS)
* realistische Innenlichter an Panelen und Schubhebeln (nur ALS)
* 4 Innenraumansichten (Pilot und Passagiere) Hexk und Flügelsichten
* <s>Be</s>gehbar (Pilot kann herumlaufen)
* Dynamisch plazierte statische Elemente, wie ein Treibstofftankwagen, Leitern und Sicherheitspylonen, die mit dem Piloten im Laufmodus bedient werden können.
* Reifenkeile, die das Flugzeug ohne weiteres allein auf Position halten (auch ohne Verwendung der Parkbremse)
* Bessere Bildraten verglichen mit der [[De/Cessna 172P|172P]] (45% Bessere fps-Leistungen bei underen Tests)

Viel Spaß!

<gallery mode="packed">
C182s.jpg
C182-panel-detail.jpg
C182-external4.jpg
C182-cockpit-at-night.jpg
C182-default.jpg
</gallery>

=== ErAZ-762 ===
Der '''[[ErAZ-762]]''' wurde freigegeben. Er kann in {{github source|proj=aucafly|repo=ERAZ762|text=GitHub}} gefunden werden. Sieh Dir auch die [https://aucafly.wordpress.com Offizielle Webseite] an.

=== MQ-9 ===
"'''''Die MQ-9 Reaper''' (dt. „Sensenmann“) ist eine Drohne des US-amerikanischen Herstellers General Atomics. Sie basiert auf der MQ-1 Predator (deshalb anfangs auch '''Predator B''' genannt), ist aber wesentlich größer und dient in erster Linie der Luftnahunterstützung. Sie wird unter anderem von den Streitkräften der Vereinigten Staaten und der Royal Air Force in Afghanistan eingesetzt. <sup>({{wikipedia|General Atomics MQ-9|Zitat von Wikipedia|lang=de}})</sup>
<br />

Er wurde gerade im {{github source|proj=meirm|repo=MQ-9|text=GitHub}} veröffentlicht.<br />
'''Beta Tester''' sind willkommen. Bitte gib dein Feedback in Github oder im Forum ([https://forum.flightgear.org/viewtopic.php?f=4&t=29975 "Announcing New UAV MQ-9 Predator B"]) an den Nutzer "falafel" und/oder "pjedvaj"

=== Rewloola ===
'''[[Rewloola]]''' ist ein futuristisches Flugzeug, das aus dem Animationsfilm ''Mobile Suit Gundam'' bekannt ist: ''Char's Counterattack'' und später in der Serie ''Mobile Suit Gundam Unicorn OVA''. Es kann in {{github source|proj=aucafly|repo=Rewloola|text=GitHub}} gefunden werden. Besuche auch die [https://aucafly.wordpress.com offizielle Website].
<gallery mode="packed">
ERAZ762.png|ErAZ-762
MQ-9 version 1.2.jpg|Erste Darstellung vom MQ-9 in der Version 1.2
Rewloola.jpg|Rewloola im Testflug
</gallery>

== Szenerie-Abteilung ==
=== Nachtlichter für EarthView ===
FGs Weltraum-Darstellungs-Engine [[Earthview]] hat ein Update für die Lichter bei Nacht erhalten. Viele von euch haben wahrscheinlich die atemberaubend Fotos von den beleuchteten Städten bei Nacht gesehen, die ISS Astronauten gemacht haben. Earthview macht jetzt das gleiche.<br />
Mithilfe des Alpha-Channel der Texturen der Erde brechnet EarthView jetzt die Lichterstärken.

Zurzeit sind in FGData nur Texturen mit 2k Auflösung vorhanden, um Speicherplatz zu sparen. Allerdings sind auch die 4k und 8k Auflösungen verfügbar!

Die höheren Texturen kannst Du [[Earthview#Customization|hier]] seperat downloaden.

{{note|Bedenke dabei, dass zu hohe Auflösungen deine Grafikkarte in die Knie zwingen können. Außerdem kann das Laden der großen Datenmengen mehr Zeit in Anspruch nehmen. Wenn nach dem Laden die Bildraten extrem niedrig sind - oder FlightGear sogar abstürzt - solltest Du es mit einer niedrigeren Auflösung probieren.}}

<gallery mode="packed">
Shuttle night01.jpg|Nightview aus dem Shuttle
Shuttle night02.jpg|Nightview aus dem Shuttle
EarthView with night lights.jpg|Erde aus 6000km Höhe mit den Lichtern der Städte, die die Erde erhellen.
</gallery>

== Mitarbeiten ==
=== Übersetzer gesucht ===
{|
| [[File:en.gif]]
| The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multilingual, start at [[Help:Translate]].
|-
| [[File:fr.gif]]
| Le wiki de FlightGear a toujours besoin d'aide pour être traduit en différentes langues. Si vous êtes intéressé par le rendre multilingue, commencez par lire [[:fr:Help:Traduire|Help:Traduire]].
|-
| [[File:de.gif]]
| Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
| [[File:nl.gif]]
| De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
| [[File:es.gif]]
| La wiki de FlightGear todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|-
| [[File:cat.gif]]
| La wiki de FlightGear encara necessita ajuda per traduir-la a diverses llengües. Si esteu interessat en fer la wiki de FlightGear multilingüe, llavors comenceu a [[:ca:Help:Traduir|Help:Traduir]].
|-
| [[File:pt.gif]]
| A wiki de FlightGear ainda necessita de ajuda para traduzi-la em vários idiomas. Se estás interessado em tornar a wiki de FlightGear multi-lingual, por favor começa em [[:pt:Help: Traduzir|Help: Traduzir]].
|}

=== FlightGear Logos ===
Solltest Du graphische Elemente für deine FlightGear Website (Hangar, YouTube-Kanal, o.ä.) suchen, wirf doch einen Blick auf die [[FlightGear logos|FlightGear Logos]]. Und falls Du eine künstlerische Ader hast, fühl Dich frei, eigene Designs zu erstellen und hier hochzuladen.

=== Screenshots ===
Das FlightGear-Projekt benötigt ständig Screenshots, welche neue Features seit dem letzten Release zeigen. Diese sollten von hoher Qualität sein, besonders von inhaltlicher und technischer Seite. Dafür wird empfohlen, die besten Graphikfilter zu nutzen ([[De/Antialiasing|Antialiasing]], Texturenschärfung, etc.). Näheres unter [[De/Howto:Gute Screenshots machen|Howto:Gute Screenshots machen]].

==== Screenshot des Monats ====
FlightGears Screenshot des Monats Juli 2016 ist ''Sunrise soaring in Corsica'' von {{usr|Dg-505|Jonathan S. (Dg-505)}}
[[File:ASK 13 over Corsica.jpg|900px|center|Ein Segelflugzeug Schleicher ASK 13 fliegt über Korsika bei Sonnenaufgang]]

[[Category:De/FlightGear Newsletter|2016 07]]
[[Category:Changes after 2016.2]]
[[en:FlightGear Newsletter July 2016]]

User:Axlerate

2019-09-07T09:48:01Z

Axlerate: Added a user category

Hello.

I'm here for anti-vandalism work.

I also have an interest in fixing any grammatical errors around here.

I am also a friendly editor here, as I don't bite, probably to the vandals. (Hoping to become an admin here too!)

Any questions, comments, suggestions, concerns, discussions, enquiries, etc,.? Post them on my talk page, or send them via email at dovewindsor@gmail.com.

[[Category:Users]]

User talk:Chrisf

2019-09-07T09:40:32Z

Axlerate: Welcomed new user!

{{Welcome to the wiki}} --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 05:40, 7 September 2019 (EDT)

Bad graphics performance under KDE

2019-09-07T09:39:24Z

Axlerate: Fixed grammatical errors using Grammarly

== Problem ==
When starting Flightgear under KDE, the graphics performance is very bad, i.e. low framerates, while running Flightgear in a different window manager shows better performance.

== Reason ==
It is likely that "compositing" is activated. KDE includes a large number of various effects which use OpenGL. This might degrade the performance of applications that use OpenGL heavily.

== Recommended Solution ==
For KDE 4.9+:
You can import a so called '''window rule''':

Save the following as '''''flightgear.kwinrule''''', then open KDE's '''System Settings''', go to '''Window Behaviour''', then '''Window Rules'''. From the right select '''import rule''', then navigate to where you saved '''''flightgear.kwinrule''''', select it then press '''Open'''. You will be returned to the '''Window Rules''' tab. Press '''Apply''' and then close the '''System Settings''' window.

Next time you start Flightgear (''or osgviewer for that matter'') kwin will block compositing as long as Flightgear is running, then restore compositing when you close Flightgear, regardless if you start Flightgear in windowed or fullscreen mode.

<syntaxhighlight lang="ini">
[Application settings for osgviewer]
Description=Application settings for osgviewer
blockcompositing=true
blockcompositingrule=2
types=4294967295
wmclass=osg osgviewer
wmclasscomplete=true
wmclassmatch=1
</syntaxhighlight>

== Solution for older KDE versions ==
Disable compositing permanently or temporarily in the KDE settings, via the assigned hotkey (normally Shift + Alt + F12) or via a script.

== Caveats ==
With compositing disabled, KDE desktop effects don't work anymore.

== Example ==
'''WARNING:''' This method is obsolete, and is only left here as a convenience for those using very old versions of KDE.

This example by i4dnf deactivates compositing, starts Flightgear and reactivates compositing after Flightgear ended.
<syntaxhighlight lang="bash">
#!/bin/sh
qdbus org.kde.kwin /KWin toggleCompositing && /usr/games/bin/fgfs $@ && qdbus org.kde.kwin /KWin toggleCompositing
</syntaxhighlight>

== See also / related ==
* [http://forum.flightgear.org/viewtopic.php?f=37&t=15390&p=152496#p152488 Forum post by i4dnf]

[[Category:Knowledge_Base|Graphics, bad performance, KDE]]

Rallye-MS893E/info

2019-09-07T09:37:37Z

Axlerate: Spaced category from infobox

<includeonly>{{infobox aircraft
| name = Socata Rallye MS-893E
| hangar = fgaddon
| aircraft = rallye-MS893
| image = rallye-MS893.jpg
| image2 = Rallye-MS893-cockpit.png
| type = Civil aircraft/Civil utility aircraft/Glider tug
| config = Low wing aircraft
| propulsion = Propeller aircraft/Single-engine aircraft
| manufacturer = SOCATA
| authors = Patrice Poly (3D, FDM)/Beber (Sounds)
| fdm = Yasim
| fgname = rallye-MS893
| status = Alpha
| ready = aerotow
| navbar = 1
}}</includeonly><noinclude>
This is the aircraft infobox subpage of the [[Rallye-MS893E]].

[[Category:Aircraft infobox documentation]]
</noinclude>

Bell Boeing V-22 Osprey

2019-09-07T09:36:53Z

Axlerate: Fixed grammatical errors using Grammarly

{{:{{PAGENAME}}/info}}
{{for|unfinished and abandoned development model in [[FGAddon]]|Bell Boeing VMX22-Osprey}}
[[File:v22inflight.jpg|thumb|270px|The V-22 in flight.]]
[[File:v22cockpit3.jpg|thumb|270px|A wider view of the detailed cockpit with pilot figure.]]
[[File:V22_fold.jpg|thumb|270px|The V22 with folded wings.]]
The '''V22 Osprey''' is not a plane, nor a [[helicopter]]: it is a tiltrotor [[aircraft]], so it's both!

== Summary ==
The V-22 Osprey is an interesting aircraft, and the FlightGear model is a fully functional, instrumented model that is relatively easy to fly.

== First Flight ==
The first thing to do is to start the engines by pressing and holding down the } key. The rotors take a while to start. The rotors slowly increase in speed until they become a blur.

The simplest take- off is a vertical one. Make sure the controls are absolutely centered before starting otherwise the aircraft will roll and crash into the tarmac.
Increase the rotor pitch by pressing the "Page Down" key. Yes, that's right, "Page Down". For some reason, page up decreases the pitch of the blades or the power. Press the "Page Down" key and watch the aircraft climb vertically into the sky.

Once you are up to a good height, say 2,000 ft, slowly test the controls. The left stick makes the aircraft roll to the left but starts yaw as well probably due to the airflow hitting the tail surfaces, which means that now you are spinning like a top at 2,000 ft and going nowhere. To stop the spinning, use opposite stick, that is, stick to the right. Rudder controls will work as well, I suppose but I did not try them.

On my second flight, once again I had to correct rotation to the left using right aileron, very gently, to get the V-22 pointing in one direction. A little forward speed was gained by tilting the rotor forward, progressively. At this point, a strong pitch up was encountered, and after a struggle, the level flight was restored. The rotors were tilted progressively forwards, and the aircraft gained speed without losing height. Pitch changes were easily controlled this time.

With the rotors at a full-forward tilt, the V-22 behaved like a fixed-wing aircraft, although ailerons were a bit slow to respond, stable turns could be made.

On the first flight, the landing was easier than I thought, from a vertical hover, the spinning stopped, I lowered power until a comfortable 2,000 ft per minute descent was indicated on the lower right instrument. A slight forward velocity was also experienced, which I left without checking. At the last moment, I increased power and slowed descent to 200 fpm and landed solidly.

The descent is the most stable and pleasant part of the flight for me. The V-22 will fly hands-off in a descent, almost. I established a 2,000 fpm descent and descended all the way down to the ground, landing on a roadway at about 40kt forward speed and about 2,000 fpm, which is slightly excessive. 400 fpm is the maximum that would be comfortable, I would think. Once I have the 'collective pitch' figured out this should be easy.

I would prefer if left and right stick resulted in roll only, with automatic compensation for yaw, however this probably a design feature to make it fly like a helicopter.

After two flights, this is definitely an aircraft I want to fly again, with its fascinating VTOL capability, impressive looks, attractive digital cockpit, and decent handling. One could really go places in this one.

All in all, a fascinating aircraft, nicely modeled, with an excellent cockpit. This one brings out all that is best in FlightGear.

=== Compatibility ===
* FlightGear 1.9.1.: Loads and runs
* FlightGear 2.0: Not Tested
* FlightGear 2.4: Not Tested
* FlightGear 2.6: Not Tested
* FlightGear 2017.1.3: Loads and runs

== Aircraft help ==
{| class="keytable"
!Key
!Function
|-
| {{key press|} }}
| Start engines
|-
| {{key press|{}}
| Stop engines
|-
| {{key press|PageUp}}
| Increase power
|-
| {{key press|PageDown}}
| Decrease power
|-
| {{key press|m}}
| Tilt rotors forward by 10 degrees
|-
| {{key press|M}}
| Tilt rotors afterward by 10 degrees
|-
| {{key press|Alt|M}}
| Tilt rotors vertical
|-
| {{key press|n}}
| Unfold wing
|-
| {{key press|N}}
| Fold wing
|}

* The tilt range is -10deg .. 0deg (vertical) .. 90deg (horizontal)
* The allowed tilt range is a function of the aircraft's speed.
* The flight computer limits the actual tilt to this range.
* Therefore you can lift off with vertical rotors and accelerate like a helicopter.
* The computer will increase the tilt with increasing airspeed.
* For faster acceleration set the tilt to the maximum.
* The Osprey can hover within a range of -10deg to 30deg.
* You can set the tilt to horizontal/90deg on the ground. Due to the lack of speed, the tilt is limited to 30deg max.

== External Links ==
* [http://www.boeing.com/rotorcraft/military/v22/index.htm Boeing.com V-22]

{{Bell}}
{{Boeing}}

FSweekend 2013

2019-09-07T09:31:34Z

Axlerate: Spaced the headers back

This wiki page lists all information related to [[FlightGear]]'s [[FSweekend]] 2013 attendance, as well as information for those that would like to pay a virtual visit. FlightGear will be represented by a team of regular FlightGear developers.
<font size="5">'''FSweekend'''</font> at 2&3 November 2013.

== Booth information ==
=== Equipment Checklist ===
== Flight information ==
=== Airports ===
[[File:EHLE_schipholgebouw.png|thumb|270px|The old terminal of Schiphol (1928), now located at EHLE.]]
Activities will mainly take place at and around [[Amsterdam Airport Schiphol]] (EHAM) and [[Lelystad Airport]] (EHLE).

=== Charts ===
All charts that you may have to use on your flights are available at http://ais-netherlands.nl (AIS Publications > Integrated Package). Please note that these are the most up to date charts available, so certain situations might not have been changed in FlightGear (EHAM, EHLE and EHVK taxiways should be correct though).

Parking positions have been created for most of the Dutch airports including EHAM, EHRD, EHVK, and EHLE (A1-A6, B1, and B2).

=== Weather information ===
Real-life weather information can be found at the KNMI (Dutch Meteorological Institute) website.
* [http://knmi.nl/actueel/metar.html METAR] current weather at airports
* [http://knmi.nl/waarschuwingen_en_verwachtingen/luchtvaart/nederlandse_vliegveldverwachtingen.html TAF] expected weather at airports
If the weather is really bad, it is likely that the FSweekend guys will use a preset weather scenario.

== External links ==
* [http://www.fsweekend.com Official FSweekend website]

[[Category:FSweekend]]

Howto:Place 3D objects with the UFO

2019-09-07T09:29:35Z

Axlerate: Spaced the headers back

The [[UFO from the 'White Project' of the UNESCO|UFO]] aircraft is a superb tool for placing a new (or old) 3D object at any arbitrary location in the scenery with just a few clicks of the mouse. Placing objects in the scenery is a really easy way to contribute to the [[FlightGear]] project. It does not require any programming knowledge, and you can contribute something valuable in just a few minutes.

This article gives an overview of placing, editing and saving objects using the UFO. You can get a list of flying controls and editing commands by pressing the {{key press|?}} key while flying the UFO.

== Choosing your object ==
The first thing you need is a 3D model to place in the scenery. The [[FlightGear Scenery Database]] ([http://scenemodels.flightgear.org/ scenemodels.flightgear.org]) maintains a huge library of generic models, which will have been included in your FlightGear installation under the <tt>[[$FG_ROOT]]/Models/</tt> directory. You can skip to the next section when using a generic model.

=== Consider the file sizes ===
If you add many complex models or models with big textures to the scenery it ''will'' increase the memory usage and slow down FlightGear.
Here are two lists with shared models and shared model textures sorted by file size:
* [[Shared models sorted by file size]]
* [[Textures of shared models sorted by file size]]

=== Creating your own models ===
Alternatively, you can create your own models. You should save it in a subdirectory of your [[$FG_ROOT]] folder. Two options seem reasonable, although others are possible as well:
* Shared model, not unique to a single objects (for example a wind turbine): save it in a subdirectory of <tt>[[$FG_ROOT]]/Models/</tt>. That is the standard directory where the UFO will go when you press the space bar {{Key press|Space}}.
* Static model, unique object (like the Eiffel Tower): save it in the respective subdirectory of the Scenery folder, e.g. <tt>[[$FG_ROOT]]/Scenery/Objects/w130n30/w123n37</tt>. To browse objects anywhere on your computer, press {{key press|L}} when using the UFO.

When creating your own object, make sure it is the correct size. In [[Blender]], units are meters. Note that you should be careful about using Google Earth, due to restrictions in their license that might prevent submitting your work to the FlightGear database. See {{forum link|t=3356|text=here}} and {{forum link|t=3415|text=here}}.

== Selecting the UFO ==
[[File:Placing_objects_with_UFO_html_m49fbed81.jpg|400px]]

Now start FlightGear with the UFO as your aircraft and enable the console, which is needed later on. When launching FlightGear from command line, use <code>--aircraft=ufo --console</code>. In [[FGRun]], the "Show console" option on the last page should be checked.

== Placing objects ==
Once FlightGear has been started, fly with the UFO to roughly the place you want the model to be positioned.

[[File:Placing_objects_with_UFO_html_5fa8d7b1.jpg|400px]]

Let's say we want to position the catii-iii.xml object at the end of a taxiway. We stop the UFO just above this intersection and press the space key. A Select Model window will open up where the contents of the <tt>[[$FG_ROOT]]/Models/</tt> directory will be shown (or press {{key press|Shift}}+{{key press|L}} and you can go to any desired directory). Select your preferred model from this list, then close the window. The selected model path/name will be displayed in green text at the bottom left of the FlightGear screen.

[[File:Placing_objects_with_UFO_html_m184fb381.jpg|400px]]

To place the object, simply left-click on the position that you want to place it. By default, it is placed completely horizontal and rotated to point north. It will probably not have the correct orientation and it might be partly covered by the surrounding terrain, but we can adjust that.

[[File:Placing_objects_with_UFO_html_12ee70a1.jpg|400px]]

=== Rotating objects ===
Fly closer to the ground with the UFO, so that you can see it better.

Now press {{key press|{{=}}}} (earlier versions than 3.0 uses {{key press|Tab}}) and use the resulting sliders to adjust the latitude/longitude/elevation/heading of the model. NB: "Pitch" and "roll" will not be saved, so using them might be fun, but won't help eventually.

[[File:Placing_objects_with_UFO_html_439816e9.jpg|400px]]

See the [[UFO from the 'White Project' of the UNESCO]] page for more information on the UFO command keys and exported file locations, or press {{key press|?}} while in FlightGear.

=== Deleting objects ===
There are three different ways to three different situations in which which you want to delete an object:
You want to delete the last object that you placed in this session:
: Press the [http://en.wikipedia.org/wiki/Backspace backspace button].
You want to delete an object that you placed in this session, but you have placed one or two models after it:
: That means that it is no longer active. Activate it by placing one more model '''on''' the object you want to delete, press the backspace button. Result: The model you want to delete starts blinking, which tells you that it is active.
You want to delete an object that is already saved in the corresponding .stg file and you don't know where it is:
: You don't know the filename: The model you want to delete is probably a shared model. You find it in the [http://scenemodels.flightgear.org/ scenery database]. Now you know the model's filename (e.g. [http://scenemodels.flightgear.org/modeledit.php?id=45 generic_skyscraper_01.ac] or [http://scenemodels.flightgear.org/modeledit.php?id=537 Office26x22.xml]).
: You still need to know where you find it. Place any model on that building and press {{key press|D}} to know in which file you find it (see [[#Exporting the result|Exporting the result]] below). If there are several objects of that type and you want to delete only one of them, find the one closest to the coordinates of your model placed on top.
: Open the .stg file, delete the whole model entry (see [[#Exporting the result|Exporting the result]] below). Done.

== Exporting the result ==
Now that the model is correctly positioned, press the {{key press|D}} key to dump the model position data to the terminal. A few lines will be printed on the console, providing the necessary orientation data.

[[File:Placing_objects_with_UFO_html_m4cf0cbf7.jpg]]

The most important lines are the last ones:
# e000n50/e008n50/3089154.stg
OBJECT_SHARED Models/Tabu/catii-iii.xml 8.57928135 50.03667992 105.9972 111.1

The first line identifies the location of the scenery file for the object. The OBJECT_SHARED line indicates the object's name, longitude, latitude, altitude, and orientation. This can be read by FlightGear itself and can be [http://scenemodels.flightgear.org/contribute.php submitted] to the FlightGear Scenery Object Database.

You can also save these coordinates into your own scenery file so that your changes will not be lost the next time you start FlightGear.

=== Saving the changes to your scenery ===
In the terminal window, you get three sections printed out by the UFO with very detailed information about what's going on. We need the lines at the end.

As noted above, the UFO helpfully exports the name of the scenery file where the object's coordinates have to be saved. In our example: e000n50/e008n50/3089154.stg

The default location for scenery objects is <tt>[[$FG_SCENERY]]/Objects/</tt>. Simply open the referenced .stg file, add the OBJECT_SHARED line to the bottom and save the file. Now you have your object's position saved, and it will appear inside the scenery every time you start FlightGear! There is one pitfall here. If TerraSync is enabled, which is the default in latest FlightGear versions, and you modified the stg file in the TerraSync folder, your modifications might be overridden by the syncing process. You might need to add the startup option --disable-terrasync for avoiding this and to keep your modifications.

In our example we would open in <tt>[[$FG_SCENERY]]/Objects/e000n50/e008n50/3089154.stg</tt> and add the following line:
OBJECT_SHARED Models/Tabu/catii-iii.xml 8.57928135 50.03667992 105.9972 111.1

For a short video demonstrating the .stg method, see the following video:
{{#ev:youtube|i2BSUOMyiIg|400|center}}

If you are running Windows OS, then please refer to this video:
{{#ev:youtube|e93OUEp0YKc|400|center}}

=== Saving to XML ===
Alternatively, if you press the {{key press|E}} key while developing scenery with UFO, FlightGear will generate an XML file with the dump of your current work in an "ufo-model-export.xml" file under [[$FG_HOME]].

=== Loading the XML file as part of FlightGear scenery ===
You can later reload this XML file with --config= command-line parameter:
Example for Linux: fgfs --config=$HOME/.fgfs/Export/ufo-model-export.xml

In Windows, this is done using the Advanced dialog, found on the last page of the [[FGRun]] GUI. Click Advanced and, under General, click the double-dot button, browse to the ufo-model-export.xml file and click OK.

== Sharing your updates with everyone! ==
Please, once you've improved the scenery around your place, consider sharing it with the community. This is done very easily using our [http://scenemodels.flightgear.org/submission scenery submission webforms]. More information and help on {{forum link|t=14671|text=the dedicated topic}} on the scenery forum.

[[Category:Howto]]
[[Category:Scenery enhancement]]
[[ar:Howto:Place 3D objects with the UFO]]
[[es:Colocar objetos con el UFO]]
[[fr:Placer des objets 3D avec UFO]]

Changelog 2.4.0

2019-09-07T09:26:50Z

Axlerate:

{{changelogs|next=2.6.0}}
The FlightGear development team is happy to announce the release of FlightGear 2.4.0. This new version contains many exciting new features, enhancements, bug fixes, and other improvements.

After adopting the newly available shader technology in 2.0.0, FlightGear’s graphical quality has been substantially improved. Besides that, assorted highlights of this version include: a configurable local weather system, many new and improved aircraft, and numerous scenery additions.

=== Some of the major changes include: ===
'''Aircraft operations:'''
* A new head-up display (HUD) system
* An in-sim moving map
* ATC/ATIS improvements
* EICAS instruments are available on a selected number of aircraft
* Improved autopilots
* TCAS works with AI and multiplayer aircraft provides aural warnings for conflicting traffic and is also capable of driving a realistic traffic display. AI aircraft also respond to TCAS alerts and take evasive action
* Updates to the KLN89 GPS.
* tanker now refuels with any callsign and can enable/disable refueling in flight.

'''AI system'''
* A standalone AI flight plan generator program
* Approaching aircraft now follow realistic approach trajectories
* Ballistic objects can slave to any AI object
* Improved AI ballistics behavior
* More communication/interaction between AI aircraft and ground. Support for multiple frequencies for AI/ATC interaction.
* Speed-up for AI traffic initialization by means of an aircraft usage statistics collection mechanism

'''AI Traffic'''
* General and commercial aviation traffic at LOWI airport
* Malaysian Airways / Kuala Lumpur based traffic
* Traffic for Adria (Croatia)

'''Flight dynamics'''
* A new MIL-STD Turbulence model has been added to the JSBSim flight dynamics simulation engine

'''Environment'''
* A local weather system to simulate physically correct local weather phenomena
* Discard of outdated METAR weather information sources and improved METAR parsing
* New Fog layers with limited elevation
* Scenery can be downloaded and installed on-the-fly via an in-sim TerraSync interface
* Specific multiplayer pilots can be selectively ignored

'''Interface'''
* Complete overhaul of the autopilot system
** New digital controllers
** Flexible use of input and output values
** Support for mathematical expressions
** Usable for generic numeric data processing as a "property rule" system
* Better integration of separate weather systems
* New support of draggable 3d objects like throttle-levers
* Support for textures generated from VNC clients
* Unified runway selection code that is shared between user-controlled and AI-controlled aircraft
* New HLA interface for distributed simulations
* New on-demand loading of Nasal modules
* New support for external (aka real) Garmin 400/500 WAAS Units
* Optional automatic selection of nearest tower for external 'tower view'

'''Highlighted new and improved aircraft'''
* A new and highly detailed IAR-80 (a Romanian-produced WW2 fighter)
* A new highly detailed Piper Cub
* Airbus A320 Family (318/319/320/321)
* An improved P-51D, completely remodeled and containing improved flight dynamics
* Boeing 717
* Boeing 757-200
* Bombardier CRJ700 Series (700/900/1000)
* Bombardier CRJ200
* Douglas A-4F Skyhawk
* Improvements to the Boeing 787
* MiG-15bis
* PZL-Mielec M18B "Dromader"
* Short S.23 Empire flying boat
* The Boeing 737NG Series
* The Boeing 747-400 and 777-200 have received lots of improvements
* The Douglas DC-8 Series
* The Eurocopter EC130 B4 Helicopter
* Tyre smoke effects on many aircraft
* Zeppelin LZ 121 Nordstern

'''Navigation'''
* A new route manager
* Autopilots can be driven by NAV or GPS instruments

'''Project infrastructure'''
* Change to Git as a revision control system
* Moved to make based build system
* Set up [http://flightgear-bugs.googlecode.com a bug tracker]
* Support for automatic nightly snapshot releases
* Support for placing add-on aircraft in a separate aircraft directory, separate from the main data directory

'''Scenery improvements'''
* Animated jetways
* (Are all of the following in scene models?)--[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)
* Improvements to the Innsbruck area, Austria
* Las Vegas McCarran Intl. Airport
* London Gatwick Airport
* Many buildings for small airports in the Italian Alps
* Many contributions to the Switzerland area, including building models and shapefiles for future terrain improvements
* Many historic and current launch sites have been added to the Kennedy Space Center Area, including some AI-controlled rocket launches
* The city of Dubai (terrain, city buildings, and AI traffic)
* <s>Time dependent placement of buildings.</s> What is this? --[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)

'''Visual effects'''
* Various graphics improvements using shaders, including 3D urban effects, reflections, water, rock textures, lightmaps, skydome scattering
* Easy GUI-based access to a host of stereoscopic 3D rendering effects
* Panoramic distortion (Is this really implemented?)--[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)
* Persistent contrails
* New standalone 2D-Panel rendering utility

'''Bug fixes'''
* Fixed METAR live weather (http requests from NOAA)
* Fixed many sources of the infamous NaN errors
* Improved stability by fixing many segmentation faults, deadlocks and memory leaks
* Improved placement of random objects
* Fixed inconsistencies with scenery tile scheduling
* The replay system now works again as advertised
* The ground proximity warning system (GPWS) works reliably now
* Runway lights also working with ATI graphics cards now (rendering option to disable point-sprites)
* Many, many more. See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.4.0 our bugtracker] for an extensive list

[[Category:FlightGear changelogs]]

Changelog 2.4.0

2019-09-07T09:26:03Z

Axlerate: Spaced the headers back

{{changelogs|next=2.6.0}}
The FlightGear development team is happy to announce the release of FlightGear 2.4.0. This new version contains many exciting new features, enhancements, bug fixes, and other improvements.

After adopting the newly available shader technology in 2.0.0, FlightGear’s graphical quality has been substantially improved. Besides that, assorted highlights of this version include: a configurable local weather system, many new and improved aircraft, and numerous scenery additions.

=== Some of the major changes include: ===
'''Aircraft operations:'''
* A new head-up display (HUD) system
* An in-sim moving map
* ATC/ATIS improvements
* EICAS instruments are available on a selected number of aircraft
* Improved autopilots
* TCAS works with AI and multiplayer aircraft provides aural warnings for conflicting traffic and is also capable of driving a realistic traffic display. AI aircraft also respond to TCAS alerts and take evasive action
* Updates to the KLN89 GPS.
* tanker now refuels with any callsign and can enable/disable refueling in flight.

'''AI system'''
* A standalone AI flightplan generator program
* Approaching aircraft now follow realistic approach trajectories
* Ballistic objects can slave to any AI object
* Improved AI ballistics behavior
* More communication/interaction between AI aircraft and ground. Support for multiple frequencies for AI/ATC interaction.
* Speed-up for AI traffic initialization by means of an aircraft usage statistics collection mechanism

'''AI Traffic'''
* General and commercial aviation traffic at LOWI airport
* Malaysian Airways / Kuala Lumpur based traffic
* Traffic for Adria (Croatia)

'''Flight dynamics'''
* A new MIL-STD Turbulence model has been added to the JSBSim flight dynamics simulation engine

'''Environment'''
* A local weather system to simulate physically correct local weather phenomena
* Discard of outdated METAR weather information sources and improved METAR parsing
* New Fog layers with limited elevation
* Scenery can be downloaded and installed on-the-fly via an in-sim TerraSync interface
* Specific multiplayer pilots can be selectively ignored

'''Interface'''
* Complete overhaul of the autopilot system
** New digital controllers
** Flexible use of input and output values
** Support for mathematical expressions
** Usable for generic numeric data processing as a "property rule" system
* Better integration of separate weather systems
* New support of draggable 3d objects like throttle-levers
* Support for textures generated from VNC clients
* Unified runway selection code that is shared between user-controlled and AI-controlled aircraft
* New HLA interface for distributed simulations
* New on-demand loading of Nasal modules
* New support for external (aka real) Garmin 400/500 WAAS Units
* Optional automatic selection of nearest tower for external 'tower view'

'''Highlighted new and improved aircraft'''
* A new and highly detailed IAR-80 (a Romanian-produced WW2 fighter)
* A new highly detailed Piper Cub
* Airbus A320 Family (318/319/320/321)
* An improved P-51D, completely remodeled and containing improved flight dynamics
* Boeing 717
* Boeing 757-200
* Bombardier CRJ700 Series (700/900/1000)
* Bombardier CRJ200
* Douglas A-4F Skyhawk
* Improvements to the Boeing 787
* MiG-15bis
* PZL-Mielec M18B "Dromader"
* Short S.23 Empire flying boat
* The Boeing 737NG Series
* The Boeing 747-400 and 777-200 have received lots of improvements
* The Douglas DC-8 Series
* The Eurocopter EC130 B4 Helicopter
* Tyre smoke effects on many aircraft
* Zeppelin LZ 121 Nordstern

'''Navigation'''
* A new route manager
* Autopilots can be driven by NAV or GPS instruments

'''Project infrastructure'''
* Change to Git as a revision control system
* Moved to make based build system
* Set up [http://flightgear-bugs.googlecode.com a bug tracker]
* Support for automatic nightly snapshot releases
* Support for placing add-on aircraft in a separate aircraft directory, separate from the main data directory

'''Scenery improvements'''
* Animated jetways
* (Are all of the following in scene models?)--[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)
* Improvements to the Innsbruck area, Austria
* Las Vegas McCarran Intl. Airport
* London Gatwick Airport
* Many buildings for small airports in the Italian Alps
* Many contributions to the Switzerland area, including building models and shapefiles for future terrain improvements
* Many historic and current launch sites have been added to the Kennedy Space Center Area, including some AI-controlled rocket launches
* The city of Dubai (terrain, city buildings, and AI traffic)
* <s>Time dependent placement of buildings.</s> What is this? --[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)

'''Visual effects'''
* Various graphics improvements using shaders, including 3D urban effects, reflections, water, rock textures, lightmaps, skydome scattering
* Easy GUI-based access to a host of stereoscopic 3D rendering effects
* Panoramic distortion (Is this really implemented?)--[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)
* Persistent contrails
* New standalone 2D-Panel rendering utility

'''Bug fixes'''
* Fixed METAR live weather (http requests from NOAA)
* Fixed many sources of the infamous NaN errors
* Improved stability by fixing many segmentation faults, deadlocks and memory leaks
* Improved placement of random objects
* Fixed inconsistencies with scenery tile scheduling
* The replay system now works again as advertised
* The ground proximity warning system (GPWS) works reliably now
* Runway lights also working with ATI graphics cards now (rendering option to disable point-sprites)
* Many, many more. See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.4.0 our bugtracker] for an extensive list

[[Category:FlightGear changelogs]]

User:Axlerate

2019-09-07T09:23:59Z

Axlerate: Add

Hello.

I'm here for anti-vandalism work.

I also have an interest in fixing any grammatical errors around here.

I am also a friendly editor here, as I don't bite, probably to the vandals. (Hoping to become an admin here too!)

Any questions, comments, suggestions, concerns, discussions, enquiries, etc,.? Post them on my talk page, or send them via email at dovewindsor@gmail.com.

User talk:Johan G

2019-09-07T09:23:17Z

Axlerate: /* Introduction */

{{Archives|[[/Archive 2011-2015|2011-2015]]}}
{{Welcome to the wiki|name=Johan|added-by=Johan G}}{{-}}

== Newsletter drafts ==
Hi Johan. Would it be possible for you to create the "draft" newsletters up to December? Not sure of the exact format, don't want to mess things up ;)
[[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 08:22, 25 October 2017 (EDT)

: With a bit of luck I could give it a try tomorrow.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:36, 28 October 2017 (EDT)

:: Sorry for my delays. At some point (probably some weekend) I aim to implement what have been [http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=111694 discussed at the Village Pump recently] regarding using preloaded pages. In essence making a single click link to create a draft of the next newsletter. (Unless someone is quicker on that than me...)

:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 5 November 2017 (EST)

:: An early newsletter template draft is now available in my sandbox.
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:08, 11 November 2017 (EST)

== Progress bar and icons ==

Hi Johan. I was wondering if you could upload a new set of [[:Category:Progress icons|progress bar icons]]? Half of the current set have been lost from the wiki backend, so scaled icons are broken. See {{tl|progressbar}} where a number of these graphics are shown as the text: '''Error creating thumbnail: File missing'''. For two of these, I have manually recreated bitmap versions. Maybe it would be good to upload the SVG originals? I have been using scaled versions of these via the {{tl|progressbar}} template for the [http://wiki.flightgear.org/index.php?title=Translation_requests&oldid=113443 current version of the translation requests page]. For better table packing, I am wondering if we should introduce a {{param|vertical}} parameter for this template and have a full set of vertical icons, as a copy of your progress icons rotated 90 degrees.

[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:02, 29 December 2017 (EST)

: I feel I need to apologize for not doing this literally years ago. I have finally gotten around to reupload these particular missing files. It seems likely that they have been missing ever since the wiki crashed when the ISP migrated the wiki's virtual server to new hardware back in late January 2015 (see the forum topic [https://forum.flightgear.org/viewtopic.php?f=42&t=25209 wiki.flightgear.org scheduled downtime] for the details.)

: As for vertical ones, I am not there yet, but I think just turning them vertical would make them nearly unreadable. I have some ideas, but is as often slow to implement them.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 09:27, 19 May 2018 (EDT)

: Have done a test with vertical ones. Even reading out 20% steps is hard in normal running text. 1/3rds maybe are possible. Could probably be better to have a compact 20%-step version of the horizontal one instead.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:24, 19 May 2018 (EDT)

== Introduction ==
Hello. Who is in charge around here? --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 10:23, 6 September 2019 (EDT)

: Well, the wiki is maintained/run by [[User talk:Hellosimon|Hellosimon]] and there are [http://wiki.flightgear.org/Special:ListGroupRights some users with more rights than others], but like many other things in FlightGear there is not really anyone "in charge" (several times some of us has described us as "a heard of cats").
: Is there anything, in particular, you would like help with?
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:11, 6 September 2019 (EDT)

: I took the liberty to add the {{tl|welcome to the wiki}} template with some tips and hints to your discussion page. I hope you do not mind.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:17, 6 September 2019 (EDT)

:: Is it okay for me to have admin privileges to improve protected pages? Plus, I have not spaced any more headers from the text. I have also reverted them back. --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 05:22, 7 September 2019 (EDT)

User talk:Johan G

2019-09-07T09:22:31Z

Axlerate: /* Introduction */

{{Archives|[[/Archive 2011-2015|2011-2015]]}}
{{Welcome to the wiki|name=Johan|added-by=Johan G}}{{-}}

== Newsletter drafts ==
Hi Johan. Would it be possible for you to create the "draft" newsletters up to December? Not sure of the exact format, don't want to mess things up ;)
[[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 08:22, 25 October 2017 (EDT)

: With a bit of luck I could give it a try tomorrow.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:36, 28 October 2017 (EDT)

:: Sorry for my delays. At some point (probably some weekend) I aim to implement what have been [http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=111694 discussed at the Village Pump recently] regarding using preloaded pages. In essence making a single click link to create a draft of the next newsletter. (Unless someone is quicker on that than me...)

:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 5 November 2017 (EST)

:: An early newsletter template draft is now available in my sandbox.
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:08, 11 November 2017 (EST)

== Progress bar and icons ==

Hi Johan. I was wondering if you could upload a new set of [[:Category:Progress icons|progress bar icons]]? Half of the current set have been lost from the wiki backend, so scaled icons are broken. See {{tl|progressbar}} where a number of these graphics are shown as the text: '''Error creating thumbnail: File missing'''. For two of these, I have manually recreated bitmap versions. Maybe it would be good to upload the SVG originals? I have been using scaled versions of these via the {{tl|progressbar}} template for the [http://wiki.flightgear.org/index.php?title=Translation_requests&oldid=113443 current version of the translation requests page]. For better table packing, I am wondering if we should introduce a {{param|vertical}} parameter for this template and have a full set of vertical icons, as a copy of your progress icons rotated 90 degrees.

[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:02, 29 December 2017 (EST)

: I feel I need to apologize for not doing this literally years ago. I have finally gotten around to reupload these particular missing files. It seems likely that they have been missing ever since the wiki crashed when the ISP migrated the wiki's virtual server to new hardware back in late January 2015 (see the forum topic [https://forum.flightgear.org/viewtopic.php?f=42&t=25209 wiki.flightgear.org scheduled downtime] for the details.)

: As for vertical ones, I am not there yet, but I think just turning them vertical would make them nearly unreadable. I have some ideas, but is as often slow to implement them.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 09:27, 19 May 2018 (EDT)

: Have done a test with vertical ones. Even reading out 20% steps is hard in normal running text. 1/3rds maybe are possible. Could probably be better to have a compact 20%-step version of the horizontal one instead.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:24, 19 May 2018 (EDT)

== Introduction ==
Hello. Who is in charge around here? --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 10:23, 6 September 2019 (EDT)

: Well, the wiki is maintained/run by [[User talk:Hellosimon|Hellosimon]] and there are [http://wiki.flightgear.org/Special:ListGroupRights some users with more rights than others], but like many other things in FlightGear there is not really anyone "in charge" (several times some of us has described us as "a heard of cats").
: Is there anything, in particular, you would like help with?
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:11, 6 September 2019 (EDT)

: I took the liberty to add the {{tl|welcome to the wiki}} template with some tips and hints to your discussion page. I hope you do not mind.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 13:17, 6 September 2019 (EDT)

:: Is it okay for me to have admin privileges to improve protected pages? --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 05:22, 7 September 2019 (EDT)

Submitting Screenshots

2019-09-07T09:20:50Z

Axlerate: Fixed grammatical errors using Grammarly. Did not remove the space equal headers from the sub headers

{{mergeto|Howto:Make nice screenshots|Howto talk:Make nice screenshots#Merging Submitting Screenshots into this page|date=January 2014}}
{{Draft}}
The FlightGear project always needs screenshots for the website, which show features that were added since the last release. These shots should be of good quality -- regarding contents and technical image properties. It is therefore recommended to use the best viable filter settings (antialiasing, texture sharpening, etc.). Screenshots should only show features that are actually available to the public, not models that are private and can't be distributed due to a non-GPL-compatible, restrictive license, etc.

'''By submitting a screenshot the submitter agrees to these terms:'''
* The creator of the screenshot retains full ownership and copyright.
* The creator grants the FlightGear project revocable and non-exclusive copyright, which permits the project
** To add a copyright notice to the screenshot, which denotes the FlightGear project as a copyright holder[1],
** To persecute copyright infringement on behalf of the screenshot creator[2].
* The creator grants anyone the non-revocable, perpetual right
** To use the screenshot for private, non-commercial purposes,
** To use the screenshot in articles ''about'', and reviews, announcements, documentation and promotion ''of'' the FlightGear simulator, provided that
*** The simulator is presented under its official name "FlightGear",
*** It is mentioned in that work that the simulator is Free and licensed under the GPL (GNU General Public License),
*** The screenshot remains unchanged, with the sole exception of optional scaling.

ad 1: This is meant to guarantee the consistent look and easier maintenance, and to strengthen the project's position in cases of 2.<br />
ad 2: This should make it easier to demand of infringers that they take all screenshots down from a web page. We can't do that if we don't have a mandate. This is not a promise that the project ''will'' persecute infringement. We'd probably use other means to achieve the goal. :-)

'''On the screenshot page, there would be a copyright notice like the following:'''
All screenshots displayed on this website are copyright of their respective creators. Permission is granted to anyone
* To use the screenshots for private, non-commercial purposes
* To use the screenshots in articles ''about'', and reviews, announcements, documentation and promotion ''of'' the FlightGear simulator, provided that:
** The simulator is presented under its official name "FlightGear",
** It is mentioned in that work that the simulator is Free and licensed under the GPL (GNU General Public License),
** The screenshots remain unchanged, with the sole exception of optional scaling.

== Related content ==
* [[Howto:Make full spherical panorama]]
* [[Howto:Make nice screenshots]]

[[Category:FlightGear]]

Template:Welcome to the wiki

2019-09-07T09:16:52Z

Axlerate:

<div style="width: 75%; margin-left: 5%; background: #eeeeff; padding: 10px; border-color: #8888ff; border-style: solid; border-width: 1px; text-align: left;">{{LangSwitch
| en = 
<big>'''Welcome to the wiki, {{#if: {{{name|}}} | {{{name}}} | {{BASEPAGENAME}}}}!'''</big>

We hope you will enjoy your stay!

If you need some help in general, do not be afraid to ask your questions at [[FlightGear wiki:Village pump]].

Please remember to sign your messages on talk pages by typing four tildes (<nowiki>~~~~</nowiki>); this will automatically insert your username and the date.

Some links that may be of help (you can find more of them at [[Help:Contents]]):

{{{!}}
! Useful pages to get you started !! These might be useful too
{{!-}}
{{!}} style="vertical-align: top;" {{!}}
* [[Help:Tracking changes]] - Ways to follow changes on the wiki
* [[Help:Discussion pages]] - Using discussion pages
* [[Help:Your first article]] - Well worth skimming through even if you do not feel ready yet
* [[Help:Categories]] - Using categories
* [[Help:Upload]] - Image uploading
{{!}} style="vertical-align: top;" {{!}}
* [[Help:Main navigation elements]] - Tools available on all pages
* [[Help:Namespaces]] - What are namespaces?
* [[Help:Translate]] - You can help translating wiki pages
* [[Help:Maintenance]] - Overview of the maintenance work you can help with
* [[Help:Glossary]] - Wiki terminology
* [[FlightGear wiki:Manual of Style]] - The Style Manual

Again, welcome!
{{!}}}
{{#if: {{{non-manual|}}}
||

<small>''This template was added manually by {{#if: {{{added-by|}}} | {{usr|{{{added-by}}}}} | another user}}.''</small>}}
















| lang = {{{lang|}}}
}}

</div><includeonly>{{#if: {{{nocat|}}} || {{user talk other|[[Category:Users given welcome to the wiki template]]}}}}{{-}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This template is intended to be placed on the top of users discussion pages (<code><nowiki>User talk:<Username></nowiki></code>). New users can be found on [[Special:RecentChanges]] and in the [http://wiki.flightgear.org/index.php?title=Special%3ALog&type=newusers&user=&page=&year=&month=-1&tagfilter=&hide_patrol_log=1&hide_tag_log=1 user creation log].

This will hopefully get users better aquatinted with the wiki's [[Help:Contents|documentation]], features and quirks (and maybe even make them skim through the [[FlightGear wiki:Manual of Style|Manual of Style]]).

Adding this template to a user discussion page will automatically add [[:Category:Users given welcome to the wiki template]] to that page.

== Usage ==
{{obr}}'''Welcome to the wiki''' {{!}}''name='' {{!}}''added-by='' {{!}}''lang='' {{!}}''non-manual='' {{!}}''nocat='' {{cbr}}

All parameters are optional.

; name: You can use a different name than the wiki user name used by default if the user on his user page have stated his real or another name.

; added-by: Your user name (shown in page history anyway)

; lang: Two-letter language code for language to use instead of English.

; non-manual: If not empty the template will not state that it was added manually by another user

; nocat: If not empty the page will not be automatically categorized

== Examples ==
<nowiki>{{Welcome to the wiki}}</nowiki>
{{Welcome to the wiki}}

<nowiki>{{Welcome to the wiki |name=George "Auto" Butterfingers}}</nowiki>
{{Welcome to the wiki |name=George "Auto" Butterfingers}}

<nowiki>{{Welcome to the wiki |added-by=Example user}}</nowiki>
{{Welcome to the wiki |added-by=Example user}}

<nowiki>{{Welcome to the wiki |non-manual=yes}}</nowiki>
{{Welcome to the wiki |non-manual=yes}}
}}

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

Template:Welcome to the wiki

2019-09-07T09:15:42Z

Axlerate: Added most important: Add the four tildes at the end of each message (~~~~) It will automatically insert the time, date and signature

<div style="width: 75%; margin-left: 5%; background: #eeeeff; padding: 10px; border-color: #8888ff; border-style: solid; border-width: 1px; text-align: left;">{{LangSwitch
| en = 
<big>'''Welcome to the wiki, {{#if: {{{name|}}} | {{{name}}} | {{BASEPAGENAME}}}}!'''</big>

We hope you will enjoy your stay!

If you need some help in general, do not be afraid to ask your questions at [[FlightGear wiki:Village pump]].

Please remember to sign your messages on talk pages by typing four tildes (<nowiki>~~~~</nowiki>); this will automatically insert your username and the date.

Some links that may be of help (you can find more of them at [[Help:Contents]]):

{{{!}}
! Useful pages to get you started !! These might be useful too
{{!-}}
{{!}} style="vertical-align: top;" {{!}}
* [[Help:Tracking changes]] - Ways to follow changes on the wiki
* [[Help:Discussion pages]] - Using discussion pages
* [[Help:Your first article]] - Well worth skimming through even if you do not feel ready yet
* [[Help:Categories]] - Using categories
* [[Help:Upload]] - Image uploading
{{!}} style="vertical-align: top;" {{!}}
* [[Help:Main navigation elements]] - Tools available on all pages
* [[Help:Namespaces]] - What are namespaces?
* [[Help:Translate]] - You can help translating wiki pages
* [[Help:Maintenance]] - Overview of the maintenance work you can help with
* [[Help:Glossary]] - Wiki terminology
* [[FlightGear wiki:Manual of Style]] - The Style Manual
{{!}}}
{{#if: {{{non-manual|}}}
||

<small>''This template was added manually by {{#if: {{{added-by|}}} | {{usr|{{{added-by}}}}} | another user}}.''</small>}}
















| lang = {{{lang|}}}
}}

</div><includeonly>{{#if: {{{nocat|}}} || {{user talk other|[[Category:Users given welcome to the wiki template]]}}}}{{-}}</includeonly><noinclude>
{{Informative template|1=
__NOTOC__
== Goal ==
This template is intended to be placed on the top of users discussion pages (<code><nowiki>User talk:<Username></nowiki></code>). New users can be found on [[Special:RecentChanges]] and in the [http://wiki.flightgear.org/index.php?title=Special%3ALog&type=newusers&user=&page=&year=&month=-1&tagfilter=&hide_patrol_log=1&hide_tag_log=1 user creation log].

This will hopefully get users better aquatinted with the wiki's [[Help:Contents|documentation]], features and quirks (and maybe even make them skim through the [[FlightGear wiki:Manual of Style|Manual of Style]]).

Adding this template to a user discussion page will automatically add [[:Category:Users given welcome to the wiki template]] to that page.

== Usage ==
{{obr}}'''Welcome to the wiki''' {{!}}''name='' {{!}}''added-by='' {{!}}''lang='' {{!}}''non-manual='' {{!}}''nocat='' {{cbr}}

All parameters are optional.

; name: You can use a different name than the wiki user name used by default if the user on his user page have stated his real or another name.

; added-by: Your user name (shown in page history anyway)

; lang: Two-letter language code for language to use instead of English.

; non-manual: If not empty the template will not state that it was added manually by another user

; nocat: If not empty the page will not be automatically categorized

== Examples ==
<nowiki>{{Welcome to the wiki}}</nowiki>
{{Welcome to the wiki}}

<nowiki>{{Welcome to the wiki |name=George "Auto" Butterfingers}}</nowiki>
{{Welcome to the wiki |name=George "Auto" Butterfingers}}

<nowiki>{{Welcome to the wiki |added-by=Example user}}</nowiki>
{{Welcome to the wiki |added-by=Example user}}

<nowiki>{{Welcome to the wiki |non-manual=yes}}</nowiki>
{{Welcome to the wiki |non-manual=yes}}
}}

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

User talk:Axlerate

2019-09-07T09:10:35Z

Axlerate: Reply

{{Welcome to the wiki|added-by=Johan G}}
'''Welcome to my talk page.'''

== Checking automated grammar and spelling correction with Grammarly ==
I have looked at some of your initial edits and feel that I need to ask you to not trust Grammarly blindly.

While the very most of the corrections are correct there are some technical terms that Grammarly seems to be unaware of. These are not all that many so far, but they will likely become more.

In [http://wiki.flightgear.org/index.php?title=Changelog_2.4.0&diff=prev&oldid=120263 Changelog 2.4.0] edit:
* "Ballistic objects can slave to any AI object" should still be "Ballistic objects can be slaved to any AI object"
* "Moved to make based build system" should be "Moved to CMake based build system" (See {{wikipedia|CMake}})

Also typically there would be single whitespace between the equal signs and the title, though that is not visible on the rendered page (it makes the wiki markup slightly easier to read).

Apart from checking what Grammarly suggests or does, feel free to go on. Some of the FlightGear wiki users sometimes use all lowercase, odd punctuation, etc. In addition, the [[FlightGear wiki:Manual of Style|Manual of Style]] was not around until 2014, and I am certain most users are still oblivious to its existence. Because of these and some other things the wiki is sometimes a bit of a mess.

I have added the above welcome template to all user discussion pages of users having registered after April this year, in the hope that more of the users will understand how a wiki using MediaWiki typically works, and make them aware of the style guide (which I believe might be loosely based on the style guide of the English Wikipedia). Some of us have looked into having it added automatically to discussion pages of new users and adding it to all existing user discussion pages, similar to how they are used on some language editions of Wikipedia. See also [[FlightGear wiki:Village pump#Welcoming template]] ([http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=119685#Welcoming_template permalink]).

—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:05, 6 September 2019 (EDT)

:@[[User talk:Johan G]] Thank you for the advice! Sorry about removing the white spaces from the equals. Will not do that again, as I now see clealy that it confuses other readers. --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 05:10, 7 September 2019 (EDT)

Howto:Place 3D objects with the UFO

2019-09-06T14:33:28Z

Axlerate: Fixed grammatical errors using Grammarly

The [[UFO from the 'White Project' of the UNESCO|UFO]] aircraft is a superb tool for placing a new (or old) 3D object at any arbitrary location in the scenery with just a few clicks of the mouse. Placing objects in the scenery is a really easy way to contribute to the [[FlightGear]] project. It does not require any programming knowledge, and you can contribute something valuable in just a few minutes.

This article gives an overview of placing, editing and saving objects using the UFO. You can get a list of flying controls and editing commands by pressing the {{key press|?}} key while flying the UFO.

==Choosing your object==
The first thing you need is a 3D model to place in the scenery. The [[FlightGear Scenery Database]] ([http://scenemodels.flightgear.org/ scenemodels.flightgear.org]) maintains a huge library of generic models, which will have been included in your FlightGear installation under the <tt>[[$FG_ROOT]]/Models/</tt> directory. You can skip to the next section when using a generic model.

===Consider the file sizes===
If you add many complex models or models with big textures to the scenery it ''will'' increase the memory usage and slow down FlightGear.
Here are two lists with shared models and shared model textures sorted by file size:
* [[Shared models sorted by file size]]
* [[Textures of shared models sorted by file size]]

===Creating your own models===
Alternatively, you can create your own models. You should save it in a subdirectory of your [[$FG_ROOT]] folder. Two options seem reasonable, although others are possible as well:
* Shared model, not unique to a single objects (for example a wind turbine): save it in a subdirectory of <tt>[[$FG_ROOT]]/Models/</tt>. That is the standard directory where the UFO will go when you press the space bar {{Key press|Space}}.
* Static model, unique object (like the Eiffel Tower): save it in the respective subdirectory of the Scenery folder, e.g. <tt>[[$FG_ROOT]]/Scenery/Objects/w130n30/w123n37</tt>. To browse objects anywhere on your computer, press {{key press|L}} when using the UFO.

When creating your own object, make sure it is the correct size. In [[Blender]], units are meters. Note that you should be careful about using Google Earth, due to restrictions in their license that might prevent submitting your work to the FlightGear database. See {{forum link|t=3356|text=here}} and {{forum link|t=3415|text=here}}.

==Selecting the UFO==
[[File:Placing_objects_with_UFO_html_m49fbed81.jpg|400px]]

Now start FlightGear with the UFO as your aircraft and enable the console, which is needed later on. When launching FlightGear from command line, use <code>--aircraft=ufo --console</code>. In [[FGRun]], the "Show console" option on the last page should be checked.

==Placing objects==
Once FlightGear has been started, fly with the UFO to roughly the place you want the model to be positioned.

[[File:Placing_objects_with_UFO_html_5fa8d7b1.jpg|400px]]

Let's say we want to position the catii-iii.xml object at the end of a taxiway. We stop the UFO just above this intersection and press the space key. A Select Model window will open up where the contents of the <tt>[[$FG_ROOT]]/Models/</tt> directory will be shown (or press {{key press|Shift}}+{{key press|L}} and you can go to any desired directory). Select your preferred model from this list, then close the window. The selected model path/name will be displayed in green text at the bottom left of the FlightGear screen.

[[File:Placing_objects_with_UFO_html_m184fb381.jpg|400px]]

To place the object, simply left-click on the position that you want to place it. By default, it is placed completely horizontal and rotated to point north. It will probably not have the correct orientation and it might be partly covered by the surrounding terrain, but we can adjust that.

[[File:Placing_objects_with_UFO_html_12ee70a1.jpg|400px]]

===Rotating objects===
Fly closer to the ground with the UFO, so that you can see it better.

Now press {{key press|{{=}}}} (earlier versions than 3.0 uses {{key press|Tab}}) and use the resulting sliders to adjust the latitude/longitude/elevation/heading of the model. NB: "Pitch" and "roll" will not be saved, so using them might be fun, but won't help eventually.

[[File:Placing_objects_with_UFO_html_439816e9.jpg|400px]]

See the [[UFO from the 'White Project' of the UNESCO]] page for more information on the UFO command keys and exported file locations, or press {{key press|?}} while in FlightGear.

===Deleting objects===
There are three different ways to three different situations in which which you want to delete an object:
You want to delete the last object that you placed in this session:
: Press the [http://en.wikipedia.org/wiki/Backspace backspace button].
You want to delete an object that you placed in this session, but you have placed one or two models after it:
: That means that it is no longer active. Activate it by placing one more model '''on''' the object you want to delete, press the backspace button. Result: The model you want to delete starts blinking, which tells you that it is active.
You want to delete an object that is already saved in the corresponding .stg file and you don't know where it is:
: You don't know the filename: The model you want to delete is probably a shared model. You find it in the [http://scenemodels.flightgear.org/ scenery database]. Now you know the model's filename (e.g. [http://scenemodels.flightgear.org/modeledit.php?id=45 generic_skyscraper_01.ac] or [http://scenemodels.flightgear.org/modeledit.php?id=537 Office26x22.xml]).
: You still need to know where you find it. Place any model on that building and press {{key press|D}} to know in which file you find it (see [[#Exporting the result|Exporting the result]] below). If there are several objects of that type and you want to delete only one of them, find the one closest to the coordinates of your model placed on top.
: Open the .stg file, delete the whole model entry (see [[#Exporting the result|Exporting the result]] below). Done.

==Exporting the result==
Now that the model is correctly positioned, press the {{key press|D}} key to dump the model position data to the terminal. A few lines will be printed on the console, providing the necessary orientation data.

[[File:Placing_objects_with_UFO_html_m4cf0cbf7.jpg]]

The most important lines are the last ones:
# e000n50/e008n50/3089154.stg
OBJECT_SHARED Models/Tabu/catii-iii.xml 8.57928135 50.03667992 105.9972 111.1

The first line identifies the location of the scenery file for the object. The OBJECT_SHARED line indicates the object's name, longitude, latitude, altitude, and orientation. This can be read by FlightGear itself and can be [http://scenemodels.flightgear.org/contribute.php submitted] to the FlightGear Scenery Object Database.

You can also save these coordinates into your own scenery file so that your changes will not be lost the next time you start FlightGear.

===Saving the changes to your scenery===
In the terminal window, you get three sections printed out by the UFO with very detailed information about what's going on. We need the lines at the end.

As noted above, the UFO helpfully exports the name of the scenery file where the object's coordinates have to be saved. In our example: e000n50/e008n50/3089154.stg

The default location for scenery objects is <tt>[[$FG_SCENERY]]/Objects/</tt>. Simply open the referenced .stg file, add the OBJECT_SHARED line to the bottom and save the file. Now you have your object's position saved, and it will appear inside the scenery every time you start FlightGear! There is one pitfall here. If TerraSync is enabled, which is the default in latest FlightGear versions, and you modified the stg file in the TerraSync folder, your modifications might be overridden by the syncing process. You might need to add the startup option --disable-terrasync for avoiding this and to keep your modifications.

In our example we would open in <tt>[[$FG_SCENERY]]/Objects/e000n50/e008n50/3089154.stg</tt> and add the following line:
OBJECT_SHARED Models/Tabu/catii-iii.xml 8.57928135 50.03667992 105.9972 111.1

For a short video demonstrating the .stg method, see the following video:
{{#ev:youtube|i2BSUOMyiIg|400|center}}

If you are running Windows OS, then please refer to this video:
{{#ev:youtube|e93OUEp0YKc|400|center}}

===Saving to XML===
Alternatively, if you press the {{key press|E}} key while developing scenery with UFO, FlightGear will generate an XML file with the dump of your current work in an "ufo-model-export.xml" file under [[$FG_HOME]].

===Loading the XML file as part of FlightGear scenery===
You can later reload this XML file with --config= command-line parameter:
Example for Linux: fgfs --config=$HOME/.fgfs/Export/ufo-model-export.xml

In Windows, this is done using the Advanced dialog, found on the last page of the [[FGRun]] GUI. Click Advanced and, under General, click the double-dot button, browse to the ufo-model-export.xml file and click OK.

==Sharing your updates with everyone!==
Please, once you've improved the scenery around your place, consider sharing it with the community. This is done very easily using our [http://scenemodels.flightgear.org/submission scenery submission webforms]. More information and help on {{forum link|t=14671|text=the dedicated topic}} on the scenery forum.

[[Category:Howto]]
[[Category:Scenery enhancement]]
[[ar:Howto:Place 3D objects with the UFO]]
[[es:Colocar objetos con el UFO]]
[[fr:Placer des objets 3D avec UFO]]

User:Axlerate

2019-09-06T14:26:10Z

Axlerate: Add

Hello.

I'm here for anti-vandalism work.

I also have an interest in fixing any grammatical errors around here.

I am also a friendly editor here, as I don't bite, probably to the vandals.

Any questions, comments, suggestions, concerns, discussions, enquiries, etc,.? Post them on my talk page, or send them via email at dovewindsor@gmail.com.

User talk:Johan G

2019-09-06T14:23:50Z

Axlerate: /* Introduction */ new section

{{Archives|[[/Archive 2011-2015|2011-2015]]}}
{{Welcome to the wiki|name=Johan|added-by=Johan G}}{{-}}

== Newsletter drafts ==
Hi Johan. Would it be possible for you to create the "draft" newsletters up to December? Not sure of the exact format, don't want to mess things up ;)
[[User:Legoboyvdlp|Legoboyvdlp]] ([[User talk:Legoboyvdlp|talk]]) 08:22, 25 October 2017 (EDT)

: With a bit of luck I could give it a try tomorrow.
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 12:36, 28 October 2017 (EDT)

:: Sorry for my delays. At some point (probably some weekend) I aim to implement what have been [http://wiki.flightgear.org/index.php?title=FlightGear_wiki:Village_pump&oldid=111694 discussed at the Village Pump recently] regarding using preloaded pages. In essence making a single click link to create a draft of the next newsletter. (Unless someone is quicker on that than me...)

:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 16:40, 5 November 2017 (EST)

:: An early newsletter template draft is now available in my sandbox.
:: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 07:08, 11 November 2017 (EST)

== Progress bar and icons ==

Hi Johan. I was wondering if you could upload a new set of [[:Category:Progress icons|progress bar icons]]? Half of the current set have been lost from the wiki backend, so scaled icons are broken. See {{tl|progressbar}} where a number of these graphics are shown as the text: '''Error creating thumbnail: File missing'''. For two of these, I have manually recreated bitmap versions. Maybe it would be good to upload the SVG originals? I have been using scaled versions of these via the {{tl|progressbar}} template for the [http://wiki.flightgear.org/index.php?title=Translation_requests&oldid=113443 current version of the translation requests page]. For better table packing, I am wondering if we should introduce a {{param|vertical}} parameter for this template and have a full set of vertical icons, as a copy of your progress icons rotated 90 degrees.

[[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 12:02, 29 December 2017 (EST)

: I feel I need to apologize for not doing this literally years ago. I have finally gotten around to reupload these particular missing files. It seems likely that they have been missing ever since the wiki crashed when the ISP migrated the wiki's virtual server to new hardware back in late January 2015 (see the forum topic [https://forum.flightgear.org/viewtopic.php?f=42&t=25209 wiki.flightgear.org scheduled downtime] for the details.)

: As for vertical ones, I am not there yet, but I think just turning them vertical would make them nearly unreadable. I have some ideas, but is as often slow to implement them.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 09:27, 19 May 2018 (EDT)

: Have done a test with vertical ones. Even reading out 20% steps is hard in normal running text. 1/3rds maybe are possible. Could probably be better to have a compact 20%-step version of the horizontal one instead.

: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 11:24, 19 May 2018 (EDT)

== Introduction ==

Hello. Who is in charge around here? --[[User:Axlerate|Axlerate]] ([[User talk:Axlerate|talk]]) 10:23, 6 September 2019 (EDT)

Changelog 2.4.0

2019-09-06T14:21:51Z

Axlerate: Fixed grammatical errors using Grammarly

{{changelogs|next=2.6.0}}
The FlightGear development team is happy to announce the release of FlightGear 2.4.0. This new version contains many exciting new features, enhancements, bugfixes, and other improvements.

After adopting the newly available shader technology in 2.0.0, FlightGear’s graphical quality has been substantially improved. Besides that, assorted highlights of this version include: a configurable local weather system, many new and improved aircraft, and numerous scenery additions.

===Some of the major changes include:===
'''Aircraft operations:'''
* A new head-up display (HUD) system
* An in-sim moving map
* ATC/ATIS improvements
* EICAS instruments are available on a selected number of aircraft
* Improved autopilots
* TCAS, works with AI and multiplayer aircraft, provides aural warnings for conflicting traffic and is also capable of driving a realistic traffic display. AI aircraft also respond to TCAS alerts and take evasive action
* Updates to the KLN89 GPS.
* tanker now refuels with any callsign and can enable/disable refueling in flight.

'''AI system'''
* A standalone AI flightplan generator program
* Approaching aircraft now follow realistic approach trajectories
* Ballistic objects can slave to any AI object
* Improved AI ballistics behavior
* More communication/interaction between AI aircraft and ground. Support for multiple frequencies for AI/ATC interaction.
* Speed-up for AI traffic initialization by means of an aircraft usage statistics collection mechanism

'''AI Traffic'''
* General and commercial aviation traffic at LOWI airport
* Malaysian Airways / Kuala Lumpur based traffic
* Traffic for Adria (Croatia)

'''Flight dynamics'''
* A new MIL-STD Turbulence model has been added to the JSBSim flight dynamics simulation engine

'''Environment'''
* A local weather system to simulate physically correct local weather phenomena
* Discard of outdated METAR weather information sources and improved METAR parsing
* New Fog layers with limited elevation
* Scenery can be downloaded and installed on-the-fly via an in-sim TerraSync interface
* Specific multiplayer pilots can be selectively ignored

'''Interface'''
* Complete overhaul of the autopilot system
** New digital controllers
** Flexible use of input and output values
** Support for mathematical expressions
** Usable for generic numeric data processing as a "property rule" system
* Better integration of separate weather systems
* New support of draggable 3d objects like throttle-levers
* Support for textures generated from VNC clients
* Unified runway selection code that is shared between user-controlled and AI-controlled aircraft
* New HLA interface for distributed simulations
* New on-demand loading of Nasal modules
* New support for external (aka real) Garmin 400/500 WAAS Units
* Optional automatic selection of nearest tower for external 'tower view'

'''Highlighted new and improved aircraft'''
* A new and highly detailed IAR-80 (a Romanian-produced WW2 fighter)
* A new highly detailed Piper Cub
* Airbus A320 Family (318/319/320/321)
* An improved P-51D, completely remodeled and containing improved flight dynamics
* Boeing 717
* Boeing 757-200
* Bombardier CRJ700 Series (700/900/1000)
* Bombardier CRJ200
* Douglas A-4F Skyhawk
* Improvements to the Boeing 787
* MiG-15bis
* PZL-Mielec M18B "Dromader"
* Short S.23 Empire flying boat
* The Boeing 737NG Series
* The Boeing 747-400 and 777-200 have received lots of improvements
* The Douglas DC-8 Series
* The Eurocopter EC130 B4 Helicopter
* Tyre smoke effects on many aircraft
* Zeppelin LZ 121 Nordstern

'''Navigation'''
* A new route manager
* Autopilots can be driven by NAV or GPS instruments

'''Project infrastructure'''
* Change to Git as a revision control system
* Moved to make based build system
* Set up [http://flightgear-bugs.googlecode.com a bug tracker]
* Support for automatic nightly snapshot releases
* Support for placing add-on aircraft in a separate aircraft directory, separate from the main data directory

'''Scenery improvements'''
* Animated jetways
* (Are all of the following in scene models?)--[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)
* Improvements to the Innsbruck area, Austria
* Las Vegas McCarran Intl. Airport
* London Gatwick Airport
* Many buildings for small airports in the Italian Alps
* Many contributions to the Switzerland area, including building models and shapefiles for future terrain improvements
* Many historic and current launch sites have been added to the Kennedy Space Center Area, including some AI-controlled rocket launches
* The city of Dubai (terrain, city buildings, and AI traffic)
* <s>Time dependent placement of buildings.</s> What is this? --[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)

'''Visual effects'''
* Various graphics improvements using shaders, including 3D urban effects, reflections, water, rock textures, lightmaps, skydome scattering
* Easy GUI-based access to a host of stereoscopic 3D rendering effects
* Panoramic distortion (Is this really implemented?)--[[User:T3r|T3r]] 16:59, 3 August 2011 (EDT)
* Persistent contrails
* New standalone 2D-Panel rendering utility

'''Bug fixes'''
* Fixed METAR live weather (http requests from NOAA)
* Fixed many sources of the infamous NaN errors
* Improved stability by fixing many segmentation faults, deadlocks and memory leaks
* Improved placement of random objects
* Fixed inconsistencies with scenery tile scheduling
* The replay system now works again as advertised
* The ground proximity warning system (GPWS) works reliably now
* Runway lights also working with ATI graphics cards now (rendering option to disable point-sprites)
* Many, many more. See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.4.0 our bugtracker] for an extensive list

[[Category:FlightGear changelogs]]

User:Axlerate

2019-09-06T14:17:40Z

Axlerate: Add

User:Axlerate

2019-09-06T14:15:52Z

Axlerate: Add

Hello.

I'm here for anti-vandalism work.

I also have an interest in fixing any grammatical errors around here.

User talk:Axlerate

2019-09-06T14:14:53Z

Axlerate: Created page with "'''Welcome to my talk page.'''"

'''Welcome to my talk page.'''

FSweekend 2013

2019-09-06T14:13:44Z

Axlerate: Fixed grammatical errors using Grammarly

This wiki page lists all information related to [[FlightGear]]'s [[FSweekend]] 2013 attendance, as well as information for those that would like to pay a virtual visit. FlightGear will be represented by a team of regular FlightGear developers.
<font size="5">'''FSweekend'''</font> at 2&3 November 2013.

==Booth information==
===Equipment Checklist===
==Flight information==
===Airports===
[[File:EHLE_schipholgebouw.png|thumb|270px|The old terminal of Schiphol (1928), now located at EHLE.]]
Activities will mainly take place at and around [[Amsterdam Airport Schiphol]] (EHAM) and [[Lelystad Airport]] (EHLE).

===Charts===
All charts that you may have to use on your flights are available at http://ais-netherlands.nl (AIS Publications > Integrated Package). Please note that these are the most up to date charts available, so certain situations might not have been changed in FlightGear (EHAM, EHLE and EHVK taxiways should be correct though).

Parking positions have been created for most of the Dutch airports including EHAM, EHRD, EHVK, and EHLE (A1-A6, B1, and B2).

===Weather information===
Real-life weather information can be found at the KNMI (Dutch Meteorological Institute) website.
* [http://knmi.nl/actueel/metar.html METAR] current weather at airports
* [http://knmi.nl/waarschuwingen_en_verwachtingen/luchtvaart/nederlandse_vliegveldverwachtingen.html TAF] expected weather at airports
If the weather is really bad, it is likely that the FSweekend guys will use a preset weather scenario.

==External links==
* [http://www.fsweekend.com Official FSweekend website]

[[Category:FSweekend]]

User:Axlerate

2019-09-06T14:10:09Z

Axlerate: Add

Hello.

I'm here for anti-vandalism work.

User:Axlerate

2019-09-06T13:01:34Z

Axlerate: Beginning my user page!

Hello.