https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=TeXnicer&feedformat=atomFlightGear wiki - User contributions [en]2024-03-29T08:02:16ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=F%C3%BCssen_(ED02)&diff=83751Füssen (ED02)2015-04-23T19:20:27Z<p>TeXnicer: </p>
<hr />
<div>== Füssen (ED02) ==<br />
This is work in progress to build up a full documentation of German scenery as present in terrasync/Flightgear 3.4.0. [[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]])<br />
'''Füssen Airfield''' is a glider airfield near Füssen in Bavaria, Germany.<br />
{{infobox Airport<br />
|name = Füssen<br />
|image =ED02-top.jpg<br />
|alt = <br />
|iata =<br />
|icao =<br />
|type =<br />
|city =<br />
|owner =<br />
|website =http://luftsportverein-fuessen.de/<br />
|runway=<br />
|length=<br />
|material=<br />
}}<br />
<br />
[[File:ED02-overview.jpg|thumb|Füssen (ED02)]]<br />
<br />
<br />
<br />
{|<br />
| Autor: || unknown<br />
|-<br />
|}<br />
<br />
[[Category:Airports in Germany]]<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 12:54, 17 March 2015 (EDT)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Munich_Airport&diff=82595Munich Airport2015-03-18T19:47:49Z<p>TeXnicer: </p>
<hr />
<div>{{infobox Airport<br />
|name = Flughafen München - Franz Josef Strauß<br />
|image = EDDM panorama.jpg<br />
|alt = 1,487 ft / 453 m<br />
|iata = MUC<br />
|icao = EDDM<br />
|type = Public<br />
|city = Munich<br />
|owner = Flughafen München GmbH<br />
|website = http://www.munich-airport.com/<br />
|runway = 26R/08L<br />
|length = 4000 m <br />
|material = Concrete<br />
|runway2 = 26L/08R<br />
|length2 = 4000 m <br />
|material2 = Concrete <br />
}}[[File:E170TakeOffEDDM.png|thumb|270px|Embraer E170 taking off from EDDM 26R facing west.]]<br />
<br />
<br />
== '''Munich Airport- Franz Josef Strauß''' ==<br />
<br />
<br />
The '''Flughafen München''' is also known as '''Flughafen München - Franz Josef Strauß''' and is the international [[airport]] that serves the city of Munich. It is located 28 km northeast of downtown München, and popular by regional airlines.<br />
<br />
Franz Josef Strauß (1915-1988) was a Bavarian politician (CSU) and hobby-pilot. He was also member of the Airbus supervising board and the "father" of the [[A340]]. The A340 prototype, called "Franz Josef Strauß", was the first aircraft taking off the new Munich Airport in 1992.<br />
<br />
== Runways ==<br />
EDDM has two runways. The runways are positioned approximately parallel (82°/262°).The distance between both runways is 2300m, the runways are 1500m put, this allows independent operation of each.<br />
<br />
A third runway is planned in the north of the airport, which is like the other two 4000m long and 60m wide.<br />
Currently, this project stopped by people decission in Munich on the 17.06.2012.<br />
<br />
== ILS ==<br />
<br />
In "The Manual" you can read how to perform an [[ILS]]-Landing.<br />
<br />
Use the listed values, when you want to land at EDDM<br />
<br />
{| class="wikitable" style="width:50%" border="1" cellpadding="5" cellspacing="2"<br />
|+ EDDM-ILS<br />
!'''RWY''' !!'''FREQ''' !!'''HDG''' !!'''GS''' !!'''CAT'''<br />
|-<br />
|08L ||110.3||82°||3.00°||CAT-IIIb<br />
|-<br />
|08R ||110.9||82°||3.00°||CAT-IIIb<br />
|-<br />
|26L ||108.3||262°||3.00°||CAT-IIIb<br />
|-<br />
|26R ||108.7||262°||3.00°||CAT-IIIb<br />
|}<br />
<br />
== Terminals ==<br />
EDDM has 2 terminals: Terminal 1 and Terminal 2.<br />
<br />
'''Terminal 1''' is a 1081m long building, which is splitted in 5 parts. <br />
In the near of Terminal 2, there is an extern building called Terminal 1 F<br />
<br />
'''NOTICE: ALL PARKING POSITIONS ARE COMING WITH THE NEWEST TERRASYNC UPDATE'''<br />
<br />
{| class="wikitable" style="width:50%" border="1" cellpadding="5" cellspacing="2"<br />
|+ EDDM-Terminal 1<br />
!'''Part''' !!'''Airlines''' !!'''Parking-Positions''' !!'''Notices'''<br />
|-<br />
|A ||Air Berlin and partners||101-105||<br />
|-<br />
|B ||British Airlines,Condor,Delta,Iberia...||107-110||<br />
|-<br />
|C ||Emirates ([[A380]]), Etihad,Aeroflot,Polet,Rossyia...||111-113||<br />
|-<br />
|D ||Air France,KLM,Alitalia and other Skyteam||115-121||only Departure<br />
|-<br />
|E ||Skyteam||115-121||only Arrival<br />
|-<br />
|F ||Lufthansa,El Al,Akria,Sun d'Or||Other positions at Field West||Flights to Israel, Extern Building<br />
|-<br />
|Other positions||All Airlines||131-197||Field positions, some with satellite-jetways<br />
|}<br />
<br />
'''Terminal 2''' was opened in 2003 and is operated by the Lufthansa and Star Alliance.<br />
The building on the field east become in the near future a satellite terminal for T2.<br />
<br />
{| class="wikitable" style="width:50%" border="1" cellpadding="5" cellspacing="2"<br />
|+ EDDM-Terminal 2<br />
!'''Part''' !!'''Airlines''' !!'''Parking-Positions'''!!Notices <br />
|-<br />
|T2-Building ||Star Alliance+Qatar Airways||201-231||<br />
|-<br />
|Satellite (future)||Star Alliance||243-256;305-317||<br />
|-<br />
|Regional Aircraft||Lufthansa Cityline, Augsburg Airways,Air Dolomiti...||261,262,321-339||<br />
|}<br />
<br />
{| class="wikitable" style="width:50%" border="1" cellpadding="5" cellspacing="2"<br />
|+ EDDM-Special positions<br />
!'''Part''' !!'''Airlines''' !!'''Parking-Positions'''!!Notices <br />
|-<br />
|CARGO ||Lufthansa Cargo,Polet,Global Supply Systems, TNT, DHL, FedEX||901-907||<br />
|-<br />
|Apron 6+7+8||Special Guests||601-805||<br />
|}<br />
<br />
[[File:MIA0283-KL666@eddm.png|thumb|540px|A320-NEO (Merlion) and B777-200 (KLM) at T2.]]<br />
<br />
<br />
[[Category:Airports in Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:EDDM_panorama.jpg&diff=82594File:EDDM panorama.jpg2015-03-18T19:38:44Z<p>TeXnicer: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=EDDM Munich airport panorama taken from scenic public (admission fee) viewpoint "Besucherhügel"}}<br />
|date=2015-03-18 20:36:28<br />
|source={{own}}<br />
|author=[[User:TeXnicer|TeXnicer]]<br />
|permission=<br />
|other versions=<br />
}}<br />
EDDM Munich airport panorama taken from scenic public (admission fee) viewpoint "Besucherhügel"<br />
<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}<br />
<br />
<br />
[[Category:EDDM]]<br />
[[Category:Airport]]<br />
[[Category:Germany]]<br />
[[Category:Panorama]]<br />
[[Category:Photographs]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=F%C3%BCssen_(ED02)&diff=82554Füssen (ED02)2015-03-17T17:11:46Z<p>TeXnicer: Created page with "== Füssen (ED02) == This is work in progress to build up a full documentation of German scenery as present in terrasync/Flightgear 3.4.0. ~~~ {{infobox Airport |name = Füss..."</p>
<hr />
<div>== Füssen (ED02) ==<br />
This is work in progress to build up a full documentation of German scenery as present in terrasync/Flightgear 3.4.0. [[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]])<br />
<br />
{{infobox Airport<br />
|name = Füssen<br />
|image =ED02-top.jpg<br />
|alt = <br />
|iata =<br />
|icao =<br />
|type =<br />
|city =<br />
|owner =<br />
|website =http://luftsportverein-fuessen.de/<br />
|runway=<br />
|length=<br />
|material=<br />
}}<br />
<br />
[[File:ED02-overview.jpg|thumb|Füssen (ED02)]]<br />
<br />
<br />
<br />
{|<br />
| Autor: || unknown<br />
|-<br />
|}<br />
<br />
[[Category:Airports in Germany]]<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 12:54, 17 March 2015 (EDT)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Agathazell_(ED01)&diff=82553Agathazell (ED01)2015-03-17T17:07:35Z<p>TeXnicer: </p>
<hr />
<div>== Agathazell (ED01) ==<br />
This is work in progress to build up a full documentation of German scenery as present in terrasync/Flightgear 3.4.0. [[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]])<br />
<br />
{{infobox Airport<br />
|name = Agathazell<br />
|image =Ed01-top.jpg<br />
|alt = <br />
|iata =<br />
|icao =<br />
|type =<br />
|city =<br />
|owner =<br />
|website =http://www.agathazell.info/<br />
|runway=<br />
|length=<br />
|material=<br />
}}<br />
<br />
[[File:Ed01-overview.jpg|thumb|ed01 Agathazell]]<br />
<br />
<br />
<br />
{|<br />
| Autor: || unknown<br />
|-<br />
|}<br />
<br />
[[Category:Airports in Germany]]<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 12:54, 17 March 2015 (EDT)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:ED02-top.jpg&diff=82552File:ED02-top.jpg2015-03-17T17:02:48Z<p>TeXnicer: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=ed02 Füssen}}<br />
|date=2015-03-17 18:02:14<br />
|source={{own}}<br />
|author=[[User:TeXnicer|TeXnicer]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:ED02-overview.jpg&diff=82551File:ED02-overview.jpg2015-03-17T17:02:37Z<p>TeXnicer: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=ed02 Füssen}}<br />
|date=2015-03-17 18:02:13<br />
|source={{own}}<br />
|author=[[User:TeXnicer|TeXnicer]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Agathazell_(ED01)&diff=82550Agathazell (ED01)2015-03-17T16:56:32Z<p>TeXnicer: </p>
<hr />
<div>{{infobox Airport<br />
|name = Agathazell<br />
|image =Ed01-top.jpg<br />
|alt = <br />
|iata =<br />
|icao =<br />
|type =<br />
|city =<br />
|owner =<br />
|website =http://www.agathazell.info/<br />
|runway=<br />
|length=<br />
|material=<br />
}}<br />
<br />
[[File:Ed01-overview.jpg|thumb|ed01 Agathazell]]<br />
<br />
<br />
== Runways ==<br />
ED01 has one runway.<br />
<br />
<br />
== Agathazell (ED01) ==<br />
{|<br />
| Autor: || unknown<br />
|-<br />
|}<br />
<br />
[[Category:Airports in Germany]]<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 12:54, 17 March 2015 (EDT)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Agathazell_(ED01)&diff=82549Agathazell (ED01)2015-03-17T16:54:27Z<p>TeXnicer: Created page with "{{infobox Airport |name = Agathazell |image =Ed01-top.jpg |alt = |iata = |icao = |type = |city = |owner = |website =http://www.agathazell.info/ |runway= |length= |material= }..."</p>
<hr />
<div>{{infobox Airport<br />
|name = Agathazell<br />
|image =Ed01-top.jpg<br />
|alt = <br />
|iata =<br />
|icao =<br />
|type =<br />
|city =<br />
|owner =<br />
|website =http://www.agathazell.info/<br />
|runway=<br />
|length=<br />
|material=<br />
}}<br />
<br />
<br />
<br />
<br />
== Runways ==<br />
ED01 has one runway.<br />
<br />
<br />
== Agathazell (ED01) ==<br />
{|<br />
| Autor: || unknown<br />
|-<br />
|}<br />
<br />
[[Category:Airports in Germany]]<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 12:54, 17 March 2015 (EDT)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Ed01-top.jpg&diff=82548File:Ed01-top.jpg2015-03-17T16:53:14Z<p>TeXnicer: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=ed01 Agathazell}}<br />
|date=2015-03-17 17:49:26<br />
|source={{own}}<br />
|author=[[User:TeXnicer|TeXnicer]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Ed01-overview.jpg&diff=82547File:Ed01-overview.jpg2015-03-17T16:53:04Z<p>TeXnicer: User created page with UploadWizard</p>
<hr />
<div>=={{int:filedesc}}==<br />
{{Information<br />
|description={{en|1=ed01 Agathazell}}<br />
|date=2015-03-17 17:49:16<br />
|source={{own}}<br />
|author=[[User:TeXnicer|TeXnicer]]<br />
|permission=<br />
|other versions=<br />
}}<br />
<br />
=={{int:license-header}}==<br />
{{self|cc-by-sa-4.0}}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User:TeXnicer&diff=82546User:TeXnicer2015-03-17T16:37:40Z<p>TeXnicer: /* Arbeiten */</p>
<hr />
<div>== Arbeiten ==<br />
<br />
<pre><br />
ED01, Agathazell<br />
ED02, Füssen<br />
ED03, Pohlheim Viehheide<br />
ED04, Braunfels<br />
ED05, Unterwössen<br />
ED06, Butzbach - Pfingstweide<br />
ED07, Glashütten-Oberems<br />
ED08, Kaufbeuren<br />
ED09, Riedelbach<br />
ED10, ---<br />
ED11, Kamen<br />
EDAB, Bautzen<br />
EDAC, Altenburg Nobitz<br />
EDAD, Dessau<br />
EDAE, Eisenhüttenstadt<br />
EDAH, Heringsdorf<br />
EDAI, Segeletz<br />
EDAJ, Gera Leumnitz<br />
EDAK, Großenhain<br />
EDAL, Fürstenwalde<br />
EDAM, Merseburg<br />
EDAN, Neustadt-Glewe<br />
EDAP, Neuhausen<br />
EDAQ, Halle-Oppin<br />
EDAR, Prina Pratzschwitz<br />
EDAS, Finsterwalde<br />
EDAU, Riesa-Göhlis<br />
EDAV, Finow<br />
EDAW, Roitzschjora<br />
EDAX, Rechlin Larz<br />
EDAY, Strausberg<br />
EDAZ, Schonhagen<br />
EDBC, Magdeburg Cochstedt<br />
EDBD, Dedelow<br />
EDBF, Fehrbellin<br />
EDBH, Barth<br />
EDBJ, Jena Schongleina<br />
EDBK, Kyritz<br />
EDBL, Laucha<br />
EDBM, Magdeburg<br />
EDBO, Oehna<br />
EDBP, Pinnow<br />
EDBQ, Bronkow<br />
EDBR, Rothenburg Görlitz<br />
EDBS, Sömmerda-Dermsdorf<br />
EDBT, Allstedt<br />
EDBU, Pritzwalk Sommersberg<br />
EDBV, Stralsund<br />
EDBW, Werneuchen<br />
EDBY, Scholdow<br />
EDBZ, Schwarzheide Schipkau<br />
EDCA, Anklam<br />
EDCB, Ballenstedt<br />
EDCD, Cottbus Drewitz<br />
EDCE, Eggerstdorf Müncheberg<br />
EDCG, Rugen<br />
EDCJ<br />
EDCM<br />
EDCT<br />
EDCW<br />
EDCY<br />
EDDC<br />
EDDG<br />
EDDH<br />
EDDM<br />
EDDN<br />
EDDP<br />
EDDV<br />
EDDW<br />
EDFQ<br />
EDH1<br />
EDHB<br />
EDHC<br />
EDHE<br />
EDHF<br />
EDHG<br />
EDHI<br />
EDHK<br />
EDHL<br />
EDHM<br />
EDHN<br />
EDHO<br />
EDHS<br />
EDHU<br />
EDHW<br />
EDIG<br />
EDJA<br />
EDKL<br />
EDKM<br />
EDKO<br />
EDKZ<br />
EDLA<br />
EDLB<br />
EDLH<br />
EDLI<br />
EDLM<br />
EDLO<br />
EDLP<br />
EDLT<br />
EDLW<br />
EDLZ<br />
EDME<br />
EDMJ<br />
EDMK<br />
EDML<br />
EDMO<br />
EDMS<br />
EDMV<br />
EDMW<br />
EDNB<br />
EDNF<br />
EDNL<br />
EDNM<br />
EDNV<br />
EDOD<br />
EDOE<br />
EDOG<br />
EDOP<br />
EDOQ<br />
EDOX<br />
EDPQ<br />
EDPS<br />
EDQD<br />
EDQE<br />
EDQP<br />
EDQW<br />
EDUF<br />
EDUS<br />
EDVH<br />
EDVM<br />
EDVR<br />
EDVY<br />
EDWB<br />
EDWC<br />
EDWE<br />
EDWF<br />
EDWG<br />
EDWH<br />
EDWI<br />
EDWJ<br />
EDWK<br />
EDWL<br />
EDWM<br />
EDWN<br />
EDWO<br />
EDWQ<br />
EDWR<br />
EDWS<br />
EDWU<br />
EDWV<br />
EDWX<br />
EDWY<br />
EDWZ<br />
EDXA<br />
EDXC<br />
EDXD<br />
EDXE<br />
EDXF<br />
EDXG<br />
EDXI<br />
EDXJ<br />
EDXL<br />
EDXM<br />
EDXN<br />
EDXP<br />
EDXQ<br />
EDXR<br />
EDXS<br />
EDXT<br />
EDXU<br />
EDXZ<br />
</pre></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User:TeXnicer&diff=82545User:TeXnicer2015-03-17T16:26:48Z<p>TeXnicer: </p>
<hr />
<div>== Arbeiten ==<br />
<br />
<pre><br />
ED01<br />
ED02<br />
ED05<br />
ED08<br />
ED11<br />
EDAB<br />
EDAC<br />
EDAD<br />
EDAJ<br />
EDAK<br />
EDAN<br />
EDAP<br />
EDAQ<br />
EDAR<br />
EDAS<br />
EDAU<br />
EDAW<br />
EDBO<br />
EDBP<br />
EDBQ<br />
EDBR<br />
EDBZ<br />
EDCD<br />
EDCJ<br />
EDCM<br />
EDCT<br />
EDCW<br />
EDCY<br />
EDDC<br />
EDDG<br />
EDDH<br />
EDDM<br />
EDDN<br />
EDDP<br />
EDDV<br />
EDDW<br />
EDFQ<br />
EDH1<br />
EDHB<br />
EDHC<br />
EDHE<br />
EDHF<br />
EDHG<br />
EDHI<br />
EDHK<br />
EDHL<br />
EDHM<br />
EDHN<br />
EDHO<br />
EDHS<br />
EDHU<br />
EDHW<br />
EDIG<br />
EDJA<br />
EDKL<br />
EDKM<br />
EDKO<br />
EDKZ<br />
EDLA<br />
EDLB<br />
EDLH<br />
EDLI<br />
EDLM<br />
EDLO<br />
EDLP<br />
EDLT<br />
EDLW<br />
EDLZ<br />
EDME<br />
EDMJ<br />
EDMK<br />
EDML<br />
EDMO<br />
EDMS<br />
EDMV<br />
EDMW<br />
EDNB<br />
EDNF<br />
EDNL<br />
EDNM<br />
EDNV<br />
EDOD<br />
EDOE<br />
EDOG<br />
EDOP<br />
EDOQ<br />
EDOX<br />
EDPQ<br />
EDPS<br />
EDQD<br />
EDQE<br />
EDQP<br />
EDQW<br />
EDUF<br />
EDUS<br />
EDVH<br />
EDVM<br />
EDVR<br />
EDVY<br />
EDWB<br />
EDWC<br />
EDWE<br />
EDWF<br />
EDWG<br />
EDWH<br />
EDWI<br />
EDWJ<br />
EDWK<br />
EDWL<br />
EDWM<br />
EDWN<br />
EDWO<br />
EDWQ<br />
EDWR<br />
EDWS<br />
EDWU<br />
EDWV<br />
EDWX<br />
EDWY<br />
EDWZ<br />
EDXA<br />
EDXC<br />
EDXD<br />
EDXE<br />
EDXF<br />
EDXG<br />
EDXI<br />
EDXJ<br />
EDXL<br />
EDXM<br />
EDXN<br />
EDXP<br />
EDXQ<br />
EDXR<br />
EDXS<br />
EDXT<br />
EDXU<br />
EDXZ<br />
</pre></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Leipzig-Altenburg_Airport_(EDAC)&diff=82544Leipzig-Altenburg Airport (EDAC)2015-03-17T15:44:32Z<p>TeXnicer: Created page with "== Leipzig-Altenburg (EDAC) == {| class="wikitable" |- ! Category !! Status |- | Terragear || unknown |- | Runway/Taxiway || unknown |- | Taxiway Signs || unknown |- | Buildi..."</p>
<hr />
<div>== Leipzig-Altenburg (EDAC) ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Category !! Status<br />
|-<br />
| Terragear || unknown<br />
|-<br />
| Runway/Taxiway || unknown<br />
|-<br />
| Taxiway Signs || unknown<br />
|-<br />
| Buildings || unknown<br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
! Radio !! Name !! Frequency<br />
|-<br />
| FIS || München Information || 125.800<br />
|-<br />
| VDF || || 123.575 <br />
|-<br />
| ILS || 22 || 108.700 <br />
|-<br />
| ATIS || || <br />
|-<br />
| TWR || Altenburg Tower || 123.575 <br />
|-<br />
| GND || || <br />
|-<br />
| INFO || Altenburg Info || 123.575<br />
|}<br />
<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 11:30, 17 March 2015 (EDT)<br />
<br />
[[Category:Airports in Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Bautzen_(EDAB)&diff=82543Bautzen (EDAB)2015-03-17T15:30:12Z<p>TeXnicer: </p>
<hr />
<div>== Bautzen (EDAB) ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Category !! Status<br />
|-<br />
| Terragear || unknown<br />
|-<br />
| Runway/Taxiway || unknown<br />
|-<br />
| Taxiway Signs || unknown<br />
|-<br />
| Buildings || unknown<br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
! Radio !! Name !! Frequency<br />
|-<br />
| FIS || München Information || 125.800<br />
|-<br />
| ATIS || || <br />
|-<br />
| TWR || || <br />
|-<br />
| GND || || <br />
|-<br />
| INFO || Bautzen Info || 120.600<br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
| ELEV || 568<br />
|-<br />
| RWY 07R/25L || 2200×50m<br />
|-<br />
| RWY 07L/25R || 1000×40m<br />
|-<br />
| LAT || N 51° 11,61'<br />
|-<br />
| LON || E 014° 31,18'<br />
|}<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 11:30, 17 March 2015 (EDT)<br />
<br />
[[Category:Airports in Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Bautzen_(EDAB)&diff=82542Bautzen (EDAB)2015-03-17T15:21:55Z<p>TeXnicer: Created page with "== Bautzen (EDAB) == {| class="wikitable" |- ! Radio !! Name !! Frequency |- | FIS || München Information || 125.800 |- | ATIS || || |- | TWR || || |- | GND || || |- |..."</p>
<hr />
<div>== Bautzen (EDAB) ==<br />
<br />
{| class="wikitable"<br />
|-<br />
! Radio !! Name !! Frequency<br />
|-<br />
| FIS || München Information || 125.800<br />
|-<br />
| ATIS || || <br />
|-<br />
| TWR || || <br />
|-<br />
| GND || || <br />
|-<br />
| INFO || Bautzen Info || 120.600<br />
|}<br />
<br />
{| class="wikitable"<br />
|-<br />
| ELEV || 568<br />
|-<br />
| RWY 07R/25L || 2200×50m<br />
|-<br />
| RWY 07L/25R || 1000×40m<br />
|-<br />
| LAT || N 51° 11,61'<br />
|-<br />
| LON || E 014° 31,18'<br />
|}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Portal:Wiki&diff=81962Portal:Wiki2015-03-06T09:35:07Z<p>TeXnicer: Changed the IRC link to be clickable. (Windows, Chatzilla configured)</p>
<hr />
<div>{{Main page/Header<br />
|title=Welcome to the wiki editing portal<br />
|introduction= This is the place to find out what is happening on the FlightGear wiki. Learn what tasks need to be done and what groups there are to join, and share news about recent events or current activities taking place on the wiki.<br />
|rightbox=<br />
<!-------------------------------------------------------------<br />
Portal overview<br />
--------------------------------------------------------------><br />
|rightcolumn1= </div><br />
<span style="font-size:105%; font-weight:bold">Checking articles</span><br /><br />
<span style="font-style:italic;"><br />
Also check: [[Special:NewPages|new articles]], [[Special:NewFiles|new files]] and [[Special:RecentChanges|recent changes]].</span><br />
|rightcolumn2= [[FIle:Portal lamp.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">Inspiration for new articles</span><br /><br />
<span style="font-style:italic;"><br />
[[Understanding the Project]]<br/><br />
[[Special:WantedPages|Most wanted articles]]<br/><br />
[[Help:Translate|Translating articles]]</span><br />
|rightcolumn3= [[File:Portal_radarwheel.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">Improving articles</span><br /><br />
<span style="font-style:italic;"><br />
[[:Category:Articles considered for deletion|Articles considered for deletion]] – [[:Category:Accuracy disputes|Accuracy disputes]]<br/><br />
[[:Category:Stubs|Extending short articles]]<br/><br />
[[Fixing up articles with wrong quotes]]<br/><br />
[[:Category:Articles to be merged|Articles to be merged]]</span><br />
|rightcolumn4= [[File:Portal developer.png|40px]] </div><br />
<span style="font-size:105%; font-weight:bold">Regular maintenance</span><br /><br />
<span style="font-style:italic;"><br />
[[Portal:Wiki/Plugin Requests|Plugin Installation Requests]]<br/><br />
[[:Category:Picture of the week|Pictures of the week]]<br/><br />
Uncategorized: [[Special:UncategorizedFiles|files]] – [[Special:UncategorizedPages|pages]]<br/><br />
[[Special:LonelyPages|Orphaned pages]] – Pages with no links to them yet.<br/><br />
[[:Category:Undocumented templates|Undocumented templates]]<br/><br />
[[Special:Categories|Categories]]<br/><br />
[[FlightGear wiki:Missing images|If you find missing images]]<br/><br />
[[FlightGear wiki:Notes to administrators|Notes to admins]]</span><br />
<br />
<!-------------------------------------------------------------<br />
Main sections<br />
--------------------------------------------------------------><br />
|sections=<br />
{{Main page/Leftbox|title=Get involved!<br />
|contents=Just like FlightGear itself, the wiki can be considered open-source. Everyone is encouraged to [[Special:UserLogin|register an account]] and start contributing!<br />
<br />
Maybe you noticed that the article on your favourite aircraft is a bit [[:Category:out of date|out of date]] and you can give it a refresh, or the Howto on making coffee on the 747 [[:Category:cleanup|needs a cleanup]], or the one on Blender [[:Category:Image requested|lacks a picture]], you have found a spam link or simply a typo and want to fix it! All are very valid reasons to join and every little effort helps the maintainers, even just adding the [[:Category:Maintenance templates|proper template]] to let them know. Remember to add a meaningful summary message, maintainers [[Special:RecentChanges|do read them]]!<br />
<br />
By the way, do you want to help with [[Help:Maintenance|regular maintenance]]? That would give you the opportunity to learn a whole lot on the FlightGear project. In fact, ''maintaining documentation is the classical way of getting into an open project''.<br />
<br />
This portal provides links to useful wikitools and articles, ranging from how to write your first article to extensive markup techniques. See also the [[Help:Contents|help pages]].<br />
<br />
One last note. Remember that any contribution to this wiki is licensed under the [[GPL|GNU GPL version 2]].<br />
<br />
}}<br />
<br />
{{Main page/Leftbox|title=Discuss!<br />
|contents=__NOTOC__<br />
Discuss the wiki and helping each other out improving the wiki!<br />
<br />
Please, '''remember to sign your comments''': use four tildes ("<tt><nowiki>~~~~</nowiki></tt>") or the sign button ([[File:Button sig.png|16px]]) above the editor text box.<br />
<br />
; Individual pages: To discuss individual pages, use their "Discussion" page accessible through the tab at the top left of corner of the page.<br />
<br />
; The wiki in general: Discuss the wiki, its organization and maintenance at the [[FlightGear wiki:Village pump|Village pump]].<br />
<br />
; Chat: There is a wiki related IRC channel at irc://irc.flightgear.org/#wiki<br />
<br />
}}<br />
<br />
}}<br />
{{Main page/Rightcolumn end|title=[[Special:Statistics|Wiki statistics]]<br />
|contents=<br />
* {{NUMBEROFARTICLES}} articles<br />
* {{NUMBEROFFILES}} files<br />
* {{NUMBEROFUSERS}} users<br />
}}<br />
<br />
[[es:Portal:Wiki]]<br />
[[fr:Portal:Wiki]]<br />
[[nl:Portaal:Wiki]]<br />
[[Category:Portals]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User_talk:Fgjosh&diff=77970User talk:Fgjosh2014-11-23T13:18:15Z<p>TeXnicer: </p>
<hr />
<div>Hi, this is Carsten.<br />
Pretty nice work in Dresden.<br />
I like to link up with you and you can teach me some lessons how to do those airports.<br />
I work with blender, but have no problem learning other things, too.<br />
<br />
Looking forward to talk to you. Are you actively flying in FG?<br />
I recently started dr400-dauphin, single mot. D-ECHO, D-EKSW, D-7875<br />
<br />
Greetings!<br />
TeXnicer<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 08:14, 25 October 2014 (UTC)<br />
<br />
::Hej Carsten,<br />
<br />
::It is nice to read. Your terminal of dresden was my first template and inspiration. For modelling I use sketchup (currently Version 8), because I knew this tool a little bit. What I found good was the import of google maps to sketchup. You can add a location/region. So you can draw the base geometry of a building. I have read a lot about flightgear 3D modelling at the forum and wiki. I learned a lot from models of the database too. 3 years later i can say: I never stop learning :-) For xml editing I use bluefish, mostly I paste and copy my code snippets. I don't fly online very often and I don't have a fix callsign. You are welcome in the flightgear forum (http://forum.flightgear.org/)! We can communicate via PM or E-Mail. There are a lot of helpers. josh is my name at this forum.<br />
:: Greetings from Dresden<br />
:: — [[User:Fgjosh|Fgjosh]] ([[User talk:Fgjosh|talk]]) 13:03, 23 November 2014 (UTC)<br />
<br />
Hallo Fgjosh, (if you cannot read the following lines in German, please let me know.)<br />
ich denke, wenn ich 10 Jahre in Dresden gelebt habe und Du in Dresden lebst, können wir auch deutsch schreiben?! Ich gucke immer wieder mal in das Flightgear-Projekt, insbesondere wenn mich andere Flugsimulatoren nerven. Mich hat es jetzt nach Bayern verschlagen. Seit Juli arbeite ich an meiner Segelfluglizenz - ich stehe kurz vor der B-Prüfung. Jetzt ist aber erst einmal Theorie angesagt. Zeit zu modellieren, z.B. unseren Flugplatz. Die Lage ist malerisch vor der Bergkette der Oberbayrischen Voralpen im Inntal. <br />
Bist Du im IRC?<br />
Bist Du im mumble?<br />
Bist Du im Teamspeak?<br />
Zur Not: Skype? <br />
Ich würde gerne mal ein paar Worte mit Dir wechseln, lernen. <br />
Vor allem Terragear macht mir Sorgen - mit Taxidraw habe ich schon einmal gearbeitet, aber EDWP scheint nicht aufgenommen worden zu sein. <br />
<br />
Du merkst, ich habe viele Fragen, ich werde aber auch mal in das Forum schauen.<br />
<br />
Grüße aus Bayern,<br />
TeXnicer</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=De/Extra_EA-500&diff=77291De/Extra EA-5002014-10-25T09:29:57Z<p>TeXnicer: /* Download */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = <br />
|name = Extra EA-500<br />
|type = Ziviler Flugzeugtyp<br />
|fdm = JSBSim<br />
|status-fdm = 4<br />
|status-systems = 2<br />
|status-cockpit = 2<br />
|status-model = 2<br />
|authors = D-EKEW, D-Leon, D-STHO<br />
|fgname = extra500<br />
}}<br />
[[File:Extra 500.jpg|thumb|250px|Die echte Extra 500]]<br />
Die '''Extra EA-500''' ist ein einmotoriges Turbopropgetriebenes Reise- und Geschäftsflugzeug der Extra Flugzeugproduktions- und Vertriebs GmbH. Es wird das erste Flugmodell in [[:de:FlightGear|FlightGear]] sein, bei dem Verschleiß vollständig simuliert wird. Außerdem wird es über eines der am weitesten entwickelten und modernsten Glascockpits in FlightGear verfügen.<br />
<br />
== Status ==<br />
Seit März 2013 arbeiten D-EKEW, D-Leon, D-STHO an diesem Modell. Dazu greifen sie auf Originaldaten des Pilotenhandbuches zurück. Personen die das Flugzeug in der Wirklichkeit erlebt haben, helfen außerdem bei der Feineinstellung des Flugdynamikverhaltens sowie dem Verhalten der Bordsysteme.<br />
<br />
== Flugzeugdaten ==<br />
{| class="wikitable" cellpadding="2" style="margin-left:auto; margin-right:auto"<br />
|-<br />
!colspan=2| Allgemein<br />
|-<br />
|Besatzung<br />
|1<br />
|-<br />
|Kapazität<br />
|5 PAX oder 525 kg Nutzlast<br />
|-<br />
|Länge <br />
|10,1 m<br />
|-<br />
|Spannweite<br />
|11,7 m<br />
|-<br />
|Höhe<br />
|3,4 m<br />
|-<br />
|Leergewicht<br />
|1.420 kg<br />
|-<br />
|Maximales Startgewicht<br />
|2.130 kg<br />
|-<br />
!colspan=2| Antrieb<br />
|-<br />
|Triebwerkstyp<br />
|Turboprop<br />
|-<br />
|Triebwerk<br />
|Rolls-Royce Modell 250-B17F/2<br />
|-<br />
!colspan=2| Leistungsdaten<br />
|-<br />
|Reisegeschwindigkeit<br />
|210 kto<br />
|-<br />
|Strömungsabriss-Geschw.<br />
|61 kto<br />
|-<br />
|Reichweite<br />
|2.963 km<br />
|-<br />
|Betriebsdauer<br />
|7,9 Stunden bei Reisegeschw.<br />
|-<br />
|Flughöhe<br />
|25.000 ft<br />
|-<br />
|Steigrate<br />
|1.335 ft/min<br />
|}<br />
<br />
== Download ==<br />
Die Entwickler-Version wird in Kürze via Gitorius verfügbar sein.<br />
<br />
https://gitorious.org/extra500/extra500<br />
<br />
[[Category:Business aircraft]]<br />
[[Category:Civil utility aircraft]]<br />
[[Category:Extra]]<br />
[[Category:High wing aircraft]]<br />
[[Category:Propeller aircraft]]<br />
[[Category:Single-engine aircraft]]<br />
<br />
[[en:Extra EA-500]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User_talk:Fgjosh&diff=77290User talk:Fgjosh2014-10-25T08:14:24Z<p>TeXnicer: Created page with "Hi, this is Carsten. Pretty nice work in Dresden. I like to link up with you and you can teach me some lessons how to do those airports. I work with blender, but have no probl..."</p>
<hr />
<div>Hi, this is Carsten.<br />
Pretty nice work in Dresden.<br />
I like to link up with you and you can teach me some lessons how to do those airports.<br />
I work with blender, but have no problem learning other things, too.<br />
<br />
Looking forward to talk to you. Are you actively flying in FG?<br />
I recently started dr400-dauphin, single mot. D-ECHO, D-EKSW, D-7875<br />
<br />
Greetings!<br />
TeXnicer<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 08:14, 25 October 2014 (UTC)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User:TeXnicer&diff=65357User:TeXnicer2013-12-07T11:16:35Z<p>TeXnicer: </p>
<hr />
<div>==Errors== <br />
<br />
===WED/X-Plane===<br />
I worked out an airport layout in WED. When testing in Xplane10 it seems to be scaled less 1.0. The overall location seems to be smaller. Anyone experience the same? Will it be the same in FG?<br />
I have no plan to test WED-files in FG prior to submitting to Robin.<br />
<br />
<br />
===genapts===<br />
<code><pre>Longitude = -180:180<br />
Latitude = -90:90<br />
Warning: cannot open ./AirportArea/poly_counter<br />
Unknown line in file: 100 30.00 3 0 0.00 1 0 1 14 53.32268283 008.06949400<br />
0 0 1 0 0 0 32 53.31992100 008.07722500 0 0 1 0 0 0</pre></code></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User_talk:Johan_G&diff=65356User talk:Johan G2013-12-07T11:14:53Z<p>TeXnicer: </p>
<hr />
<div>== Wrong page ==<br />
Thanks, I noticed that something is wrong, but did not find time to work on it. <br />
In Categories EDWP is now listed under "S" for Sonderlandeplatz. I think better would be "W"iefelstede-Conneforde (Sonderlandeplatz).<br />
What do you think about it?<br />
<br />
[[User:TeXnicer|TeXnicer]] ([[User talk:TeXnicer|talk]]) 11:14, 7 December 2013 (UTC)<br />
<br />
<br />
== Swedish ==<br />
<br />
Hi Johan,<br />
<br />
thanks for starting translating articles to Swedish! Unfortunately, the wiki admin has to "add" this language to the system (therefore adding [[sv:Article]] does not work as of now). I've immediately asked him to do so, but it might take a while. In the meantime you can continue translating articles, it's just the linking that doesn't work.<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 08:36, 3 July 2011 (EDT)<br />
<br />
:Ah, that explains why the language link doesn't seem to work. Thank you! I sent him a mail as well. Well, at least I can continue (in a slow pace). [[User:Johan G|Johan G]] 08:43, 3 July 2011 (EDT)<br />
<br />
== Don't be a stranger. ==<br />
<br />
Jag hoppas att du kommer tillbaka snart. {{Unsigned2|11:45, 11 October 2011|PH-JBO}}<br />
<br />
:Thank you for hoping for my return. Den som väntar på något gott... ''In other words, I'm back.'' [[User:Johan G|Johan G]] 09:59, 5 December 2011 (EST)<br />
::Du är inte ensam. Välkommen tillbaka! [[User:PH-JBO|PH-JBO]] 07:28, 6 December 2011 (EST)<br />
<br />
== Test ==<br />
<br />
A short thest to see if a new section added with the "+" tab is appended to the bottom of the page. [[User:Johan G|Johan G]] 07:32, 9 February 2012 (EST)<br />
<br />
== Discussing new main page/portals ==<br />
<br />
Hi,<br />
<br />
would be nice if you could come on [[IRC]] this week. I'd like to discuss the new main page/portals that I've been working on ;)<br />
You'll find me in [irc://#wiki@irc.flightgear.org #wiki@irc.flightgear.org]<br />
<br />
Cheers,<br />
[[User:Gijs|Gijs]] 12:27, 19 March 2012 (EDT)<br />
<br />
: Hi, I should be in #wiki now as Johan_G. This will bee interesting. I have not used IRC before, and last time I watched it over someones shoulder was in <s>1999</s> 1998!<br />
: —[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 14:52, 19 March 2012 (EDT)<br />
<br />
== Infobox aircraft changes ==<br />
<br />
I thought, I'd better get in touch with the only wikimedia template guru that I know :-) I just added a handful of meta categories (inspired by [http://forum.flightgear.org/viewtopic.php?f=25&t=21431#p195109]), and now want to extend the infobox accordingly, including images for each supported features, see: http://wiki.flightgear.org/Template_talk:Infobox_aircraft Any ideas/preference how to implement this best? Images will probably be contributed by Michat. Thanks --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:33, 30 November 2013 (UTC)<br />
<br />
:It is low on my to-do list, but see my answer at [[Template talk:Infobox aircraft]].<br />
:—[[User:Johan G|Johan G]] ([[User_talk:Johan_G|Talk]] | [[Special:Contributions/Johan_G|contribs]]) 18:08, 1 December 2013 (UTC)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=User:TeXnicer&diff=65273User:TeXnicer2013-12-05T20:38:06Z<p>TeXnicer: Created page with "==Errors== ===genapts=== <code><pre>Longitude = -180:180 Latitude = -90:90 Warning: cannot open ./AirportArea/poly_counter Unknown line in file: 100 30.00 3 0 0.00 1 0 1 14 ..."</p>
<hr />
<div>==Errors== <br />
<br />
===genapts===<br />
<code><pre>Longitude = -180:180<br />
Latitude = -90:90<br />
Warning: cannot open ./AirportArea/poly_counter<br />
Unknown line in file: 100 30.00 3 0 0.00 1 0 1 14 53.32268283 008.06949400<br />
0 0 1 0 0 0 32 53.31992100 008.07722500 0 0 1 0 0 0</pre></code></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Sonderlandeplatz_Wiefelstede-Conneforde&diff=65272Sonderlandeplatz Wiefelstede-Conneforde2013-12-05T20:34:16Z<p>TeXnicer: Created page with "{{airport-stub}} {{infobox Airport |name = Sonderlandeplatz Wiefelstede-Conneforde |image = |iata = |icao = EDWP |type = Public |owner = |city = Conneforde, Germany (near Wie..."</p>
<hr />
<div>{{airport-stub}}<br />
<br />
{{infobox Airport<br />
|name = Sonderlandeplatz Wiefelstede-Conneforde<br />
|image =<br />
|iata =<br />
|icao = EDWP<br />
|type = Public<br />
|owner =<br />
|city = Conneforde, Germany (near Wiefelstede)<br />
|runway = 12/30<br />
|length = 600 m <br />
|material = Grass<br />
|website = http://www.flugplatz-wiefelstede-conneforde.de/<br />
}}<br />
The [[:Category:Airports|airport]] is open for [[aircraft]] that fall in the following categories:<br />
* Aircraft up to 2.0to MTOW.<br />
* Powered gliders.<br />
* [[Helicopter]] up to 3.5 to.<br />
<br />
<br />
<br />
Random specs:<br />
* Contact Conneforde Info 126,500 MHz 5min prior to arrival<br />
* No take-offs between 1200h and 1400 (GMT+1) (summer: 1300h and 1500h (GMT+2))<br />
* Aproaching RWY 30 avoid overflying holiday resort in extension to RWY 30.<br />
* Do not overfly urban areas below 800 ft.<br />
* fuel: Super bleifrei, SuperPlus, Diesel, AVGAS<br />
* RWY 12 TORA 399 m LDA 600 m x 30 m<br />
* RWY 30 TORA 600 m LDA 399 m x 30 m<br />
* ELEV 31,17 ft / 9,5 m<br />
* FROM VOR WSR 112,90 MHz 268° 28 NM<br />
* VOR BMN 117,45 MHz 334° 30 NM<br />
* VOR BMN 112,40 MHz 079° 53 NM<br />
* NDB JEV 390,00 kHz 165° 12 NM<br />
* AIS: Bremen <br />
* MET: Hamburg <br />
* GAFOR: 5 NW Niedersachsen (Lower-Saxony)<br />
<br />
[[Category:Airports in Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Category:Airports_in_Germany&diff=65271Category:Airports in Germany2013-12-05T20:32:45Z<p>TeXnicer: </p>
<hr />
<div>{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"<br />
|-<br />
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! style="background:#efefef" | [[TerraSync]] !! class="unsortable" style="background:#efefef" | Comment <br />
|-<br />
| [[Leipzig-Altenburg Airport|EDAC]] || Leipzig-Altenburg || some models || 850 layout || {{tick}} || military hangars, tower, some landmarks next to the airfield, lightning is Rembrandt ready <br />
|-<br />
| EDAH || Heringsdorf, Usedom || Taxidraw || unknown || {{cross}} || nice coastal site<br />
|-<br />
| EDDB || Berlin-Schönefeld || Taxidraw || unknown || {{cross}} <br />
|-<br />
| [[EDDF]] || Frankfurt am Main || many models, Taxidraw || Custom Scenery, refinements || {{tick}} || many models, interactive traffic, moving Skytrain (separate Custom Scenery existing) ||<br />
|-<br />
| [[EDDK]] || Köln-Bonn || Taxidraw || unknown|| {{tick}} || Terminals but no taxi signs.<br />
|-<br />
| [[EDDM]] || München || many models, Taxidraw || unknown|| {{tick}} || many models, interactive traffic<br />
|-<br />
| [[EDDC]] || Dresden International || some models || lit, 850 Layout || {{tick}} ||Terminal, Tower and animated GA Hangars, lightning is Rembrandt ready <br />
|-<br />
| [[EDDH]] || Hamburg-Fuhlsbüttel || some models || unknown || {{tick}} ||<br />
|-<br />
| [[EDDI]] || Berlin-Tempelhof || many models || unknown || {{tick}} || famous main terminal and many static airport buildings around<br />
|-<br />
| [[EDDL]] || Düsseldorf || some models || unknown || {{cross}} || (separate Custom Scenery existing)<br />
|-<br />
| [[EDDP]] || Leipzig/Halle || many models || 850 Layout || {{tick}} || Terminals B and C, DHL hub, luggage terminal, taxiway bridges over highway, taxiway signs, modelled villages, many static models in the area around (some still under devel.), only lightning on Apron 1 is Rembrandt ready<br />
|-<br />
| [[EDDS]] || Stuttgart || some models || unknown || {{tick}} || hole airport arranged exclusively by shared models<br />
|-<br />
| [[EDDT]] || Berlin-Tegel || some models || unknown || {{tick}} ||<br />
|- <br />
| [[EDDV]] || Hannover || Taxidraw || Tower || {{Feedback}} || Terminals and other models from Heliflyer have yet to be brought into proper shape.<br />
|-<br />
| EDDW || Bremen Airport || generic || unknown || {{Feedback}} || many models<br />
|-<br />
| [[EDFM]] || Mannheim || some models || unknown || {{Feedback}} || <br />
|-<br />
| [[EDHL]] || Lübeck Blankensee || models (excl. Tile) || models (incl. Tile) || {{cross}} || <br />
|-<br />
| [[EDKB]] || Bonn-Hangelar || some models || unknown || {{cross}} || <br />
|-<br />
| [[EDLA]] || Arnsberg-Menden || generic || unknown || {{Feedback}} || nice wavy pasture<br />
|-<br />
| [[EDLE]] || Essen-Mühlheim || Taxidraw || unknown || {{cross}} || <br />
|- <br />
| [[EDLN]] || Mönchengladbach || Taxidraw || Redone v850 layout || {{Feedback}} || So far only full taxisigns and aircraft ways, working on models next<br />
|-<br />
| [[EDVE]] || Braunschweig || many models || unknown || {{tick}} || <br />
|-<br />
| EDVI || Höxter-Holzminden || generic || unknown || {{Feedback}} || nice wavy pasture<br />
|-<br />
| (none) || Verden-Scharnhorst || unknown || unknown || {{cross}} || <br />
|-<br />
| [[EDWM]] || Weser-Wümme airfield || unknown || unknown || {{Feedback}} || <br />
|-<br />
| [[Sonderlandeplatz Wiefelstede-Conneforde|EDWP]] || Wiefelstede-Conneforde || in development || in development || {{cross}} || <br />
|-<br />
<br />
| [[EDWQ]] || Ganderkesee-Atlas airfield || generic || unknown || {{Feedback}} || <br />
|-<br />
| [[EDWL]] || Langeoog || nothing || unknown || {{cross}} || small island airfield <br />
|-<br />
| EDXH || Helgoland || Custom Scenery || Taxidraw || {{Feedback}} || would need a way to model hight levels<br />
|-<br />
| [[EDXW]] || Sylt-Westerland || Terminals, Hangar || more static models || {{tick}} || complex modelled Apron 1 and 2 with nice static models.<br />
|-<br />
|(none) || Menden-Barge || some models || unknown || {{cross}} || glider field<br />
|}<br />
<br />
[[Category:Airports in Europe|Germany]]<br />
[[Category:Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Category:Airports_in_Germany&diff=65270Category:Airports in Germany2013-12-05T20:31:10Z<p>TeXnicer: </p>
<hr />
<div>{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"<br />
|-<br />
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! style="background:#efefef" | [[TerraSync]] !! class="unsortable" style="background:#efefef" | Comment <br />
|-<br />
| [[Leipzig-Altenburg Airport|EDAC]] || Leipzig-Altenburg || some models || 850 layout || {{tick}} || military hangars, tower, some landmarks next to the airfield, lightning is Rembrandt ready <br />
|-<br />
| EDAH || Heringsdorf, Usedom || Taxidraw || unknown || {{cross}} || nice coastal site<br />
|-<br />
| EDDB || Berlin-Schönefeld || Taxidraw || unknown || {{cross}} <br />
|-<br />
| [[EDDF]] || Frankfurt am Main || many models, Taxidraw || Custom Scenery, refinements || {{tick}} || many models, interactive traffic, moving Skytrain (separate Custom Scenery existing) ||<br />
|-<br />
| [[EDDK]] || Köln-Bonn || Taxidraw || unknown|| {{tick}} || Terminals but no taxi signs.<br />
|-<br />
| [[EDDM]] || München || many models, Taxidraw || unknown|| {{tick}} || many models, interactive traffic<br />
|-<br />
| [[EDDC]] || Dresden International || some models || lit, 850 Layout || {{tick}} ||Terminal, Tower and animated GA Hangars, lightning is Rembrandt ready <br />
|-<br />
| [[EDDH]] || Hamburg-Fuhlsbüttel || some models || unknown || {{tick}} ||<br />
|-<br />
| [[EDDI]] || Berlin-Tempelhof || many models || unknown || {{tick}} || famous main terminal and many static airport buildings around<br />
|-<br />
| [[EDDL]] || Düsseldorf || some models || unknown || {{cross}} || (separate Custom Scenery existing)<br />
|-<br />
| [[EDDP]] || Leipzig/Halle || many models || 850 Layout || {{tick}} || Terminals B and C, DHL hub, luggage terminal, taxiway bridges over highway, taxiway signs, modelled villages, many static models in the area around (some still under devel.), only lightning on Apron 1 is Rembrandt ready<br />
|-<br />
| [[EDDS]] || Stuttgart || some models || unknown || {{tick}} || hole airport arranged exclusively by shared models<br />
|-<br />
| [[EDDT]] || Berlin-Tegel || some models || unknown || {{tick}} ||<br />
|- <br />
| [[EDDV]] || Hannover || Taxidraw || Tower || {{Feedback}} || Terminals and other models from Heliflyer have yet to be brought into proper shape.<br />
|-<br />
| EDDW || Bremen Airport || generic || unknown || {{Feedback}} || many models<br />
|-<br />
| [[EDFM]] || Mannheim || some models || unknown || {{Feedback}} || <br />
|-<br />
| [[EDHL]] || Lübeck Blankensee || models (excl. Tile) || models (incl. Tile) || {{cross}} || <br />
|-<br />
| [[EDKB]] || Bonn-Hangelar || some models || unknown || {{cross}} || <br />
|-<br />
| [[EDLA]] || Arnsberg-Menden || generic || unknown || {{Feedback}} || nice wavy pasture<br />
|-<br />
| [[EDLE]] || Essen-Mühlheim || Taxidraw || unknown || {{cross}} || <br />
|- <br />
| [[EDLN]] || Mönchengladbach || Taxidraw || Redone v850 layout || {{Feedback}} || So far only full taxisigns and aircraft ways, working on models next<br />
|-<br />
| [[EDVE]] || Braunschweig || many models || unknown || {{tick}} || <br />
|-<br />
| EDVI || Höxter-Holzminden || generic || unknown || {{Feedback}} || nice wavy pasture<br />
|-<br />
| (none) || Verden-Scharnhorst || unknown || unknown || {{cross}} || <br />
|-<br />
| [[EDWM]] || Weser-Wümme airfield || unknown || unknown || {{Feedback}} || <br />
|-<br />
| [[EDWP]] || Wiefelstede-Conneforde || in development || in development || {{cross}} || <br />
|-<br />
<br />
| [[EDWQ]] || Ganderkesee-Atlas airfield || generic || unknown || {{Feedback}} || <br />
|-<br />
| [[EDWL]] || Langeoog || nothing || unknown || {{cross}} || small island airfield <br />
|-<br />
| EDXH || Helgoland || Custom Scenery || Taxidraw || {{Feedback}} || would need a way to model hight levels<br />
|-<br />
| [[EDXW]] || Sylt-Westerland || Terminals, Hangar || more static models || {{tick}} || complex modelled Apron 1 and 2 with nice static models.<br />
|-<br />
|(none) || Menden-Barge || some models || unknown || {{cross}} || glider field<br />
|}<br />
<br />
[[Category:Airports in Europe|Germany]]<br />
[[Category:Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Category:Airports_in_Germany&diff=65269Category:Airports in Germany2013-12-05T20:04:38Z<p>TeXnicer: </p>
<hr />
<div>{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"<br />
|-<br />
! style="background:#efefef" | ICAO-Code !! style="background:#efefef" | Name of Airfield/Town !! style="background:#efefef" | Status (published) !! style="background:#efefef" | Status (development) !! style="background:#efefef" | [[TerraSync]] !! class="unsortable" style="background:#efefef" | Comment <br />
|-<br />
| [[Leipzig-Altenburg Airport|EDAC]] || Leipzig-Altenburg || some models || 850 layout || {{tick}} || military hangars, tower, some landmarks next to the airfield, lightning is Rembrandt ready <br />
|-<br />
| EDAH || Heringsdorf, Usedom || Taxidraw || unknown || {{cross}} || nice coastal site<br />
|-<br />
| EDDB || Berlin-Schönefeld || Taxidraw || unknown || {{cross}} <br />
|-<br />
| [[EDDF]] || Frankfurt am Main || many models, Taxidraw || Custom Scenery, refinements || {{tick}} || many models, interactive traffic, moving Skytrain (separate Custom Scenery existing) ||<br />
|-<br />
| [[EDDK]] || Köln-Bonn || Taxidraw || unknown|| {{tick}} || Terminals but no taxi signs.<br />
|-<br />
| [[EDDM]] || München || many models, Taxidraw || unknown|| {{tick}} || many models, interactive traffic<br />
|-<br />
| [[EDDC]] || Dresden International || some models || lit, 850 Layout || {{tick}} ||Terminal, Tower and animated GA Hangars, lightning is Rembrandt ready <br />
|-<br />
| [[EDDH]] || Hamburg-Fuhlsbüttel || some models || unknown || {{tick}} ||<br />
|-<br />
| [[EDDI]] || Berlin-Tempelhof || many models || unknown || {{tick}} || famous main terminal and many static airport buildings around<br />
|-<br />
| [[EDDL]] || Düsseldorf || some models || unknown || {{cross}} || (separate Custom Scenery existing)<br />
|-<br />
| [[EDDP]] || Leipzig/Halle || many models || 850 Layout || {{tick}} || Terminals B and C, DHL hub, luggage terminal, taxiway bridges over highway, taxiway signs, modelled villages, many static models in the area around (some still under devel.), only lightning on Apron 1 is Rembrandt ready<br />
|-<br />
| [[EDDS]] || Stuttgart || some models || unknown || {{tick}} || hole airport arranged exclusively by shared models<br />
|-<br />
| [[EDDT]] || Berlin-Tegel || some models || unknown || {{tick}} ||<br />
|- <br />
| [[EDDV]] || Hannover || Taxidraw || Tower || {{Feedback}} || Terminals and other models from Heliflyer have yet to be brought into proper shape.<br />
|-<br />
| EDDW || Bremen Airport || generic || unknown || {{Feedback}} || many models<br />
|-<br />
| [[EDFM]] || Mannheim || some models || unknown || {{Feedback}} || <br />
|-<br />
| [[EDHL]] || Lübeck Blankensee || models (excl. Tile) || models (incl. Tile) || {{cross}} || <br />
|-<br />
| [[EDKB]] || Bonn-Hangelar || some models || unknown || {{cross}} || <br />
|-<br />
| [[EDLA]] || Arnsberg-Menden || generic || unknown || {{Feedback}} || nice wavy pasture<br />
|-<br />
| [[EDLE]] || Essen-Mühlheim || Taxidraw || unknown || {{cross}} || <br />
|- <br />
| [[EDLN]] || Mönchengladbach || Taxidraw || Redone v850 layout || {{Feedback}} || So far only full taxisigns and aircraft ways, working on models next<br />
|-<br />
| [[EDVE]] || Braunschweig || many models || unknown || {{tick}} || <br />
|-<br />
| EDVI || Höxter-Holzminden || generic || unknown || {{Feedback}} || nice wavy pasture<br />
|-<br />
| (none) || Verden-Scharnhorst || unknown || unknown || {{cross}} || <br />
|-<br />
| [[EDWM]] || Weser-Wümme airfield || unknown || unknown || {{Feedback}} || <br />
|-<br />
| [[EDWP]] || Sonderlandeplatz Wiefelstede-Conneforde || in development || in development || {{cross}} || <br />
|-<br />
<br />
| [[EDWQ]] || Ganderkesee-Atlas airfield || generic || unknown || {{Feedback}} || <br />
|-<br />
| [[EDWL]] || Langeoog || nothing || unknown || {{cross}} || small island airfield <br />
|-<br />
| EDXH || Helgoland || Custom Scenery || Taxidraw || {{Feedback}} || would need a way to model hight levels<br />
|-<br />
| [[EDXW]] || Sylt-Westerland || Terminals, Hangar || more static models || {{tick}} || complex modelled Apron 1 and 2 with nice static models.<br />
|-<br />
|(none) || Menden-Barge || some models || unknown || {{cross}} || glider field<br />
|}<br />
<br />
[[Category:Airports in Europe|Germany]]<br />
[[Category:Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=EDWP&diff=65268EDWP2013-12-05T20:01:19Z<p>TeXnicer: Created page with "{{airport-stub}} {{infobox Airport |name = Sonderlandeplatz Wiefelstede-Conneforde |image = |iata = |icao = EDWP |type = Public |owner = |city = Conneforde, Germany (near Wie..."</p>
<hr />
<div>{{airport-stub}}<br />
<br />
{{infobox Airport<br />
|name = Sonderlandeplatz Wiefelstede-Conneforde<br />
|image =<br />
|iata =<br />
|icao = EDWP<br />
|type = Public<br />
|owner =<br />
|city = Conneforde, Germany (near Wiefelstede)<br />
|runway = 12/30<br />
|length = 600 m <br />
|material = Grass<br />
|website = http://www.flugplatz-wiefelstede-conneforde.de/<br />
}}<br />
The [[:Category:Airports|airport]] is open for [[aircraft]] that fall in the following categories:<br />
* Aircraft up to 2.0to MTOW.<br />
* Powered gliders.<br />
* [[Helicopter]] up to 3.5 to.<br />
<br />
<br />
<br />
Random specs:<br />
* Contact Conneforde Info 126,500 MHz 5min prior to arrival<br />
* No take-offs between 1200h and 1400 (GMT+1) (summer: 1300h and 1500h (GMT+2))<br />
* Aproaching RWY 30 avoid overflying holiday resort in extension to RWY 30.<br />
* Do not overfly urban areas below 800 ft.<br />
* fuel: Super bleifrei, SuperPlus, Diesel, AVGAS<br />
* RWY 12 TORA 399 m LDA 600 m x 30 m<br />
* RWY 30 TORA 600 m LDA 399 m x 30 m<br />
* ELEV 31,17 ft / 9,5 m<br />
* FROM VOR WSR 112,90 MHz 268° 28 NM<br />
* VOR BMN 117,45 MHz 334° 30 NM<br />
* VOR BMN 112,40 MHz 079° 53 NM<br />
* NDB JEV 390,00 kHz 165° 12 NM<br />
* AIS: Bremen <br />
* MET: Hamburg <br />
* GAFOR: 5 NW Niedersachsen (Lower-Saxony)<br />
<br />
[[Category:Airports in Germany]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Airports_under_construction&diff=65266Airports under construction2013-12-05T19:51:21Z<p>TeXnicer: </p>
<hr />
<div>== Preface ==<br />
<br />
=== Found a beacon in the middle of the runway in [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal LMML] or some other faults? ===<br />
First you have to know that 90 % of the airports have "bad layouts" at the moment and at some places even maps are not updated (have a [http://mpmap02.flightgear.org/?ll=48.34849178268444,-107.88724422454834&z=16&t=s&fg_server=mpserver02:5000,mpserver02.flightgear.org,5001&update_interval=5&pilot_label=always&icon_mode=normal look here] i.e.). Most of the airports need updates. This is a lot of work when you think about the 20’000 airports in the database. When you read the tutorials how to build airports you can do it yourself and submit your work. Or someone of the contributors here will once start to work on your "wish" - but please be patient and do not send any messages/mails to contributors. You can go to the forum ([http://forum.flightgear.org/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.<br />
<br />
== Airports under construction ==<br />
In this article you find a list of all airports which currently are under construction. You can also see if an airport is "finished" and if the data is already submited to the current database of the mapserver (apt.dat). <br />
<br />
=== Availability of new/changed airports needs some time ===<br />
In FlightGear there is a common workflow to edit airports. First, experienced contributors have to change the airport data with [[Wed]]. Then they submit the new data to the X-Plane community (main scenery data files/airport data file apt.dat). Meantime, other contributors can also submit some scenery to the custom scenery database (for downloading via TerraSync). But for runways, taxiways, beacons, frequencies, the apt.dat file needs an update anyway and maybe also the base scenery around the airport needs an update. Please be patient with updates. It needs more time than you expected.<br />
<br />
== Submit your work plans and schedule your activities ==<br />
Please feel free to edit this page and submit your "pending airport" directly.<br />
<br />
=== Current Activities ===<br />
<br />
{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"<br />
|-<br />
! style="background:#efefef" | ICAO !! style="background:#efefef" | Who !! class="unsortable" style="background:#efefef" | Airport layout !! class="unsortable" style="background:#efefef" | Airport objects !! class="unsortable" style="background:#efefef" | AI Network !! class="unsortable" style="background:#efefef" | Start date !! class="unsortable" style="background:#efefef" | .dat submitted !! class="unsortable" style="background:#efefef" | Comments<br />
|-<br />
|[[EDDP]]||August, D-STHO||x||x||||2012-07-01|||| new 850-layout, ground vehicles and new light concept for Apron 1 and 4 (published 2012-08-05), new Terminal C (published 2012-08-30), new customized buildings on Apron 1, 3 and 4, improved Terminal B and further improvements other buildings<br />
|-<br />
|EDLM||laserman|| ||x|||||2013||||<br />
|-<br />
|EDWG||gral||x||||||2010-02-03||||<br />
|-<br />
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions<br />
|-<br />
|[[EDWL]]||gral||x||||||2010-02-03||||<br />
|-<br />
|[[EDWP]]||TeXnicer||||||||2013-12-05||||First attempts with WED & Co., small airfield<br />
|-<br />
|EDWY||gral||x||||||2010-02-03||||<br />
|-<br />
|EEKE||henrikp||x||||||2010-10||||<br />
|-<br />
|EERU||henrikp||x||||||2010-10||||<br />
|-<br />
|EEKA||henrikp||x||||||2010-10||||<br />
|-<br />
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail<br />
|-<br />
|[[London Gatwick Airport|EGKK]]||karla||||x||x||2010-02-13||2010-02-07||fully complete; over 60 customized buildings and other features with highly detailed day and night textures; full taxiway signs; AI traffic, parking and taxiways; available as direct download (see forum) or on Git/Git<br />
|-<br />
|EHGG||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|[[EHAM]]||Gijs||x||x||x||x||x|| || ||<br />
|- <br />
|[[EHLE]]||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|[[EHVK]]||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHEH||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHKD||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHTX||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|EHAL||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHRD||Gijs||x||x||x||x||x|| || || <br />
|-<br />
|EHLW||Gijs||x||x||x||x||x|| || ||<br />
|-<br />
|KCHO||Catchatyou||x|| || ||2010-12-05|| ||The basic structure of the airport is almost complete, and once the airport is correctly modeled, I will be adding the parking lot, hangars...||<br />
|-<br />
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways<br />
|-<br />
|KDTW||Fgoldbatch||||x||||2011-03-30||||Replacement of McNamara Terminal and addition of North Terminal<br />
|-<br />
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.<br />
|-<br />
|KSFO||karla|| ||x|| ||2010-08-06 ||2010-08-27 ||Terminal 2 fully remodelled; new day and night textures; new light masts; jetways included; actual T2 under reconstruction 2010; available as direct download (see forum) or on Git/Git<br />
|-<br />
|LHPP||sztamas6||x||||||2011-11-02|| || Changin generic taxiways to realistic ones. Adding paved and unpaved aprons. Moving tower position to actual location<br />
|- <br />
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs<br />
|-<br />
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)<br />
|-<br />
|RPLL||D-SKY1||||x||x||2009-12-03||2010-02-11||T1, T2, T3, Tower, AI ground network, AI traffic, ATC freqs. Todo: taxi- and runways redesign<br />
|-<br />
|SBBG||Prestes||x||x|| ||2009-12-26 || ||<br />
|-<br />
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz<br />
|-<br />
|SBPK||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|SBRG||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|SUMU||Prestes||x||x|| ||2010-01-31 || ||<br />
|-<br />
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues<br />
|-<br />
|VTBD||D-SKY1||||x||x||2010-11-27 || ||[http://forum.flightgear.org/viewtopic.php?f=5&t=10075 Work in progress]<br />
|-<br />
|YSSY||scotth1||x||x||x|| ||2011-01-11||adjusted aprons, taxiways, moved windsocks, AI ground network submitted. very basic International terminal yet to be submitted, TODO: domestic terminal, cargo terminal<br />
|}<br />
<br />
== Submit your wishes ==<br />
If you wish to add an airport or think this or another airport needs a change '''[http://forum.flightgear.org/viewtopic.php?f=5&t=6749 you have to post in the forum (scenery enhancement)]'''. But first search the forum with the ICAO code of the airport and be sure that you have read all the posts about this airport. And please submit also some links to images and information you have about/from this airport.<br />
<br />
== Links ==<br />
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] <sup>1)</sup><br />
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] <sup>1)</sup><br />
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]<br />
* [[Taxidraw|TaxiDraw Tutorial]]<br />
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]<br />
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]<br />
<br />
<sup>1)</sup> "mapserver.flightgear.org" is NOT "mpmap02.flightgear.org". The mpmap02 is hosted on another server and could reflect an older apt.dat.gz than the current one of the mapserver or of the Git server.<br />
<br />
=== Other airport work related pages in the FlightGear wiki ===<br />
* List of [[Developed Airports]] with buildings and [[Signs]] already included in the [[FlightGear Scenery Database]]<br />
* [[Germany|Current work in Germany]]<br />
* [[Current Scenery Projects]]<br />
* [[FlightGear User Created Helipad List]]<br />
<br />
[[Category:Airports]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=$FG_ROOT&diff=43462$FG ROOT2012-03-02T10:55:03Z<p>TeXnicer: </p>
<hr />
<div>'''$FG_ROOT''' is refered to as the main directory of [[FlightGear]], containing the so called ''base package'' ([[aircraft]], [[scenery]], [[Menubar|GUI]] files etc). When running FlightGear from a [[command line]], you can set $FG_ROOT via <tt>--fg-root=path/to/root</tt>. In [[FGRun]], it is set on the paths page, previous to the aircraft selection page.<br />
<br />
On Mac OS X, $FG_ROOT is not installed automatically. See [[New to FlightGear#Installing on Mac OS X|New to FlightGear]] for an installation manual.<br />
<br />
===Common paths===<br />
* '''Mac OS X:''' <tt>Applications/FlightGear.app/Contents/Resources/data/</tt><br />
* '''Ubuntu:''' <tt>/usr/share/games/flightgear/</tt><br />
* '''Windows:''' <tt>%ProgramFiles%/FlightGear/data/</tt><br/>In Windows the locale is set using <tt>SET</tt> in prompt.<br />
<br />
[[Category:Special directories|ROOT]]<br />
<br />
[[nl:$FG_ROOT]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Problematic_video_cards&diff=43457Problematic video cards2012-03-02T08:31:45Z<p>TeXnicer: </p>
<hr />
<div>{{Stub}}<br />
<br />
''This is meant to become a list of those video cards that are known to frequently cause issues trying to run FlightGear due to having insufficient capabilities or driver support to properly run FlightGear, please feel free to help maintain this page by adding new entries or updating existing ones'''.<br />
<br />
When building a new system or buying hardware for a computer that is specifically intended to run FlightGear, it seems like a good idea to avoid these cards and instead check out [[Hardware Recommendations]] or more specifically [[Supported Video Cards]].<br />
<br />
Please note that even if you have one of these models, you may still be able to run FlightGear by disabling certain features, please check the forums for advice.<br />
So, if you manage to run FlightGear with any of the cards listed here, please do feel free to update this page and preferably also list any relevant customizations or configuration settings that need to be applied.<br />
<br />
= ASUS =<br />
<br />
* '''ASUS EAH6850 Series''' throws artefacts using shaders. Quick and dirty: shader=0. Not nice though. Help appreciated. [[User:TeXnicer|TeXnicer]] 03:31, 2 March 2012 (EST)<br />
<br />
<br />
= ATI =<br />
* Most ATI Cards have problems running FlightGear. One ATI card that is known to work OK, is the ATI Radeon x1600, with the latest drivers.<br />
* ATI Mobility Radeon [http://flightgear.org/forums/viewtopic.php?f=2&t=2866&p=25018&hilit=intel+gma#p25013]<br />
<br />
= Intel GMA =<br />
The following models of Intel GMA cards have often been found to have insufficient OpenGL support to make use of FlightGear's more recent and advanced features (such as shaders):<br />
* Intel GMA 945<br />
* Intel GMA 950<br />
* Intel GMA 965<br />
* Intel GMA 3000<br />
* Intel GMA X3100<br />
<br />
== Other Intel ==<br />
Non-GMA cards can be posted here, these are most often found on lower-end PCs and laptops/notebooks.<br />
<br />
* Mobile Intel 4 Series Express Chipset Family</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43334Howto:Step-by-step Scenery2012-03-01T00:05:18Z<p>TeXnicer: </p>
<hr />
<div>Status: [[User:TeXnicer|TeXnicer]] 05:50, 29 February 2012 (EST)<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)<br />
<br />
<br />
==== Usable Surface ====<br />
<br />
''''WED''''<br />
* Program (current suggestion: 1.1beta) http://wiki.x-plane.com/Scenery_Tools<br />
* Documentation http://wiki.x-plane.com/Airport_Customization#Importing_airport_data<br />
* fake x-Plane folder [ROOT] needs:<br />
** Sub-Folder: 'Custom Scenery'<br />
** dummy files: 'X-Plane-i686' and 'X-Plane-i686'<br />
<br />
<div style="padding-left:10em;"><br />
<gallery><br />
Image:Fake-xplane.jpg|Creating "fake" X-Plane-Folder for WED<br />
Image:X-plane-folder.jpg|Selecting X-Plane-Folder at WED startup<br />
</gallery><br />
</div><br />
<br />
<br />
==== 3D Modelling ====<br />
<br />
''''Blender''''<br />
<br />
* Use the older version: 2.49b, since 2.6 throws errors using outputs with FlightGear, further 2.6 has not an proper .ac export yet.<br />
* python needs to be installed<br />
* Keep the amount of faces low, better use textures.<br />
* Textures are in 2^n x 2^m size (e.g. 512px x 256px) and .png format. Recommended programs: inkscape, The GIMP.<br />
* LOD should not be created by animation/distance feature but in OSB itself.<br />
* Still only Trigs and Quads are allowed faces. CTRL+R "loop cut" might help to control the faces' shape then.<br />
* Merge existing Objects into one<br />
<br />
==== Issues/Todo ====<br />
<br />
''''OSM''''<br />
<br />
* http://flightgear.org/forums/viewtopic.php?f=5&t=3415</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43312Howto:Step-by-step Scenery2012-02-29T22:21:01Z<p>TeXnicer: </p>
<hr />
<div>Status: [[User:TeXnicer|TeXnicer]] 05:50, 29 February 2012 (EST)<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)<br />
<br />
<br />
==== Usable Surface ====<br />
<br />
''''WED''''<br />
* Program (current suggestion: 1.1beta) http://wiki.x-plane.com/Scenery_Tools<br />
* Documentation http://wiki.x-plane.com/Airport_Customization#Importing_airport_data<br />
* fake x-Plane folder [ROOT] needs:<br />
** Sub-Folder: 'Custom Scenery'<br />
** dummy files: 'X-Plane-i686' and 'X-Plane-i686'<br />
<br />
<div style="padding-left:10em;"><br />
<gallery><br />
Image:Fake-xplane.jpg|Creating "fake" X-Plane-Folder for WED<br />
Image:X-plane-folder.jpg|Selecting X-Plane-Folder at WED startup<br />
</gallery><br />
</div><br />
<br />
<br />
==== 3D Modelling ====<br />
<br />
''''Blender''''<br />
<br />
* Use the older version: 2.49b, since 2.6 throws errors using outputs with FlightGear, further 2.6 has not an proper .ac export yet.<br />
* python needs to be installed<br />
* Keep the amount of faces low, better use textures.<br />
* Textures are in 2^n x 2^m size (e.g. 512px x 256px) and .png format. Recommended programs: inkscape, The GIMP.<br />
* LOD should not be created by animation/distance feature but in OSB itself.<br />
* Still only Trigs and Quads are allowed faces. CTRL+R "loop cut" might help to control the faces' shape then.<br />
* Merge existing Objects into one</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43298Howto:Step-by-step Scenery2012-02-29T21:37:47Z<p>TeXnicer: </p>
<hr />
<div>Status: [[User:TeXnicer|TeXnicer]] 05:50, 29 February 2012 (EST)<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)<br />
<br />
<br />
==== Usable Surface ====<br />
<br />
''''WED''''<br />
* Program (current suggestion: 1.1beta) http://wiki.x-plane.com/Scenery_Tools<br />
* Documentation http://wiki.x-plane.com/Airport_Customization#Importing_airport_data<br />
* fake x-Plane folder [ROOT] needs:<br />
** Sub-Folder: 'Custom Scenery'<br />
** dummy files: 'X-Plane-i686' and 'X-Plane-i686'<br />
<br />
<div style="padding-left:10em;"><br />
<gallery><br />
Image:Fake-xplane.jpg|Creating "fake" X-Plane-Folder for WED<br />
Image:X-plane-folder.jpg|Selecting X-Plane-Folder at WED startup<br />
</gallery><br />
</div><br />
<br />
<br />
==== 3D Modelling ====<br />
<br />
''''Blender''''<br />
<br />
* Use the older version: 2.49b, since 2.6 throws errors using outputs with FlightGear, further 2.6 has not an proper .ac export yet.<br />
* Keep the amount of faces low, better use textures.<br />
* Textures are in 2^n x 2^m size (e.g. 512px x 256px) and .png format. Recommended programs: inkscape, The GIMP.<br />
* LOD should not be created by animation/distance feature but in OSB itself.<br />
* Still only Trigs and Quads are allowed faces. CTRL+R "loop cut" might help to control the faces' shape then.<br />
* Merge existing Objects into one</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Fake-xplane.jpg&diff=43259File:Fake-xplane.jpg2012-02-29T11:33:05Z<p>TeXnicer: uploaded a new version of &quot;File:Fake-xplane.jpg&quot;</p>
<hr />
<div>Creating a Fake X-Plane for WED</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43258Howto:Step-by-step Scenery2012-02-29T11:31:12Z<p>TeXnicer: </p>
<hr />
<div>Status: [[User:TeXnicer|TeXnicer]] 05:50, 29 February 2012 (EST)<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)<br />
<br />
<br />
==== Usable Surface ====<br />
<br />
''''WED''''<br />
* Program (current suggestion: 1.1beta) http://wiki.x-plane.com/Scenery_Tools<br />
* Documentation http://wiki.x-plane.com/Airport_Customization#Importing_airport_data<br />
* fake x-Plane folder [ROOT] needs:<br />
** Sub-Folder: 'Custom Scenery'<br />
** dummy files: 'X-Plane-i686' and 'X-Plane-i686'<br />
<br />
<div style="padding-left:10em;"><br />
<gallery><br />
Image:Fake-xplane.jpg|Creating "fake" X-Plane-Folder for WED<br />
Image:X-plane-folder.jpg|Selecting X-Plane-Folder at WED startup<br />
</gallery><br />
</div></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43257Howto:Step-by-step Scenery2012-02-29T11:21:25Z<p>TeXnicer: </p>
<hr />
<div>Status: [[User:TeXnicer|TeXnicer]] 05:50, 29 February 2012 (EST)<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)<br />
<br />
<br />
==== Usable Surface ====<br />
<br />
''''WED''''<br />
* Program (current suggestion: 1.1beta) http://wiki.x-plane.com/Scenery_Tools<br />
* Documentation http://wiki.x-plane.com/Airport_Customization#Importing_airport_data<br />
* fake x-Plane folder [ROOT] needs:<br />
** Sub-Folder: 'Custom Scenery'<br />
** dummy files: 'X-Plane-i686' and 'X-Plane-i686'<br />
<br />
<gallery><br />
Image:Fake-xplane.jpg|Creating "fake" X-Plane-Folder for WED<br />
Image:X-plane-folder.jpg|Selecting X-Plane-Folder at WED startup<br />
</gallery></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Fake-xplane.jpg&diff=43256File:Fake-xplane.jpg2012-02-29T11:20:37Z<p>TeXnicer: Creating a Fake X-Plane for WED</p>
<hr />
<div>Creating a Fake X-Plane for WED</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:X-plane-folder.jpg&diff=43255File:X-plane-folder.jpg2012-02-29T11:14:54Z<p>TeXnicer: WED - startup</p>
<hr />
<div>WED - startup</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43252Howto:Step-by-step Scenery2012-02-29T10:50:49Z<p>TeXnicer: </p>
<hr />
<div>Status: [[User:TeXnicer|TeXnicer]] 05:50, 29 February 2012 (EST)<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Howto:Step-by-step_Scenery&diff=43251Howto:Step-by-step Scenery2012-02-29T10:49:28Z<p>TeXnicer: Created page with "'''Carsten''' Status: Feb 29th 2012 == Scenery Development: Step by Step == === Aspects of Modelling and Simulation === * Terrain Data and Texture (Landclass?) * Usable Sur..."</p>
<hr />
<div>'''Carsten'''<br />
<br />
Status: Feb 29th 2012<br />
<br />
<br />
== Scenery Development: Step by Step ==<br />
<br />
=== Aspects of Modelling and Simulation ===<br />
<br />
* Terrain Data and Texture (Landclass?)<br />
* Usable Surface (e.g. Runways, Taxiways, Parking areas)<br />
* 3D-Models (e.g. different LOD, day/dusk|dawn/night)<br />
* Navigation data (e.g. ILS/VOR/NDB/TACAN, radio, tower, ground)<br />
* Interaction (e.g. reaction of models to environment like wind, weather, radio requests)<br />
* AI (automatic, semi-automatic, interactive behaviour of NPC/NPV)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Portal:Developer/Scenery&diff=43250Portal:Developer/Scenery2012-02-29T10:41:21Z<p>TeXnicer: </p>
<hr />
<div>{{PortalMenu}}<br />
<br />
{|style="border-spacing:8px; margin:0px -8px; width:100%;"<br />
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|<br />
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
! <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;">The Scenery Portal</h2><br />
|-<br />
|style="color:#000;"| <br />
This portal is for developers of [[FlightGear]] [[scenery]]. And tends to be a home for scenery related articles. See the [[Portal:Developer|developers portal]] for more articles about development.<br />
|}<br />
|}<br />
<br />
{|style="border-spacing:8px; margin:0px -8px;"<br />
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|<br />
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
<br />
! <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;">Scenery</h2><br />
|-<br />
|style="color:#000;"|<br />
* [[Texture requests]] <br />
* [[3D object requests]] <br />
* [[Airport requests]] <br />
<br />
* [[Howto: Shader Programming in FlightGear]]<br />
* [[Howto: Modelling Clouds]] <br />
* [[Howto: Add shared models manually|Add shared models manually]] <br />
* [[Current Scenery Projects]]<br />
* [[Howto: Decrease the number of faces|Decrease the number of faces]] <br />
* [[Howto: Get a number of elevation offsets for a number of objects|Get a number of elevation offsets for a number of objects]] <br />
* [[Howto: Calculate elevations|Calculate elevations]] <br />
* [[Howto: Convert objects from X-Plane|Convert objects from X-Plane or MSFS]]<br />
* [[Howto: Illuminate faces|Illuminate faces]] <br />
* [[Howto: Place 3D objects with the UFO|Place 3D objects with the UFO]] <br />
* [[Howto: Texture a building|Texture a building]]<br />
* [[Scenery Development Resources]]<br />
* [[Textures & Texture Maps in SketchUp]] <br />
* [[Howto: Using QGIS and satellite pictures|Using QGIS and satellite pictures]]<br />
* [[Using Terragear]] <br />
* [[Howto: Step-by-step Scenery]]<br />
|-<br />
|}<br />
<br />
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
! <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;">Airports</h2><br />
|-<br />
|style="color:#000;"|<br />
* [[Blender Ground Signs Tutorial]] <br />
* [[Howto: Make an airport|Make an airport]] <br />
* [[Howto: Make a helipad|Make a helipad]] <br />
* [[Signs]] (placing and explanation) <br />
* [[Testing Your Airport Layout : Quick and Easy]]<br />
* [[About Scenery/Airports|About the Scenery/Airports folder]]<br />
|-<br />
<br />
! <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;">Software</h2><br />
|-<br />
|style="color:#000;"|<br />
* [[Building Terragear]] <br />
* [[Building terragear-cs in Ubuntu 910 (32- or 64-bit)]]<br />
* [[TaxiDraw]]<br />
* [[TerraGear]]<br />
* [[Using Terragear]] <br />
|-<br />
|}<br />
<br />
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
! <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;">Wish Lists</h2><br />
|-<br />
|style="color:#000;"|<br />
* [[Landmark Wish List]] <br />
* [[UK Scenery Wish List]] <br />
|-<br />
|}<br />
<br />
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
! <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;">Nasal Scripting</h2><br />
|-<br />
|style="color:#000;"|<br />
* [[Nasal scripting language]]<br />
* [[Howto: Nasal in scenery object XML files|Nasal in scenery object XML files]]<br />
* [[Howto: Write simple scripts in Nasal|Write simple scripts in Nasal]]<br />
|-<br />
|}<br />
|}<br />
<br />
__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
[[es:Portal:Developer/Scenery]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Texnicer-002.png&diff=12116File:Texnicer-002.png2009-04-12T08:24:44Z<p>TeXnicer: EC135 - Panel reorganisation (Devel of new instrument)</p>
<hr />
<div>EC135 - Panel reorganisation (Devel of new instrument)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Texnicer-001.png&diff=12114File:Texnicer-001.png2009-04-12T08:11:43Z<p>TeXnicer: Transponder in Blender
(TeXnicer)</p>
<hr />
<div>Transponder in Blender<br />
(TeXnicer)</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Texnicer-panel-devel0.png&diff=12111File:Texnicer-panel-devel0.png2009-04-12T07:40:58Z<p>TeXnicer: </p>
<hr />
<div></div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Portal:Developer/3D_Modelers&diff=12089Portal:Developer/3D Modelers2009-04-11T17:48:27Z<p>TeXnicer: </p>
<hr />
<div>{{Stub}}<br />
<div align="center"><br />
[[Portal:Developer|Developer]] - [[Portal:User|User]]<br />
</div><br />
<br />
{|style="border-spacing:8px; margin:0px -8px; width:100%;"<br />
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|<br />
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
! <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;">The 3D Modeling Portal</h2><br />
|-<br />
|style="color:#000;"| <br />
This portal is specific to 3D modeling in general, it is not meant to be about FlightGear specifics such as aircraft or scenery modeling. <br />
It is only meant to provide resources related to 3D modeling for FlightGear in general, for resources such as tutorials, online courses, ebooks, webcasts etc.<br />
If you already know about 3D modeling and you are specifically interested in modeling scenery or aircraft, you will probably want to check out [[Portal:Developer/Aircraft]] or [[Portal:Developer/Scenery]].<br />
|}<br />
|}<br />
<br />
<br />
{|style="border-spacing:8px; margin:0px -8px;"<br />
|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|<br />
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"<br />
<br />
|-<br />
! <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;">3D Modeling</h2><br />
|-<br />
|style="color:#000;"| <br />
* [http://www.linuxhaxor.net/2009/02/19/25-tutorials-to-get-you-started-with-blender/ 25 tutorials to get you started with blender]<br />
* [http://www.linuxhaxor.net/2009/02/09/50-tutorials-to-get-you-started-with-gimp/ 50 tutorials to get started with gimp]<br />
* [[Howto: Illuminate faces|Illuminate faces]]<br />
* [[ Howto: 3D Aircraft Models|3D Aircraft Models]] (howto)<br />
* [[ Model Import and Export ]]<br />
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender|Add smooth shadows in Blender]]<br />
* [[ Modeling - FAQ ]]<br />
* [[ Modeling - Getting Started ]]<br />
* [[ Modeling Resources ]]<br />
* [[ Modeling - SketchUp]]<br />
* [[ Normals and Transparency Tutorial ]]<br />
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Blender3D Modeling]<br />
* [http://wiki.flightgear.org/index.php/Copyright_Inquiry Copyright Inquiry]<br />
* [[ Blender and FlightGear - some experiences]]<br />
|}<br />
|}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=L%C3%BCbeck_Blankensee_Airport&diff=11653Lübeck Blankensee Airport2009-03-29T10:13:30Z<p>TeXnicer: /* Description */</p>
<hr />
<div>Back to [[Germany|Germany Scenery Overview]]<br />
<br />
{{infobox Airport<br />
|name = Lübeck Airport<br />
|image = EDHL.jpg<br />
|iata = N/A<br />
|icao =EDHL<br />
|type =Public<br />
|city = Lübeck, Schleswig-Holstein, Germany<br />
|runway= 25/07<br />
|length= 1800m <br />
|material= Asphalt <br />
|website =http://www.flughafen-luebeck.net/<br />
}}<br />
<br />
{| cellpadding="5" <br />
| Autor: || Torsten Dreyer <br />
|-<br />
| Contact: || via flightgear-devel<br />
|-<br />
| Latest update: || 2009-03-15<br />
|-<br />
| Where to get: || official scenery (models only)<br />
|-<br />
| || http://www.t3r.de/fg/scenery/ (including temp tile)<br />
|}<br />
<br />
[[Image:EDHL-td.jpg|thumb|EDHL (incl. Tile), 2009-03-15]]<br />
<br />
=== Description ===<br />
<br />
The [http://en.wikipedia.org/wiki/Hanse Hansestadt] [http://www.luebeck.de/ Lübeck] is located approx 40km north-east of [http://www.hamburg.de Hamburg] and part of the [http://en.wikipedia.org/wiki/Hanse Hanseatic League] as known from Thomas Mann's famous novel [http://en.wikipedia.org/wiki/Buddenbrooks Die Buddenbrooks].<br />
Its proximity to Hamburg, but also to the Baltic qualifies this rather small airfield as well as its cheap landing fees. No wonder that even Ryanair is using this airfield on a regular (daily?) basis. The "Lübecker Bucht" (Bay of Lübeck) is a known holiday resort.<br />
<br />
Torsten Dreyer modeled many buildings of that Airfield including some nice features. The Town of Lübeck still is generic but looks for people to give it a shape.<br />
<br />
In correlation to this sophisticated piece of work he also modeled the [[Seneca| PA34-200T "Seneca II"]], that is strongly recommended for use from its "homeplate".<br />
<br />
=== Links ===<br />
<br />
{| cellpadding="5" <br />
|-<br />
| Airport info || http://www.eddh.de/info/landeinfo-ergebnis.php?eicao=EDHL<br />
|}<br />
<br />
<br />
<br />
[[User:TeXnicer|TeXnicer]] 15:13, 16 March 2009 (EDT)<br />
<br />
[[Category:Airports]]</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=Scenery&diff=11652Scenery2009-03-29T10:12:18Z<p>TeXnicer: /* See also */</p>
<hr />
<div>'''Scenery''' is the landscape in [[FlightGear]] (or any other simulator).<br />
It includes airports, buildings, trees, mountains, valleys, vegetation, settlements and waterbodies.<br />
The whole world is available for FlightGear, but the details and accuracy vary. The data is released as [[World Scenery]] collections available from the the FlightGear website.<br />
<br />
==Scenery Projects==<br />
* [[Brest]]<br />
* [[Dublin (Scenery)|Dublin]]<br />
* [[FlightGear NL]]<br />
* [[Germany]]<br />
<br />
''See also [[FlightGear related projects]]<br />
<br />
==See also==<br />
* [[Landmark Wish List]]<br />
* [[FlightGear Scenery Designer]]<br />
* [[Installing Scenery]]<br />
* [[Next Generation Scenery]]<br />
* [[Image:Worldscenery-text.jpg]]<br />
<br />
==External links==<br />
* http://www.flightgear.org/Downloads/scenery-0.9.10.html <br />
* http://www.flightgear.org/Downloads/scenery-1.0.0.html<br />
* http://www.flightgear.org/Downloads/scenery-1.0.1.html<br />
<br />
[[Category:Scenery]]<br />
<br />
{{Terra}}</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=File:Worldscenery-text.jpg&diff=11651File:Worldscenery-text.jpg2009-03-29T10:10:56Z<p>TeXnicer: Overview in order to determine the [e|w]NNN[n|s]MMM-coding</p>
<hr />
<div>Overview in order to determine the [e|w]NNN[n|s]MMM-coding</div>TeXnicerhttps://wiki.flightgear.org/w/index.php?title=FGCom_(before_3.0)&diff=11536FGCom (before 3.0)2009-03-21T22:53:20Z<p>TeXnicer: </p>
<hr />
<div>{{cleanup}}<br />
<br />
'''FGCom''' is an addon for [[FlightGear]]. With FGCom (and the infrastructure behind it), FlightGear now has a realtime voice communication system which enriches the FlightGear capabilities, especially for Multiplayer events, like:<br />
*flying in groups (see e.g. the '''Forum Multiplayer Events'''):<br />
**invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”<br />
**do military training like “Air-Air-Refuelling”, “Dog fights”, “Escort flights”, etc. <br />
*offering additional services at an airport like ATC, Snowplows, Pushbacks, etc. (Visit e.g. KSFO on a weekend – sorry enough: Most communication is still by keyboard - we are sure that will change!)<br />
*have a real time flightraing (e.g. pilot in Hongkong, teacher in Sydney) or just ask for online support during flight or just ask somebody flying a plane of interest about specifics<br />
*or e.g. just sit in a cockpit e.g. in Germany while sightseeing San Francisco in a C172, voice-chatting with a Texan in a plan I dreamed of as a boy (Super Constellation), and both getting informations from a New Zealand guy (it shall be a wonderful island – but do real people live there? He said: Yes!!).<br />
*etc.<br />
In the future FGCom surely will extend further and surley will get a “Speech to Text” capability in order to also use the Text-based standard ATC-routines inside FlightGear (see also [[Development]]).<br />
<br />
==Status==<br />
*'''March, 2009:'''<br />
<div style="font-size:150%"><span style="color:magenta">'''This wiki-Page is undergoing a Major Revision'''</span></div><br />
<br />
Since the new version Nov.2008 the usage of FGCom is picking up rapidly – but so are also the confusions of many “Computer-Non-Professionals” trying to use it. We hope to help users by adding many more user-specific informations, like e.g. installation on different Operating Systems, testing, operating, informing, and “how to get the most out of it”. The existing more tech. Informations will remain but will be restructured. We decided to do it online in the “wiki-fashion” so that others can benefit as soon as possible.<br />
This major update will take about a month (or 2).<br />
<br />
--[[User:Jomo|Jomo]] 12:46, 3 March 2009 (EST)<br />
<br />
<br />
*'''18 November, 2008:'''<br />
Latest SVN (rev 163) has the compile problems fixed. Also we have a '''new server: fgcom.flightgear.org.uk'''. User accounts not required (ie. do '''not''' use -U or -P)<br />
*'''31 October, 2008:''' <br />
<br />
The latest SVN release at this time is the '''r149''' which does not compile due to a constant that is not defined (STL_STRING). Such constant appears at line 57 in the file ''src/fgcom_init.cpp'' which is:<br />
''#include STL_STRING''<br />
<br />
I guess that such constant must point to the STL library include file but I am not sure.<br />
I revert to the '''r148''' SVN version which successfully compiles.<br />
<br />
Command to get such version is: ''svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148''<br />
<br />
* '''19 June, 2008:''' Currently the server is <u>down</u> due to hardware problems. It is unknown when the service comes back because he currently has no time to fix the problems.<br />
<br />
* '''22 November 2007:''' Due to heavy development at this time there may be some differences between the information on the web pages and the installation. Please follow the discussions on the FlightGear development list!<br />
<br />
==The Client installation==<br />
===Installing FGCom===<br />
====Hardware Requirements====<br />
If you are satisfied with the operation and responsetimes of your current FGFS installation, then you should see no significant difference after adding the FGCom. If your FGFS installation runs already a little marginal, then you might experience some delays when many new airplane-models etc. must be loaded. This may happen when starting up at a busy airport. You can monitor/verify such a "short-time overload" in the FGstart command-window.<br />
<br />
For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html<br />
<br />
Of course in addition you need a constant connection into the INTERNET, if you actually want to have a worldwide communication.<br />
<br />
====Prequisites/Companions====<br />
<br />
{| style="width:75%" border="1"<br />
|+<br />
|-<br />
|align="center" width="100" |'''FGFS''' ||The basic Flight-Gear-Flight-Simulation installation. This must be installed prior to installing the FGCom ''(except if installing the Linux "CVS complete" version which can install FGCom and FGFS concurrently)''. ref.: http://www.flightgear.org/ <br />
|-<br />
|align="center" | '''FGrun'''||This [[FlightGear Launch Control]] (also known as FG-Wizard), is a graphical front end to start the FGFS. This makes it very easy to startup the FGFS with all it's possible options. In some newer distributions this is already part of the basic FGFS installation package<br />
|-<br />
|align="center" |'''Atlas'''||[[Atlas]] displays the current position of your airplane on an landscape type of map together with navigational informations. It derives its data direct out of the installed FGFS databases. So you do not need any connections to the INTERNET.<br />
|-<br />
|align="center" |'''MPMap'''||[[MPMap]] is a pure browser application based on Google Maps, so it does not need any installation, except a Web-Browser. With MPMap you can watch all Multiuser-planes worldwide on a road-map, satellite picture or a composite of both. It includes most of the airports, navigational aids, and current weather informations. So it can be used for preflight planning, without having the FGFS started or even installed. But it needs a constant connection to the INTERNET - on the other hand you can do your preflight planning anywhere where there is a PC, connected to the INTERNET.<br />
|-<br />
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of the FGFS. As the name says, it enables communication of several players via a chat-function (keyboard) - or with this vocal interface ==> FGCom.<br />
|-<br />
|align="center" |'''Festival'''||Festival is a TTS (Text To Speech) system that can convert all in the FGFS displayed written text (ATC, Chat, etc.) into speech and put it on your loudspeakers. ref.: http://www.flightgear.org/Docs/getstart/getstartch5.html#x10-790005.6 <br />
|-<br />
|align="center" |'''Runwayfinder'''||This standalone Browser-Application( http://www.runwayfinder.com ) does present a fantastic Fight-Planning tool, showing similar aspects like the "MPMap" but adds an Aeronatical map. It does not link to FGFS or MPMap or Multiplayer -- and covers only the domestic USA. <br />
|}<br />
--[[User:Jomo|Jomo]] 12:06, 11 March 2009 (EDT)<br />
====Install on Linux====<br />
For Linux-Systems there are 3 ways to install:<br />
<br />
'''1) Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).''' <br />
*'''Advantage:''' This is the easiest way and ensures that maintenance and services for this package and all concurrencies to it are provided automatically for a reasonable time-frame.<br />
*'''Disadvantage:''' The availability of those packages is usually very late and most Distributors do not cover all FGFS-features. To our knowledge none of the Distributors has an FGCom package available as of March 2009.<br />
*'''Installation:''' Follow the usual procedures of your distributer on how to install additional packages.<br />
'''2) Installing a “CVS complete”''' <br />
*'''Advantage:''' It is the very easiest form of installation and installs in one step all prerequisite/companion modules (FGFS, FGrun, FGcom, PLIB, OSG, Simgear, AT). Also it can be added and removed from the system without disturbing the rest of the system (Libraries, Menus, Structures, etc.). It was tested on several Ubuntu and Debian systems.<br />
*'''Disadvantage:''' No automated maintenance available. The handling is a little different from the standard Menu-driven practice.<br />
*'''Installation:''' http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu<br />
'''3) Compiling it locally'''<br />
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.<br />
*'''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and it's devices.<br />
*'''Installation:'''<br />
<br><br />
Fetch FGCom (a copy of a working iaxclient is inside)<br />
<br />
svn checkout svn://svn.dfn.de:/fgcom/trunk fgcom<br />
<br />
Optional: edit iaxclient/lib/Makefile<br />
<br />
To use OpenAl (Recommended and the default for now. Note however, that it requires OpenAl with capture support.)<br />
<br />
USE_PA_OSS=0<br />
USE_PA_ALSA=0<br />
USE_PA_JACK=0<br />
AUDIO_ALSA=0<br />
AUDIO_OPENAL=1<br />
<br />
To use oss emulation<br />
<br />
USE_PA_OSS=1<br />
USE_PA_ALSA=0<br />
USE_PA_JACK=0<br />
AUDIO_ALSA=0<br />
AUDIO_OPENAL=0<br />
<br />
To use native alsa (WARNING: PTT won't work)<br />
<br />
USE_PA_OSS=0<br />
USE_PA_ALSA=0<br />
USE_PA_JACK=0<br />
AUDIO_ALSA=1<br />
AUDIO_OPENAL=0<br />
<br />
To use portaudio alsa (WARNING: only if your card natively supports 8000Hz sample rate)<br />
<br />
USE_PA_OSS=0<br />
USE_PA_ALSA=1<br />
USE_PA_JACK=0<br />
AUDIO_ALSA=0<br />
AUDIO_OPENAL=0<br />
<br />
Edit fgcom/src/Makefile and check the pathes for PLIB_PREFIX and OPENAL_PREFIX.<br />
<br />
Compile iaxclient and fgcom. To do so, do the following:<br />
<br />
cd fgcom/src && make<br />
<br />
<br />
Note: If you ran that Debian Script you likely need to edit the CXXFLAGS and LDFLAGS lines to, that want to have a dir-info.<br />
e.g.<br />
<br />
CXXFLAGS ... -I [...]/OpenSceneGraph/include<br />
LDFLAGS -L [...]/OpenSceneGraph(/lib)<br />
<br />
Install<br />
<br />
make install<br />
<br />
and you should be ready for a quick test...<br />
<br />
====Install on Windows====<br />
There is no download available directly from the FlightGear home-pages, so you need to search for one in the Internet. We found and tested that one: http://files.ww.com/files/50789.html<br />
*Download the binary file “fgcom-win32.zip” (or similar) and define as target your FGFS-directory. <br />
*Unzip the downloaded file – now you should have added “fgcom.exe” and “positions.txt” to your FGFS-directory<br />
*open a [[Command line|command]] window and type in:<br />
c:\FGFS\fgcom.exe<br />
c: stands for the drive/partion where your FGFS is installed<br />
FGFS stands for the Directory where the FGFS is installed<br />
*if your system requests access via the firewall allow that<br />
<br>--[[User:Jomo|Jomo]] 12:06, 11 March 2009 (EDT)<br />
====Install on Mac====<br />
You can download the "MAC OSX Binary" from the FGFS download-center ( http://www.flightgear.org/Downloads/binary.shtml#mac ). The latest version of the code does contain also the FGCOM.<br />
<br>--[[User:Jomo|Jomo]] 13:13, 21 March 2009 (EDT) <br />
<br />
===Testing===<br />
''If in the following some pictures seem to small to read on your screen, click on it and it will enlarge. Then return with the left arrow at the top of your screen.''<br><br><br />
====Test the basic function==== <br />
Prior to your first FGCom-tests you should verify your audio-system, because the FGCom-installation relies heavily on a good performance of it. If you had already used microphone-recordings or VoIP and thus “trust” your system, then you may pass this chapter and continue with the “-f910”-test. But be sure to return here just as soon as the audio system is not performing as you expected!<br />
(--> [[The "-f910"-Test]])<br />
<br><br>For these basic tests you do not have to start the FGFS nor do you need to operate the PTT (PushToTalk) button.<br />
<br />
=====Verifying your Audio-System=====<br />
Keep the audio-tools easily accessible for adjustments. Please be aware that, due to the different Operating-Systems multiplied by the different Sound-Cards, there are thousands of different tools available for the following tasks. If you cannot recognize the tools by the sample-pictures, please see your system and/or sound-card documentation for the tools you can use for the following basic tasks:<br />
#Make sure you have '''easy access to your audio-controls''' – and know them.<br />
#From the devices available '''define the audio-devices''' you want to use. You may have an audio-module on your motherboard, and multiple sound-cards, and headsets, and Dolby-surround, etc. etc. We strongly recommend to use a headset (at least not to use loudspeakers) in order to reduce the very possible problem of feedback noise. A further reduction in noise can be achieved by using USB-headsets.<br />
#'''Adjust''' your master '''volume-control''' and possible sub-controls to please your ears. Check your volume-control-panel for all controls that may influence your sound output. At least there is one master-control affecting all outputs. In addition there may be several outputs with individual adjustments. You may switch all regulators and switches off – and then switch them on one by one to find out which ones you need. You may also look into all tabs of your volume-control-panel, to see if there are features which may not have been used yet (if e.g. you never yet used a microphone, or VoIP, etc.)<br />
#'''Adjust the Microphone''' and “Boost” devices. All modern Operating-Systems do have an integrated audio-recorder for such adjustments – you should be able to make an acceptable speech-recording. Most microphones do need a “boost” device-driver or extra amplifier. It is nice that all systems do provide this capability, but you have to activate it manually (if needed)! Also be aware that some of the devices may be switched off automatically if the system gets rebooted or an application gets closed. <br />
#Finally '''find the “best fit”''' between your hardware, the network, and the FGCom-server response.<br />
<br />
See the following examples:<br />
<br />
'''1) Easy access to your audio-controls:''' You may need those controls often, so they should be placed easily accessible. Check if you have the Audio-Icon in your Task-bar: e.g.<br />
[[image:FGCOM-Audio-Icon.jpg|thumb|center|400px|Audio-Icon]]<br />
If there is no such Icon anywhere on the screen do:<br />
{| align=center width=900 border="1"<br />
|+<br />
|width=300|typical for '''Linux'''<br />
|width=300|typical for '''Windows'''<br />
|width=300|typical for '''MAC'''<br />
|-<br />
|<br>To my knowledge the icon is shown on all graphical systems of all Linux-Distributions. Thus there is no action required.<br />
|Click on Start → Control Panel → Sounds and Audio:<br />
[[image:FGCOM-W-Volume.jpg|thumb|center|250px|Enabel Audio-Icon]]<br />
|}<br />
<br>'''2) Define the audio-devices to use:'''<br />
{| align=center width=900 border="1"<br />
|-<br />
|width=300|Enter [[Command line|command]]: ''gnome-sound-properties''<br />
[[image:FGCOM-U-Prefs.jpg|thumb|center|250px|test devices]]<br />
For each task you can open a selection-menu (on the right the downward arrow) in order to select the wanted device. I suggest to set all the same:<br />
* for a USB-headset you must select the USB-device<br />
* for all others you might first try “Autodetect”<br />
|width=300|Click right onto the audio-icon → Preferences → Audio-tab:<br />
[[image:FGCOM-W-Audio.jpg|thumb|center|250px|set devices]]<br />
Select your Devices for Playback and Mic.<br />
|width=300|<br />
|}<br />
If you did change these device-settings, it is a good idea to reboot the system prior to continue.<br />
<br><br><br />
'''3) Adjust volume-control''' (for theses first adjustments you should switch the Mic. off!)<br />
{| align=center width=900 border="1"<br />
|-<br />
|width=300|Click right on Audio-Icon → Open Vol. Ctrl:<br />
[[image:FGCOM-UVolCtrl.jpg|thumb|center|250px|Volume Control]]<br />
The amount of the slider-controls may vary depending on the capabilities of the sound-card or the usage of USB-headsets.<br />
<br />
The “booster” is available under “Switches”.<br />
|width=300|Click right on the Audio-Icon → Volume-Ctrl. (or type command: sndvol32)<br />
[[image:FGCOM-W-VolCtrl.jpg|thumb|center|250px|set devices]]<br />
In this example the card overrides the std. Microsoft “Mic.” with “Rear Pink In” because all jacks can accept whatever you like!) - in this case it is the Mic. Be aware of such changes caused by usually “high expense” devices!<br />
<br />
The “booster” is available under options.<br />
|-<br />
|width=300|Just click onto the green “Test” marks in the above device-selection and adjust the volume controls for a good sound.<br />
|width=300|Click on tab. Sounds<br />
[[image:FGCOM-W-Sound.jpg|thumb|center|250px|Sound-test]]<br />
Select one of the longer lasting signals (1), then click on 2 and adjust loudness with above slider-controls.<br />
|width=300|<br />
|}<br />
<br>'''4) Adjust the Microphone:'''<br />
<br>Use the volume-control-panels to enable the microphone for this test. Then:<br />
{| align=center width=900 border="1"<br />
|-<br />
|width=300|Open the recorder with the [[Command line|command]]: ''gnome-sound-recorder''<br />
[[image:FGCOM-U-sndctrl.jpg|thumb|center|250px|Recording-test]]<br />
*Record<br />
*Stop<br />
*Play<br />
|width|Open the Recorder with [[Command line|command]]: ''sndrec32''<br />
[[image:FGCOM-W-sndrec.jpg|thumb|center|250px|Recording-test]]<br />
*Start recording (click red point)<br />
*talk some words into the mic<br />
*stop (rectangel)<br />
*spool back ( < < )<br />
*listen (>)<br />
|width=300| <br />
|}<br />
Try to find the lowest possible microphone-volume for a reasonable speech-replay, without adjusting the loudness-volume from the above set values. If needed add the “booster” or “gain”. But it would be better if you do not need/use the booster, because that will always try to adjust to a recordable volume – even if there are only some background-noises which nobody really wants to hear. <br />
<br><br><br />
'''5) Find the “best fit”'''<br />
<br />
Now perform the following “-f910” test and make final adjustments if needed:<br />
<br />
--[[User:Jomo|Jomo]] 08:28, 18 March 2009 (EDT)<br />
<br><br />
=====The "-f910"-Test=====<br />
Prior to executing the following [[Command line|command]] change into the directory, into which the FGCom was installed. This path will then shown up before the "$" sign.<br />
In case of a "cvs" installation you have to replace "fgcom" with "sh ./run_fgcom.sh". Then type:<br />
<br />
$ fgcom -Sfgcom.flightgear.org.uk -f910 <br />
<br />
<br>That will give the following output:<br />
fgcom - a communication radio based on VoIP with IAX/Asterisk<br />
(c)2007 by H. Wirtz <wirtz@dfn.de><br />
Version 1.2.2 build 163M<br />
Using iaxclient library Version SVN 163M<br />
<br />
Successfully parsed commandline options.<br />
Reading list of airports...done.<br />
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk<br />
Call 0 accepted<br />
Call 0 answered<br />
<br />
speak into the mic and your words will be echoed back with a short delay.<br />
<br>Then type <nowiki>ctrl-C</nowiki> to exit this Quick-Test<br />
<br />
<br>'''In case of trouble''' check the following:<br />
<br />
*'''"parsed command-line options"''' not successful: Check for wrong commands and/or missing “-” signs in front of them. See [[FGCOM#FGCom Options|FGcom Options]].<br />
*'''"Reading list of airports .."''' not successful: Check your file “positions.txt” which should be in the same directory in which you installed the FGCom. This is a normal text-file in which you can add missing informations. (Replacing a complete "Windows" position.txt with a "Linux" one can lead to errors, although lines of both files may be exchanged/added).<br />
*'''"Initializing IAX client"''' not successful: Check if you defined the right server, it must be "-Sfgcom.flightgear.org.uk”. Watch it: The “S” must be capital in Linux, but small for Windows (“-sfgcom.flightgear.org.uk”)! <br />
*No response '''"Call 0 accepted"''': Check your network, especially your firewall for open ports.<br />
*If you did not hear the '''"delayed response"''' echoed back, check the Chapter [[FGCOM#Solving Audio-Problems|Solving Audio-Problems]].<br />
--[[User:Jomo|Jomo]] 01:01, 7 March 2009 (EST)<br />
<br />
====Functional Test + User Briefing====<br />
<br />
Experiences pointed out, that the cooperation FGCom/FGFS works more reliable, if the FGFS gets started first. So we will start with setting up a flight-test-environment:<br />
=====Start the FGFS=====<br />
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:<br />
<br />
If you don't have an Icon available to start the FGrun, then<br />
*use a [[command|command-window]]<br />
*change into the directory in which FGFS was installed <br />
*and start the program from there:<br />
{|border="1"<br />
|+<br />
|-<br />
|width="150"|for linux CVS e.g.:<br />
|width="250"|cd ~/fgfs<br>sh ./run_fgrun.sh <br />
|-<br />
||for Std. Linux e.g.: ||fgrun<br />
|- <br />
||for Windows e.g.: ||D:<br>cd \flightgear<br>fgrun <br />
|-<br />
||for Mac: || ||<br />
|}<br />
Wait for the Program-Window to start and then define:<br><br><br />
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[Tips and Tricks]])<br> <br />
→ Click “Next”<br><br><br />
'''2)''' As '''starting place''' please define the airport KPAO (Palo Alto) runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br><br />
→ Click “Next”<br><br><br />
'''3)''' Define the '''Multiplayer options:''' (see wiki [[Howto: Multiplayer]] for details)<br />
{|<br />
|+<br />
|-<br />
|width=610|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]<br />
|“AI models” must be activated in order to see all traffic<br />
<br><br>“Multiplayer” must be activated<br />
<br><br>type “mpserverXX.flightgear.org” into the field “Hostname:”, replace “XX” with the [[Flightgear mpserver02 - Hong Kongavailable|server number]] nearest you. Actually it does not matter which server you take (as long as it is online) - you might try which server gives you the best response-times.<br />
<br><br>Insert your “Callsign:” (max. 7 characters)<br />
<br><br>define the “in” and “out” ports both with the standard “5000”<br />
<br><br>With "Load/Save as" you may build up yourself library of settings for different airports.<br />
|}→ Click “Advanced”<br><br />
'''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column):<br />
#General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).<br />
#Features: “AI Traffic” should be activated already<br />
#Initial Position: <br />
{|<br />
|+<br />
|-<br />
|width=420|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]<br />
|<br />
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''<br />
<br><br><br>''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.<br />
|}<br />
Open http://mpmap01.flightgear.org<br />
{|<br />
|+<br />
|-<br />
|width=510|[[image:MPmap.jpg|thumb|left|500px|Preflight]]<br />
|<br />
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”<br />
*click on “nav”<br />
*disable all options except “apt code”<br />
*type “KPAO” into the filed “Navaids lookup”<br />
*hit ENTER or click onto the reading-glass symbol<br />
*click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”<br />
*now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links” <br />
*then zoom into the airport<br />
*set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen<br />
*type those long/lat values into the field below and also the wanted heading of the plane while parking<br />
|}<br />
'''5) Network:''' <br />
{|<br />
|+<br />
|-<br />
|width=420|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]<br />
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.<br />
<br><br>WARNING: When saving these settings and reloading them again, FGrun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".<br />
|}<br />
If you need to '''define the unique IP-Address''', open an [[Command|command-window]] and type<br />
{|border="1"<br />
|+<br />
|width="100"|OS<br />
|width="75"|'''to type''' <br />
|width="40"|Cap. ||returned values<br />
|-<br />
||for linux: ||ifconfig ||eth0 ||<br />
Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab<br />
<br>inet addr:'''192.168.178.23''' Bcast:192.168.178.255 Mask:255.255.255.0 <br />
|- <br />
||for Windows: ||ipconfig /all ||et ||<br />
Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF<br />
<br>DHCP aktiviert. . . . . . . . . . : Ja <br />
<br>Autokonfiguration aktiviert . . . : Ja <br />
<br>IP-Adresse. . . . . . . . . . . . : '''192.168.178.20''' <br />
<br>Subnetzmaske. . . . . . . . . . . : 255.255.255.0 <br />
<br>IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4<br />
|-<br />
||for Mac: || || || <br />
|}<br />
The '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!!<br />
<br />
'''6) Input/Output:''' <br />
{|<br />
|+<br />
|-<br />
|width=420|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]<br />
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.<br />
<br><br><br><br />
To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.<br><br><br />
Editing an existing line: Start by clicking onto the existing one, then change as required.<br><br><br />
Deleting an existing Line: Click onto the line to be deleted, then hit "Delete"<br />
<br />
|}<br />
<br />
'''7) Avionics:''' let's define: <br />
{|<br />
|+<br />
|-<br />
|width="50"| <br />
|width="60"|Nav1:<br />
|width="100"|114.10 ||San Jose VOR<br />
|-<br />
| ||Nav2: || 115.80 ||SF VOR<br />
|-<br />
| ||ADF: || 379 || Brijj, beacon at SF<br />
|}<br />
and activate: DME to Nav1<br><br><br />
There is no field to input COM-radios, but remember them for setting them later manually:<br />
{|<br />
|+<br />
|-<br />
|width="50"| <br />
|width="60" |Com1<br />
|width="100" |118.60 ||Paolo Alto<br />
|-<br />
| ||Com2 || 120.50 || San Francisco<br />
|}<br />
<br />
'''8) Properties:''' <br />
Here you can define any presetting for any values in the FGFS.<br>see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”<br />
{|<br />
|+<br />
|-<br />
|width=520|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]<br />
|<br />
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.<br />
<br><br>Input a new line: Just hit “New” and type your string.<br />
<br><br>Edit a line: Be sure first to click onto an existing item and then edit this “Property”<br />
<br><br>Delete a line: Click onto the line to be deleted then hit "Delete"<br />
|}<br />
Hit “OK” → “Run” and watch the FGFS starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.<br><br />
--[[User:Jomo|Jomo]] 13:55, 12 March 2009 (EDT)<br />
<br />
=====Start the FGCom=====<br />
Open a [[command|command-window]] and change into the directory in which FGCom was installed (probably the same as the FGFS) and start the FGCom. Do not use any other options than the server address “-sfgcom.flightgear.org.uk”:<br />
{|border="1"<br />
|+<br />
|-<br />
|width="150"|for linux CVS e.g.:<br />
|width="250"|cd ~/fgfs<br>sh ./run_fgcom.sh <br />
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.<br />
|-<br />
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"<br />
|- <br />
||for Windows e.g.: ||D:<br>cd \flightgear<br>fgcom -sfgcom.flightgear.org.uk ||"-sfgcom..." with small "s"<br />
|-<br />
||for Mac: || ||<br />
|}<br />
The response should be:<br />
/fgcom - a communication radio based on VoIP with IAX/Asterisk <br />
(c)2007 by H. Wirtz <wirtz@dfn.de> <br />
Version 1.2.2 build 206M <br />
Using iaxclient library Version SVN 206M <br />
<br />
Successfully parsed command-line options. <br />
Reading list of airports...done. <br />
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk<br />
If your printout up to that line is different go back to chapter [[Test the basic function]]<br />
<br />
For this test position this command-window somewhere, where you can monitor it throughout the test.<br />
<br />
{|<br />
|+<br />
|-<br />
|width="300"| ||<br />
|-<br />
|1) If COM1 was set to 119.650 you will see the following 2 lines added to the initialization of the FGCom-window: ||<br />
|-<br />
|<br />
Selected frequency: 119.650 <br />
Call rejected by remote<br />
|<br />
Instead of “119.650” there will be shown the last used frequency. In this case the source of the nearest ATC-Freq. 119.650 is more than 50km away from your actual position of the airplane, so FGCom rejects a connection to it. If the last frequency used would have been within 50 km you get an indication very similar to the next item.<br />
|-<br />
|2) Switch COM1 to the for this airport needed 118.60:<br />
|-<br />
|<br />
Selected frequency: 118.600 <br />
Hanging up call 0 <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) <br />
|This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,'''10''',,5500,tcp”, you may change that value later according to your preferences.<br />
|-<br />
|<br>3) Press your PTT (PushToTalk on space-bar and joystick, as available):<br />
|-<br />
|<br />
[SPEAK] unmute mic, mute speaker <br />
[LISTEN] mute mic, unmute speaker <br />
[SPEAK] unmute mic, mute speaker <br />
[LISTEN] mute mic, unmute speaker <br />
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.<br />
|-<br />
|<br>Now lets set the other Radios:<br />
*COM2 = 120.50 San Francisco<br />
*NAV1 = 114.10 San Jose<br />
*NAV2 = 115.80 San Francisco<br />
4) Pressing Upper+Space will now switch to the next radio: '''NAV1'''<br />
|-<br />
|<br />
Radio-Select: NAV1 <br />
Selected frequency: 114.100 <br />
Hanging up call 0 <br />
Call rejected by remote <br />
[LISTEN] mute mic, unmute speaker <br />
|Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!<br />
|-<br />
|<br>5) Pressing Upper+Space once more switches to '''COM2'''<br />
|-<br />
|<br />
Radio-Select: COM2 <br />
Selected frequency: 120.500 <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km) <br />
[LISTEN] mute mic, unmute speaker <br />
Call 0 accepted <br />
Call 0 answered<br />
|That looks OK: San Francisco is about 29 km away<br><br>watch the “km” instead of miles!<br>'''10 km''' = '''6.2137 mi'''<br />
|-<br />
|<br>6) Pressing Upper+Space once more switches to '''NAV2'''<br />
|-<br />
|<br />
Radio-Select: NAV2 <br />
Selected frequency: 115.800 <br />
Hanging up call 0 <br />
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
[LISTEN] mute mic, unmute speaker <br />
|And Yes: The SF VOR is just a little closer than the airport(center)<br />
|-<br />
|<br>7) Pressing Upper+Space once more brings back '''COM1''':<br />
|-<br />
|<br />
Radio-Select: COM1 <br />
Selected frequency: 118.600 <br />
Hanging up call 0 <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
[LISTEN] mute mic, unmute speaker <br />
|-<br />
|<br>8) Lets us start and continue flying in the direction about 130°:<br />
|-<br />
|<br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km) <br />
|notice that you first come closer (to the center of the airport) and after that getting away<br />
|- <br />
|<br>9) Let's switch to '''COM2''' (San Francisco) and watch: <br />
|-<br />
|<br />
Radio-Select: COM2 <br />
Selected frequency: 120.500 <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
[LISTEN] mute mic, unmute speaker <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km) <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km) <br />
.. <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km) <br />
Hanging up call 0 <br />
Radio-Select: NAV2 <br />
Selected frequency: 115.800 <br />
Call rejected by remote <br />
[LISTEN] mute mic, unmute speaker <br />
|That means: at about 50KM we are getting out of ran'''Start the FGFS:'''<br>ge and thus the on COM2 active SF getts terminated. Notice that also the inactive NAV2 gets terminated, because it exceeded the allowable range at about the same time!<br />
|}<br />
10) You could turn now and watch the opposite: At about the same distance those two will become active again (automatically, if you did not change the settings).<br />
<br><br><br />
If you got here without any (technical) problems your FGCom is fully functional. All you have to do now, is trying to test the audio.<br />
=====Final Audio Test=====<br />
There is no formal Test-Environment for that. Just cruise within the San Francisco (or any other) area and listen and/or try calling from time to time: “This is ''YourCallSign'', is somebody listing” or similar. If you hear somebody talking (and it is not the AI-ATC chatter!) but you get no answers, see the chapter "Solving Audio-Problems".<br />
<br />
Also there are many "Multiplayer Events" which use the FGCom possibilities, but also use the text-based FGFS-Menu "Network --> Chat" to enable communication outside the FGCom. See the Flightgear-Forum [[ http://www.flightgear.org/forums/]] and there the "Multiplayer Events".<br />
<br>--[[User:Jomo|Jomo]] 04:20, 18 March 2009 (EDT)<br />
<br />
===Solving Audio-Problems===<br />
Before you start, make sure that your headset is (or speakers and microphone are) working and tested to sensible volumes. Headsets are strongly recommended in order to avoid feedback resonances, which could affect not only you but all fellow listeners with awful or even painful noises. <br />
You may test your Audio-Devices using the basically installed Utilities of your operating system. e.g.: type into a command line for: <br />
#Linux: "gnome-sound-recorder", (you may also check on: Linux software audio mixing with FlightGear) <br />
#Windows: "audiorecorder" <br />
#Mac: ??? <br />
<br />
more Tests / TestSetups etc. ToBeDefined<br />
<br />
===Using FGCom===<br />
ToBeDefined<br />
====Tips and Tricks====<br />
'''Copying-Printing this WIKI-Page'''<br><br />
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:<br />
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )<br />
*to copy:<br />
**select in the Browser-Menu: "File" --> "Save Page as.. "<br />
*to print:<br />
**select the last entry in the sidebar on the left: "Printable version"<br />
**Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"<br />
**before printing I recommend: Menu --> File --> "Print Preview" and you see those now many many pages!<br />
**If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer<br />
Remember the policies: '''Private use only''' !<br />
<br />
'''Editing'''<br><br />
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.<br />
*For windows you can use "WordPad"<br />
*For Linux the "gedit" works fine<br />
<br />
'''Ports needed'''<br><br />
In case of problems over the INTERENT you might check that the the following ports are allowed:<br />
1314 TCP if the Festival-Server is used for Text/Sound <br />
2005 UDP Vcp-Stream<br />
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)<br />
5000 UDP in/out Multiplayer (VPN Sftw.)<br />
5001 UDP Enable HTTP-server<br />
5002 UDP Enable property server<br />
5003 UDP Enable Screen-Shot services<br />
5004 UDP (may be used as a spare)<br />
5505 UDP Terra Sync<br />
16661 UDP FGCom listening to FGFS, usually “local host” only<br />
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).<br />
<br><br><br />
'''PTT Problems''' (Push To Talk)<br />
*'''if the FGCom Command-window initiates, but does not respond to any COMM or PTT activity:'''<br />
**Try to enforce (the usually predefined) port as option. i.e. add “-p16661” to the FGCom Start-Command<br />
**check the FGrun extended Options → Input/output “generic=socket..”: The port there must be the same as for the FGCom, i.e. 16661 (if it was not intentionally changed by you)<br />
**You may try to change the port to e.g. UPD 5004. In this case you have to change at 2 places:<br />
***add the option “-p5004” to the FGCom start-command<br />
***also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004.<br />
***and you may have to tell your Firewall to allow port UPD 5004<br><br><br />
*'''if in the FGCom Command-Window the Airport indication is ok''',<br />
**but when hitting the PTT it does not appear:<br />
***[LISTEN] mute mic, unmute speaker <br />
***[SPEAK] unmute mic, mute speaker</nowiki> <br><br />
**Be sure the FGFS window is the active window. Move the Mouse-Pointer into the FlightGear-Window and click once, then try again (while the Mouse-Pointer remains in that window! Some systems do change the “active Window” according to where the mouse is!)<br />
**Check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line “<key n="32">” then this plane is intentionally using “key 32” (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10.., seafireIIc, spitfireIIa, ufo.<br />
<br><br />
'''Timezones'''<br><br />
When communicating it may be wise to always use the internationally accepted GMT (GreenwichMeanTime). On http://www.timezoneconverter.com/cgi-bin/tzc.tzc everybody can check what GMT means to him/her and thus knows what time you mean.<br />
<br />
===Supplemantery Informations===<br />
====Commandline Parameters====<br />
<br />
''Or if it didn't work perfectly first time''<br />
<br />
fgcom --help<br />
<br />
returns the following useful info<br />
<br />
fgcom - a communication radio based on VoIP with IAX/Asterisk<br />
(c)2007 by H. Wirtz <wirtz@dfn.de><br />
Version 1.2.2 build 163M<br />
Using iaxclient library Version SVN 163M<br />
<br />
OPTION DESCRIPTION<br />
<br />
-d, -debug, --debug= show debugging information<br />
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')<br />
-s, -fgserver, --fgserver= fg to connect to (default: 'localhost')<br />
-p, -port, --port= where we should listen to FG (default: '16661')<br />
-a, -airport, --airport= airport-id (ICAO) for ATC-mode<br />
-f, -frequency, --frequency= frequency for ATC-mode<br />
-U, -user, --user= username for VoIP account (default: 'guest')<br />
-P, -password, --password= password for VoIP account (default: 'guest')<br />
-i, -mic, --mic= mic input level (0.0 - 1.0)<br />
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)<br />
-b, -mic-boost, --mic-boost= enable mic boost<br />
-l, -list-audio, --list-audio= list audio devices<br />
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input<br />
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output<br />
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')<br />
<br />
Available codecs:<br />
u - ulaw (default and best codec because the mixing is based onto ulaw)<br />
a - alaw<br />
g - gsm<br />
s - speex<br />
7 - G.723<br />
<br />
Mode 1: client for COM1 of flightgear:<br />
$ fgcom<br />
- connects fgcom to fgfs at localhost:16661<br />
$ fgcom -sother.host.tld -p23456<br />
- connects fgcom to fgfs at other.host.tld:23456<br />
<br />
Mode 2: client for an ATC at <airport> on <frequency>:<br />
$ fgcom -aKSFO -f120.500<br />
- sets up fgcom for an ATC radio at KSFO 120.500 MHz<br />
<br />
Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!<br />
<br />
Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''<br />
<br />
==Server installation==<br />
<br />
For running a FGCOM server you need Asterisk and depending on the amount of users much bandwith and CPU power. Because of putting pilots and ATCs in a VoIP conference the server-admin has to assure that there is enough network and cpu power to avoid drop-outs of the voice stream.<br />
<br />
===Prerequirements===<br />
<br />
Install Asterisk on top of your favorite distribution. Please refer to installation manuals (e.g. [[http://www.asteriskguru.com/|Asterisk-Guru]]) you can find on the net. You do not need H.323 or SIP because the fgcom client uses IAX2 as VoIP signaling protocol. Only if you think about connecting external VoIP applications to FGCOM you should consider to activate H.323 or SIP (but this is not the scope of this small howto).<br />
<br />
Notice: You need to install the zaptel driver modules - even if you won't use any hardware for telecom interfacing. You need the ztdummy kernel module for the asterisk conference application MeetMe() because it simulates a hardware clock needed by this application. Further development of FGCOM might use app_conference which don't needs any timing device.<br />
<br />
For now we want to use /etc/asterisk as the base configuration directory.<br />
<br />
===Setting up the radio frequencies===<br />
<br />
The radio frequencies are "simple" Conferences and realized due to the Asterisk application MeetMe().<br />
<br />
====Part 1: General configuration====<br />
<br />
First you have to set up the general configuration of the system. Put the following at the top of your "extensions.conf" file:<br />
<br />
[general]<br />
static=yes<br />
writeprotect=yes<br />
;<br />
[globals]<br />
;<br />
[macro-com]<br />
exten => s,1,Answer()<br />
exten => s,n,MeetMe(${MACRO_EXTEN},qd)<br />
exten => s,n,Hangup()<br />
;<br />
[macro-echo]<br />
exten => s,1,Answer()<br />
exten => s,n,Echo()<br />
exten => s,n,Hangup()<br />
;<br />
[guest]<br />
; ATC-Help<br />
exten => 01-ZZZZ-911.000,1,Macro(com)<br />
exten => 012525252591100,1,Dial(Local/01-ZZZZ-911.000)<br />
exten => 01-ZZZZ-910.000,1,Macro(echo)<br />
exten => 012525252591000,1,Dial(Local/01-ZZZZ-910.000)<br />
;<br />
[default]<br />
include => guest<br />
;<br />
; Code:<br />
; 01 - FlightGear<br />
; 02 - Microsoft Flight-Simulator<br />
; 03 - ...<br />
;<br />
; Air2Air<br />
exten => 01-ZZZZ-123.450,1,Macro(com)<br />
exten => 012525252512345,1,Dial(Local/01-ZZZZ-123.450)<br />
exten => 01-ZZZZ-122.750,1,Macro(com)<br />
exten => 012525252512275,1,Dial(Local/01-ZZZZ-122.750)<br />
<br />
====Part 2: Adding your favorite (all?) frequencies====<br />
<br />
For this you have simply to create an extension for every touple of airport/frequency in extensions.conf. The following is an example for Berlin-Tempelhof (EDDI). The information comes from the file "apt.dat.gz" of your FlightGear installation.<br />
<br />
; EDDI ATIS 126.020 - Berlin Tempelhof<br />
exten => 01-EDDI-126.020,1,Macro(com)<br />
exten => 010403030812602,1,Dial(Local/01-EDDI-126.020)<br />
;<br />
; EDDI BERLIN DEP 120.620 - Berlin Tempelhof<br />
exten => 01-EDDI-120.620,1,Macro(com)<br />
exten => 010403030812062,1,Dial(Local/01-EDDI-120.620)<br />
;<br />
; EDDI BERLIN DIRECTOR 121.120 - Berlin Tempelhof<br />
exten => 01-EDDI-121.120,1,Macro(com)<br />
exten => 010403030812112,1,Dial(Local/01-EDDI-121.120)<br />
;<br />
; EDDI BERLIN ARR 126.420 - Berlin Tempelhof<br />
exten => 01-EDDI-126.420,1,Macro(com)<br />
exten => 010403030812642,1,Dial(Local/01-EDDI-126.420)<br />
;<br />
; EDDI GND 121.950 - Berlin Tempelhof<br />
exten => 01-EDDI-121.950,1,Macro(com)<br />
exten => 010403030812195,1,Dial(Local/01-EDDI-121.950)<br />
;<br />
; EDDI TWR 119.570 - Berlin Tempelhof<br />
exten => 01-EDDI-119.570,1,Macro(com)<br />
exten => 010403030811957,1,Dial(Local/01-EDDI-119.570)<br />
;<br />
; EDDI BERLIN DIRECTOR 136.100 - Berlin Tempelhof<br />
exten => 01-EDDI-136.100,1,Macro(com)<br />
exten => 010403030813610,1,Dial(Local/01-EDDI-136.100)<br />
;<br />
; EDDI TWR 118.100 - Berlin Tempelhof<br />
exten => 01-EDDI-118.100,1,Macro(com)<br />
exten => 010403030811810,1,Dial(Local/01-EDDI-118.100)<br />
;<br />
; EDDI BERLIN DEP 119.500 - Berlin Tempelhof<br />
exten => 01-EDDI-119.500,1,Macro(com)<br />
exten => 010403030811950,1,Dial(Local/01-EDDI-119.500)<br />
;<br />
; EDDI BERLIN ARR 119.620 - Berlin Tempelhof<br />
exten => 01-EDDI-119.620,1,Macro(com)<br />
exten => 010403030811962,1,Dial(Local/01-EDDI-119.620)<br />
<br />
What does the above mean? There are two lines (three with the comment) for each frequency: The first one sets up an extension named "01-EDDI-119.500". Yes, for VoIP you can use textual extensions but be careful if you want to setup your Asterisk-Server with POTS (=Plain old telephone service). Therefor you need the second line which is the same as above but without dashes and the letters in the decimal representation of the ASCII Code. The second line does only a "rewrite" of the numerical representation to the textual one.<br />
<br />
For setting up all airports you can write your own simple script. But this maybe also not needed in further versions of FGCOM.<br />
<br />
After editing the extensions.conf file you have to reload the extensions file (e.g. "asterisk -rx extensions reload").<br />
<br />
You can add further nice goodies to your extensions.conf: MorseCode() for morsing the code of the VOR (MorseCode() will only work in Asterisk >= 1.4), Recording of metar data and playing this recording back when using the frequency of the metar information, ...<br />
<br />
===Setting up user accounts===<br />
<br />
The user accounts are located in the file iax.conf (and perhaps also in sip.conf, but this is not necessary). The top of the file should look like this:<br />
<br />
[general]<br />
bandwith=low<br />
disallow=lpc10<br />
jitterbuffer=yes<br />
forcejitterbuffer=no<br />
tos=lowdelay<br />
autokill=yes<br />
disallow=all<br />
allow=alaw<br />
allow=gsm<br />
allow=ilbc<br />
allow=g726<br />
allow=ulaw<br />
language=en<br />
maxauthreq=10<br />
context=guest<br />
;<br />
[guest]<br />
type=user<br />
username=guest<br />
context=guest<br />
qualify=yes<br />
callerid=Guest IAX User<br />
host=dynamic<br />
;<br />
<br />
You may want to disallow more codecs or want to allow additional codecs (such as speex). But have in mind that the internal mixing of the conferences are done in "ulaw". But "ulaw" needs about 80 kBit/s because it does no compression. So you have to think about what's better for you: less bandwidth (per user) and more CPU usage or more bandwidth (per user) and less CPU usage... you should also consider the "sound" of some codecs may not have the 'real radio sound'.<br />
<br />
For each user you have to add a bunch of lines to your iax.conf file:<br />
<br />
[<USERNAME>]<br />
type=user<br />
username=<USERNAME><br />
secret=<PASSWORD><br />
context=default<br />
host=dynamic<br />
nat=yes<br />
notransfer=yes<br />
<br />
You just have to fill in the <USERNAME> and <PASSWORD>. After each change you have to reload the configuration (e.g. "asterisk -rx reload chan_iax2.so"). Perhaps you want to write scripts for automatic configuration and so on. But be warned: Further versions of fgcom may use the multiplayer servers for getting usernames and position data and you have to change your scripts.<br />
<br />
===Problems?===<br />
<br />
If you have problems you can contact me via email at "dcoredump AT gmail.com".<br />
<br />
==External links==<br />
* [http://squonk.abacab.org/dokuwiki/fgcom Official website]<br />
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]<br />
<br />
==Development==<br />
<br />
TODO<br />
<br />
==See also==<br />
*[[FlightGear related projects]]<br />
<br />
[[Category:Software]]</div>TeXnicer