FlightGear wiki - User contributions [en]

Poland

2013-08-11T17:29:52Z

Zbyszek: /* Objects & airports */

'''Poland''' (Polish: Polska), officially the Republic of Poland (Polish: Rzeczpospolita Polska), is a country in Central Europe, bordered by Germany to the west; the Czech Republic and Slovakia to the south; Ukraine, Belarus and Lithuania to the east; and the Baltic Sea and Kaliningrad Oblast, a Russian exclave, to the north. The total area of Poland is 312,679 square kilometres (120,726 sq mi), making it the 9th largest in Europe. Poland has a population of over 38 million people.

== FlightGear community ==

Polish FlightGear community has own Facebook site [http://www.facebook.com/pages/FlightGear-Polska/184032164996361]

Forums:
[http://www.fgforum.comuv.com/ Polish FlightGear Forum]

== Custom Scenery of Poland ==

[[File:Warsaw Skyline.png|thumb|Warsaw skycrapers.]]
[[File:Hel Peninsula.png|thumb|Hel Peninsula]]
[[File:Czorsztynskie Lake.png|thumb|Czorsztyńskie Lake]]
===Terrain===

Custom Scenery of Poland includes whole Poland territory and border areas of surrounding countries. Terrain was generated using CORINE 2006 and OSM data for roads and railways.

===Objects & airports===

Currently we have objects on following airports:

International
*[[Warsaw Chopin Airport|EPWA Warsaw-Okęcie]]
*EPGD Gdańsk-Rębiechowo
*EPSC Szczecin-Goleniów
*[[Zielona Góra Airport|EPZG Zielona Góra-Babimost]]
*EPLL Łódź-Lublinek
*[[Lublin Airport|EPLB Lublin]]

Regional
*EPBC Warsaw-Babice
*[[Wloclawek-Kruszyn|EPWK Włocławek-Kruszyn]]
*[[Plock-Kostrogaj|EPPL Płock-Kostrogaj]]
*[[Aeroclub of Lublin|EPLR Lublin-Radawiec]]
*EP70 Rzepin

Military
*EPDE Dęblin

Foreign
*EKRN Bornholm-Rønne
*LZTT Poprad-Tatry

See [http://wiki.flightgear.org/Category:Airports_in_Poland Category:Airports in Poland]

And some VFR landmarks including Warsaw skyline.

Most airports uses v.850 layout. See full list here: [https://gitorious.org/custom-scenery-polish/pages/Lotniska gitorious.org/custom-scenery-polish/pages/Lotniska]

===Volunteer===

Feel free to help us! This scenery still needs objects and v.850 layouts. You can take some pictures of nearby airports or VFR landmarks and send them to us. We also appreciate new 3d models. If You'd like to contribute contact us by [https://www.facebook.com/pages/FlightGear-Polska/184032164996361 Facebook] or [http://www.fgforum.comuv.com/viewtopic.php?f=10&t=1249&sid=377f274e9c94a34bd082fce4b7f443e3 thread] on Polish FlightGear forum.

===Credits===
* SP-DAM objects, layouts
* SP-MMA objects, layouts, terrain
* SP-MAKA objects
* SP-R22 objects
* Zbyszek objects, layouts

===Download===

You can download scenery from: https://gitorious.org/custom-scenery-polish

Category:Airports in Poland

2013-08-11T17:28:07Z

Zbyszek:

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! class="unsortable" style="background:#efefef" | Comment
|-
| EPWA || [[Warsaw Chopin Airport]], Warsaw || custom layout, 3d models, airport service || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery]
|-
| EPSC || [[Goleniow Airport]], Goleniów/Sczecin || custom layout, 3d models, airport service || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery]
|-
| EPDE || [[Deblin Airport]], Dęblin || custom layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Military/Cyvil airport
|-
| EPZG || [[Zielona Góra Airport]], Zielona Góra || custom layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Cyvil airport
|-
| EPLL || [[Łodź Airport]], Lublinek || custom layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Cyvil airport
|-
| EPLB || [[Lublin Airport]], Lublin || v850 layout, 3d models || in progress || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Cyvil airport
|-
| EPLR || [[Aeroclub of Lublin]] Radawiec || v850 layout, 3d models || in progress || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EPSW || [[Aeroclub of Swidnik]] Świdnik || v850 layout, 3d models || in progress || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EPWK || [[Wloclawek-Kruszyn]] || v850 layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EPPL || [[Plock-Kostrogaj]] || v850 layout, 3d models, Rembrandt || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EP70 || [[Rzepin]] || v850 layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass, forest landing
|-
| EPWR || [[Wroclaw Airport ]] || 3d models, Rembrandt || stalled || makaPL [https://sites.google.com/site/fgmakapl/home/download makaPL download] Cyvil airport
|-
| EPGD || [[Gdansk Airport ]] || v810 layout, 3d models || in progress || Part of [http://code.google.com/p/sceneria-epzg-babimost/downloads/detail?name=EPGDver.1.0.rar&can=2&q= Poland Custom Scenery] Cyvil airport
|-
| EPBC || [[Warszawa Babice ]] || v850 layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Concrete, Warsaw Aeroclub airport
|}

[[Category:Airports in Europe]]

Poland

2013-08-11T17:16:08Z

Zbyszek:

'''Poland''' (Polish: Polska), officially the Republic of Poland (Polish: Rzeczpospolita Polska), is a country in Central Europe, bordered by Germany to the west; the Czech Republic and Slovakia to the south; Ukraine, Belarus and Lithuania to the east; and the Baltic Sea and Kaliningrad Oblast, a Russian exclave, to the north. The total area of Poland is 312,679 square kilometres (120,726 sq mi), making it the 9th largest in Europe. Poland has a population of over 38 million people.

== FlightGear community ==

Polish FlightGear community has own Facebook site [http://www.facebook.com/pages/FlightGear-Polska/184032164996361]

Forums:
[http://www.fgforum.comuv.com/ Polish FlightGear Forum]

== Custom Scenery of Poland ==

[[File:Warsaw Skyline.png|thumb|Warsaw skycrapers.]]
[[File:Hel Peninsula.png|thumb|Hel Peninsula]]
[[File:Czorsztynskie Lake.png|thumb|Czorsztyńskie Lake]]
===Terrain===

Custom Scenery of Poland includes whole Poland territory and border areas of surrounding countries. Terrain was generated using CORINE 2006 and OSM data for roads and railways.

===Objects & airports===

Currently we have objects on following airports:

International
*EPWA Warsaw-Okęcie
*EPGD Gdańsk-Rębiechowo
*EPSC Szczecin-Goleniów
*EPZG Zielona Góra-Babimost
*EPLL Łódź-Lublinek
*EPLB Lublin

Regional
*EPBC Warsaw-Babice
*EPWK Włocławek-Kruszyn
*EPPL Płock-Kostrogaj
*EPLR Lublin-Radawiec
*EP70 Rzepin

Military
*EPDE Dęblin

Foreign
*EKRN Bornholm-Rønne
*LZTT Poprad-Tatry

See [http://wiki.flightgear.org/Category:Airports_in_Poland Category:Airports in Poland]

And some VFR landmarks including Warsaw skyline.

Most airports uses v.850 layout. See full list here: [https://gitorious.org/custom-scenery-polish/pages/Lotniska gitorious.org/custom-scenery-polish/pages/Lotniska]

===Volunteer===

Feel free to help us! This scenery still needs objects and v.850 layouts. You can take some pictures of nearby airports or VFR landmarks and send them to us. We also appreciate new 3d models. If You'd like to contribute contact us by [https://www.facebook.com/pages/FlightGear-Polska/184032164996361 Facebook] or [http://www.fgforum.comuv.com/viewtopic.php?f=10&t=1249&sid=377f274e9c94a34bd082fce4b7f443e3 thread] on Polish FlightGear forum.

===Credits===
* SP-DAM objects, layouts
* SP-MMA objects, layouts, terrain
* SP-MAKA objects
* SP-R22 objects
* Zbyszek objects, layouts

===Download===

You can download scenery from: https://gitorious.org/custom-scenery-polish

File:Warsaw Skyline.png

2013-08-11T16:40:45Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Warsaw skycrapers.}}
|date=2013-08-11 18:36:13
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

File:Czorsztynskie Lake.png

2013-08-11T16:40:44Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Lovely place near Pieniny National Park.}}
|date=2013-08-11 18:36:12
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

File:Hel Peninsula.png

2013-08-11T16:40:42Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Hel Peninsula}}
|date=2013-08-11 18:36:05
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

Pl/Changelog 2.12

2013-08-11T16:28:34Z

Zbyszek:

{{draft|changelog|This changelog is currently being written for the next FlightGear release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.<br/>It's a good idea to check [[:Category:Changes_after_2.10|the newsletters since the last release]], and the git commit history.
To view the changelog for the most recent release, please see [[Changelog 2.10]]. }}

==Upcoming FlightGear Changelog==

Zespół deweloperski FlightGear ma przyjemność poinformować o wydaniu FlightGear v2.12, wolnego, open-sourcowego symulatora lotu. Nowa wersja przynosi wiele ekscytujących funkcji, ulepszeń oraz poprawek. Szczególnie ważne dla tego wydania są poprawiona użyteczność, kontynuacja rozwoju pakietu renderującego Canvas oraz ulepszone renderowanie scenerii.

Rozpoczęty w 1997 roku, projekt FlightGear jest rozwijany przez grupę wolontariuszy z całego świata, zjednoczonych przez wspólne staranie stworzenia jak najbardziej realistycznego, wolnego i otwartego symulatora lotu. FlightGear jest używane szeroko przez entuzjastów symulacji, w badaniach uniwersyteckich oraz jako element interaktywnych wystaw w muzeach

FlightGear oferuje ponad 400 statków powietrzych, scenerie całego świata, środowisko multiplayer, szczegółowe modelowanie nieba, elastyczny i otwarty system modelowania samolotów. FlightGear należy do społeczności i każdy jest zaproszony do współpracy.
Pobierz FlightGear v2.12 za darmo z [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

=== Główne zmiany w tym wydaniu ===

'''Modelowanie samolotów'''
* Nowy system śledzenia animacji zapewnia łatwe rozwiąznie dla twórców samolotów, aby zanimować skomplikowane ruchy elementów, takie jak drzwi goleni podwozia przymocowane do zawiasów czy "gear scissors". Animacje mogą być zrobione w Blenderze i potem wyeksportowane do FlightGear

'''Środowisko'''

* Góry lodowe pojawiają się na morzach arktycznych.
* Drzewa liściaste tracą swoje listowie, jeśli znajdują się powyżej lini śniegu, tworząc przekonujący, zimowy wygląd.
* Klimatyczna linia śniegu podnosi się i opada podczas latania po całym świecie
* "Basic weather" jest teraz połączone z "Atmospheric Light Scattering".
* Chmury są rozmieszczane bardziej realistycznie, kiedy używasz dokładnego modelowania pogody.

'''Transponder'''

Przyrząd transpodera został gruntownie przebudowany pozwalając na prostsze użycie go z poziomu paneli, wspiera Mod-S i wysyła ważne wartości przez multiplayer. To pozwala na bardziej relistyczną komunikację z ATC, ponieważ kod transpondera (squawk) ma teraz znaczenie! Przejdź do tej strony wiki, aby zobaczyć więcej informacji dotyczących instalacji/aktualizacji transpondera w samolocie.

'''Wydajność'''

Wiele problemów związanych z NavCache doświadczanych przez użytkowników Windowsa (lagi) zostało rozwiązanych.

'''Zgodność'''

Znów została przywrócona zgodność ze starszymi systemami nie obsługującymi GLSL (shadery), więc FlightGear już nie odmawia współpracy z takimi systemami.

'''Atmospheric Light Scattering (rozpraszanie światła w atmosferze)'''
* Niezwykle zaawansowany shader wysokiej jakości pozwwala na automatyczne generowanie detali, nawet do kilku centymetrów.
* Wprowadzono symulacje jesiennych barw od środka lata do początku zimy.
* Warunki niskiej widoczności są teraz znacznie lepiej renderowane.
* Drzewa poruszają się z wiatrem.
* Widoczne są fale morskie przy wysokich klifach.

''' Zwiększona wydajność, zmniejszenie wymagań pamięci '''

''' Funkcjonalność '''
* Moduł checklist został rozbudowany.
** Punkty checklisty są kolorowane, w celu pokazania czy zostały wykonane, jeśli tak - są zielone, natomiast niekompletne - żółte
** Aby uwałtwić zapoznanie się z cockpitem, można podświetlić dany przyrząd.
** Wirtualny drugi pilot może wykonywać chcecklistę w imieniu kapitana.
** Tutoriale są automatycznie generowane na podstawie checklist, przez co wirtualny instruktor może Cię poprowadzić przez całą checklistę,
* A knob animation generalizes the operation of knobs and switches in the cockpits of various aircraft.

* Okno Pogody została przeprojektowane, aby ułatwić jego użytkowanie.
* Tooltips (available under the Debug menu) provide feedback that computer pilots have to miss due to an absence of audio or haptic feedback. When you hover your mouse over a switch or lever, a little window tells you the current state of the switch.

''' Tłumaczenie '''

* Menu oraz wiadomości systemowe zostały przetłumaczone na portugalski.

'''System Canvas '''

"Canvas" (ang. płótno) jest w pełni skryptowalnym systemem renderowania 2D, ułatwiającym użytkowinkom tworzenie nowych instrumentów, wyświetlaczy glass cockpit, HUDów, a nawet okien dialogowych i niestandardowych widżetów GUI, używając wbudowanego w FlightGear języka skryptowego [[Nasal]] (który wygląda bardzo podobnie do JavaScript).

Kilka udoskonaleń Canvas w tym wydaniu:
* The style setter system has been reworked, style setters are now only setup once for each element type and not for each element instance as before. A static map holds the setters for each element type. Also an animation type is stored which will later allow to animate properties of Canvas elements without specifying an animation type.
* The Nasal/cppbind framework has been improved to expose more Canvas internals to Nasal space
* Canvas textures can now not only be used as aircraft/cockpit textures (instruments, MFDs) and for the HUD/GUI, but also for scenery objects. Canvas textures can now be placed on scenery objects. This allows for example creating animated signs/monitors such as a Visual Docking Guidance System.
* Powtarzanie tekstur dla zdjęć Canvas.
* Większe wsparcie dla wyświetlania widżetów GUI.

'''Nasal Scripting'''
* All methods exposed to the Nasal props module now accept an optional first parameter refering to another node by a relative path.
* SimGear's SGTimer class is now fully exposed to Nasal, see the new '''maketimer'''() API.
* Kilka błędów Nasal mogących powodować "wysypywanie się" zostało naprawionych.

'''Rembrandt'''

* Wzrastająca liczba samolotów jest kompatybilna z techniką renderowania Rembrandt.

'''Ulepszenia AI'''

* Scenariusze AI mogą być ładowane w czasie działania symulatora.
* Duża część samolotów AI otrzymała nowe malowania. Airbus A320 i A330 zostały przemodelowane, podczas gdy w innych modelach ulepszono animacje.
* Tankowanie w powietrzu zostało udoskonalone.
** Piloci mają możliwośc wybieranie liczby cystern AI oraz mogą dopasować ich prędkość do wartości szybkości samolotu.
** Cysterny są bardziej realistyczne, wspierają wiele punktów tankowania, można modyfikować przepływ paliwa, strefa tankowania jest wycentrowana na przewodzie paliwowym.
* Do określania kiedy nastąpił kontakt brana jest pod uwagę pozycja sondy na samolocie.
** Poziom trudności tankowania może być modyfikowany bezpośrednio w symulatorze przez określenie w jakiej odległości od przewodu paliwowego zachodzi tankowanie.
** Cysterna informuje pilota o udanym kontakcie.

''' Regionalne tekstury '''

Następujące miejsca mają teraz własne, indywidualne tekstury oraz automatycznie generowane budynki:
* Środkowy Wchód,
* Wielka Brytania,
* Wyspy na północnym Atlantyku - Wyspy owcze, Szetlandy, Greenlandia,
* Madagaskar.

'''Wyróżnione i poprawione samoloty'''
* Mudry CAP 10C
* Tupolev Tu-154B-2
* ASW-20

'''Inne'''

* Dodatkowe joysticki i pedały orczyka zyskały wsparcie:
** GoFlight TQ6-ADV
** Genius Metalstrike 3D
** Microsoft SideWinder Precision Racing Wheel rudder pedals

'''Bug fixes'''

* Idź na [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.12.0 our bugtracker], aby zobaczyć niekomplentą jeszcze listę bugów naprawionych w tym wydaniu.

[[Category:FlightGear changelogs]]
[[en:Changelog 2.12]]

Plock-Kostrogaj

2013-08-09T20:57:01Z

Zbyszek: Created page with " {{infobox Airport |name = Płock-Kostrogaj |image =EPPL hangars.png |alt =EPWK hangars |iata =QPC |icao =EPWK |type =public |owner =Aeroklub Ziemi Mazowieckiej |city =Płock,..."

{{infobox Airport
|name = Płock-Kostrogaj
|image =EPPL hangars.png
|alt =EPWK hangars
|iata =QPC
|icao =EPWK
|type =public
|owner =Aeroklub Ziemi Mazowieckiej
|city =Płock, [[Poland]]
|runway= 13/31
|length= 680m
|material=Grass
|runway2= 08/26
|length2= 550m
|material2=Grass

|website =http://www.aeroklub.wloclawek.pl/
|scenerytile =e019n52
}}
==Description==
Płock-Kostrogaj (IATA: QPC, ICAO: EPPL) – small grass airport nerby Płock, own by Aeroklub Ziemii Mazowieckiej.

==Links==
*http://http://www.aeroklubplock.pl/ [PL]
*https://pl.wikipedia.org/wiki/Lotnisko_P%C5%82ock [PL]
==Scenery==

*custom layout (v850)
*3d objects

EPPL terrain and objects is included in the [[Poland]] scenery, which is available at [http://gitorious.org/custom-scenery-polish].
===Sreenshot===
[[File:EPPL hangars.png|500px|Płock-Kostrogaj airport scenery.]]
[[File:EPPL hangars (closer look).png|500px|Płock-Kostrogaj airport scenery.]]

[[Category:Airports in Poland]]

Wloclawek-Kruszyn

2013-08-09T20:40:01Z

Zbyszek: Created page with " {{infobox Airport |name = Włocławek-Kruszyn |image =EPWK_hangars_2.png |alt =EPWK hangars |icao =EPWK |type =public |owner =Aeroclub of Wloclawek |city =Kruszyn, Poland..."

{{infobox Airport
|name = Włocławek-Kruszyn
|image =EPWK_hangars_2.png
|alt =EPWK hangars
|icao =EPWK
|type =public
|owner =Aeroclub of Wloclawek
|city =Kruszyn, [[Poland]]
|runway= 08/26
|length= 1000m
|material=Grass
|runway2= 17/35
|length2= 600m
|material2=Grass

|website =http://www.aeroklub.wloclawek.pl/
|scenerytile =e019n52
}}
==Description==
Włocławek-Kruszyn (ICAO: EPWK) is small cyvil airport located in Kruszyn near Włocławek (Kujawsko-Pomorskie Voivodeship).
Aeroklub of Wloclawek organises many contests like:
* FAI World Championships for Model Helicopters
* FAI European HAB Championship
* and more

==Links==
*http://www.aeroklub.wloclawek.pl/ [PL]
*https://pl.wikipedia.org/wiki/Lotnisko_Włocławek-Kruszyn [PL]
==Scenery==

*custom layout (v850)
*3d objects

EPWK terrain and objects is included in the [[Poland]] scenery, which is available at [http://gitorious.org/custom-scenery-polish].
===Sreenshot===
[[File:EPWK panorama.png|500px|Włocławek-Kruszyn airport scenery.]]
[[File:EPWK hangars.png|500px|Włocławek-Kruszyn airport scenery.]]

[[Category:Airports in Poland]]

File:EPPL hangars (closer look).png

2013-08-09T20:19:40Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Płock-Kostrogaj airport scenery.}}
|date=2013-08-09 22:14:30
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Scenery]]
[[Category:Airports in Europe]]
[[Category:Airports in Poland]]

File:EPPL hangars.png

2013-08-09T20:19:39Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Płock-Kostrogaj airport scenery.}}
|date=2013-08-09 22:14:14
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Scenery]]
[[Category:Airports in Europe]]
[[Category:Airports in Poland]]

File:EPWK hangars 2.png

2013-08-09T20:19:37Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Włocławek-Kruszyn airport scenery.}}
|date=2013-08-09 22:14:09
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Scenery]]
[[Category:Airports in Europe]]
[[Category:Airports in Poland]]

File:EPWK hangars.png

2013-08-09T20:19:36Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Włocławek-Kruszyn airport scenery.}}
|date=2013-08-09 22:13:42
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Scenery]]
[[Category:Airports in Europe]]
[[Category:Airports in Poland]]

File:EPWK panorama.png

2013-08-09T20:19:35Z

Zbyszek: User created page with UploadWizard

=={{int:filedesc}}==
{{Information
|description={{en|1=Włocławek-Kruszyn airport scenery.}}
|date=2013-08-09 22:13:41
|source={{own}}
|author=[[User:Zbyszek|Zbyszek]]
|permission=
|other_versions=
|other_fields=
}}
{{Location dec|0|0}}

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

[[Category:Scenery]]
[[Category:Airports in Europe]]
[[Category:Airports in Poland]]

Category:Airports in Poland

2013-08-09T20:01:13Z

Zbyszek:

Category:Airports in Poland

2013-08-09T19:58:48Z

Zbyszek: Wiki doesn't like Polish characters (database error when starting new article).

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! class="unsortable" style="background:#efefef" | Comment
|-
| EPWA || [[Warsaw Chopin Airport]], Warsaw || custom layout, 3d models, airport service || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery]
|-
| EPSC || [[Goleniow Airport]], Goleniów/Sczecin || custom layout, 3d models, airport service || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery]
|-
| EPDE || [[Deblin Airport]], Dęblin || custom layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Military/Cyvil airport
|-
| EPZG || [[Zielona Góra Airport]], Zielona Góra || custom layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Cyvil airport
|-
| EPLL || [[Łódź Airport]], Lublinek || custom layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Cyvil airport
|-
| EPLB || [[Lublin Airport]], Lublin || v850 layout, 3d models || in progress || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Cyvil airport
|-
| EPLR || [[Aeroclub of Lublin]] Radawiec || v850 layout, 3d models || in progress || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EPSW || [[Aeroclub of Świdnik]] Świdnik || v850 layout, 3d models || in progress || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EPWK || [[Wlocławek-Kruszyn]] || v850 layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EPPL || [[Plock-Kostrogaj]] || v850 layout, 3d models, Rembrandt || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass
|-
| EP70 || [[Rzepin]] || v850 layout, 3d models || stalled || Part of [http://gitorious.org/custom-scenery-polish Poland Custom Scenery] Grass, forest landing
|-
| EPWR || [[Wrocław Airport ]] || 3d models, Rembrandt || stalled || makaPL [https://sites.google.com/site/fgmakapl/home/download makaPL download] Cyvil airport
|-
| EPGD || [[Gdańsk Airport ]] || v810 layout, 3d models || in progress || Part of [http://code.google.com/p/sceneria-epzg-babimost/downloads/detail?name=EPGDver.1.0.rar&can=2&q= Poland Custom Scenery] Cyvil airport
|}

[[Category:Airports in Europe]]

Pl/Changelog 2.12

2013-08-07T11:00:13Z

Zbyszek:

{{draft|changelog|This changelog is currently being written for the next FlightGear release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.<br/>It's a good idea to check [[:Category:Changes_after_2.10|the newsletters since the last release]], and the git commit history.
To view the changelog for the most recent release, please see [[Changelog 2.10]]. }}

==Upcoming FlightGear Changelog==

Zespół deweloperski FlightGear ma przyjemność poinformować o wydaniu FlightGear v2.12, wolnego, open-sourcowego symulatora lotu. Nowa wersja przynosi wiele ekscytujących funkcji, ulepszeń oraz poprawek. Szczególnie ważne dla tego wydania są poprawiona użyteczność, kontynuacja rozwoju pakietu renderującego Canvas oraz ulepszone renderowanie scenerii.

Rozpoczęty w 1997 roku, projekt FlightGear jest rozwijany przez grupę wolontariuszy z całego świata, zjednoczonych przez wspólne staranie stworzenia jak najbardziej realistycznego, wolnego i otwartego symulatora lotu. FlightGear jest używane szeroko przez entuzjastów symulacji, w badaniach uniwersyteckich oraz jako element interaktywnych wystaw w muzeach

FlightGear oferuje ponad 400 statków powietrzych, scenerie całego świata, środowisko multiplayer, szczegółowe modelowanie nieba, elastyczny i otwarty system modelowania samolotów. FlightGear należy do społeczności i każdy jest zaproszony do współpracy.
Pobierz FlightGear v2.12 za darmo z [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

=== Główne zmiany w tym wydaniu ===

'''Modelowanie samolotów'''
* Nowy system śledzenia animacji zapewnia łatwe rozwiąznie dla twórców samolotów, aby zanimować skomplikowane ruchy elementów, takie jak drzwi goleni podwozia przymocowane do zawiasów czy "gear scissors". Animacje mogą być zrobione w Blenderze i potem wyeksportowane do FlightGear
A new tracking animation provides an easy way for aircraft developers to animate complex kinematic systems like gear scissors or landing gear doors attached to struts. The animation can be implemented in Blender and then exported to FlightGear.

'''Środowisko'''

* Góry lodowe pojawiają się na morzach arktycznych.
* Drzewa liściaste tracą swoje listowie, jeśli znajdują się powyżej lini śniegu, tworząc przekonujący, zimowy wygląd
Deciduous trees shed their foliage if they are above the snowline, creating a convincing winter look.
* Klimatyczna linia śniegu podnosi się i opada podczas latania po całym świecie
The climatic snow line moves up and down as you fly around the world.
* "Basic weather" jest teraz połączone z "Atmospheric Light Scattering".
* Chmury są rozmieszczane bardziej realistycznie, kiedy używasz dokładnego modelowania pogody.

'''Transponder'''

Przyrząd transpodera został gruntownie przebudowany pozwalając na prostsze użycie go z poziomu paneli, wspiera Mod-S i wysyła ważne wartości przez multiplayer. To pozwala na bardziej relistyczną komunikację z ATC, ponieważ kod transpondera (squawk) ma teraz znaczenie! Przejdź do tej strony wiki, aby zobaczyć więcej informacji dotyczących instalacji/aktualizacji transpondera w samolocie.

'''Wydajność'''

Wiele problemów związanych z NavCache doświadczanych przez użytkowników Windowsa (lagi) zostało rozwiązanych.

'''Zgodność'''

Znów została przywrócona zgodność ze starszymi systemami nie obsługującymi GLSL (shadery), więc FlightGear już nie odmawia współpracy z takimi systemami.

'''Atmospheric Light Scattering (rozpraszanie światła w atmosferze)'''
* Niezwykle zaawansowany shader wysokiej jakości pozwwala na automatyczne generowanie detali, nawet do kilku centymetrów.
* Wprowadzono symulacje jesiennych barw od środka lata do początku zimy.
* Warunki niskiej widoczności są teraz znacznie lepiej renderowane.
* Drzewa poruszają się z wiatrem.
* Widoczne są fale morskie przy wysokich klifach.

''' Zwiększona wydajność, zmniejszenie wymagań pamięci '''

''' Funkcjonalność '''
* Moduł checklist został rozbudowany.
** Punkty checklisty są kolorowane, w celu pokazania czy zostały wykonane, jeśli tak - są zielone, natomiast niekompletne - żółte
** Aby uwałtwić zapoznanie się z cockpitem, można podświetlić dany przyrząd.
** Wirtualny drugi pilot może wykonywać chcecklistę w imieniu kapitana.
** Tutoriale są automatycznie generowane na podstawie checklist, przez co wirtualny instruktor może Cię poprowadzić przez całą checklistę,
* A knob animation generalizes the operation of knobs and switches in the cockpits of various aircraft.

* Okno Pogody została przeprojektowane, aby ułatwić jego użytkowanie.
* Tooltips (available under the Debug menu) provide feedback that computer pilots have to miss due to an absence of audio or haptic feedback. When you hover your mouse over a switch or lever, a little window tells you the current state of the switch.

''' Tłumaczenie '''

* Menu oraz wiadomości systemowe zostały przetłumaczone na portugalski.

'''System Canvas '''

"Canvas" (ang. płótno) jest w pełni skryptowalnym systemem renderowania 2D, ułatwiającym użytkowinkom tworzenie nowych instrumentów, wyświetlaczy glass cockpit, HUDów, a nawet okien dialogowych i niestandardowych widżetów GUI, używając wbudowanego w FlightGear języka skryptowego [[Nasal]] (który wygląda bardzo podobnie do JavaScript).

Kilka udoskonaleń Canvas w tym wydaniu:
* The style setter system has been reworked, style setters are now only setup once for each element type and not for each element instance as before. A static map holds the setters for each element type. Also an animation type is stored which will later allow to animate properties of Canvas elements without specifying an animation type.
* The Nasal/cppbind framework has been improved to expose more Canvas internals to Nasal space
* Canvas textures can now not only be used as aircraft/cockpit textures (instruments, MFDs) and for the HUD/GUI, but also for scenery objects. Canvas textures can now be placed on scenery objects. This allows for example creating animated signs/monitors such as a Visual Docking Guidance System.
* Powtarzanie tekstur dla zdjęć Canvas.
* Większe wsparcie dla wyświetlania widżetów GUI.

'''Nasal Scripting'''
* All methods exposed to the Nasal props module now accept an optional first parameter refering to another node by a relative path.
* SimGear's SGTimer class is now fully exposed to Nasal, see the new '''maketimer'''() API.
* Kilka błędów Nasal mogących powodować "wysypywanie się" zostało naprawionych.

'''Rembrandt'''

* Wzrastająca liczba samolotów jest kompatybilna z techniką renderowania Rembrandt.

'''Ulepszenia AI'''

* Scenariusze AI mogą być ładowane w czasie działania symulatora.
* Duża część samolotów AI otrzymała nowe malowania. Airbus A320 i A330 zostały przemodelowane, podczas gdy w innych modelach ulepszono animacje.
* Tankowanie w powietrzu zostało udoskonalone.
** Piloci mają możliwośc wybieranie liczby cystern AI oraz mogą dopasować ich prędkość do wartości szybkości samolotu.
** Cysterny są bardziej realistyczne, wspierają wiele punktów tankowania, można modyfikować przepływ paliwa, strefa tankowania jest wycentrowana na przewodzie paliwowym.
* Do określania kiedy nastąpił kontakt brana jest pod uwagę pozycja sondy na samolocie.
** Poziom trudności tankowania może być modyfikowany bezpośrednio w symulatorze przez określenie w jakiej odległości od przewodu paliwowego zachodzi tankowanie.
** Cysterna informuje pilota o udanym kontakcie.

''' Regionalne tekstury '''

Następujące miejsca mają teraz własne, indywidualne tekstury oraz automatycznie generowane budynki:
* Środkowy Wchód,
* Wielka Brytania,
* Wyspy na północnym Atlantyku - Wyspy owcze, Szetlandy, Greenlandia,
* Madagaskar.

'''Wyróżnione i poprawione samoloty'''
* Mudry CAP 10C
* Tupolev Tu-154B-2
* ASW-20

'''Inne'''

* Dodatkowe joysticki i pedały orczyka zyskały wsparcie:
** GoFlight TQ6-ADV
** Genius Metalstrike 3D
** Microsoft SideWinder Precision Racing Wheel rudder pedals

'''Bug fixes'''

* Idź na [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.12.0 our bugtracker], aby zobaczyć niekomplentą jeszcze listę bugów naprawionych w tym wydaniu.

[[Category:FlightGear changelogs]]
[[en:Changelog 2.12]]

Pl/Changelog 2.12

2013-07-29T12:23:21Z

Zbyszek:

{{draft|changelog|This changelog is currently being written for the next FlightGear release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.<br/>It's a good idea to check [[:Category:Changes_after_2.10|the newsletters since the last release]], and the git commit history.
To view the changelog for the most recent release, please see [[Changelog 2.10]]. }}

==Upcoming FlightGear Changelog==

The FlightGear development team is happy to announce the v2.12 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include improved usability, continued development of the Canvas rendering toolkit, and improved scenery rendering.

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create
the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world
by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2.12 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

=== Główne zmiany w tym wydaniu ===

'''Modelowanie samolotów'''
* Nowy system śledzenia animacji zapewnia łatwe rozwiąznie dla twórców samolotów, aby zanimować skomplikowane ruchy elementów, takie jak drzwi goleni podwozia przymocowane do zawiasów czy "gear scissors". Animacje mogą być zrobione w Blenderze i potem wyeksportowane do FlightGear
A new tracking animation provides an easy way for aircraft developers to animate complex kinematic systems like gear scissors or landing gear doors attached to struts. The animation can be implemented in Blender and then exported to FlightGear.

'''Środowisko'''

* Góry lodowe pojawiają się na morzach arktycznych.
* Drzewa liściaste tracą swoje listowie, jeśli znajdują się powyżej lini śniegu, tworząc przekonujący, zimowy wygląd
Deciduous trees shed their foliage if they are above the snowline, creating a convincing winter look.
* Klimatyczna linia śniegu podnosi się i opada podczas latania po całym świecie
The climatic snow line moves up and down as you fly around the world.
* "Basic weather" jest teraz połączone z "Atmospheric Light Scattering".
* Chmury są rozmieszczane bardziej realistycznie, kiedy używasz dokładnego modelowania pogody.

'''Transponder'''

Przyrząd transpodera został gruntownie przebudowany pozwalając na prostsze użycie go z poziomu paneli, wspiera Mod-S i wysyła ważne wartości przez multiplayer. To pozwala na bardziej relistyczną komunikację z ATC, ponieważ kod transpondera (squawk) ma teraz znaczenie! Przejdź do tej strony wiki, aby zobaczyć więcej informacji dotyczących instalacji/aktualizacji transpondera w samolocie.

'''Wydajność'''

Wiele problemów związanych z NavCache doświadczanych przez użytkowników Windowsa (lagi) zostało rozwiązanych.

'''Zgodność'''

Znów została przywrócona zgodność ze starszymi systemami nie obsługującymi GLSL (shadery), więc FlightGear już nie odmawia współpracy z takimi systemami.

'''Atmospheric Light Scattering (rozpraszanie światła w atmosferze)'''
* Niezwykle zaawansowany shader wysokiej jakości pozwwala na automatyczne generowanie detali, nawet do kilku centymetrów.
* Wprowadzono symulacje jesiennych barw od środka lata do początku zimy.
* Warunki niskiej widoczności są teraz znacznie lepiej renderowane.
* Drzewa poruszają się z wiatrem.
* Widoczne są fale morskie przy wysokich klifach.

''' Zwiększona wydajność, zmniejszenie wymagań pamięci '''

''' Funkcjonalność '''
* Moduł checklist został rozbudowany.
** Punkty checklisty są kolorowane, w celu pokazania czy zostały wykonane, jeśli tak - są zielone, natomiast niekompletne - żółte
** Aby uwałtwić zapoznanie się z cockpitem, można podświetlić dany przyrząd.
** Wirtualny drugi pilot może wykonywać chcecklistę w imieniu kapitana.
** Tutoriale są automatycznie generowane na podstawie checklist, przez co wirtualny instruktor może Cię poprowadzić przez całą checklistę,
* A knob animation generalizes the operation of knobs and switches in the cockpits of various aircraft.

* Okno Pogody została przeprojektowane, aby ułatwić jego użytkowanie.
* Tooltips (available under the Debug menu) provide feedback that computer pilots have to miss due to an absence of audio or haptic feedback. When you hover your mouse over a switch or lever, a little window tells you the current state of the switch.

''' Tłumaczenie '''

* Menu oraz wiadomości systemowe zostały przetłumaczone na portugalski.

'''System Canvas '''

"Canvas" (ang. płótno) jest w pełni skryptowalnym systemem renderowania 2D, ułatwiającym użytkowinkom tworzenie nowych instrumentów, wyświetlaczy glass cockpit, HUDów, a nawet okien dialogowych i niestandardowych widżetów GUI, używając wbudowanego w FlightGear języka skryptowego [[Nasal]] (który wygląda bardzo podobnie do JavaScript).

Kilka udoskonaleń Canvas w tym wydaniu:
* The style setter system has been reworked, style setters are now only setup once for each element type and not for each element instance as before. A static map holds the setters for each element type. Also an animation type is stored which will later allow to animate properties of Canvas elements without specifying an animation type.
* The Nasal/cppbind framework has been improved to expose more Canvas internals to Nasal space
* Canvas textures can now not only be used as aircraft/cockpit textures (instruments, MFDs) and for the HUD/GUI, but also for scenery objects. Canvas textures can now be placed on scenery objects. This allows for example creating animated signs/monitors such as a Visual Docking Guidance System.
* Powtarzanie tekstur dla zdjęć Canvas.
* Większe wsparcie dla wyświetlania widżetów GUI.

'''Nasal Scripting'''
* All methods exposed to the Nasal props module now accept an optional first parameter refering to another node by a relative path.
* SimGear's SGTimer class is now fully exposed to Nasal, see the new '''maketimer'''() API.
* Kilka błędów Nasal mogących powodować "wysypywanie się" zostało naprawionych.

'''Rembrandt'''

* Wzrastająca liczba samolotów jest kompatybilna z techniką renderowania Rembrandt.

'''Ulepszenia AI'''

* Scenariusze AI mogą być ładowane w czasie działania symulatora.
* Duża część samolotów AI otrzymała nowe malowania. Airbus A320 i A330 zostały przemodelowane, podczas gdy w innych modelach ulepszono animacje.
* Tankowanie w powietrzu zostało udoskonalone.
** Piloci mają możliwośc wybieranie liczby cystern AI oraz mogą dopasować ich prędkość do wartości szybkości samolotu.
** Cysterny są bardziej realistyczne, wspierają wiele punktów tankowania, można modyfikować przepływ paliwa, strefa tankowania jest wycentrowana na przewodzie paliwowym.
* Do określania kiedy nastąpił kontakt brana jest pod uwagę pozycja sondy na samolocie.
** Poziom trudności tankowania może być modyfikowany bezpośrednio w symulatorze przez określenie w jakiej odległości od przewodu paliwowego zachodzi tankowanie.
** Cysterna informuje pilota o udanym kontakcie.

''' Regionalne tekstury '''

Następujące miejsca mają teraz własne, indywidualne tekstury oraz automatycznie generowane budynki:
* Środkowy Wchód,
* Wielka Brytania,
* Wyspy na północnym Atlantyku - Wyspy owcze, Szetlandy, Greenlandia,
* Madagaskar.

'''Wyróżnione i poprawione samoloty'''
* Mudry CAP 10C
* Tupolev Tu-154B-2
* ASW-20

'''Inne'''

* Dodatkowe joysticki i pedały orczyka zyskały wsparcie:
** GoFlight TQ6-ADV
** Genius Metalstrike 3D
** Microsoft SideWinder Precision Racing Wheel rudder pedals

'''Bug fixes'''

* Idź na [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.12.0 our bugtracker], aby zobaczyć niekomplentą jeszcze listę bugów naprawionych w tym wydaniu.

[[Category:FlightGear changelogs]]
[[en:Changelog 2.12]]

Changelog 2.12

2013-07-28T12:42:45Z

Zbyszek:

{{draft|changelog|This changelog is currently being written for the next FlightGear release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.<br/>It's a good idea to check [[:Category:Changes_after_2.10|the newsletters since the last release]], and the git commit history.
To view the changelog for the most recent release, please see [[Changelog 2.10]]. }}

Available in: '''English''', [[:pl:Changelog 2.12|Polish]],
Please help us translate in other languages!

==Upcoming FlightGear Changelog==

The FlightGear development team is happy to announce the v2.12 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include improved usability, continued development of the Canvas rendering toolkit, and improved scenery rendering.

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create
the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world
by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2.12 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

=== Major enhancements in this release ===

'''Aircraft Modeling'''
* A new tracking animation provides an easy way for aircraft developers to animate complex kinematic systems like gear scissors or landing gear doors attached to struts. The animation can be implemented in Blender and then exported to FlightGear.

'''Environment'''

* Icebergs now appear in the arctic seas.
* Deciduous trees shed their foliage if they are above the snowline, creating a convincing winter look.
* The climatic snow line moves up and down as you fly around the world.
* Basic weather is now integrated with Atmospheric Light Scattering.
* Clouds are placed more realistically when using detailed weather modelling.

'''Transponder'''

The transponder instrument system has been overhauled, making it easier to use from panels, supporting Mode-S altitude encoding, and sending the important properties over multi-player. This will allow more realistic ATC interactions, since id (squawk) codes now matter! See this wiki page for more information on installing / updating the transponder installation in aircraft.

'''Performance'''

Many NavCache related startup issues experienced by Windows users (lag) were resolved

'''Portability'''

Portability for older systems without GLSL (shaders) support has been restored again, so that FlightGear no longer crashes on such systems.

'''Atmospheric Light Scattering'''
* An ultra-high quality shader has been introduced, algorithmically generating detail down to the centimetre scale.
* Autumn colors are now simulated from the middle of summer through to the beginning of winter.
* Low visibility conditions are now more realistically rendered.
* Trees move with the wind.
* Surf is now visibile below steep sea-cliffs.

''' Improved performance, reduced memory occupancy '''

''' Usability '''
* The checklist feature has been expanded.
** Checklist items are color coded to indicate whether they are complete - green for those items that are complete, yellow for those that are incomplete.
** To ease cockpit familiarization, users can request that the relevant control is highlighted.
** A virtual co-pilot can execute checklist items on behalf of the pilot.
** Tutorials are auto-generated from checklists providing a virtual instructor to guide you through completing the checklist.
* A knob animation generalizes the operation of knobs and switches in the cockpits of various aircraft.

* The Weather dialog has been improved to make it easier to understand.
* Tooltips (available under the Debug menu) provide feedback that computer pilots have to miss due to an absence of audio or haptic feedback. When you hover your mouse over a switch or lever, a little window tells you the current state of the switch.

''' Internationalization '''

* The menu and system messages have been translated to Portuguese.

'''Canvas System'''

The "canvas" system is FlightGear's fully scriptable 2D rendering system, which makes it easy for users to create new instruments, glass cockpit displays, HUDs and even dialogs and custom GUI widgets using FlightGear's built-in scripting language [[Nasal]] (which looks really similar to JavaScript).

Canvas improvements in this release include:
* The style setter system has been reworked, style setters are now only setup once for each element type and not for each element instance as before. A static map holds the setters for each element type. Also an animation type is stored which will later allow to animate properties of Canvas elements without specifying an animation type.
* The Nasal/cppbind framework has been improved to expose more Canvas internals to Nasal space
* Canvas textures can now not only be used as aircraft/cockpit textures (instruments, MFDs) and for the HUD/GUI, but also for scenery objects. Canvas textures can now be placed on scenery objects. This allows for example creating animated signs/monitors such as a Visual Docking Guidance System.
* Enable texture repeat for Canvas images
* Improved support for displaying GUI widgets.

'''Nasal Scripting'''
* All methods exposed to the Nasal props module now accept an optional first parameter refering to another node by a relative path.
* SimGear's SGTimer class is now fully exposed to Nasal, see the new '''maketimer'''() API.
* Several Nasal bugs that could previously trigger a crash were fixed.

'''Rembrandt'''

* A growing number of aircraft are compliant with the Rembrandt rendering technique.

'''AI Improvements'''

* AI scenarios may now be loaded at runtime.
* A broad range of AI aircraft received a fresh paint job. The Airbus A320 and A330 have been remodelled, while some other models got improved animations.
* Air-to-air refueling has been improved:
** Pilots can now have a choice of a number of AI air-to-air refueling tankers and can select the airspeed of the tanker to match their own aircraft if required.
** Tankers are more realistic, support multiple refuelling points, configurable fuel flow rates, and the refuelling "envelope" centered on the drogue/boom position.
** The probe position on the receiving aircraft taken into account when calculating whether contact has been made.
** Refuelling difficulty is configurable in-sim by setting the distance from the drogue/boom that refuelling occurs.
** The tanker is now able report a successful contact to the pilot.

''' Regional Textures '''

The following areas now include their own region-specific texturing and auto-generated models/buildings:
* Indonesia
* The Middle East
* The United Kingdom,
* The North Atlantic Islands - Faroe, Shetland, Greenland
* Madagascar

'''Highlighted new and improved aircraft'''
* Mudry CAP 10C
* Tupolev Tu-154B-2
* ASW-20

'''Other'''

* Additional joysticks and rudder pedals are supported out-of-the-box:
** GoFlight TQ6-ADV
** Genius Metalstrike 3D
** Microsoft SideWinder Precision Racing Wheel rudder pedals

'''Bug fixes'''

* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.12.0 our bugtracker] for an extensive, yet incomplete, list of the bugs fixed in this release.

[[Category:FlightGear changelogs]]
[[pl:Changelog 2.12]]

Pl/Changelog 2.12

2013-07-28T12:36:20Z

Zbyszek: Created page with "{{draft|changelog|This changelog is currently being written for the next FlightGear release. Feel free to help! If you are aware of any FlightGear related changes, please add ..."

{{draft|changelog|This changelog is currently being written for the next FlightGear release. Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.<br/>It's a good idea to check [[:Category:Changes_after_2.10|the newsletters since the last release]], and the git commit history.
To view the changelog for the most recent release, please see [[Changelog 2.10]]. }}

==Upcoming FlightGear Changelog==

The FlightGear development team is happy to announce the v2.12 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include improved usability, continued development of the Canvas rendering toolkit, and improved scenery rendering.

Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create
the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world
by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide scenery database, a multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2.12 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

=== Główne zmiany w tym wydaniu ===

'''Modelowanie samolotów'''
* Nowy system śledzenia animacji zapewnia łatwe rozwiąznie dla twórców samolotów, aby zanimować skomplikowane ruchy elementów, takie jak drzwi goleni podwozia przymocowane do zawiasów czy "gear scissors". Animacje mogą być zrobione w Blenderze i potem wyeksportowane do FlightGear
A new tracking animation provides an easy way for aircraft developers to animate complex kinematic systems like gear scissors or landing gear doors attached to struts. The animation can be implemented in Blender and then exported to FlightGear.

'''Środowisko'''

* Góry lodowe pojawiają się na morzach arktycznych.
* Drzewa liściaste tracą swoje listowie, jeśli znajdują się powyżej lini śniegu, tworząc przekonujący, zimowy wygląd
Deciduous trees shed their foliage if they are above the snowline, creating a convincing winter look.
* Klimatyczna linia śniegu podnosi się i opada podczas latania po całym świecie
The climatic snow line moves up and down as you fly around the world.
* "Basic weather" jest teraz połączone z "Atmospheric Light Scattering".
* Chmury są rozmieszczane bardziej realistycznie, kiedy używasz dokładnego modelowania pogody.

'''Transponder'''

The transponder instrument system has been overhauled, making it easier to use from panels, supporting Mode-S altitude encoding, and sending the important properties over multi-player. This will allow more realistic ATC interactions, since id (squawk) codes now matter! See this wiki page for more information on installing / updating the transponder installation in aircraft.

'''Wydajność'''

Wiele problemów związanych z NavCache doświadczanych przez użytkowników Windowsa (lagi) zostało rozwiązanych.

'''Zgodność'''

Znów została przywrócona zgodność ze starszymi systemami nie obsługującymi GLSL (shadery), więc FlightGear już nie odmawia współpracy z takimi systemami.

'''Atmospheric Light Scattering (rozpraszanie światła w atmosferze)'''
* Niezwykle zaawansowany shader wysokiej jakości pozwwala na automatyczne generowanie detali, nawet do kilku centymetrów.
* Wprowadzono symulacje jesiennych barw od środka lata do początku zimy.
* Warunki niskiej widoczności są teraz znacznie lepiej renderowane.
* Drzewa poruszają się z wiatrem.
* Widoczne są fale morskie przy wysokich klifach.

''' Zwiększona wydajność, zmniejszenie wymagań pamięci '''

''' Funkcjonalność '''
* Moduł checklist został rozbudowany.
** Punkty checklisty są kolorowane, w celu pokazania czy zostały wykonane, jeśli tak - są zielone, natomiast niekompletne - żółte
** Aby uwałtwić zapoznanie się z cockpitem, można podświetlić dany przyrząd.
** Wirtualny drugi pilot może wykonywać chcecklistę w imieniu kapitana.
** Tutoriale są automatycznie generowane na podstawie checklist, przez co wirtualny instruktor może Cię poprowadzić przez całą checklistę,
* A knob animation generalizes the operation of knobs and switches in the cockpits of various aircraft.

* Okno Pogody została przeprojektowane, aby ułatwić jego użytkowanie.
* Tooltips (available under the Debug menu) provide feedback that computer pilots have to miss due to an absence of audio or haptic feedback. When you hover your mouse over a switch or lever, a little window tells you the current state of the switch.

''' Tłumaczenie '''

* Menu oraz wiadomości systemowe zostały przetłumaczone na portugalski.

'''System Canvas '''

The "canvas" system is FlightGear's fully scriptable 2D rendering system, which makes it easy for users to create new instruments, glass cockpit displays, HUDs and even dialogs and custom GUI widgets using FlightGear's built-in scripting language [[Nasal]] (which looks really similar to JavaScript).

Canvas improvements in this release include:
* The style setter system has been reworked, style setters are now only setup once for each element type and not for each element instance as before. A static map holds the setters for each element type. Also an animation type is stored which will later allow to animate properties of Canvas elements without specifying an animation type.
* The Nasal/cppbind framework has been improved to expose more Canvas internals to Nasal space
* Canvas textures can now not only be used as aircraft/cockpit textures (instruments, MFDs) and for the HUD/GUI, but also for scenery objects. Canvas textures can now be placed on scenery objects. This allows for example creating animated signs/monitors such as a Visual Docking Guidance System.
* Enable texture repeat for Canvas images
* Improved support for displaying GUI widgets.

'''Nasal Scripting'''
* All methods exposed to the Nasal props module now accept an optional first parameter refering to another node by a relative path.
* SimGear's SGTimer class is now fully exposed to Nasal, see the new '''maketimer'''() API.
* Several Nasal bugs that could previously trigger a crash were fixed.

'''Rembrandt'''

* Wzrastająca liczba samolotów jest kompatybilna z techniką renderowania Rembrandt.

'''Ulepszenia AI'''

* Scenariusze AI mogą być ładowane w czasie działania symulatora.
* Duża część samolotów AI otrzymała nowe malowania. Airbus A320 i A330 zostały przemodelowane, podczas gdy w innych modelach ulepszono animacje.
* Tankowanie w powietrzu zostało udoskonalone.
** Pilots can now have a choice of a number of AI air-to-air refueling tankers and can select the airspeed of the tanker to match their own aircraft if required.
** Tankers are more realistic, support multiple refuelling points, configurable fuel flow rates, and the refuelling "envelope" centered on the drogue/boom position.
** The probe position on the receiving aircraft taken into account when calculating whether contact has been made.
** Refuelling difficulty is configurable in-sim by setting the distance from the drogue/boom that refuelling occurs.
** The tanker is now able report a successful contact to the pilot.

''' Regionalne tekstury '''

Następujące miejsca mają teraz własne, indywidualne tekstury oraz automatycznie generowane budynki:
* Środkowy Wchód,
* Wielka Brytania,
* Wyspy na północnym Atlantyku - Wyspy owcze, Szetlandy, Greenlandia,
* Madagaskar.

'''Wyróżnione i poprawione samoloty'''
* Mudry CAP 10C
* Tupolev Tu-154B-2
* ASW-20

'''Inne'''

* Dodatkowe joysticki i pedały orczyka zyskały wsparcie:
** GoFlight TQ6-ADV
** Genius Metalstrike 3D
** Microsoft SideWinder Precision Racing Wheel rudder pedals

'''Bug fixes'''

* Idź na [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.12.0 our bugtracker], aby zobaczyć niekomplentą jeszcze listę bugów naprawionych w tym wydaniu.

[[Category:FlightGear changelogs]]
[[en:Changelog 2.12]]

Pl/Changelog 2.8.0

2012-08-22T10:20:42Z

Zbyszek: Created page with "== FlightGear 2.8.0 ChangeLog == The FlightGear development team is happy to announce the v2.8.0 release of FlightGear, the free, open-source flight simulator. This new versio..."

== FlightGear 2.8.0 ChangeLog ==
The FlightGear development team is happy to announce the v2.8.0 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Major improvements from v2.6.0 include improved AI aircraft, up to date with all the recent JSBSim flight dynamics model improvements, support for region specific textures, better random 3d buildings, better random object placement, 3d airport signage, in-sim toggling between summer and winter texture sets. The core FlightGear code now supports a flexible 2d rendering system which can be used to accurately model glass cockpit displays and other complex instrumentation. There are many new and improved aircraft to explore. A new automated system is now available for scenery submissions that automatically get rolled into the scenery distribution to be enjoyed by everyone. Version 2.8 has improved atmospheric light scatter modeling, better terrain haze, and improved 3d clouds.

A very exciting new addition is “Project Rembrandt”. This is still considered “experiemental” and not enabled by default. But when you turn it on you will get real-time shadows, support for multiple light sources (landing lights, instrument lights, directional ground spotlights, even the rotating beacons illuminate the surrounding correctly.) In addition, Project Rembrandt offers a variety of other visual effects such as night vision, film grain effects, depth of field effects, lens (i.e. fisheye) distortion — all in real time.

Founded in 1997, FlightGear celebrated the 15th anniversary of it’s first official release in July. FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for University research and education, for a variety of aerospace engineering and visualization work in industry, and even for interactive exhibits in museums.

FlightGear features more than 400 aircraft, a worldwide seamless scenery database, a worldwide multi-player environment, detailed sky modelling, a flexible and open aircraft modelling system, varied networking options, multiple display support, a powerful scripting language, and an open architecture. Best of all, being open-source, the simulator is owned by the community and everyone is encouraged to contribute.

Download FlightGear v2.8.0 for free from [http://www.flightgear.org FlightGear.org]

FlightGear - Fly Free!

===Do niektórych z głównych zmian należą ===

'''Ruch AI'''
* Ulepszone modele samolotów i tekstury.

'''Modele lotu'''
* FlightGear zostatło zsynchronizowane z projektem JSBSim.

'''Środowisko'''
* Dostępne są regionalne tekstury dla Europy i Hawaii. Miasta w Europie mają inny wygląd niż te w USA.
* Miasta i miasteczka wyglądają obecnie na bardziej zaludnione, dzięki losowym budynkom wyposażonym w nocną illuminacje.
* Sceneria stała sie bardziej realistyczna, dzięki postępie w umieszczaniu losowych obiektów, budynków i drzew.
* Znaki lotniskowe są teraz renderowane w 3d, z wsparciem dla dwustronnych zanków. Pełna współpraca apt.dat 850 jest obsługiwana.
* Możesz wybrać letnią/zimową scenerię w symulatorze.

'''Przyrządy & HUD'y'''
* Nowy, elastyczny system renderowania 2d zaprojektowany dla skomplikowanych przyrządów takich jak CDU, MFD, EICAS, HUD oraz innych wyświetlaczy glass cockpit. [[Canvas]] pozwala twórcom samolotów na proste budowanie skomplikowanych przyrządów bez potrzeby stosowania wyspecjalizowanego kodu C++.

'''Interfejs'''
* Wsparcie dla tłumaczeń menu głównego na języki inne niż angielski.
* Dostępne jest Nasal API pozwalające na dostęp do danych nawigacyjnych i menadżera tras.

'''Wyróżniające się i dopracowane samoloty'''
* [[Airwave Xtreme 150]]: całkowicie nowy model lotu (JSBSim), nowy model 3d, zaawansowane animacje pilota.
* [[Cessna 337G Skymaster]]

'''Infrastruktura projektu '''
* Wiele udostkonaleń w naszej bazie danych scenerii, pozwala łatwiej niż kiedykolwiek dodawać, usuwać lub aktualizować obiekty w świecie FlightGear.
* Nowa strona pobierania samolotów pozwala na łatwe znalezienie wysokiej jakosci samolotów przez fitrowanie statusu.

'''Efekty graficzne'''
* Rozwinięta symulacja rozpraszania światła w atmosferze z zamgleniem terenu.
* Eksperymentalny system renderowania, nazwany po sławnym malarzu "Rembrandt" został włączony i udostępniony do testowania. An experimental renderer, named after the famous painter Rembrandt, is included for testing purposes. [[Project Rembrandt]] wspiera wiele źródeł światła (światła lądowania, przyrządów), cienie w czasie rzeczywistym oraz ambient occlusion dla o wiele lepszych doznać wizualnych.

'''Inne'''
* Dodatkowe joysticki i pedały orczyka są wspierane:
** InterLink Elite
** Micorosft Xbox 360 Controller
** Qware USB
** Saitek Cyborg X (F.L.Y. 5)
** Saitek Pro Flight Cessna Yoke
** Saitek Pro Flight Cessna Trim Wheel
** Saitek Pro Flight Cessna Rudder Pedals
** Speedlink Defender
* Częściowe tłumaczenie Podręcznika FlightGear jest dostępne dla języka francuskiego.

'''Bug fixes'''
* Zobacz [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D2.8.0 nasz bugtracker] dla obszernej listy błędów, które zostały naprawione w tym wydaniu
[[Category:FlightGear changelogs]]
[[en:Changelog 2.8.0]]
[[fr:Changelog 2.8.0]]
[[nl:Changelog 2.8.0]]

Category:Airports in Poland

2012-04-27T22:13:41Z

Zbyszek:

Zielona Góra Airport

2012-04-27T22:11:27Z

Zbyszek: Created page with "{{infobox Airport |name = Zielona Góra Airport |image =EPZG_Terminal.png |alt =Zielona Góra Poland scenery |iata =IEG |icao =EPZG |type =public |owner =Przedsiębiorstwo..."

{{infobox Airport
|name = Zielona Góra Airport
|image =EPZG_Terminal.png
|alt =Zielona Góra [[Poland]] scenery
|iata =IEG
|icao =EPZG
|type =public
|owner =Przedsiębiorstwo Państwowe "Porty Lotnicze" (PPL)
|city =Zielona Góra, [[Poland]]
|runway= 06/24
|length= 2500 m
|material=Asfalt

|website =http://www.lotnisko.zielonagora.pl
|scenerytile =e010n50
}}

'''Zielona Góra-Babimost Airport''' (Polish: Port Lotniczy Zielona Góra-Babimost) (IATA: IEG, ICAO: EPZG) is a regional airport located within the greater Zielona Góra agglomeration (the so-called Lubusian Tri-city) in western Poland. It lies 10 km (6.2 mi) from Sulechów, or 35 km (22 mi) northwest of the Zielona Góra city centre.

== ATC ==

Please use [[FGCom]], it facilitates the work of traffic controllers.

'''Languages'''

You can communicate with ATC using English or Polish

== Scenery ==
EPZG Terrain is includen in the [[Poland]] scenery, which is available at [http://code.google.com/p/custom-scenery-roztocze/downloads/list?saved=1&ts=1314341645]. Buildings here: [http://code.google.com/p/sceneria-epzg-babimost/downloads/list]

== External links ==
* [http://code.google.com/p/sceneria-epzg-babimost/downloads/detail?name=EPZG%20fix%2C%20vor.rar&can=2&q=Additional Nav data]
[[pl:Lotnisko Zielona Góra]]

[[Category:Airports in Poland]]

File:EPZG Terminal.png

2012-04-27T22:08:11Z

Zbyszek:

=={{int:filedesc}}==
{{Information
|description={{en|1=Zielona Góra Airport terminal.}}
|date=2012-04-28
|source=sended to me by author
|author=Damian Piątek
|permission=
|other_versions=
|other_fields=
}}

=={{int:license-header}}==
{{FAL}}

Pl/FlightGear Git na Windows

2012-04-15T13:49:56Z

Zbyszek: Created page with "{{WIP}} {{FlightGearGitOn}} Ten dokument zawiera wskazówki, które przeprowadzą cię przez proces instalacji rozwojowej wersji FlightGear (Git) na Windows. == Pierw..."

{{WIP}}
{{FlightGearGitOn}}
Ten dokument zawiera wskazówki, które przeprowadzą cię przez proces instalacji rozwojowej wersji [[FlightGear]] ([[Git]]) na Windows.

== Pierwsza instalacja Git ==
=== Przygotowanie przed instalacyjne ===
Zanim zaczniemy, wybierzmy folder docelowy instalacji. To może być jakikolwiek dysk na twoim komputerze. W tym artykule zakladamy, że instalujesz FlightGear na dysku D:/. Jeżeli wybrałeś inną lokalizacje, po prostu zamień komendy podane w tym dokumencie swoją własną.

Stwórz następujące katalogi na swoim dysku:

* <tt>FlightGear/</tt>
** <tt>bin/</tt>
*** <tt>win32/</tt>
** <tt>data/</tt>

=== Uzyskiwanie danych z Git ===

Możesz użyć jakiegokolwiek oprgoramowania Git, jednak radzimy użycie msysGit (który będzie używany w tym dokumencie). Możesz go poprać stąd:[http://code.google.com/p/msysgit/downloads/list this link]. Podążaj za wskazówkami pobrania i instalacji wyświetlającymi się na ekranie.

Jeśli masz wolne połączenie internetowe lub nie możesz mieć przez długi czas włączonego komputera - pobieranie danych jest bardzo czasochłonne, użyj Metody 2

==== Metoda 1: ====
Zanim zaczniesz, upewnij się, że ścieżka docelowa (którą utworzyłeś podczas dodawania katalogów) NIE zawiera istniejącej kopii FlightGear!

[[File:msysgit_clone_fgdata.jpg|thumb|270px|Okno Git Bash]]
Otwórz Git Bash przez <tt>C:/Program Files/msysgit/Git Bash</tt> (lub przez skrót) i wpisz (zamieniając ścieżkę na własna):
cd D:/FlightGear/data

W sytuacji gdy program odmawia przeczytania pliku, spróbuj:
cd "D:/FlightGear/data"

(zamień powyższy adres ścieżką gdzie twój folder fg/data powinien być - upewnił się, ze nie ma tam żadnego pliku!)

Następnie wpisz następującą komendę, aby zainicjalizować repozytorium Git. Powinien utworzyć się folder .git w lokalizacji data/.

git init

Dodaj następną komendę i kliknij Enter.

git clone git://gitorious.org/fg/fgdata.git

Teraz msysGit pobierze cały katalog fgdata do wybranej przez ciebie lokalizacji <tt>FlightGear/data</tt>. '''To może zając kilka godzin w przypadku wolnych połączeń internetowych!'''

'''WAŻNE:''' Upewnij się, że używasz msysGit 1.7.0.2 lub nowszej wersji, wcześniejsze miały problem z pobieraniem dużych paczek i nie ściągną niczego większego niz 2Gb.

'''WAŻNE II:''' Some files demand that CR/LF (carriage return / line feed) line breaks are kept in the way they are stored on Gitorious. Make sure to set "git-config core.safecrlf true" and "git-config core.autocrlf false" in your options or you may receive nasty error or even a crash on startup of FG (e.g. fgtzfile_read(): : Invalid argument... Fatal error: Timezone reading failed).

==== Metoda 2: ====
Ściągnij <tt>fgdata.bundle</tt> z http://peter-server.homelinux.net/fgdata/fgdata/
lub http://flightgear.mxchange.org/pub/fgfs/. Użyj <tt>Prawego przycisku mysze > Zapisz jako</tt> jeśli trafisz na stronę internetową pełną dziwnych znaków.

Po pobraniu, potwierdź, że pliki nie są uszkodzone używając tej sumy kontrolnej MD5:
2996221BD2B8AB7740F332F49396CF56
Możesz zweryfikować sumę kontrolną pliku używakjąc jakiegokolwiek darmowego narzędzia sprawdzania Md5, jak na przykład to:
http://www.bullzip.com/products/md5/info.php
Powinna pasować do tej podanej wyżej. Jeśli nie, pobierz jeszcze raz.

Skopiuj ten plik do <tt>FlightGear/data</tt>.

Otwórz Git Bash przez <tt>C:/Program Files/msysgit/Git Bash</tt> (lub skrót) i uruchom skrypt (zmieniajac ścieżkę na preferowaną przez ciebie):
cd FlightGear/data
git clone fgdata.bundle

Teraz msysGit pobierze cały katalog fgdata do wybranej przez ciebie lokalizacji <tt>FlightGear/data</tt>.
Poczekaj kilka minut, kiedy się skończy pojawi się migający kursor.

Jeżeli wyskoczy ten błąd:

warning: unrecognized header: -deg" - /orientation/roll += "-deg" - /position/altitude += "-ft" - /position/altitude-agl += "-ft" - /position/latitude += "-deg" - /position/longitude += "-deg" - /radios
/adf/frequencies/selected += "-khz" - /radios/adf/frequencies/standby += "-khz" - /radios/adf/rotation += "-deg" - /radios/nav1/* => /radios/nav[0]/* - /radios/nav2/* => /radios/nav[1]/* - /radios/nav[*]
/dme/distance += "-nm" - /radios/nav[*]/frequencies/selected += "-mhz" - /radios/nav[*]/frequencies/standby += "-mhz" - /radios/nav[*]/radials/actual += "-deg" - /radios/nav[*]/radials/selected += "-deg" -
/sim/view/goal-offset += "-deg" - /sim/view/offset += "-deg" - /steam/adf += "-deg" - /steam/airspeed += "-kt" - /steam/altitude += "-ft" - /steam/gyro-compass += "-deg" - /steam/gyro-compass-error += "-deg" -
/steam/mag-compass += "-deg" - /steam/vertical-speed += "-fpm" - /velocities/airspeed += "-kt" - /velocities/side-slip += "-rad" - /velocities/speed-down += "-fps" - /velocities/speed-east += "-fps" -
/velocities/speed-north += "-fp
warning: remote HEAD refers to nonexistent ref, unable to checkout.

uruchom tą komendę:
cd fgdata

i naciśnij enter
następnie
git checkout -b master origin/master

Powinno być już naprawione.

Teraz pobierz z GIT, aby zaktualizować ostatnie pliki, których używałeś:

git pull git://gitorious.org/fg/fgdata.git master

=== Pobieranie plików binarnych ===
Now we've got all the data, we need to have a binary, which contains the actual software that runs FlightGear.
* Go to http://flightgear.simpits.org:8080/job/Win32-installer-Cmake/ and download the <tt>fgfs_win32_nightly_*.exe</tt> file. Run the installer and follow its instructions. Let it install the binary into your <tt>FlightGear/bin/win32</tt> directory.
* If you want to automate this, you can run the installer in silent mode by passing the /S parameter, the /D parameter can be used to set the target directory into which he needs to install the binaries:
** e.g. ''fgfs_win32_vs2010_nightly_2.7.0.exe /S /D=C:\Flightgear\bin''

If your antivirus warns you of a trojan, ignore. AVG and avast! are known for false positives.

=== Running FlightGear ===
Run <tt>FlightGear/bin/win32/fgrun.exe</tt> to launch the [[FlightGear Wizard]], or run <tt>FlightGear/bin/win32/fgfs.exe</tt> by commandline.

== Keeping your FlightGear up to date ==
Of course you want to keep FlightGear up to date, to keep current with the latest developments. Else you don't have a reason to use the development version.

# Download the latest binary, as described in [[#Getting the binary|Getting the binary]] and overwrite the old one in <tt>FlightGear/bin/win32</tt> (instead you could rename the current binary's directory to something like win32_latest, in case the newer binary doesn't work well).
# Update your <tt>FlightGear/data/</tt> directory, to match it with the binary. For smooth operations, it is very important to have data and a binary from matching dates!
## Navigate to <tt>FlightGear/data/</tt> directory and open Git Bash.
## Run ''git reset --hard'' to revert any local changes. <font color="red">'''Note: this will delete all local changes! If you made local changes, make sure to backup those first, outside your FlightGear data directory! Or, better, learn to commit your changes to your local git repository.'''</font>
## Run ''git pull'' and let it update, this can take a while.

== Commiting changes ==
As a developer, you probably want to share your work with the world. For FlightGear, most developers do this by commiting stuff to the Git repository.

=== Getting started ===
# Register an account at [http://gitorious.org Gitorious].
# [http://gitorious.org/fg/fgdata/clone Clone fgdata].
# Open Git Bash in your data directory and run ''ssh-keygen''.
# Enter the name of the file in which you prefer to save the key and press Enter.
# Enter your password/passphrase and press Enter. You'll have to do this twice.
# Your key is now being generated. Open the .pub file with an editor (eg. Notepad++) and copy the content.
# Visit your dashboard at Gitorious and navigate to "Manage SSH keys".
# Click the "Add SSH key" button and paste the content of the .pub file. Follow the instructions on the screen.
# Open Git Bash in your data directory and run ''git remote add fgdata git://gitorious.org/fg/fgdata.git''. This adds a remote ref to the master fgdata repository in Gitorious. You can also add the mapserver URL by running ''git remote add fgdata-mapserver git://mapserver.flightgear.org/fgdata/'', which may be faster than Gitorious.
# Now run ''git remote set-url origin <url>'', where ''<url>'' is the line that you get by clicking SSH on your fgdata clone page at Gitorious (should be something like ''git@gitorious.org:~your/fg/yours-fgdata.git''). This switches the origin ref to the correct URL that Gitorious will take when updating.

It is recommended to split your new fgdata clone into separate local branches for your work. For instance, if you're working on the [[Boeing 747-400]] and the [[Howto: Aircraft Reflection Shader|aircraft reflection shader]], you might create 2 branches named "747-400" and "reflect-shader". To do this,
# ''git checkout master''
# ''git branch <branch name>''
# ''git checkout <branch name>''

Then you can make your changes to the new local branch(es), which will make merge requests easier for both yourself and committers. To switch in between branches, simply use
* ''git checkout <branch name>''

=== Pulling ===
To pull updates from the master fgdata repository,
* <branch name> is the name of the branch you want to update.
* <ref> is the repository ref. If you followed the [[#Getting Started|getting started]] section, this will be "fgdata" or "fgdata-mapserver".
# ''git checkout <branch name>''
# ''git pull <ref>''
# Assuming you got no merging errors, run ''git push origin <branch name>'' to push the updates out to Gitorious.

=== Pushing ===
{{WIP}}
To push local updates to your fgdata clone,
* <branch name> is the name of the local branch you want to push.
# ''git checkout <branch name>''
# Use ''git status --'' to list all the changed files.
## If you want to commit all changed files, run ''git commit -a'' and type your commit message.
## If you only want to commit some files, run ''git add <path/to/file>'' to add certain files (you can use ''git add --all <path/to/folder>'' to add all files within a certain folder) and ''git rm <path/to/file>'' to mark files you have removed for deletion in the repository.
# If you used ''git commit -a'', the commit has already been created for you. Otherwise, run ''git commit -m "<commit message>"'' (quotes required), where <commit message> is the message for your commit (i.e. "747-400: Improved lightmaps").
# ''git push origin <branch name>''

==== Rebase the development branch ====
Normally developments take some time, so the root of a development branch most likely will be outdated by the time the development is finished and a merge can be prepared. In order to make the merge easier for the contributor, it could be helpful to rebase the development branch to the current HEAD of the master.

Let <branch name> be the name of the local branch you want to push, that branch contains your work.
Furthermore, <tt>fgdata</tt> refers to the repository at <tt>git://gitorious.org/fg/fgdata</tt>, i.e. the official repository, whereas <tt>origin</tt> refers to your personal Gitorious repository.(You can use <code>git remote -v</code> to learn about all the remotes and their names.)

# Switch to that branch: <code>git checkout <branch name></code>
# Rebase your branch to the current HEAD of fgdata/master: <code>git rebase fgdata/master</code>
# Push your rebased development branch to your personal Gitorious repo
## First try <code>git push origin</code>. If that produces some warnings about merges, you can
## force it by using <code>git push origin -f</code> .

For more details on what rebasing does, check out http://book.git-scm.com/4_rebasing.html.

==== Creating a merge request ====
# Check that the commit to your fgdata clone is recognized by Gitorious.
# Click the "Request merge" button on your fgdata clone page. Loading the next page can take a while, as it will list all commits of the past years!
# Once again write a short summary (could be the same as used with git commit), but this time, also write an explanation of your merge request (what does it do). Make sure you set target repository to fgdata, Target Branch to master and Source Branch to the local branch with your updates.
# Tick the box in front of your commit and click the "Create merge request" button.
# Now, all you have to do is contact a [http://gitorious.org/+flightgear-developers contributor] and wait untill he accepts your merge request ;)

Creating merge requests using this method literally means merging an entire branch into fgdata; this may not be desirable for some situations, such as small changes that only require one little commit. There's a neat method to only push certain commits to a merge request discussed by Anders Gidenstam [http://flightgear.org/forums/viewtopic.php?f=4&t=10392&start=45#p115747 on the FlightGear Forums].
[[en:FlightGear Git on Windows]]

FlightGear Newsletter March 2012

2012-03-10T20:09:07Z

Zbyszek: /* Airport of the month */

File:EPWA service.png

2012-03-10T19:36:02Z

Zbyszek:

File:EPWA night.png

2012-03-10T19:35:42Z

Zbyszek:

Category:Airports in Poland

2012-03-10T16:14:42Z

Zbyszek:

[[Category:Airports]]

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! class="unsortable" style="background:#efefef" | Comment
|-
| EPWA || [[Warsaw Chopin Airport]], Warsaw || custom layout, 3d models, airport service || stalled || Part of [http://code.google.com/p/custom-scenery-roztocze/downloads/list?saved=1&ts=1314341645 Poland Custom Scenery]
|-
| EPSC || [[Goleniow Airport]], Goleniów/Sczecin || custom layout, 3d models, airport service || stalled || Part of [http://code.google.com/p/custom-scenery-roztocze/downloads/list?saved=1&ts=1314341645 Poland Custom Scenery]
|-
| EPDE || [[Deblin Airport]], Dęblin || custom layout, 3d models || stalled || Part of [http://code.google.com/p/custom-scenery-roztocze/downloads/list?saved=1&ts=1314341645 Poland Custom Scenery] Military/Cyvil airport
|-
|}

Poland

2012-03-10T16:02:49Z

Zbyszek: Created page with "{{stub}} '''Poland''' (Polish: Polska), officially the Republic of Poland (Polish: Rzeczpospolita Polska), is a country in Central Europe, bordered by Germany to the west; the C..."

{{stub}}

'''Poland''' (Polish: Polska), officially the Republic of Poland (Polish: Rzeczpospolita Polska), is a country in Central Europe, bordered by Germany to the west; the Czech Republic and Slovakia to the south; Ukraine, Belarus and Lithuania to the east; and the Baltic Sea and Kaliningrad Oblast, a Russian exclave, to the north. The total area of Poland is 312,679 square kilometres (120,726 sq mi), making it the 9th largest in Europe. Poland has a population of over 38 million people.

== FlightGear community ==

FlightGear community has own Facebook site [http://www.facebook.com/pages/FlightGear-Polska/184032164996361]

Due to server problems forum adress has been changed. Forum is still beta, so please be patience.
[http://www.flightgear.darmowefora.pl/index.php Polish FlightGear Forum]

== Scenery Projects ==

There are a few scenery projects for Poland. <br>

See [http://wiki.flightgear.org/Category:Airports_in_Poland Category:Airports in Poland]

Warsaw Chopin Airport

2012-03-10T14:03:06Z

Zbyszek:

{{infobox Airport
|name = Lotnisko Chopina w Warszawie
|image =EPWA.png
|alt =Okęcie [[Poland]] scenery
|iata =WAW
|icao =EPWA
|type =public
|owner =Przedsiębiorstwo Państwowe "Porty Lotnicze" (PPL)
|city =Warsaw, [[Poland]]
|runway= 15/33
|length= 3690 m
|material= Asfalt
|runway2= 11/29
|length2= 2800 m
|material2=Asfalt

|website =http://www.lotnisko-chopina.pl/
|scenerytile =e020n50
}}

'''Warsaw Chopin Airport''' (Polish: Lotnisko Chopina w Warszawie) (IATA: '''WAW''', ICAO: '''EPWA''') is an international airport located in the Włochy district of Warsaw, [[Poland]]. Poland's busiest airport, Warsaw Chopin handles just under 50% of the country's air passenger traffic. Warsaw Chopin handles approximately 300 scheduled flights daily and an ever rising number of charters. London, Frankfurt, Paris, and Amsterdam are the busiest international connections, while Kraków, Wrocław, and Gdańsk are the most popular domestic ones.

== ATC ==

'''Frequencies'''

GND 121.9 <br>
TWR 118.3 <br>
APP 129.37 <br>

Please use [[FGCom]] it facilitates the work of traffic controllers

'''Languages'''

You can communicate with ATC using English or Polish

== Scenery ==
Chopin Airport is included in the [[Poland]] scenery, which is available at [http://code.google.com/p/custom-scenery-roztocze/downloads/list?saved=1&ts=1314341645].
EPWA scenery contains:
*custom airport layout (v.810)
*signs
*terminals, hagars, tower models
*day/night photorealistic textures
*details like custom lamps
*airport service vehicles(ot-666 models)

== External links ==
* [http://www.arminair.darmowefora.pl/index.php?topic=316.0Airport Diagrams]
[[pl:Lotnisko Chopina w Warszawie]]

[[Category:Airports in Poland]]

Warsaw Chopin Airport

2012-03-10T12:09:22Z

Zbyszek: Created page with "{{infobox Airport |name = Lotnisko Chopina w Warszawie |image =EPWA.png |alt =Okęcie Poland scenery |iata =WAW |icao =EPWA |type =public |owner =Przedsiębiorstwo Państwowe..."

{{infobox Airport
|name = Lotnisko Chopina w Warszawie
|image =EPWA.png
|alt =Okęcie [[Poland]] scenery
|iata =WAW
|icao =EPWA
|type =public
|owner =Przedsiębiorstwo Państwowe "Porty Lotnicze" (PPL)
|city =Warsaw, [[Poland]]
|runway= 15/33
|length= 3690 m
|material= Asfalt
|runway2= 11/29
|length2= 2800 m
|material2=Asfalt

|website =http://www.lotnisko-chopina.pl/
|scenerytile =e020n50
}}

'''Warsaw Chopin Airport''' (Polish: Lotnisko Chopina w Warszawie) (IATA: '''WAW''', ICAO: '''EPWA''') is an international airport located in the Włochy district of Warsaw, [[Poland]]. Poland's busiest airport, Warsaw Chopin handles just under 50% of the country's air passenger traffic. Warsaw Chopin handles approximately 300 scheduled flights daily and an ever rising number of charters. London, Frankfurt, Paris, and Amsterdam are the busiest international connections, while Kraków, Wrocław, and Gdańsk are the most popular domestic ones.

== ATC ==

TODO

== Scenery ==
Chopin Airport is included in the [[Poland]] scenery, which is available at [http://code.google.com/p/custom-scenery-roztocze/downloads/list?saved=1&ts=1314341645].

== External links ==
* [http://www.arminair.darmowefora.pl/index.php?topic=316.0Airport Diagrams]
[[pl:Lotnisko Chopina w Warszawie]]

[[Category:Airports in Poland]]

File:EPWA.png

2012-03-10T11:50:06Z

Zbyszek:

FlightGear Newsletter December 2011

2011-12-29T10:42:12Z

Zbyszek: /* Custom Poland scenery */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

[[Image:Fgfs-screen-372-gooneybird-xmas-2011.jpg|thumb|Gooneybird's xmas wishes]]

== Development news ==

=== FlightGear development over time ===
Graphics created by stuart:

[[File:6month.png]]

"As you can see, FG development has been quite variable over time (generally a lot of development in the northern hemisphere winter), but core development, as shown by the red and blue lines (FG is made up of the separate simgear and flightgear codebases) has been fairly constant since the start of the project.It also highlights the massive increase in aircraft over the last couple of years, as shown by the amount of change to fgdata (yellow line)."

For more info, please see [http://flightgear.org/forums/viewtopic.php?f=42&t=12881#p131567].

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

=== New terrain textures ===
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository.
More info and screenshots in this forum [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14254 thread]. This is still work in progress, of course.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* '''How long have you been involved in FlightGear?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created. These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
==== CASA C-101 Aviojet ====
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===
====Learjet 35-A====
The [[Learjet 35-A]] has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it (download soon on forum) and take your favorite plane. There are some really nice areas just perfect for long VFR routes!<br>
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html the mailinglist].

=== EBAW (Antwerpen - Deurne) ===

Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)

This scenery, is sadly enough, not yet available with terrasync. You can download it from the [https://gitorious.org/dvanmosselbeen/flightgear-custom-scenery Belgian scenery git repo].

[[File:Ebaw_textured_01.jpg|200px]][[File:Ebaw_textured_02.jpg|200px]][[File:Ebaw_textured_03.jpg|200px]]

Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit and the request is done!

The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

P.A.F. ( LFLG home base ) wish you a Merry X-mas!
[[File:LFLG Lancair Chrismas.png|1200 px]]

Merry X-mas!

PAF link : http://equipe-flightgear.forumactif.com/t835-hangar-de-la-paf

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===Updated articles===
*[[Learjet 35-A]] is updated matching the true Aircraft flight manual (with FlightGear limitations). On the Wiki it is one of the best described aircraft.
*[[Unique Features]] now contains a massive list of what makes [[FlightGear]] unique.
*[[De/Flughöhe]] is close to complete matching the English version.
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|2eGOdBsd8Os|400|F-4E formation training at TFFG}} (Also see [[Toward real close formation flight]])
{{#ev:youtube|9_4zOOZTWqI|400|Santa Claus doing a practice run for his big night in December.}}

=== New tutorials and screencasts ===
=== Forum news ===
[[File:Santa2011.png]]

The headers on [http://flightgear.org/forums the forum] have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?

=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
You can turn on [[Anti-aliasing]], I know I didn't.
[[Category:FlightGear Newsletter|2011 12]]

FlightGear Newsletter December 2011

2011-12-15T16:27:11Z

Zbyszek: /* Custom Poland scenery */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado Scenery, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html]

=== Shader dialog revamp completed ===
Gijs has been working hard to revamp the shader dialog, for more details please see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34919.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* '''How long have you been involved in FlightGear?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created. These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
=== CASA C-101 Aviojet ===
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it and take your favorite plane. There are some really nice areas just perfect for long VFR routes!<br>
[[File:roztocze_1.png|200px]][[File:roztocze_2.png|200px]][[File:roztocze_3.png|200px]]<br><br>

Download! (none yet)

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added in FG tools on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!). Once clicked on submit, the request is done!
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|LyBUPlf5NSw|400|diamond formation flight by jano}} (Also see [[Toward real close formation flight]])

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2011 12]]

File:Roztocze 3.png

2011-12-15T16:24:28Z

Zbyszek: custom Poland scenery

custom Poland scenery

File:Roztocze 2.png

2011-12-15T16:19:18Z

Zbyszek: custom Poland scenery

custom Poland scenery

File:Roztocze 1.png

2011-12-15T16:16:20Z

Zbyszek: custom Poland scenery

custom Poland scenery

FlightGear Newsletter December 2011

2011-12-15T16:13:19Z

Zbyszek: /* Scenery corner */

{{Draft|newsletter|Please read [[FlightGear Newsletter November 2011|the latest edition]].}}

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== Feature freeze for the 2.6.0 release ===
(placeholder) http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34864.html and http://flightgear.org/forums/viewtopic.php?f=11&t=14627

=== Aircraft maintenance ===
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see [[Aircraft maintenance]] for more info.

=== Improving random trees & buildings ===
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35035.html].

=== Marketting of 2.6.0 via FS Break podcast ===
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35023.html]

=== Trying to get more performance out of the 3D clouds! ===
There has been quite a lengthy discussion on optimizing FlightGear's 3D clouds even more, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35092.html] and [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35100.html].

=== Improvements to the radio code in FlightGear ===
The FlightGear radio code has been recently overhauled, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg35010.html].

=== Southwest Colorado Scenery - beta 4 ===
New custom built scenery has been made available for the region of Southwest Colorado Scenery, for more info please see: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34986.html]

=== Shader dialog revamp completed ===
Gijs has been working hard to revamp the shader dialog, for more details please see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34919.html].

=== Sound support for AI traffic ===
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34985.html].

=== New performance dialog ===
FlightGear core developer ThorstenB has added a new subsystem and a dialog to monitor FG performance. It's replacing/improving the original code which was only capable of writing statistics data to the console (presumably, few people ever used or were even aware of the old option). The new GUI dialog is available in the menu: "Debug" => "Monitor system performance". More info is available here: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg34886.html]. A screen shot can be found here: http://imageshack.us/photo/my-images/521/fgfsscreen031.png/

=== Shaders ===
Shader development continues at a breakneck pace! We now have a nice wet runway effect:

http://imageshack.us/photo/my-images/571/fgfsscreen011.jpg/

http://imageshack.us/f/859/fgfsscreen013.jpg/

We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.

http://imageshack.us/photo/my-images/189/fgfsscreen024.jpg/

http://imageshack.us/photo/my-images/703/fgfsscreen025.jpg/

http://imageshack.us/photo/my-images/6/fgfsscreen026.jpg/

http://imageshack.us/photo/my-images/18/fgfsscreen027.jpg/

http://imageshack.us/f/525/fgfsscreen020.jpg/

It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.

At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the <tt>View > Rendering Options</tt> dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.

Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.

This is all in fgdata in Gitorious now - use <tt>--materials-file=materials-dds.xml</tt> and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.

== Logo & banner contest ==
[[File:Fg26banner2_by_someguy.jpg]]

A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See [http://flightgear.org/forums/viewtopic.php?f=67&t=14597 the forum thread] for the latest submissions and send in your own ideas.

== Interview with a contributor (Olivier Jacq) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* '''How long have you been involved in FlightGear?'''
I've been following FG closely since [[FlightGear 0.9.8]]. So, checking on the Wiki, this already dates back to... 2005!

* '''What are your major interests in FlightGear?'''
At first, I was using FG as a "casual" user, mainly contributing positions in my local area ([[Brittany]]) and especially the [[Brest]] area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!

* '''What project are you working on right now?'''
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under
development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!

* '''What do you plan on doing in the future?'''
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!

* '''Are you happy with the way the FlightGear project is going?'''
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.

* '''What do you enjoy most about developing for FlightGear?'''
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg [[radio propagation]] early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small
projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.

* '''Have you previously used other flight simulators or simulation software in general?'''
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features,
compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So
everyone should be able to contribute to FG (in a proper manner), that's the way to success!

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!

* '''Is there anything else you'd like to share with us?'''
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created. These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

=== New aircraft ===
=== CASA C-101 Aviojet ===
[[File:C-101screenshot_02.png|thumb|250px|CASA C-101EB with "Patrulla Águila" colors]]
The Spain-Latinamerica's community [http://www.vivefg.org Vive FlightGear!] recently introduced the [[CASA C-101 Aviojet]] to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.

This ''beta'' release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.

[http://www.flightgear.org/forums/viewtopic.php?f=4&t=14523 CASA C-101 official forum post]

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Custom Poland scenery ===
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it and take your favorite plane. There are some really nice areas just perfect for long VFR routes!

=== Tools ===
[[File:Fg_submission_form.png|thumb|250px|FG scenery submission tool]]
Added in FG tools on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FG scenery database. We hope this will make the number of positions increase!

The steps are very easy to follow :

* Place the object within FG.
* Take the data and copy/paste it within the form (please double check the content of what you're inserting!). Once clicked on submit, the request is done!
* Add a small kind comment for Martin, telling him what you're doing.
* Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
* Click submit.

More improvements (mass import, edit, delete) are to come, so [http://www.flightgear.org/forums/viewtopic.php?f=5&t=14671&p=144878 follow the forum thread] if you're interested.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.

It's time to go to Austria and visit [[Innsbruck Airport]]. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
[[File:LOWI december.jpg|600 px]]

Merry X-mas!

== Screenshot of the month ==

== Suggested flights ==
===Ngorngoro===
For this [[VFR]] trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania , what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, [http://en.wikipedia.org/wiki/Lake_Manyara Lake Manyara], runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
[[File:Map Ngorngoro Crater.jpg|thumb|200px|left|Heightmap with visual reference points]]
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.

Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield.
You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.

We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
[[File:Ol Doinyo Lengai.jpg|thumb|250px|Mt.Kerimasi (left), Mt.Ol Doinyo Lengai (ahead)]]
On the '''image''' we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards [http://en.wikipedia.org/wiki/Ol_Doinyo_Lengai Mt.Ol Doinyo Lengai]. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.

The mountain ahead, [http://www.ntz.info/gen/n00161.html#id03702 Mt.Embagai], we see does not appear to be anything spectacular. Aim towards it since we have to go over it.
Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.

After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.

After a small hill we enter one of the most amazing places in Africa, the [http://en.wikipedia.org/wiki/Ngorongoro_Conservation_Area Ngorngoro Crater], the second biggest crater in the world. A micro climate and amazing wildlife.
Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.

After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.

Don't scare the wildebeast!

Notecard:
<tt>
#Fair weather, no snow
#HTLM RW 12 4150 feet
#Course 30 to 0 deg 15 mins, mountains close left
#Head towards /\volcano
#Sharp left turn course 225 deg altitude 9000 feet
#Volcano, lake, 10 000 feet
#Course 225 deg, slow descend 9 min
#Large lake, course 123 deg 5 mins
#River left, road right. Follow road
#Landing 124.5 deg 4150 feet.</tt>

*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on Google+ ===
Following up on last month's launch, the [http://gplus.to/flightgear FlightGear page on Google+] welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.

=== FlightGear on YouTube ===
{{#ev:youtube|VBWZ6JZe_Mw|400|winter video by planetacancun2 showing FlightGear's snow.}}
{{#ev:youtube|LyBUPlf5NSw|400|diamond formation flight by jano}} (Also see [[Toward real close formation flight]])

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2011 12]]

User:Zbyszek

2011-10-26T13:29:50Z

Zbyszek: Created page with "{{User |name = Zbyszek |location = Gostynin, Poland |age = 15 |job = student |interests = Webdesign, computer graphics, simulation |callsign = Zbyszek |favourite = [[Pi..."

{{User
|name = Zbyszek
|location = Gostynin, Poland
|age = 15
|job = student
|interests = Webdesign, computer graphics, simulation
|callsign = Zbyszek
|favourite = [[Piper PA-22 Tri-Pacer]]
|website = [http://flightgear.pl/ FlightGear PL]
}}

FlightGear user since 2008. I've been moderating Polish FlightGear Forum.

'''Scenery projects:'''
*[http://www.forum.flightgear.pl/viewtopic.php?f=10&t=1357&st=0&sk=t&sd=a&sid=ced2eaeb3b2b3fb3c12a5e387dc31f17 VFR Warsaw]
*[http://www.flightgear.org/forums/viewtopic.php?f=5&t=11980 Bornholm Lufthavn (EKRN)]

Airport layouts:
*EPWA
*EKRN
*EPBC
*EPKS
*EPOK

Building for [http://www.forum.flightgear.pl/viewtopic.php?f=10&t=2101&sid=ced2eaeb3b2b3fb3c12a5e387dc31f17 Roztocze Project]

Translation requests

2011-10-25T19:51:12Z

Zbyszek: /* Open translation requests */

Please post your translation requests here, so that other people can more easily track what's going on, hopefully avoiding duplicate efforts.

In general, it is a good idea to check out the wiki statistics before translating a page, so that the most popular and most important pages get translated first: http://wiki.flightgear.org/index.php/Special:PopularPages
*How to translate is described here: [[Help:Translate]].

= Currently work in progress =
*Please see table below.
*Please enter <tt><nowiki>{{BeingTranslated}}</nowiki></tt> on pages that are being translated, remove this when you are finished.
*Also look at [[:Category:Articles being translated]].

= Open translation requests =
Check out http://wiki.flightgear.org/index.php/Special:Statistics for the most viewed pages:

{| cellpadding="10" cellspacing="0" border="1"
|- style="font-style:italic"
|English || Deutsch || Español || Suomi
|| Français || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|- style="font-weight:bold"
|[[Help:Translate]] || '''/H'''[[De/Help:Übersetzen|De/Done]] || '''/H'''[[Es/Help:Traducir|Es/Done]]|| Suomi
||'''/H'''[[Fr/Help:Traduire|Fr/Done]]|| Italiano || [[Nl/Help:Vertalen|Nl/Done]]|| Português || [[Pl/Pomoc:Tłumaczenie|Pl/Done]] || '''/H'''[[Ru/Справка:Перевод|Ru/Done]]|| 中文||'''/H'''[[Sv/Hjälp:Översättning|Sv/Done]]
|-
|[[Main Page]]|| [[De/Hauptseite| De/Done]]|| [[Es/Portada| Es/Done]] || [[Fi/Etusivu| Fi/Done]]
|| [[Fr/Accueil| Fr/Done]] || [[It/Pagina principale| It/Done]]|| [[Nl/Hoofdpagina| Nl/Done]]|| [[Pt/Página principal| Pt/Done]]|| [[Pl/Strona główna| Pl/Done]]|| [[Ru/Заглавная страница| Ru/Done]]|| [[Zh/首页| Zh/Done]]||Svenska
|-
|[[New to FlightGear]]|| '''/H'''[[De/Neu bei FlightGear| De 50%]]|| [[Es/Nuevo en FlightGear| Es/ Done]] || Suomi
||[[Fr/Nouveau sur flightgear| Fr/Done]]|| Italiano || [[Nl/Nieuw bij FlightGear|Nl 50%]] || Português || Polski || Русский || [[Zh/FlightGear新手| Zh 50%]]||Svenska
|-
|[[Aircraft]]|| [[De/Flugzeuge| De/Done]]|| [[Es/Aeronaves|Es/Done]]|| Suomi
||[[Fr/Avions| Fr/Done]]|| Italiano || Nederlands || [[Pt/Avião|Pt/Done]]|| Polski || Русский || 中文||Svenska
|-
|[[Frequently asked questions]]|| '''/H'''[[De/FAQ| De 50%]]|| [[Es/Preguntas frecuentes| Es/Done]]|| Suomi
||[[Fr/Foire aux questions| Fr/Done]]|| Italiano || Nederlands || Português || [[Pl/FAQ| Pl/Done]] || Русский || 中文||Svenska
|-
|[[Portal:User]]|| [[De/Portal:Benutzer|De/Done]]|| [[Es/Portal:Usuario| Es/Done]] || Suomi
||[[Fr/Portal:Utilisateur|Fr/Done]]|| Italiano || Nederlands || Português || [[Pl/Portal:Dla użytkowników|Pl 50%]]|| Русский || [[Zh/Portal:用户|Zh/Done]]||Svenska
|-
|[[Howto: Multiplayer]]|| [[De/Howto: Multiplayer| De/Done]] || [[Es/Howto: Multijugador| Es/Done]]|| Suomi
||[[Fr/Howto: Multijoueur|Fr/Done]]|| Italiano || [[Nl/Howto: Multiplayer|Nl/Done]]|| Português || [[Pl/Konfiguracja trybu multiplayer|Pl/Done]]|| Русский || 中文||Svenska
|-
|[[Howto: Install scenery]]|| Deutsch || Español || Suomi
||Français || Italiano || Nederlands || [[Pt/Instalando Cenário|Pt/Done]]|| [[PL/Instalowanie scenerii|Pl 50%]]|| Русский || 中文||Svenska
|-
|[[Flying the helicopter]]|| [[De/Fliegen mit dem Helikopter|De/Done]]|| [[Es/Volando el helicoptero|Es/Done]]|| Suomi ||[[Fr/Piloter l'hélicoptère|Fr/Done]]|| Italiano || [[Nl/Vliegen met de helicopter|Nl/Done]]|| Português || [[Pl/Lot śmigłowcem|Pl/Done]]|| Русский || 中文||Svenska
|-
|[[Troubleshooting problems]]|| Deutsch || Español || Suomi
||Français || Italiano || Nederlands || Português || Polski || Русский || 中文||Svenska
|-
|[[Altitude]] || '''/H'''[[De/Flughöhe| De 50%]]|| Español || Suomi
||Français || Italiano || Nederlands || Português || Polski || Русский || 中文||Svenska
|-
| [[FlightGear hangars]]|| Deutsch || Español || Suomi
|| Français || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|-
| [[FlightGear Launch Control]]|| [[De/FlightGear Launch Control|De/Done]]|| Español || Suomi
|| Français || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|-
| [[FlightGear]]|| [[De/FlightGear|De/Done]]|| [[Es/FlightGear|Es/Done]]|| Suomi
|| Français || Italiano || [[Nl/FlightGear|Nl/Done]]|| [[Pt/FlightGear|Pt/Done]]|| Polski || Русский || 中文|| Svenska
|-
| new article|| Deutsch || Español || Suomi
|| Français || Italiano || Nederlands || Português || Polski || Русский || 中文|| Svenska
|}

*Pages that are not linked from the English page are not listed. (that is no guarantee there is no (partial) translation)
*Pages that say 50% are in the process of being translated but feel free to help out (since some authors have gone MIA).
*Items in the table that have no link need your assistance.
*Items or lines in the table that are marked with '''/H''' request your help.
*Help and keep this page up-to-date please (so to avoid double work).

[[Category:Contribution requests]]

Pl/Pomoc:Tłumaczenie

2011-10-25T19:48:24Z

Zbyszek: Created page with "Od września 2009 roku FlightGear Wiki obsługuje wiele języków. Od teraz każdy artykuł może być przetłumacznony na jakikolwiek inny język, zwiększając ł..."

Od września 2009 roku [[Main Page|FlightGear Wiki]] obsługuje wiele języków. Od teraz każdy artykuł może być przetłumacznony na jakikolwiek inny język, zwiększając łatwość obsługi przez osoby nieznające angielskiego.

===Potrzebujemy CIĘ!===
Mamy {{NUMBEROFARTICLES}} artykułów (niektóre krótsze od innych) - naprawdę dużo pracy trzeba poświęcić, aby przetłumaczyć wszystkie. Część użytkowników już rozpoczęła tłumaczenie, ale zdecydowanie potrzebujemy pomocy, aby być precyzyjnym: Twojej pomocy. Niemal wszyscy tutaj posługują się więcej niż jednym językiem, więc nie byłbym zdziwiony, gdyby dla większości angielski nie był językiem ojczystym.

Jeżeli my wszyscy przetłumaczymy choćby jedną lub dwie strony, przetłumaczenie najbardziej istotnych artykułów (jak [[Flying the helicopter]], [[FlightGear]], [[Installing Scenery]] i [[New to FlightGear]]) nie zajmie *tak dużo* czasu.

Zerknij na [[Translation requests]], aby zobaczyć najbardziej pożądane artykuły.

===Przykłady===
Aby zobaczyć przykłady stron obecnie przetłumaczonym, spójrz na stronę główną [[Pl/Strona_główna]].

===Jak mam zacząć tłumaczyć===
====Poradnik====
Najpierw musisz znaleźć artykuł, który chciałbyś przetłumaczyć. Potem wpisz w wyszukiwarce atrybut języka (dla polskiego jest to "Pl"), następnie ukośnik i nazwa strony, którą chcesz utworzyć. Dla przykładu: gdybym chciał stworzyć stronę Samoloty wpisuje w wyszukiwarce "Pl/Samoloty". Jak widzisz ta strona nie istnieje. Teraz wystarczy kliknąć "Create page".

Na końcu artykułu musisz dodać odnośniki do strony w innych językach. Dla języka angielskiego będzie to wyglądało tak: <tt><nowiki>[[:en:Aircraft|Aircraft]]</nowiki></tt>. Pamiętaj, aby na stronach obcojęzycznych dodać przekierowanie do artykułu, który stworzyłeś.

====Krok po kroku====
#Znajdź angielską wersję artykułu, który chcesz przetłumaczyć.
#Sprawdź czy zgadzasz się z zawartością angielskiej strony. Jeżeli jest nieaktualna zmień ją (nie ma powodu, aby strona przetłumaczona nie mogła być lepsza od orginału, ale dla synchronizacji, lepiej aby najpierw angielska strona została uaktualniona).
#Spójrz na lewy dolny róg strony, jeżeli strona została już przetłumaczona na inne języki będzie tam lista tych języków '''In other languages'''.
#Jeżeli twój język nie jest zamieszczony na liście, możesz zacząć tłumaczyć (jeśli jest zobacz, co możesz poprawić).
#Znajdź atrybut twojego języka ze strony ( [http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3/languages/Names.php this].
#Edytuj angielską wersje strony.
#Umieść odnośniki do twojego języka na dole strony np. <tt><nowiki>[[:pl:Samoloty|Samoloty]]</nowiki></tt>)
#Zapisz angielską stronę i sprawdź czy twój wpis się pojawił.
#Naciśnij link (wpis), aby edytować twoją stronę
#Dodaj <tt><nowiki>{{BeingTranslated}}~~~~</nowiki></tt>
#Dodaj na dole twojej strony <tt><nowiki>[[En:Page Title]]</nowiki></tt> gdzie Page Title oznacza nazwę oryginalnej strony.
#Jeżeli strona została już przetłumaczona na inne języki skopiuj ich listę z angielskiej wersji.
#Zapisz swoją stronę.
#Sprawdź czy linki do stron działają.
#Poinformuj o swoim tłumaczeniu na stronie: [[Translation requests]]
#Zacznij tłumaczyć.
#Obserwuj angielską stronę i uaktualnij swoją stronę, gdy zobaczysz interesujące wpisy.

==='''Jakie artykuły nie powinny zostać przetłumaczone?'''===
<u>'''Nie '''</u> zaczynaj tłumaczyć artykułów, które są '''[[:Category:afd|considered for deletion]]''' lub '''[[:Category:Articles to be merged|need merging]]'''.

'''Dzięki za wiele tłumaczeń i wkład w tworzenie wiki! Twoja ciężka praca jest naprawdę doceniana przez wszystkich użytkowników FG!'''

[[Category:Help|Translate]]

[[de:Help:Übersetzen]]
[[es:Help:Traducir]]
[[nl:Help:Vertalen]]
[[fr:Help:Traduire]]
[[ru:Справка:Перевод]]
[[sv:Hjälp:Översättning]]

Howto:Install scenery

2011-10-25T18:54:12Z

Zbyszek:

{{installing}}
FlightGear comes with a limited set of [[scenery]]. Apart from the Bay Area around San Francisco (including the default airport [[KSFO]]), additional scenery can be installed by the user. If you locate yourself at an airport and see nothing but water, you probably did not install that scenery area (correctly).

== Obtaining scenery ==
You can download the official [[World Scenery]] terrain from the [http://www.flightgear.org/Downloads/scenery FlightGear website]. Alternatively, custom scenery is available for certain specific areas. They are distributed separately due to their license, or because their level of detail is not suitable for low-end machines. See [[Suggested Airports/Scenery]] for a list of custom scenery projects.

There is also a 4 DVD set available for download via [http://www.torrentbox.com/download/59050/FlightGear_4_DVD_Disk-set.torrent BitTorrent], which can be a higher performance option for those wanting to download the entire world. And, last but not least, it can be purchased as 3 DVD set from the [http://www.flightgear.org/dvd/ official FlightGear website].

=== TerraSync ===
[[TerraSync]] is a very useful utility that automatically downloads and installs needed FlightGear scenery and keeps it up to date while the simulator is running.

=== Downloading from mirrors ===
A list of mirrors can be found [http://www.flightgear.org/mirrors.html#ftp here].

On most of the mirrors, the latest scenery can be found under <tt>Scenery-2.0.0/</tt>. Downloading from mirrors is often better than the official site, because mirrors are sometimes faster and have more user capacity. Use the [http://www.flightgear.org/Downloads/scenery graphical interface] to find the appropriate chunk. Be careful about confusing N with S, and E with W!!
Here is how to find an airport's co-ordinates:

# Go to the Wikipedia page for the airport in question (for example, PHNL for Honolulu)
# Find the co-ordinates (often at the top or right and side, marked with a small globe)
#* e.g. PHNL is in 21 N 157 W. If it's in the western hemisphere, you should round it up... so you should find the block with W160N20 If the co-ords were 21 N 157 E, you would round it '''down'''.. meaning that this location would be E150N20.

== Installing scenery ==
You can optionally use a GUI installer, called [[FlightGear Admin Wizard|FGAdmin]], to (un)install scenery.

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

cd [[$FG_ROOT]]/Scenery
tar -xvzf input_file.tgz

or

tar -xvzf 'input_file.tgz' -C [[$FG_ROOT]]/Scenery

In the above two examples it is supposed that the variable [[$FG ROOT]] is set to the root of the data directory. If this is not set, you should substitute in the above examples the $FG_ROOT with the full pathname of this directory. In the above examples 'input_file.tgz' should be substituted with the filename of the archive to be extracted (the filename should be completed with the full pathname or any other valid method so that the shell could find the correct archive).

=== Windows ===
Simply unpack the downloaded scenery into your <tt>[[$FG ROOT]]/Scenery</tt> directory, using software like [http://www.winzip.com/ Winzip] or [http://www.7-zip.org 7-zip]. Do not forget to press the "Refresh" (German: "Neu Laden") button on the airport selection page, when using the [[FlightGear Wizard]].<br />
'''!!! IMPORTANT !!!'''<br />
"Modern" Windows Versions (e.g. XP, Vista, Win7) tinkering a lot with user rights on access level. Therefore it's a bad idea to install and run FlightGear to and from "C:\Program Files" (German: C:\Programme). Find another drive / folder where you as logged in user have all neccesary right to read, write and execute the files you installed. Additionally there's a space / blank in folder's name which could cause weird behaviour. Use something like "C:\FlightGear".

== Technical ==
Scenery for FlightGear is determined by looking at the environment variable [[$FG SCENERY]]. Should the paths in $FG_SCENERY not be valid, FlightGear falls back to <tt>[[$FG ROOT]]/Scenery</tt>.

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

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

Then you should set up $FG_SCENERY to use the new path:
* On POSIX Clients<br />set FG_SCENERY="$FOOBAR/Scenery" + FG_SCENERY
* On Windows (FGRun)<br />Go back to the first page of fgrun, and add the <tt>$FOOBAR/Scenery</tt> folder to the list.

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

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

If you download a scenery module called w90n40.tgz from [http://flightgear.org/Downloads/scenery-1.0.1.html flightgear.org] and extract it in Scenery, the result will resemble something like the following:

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

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

=== Objects ===
Objects and models can be found at the [http://scenemodels.flightgear.org/ FlightGear Scenery Objects Database].

These objects are included in each scenery release, but as the object database is more frequently updated than the terrain, one may want to occasionally update the Object subdirectory from the FlightGear Scenery Objects Database between scenery releases.
Another option is to download or update the scenery on-demand by using the terrasync program described below.

Objects are really part of the scenery and can be found in the Scenery directory under [[$FG ROOT]].

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

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

=== Models ===
Replaces the former <tt>[[$FG_ROOT]]/Models</tt>; stores all the shader objects.

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

=== Airports ===
<s>Currently FlightGear does not use</s> this directory<s>. However, in upcoming releases, it will be</s> is being used to extract airport data (like runway usage and parking spots) from.

: See also: [[Howto: Animated jetways#Usage]]

The directory tree might look somewhat overwhelming, it simply follows the <tt>Airports/[I]/[C]/[A]/</tt> code (see [[ICAO-code]]).

<tt>
* Scenery/
** Airports/
*** K/
**** S/
***** F/
</tt>

== Related content ==
* [[FlightGear Admin Wizard|FGAdmin]]
* [[Installing Aircraft]]
* [[Scenery FAQ]]

[[pt:Instalando Cenário]]
[[PL:Instalowanie scenerii]]
[[Category:Scenery]]

FlightGear Newsletter October 2011

2011-10-25T18:32:58Z

Zbyszek: /* Call for volunteers */

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== FGdata split ===
A team of developers started preparing the FlightGear [[git]] repositories for a significant change. Aircraft will be split of from fgdata, in order to ease development of aircraft and data as a whole. At the moment (of publication of this newsletter) we're in the testing phase; inviting anyone to test out the new system and report any bugs, comments and questions.

We would like to emphasize that those testing repositories are not meant to replace the "old" fgdata yet!

Details can be found on the special wiki page: [[FlightGear Git: splitting fgdata]].

=== Move to CMake ===



=== New Replay System ===
The [[Instant Replay]] system has received a major overhaul. The existing system worked well with specific types of aircraft only, since it relied on a hard-coded set of properties to be recorded/replayed, mainly covering propeller aircraft. Jet engines (thrust-reversers, N1/N2 rpm), or non-standard gears (i.e. a Concorde with 4 landing gears) were not working well though. The new system can be adapted to any kind of aircraft and any kind of custom property or animation.

[[File:FG-instant-replay-new.png|thumb|500px|The new instant replay dialog.]]

Most obvious change is probably an improved replay dialog: the video player-like GUI provides play/pause/skip buttons and also controls replay speed. During replay use the 4 arrow keys as controls (left/right to skip, up/down to speed-up/slow-down). Also new: ''slow-motion playback'' is now supported!

Another new feature is the option of taking controls at any point during replay. Use the ''Instant Replay'' to go back in time, then hit the "My controls!" button to regain controls and continue the flight from the current position. You may find this to be useful to train particular flight phases, such as flying the same approach again and again, maybe using different weather/wind conditions. Even if you messed up an approach: go back, try again, until you're getting better! :) Currently this particular feature is only available for YASim aircraft - except helicopters. JSBSim support is likely to be available soon.

The first step to adapt an aircraft to the improved recording system is to pick one of the ready-to-use configuration files, depending on aircraft/engine/.. type. The configuration file only needs to be included in the aircraft's ...-set.xml file. As an optional second step, you can add more custom properties to cover aircraft-specific effects. For more details, see the [https://www.gitorious.org/fg/fgdata/blobs/master/Docs/README.flightrecorder README.flightrecorder] in the fgdata/Docs folder.

A few adapted aircraft examples showing different levels of customization are already present in current git/fgdata:
* ASK13 (glider)
* c172p (propeller/piston)
* b1900d (turboprop)
* UH-1 (helicopter)
* 777-200ER (jet).

Furthermore, the replay system's buffers are now fully configurable (see /sim/replay/buffer properties). If you have enough memory, you could increase the buffer recording durations and rates.

Work on the replay system isn't finished yet. However, have a test flight with the current state in current git ;-).

=== The bombable addon has been updated ===
[[File:bombable4_4_800.png]]

Flug's [[Bombable]] addon received a number of major updates, among them:

* '''AI aircraft move vertically -- and do loops''': AI aircraft now move much more realistically in the vertical direction. They do loops, dive, and all the rest. Their behavior (climb rates, dive rates, and so on) matches those of the corresponding FG aircraft. This makes for a much more realistic 3-D dogfighting experience in FlightGear.
* '''Realistic roll rates for AI aircraft''': Roll rates are one the most important factors determining the effectiveness of fighter aircraft-- aircraft that can roll faster can turn faster. Now the roll rate for AI aircraft in scenarios can be customized, and bugs in the roll & turn routines for AI aircraft have been fixed.
* '''Significant performance improvements''': Bombable now makes much less of an impact on your framerate, and much less stuttering & slowdown at key points, like when numerous machine gun rounds are impacting.
* '''Damage impact detection is the most advanced element in Bombable'''. It is greatly improved over FG's native impact detection system, and the framework is in place for further refinements or as a model for FG to implement more refined impact detection internally. Damage tracking and communication over Multiplayer works well in a very lightweight with a very low data rate. However, only a general damage percentage is tracked and communicated. Damage to different locations or systems is not simulated. Proof of concept for explosions, fires, weapons damage animations, and crash animations is in place. All these elements could be refined for greater realism.
* '''Relocate any scenario to your location''': Have an AI scenario based in San Francisco, but want to fly in London? No problem, just hit a button in the Bombable menu and your scenario comes to you, wherever you are. Damage levels for AI aircraft and objects are re-set. It's like loading a new scenario without having to re-start FlightGear.
* '''Re-spawn AI aircraft and objects''': After you have shot down (or been shot down by!) AI aircraft or objects in scenarios, you can instantly re-spawn them and try again. (Available in the Bombable menu.)

The last two are kind of game changers--it's like being able to re-start/re-load a scenario instantly without having to re-start FG.

In addition, there have been some feature requests to make the bombable addon more challenging by improving its AI. This spawned an interesting discussion about possible ways to make the AI even smarter than it is already [http://flightgear.org/forums/viewtopic.php?f=6&t=5742&start=300#p140013]. Also see [[Howto: Neural networks in Nasal]].

For a nice video demo created by Vodoun da Vinci, please see [[FlightGear Newsletter October 2011#Community news|community news]].

== Interview with a contributor: Gijs de Rooy ==
From this month onwards, we'd like to see a monthly interview with a contributor. Questions are available on [[interview questions]] and anyone is free to write an interview (with him-/herself) for next month's newsletter!

* '''How long have you been involved in FlightGear? What was it that made you join?'''
According to the forum software I joined all the way back in July 2007. One year earlier I was one of the first users of Google SketchUp, free 3D modelling software. After modelling several buildings in my home town, Amsterdam (and placing them in Google Earth) I started working on Amsterdam Airport Schiphol. By then, Google Earth had a (simple) built-in flight simulator. Amsterdam would be the first airport to be modelled especially for that, that was my plan at least...

While modelling Schiphol, I stumbled across this free flight sim, called FlightGear, that wasn't a game, unlike Google's. In [http://flightgear.org/forums/viewtopic.php?f=5&t=473 one of my first posts] on the FlightGear forum I asked for someone to place my models into FlightGear's scenery. Georg (Heliflyer) placed my first buildings. I took some effort, but I finally managed to place buildings myself. Sadly the guy that introduced me to FlightGear and gave me a hobby that would last up till today, passed away in 2009.

* '''What are your major interests in FlightGear?'''
One of the things I like about FlightGear is the wide range of things one can get involved with: modelling, texturing, writing manuals, collecting data etc. and of course flying itself. Therefore I have a very long list of interests. However, there are three key parts that I particularly enjoy. Being the development of scenery and aircraft and helping others by writing wiki articles and replying to questions at the forum.

* '''What project(s) are you working on right now?'''
My main development projects right now are the Boeing 747-400 and Dutch scenery.

* '''What do you plan on doing in the future?'''
I'd really like to bring the 744 to a state where a real pilot cannot spot a thing that is missing in the simulation.

* '''What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?'''
Starting something new is easy, completing it is much harder. I could have never guessed I would still be working on the 744, three years after I started!

I've always been telling newcomers to start improving existing features. It's a great way to familiarize yourself with the project. By looking into existing aircraft's files for example, you will quickly find out how those files are linked together and what their purpose is.

* '''Do you have real world connections with aviation or IT?'''
Since two months I'm studying Aerospace Engineering at the University of Delft. So far I really like this mix of hobby and study.

== Snapshot releases ==

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.
=== New aircraft ===

=== Updated aircraft ===
The [[Learjet 35-A]] has been updated. Several minor errors have been fixed and improvements have been put in-place. The [[Learjet 35-A]] is the only business jet with a functional autopilot. It is a gem to fly and perfect for beginners and experts to try [[radio navigation]], autopilot control and [[ILS]] procedures. Thanks Xsaint and PH-JBO for the work done.

=== Livery database reaches 600 ===
On October 8, the [[FlightGear livery database]] welcomed its 600th livery! Thanks to 70 authors, the virtual skies are more colourful than ever.

At the moment the contribution system is being rewritten. For the time being, new liveries are only accepted via direct email to [http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=510 Gijs].

== Scenery corner ==

=== Support for 8.50 airport data ===
[[File:EHAM_overview_night.png|thumb|270px|[[Amsterdam Airport Schiphol]] by night, with the new 8.50 lighting.]]
[[File:EHAM_gate_D.png|thumb|270px|Schiphol's D gates, in combination with AI traffic.]]
As mentioned in the previous newsletter; efforts are made to bring [[TerraGear]] up to a level where it supports the 8.50 apt.dat format, nowadays used by X-Plane. This new format has all kind of exciting features, including (but not limited to) curved taxiways and accurate lining/lighting (not just "ordinary" taxiway lines, but also markings like hold lines).

We'd like to thank Christian (papillon81), Peter (Psadro GM) and Emmilian (i4dnf) for their hard work. It's probably legitimate to say that this is the biggest improvements in FlightGear scenery over the past years!

=== Airports ===

== Aircraft of the month ==

Diamond DA42 Twin Star

[[File:Fgfs-screen-032.png|600px]]

http://en.wikipedia.org/wiki/Diamond_DA42

== Glider of the month ==

Jean Astir Grob G102

[[File:Astir.png|600px]]
[[File:Fgfs-screen-026.png|600px]]

== Airport of the month ==
[[File:FJDG.jpg|600px]]

The nearest airport is about 700 NM away. Around us are about 30 small islands, none with [[radio beacons]], none with an airport but some with a small beach. This Airport has four odd looking pillboxes. If you click they will open, very slowly. Now if you would have a [[Northrop B-2 Spirit |B2 bomber]] you could park your aircraft in it. If you don't have a [[Northrop B-2 Spirit|B2]] you are allowed to land, but only in an emergency. Fake an emergency and get here, bring piña colada and have a party on the beach!

*It is sooo beautiful here. Oh, where? FJDG, [http://en.wikipedia.org/wiki/Chagos_Archipelago Diego Garcia at Point Marianne]. Perfect for [[VFR]] tours, and a piña colada on the beach.

== Screenshot of the month ==
[[File:Mount Everest VNTR.jpg]]
*[[Learjet 35-A]] and [http://en.wikipedia.org/wiki/Mount_Everest Mount Everest] viewed from West towards East. Atlas image of the route to [http://en.wikipedia.org/wiki/Tumlingtar_Airport VNTR]. I could see the direction of NDB and knew the altitude of the RW. The RW was not visible till the absolute last moment racing down with airbrakes at max. The landing was a success but I had to change underwear and clean the seat.

== Suggested flights ==
It's cold where we will go so dress up warm and if we are lucky we might see whales during our flight. Don't fly too high to enjoy the amazing views, and there is a small challenge at the end. The runways we will use are long enough for bigger aircraft (7000+). Total length of the trip will be around 245 NM. So, hop in the cockpit of your favourite airliner.

Alaska, here we come! Enjoy!
#Park your aircraft on PAKT, [http://www.borough.ketchikan.ak.us/airport/airport_history.htm Ketchikan International], runway 11. The wind is coming from '''South''', change the weather if needed (SE is ok too).
#Fly North towards [[NDB]] Fredericks Point on 372.0 for 94 NM.
#Fly towards [[NDB]] Five Fingers on 295.0 for 39 NM.
#Fly towards [[NDB]] Gustavus on 219.0 for 77 NM.
#Fly towards [[NDB]] Coghlan Island on 212.0 for 32 NM.
#Set the [[ILS]] on 109.9 and land your aircraft (after 4 NM) on PAJN, [http://www.juneau.org/airport/ Juneau International], runway 08.
If you feel warm after this landing, you just crossed a NORAD microwave site, so that is why.
*More amazing flights can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==

[[User:Flug|Flug]] and [[User:Hooray|Hooray]] revamped the [[Nasal]] documentation, to make it hopefully more comprehensive and more accessible to new programmers. If you think, anything is unclear or missing, please leave a remark at the article's talk page, or just use the forum.

===New articles===
*The article about [[altitude]] has received an update and a fresh lick of paint. Please help to correct the German version.
*[[Aircraft speed]] is a bit more up-to speed now.
*Places to fly, Suggested Flights, Suggested Flights from newsletters and the flights from the main website have all been merged into one gathering place of amazing places you really have to visit one day, soon. Check out [[Suggested Flights]].
**Great a bigga thank you Brisa for your work so far and hope you find time soon to continue!

===New aircraft articles===
===Most popular newsletters===

== Community news ==
===Reminder: FSweekend===
A team of FlightGear developers will promote FlightGear to the public at the [[FSweekend]] (5 and 6 November 2011), the largest flight simulator event in the world. They highly appreciate it if you are able to stop by. If you are unable to visit [[Lelystad Airport]] (EHLE) in real life, make sure you pay a virtual visit!

A visit is definitely worth it. The more knowing that Durk Talsma, one of our longtime core developers, will do a one hour presentation on FlightGear.

[[File:Fgfs-screen-028.png|x125px]][[File:FSweekend_banner_2011.jpg|x125px|link=http://www.fsweekend.com]]

More information can be found at the event's wiki page: [[FSweekend 2011]].

=== FlightGear on YouTube ===
Vodoun da Vinci has [http://flightgear.org/forums/viewtopic.php?f=19&t=13823 uploaded a new movie] complete with music soundtrack to demonstrate the latest [[Bombable]] addon. This one primarily features head on attacks by custom [[P-51D Mustang]]s over Sochi, Russia.

The code in the Mustangs has been hacked to make them aggressive in attacking head on. My favorite style with my FW-190 D9 Dora supplied by Detlef Faber. The clips have been recorded with time set to evening and morning (dusk and dawn) as this provides the kind of dark and contrasting sky that best suits me for hunting.

=== FlightGear on Facebook ===
Started in December 2010, [http://www.facebook.com/FlightGear the FlightGear Facebook page] welcomed its 6000th "liker" on October 7! The original plan was to outnumber the likers of [[Pro Flight Simulator]] and the like, but now that we've outnumbered them by far, the Facebook page can be seen as a way to provide a periodic dose of what's new, cool or fun in FlightGear. Over the past months, we've been frequently posting nice screenshots from forummembers.

Speaking of which, [http://flightgear.org/forums the forum] is still the place to be when you're looking for support.

=== New tutorials and screencasts ===
[http://icestar-fghangar.web44.net/web/ Icecode's and Star's hangar] which was created on February 2011, is now bringing a new [http://icestar-fghangar.web44.net/web/?q=node/51 Tutorials section] where a new tutorial will be uploaded each week (sometimes more often). Starting with this week's tutorial "[http://icestar-fghangar.web44.net/web/?q=node/54 VOR navigation]". The tutorials are not going to be only limited on how to fly aircrafts but also we'll be showing you tips on how to develop aircrafts, scenery, liveries and many other things. Have fun reading and enjoy your flights!

=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== FlightGear in the news==
FlightGear was featured in the October edition of [http://microsim.over-blog.com/ MicroSim], a French flight simulation magazine. The two paged article (click images below to open larger versions) discussed our latest release 2.4.0. Altough MSFS and X-Plane have better graphics and more complete aircraft, the writer considers FlightGear a worthwhile alternative.

The next edition of MicroSim will include a tutorial, to guide new users through the program.

[[File:MicroSim_oct2011_1.png|300px]]
[[File:MicroSim_oct2011_2.png|286px]]

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
*[[Translation requests| To '''translate''' (wiki) we must '''translate translate'''!]] so, Help and translate [[Translation requests| translate]] Wenn Sie Aus Deutschland sind or Jeśli jesteś z Polski, and from anywhere!
**Special thanks to Alexmdv and Michat for their translation work! (And Hamster and so many others)

* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===
...that you can comment on the newsletter in the [http://www.flightgear.org/forums/viewforum.php?f=50 forums]? Help us improve *your* newsletter! Give comments, suggestions and feedback!

[[Category:FlightGear Newsletter]]

Pl/Szybownictwo

2011-08-14T18:08:35Z

Zbyszek: /* Skręcanie */

Latanie szybowcami w FlightGear może okazać się nieco trudniejsze niż samolotami silnikowymi, ale ostatecznie sprawia wiele radości. Osiągnięcie perfekcji w lataniu szybowcem wymaga nauki pilotażu, zrozumienia konstrukcji maszyny oraz podstaw areodynamiki. Zniechęcanie się po paru nieudanych próbach jest bezzasadne, praktyka czyni mistrza.

=== Podstawy ===
[[File:Soar pulawy.jpg|200px|thumb|right|Szybowiec Ask-13 nad Puławami]]

Do pilotażu będzie nam służył drążek steru oraz pedały. Wychylenie drążka steru od siebie nazywane jest “oddawaniem drążka” i powoduje wychylenie sterów wysokości w dół. “Ściągnięcie” drążka to ruch do siebie powodujący wychylenie sterów wysokości w górę.
Wychylenie lotki w lewo zachodzi przez wychylenie drążka w lewo, analogicznie w prawo.

Ściągnięcie drążka powoduje wzniesienie się, przy jednoczesnym zmniejszeniu prędkości lotu. Tak, więc przy nieruchomym powietrzu lepiej skierować dziób szybowca nieco w dół, co w rezultacie umożliwi pokonanie znacznie większej odległości przy jednoczesnej małej stracie wysokości. Zwiększenie prędkości uzyskujemy kierując drążek w od siebie, przez co zwiększamy kąt natarcia. Manewr kończymy łagodnie ściągając drążek steru, gdy na prędkościomierzu zobaczymy żądanej wartości.

=== Nawigacja VFR ===

W przeciwieństwie do większości samolotów silnikowych, w szybowcach posługujemy się wyłącznie nawigacją VFR. Polega to głównie na obserwacji terenu i wyszukiwaniu charakterystycznych obiektów, które mogą nam służyć za punkty nawigacyjne. Wykorzystuje się też mapy, które mogą być przydatne nawet w symulatorze.
Przy sytuacji utraty orientacji należy wznieść się oraz obserwować teren w poszukiwaniu większych dróg, linii kolejowych, miast oraz innych obiektów.

=== Scenerie ===

Ważnym elementem podczas lotu szybowcem w symulatorze jest - posiadanie dopracowanych scenerii. W FlightGear znajdziemy kilka takich, które świetnie nadają się na loty szybowcem.
Zacznijmy od Polski, Ci którzy uwielbiają loty w kraju nad Wisłą, z pewnością zadowolą się scenerią wschodniej części naszej ojczyzny. Najwięcej obiektów VFR znajdziemy w okolicach Lublina, Puław, Dęblina oraz Radomia. Zapewnia to doskonałe warunki nawet do dalszych lotów.
Należy jednak dodać, że punktem odniesienia nie musi być budynek. Równie dobrze może nam za niego służyć las lub rzeka.
Innym ciekawym miejscem są Hawaje, dostępne dzięki TerraSync<ref>[[Pl/Konfiguracja TerraSync]]</ref>. Wspaniałe ukształtowanie terenu sprawia, że odczucia płynące z lotu są jeszcze większe.
Następna propozycja to Francja. Custom France Scenery oferuje olbrzymi obszar dopracowanej scenerii. Przyjemne trasy można znaleźć na południowym wybrzeżu.

=== Start ===

Do startu szybowcem możemy użyć wyciągarki lub samolotu holowniczego. W Ask-13 podpinamy się do wyciągarki klikając <tt>Ctrl + w</tt>, włączamy ją przytrzymując <tt>w</tt> i odpinamy się <tt>Shift+w</tt>. Ostatnia faza może sprawić kłopot; pod koniec należy wyrównać lot i być przygotowanym na nagły spadek noszenia.
W szybowcu DG-101G dostępny jest robot holujący, który aktywujemy klikając <tt>Shift+d</tt>, zaczynamy holowanie klikając <tt>d</tt>.
Zobacz również: [[Pl/Holowanie przez MP]]
[[File:Fgfs-screen-007.png|200px|thumb|right|Wznoszenie ok. 1m/s]]
=== Wznoszenie ===

Do wznoszenia potrzebne są nam kominy termiczne, czyli pionowe prądy powietrza. Oznaką ich występowania są chmury typu Cumulus. Local weather system (system pogodowy wbudowany od wersji 2.4.0) umożliwia nam stworzenie świetnych warunków do szybowania. Wchodzimy w menu > Environment > Local Weather. Poniżej “Select initial scenario file” wybieramy High-pressure. Wind mode: constant, tile selection mode: realistic Weather.
Zaznaczamy również Generate thermals. Pasek na dole powoduje zmianę częstotliwości i siły kominów termicznych. Im bliżej “Rough day” tym kominów jest mniej, ale za to mocniejszych. “Low convention” powoduje utworzenie wielu słabych kominów. Ustawienia możesz dowolnie modyfikować, czuj się wolny jezeli chcesz poeksperymentować. Ja przesunę pasek blizej rough day, ale nie do końca.
Klikamy Ok. Pogoda powinna się wygenerować w ciągu 10 sekund. Tą fazę najlepiej zrobić jeszcze na ziemi.
Po starcie zaczynamy szukać najbliższej chmury, podlatujemy do niej uważając aby opadanie nie przekraczało 1m/s. Gdy będziemy już się zbliżali do chmury możemy doświadczyć mocnych turbulencji wynikających ze zderzenia się prądów powietrza poruszających się w przeciwnym kierunku. Zerkamy na wariometr, czyli przyrząd służący do wyznaczania prędkości pionowej samolotu, innymi słowami prędkości wznoszenia i opadania. Jeżeli wskazówka wychyli się znacznie do góry możemy zaczynać zakręcanie.

=== Skręcanie ===
[[File:Fgfs-screen-004.png|200px|thumb|right|Prawidłowo skoordynowany zakręt. Kulka chyłomierza pozostaje w pozycji centralnej]]
Aby prawidłowo skręcić należy posłużyć się chyłomierzem. Zasada działania tego urządzenia jest bardzo podobna do zasady działania poziomnicy. Gdy kulka jest w centrum - zakręt wykonany jest prawidłowo. Podczas skrętu należy pomagać sobie pedałami, korygując kierunek lotu. Należy powstrzymać się od nadmiernego przechyłu, który może doprowadzić do utraty nośności. Nie każdy szybowiec jest stworzony do akrobacji, choć dla niektórych pętla nie stanowi problemu.

=== Literatura dodatkowa ===
----
[http://lewczuk.com.pl/materialy/sz_zas_pil_sz_pazio.pdf Zasady Pilotażu Szybowcowego, Andrzej Pazio] <br>[http://www.plar.pl/szyb/aermech/aermech.htm Areodynamika i mechanika lotu]

=== Przypisy ===
----
<references/>

Pl/Holowanie przez MP

2011-08-13T22:57:42Z

Zbyszek:

Z [[FlightGear]] 1.0 oraz późniejszymi wersjami możesz ćwiczyć holowanie przez internet używając [[Pl/Konfiguracja trybu multiplayer|Multiplayer'a]]. Obecnie jest tylko kilka samolotów i szybowców umożliwiających takie holowanie. Te dostępne to:

'''Samoloty'''
* [[De Havilland Canada DHC-2 Beaver|Beaver]] (dhc2W)
* [[Rallye-MS893E]] (rallye-MS893 )
* [[Piper J3 Cub|J3]] (j3cub)

'''Szybowce'''
* [[ASK-13 sailplane|ASK13]]
* [[Schleicher ASK 21 Glider|ASK21]]
* [[SZD-9bis Bocian-1E|Bocian]]
* [[Glaser-Dirks DG-300|DG-300]]
* [[Glaser-Dirks_DG-101G|DG-101G]]

W następującym przykładzie używamy Beaver'a oraz Ask 13. Cub po prostu nie jest w stanie pociągnąć niemiecki szybowiec. ;)

[[File:Aerootowing ask13.png |400px ]]

Kołuj Beaver'em na odległość mniejszą niż 60 metrów od Ask-13. Pilot szybowca musi kliknąć <tt>Ctrl-o</tt>. Obaj piloci powinni widzieć wiadomość radiową, mówiącą że są ze sobą połączeni, następnie pilot Cub'a może zacząć ciągnąć szybowiec. Można obserwować odległość pomiędzy maszynami w property browser; <tt>/sim/hitches/aerotow/tow/dist</tt> and <tt>/sim/hitches/aerotow/tow/dist-time-lag-corrected</tt> Bądź ostrożny, gdy odległość zbliży się do 60m, maksymalnej długości liny holowniczej. Piloci powinni spróbować wystartować gładko. Od liny można się odpiąć klikając "O" (<tt>Shift-o</tt>).

[[File:Aerotowing ask13 2.png |400px ]]

Jeżeli nie korzysta się z sieci lokalnej, obaj piloci powinni być na tym samym serwerze, co ograniczy opóźnienie czasowe.

File:Aerotowing ask13 2.png

2011-08-13T22:54:48Z

Zbyszek:

File:Aerootowing ask13.png

2011-08-13T22:51:02Z

Zbyszek:

Pl/Portal:Dla użytkowników

2011-08-13T22:47:33Z

Zbyszek:

{{PortalMenu}}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"

! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Podstawy</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.pl/files/przewodnik.pdf Przewodnik po podstawach symulatora lotu ]
* [[FAQ]]
* [[Wymagania systemowe]]

|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Podstawy pilotażu</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.pl/files/przewodnik.pdf Przewodnik po podstawach symulatora lotu ]
* [[Pl/Lot śmigłowcem|Lot śmigłowcem]]
* [[Pl/Szybownictwo|Szybownictwo]]
* [[Pl/Holowanie przez MP|Holowanie przez MP]]
* [[Pl/Nawigacja|Nawigacja]]

|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Konfiguracja FlightGear</h2>
|-
|style="color:#000;"|
* [[PL/Instalowanie scenerii|Instalowanie scenerii]]
* [[Pl/Instalowanie samolotów|Instalowanie samolotów]]
* [[Pl/Konfiguracja TerraSync|Konfiguracja TerraSync]]
* [[Pl/Konfiguracja trybu multiplayer|Konfiguracja trybu multiplayer]]
* [[Joystick]]

|-
|}
|}

[[de:Portal:Benutzer]]
[[es:Portal:Usuario]]
[[en:Portal:User]]
[[zh:Portal:用户]]

Pl/Holowanie przez MP

2011-08-13T22:37:44Z

Zbyszek: Created page with "Z FlightGear 1.0 oraz późniejszymi wersjami możesz ćwiczyć holowanie przez internet używając Multiplayer'a. Obecnie jest tylko ki..."

Z [[FlightGear]] 1.0 oraz późniejszymi wersjami możesz ćwiczyć holowanie przez internet używając [[Pl/Konfiguracja trybu multiplayer|Multiplayer'a]]. Obecnie jest tylko kilka samolotów i szybowców umożliwiających takie holowanie. Te dostępne to:

'''Samoloty'''
* [[De Havilland Canada DHC-2 Beaver|Beaver]] (dhc2W)
* [[Rallye-MS893E]] (rallye-MS893 )
* [[Piper J3 Cub|J3]] (j3cub)

'''Szybowce'''
* [[ASK-13 sailplane|ASK13]]
* [[Schleicher ASK 21 Glider|ASK21]]
* [[SZD-9bis Bocian-1E|Bocian]]
* [[Glaser-Dirks DG-300|DG-300]]
* [[Glaser-Dirks_DG-101G|DG-101G]]

W następującym przykładzie używamy J3 Cub oraz Bociana, jeżeli jesteś niedoświadczony w holowaniu spróbuj użyć Beaver'a; jest bardziej przyjazny dla pilota.

[[File:aerotow2.jpg]]

Kołuj Cub'em na odległość mniejszą niż 60 metrów od Bociana. Pilot szybowca musi kliknąć <tt>Ctrl-o</tt>. Obaj piloci powinni widzieć wiadomość radiową, mówiącą że są ze sobą połączeni, następnie pilot Cub'a może zacząć ciągnąć szybowiec. Można obserwować odległość pomiędzy maszynami w property browser; <tt>/sim/hitches/aerotow/tow/dist</tt> and <tt>/sim/hitches/aerotow/tow/dist-time-lag-corrected</tt>Until we have the instrumentation designed that is capable of displaying the distance between the two aircraft, the J3 pilot should watch in the property browser. Bądź ostrożny, gdy odległość zbliży się do 60m, maksymalnej długości liny holowniczej. Piloci powinni spróbować wystartować gładko. Od liny można się odpiąć klikając "O" (<tt>Shift-o</tt>).

[[File:aerotow.jpg]]

Jeżeli nie korzysta się z sieci lokalnej, obaj piloci powinni być na tym samym serwerze, co ograniczy opóźnienie czasowe.