FlightGear wiki - User contributions [en]

User:D-SKY1

2012-07-19T13:09:29Z

D-SKY1: New location

{{User
|name = Mike
|location = Bacolod City, Philippines, SE Asia
|age = 43
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

'''Actual Project(s) / Work in progress'''
* Learning C++
* Learning OpenGL
* Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable
* Improving AI traffic
* adding AI traffic to less frequented areas of the earth
* building VTBD models from the scratch ([http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075 Forum thread about Suvarnabumi Int'l Airport, Bangkok, Thailand])

'''Already implemented contributions'''

''Aircraft''
[[File:A320-CEB.jpg|thumb|Airbus A320 in Cebu Pacific livery]]
[[File:731-PEX.jpg|thumb|Boeing 737-100 in People Express livery]]
* Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
* Some 3D modeling of the [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_January_2010#Boeing_737-100_updates 737-100 cockpit]
* Emirates Airlines livery for [[A380]] in AI aircrafts section (available via [[GIT]])
* New livery [http://liveries.flightgear.org/liveries.php?id=224 "Cebu Pacific Airlines"] for [http://www.flightgear.org/forums/viewtopic.php?f=4&t=9032 FlightGear Forum's A320], download from [http://gitorious.org/airbus-aircraft/a320/ git]
* AI aircraft A320-200 (redo of AI/Aircraft/A320) introducing a Gimp paintkit to create new liveries more easy
* Livery of "People Express" (PEX) for Boeing 737-100
 

''Scenery''
* Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
* Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
* [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 

''Misc''
* Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
* Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
* Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 

''My Future Plans''
* <del>AI traffic for RPLL</del> done and available via Terrasync
* More AI traffic enhancements in OMDB
* 3D models for OMDB
* Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
* Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
* My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 

Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask and be assured I don't feed trolls ;)

Building FlightGear - Debian

2011-08-18T08:07:51Z

D-SKY1: Revert changes due to issues between FGFs and OSG

HowTo build FlightGear 2.2.0 or bleeding edge development version, hereinafter simply called ''GIT'', on GNU/Linux Debian '''Stable''' 6.x (Squeeze) and '''Testing''' (Wheezy).

Even on Debian '''Oldstable''' 5.x (Lenny) this guide will work for both, 2.2.0 and GIT. At least until one or more dependencies of the GIT version are changing or beeing added.

The meaning of this article is to be a short, checklist like, overview of the specific steps to compile FlightGear and components on Debian. For more detailed information please refer to the main article [[Building_FlightGear_-_Linux | Building FlightGear on Linux]].

If you don't want to make your hands dirty, have a look at [[Scripted Compilation on Linux Debian/Ubuntu]].

== Requirements and Preparations ==
You need an OpenGL capable graphics including a proper installed driver supporting direct rendering. 

Also a bunch of packages (and some of their dependencies) are required:
* gcc, g++, make, automake, pkg-config
* mawk (or gawk)
* cmake (min. version 2.6.0-5)
* git, subversion, wget
* freeglut3-dev, libgl1-mesa-dev, libxrandr-dev
* libxi-dev, libxmu-dev, libxext-dev
* libopenal-dev (for Lenny see [[#libopenal|libopenal]]), libalut-dev
* libjpeg62-dev, libtiff4-dev, libpng12-dev
* libboost1.37-dev (min 1.37, 1.40 available for Lenny on backports.debian.org)

During installation packages ''simgear-dev'' and ''openscenegraph-dev'' '''must not''' be installed. They can safely be re-installed after compilation.

== Build and install ==
Because we are going to install versions different to the ones in the repositories it is recommended to install FG-2.2.0 and/or GIT in a place independent to the base system such as /usr/local/FG-2.2.0, /opt/FG-2.2.0 or in a subdirectory of your $HOME. I suggest to make it writeable by the user that there is no need to become root for the <code>make install</code> commands. I'll use <code>$prefix</code> as a placeholder for this directory. 
Another one will be <code>$srcdir</code>, it stands for the absolute path to the directory which is supposed to keep the folders of the various source codes. So, in the following instructions, you have to replace these with the local paths or even <code>export</code> them during the process.
export prefix=[path to install to]
export srcdir=[path to sources]

Have in mind that the data is a relatively large download (GIT about 3.5 GB and 2.2.0 300 MB). So, to save some time, it is a good idea to fetch it while building the sources.

For some basic info on git commands for FlightGear users we have a [[Git#For dummies|git for dummies]] section.

=== libopenal ===
Lenny only! The libopenal-dev package in Lenny is too old for [[fgcom]]. For FlightGear it does work but not all features (like doppler) are available, so installing an up to date version is recommended anyway.
cd $srcdir
wget http://kcat.strangesoft.net/openal-releases/openal-soft-1.11.753.tar.bz2
tar xjf openal-soft-1.11.753.tar.bz2
cd openal-soft-1.11.753/build
cmake -D CMAKE_INSTALL_PREFIX:PATH="$prefix" ..
make install

=== plib ===
Latest SVN is [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html recommended], yet package plib1.8.5-dev for Squeeze does work as well.
cd $srcdir
svn co https://plib.svn.sourceforge.net/svnroot/plib/trunk plib
cd plib
sed s/PLIB_TINY_VERSION\ \ 5/PLIB_TINY_VERSION\ \ 6/ -i src/util/ul.h
./autogen.sh
./configure --prefix=$prefix
make install

=== OpenSceneGraph ===

ln -s lib $prefix/lib64 # 64bit OS' only, if lib64 does not exist
cd $srcdir
svn co http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.10 OpenSceneGraph
mkdir osg-build && cd osg-build
cmake -D CMAKE_BUILD_TYPE="Release" \
-D CMAKE_INSTALL_PREFIX:PATH="$prefix" $srcdir/OpenSceneGraph
make install

=== SimGear ===
2.2.0 and GIT:
cd $srcdir
git clone git://gitorious.org/fg/simgear.git simgear
cd simgear

2.2.0 only:
git checkout -b releases/2.2.0 origin/releases/2.2.0

2.2.0 and GIT:
./autogen.sh
./configure --prefix=$prefix 
make install

=== FlightGear source ===
2.2.0 and GIT:
cd $srcdir
git clone git://gitorious.org/fg/flightgear.git flightgear
cd flightgear

2.2.0 only:
git checkout -b releases/2.2.0 origin/releases/2.2.0

2.2.0 and GIT:
./autogen.sh
./configure --prefix=$prefix 
make install

=== FlightGear data ===
2.2.0 only:
At the time of writing, 2.2.0 is not yet released, there is no tar archive for the data available. Test pilots for this release are advised to use the ''release/2.2.0'' branch from git. The following URL for wget will be updated, if it is not working, as soon as 2.2.0 is released.
cd $prefix
wget http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Shared/FlightGear-data-2.2.0.tar.bz2
tar xjf FlightGear-data-2.2.0.tar.bz2

GIT only:
For slow/unstable internet connections it is recommended to download the [[Git#fgdata.bundle|fgdata.bundle]] instead of cloning the data. 
FlightGear's primary git server on gitorious is known to have trouble cloning the data, the mapserver's mirror usually has no problems:
cd $prefix
git clone git://mapserver.flightgear.org/fgdata

== Trial run ==
When all the builds are done and the data download has finished it is time for a test run:
export LD_LIBRARY_PATH=$prefix/lib/:$LD_LIBRARY_PATH
$prefix/bin/fgfs --fg-root=$prefix/fgdata

For the future, if you want to start FlightGear from command line have a look at [[fgfsrc]], if you prefer a graphical user interface continue with [[#fgrun|compiling fgrun]] or check [[FGo!]]. Have in mind that <code>fgfs</code> need to find our self compiled libraries and therefore we have to tell the linker (ld) where to find them. That is what the first line here does.

== Optional Software ==
Feel free to add the commands to install other FlightGear related projects.

=== Atlas ===
cd $srcdir
cvs -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas login
#CVS passwd: [Enter]
cvs -z3 -d:pserver:anonymous@atlas.cvs.sourceforge.net:/cvsroot/atlas co Atlas
cd Atlas
sed s/get_gbs_center2/get_gbs_center/ -i src/Subbucket.cxx
./autogen.sh
./configure --prefix=$prefix
make install

=== fgcom ===
For [[fgcom]] unfortunately there is one more dependency which cannot be solved with packages on Lenny, see [[#libopenal|libopenal]].
cd $srcdir
svn co https://appfgcom.svn.sourceforge.net/svnroot/fgcom/trunk fgcom
cd fgcom/src
make INSTALL_BIN=$prefix/bin INSTALL_DIR=$prefix/fgcom \
PLIB_PREFIX=$prefix OPENAL_PREFIX=$prefix install

=== fgrun ===
To build [[fgrun]] one more package is required:
* libfltk1.1-dev
cd $srcdir
svn co http://fgrun.svn.sourceforge.net/svnroot/fgrun/trunk fgrun
cd fgrun/fgrun/
./autogen.sh
./configure --prefix=$prefix
make install

=== TaxiDraw ===
To compile [[Taxidraw|TaxiDraw]] we need to install some more packages:
* either libcurl4-gnutls-dev or libcurl4-openssl-dev for curl.h
* wx2.8-headers (at least, maybe even more than just that one. Please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!
su -c "aptitude install [libcurl4-gnutls-dev|libcurl4-openssl-dev]"
cd $srcdir
git clone git://mapserver.flightgear.org/taxidraw
cd taxidraw
./autogen.sh
./configure --prefix=$prefix
make install

=== TerraGear ===
To resolve some of the dependencies of [[TerraGear]] the GIT sections of steps [[#plib|plib]], [[#OpenSceneGraph|OpenSceneGraph]] and [[#SimGear|SimGear]] have to be done first. Additionally some packages and their dependencies have to be installed:
* libgdal1-dev, gdal-bin
* libproj-dev, libogdi3.2-dev (probably even more, please [http://wiki.flightgear.org/index.php?title=Talk:Building_FlightGear_-_Debian&action=edit&redlink=1 report]!)
Wheezy: As of June 2nd there is a bug ([http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617240 #617240]) in package libmysqlclient16 which causes compilation to fail. If it is not fixed by the time you're building TerraGear, upgrade to the version from Sid.

cd $srcdir
git clone git://mapserver.flightgear.org/terragear-cs

Two of the dependencies have to be installed manually (See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.gpc;h=226e185b1ce1d1578006b48bb426e35848cce93b;hb=HEAD README.gpc] and [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README.newmat;h=95570b6b279d3d00bd7664cd4f00d6c4802aed1b;hb=HEAD README.newmat] for details.):

# gpc install
mkdir $srcdir/gpc232 && cd $srcdir/gpc232
wget ftp://ftp.cs.man.ac.uk/pub/toby/gpc/gpc232-release.zip
unzip gpc232-release.zip
sed s/DBL_EPSILON/0.000001/ -i gpc.h
grep -A 18 '# Unix/Linux makefile' $srcdir/terragear-cs/README.gpc > Makefile
sed "s|/usr/local/lib|$prefix/lib|" -i Makefile
sed "s|/usr/local/include|$prefix/include|" -i Makefile
make install

# newmat install
mkdir $srcdir/newmat11 && cd $srcdir/newmat11
wget http://www.robertnz.net/ftp/newmat11.tar.gz
tar xzfv newmat11.tar.gz
make -f nm_gnu.mak
cp libnewmat.a $prefix/lib
mkdir $prefix/include/newmat
cp *.h $prefix/include/newmat

Finally TerraGear itself (See [http://mapserver.flightgear.org/git/?p=terragear-cs;a=blob;f=README;h=7dae654283ca0b1447aeb3aa398287219f4b57df;hb=HEAD README] for details.):
cd $srcdir/terragear-cs
./autogen.sh
./configure --prefix=$prefix
sed s/-O2// -i src/Lib/TriangleJRS/Makefile
make install

{{Building}}

[[de:FlightGear bauen - Debian]]

Template:POTW/2011-22

2011-05-28T11:04:46Z

D-SKY1: Created page with "{| class="prettytable" style="background-color:#efefef; width: 100%;" | align="center" |300px |- | align="left" | The '''737-100''' is a..."

{| class="prettytable" style="background-color:#efefef; width: 100%;"
| align="center" |[[Image:731-PEX.jpg|300px]]
|-
| align="left" | The '''[[Boeing_737-100|737-100]]''' is a short to mid-range, medium-size twin-engine narrow body aircraft manufactured by [[Boeing]] constructed in assistance of Germany's [[Lufthansa]]. The 737 is Boeing's most built aircraft. The model 737-100 was build 30 times between 1966 and 1969. Between 1981 and 1982 most of these 737-100's were sold to People Express Airlines.

<div style="text-align:right;">'''[[Boeing_737-100|Read more...]] | [[:Category:Picture of the week 2011|Archive]]'''</div>
|}

<noinclude>[[Category:Picture of the week 2011]]</noinclude>

User:D-SKY1

2011-05-18T14:40:55Z

D-SKY1: 737-100 livery People Express, screenshot Cebu Pacific livery

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 43
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

'''Actual Project(s) / Work in progress'''
* Learning C++
* Learning OpenGL
* Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable
* Improving AI traffic
* adding AI traffic to less frequented areas of the earth
* building VTBD models from the scratch ([http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075 Forum thread about Suvarnabumi Int'l Airport, Bangkok, Thailand])

'''Already implemented contributions'''

''Aircraft''
[[File:A320-CEB.jpg|thumb|Airbus A320 in Cebu Pacific livery]]
[[File:731-PEX.jpg|thumb|Boeing 737-100 in People Express livery]]
* Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
* Some 3D modeling of the [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_January_2010#Boeing_737-100_updates 737-100 cockpit]
* Emirates Airlines livery for [[A380]] in AI aircrafts section (available via [[GIT]])
* New livery [http://liveries.flightgear.org/liveries.php?id=224 "Cebu Pacific Airlines"] for [http://www.flightgear.org/forums/viewtopic.php?f=4&t=9032 FlightGear Forum's A320], download from [http://gitorious.org/airbus-aircraft/a320/ git]
* AI aircraft A320-200 (redo of AI/Aircraft/A320) introducing a Gimp paintkit to create new liveries more easy
* Livery of "People Express" (PEX) for Boeing 737-100
 

''Scenery''
* Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
* Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
* [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 

''Misc''
* Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
* Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
* Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 

''My Future Plans''
* <del>AI traffic for RPLL</del> done and available via Terrasync
* More AI traffic enhancements in OMDB
* 3D models for OMDB
* Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
* Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
* My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 

Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask and be assured I don't feed trolls ;)

File:A320-CEB.jpg

2011-05-18T13:52:16Z

D-SKY1: Airbus A320 with livery of Cebu Pacific Airlines

Airbus A320 with livery of Cebu Pacific Airlines

Boeing 737-100

2011-05-18T13:38:06Z

D-SKY1: Added available liveries

{{stub}}
{{non-stable}}

{{infobox Aircraft
|image =737-100_outside.jpg
|alt =737-100 in Lufthansa colors
|name =Boeing 737-100
|type =Airliner
|livery = Air FLorida, Air France, Alitalia, Aloha Airlines, America West Airlines, Boeing N73700, Canadian Airlines, Continental Airlines, Continental Airlines (old), Lufthansa (default), KLM, Kuwait Airways, NASA, Qatar Airways, Singapore Airlines, Swiss Air
|authors =Emmanuel Baranger
|fdm =YASim
|status =Alpha
|fgname =737-100
|download =
}}

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]

File:731-PEX.jpg

2011-05-18T13:30:49Z

D-SKY1: Boeing 737-100 with livery of "People Express" (PEX), a low-cost carrier who operated from 1981 to 1987 from Newark, New Jersey until they merged with Continental Airlines.

Boeing 737-100 with livery of "People Express" (PEX), a low-cost carrier who operated from 1981 to 1987 from Newark, New Jersey until they merged with Continental Airlines.

Airports under construction

2011-02-04T12:36:56Z

D-SKY1: /* Current Activities */ added link to forum discussion about airport VTBD

== Preface ==

=== 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? ===
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://www.flightgear.org/forums/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.

== Airports under construction ==
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).

=== Avaiability of new/changed airports needs some time ===
In FlightGear there is a common workflow to edit airports. First expierenced contributors have to change the airport data with "taxidraw". Then they submit the new data to the mapserver (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.

== Submit your work plans and schedule your activities ==
Please feel free to edit this page and submit your "pending airport" directly.

=== Current Activities ===

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! 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
|-
|EDWG||gral||x||||||2010-02-03||||
|-
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions
|-
|EDWL||gral||x||||||2010-02-03||||
|-
|EDWY||gral||x||||||2010-02-03||||
|-
|EEKE||henrikp||x||||||2010-10||||
|-
|EERU||henrikp||x||||||2010-10||||
|-
|EEKA||henrikp||x||||||2010-10||||
|-
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail
|-
|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
|-
|EHGG||Gijs||x||x||x||x||x|| || ||
|-
|EHAM||Gijs||x||x||x||x||x|| || ||
|-
|EHLE||Gijs||x||x||x||x||x|| || ||
|-
|EHVK||Gijs||x||x||x||x||x|| || ||
|-
|EHEH||Gijs||x||x||x||x||x|| || ||
|-
|EHKD||Gijs||x||x||x||x||x|| || ||
|-
|EHTX||Gijs||x||x||x||x||x|| || ||
|-
|EHAL||Gijs||x||x||x||x||x|| || ||
|-
|EHRD||Gijs||x||x||x||x||x|| || ||
|-
|EHLW||Gijs||x||x||x||x||x|| || ||
|-
|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...||
|-
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways
|-
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.
|-
|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
|-
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs
|-
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)
|-
|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
|-
|SBBG||Prestes||x||x|| ||2009-12-26 || ||
|-
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz
|-
|SBPK||Prestes||x||x|| ||2010-01-31 || ||
|-
|SBRG||Prestes||x||x|| ||2010-01-31 || ||
|-
|SUMU||Prestes||x||x|| ||2010-01-31 || ||
|-
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues
|-
|VTBD||D-SKY1||||x||x||2010-11-27 || ||[http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075 Work in progress]
|-
|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
|}

== Submit your wishes ==
If you wish to add an airport or think this or another airport needs a change '''[http://www.flightgear.org/forums/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.

== Links ==
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] 1)
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] 1)
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]
* [[Taxidraw|TaxiDraw Tutorial]]
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]

1) "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.

=== Other airport work related pages in the FlightGear wiki ===
* List of [[Developed Airports]] with buildings and [[Signs]] already included in the [[FlightGear Scenery Database]]
* [[Germany|Current work in Germany]]
* [[Current Scenery Projects]]
* [[FlightGear User Created Helipad List]]

User:D-SKY1

2011-02-04T12:35:07Z

D-SKY1: Links update

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 43
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

'''Actual Project(s) / Work in progress'''
* Learning C++
* Learning OpenGL
* Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable
* Improving AI traffic
* adding AI traffic to less frequented areas of the earth
* building VTBD models from the scratch ([http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075 Forum thread about Suvarnabumi Int'l Airport, Bangkok, Thailand])

'''Already implemented contributions'''

''Aircraft''
* Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
* Some 3D modeling of the [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_January_2010#Boeing_737-100_updates 737-100 cockpit]
* Emirates Airlines livery for [[A380]] in AI aircrafts section (available via [[GIT]])
* New livery [http://liveries.flightgear.org/liveries.php?id=224 "Cebu Pacific Airlines"] for [http://www.flightgear.org/forums/viewtopic.php?f=4&t=9032 FlightGear Forum's A320], download from [http://gitorious.org/airbus-aircraft/a320/ git]
* AI aircraft A320-200 (redo of AI/Aircraft/A320) introducing a Gimp paintkit to create new liveries more easy
 

''Scenery''
* Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
* Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
* [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 

''Misc''
* Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
* Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
* Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 

''My Future Plans''
* <del>AI traffic for RPLL</del> done and available via Terrasync
* More AI traffic enhancements in OMDB
* 3D models for OMDB
* Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
* Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
* My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 

Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask and be assured I don't feed trolls ;)

Airports under construction

2010-12-15T14:05:24Z

D-SKY1: Added VTBD work in progress

== Preface ==

=== 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? ===
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://www.flightgear.org/forums/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.

== Airports under construction ==
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).

=== Avaiability of new/changed airports needs some time ===
In FlightGear there is a common workflow to edit airports. First expierenced contributors have to change the airport data with "taxidraw". Then they submit the new data to the mapserver (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.

== Submit your work plans and schedule your activities ==
Please feel free to edit this page and submit your "pending airport" directly.

=== Current Activities ===

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! 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
|-
|EDWG||gral||x||||||2010-02-03||||
|-
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions
|-
|EDWL||gral||x||||||2010-02-03||||
|-
|EDWY||gral||x||||||2010-02-03||||
|-
|EEKE||henrikp||x||||||2010-10||||
|-
|EERU||henrikp||x||||||2010-10||||
|-
|EEKA||henrikp||x||||||2010-10||||
|-
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail
|-
|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
|-
|EHGG||Gijs||x||x||x||x||x|| || ||
|-
|EHAM||Gijs||x||x||x||x||x|| || ||
|-
|EHLE||Gijs||x||x||x||x||x|| || ||
|-
|EHVK||Gijs||x||x||x||x||x|| || ||
|-
|EHEH||Gijs||x||x||x||x||x|| || ||
|-
|EHKD||Gijs||x||x||x||x||x|| || ||
|-
|EHTX||Gijs||x||x||x||x||x|| || ||
|-
|EHAL||Gijs||x||x||x||x||x|| || ||
|-
|EHRD||Gijs||x||x||x||x||x|| || ||
|-
|EHLW||Gijs||x||x||x||x||x|| || ||
|-
|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...||
|-
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways
|-
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.
|-
|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
|-
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs
|-
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)
|-
|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
|-
|SBBG||Prestes||x||x|| ||2009-12-26 || ||
|-
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz
|-
|SBPK||Prestes||x||x|| ||2010-01-31 || ||
|-
|SBRG||Prestes||x||x|| ||2010-01-31 || ||
|-
|SUMU||Prestes||x||x|| ||2010-01-31 || ||
|-
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues
|-
|VTBD||D-SKY1||||x||x||2010-11-27 || ||Work in progress
|}

== Submit your wishes ==
If you wish to add an airport or think this or another airport needs a change '''[http://www.flightgear.org/forums/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.

== Links ==
* [http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] 1)
* [http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] 1)
* [http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear Git]
* [[Taxidraw|TaxiDraw Tutorial]]
* [http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]
* [http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]

1) "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.

=== Other airport work related pages in the FlightGear wiki ===
* [[Germany|Current work in Germany]]
* [[Current Scenery Projects]]
* [[FlightGear User Created Helipad List]]

User:D-SKY1

2010-12-05T13:17:56Z

D-SKY1: refresh

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 43
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

'''Actual Project(s) / Work in progress'''
* Learning C++
* Learning OpenGL
* Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable
* Improving AI traffic
* adding AI traffic to less frequented areas of the earth
* building VTBD models from the scratch (Suvarnabumi Int'l Airport, Bangkok, Thailand)

'''Already implemented contributions'''

''Aircraft''
* Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
* Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
* Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
* New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]
* AI aircraft A320-200 (redo of AI/Aircraft/A320) introducing a Gimp paintkit to create new liveries more easy
 

''Scenery''
* Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
* Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
* [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 

''Misc''
* Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
* Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
* Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 

''My Future Plans''
* <del>AI traffic for RPLL</del> done and available via Terrasync
* More AI traffic enhancements in OMDB
* 3D models for OMDB
* Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
* Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
* My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 

Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask and be assured I don't feed trolls ;)

Talk:FlightGear Newsletter November 2010

2010-11-15T07:55:25Z

D-SKY1: Created page with '@Danielkang1234 and TWIMC, I see a long lasting discussion in our maillist and in the forums about FPS. Ever now and then this topic gets more or less popular depending on how mu…'

@Danielkang1234 and TWIMC,
I see a long lasting discussion in our maillist and in the forums about FPS. Ever now and then this topic gets more or less popular depending on how much publicity this scam produces. I rest assured that your intentions are 100% pro-FGFS. But (there's always a "but") I'm unsure and ask myself, if this information should really go into our newsletter and therefore give the scammers more publicity than they deserve. Just my 2 cents...

[[User:D-SKY1|D-SKY1]] 07:55, 15 November 2010 (UTC)

FlightGear Newsletter November 2010

2010-11-15T00:59:26Z

D-SKY1: New Airport VTBD, AI traffic RPLL

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

== FlightGear events ==
== Call for volunteers ==
The [[OpenRadar]] project is looking for a new maintainer.

== Development news ==
Anders Gidenstam has continued to develop Walkview which opens up all sorts of exciting possibilites. Here is a short video of Walkview being used to give a different perspective on starting the Sopwith Camel [http://www.youtube.com/watch?v=KAQT2s7pFJs]. In addition to the rectangular plane that we have had for some time, we can now define the area in which we can "walk" as a line, polyline, or circle.

We use the new definitions in Multi Player Carrier Carl Vinson to move around the Goofer's deck while we are goofing, or to seek a more advantageous view from PriFly, or to inspect the Flight deck as the Flight Deck Officer [http://www.youtube.com/watch?v=h9MUT7GfzBs].

Meanwhile, in other news, Tim Moore has fixed the condition tag in the Material Animation. We can combine these two facilites to generate some more interesting views - [http://www.youtube.com/watch?v=1YmJN9o6TBc]. Alexis Bory has said that he will see if he can produce some more models with which to populate the hangar. Let's hope he finds something!

== Known problems ==
Though working perfectly for years, the "live weather" feature in FlightGear 1.9.x and 2.0 is now broken. Unfortunaltey, the FlightGear code of past releases contains minor problem which so far remained undetected and without effect. Since early November, probably caused by a server upgrade at the weather services, the FlightGear weather requests are now being rejected due to this problem. To revive live weather you have the following options:
* As a workaround, configure a proxy-server on the fgfs command-line. Relaying the request through a proxy solves the issue (see [http://www.flightgear.org/forums/viewtopic.php?t=10002 forum topic]).
* Experts being able to patch and recompile FlightGear may try to apply a patch (also see forum).
* Developers can use FlightGear's latest developer version from GIT, which already contains the required bugfix.
* Otherwise please stick with manual weather configuration and wait for the next FlightGear release (won't be too long).

== Nasal for newbies ==
== New software tools and projects ==

== FlightGear addons and mods ==
== In the hangar ==
=== New aircraft ===
=== Updated aircraft ===

===ZF Navy free balloon===
[[File:ZF_Navy_free_balloon-2.jpg|thumb|right|150px|The ZF Navy free balloon with the envelope shader enabled.]]

The [[ZF Navy free balloon]] has been updated with a custom shader effect that changes the shape of the balloon envelope according to its gas content.

=== Liveries ===

== Scenery corner ==
Jack Mermod has released the first of many NASA Interactive Launch Complexes. This first release is based on the [http://en.wikipedia.org/wiki/Mercury-Redstone_3 Launch Complex 5 and the Mercury Redstone 3 Launch.] [[File:mercuryredstone3.png|200px|thumb|right|Mercury Redstone 3 Rocket ready for launch.]] For now, you can download the scenery [http://alphashangar.co.nr/ here.] The model should be in terrasync soon.

=== Airports ===

== Aircraft of the month ==
== Airport of the month ==
Mike (aka D-Sky1) is busy again: This time he is working on VTBD (New Bangkok International Airport, Thailand) as the architecture of the airport buildings is very beautiful. It will sure take some time but a first glance at the work in progress is already possible. Discuss the progress with us in the forum: http://www.flightgear.org/forums/viewtopic.php?f=5&t=10075
After the airport is finished, placed and available, AI traffic will follow (mainly Thai Airways).
[[File:VTBD_wip01.jpg|thumb|right|150px|Bangkok Int'l Airport - work in progress.]]
 
AI traffic arrives at [[RPLL]] (Manila, Philippines): Mike created a comprehensive list of AI traffic of Cebu Pacific Airlines. Soon available via GIT, Cebu Pacific Airlines will provide domestic and international flights to the most important destinations. AI for the second big carrier of the Philippines (Philippine Airways) will follow later.

== Screenshot of the month ==

== Suggested flights ==
== Aircraft reviews ==

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

== Community news ==
=== FlightGear on youtube ===
=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===

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

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

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

=== Did you know ===

File:VTBD wip01.jpg

2010-11-15T00:40:39Z

D-SKY1: VTBD Bangkok Int'l Airport, Work in progress #01

VTBD Bangkok Int'l Airport, Work in progress #01

Airports under construction

2010-11-13T22:13:29Z

D-SKY1: /* Current Activities */ reflecting changes at RPLL

== Preface ==

=== 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? ===
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://www.flightgear.org/forums/viewforum.php?f=5 Scenery Enhancement]) to discuss some issues.

== Airports under construction ==
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).

=== Avaiability of new/changed airports needs some time ===
In FlightGear there is a common workflow to edit airports. First expierenced contributors have to change the airport data with "taxidraw". Then they submit the new data to the mapserver (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.

== Submit your work plans and schedule your activities ==
Please feel free to edit this page and submit your "pending airport" directly.

=== Current Activities ===

{| class="wikitable sortable" border="0" cellpadding="4" cellspacing="0"
|-
! 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
|-
|EDWG||gral||x||||||2010-02-03||||
|-
|EDWJ||gral||x||||||2010-02-01||2010-02-03||taxiway, runways, positions
|-
|EDWL||gral||x||||||2010-02-03||||
|-
|EDWY||gral||x||||||2010-02-03||||
|-
|EEKE||henrikp||x||||||2010-10||||
|-
|EERU||henrikp||x||||||2010-10||||
|-
|EEKA||henrikp||x||||||2010-10||||
|-
|EGGD||karla||||x||x||2009-07-12||2010-12-02||customized buildings, stock buildings, stock models and vehicles, high detail
|-
|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 CVS/Git
|-
|EHGG||Gijs||x||x||x||x||x|| || ||
|-
|EHAM||Gijs||x||x||x||x||x|| || ||
|-
|EHLE||Gijs||x||x||x||x||x|| || ||
|-
|EHVK||Gijs||x||x||x||x||x|| || ||
|-
|EHEH||Gijs||x||x||x||x||x|| || ||
|-
|EHKD||Gijs||x||x||x||x||x|| || ||
|-
|EHTX||Gijs||x||x||x||x||x|| || ||
|-
|EHAL||Gijs||x||x||x||x||x|| || ||
|-
|EHRD||Gijs||x||x||x||x||x|| || ||
|-
|EHLW||Gijs||x||x||x||x||x|| || ||
|-
|KDMA||gral||x|||| ||2010-02-10||2010-02-10||runways, taxiways
|-
|KHND||Armchair Ace|| ||x|| || || ||Hangars and static aircraft added. Terminal still needed.
|-
|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 CVS/Git
|-
|LSMA||gral||x||||||2010-04-12||2010-04-12||runways, taxiways, tower position, atc freqs
|-
|OMDB||D-SKY1||||||x||2010-06-25||||added AI traffic (UAE)
|-
|RPLL||D-SKY1||||x||x||2009-12-03||2010-02-11||Terminals 1, 2 and 3, Tower, AI groundnetwork, AI traffic, ATC freqs added. Still needed: redo of taxi- and runways
|-
|SBBG||Prestes||x||x|| ||2009-12-26 || ||
|-
|SBPA||Prestes||x||x|| ||2009-12-28 || ||Airport objects by George Luiz
|-
|SBPK||Prestes||x||x|| ||2010-01-31 || ||
|-
|SBRG||Prestes||x||x|| ||2010-01-31 || ||
|-
|SUMU||Prestes||x||x|| ||2010-01-31 || ||
|-
|UEST||gral||x|||| ||2010-01-10||2010-01-12||fixed taxiways and some minor issues
|}

== Submit your wishes ==
If you wish to add an airport or think this or another airport needs a change '''[http://www.flightgear.org/forums/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.

== Links ==
*[http://mapserver.flightgear.org/Apt.Dat.txt List of updated airports in apt.dat mapserver] 1)
*[http://mapserver.flightgear.org/apt.dat.gz Updated apt.dat.gz mapserver] 1)
*[http://cvs.flightgear.org/viewvc/data/Airports/apt.dat.gz?view=log Log of apt.dat.gz in FlightGear CVS]
*[[Taxidraw|TaxiDraw Tutorial]]
*[http://taxidraw.sourceforge.net/taxidraw/tutorial.html Another (outdated) Tutorial for TaxiDraw]
*[http://taxidraw.sourceforge.net/#download TaxiDraw download - includes also working binaries (i.e. for OSX)]

1) "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 CVS server.

=== Other airport work related pages in the FlightGear wiki ===
*[[Germany|Current work in Germany]]
*[[Current Scenery Projects]]
*[[FlightGear User Created Helipad List]]

User:D-SKY1

2010-10-08T08:25:22Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 43
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

* '''Actual Project(s) / Work in progress'''
** Learning OpenGL
** Learning C++
** Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable
** Improving AI traffic
** adding AI traffic to less frequented areas of the earth

Already implemented contributions:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]
 
* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 
* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
** Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 
* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 
Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask ;)

User:D-SKY1

2010-10-08T08:25:01Z

D-SKY1: improving AI traffic

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

* '''Actual Project(s) / Work in progress'''
** Learning OpenGL
** Learning C++
** Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable
** Improving AI traffic
** adding AI traffic to less frequented areas of the earth

Already implemented contributions:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]
 
* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 
* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
** Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 
* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 
Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask ;)

File:Trafficdata2.tar.gz

2010-10-04T18:13:15Z

D-SKY1: Modified perl script by Mike N. - changed scalar value from "@_" to "$_" because @_[n] is a slice of an array containing a single element which may lead to hard to find errors - changed "$tokens" to "$token" (without trailing 's') as we deal with a single

Modified perl script by Mike N.
- changed scalar value from "@_" to "$_" because @_[n] is a slice of an array containing a single element which may lead to hard to find errors
- changed "$tokens" to "$token" (without trailing 's') as we deal with a single token
- added verification of input ($token[3] = weekdays) with some informative output in case of error
- added the ability to use 'DAILY' as weekday to get <repeat>24Hrs</repeat> in flights section
- more informative output in case of wrong syntax

File:AI a320 ceb.png

2010-09-26T18:07:41Z

D-SKY1: Airbus A320 livery 'Cebu Pacific Airlines' for AI aircraft

Airbus A320 livery 'Cebu Pacific Airlines' for AI aircraft

User:D-SKY1

2010-09-02T17:34:53Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

* '''Actual Project(s) / Work in progress'''
** Learning OpenGL
** Learning C++
** Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers and to be more stable

Already implemented contributions:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]
 
* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 
* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
** Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 
* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 
Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask ;)

FlightGear glass cockpit

2010-08-20T20:25:29Z

D-SKY1: /* Compiling the sources */ some changes regarding minor issues

== The Flight Gear Glass Cockpit Project ==

I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.
The source is largely a dusted-off version of OpenGC by Damion Shelton.
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.

== Where the project stands ==

So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].

Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]
=== News ===
*FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]
*The garbage data segfault mentioned in issues earlier has been found and hardened against.
*The heading indicator now correctly shows major headings by name
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much...
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:
Any code of your own that you haven't looked at for six or more
months, might as well have been written by someone else. (Eagleson
is an optimist, the real number is more like three weeks.)</pre></blockquote>
:: -- From the fortunes database
*A SourceForge project has been created
*Resolved the remaining issues with the heading indicator

== Issues ==
*Due to many uninitialized variables starting up OpenGC is sometimes leading to a crash. If this happens just try again... and again... and again... suddenly it will fire up. Although there's no guaranteed stability.
*Network socket is not starting up every time. If you are faced to "Error writing data" in FG console you can be quite sure either to set the wrong parameters or the before mentioned network socket is not available. By the way: did you check your firewall to pass UDP 5800 packets?
*Just a few gauges are available: Boeing777PFD,NavTestGauge, Keypad,EGyroAltimeterSetting
*Adding own gauges demands knowledge in programming C++ and recompiling the source

== Roadmap ==

=== Near Term Goals ===
*Get a CVS resource online
*Improve code hardening to prevent ugly bailouts in FTGL and others
*Get the input processor to correctly convert elevation to barometric altitude
*Implement a command line parser to get rid of statically implemented arguments

=== Mid Term Goals ===
*Move the configuration to XML to match FG configuration
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)
*Clean up and modernize the codebase
*Further harden the code against garbage data
*Improve codebase documentation
*Create a proper API documentation

=== Long Term Goals ===
*Create a working set of generic gauges
*Implement an XML gauge constructor to get away from having to code gauges in C++
*Integrate the code closer with fg
*Remove the necessity to share code between FGGC and FG
*Turn the codebase into a real library
*Improve the input parsing code
*Implement an upstream network interface to send input back to FG

== Requirements ==
OpenGC 0.3-alpha3 has only been tested on LINUX operating system (Ubuntu 10.04). LINUX systems must have GCC version 4.0.0-8 or later, and graphics card with OpenGL support. Before unpacking and making the modified version of OpenGC there are five open source programs that must be installed on your computer:

*CMake 2.0+ program used to generate the makefiles that build the OpenGC executable, download from http://www.cmake.org/HTML/Index.html
*FLTK 1.5 includes libraries that are required to build the render windows, download from http://www.fltk.org/
*Freetype 2.19 has important include files that are needed for FTGL to work, download from http://www.freetype.org/
*FTGL 2.0.11 includes libraries and headers that are required for fonts used in OpenGC, download from http://homepages.paradise.net.nz/henryj/code/#FTGL
*Plib 1.6 important math and graphics libraries are included, download from http://plib.sourceforge.net/
 
On Ubuntu:
sudo aptitude install cmake libfltk1.1-dev libfreetype6-dev libftgl-dev libplib-dev
 
The specifics of each package is available at http://www.opengc.org/developers_building.html. Newer versions of each file have been tested, and there seems to be no backward compatibility issues, but the files above have been proven to work. Installing these programs is the most important part of having a working program. After SUCCESSFUL INSTALLATION of the programs follow the step by step guide to setup OpenGC on your system.

== Getting the Source ==
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc

== Compiling the sources on Linux==
# Unpack the compressed file to a convenient location
# Edit /path/to/your/fggc/source/FindPlib.cmake and modify line 26:
#:<pre>FIND_LIBRARY(Plib_SL_LIBRARY NAMES sl plibsl</pre>
#: the difference is the last word in this line. Before you edit it it says "plib sl". Remove the space.
# In terminal go to directory .../OpenGC/Applications/FLTKApp
## Create the file "opengc.ini"
## Edit opengc.ini and set the font and navigation path to the location of the Font and Navigation folders within the OpenGC file:
#:<pre>
#:NAV DATABASE PATH
#:/path/to/your/install/fggc/navdata/
#:FONT PATH
#:/path/to/OpenGC/Fonts/</pre>
# Switch back to .../OpenGC/ and enter the command ccmake CMakeLists.txt (alternatively CMake comes with gui as "cmake-gui" or "cmake-qt-gui", depending on your linux distribution)
## Locate the directories marked with DIR_NOT_FOUND, these are usually Freetype, Plib, and FTGL
## Scan the /usr/ directory for the libraries and include directories of the files. If you cannot locate them, compare the directories in the file packages with what you have in your /usr/... directory
## FLTK directory should be configured manually to "/usr/include/FL"; Plib and FTGL should be modified to work correctly with insertion of "/usr/include/Plib" and "/usr/include/FTGL".
## If you have linked these include directories or libraries, change directories back to the package you are having trouble with and type "make -install" again. To make it easier to find the package you may want to set the build location to a familiar spot. For help doing this type "man make" inside terminal
# Once all the directories are set hit the 'c' key to configure the file, then the 'g' key to generate the makefiles
# Run "make" to build the OpenGC libraries and executable to the location specified in the ccmake script
# If you want to see a preview of the OpenGC application change directories to the .../OpenGC/Applications/FLTKApp and type "./OpenGC opengc.ini" after a list of instructions and a short loading period you should see the display running through a previous flight test.
# Creating your own data source and collecting data in real time requires a bit more work. Start off by opening the Documentation Folder from the OpenGC directory, in that file there is a ReadMe on DataSource Creation that covers how to work with telemetry data from general sources.
# To switch to the DataSource that is compatible with the current Data Packets being sent down from the UAV or airframe platform go to opengc.ini and switch the DATASOURCE field to EGyro.

Notice that this requires valid data being sent in via the serial port. To get this valid data requires the Autopilot program be loaded onto a processor that is actively transmitting data. In the directory /FLTKApp/ call "./OpenGC opengc.ini: and the cockpit display should appear. After completing your test data should be logged in the /FLTKApp/datalog directory under the name telemetry.txt.

== Attaching to FlightGear ==
Start FlightGear with your favorite options and the following to your commandline:
--opengc=socket,out,24,aa.bb.cc.dd,5800,udp
*"opengc" describes what data is sent out
*"socket" tells FG how to present the data (here: as network socket)
*"24" = update frequency in Hz; do not change, it's hard coded inside OpenGC
*"aa.bb.cc.dd." = IP address where to send data to; use 127.0.0.1 if you intend to use OpenGC on the local pc
*"5800" describes the used port; don't change, it's also hardcoded within OpenGC
*"udp" is the used network protocol; also hard coded; don't change

== Contributing ==
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.

== Contact ==
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer

== Links ==
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]

[[Category:Glass Cockpit related]]

FlightGear glass cockpit

2010-08-20T19:55:05Z

D-SKY1: /* Requirements */ edit aptitude line

== The Flight Gear Glass Cockpit Project ==

I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.
The source is largely a dusted-off version of OpenGC by Damion Shelton.
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.

== Where the project stands ==

So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].

Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]
=== News ===
*FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]
*The garbage data segfault mentioned in issues earlier has been found and hardened against.
*The heading indicator now correctly shows major headings by name
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much...
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:
Any code of your own that you haven't looked at for six or more
months, might as well have been written by someone else. (Eagleson
is an optimist, the real number is more like three weeks.)</pre></blockquote>
:: -- From the fortunes database
*A SourceForge project has been created
*Resolved the remaining issues with the heading indicator

== Issues ==
*Due to many uninitialized variables starting up OpenGC is sometimes leading to a crash. If this happens just try again... and again... and again... suddenly it will fire up. Although there's no guaranteed stability.
*Network socket is not starting up every time. If you are faced to "Error writing data" in FG console you can be quite sure either to set the wrong parameters or the before mentioned network socket is not available. By the way: did you check your firewall to pass UDP 5800 packets?
*Just a few gauges are available: Boeing777PFD,NavTestGauge, Keypad,EGyroAltimeterSetting
*Adding own gauges demands knowledge in programming C++ and recompiling the source

== Roadmap ==

=== Near Term Goals ===
*Get a CVS resource online
*Improve code hardening to prevent ugly bailouts in FTGL and others
*Get the input processor to correctly convert elevation to barometric altitude
*Implement a command line parser to get rid of statically implemented arguments

=== Mid Term Goals ===
*Move the configuration to XML to match FG configuration
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)
*Clean up and modernize the codebase
*Further harden the code against garbage data
*Improve codebase documentation
*Create a proper API documentation

=== Long Term Goals ===
*Create a working set of generic gauges
*Implement an XML gauge constructor to get away from having to code gauges in C++
*Integrate the code closer with fg
*Remove the necessity to share code between FGGC and FG
*Turn the codebase into a real library
*Improve the input parsing code
*Implement an upstream network interface to send input back to FG

== Requirements ==
OpenGC 0.3-alpha3 has only been tested on LINUX operating system (Ubuntu 10.04). LINUX systems must have GCC version 4.0.0-8 or later, and graphics card with OpenGL support. Before unpacking and making the modified version of OpenGC there are five open source programs that must be installed on your computer:

*CMake 2.0+ program used to generate the makefiles that build the OpenGC executable, download from http://www.cmake.org/HTML/Index.html
*FLTK 1.5 includes libraries that are required to build the render windows, download from http://www.fltk.org/
*Freetype 2.19 has important include files that are needed for FTGL to work, download from http://www.freetype.org/
*FTGL 2.0.11 includes libraries and headers that are required for fonts used in OpenGC, download from http://homepages.paradise.net.nz/henryj/code/#FTGL
*Plib 1.6 important math and graphics libraries are included, download from http://plib.sourceforge.net/
 
On Ubuntu:
sudo aptitude install cmake libfltk1.1-dev libfreetype6-dev libftgl-dev libplib-dev
 
The specifics of each package is available at http://www.opengc.org/developers_building.html. Newer versions of each file have been tested, and there seems to be no backward compatibility issues, but the files above have been proven to work. Installing these programs is the most important part of having a working program. After SUCCESSFUL INSTALLATION of the programs follow the step by step guide to setup OpenGC on your system.

== Getting the Source ==
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc

== Compiling the sources ==
# Unpack the compressed file to a convenient location
# In terminal go to directory .../OpenGC/Applications/FLTKApp
## Create the file "opengc.ini"
## Edit opengc.ini and set the font and navigation path to the location of the Font and Navigation folders within the OpenGC file:
NAV DATABASE PATH
/path/to/your/install/fggc/navdata/
FONT PATH
/path/to/OpenGC/Fonts/
# Switch back to .../OpenGC/ and enter the command ccmake CMakeLists.txt (alternatively CMake comes with gui as "cmake-qt-gui")
## Locate the directories marked with DIR_NOT_FOUND, these are usually Freetype, Plib, and FTGL
## Scan the /usr/ directory for the libraries and include directories of the files. If you cannot locate them, compare the directories in the file packages with what you have in your /usr/... directory
## FLTK directory should be configured manually to "/usr/include/FL"; Plib and FTGL should be modified to work correctly with insertion of "/usr/include/Plib" and "/usr/include/FTGL".
## If you have linked these include directories or libraries, change directories back to the package you are having trouble with and type "make -install" again. To make it easier to find the package you may want to set the build location to a familiar spot. For help doing this type "man make" inside terminal
# Once all the directories are set hit the 'c' key to configure the file, then the 'g' key to generate the makefiles
# Run "make" to build the OpenGC libraries and executable to the location specified in the ccmake script
# If you want to see a preview of the OpenGC application change directories to the .../OpenGC/Applications/FLTKApp and type "./OpenGC opengc.ini" after a list of instructions and a short loading period you should see the display running through a previous flight test.
# Creating your own data source and collecting data in real time requires a bit more work. Start off by opening the Documentation Folder from the OpenGC directory, in that file there is a ReadMe on DataSource Creation that covers how to work with telemetry data from general sources.
# To switch to the DataSource that is compatible with the current Data Packets being sent down from the UAV or airframe platform go to opengc.ini and switch the DATASOURCE field to EGyro.

Notice that this requires valid data being sent in via the serial port. To get this valid data requires the Autopilot program be loaded onto a processor that is actively transmitting data. In the directory /FLTKApp/ call "./OpenGC opengc.ini: and the cockpit display should appear. After completing your test data should be logged in the /FLTKApp/datalog directory under the name telemetry.txt.

== Attaching to FlightGear ==
Start FlightGear with your favorite options and the following to your commandline:
--opengc=socket,out,24,aa.bb.cc.dd,5800,udp
*"opengc" describes what data is sent out
*"socket" tells FG how to present the data (here: as network socket)
*"24" = update frequency in Hz; do not change, it's hard coded inside OpenGC
*"aa.bb.cc.dd." = IP address where to send data to; use 127.0.0.1 if you intend to use OpenGC on the local pc
*"5800" describes the used port; don't change, it's also hardcoded within OpenGC
*"udp" is the used network protocol; also hard coded; don't change

== Contributing ==
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.

== Contact ==
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer

== Links ==
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]

[[Category:Glass Cockpit related]]

User:D-SKY1

2010-08-15T11:34:35Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

* '''Actual Project(s) / Work in progress'''
** Learning C++
** Using the new learned skills to improve and modify [[Flight Gear Glass Cockpit]] to be more convenient for non-developers

Already implemented contributions:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]
 
* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 
* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
** Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 
* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 
Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask ;)

FlightGear glass cockpit

2010-08-11T19:38:49Z

D-SKY1: Added "Issues", "Attaching to FlightGear"

== The Flight Gear Glass Cockpit Project ==

I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.
The source is largely a dusted-off version of OpenGC by Damion Shelton.
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.

== Where the project stands ==

So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].

Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]
=== News ===
*FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]
*The garbage data segfault mentioned in issues earlier has been found and hardened against.
*The heading indicator now correctly shows major headings by name
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much...
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:
Any code of your own that you haven't looked at for six or more
months, might as well have been written by someone else. (Eagleson
is an optimist, the real number is more like three weeks.)</pre></blockquote>
:: -- From the fortunes database
*A SourceForge project has been created
*Resolved the remaining issues with the heading indicator

== Issues ==
*Due to many uninitialized variables starting up OpenGC is sometimes leading to a crash. If this happens just try again... and again... and again... suddenly it will fire up. Although there's no guaranteed stability.
*Network socket is not starting up every time. If you are faced to "Error writing data" in FG console you can be quite sure either to set the wrong parameters or the before mentioned network socket is not available. By the way: did you check your firewall to pass UDP 5800 packets?
*Just a few gauges are available: Boeing777PFD,NavTestGauge, Keypad,EGyroAltimeterSetting
*Adding own gauges demands knowledge in programming C++ and recompiling the source

== Roadmap ==

=== Near Term Goals ===
*Get a CVS resource online
*Improve code hardening to prevent ugly bailouts in FTGL and others
*Get the input processor to correctly convert elevation to barometric altitude
*Implement a command line parser to get rid of statically implemented arguments

=== Mid Term Goals ===
*Move the configuration to XML to match FG configuration
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)
*Clean up and modernize the codebase
*Further harden the code against garbage data
*Improve codebase documentation
*Create a proper API documentation

=== Long Term Goals ===
*Create a working set of generic gauges
*Implement an XML gauge constructor to get away from having to code gauges in C++
*Integrate the code closer with fg
*Remove the necessity to share code between FGGC and FG
*Turn the codebase into a real library
*Improve the input parsing code
*Implement an upstream network interface to send input back to FG

== Requirements ==
OpenGC 0.3-alpha3 has only been tested on LINUX operating system (Ubuntu 10.04). LINUX systems must have GCC version 4.0.0-8 or later, and graphics card with OpenGL support. Before unpacking and making the modified version of OpenGC there are five open source programs that must be installed on your computer:

*CMake 2.0+ program used to generate the makefiles that build the OpenGC executable, download from http://www.cmake.org/HTML/Index.html
*FLTK 1.5 includes libraries that are required to build the render windows, download from http://www.fltk.org/
*Freetype 2.19 has important include files that are needed for FTGL to work, download from http://www.freetype.org/
*FTGL 2.0.11 includes libraries and headers that are required for fonts used in OpenGC, download from http://homepages.paradise.net.nz/henryj/code/#FTGL
*Plib 1.6 important math and graphics libraries are included, download from http://plib.sourceforge.net/
 
On Ubuntu:
sudo aptitude install cmake libfltk1.1-dev libfreetype6-dev libftgl-dev libplib-dev ftgl-dev
 
The specifics of each package is available at http://www.opengc.org/developers_building.html. Newer versions of each file have been tested, and there seems to be no backward compatibility issues, but the files above have been proven to work. Installing these programs is the most important part of having a working program. After SUCCESSFUL INSTALLATION of the programs follow the step by step guide to setup OpenGC on your system.

== Getting the Source ==
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc

== Compiling the sources ==
# Unpack the compressed file to a convenient location
# In terminal go to directory .../OpenGC/Applications/FLTKApp
## Create the file "opengc.ini"
## Edit opengc.ini and set the font and navigation path to the location of the Font and Navigation folders within the OpenGC file:
NAV DATABASE PATH
/path/to/your/install/fggc/navdata/
FONT PATH
/path/to/OpenGC/Fonts/
# Switch back to .../OpenGC/ and enter the command ccmake CMakeLists.txt (alternatively CMake comes with gui as "cmake-qt-gui")
## Locate the directories marked with DIR_NOT_FOUND, these are usually Freetype, Plib, and FTGL
## Scan the /usr/ directory for the libraries and include directories of the files. If you cannot locate them, compare the directories in the file packages with what you have in your /usr/... directory
## FLTK directory should be configured manually to "/usr/include/FL"; Plib and FTGL should be modified to work correctly with insertion of "/usr/include/Plib" and "/usr/include/FTGL".
## If you have linked these include directories or libraries, change directories back to the package you are having trouble with and type "make -install" again. To make it easier to find the package you may want to set the build location to a familiar spot. For help doing this type "man make" inside terminal
# Once all the directories are set hit the 'c' key to configure the file, then the 'g' key to generate the makefiles
# Run "make" to build the OpenGC libraries and executable to the location specified in the ccmake script
# If you want to see a preview of the OpenGC application change directories to the .../OpenGC/Applications/FLTKApp and type "./OpenGC opengc.ini" after a list of instructions and a short loading period you should see the display running through a previous flight test.
# Creating your own data source and collecting data in real time requires a bit more work. Start off by opening the Documentation Folder from the OpenGC directory, in that file there is a ReadMe on DataSource Creation that covers how to work with telemetry data from general sources.
# To switch to the DataSource that is compatible with the current Data Packets being sent down from the UAV or airframe platform go to opengc.ini and switch the DATASOURCE field to EGyro.

Notice that this requires valid data being sent in via the serial port. To get this valid data requires the Autopilot program be loaded onto a processor that is actively transmitting data. In the directory /FLTKApp/ call "./OpenGC opengc.ini: and the cockpit display should appear. After completing your test data should be logged in the /FLTKApp/datalog directory under the name telemetry.txt.

== Attaching to FlightGear ==
Start FlightGear with your favorite options and the following to your commandline:
--opengc=socket,out,24,aa.bb.cc.dd,5800,udp
*"opengc" describes what data is sent out
*"socket" tells FG how to present the data (here: as network socket)
*"24" = update frequency in Hz; do not change, it's hard coded inside OpenGC
*"aa.bb.cc.dd." = IP address where to send data to; use 127.0.0.1 if you intend to use OpenGC on the local pc
*"5800" describes the used port; don't change, it's also hardcoded within OpenGC
*"udp" is the used network protocol; also hard coded; don't change

== Contributing ==
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.

== Contact ==
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer

== Links ==
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]

[[Category:Glass Cockpit related]]

FlightGear glass cockpit

2010-08-11T15:03:51Z

D-SKY1: Added "Requirements" and "Compiling"

== The Flight Gear Glass Cockpit Project ==

I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.
The source is largely a dusted-off version of OpenGC by Damion Shelton.
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.

== Where the project stands ==

So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].

Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]
=== News ===
*FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]
*The garbage data segfault mentioned in issues earlier has been found and hardened against.
*The heading indicator now correctly shows major headings by name
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much...
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:
Any code of your own that you haven't looked at for six or more
months, might as well have been written by someone else. (Eagleson
is an optimist, the real number is more like three weeks.)</pre></blockquote>
:: -- From the fortunes database
*A SourceForge project has been created
*Resolved the remaining issues with the heading indicator

== Issues ==
Currently there are no known issues

== Roadmap ==

=== Near Term Goals ===
*Get a CVS resource online
*Improve code hardening to prevent ugly bailouts in FTGL and others
*Get the input processor to correctly convert elevation to barometric altitude
*Implement a command line parser to get rid of statically implemented arguments

=== Mid Term Goals ===
*Move the configuration to XML to match FG configuration
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)
*Clean up and modernize the codebase
*Further harden the code against garbage data
*Improve codebase documentation
*Create a proper API documentation

=== Long Term Goals ===
*Create a working set of generic gauges
*Implement an XML gauge constructor to get away from having to code gauges in C++
*Integrate the code closer with fg
*Remove the necessity to share code between FGGC and FG
*Turn the codebase into a real library
*Improve the input parsing code
*Implement an upstream network interface to send input back to FG

== Requirements ==
OpenGC 0.3-alpha3 has only been tested on LINUX operating system (Ubuntu 10.04). LINUX systems must have GCC version 4.0.0-8 or later, and graphics card with OpenGL support. Before unpacking and making the modified version of OpenGC there are five open source programs that must be installed on your computer:

* CMake 2.0+ program used to generate the makefiles that build the OpenGC executable, download from http://www.cmake.org/HTML/Index.html
* FLTK 1.5 includes libraries that are required to build the render windows, download from http://www.fltk.org/
* Freetype 2.19 has important include files that are needed for FTGL to work, download from http://www.freetype.org/
* FTGL 2.0.11 includes libraries and headers that are required for fonts used in OpenGC, download from http://homepages.paradise.net.nz/henryj/code/#FTGL
* Plib 1.6 important math and graphics libraries are included, download from http://plib.sourceforge.net/
 
On Ubuntu:
sudo aptitude install cmake libfltk1.1-dev libfreetype6-dev libftgl-dev libplib-dev
 
The specifics of each package is available at http://www.opengc.org/developers_building.html. Newer versions of each file have been tested, and there seems to be no backward compatibility issues, but the files above have been proven to work. Installing these programs is the most important part of having a working program. After SUCCESSFUL INSTALLATION of the programs follow the step by step guide to setup OpenGC on your system.

== Getting the Source ==
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc

== Compiling the sources ==
# Unpack the compressed file to a convenient location
# In terminal go to directory .../OpenGC/Applications/FLTKApp
## Create the file "opengc.ini"
## Edit opengc.ini and set the font and navigation path to the location of the Font and Navigation folders within the OpenGC file:
NAV DATABASE PATH
/path/to/your/install/fggc/navdata/
FONT PATH
/path/to/OpenGC/Fonts/
# Switch back to .../OpenGC/ and enter the command ccmake CMakeLists.txt (alternatively CMake comes with gui as "cmake-qt-gui")
## Locate the directories marked with DIR_NOT_FOUND, these are usually Freetype, Plib, and FTGL
## Scan the /usr/ directory for the libraries and include directories of the files. If you cannot locate them, compare the directories in the file packages with what you have in your /usr/... directory
## FLTK directory should be configured manually to "/usr/include/FL"; Plib and FTGL should be modified to work correctly with insertion of "/usr/include/Plib" and "/usr/include/FTGL".
## If you have linked these include directories or libraries, change directories back to the package you are having trouble with and type "make -install" again. To make it easier to find the package you may want to set the build location to a familiar spot. For help doing this type "man make" inside terminal
# Once all the directories are set hit the 'c' key to configure the file, then the 'g' key to generate the makefiles
# Run "make" to build the OpenGC libraries and executable to the location specified in the ccmake script
# If you want to see a preview of the OpenGC application change directories to the .../OpenGC/Applications/FLTKApp and type "./OpenGC opengc.ini" after a list of instructions and a short loading period you should see the display running through a previous flight test.
# Creating your own data source and collecting data in real time requires a bit more work. Start off by opening the Documentation Folder from the OpenGC directory, in that file there is a ReadMe on DataSource Creation that covers how to work with telemetry data from general sources.
# To switch to the DataSource that is compatible with the current Data Packets being sent down from the UAV or airframe platform go to opengc.ini and switch the DATASOURCE field to EGyro.

Notice that this requires valid data being sent in via the serial port. To get this valid data requires the Autopilot program be loaded onto a processor that is actively transmitting data. In the directory /FLTKApp/ call "./OpenGC opengc.ini: and the cockpit display should appear. After completing your test data should be logged in the /FLTKApp/datalog directory under the name telemetry.txt.

== Contributing ==
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.

== Contact ==
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer

== Links ==
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]

[[Category:Glass Cockpit related]]

Howto:Install aircraft

2010-08-11T07:46:37Z

D-SKY1: /* Windows */ Regarding user rights on c:\program files

{{installing}}
Official [[aircraft]] can be downloaded at [http://www.flightgear.org/Downloads/aircraft/ FlightGear.org Aircraft], which then usually require unzipping software to extract from a compressed file format. Then these must be manually installed in a FlightGear software installation to use. The details depend on the method of download, operating system, and user setup.

An open source file archiver is [http://www.7-zip.org/ 7-Zip], although be aware of user setup.

=== Linux ===
(Ubuntu 7.10)
# Download the aircraft
# Open Terminal and log in as root
# Navigate to /usr/share/Games/FlightGear/Aircraft
# Extract your aircraft file into the folder
# Start up flight gear. Your aircraft should show up in the launcher

=== Macintosh OS X ===

# Open GUI Launcher for FlightGear Mac
# Click on "Others" tab at middle right of launcher
# Click "Install Add-On Data" link at bottom of launcher
# Select aircraft folder from menu, and click "Open"
# Click OK on pop-up box.

=== Solaris ===
TODO

=== Windows===
# Download an aircraft and save it on your desktop.
# Unzip the file, using a file archiver like 7-Zip.
# Move the unzipped folder (usually the aircraft's name) to your <tt>FlightGear/data/Aircraft</tt> directory.
 
'''!!! IMPORTANT !!!''' 
"Modern" Windows Versions (e.g. XP, Vista, Win7) tinkering a lot with user rights on access level. Therefore it's a bad idea to install and run FlightGear to and from "C:\Program Files" (German: C:\Programme). Find another drive / folder where you as logged in user have all neccesary right to read, write and execute the files you installed. Additionally there's a space / blank in folder's name which could cause weird behaviour. Use something like "C:\FlightGear".

==Choosing aircraft==
If you are looking for information to decide what aircraft to download, try [[Table of models]] or [[Aircraft]]. External links to third=party aircraft can be found at [[FlightGear hangars]]. Remember that the latest aircraft may not load with previous versions, so look for older aircraft in the links section.

==For developers==
Help develop the [[FlightGear Package Manager]] which is intended to support automatic aircraft and scenery installation, currently in alpha development and in need of testing.

==Related content==
* [[Downloading New Flightgear Scenery for Windows XP]]
* [[Hardware Recommendations]]
* [[Installing Scenery]]
* [[Recommended Software]]

Howto:Install scenery

2010-08-11T07:45:46Z

D-SKY1: /* Windows */ Regard user rights on c:\program files

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

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

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

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

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

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

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

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

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

or

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

=== Airports ===
Currently FlightGear does not use this directory. However, in upcoming releases, it will be used to extract airport data (like runway usage and parking spots) from. The directory tree might look somewhat overwhelming, it simply follows the <tt>Aiports/[I]/[C]/[A]/</tt> code (see [[ICAO-code]]).

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

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

[[Category:Scenery]]
[[pt:Pt/Instalando Cenário]]

Portal:User

2010-08-09T21:51:51Z

D-SKY1: Promoting "Multi-computing FlightGear" in Howto section

{{PortalMenu}}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">The User Portal</h2>
|-
|style="color:#000;"|
This portal is for the users of FlightGear. To be sure you get the latest news, it's a good idea to subscribe yourself to the [http://lists.sourceforge.net/lists/listinfo/flightgear-users FlightGear users] -mailing list. An [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-users archive of the list] is available and should be checked before asking again. Also, there's a users forum to be found at http://www.flightgear.org/forums.

|}
|}

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

! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Getting Started</h2>
|-
|style="color:#000;"|
* [[ New to FlightGear ]]
* [[Unique Features]]
* [[ FlightGear Manual ]]
* [[ FAQ ]]
* [[ FlightGear tutorials]]
* [[ Hardware Recommendations ]]
* [[ Notebooks known to run FlightGear]]
* [[ Recommended Software ]]
* [[ Troubleshooting Problems ]]
* [[ Volunteer ]]
|-
! <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;">Configuring Flightgear</h2>
|-
|style="color:#000;"|
* [[ Multi core and Multi GPU support ]]
* [[ Command Line Parameters ]]
* [[ Downloading New Flightgear Scenery for Windows XP]]
* [[ Installing Scenery ]]
* [[ Installing Aircraft ]]
* [[ Improving Framerates ]]
* [[Joystick]]
* [[ Linux software audio mixing with FlightGear ]]
* [[ Multiplayer Howto ]]
* [http://www.inkdrop.net/dave/multimon.pdf Using multiple monitors with FlightGear]
* [[ Howto:Configure Camera View Windows]]
|-
! <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;">Using Flightgear</h2>
|-
|style="color:#000;"|

* [[ Aircraft ]]
* [[ Helicopter ]]
* [[ Vehicle ]]
* [[ Chat Menu ]]
* [[ Doing aerotow over the net ]]
* [[ Dual control ]]
* [[ Flying the Helicopter ]]
* [[ Instant Replay ]]
* [[ Menubar]]
* [[ Preset Properties ]]
* [[ Realism ]]
* [[ Starting in the Air ]]
* [[ Table of models]] New! 
* [[ FlightGear related projects]]
* [http://www.nanjika.co.uk/flightgear/FGShortRef.pdf FlightGear Short Reference] pdf, 80 kB
|-
! <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;">Suggested</h2>
|-
|style="color:#000;"|

* [[ Suggested Aircraft ]]
* [[ Suggested Airports/Scenery ]]
* [[ Suggested Flights ]]
* [[Suggested Prerecorded Flights]] New! 
* [[ Challenging Airports]]
* [[ Suggested Software ]]

|-
|}

|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Community/Events</h2>
|-
|style="color:#000;"|
*[[FlightGear Airways]]
*[[FlightGear Race]]
*[[Pilots of the Caribbean]]
|-
! <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;">Interactive Scenarios</h2>
|-
|style="color:#000;"|
* [[ AI Systems ]]
* [[ Interactive Traffic ]]
* [[ Soaring ]]
|-
! <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;">Howtos</h2>
|-
|style="color:#000;"|
* [[Howto: Multi-computing FlightGear|Multi-computing FlightGear]]
* [[Howto: Air-Air Refueling|Air-Air Refueling]]
* [[Howto: Be a controller|Be a controller]]
* [[Howto: Carrier|Carrier]]
* [[Howto: Get rid of common errors|Get rid of common errors]]
* [[Howto: Multiplayer|Multiplayer]]
* [[Howto: Make nice screenshots|Make nice screenshots]]
* [[Howto: 737-300|737-300]]
'''[[:Category:Howto|More...]]'''
|-
! <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;">Tutorials</h2>
|-
|style="color:#000;"|
* [[ ATC Tutorial ]]
* [[ Instrument Landing System Tutorial ]]
* [[ Updating FlightGear on Windows]]
|-
! <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;">Using additional FlightGear Tools</h2>
|-
|style="color:#000;"|
* [[ FGo! ]] - Simple GUI for launching FlightGear
* [[ Fgrun ]] - aka the FlightGear Wizard
* [[ KFreeFlight ]] - GUI like fgrun but with KDE dependencies
* [[ FGCOM ]] - realtime voice comms
* [[ Atlas ]] - How to set it up
* [[Airport Diagram Generator]] - create charts from FlightGears data
|-
! <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;">FlightGear Promotion</h2>
|-
|style="color:#000;"|
* [[Unique Features]]
* [[FlightGear Reviews]]
* [[FlightGear Videos]]
* [[FlightGear 1.0 features showcase ]]
* [[Logos|FlightGear Logos]]
* [[Presentation Recipe]]
|-
|}

|class="MainPageBG" style="width:33%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Top Rated Aircraft</h2>
|-
|style="color:#000;"|
<w4g_ratinglist numberofitems="5"/>

'''[[Ratings|More...]]'''
|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[de:Portal:Benutzer]]
[[es:Portal:Usuario]]
[[pl:Portal:Dla użytkowników]]
[[fr:Portal:Utilisateur]]
[[zh:Portal:用户]]

Howto:Multi-computing FlightGear

2010-08-09T19:29:10Z

D-SKY1: /* Side Dish: The Slave Machine(s) */ Typo

FlightGear has some very powerful functions which are (IMHO) quite disregarded yet: distributing the property tree via LAN (local area network). Thinking long about this feature I finally came to the conclusion to interconnect several computers in my LAN to react like one single FlightGear system.

== Entrée ==
Advantages:
* Distributing the load of several calculations from one PC to multiple machines
* Attaching more screens for a more realistic simulation experience
* "Cleaning up your screen" to see scenery on the screen(s) of your (graphically) most powerful machine and instruments on more weakly computers
* Add more advantages here...

Disadvantages:
* Costs, as you need more computers, screens, network equipment
* Higher power consumption
* More space for placing all devices

Ergo: low WAF (wife acceptance factor)

== Aperitif: What's in the box? ==
So what is needed for multi-computing FlightGear?

* Basic knowledge in networking (IP address, subnet mask, protocols, network sockets, firewall, etc.)
* At least two computers (use the Operating System of your choice; I prefer using Linux and/or Windows, Mac may work too, though I don't have any knowledge about Macs)
* Switch / Access Point / Hub (yikes!) for interconnecting all participating devices (think of enough network cables if you decide to use a Switch or Hub)
I advise to use a modern 8-port Gigabit Switch which is quite low in price nowadays and will not give you too much headache in solving weird issues in your LAN. Choose your favorite brand. The hardware differences in this price segment are only marginal.

== Appetizer: Interconnecting your computers ==
Attach all devices to your LAN and configure the network devices so each of them is accessible via network (try a ping or similar to assure basic connectivity). In the following example I assume that your local network is 192.168.1.0 with a subnet mask of 255.255.255.0. Give all your devices individual (consecutive) addresses from this network and '''make triple sure''' not to create double IP address entries which will result in hard to resolve network conflicts. I'm not going to provide you detailed information on how to set up a network configuration for a certain operating system. This information is written down a million times in other places and should not be subject of this article.

== Main Dish: The Master Machine ==
I decided to make my most powerful computer to become a master for FlightGear. It's name is "leader" with IP 192.168.1.10, it runs on Ubuntu Lucid x64 and comes with a neat NVidia GTX260 and 5.1 sound output. This will be my:
* Data sending instance (more of this later)
* Scenery presenter
* Joystick / Yokes / Controller input
* Sound output

Install FlightGear just like you would do on any other system. Make sure to have the corresponding FlightGear data folder and some [[Howto: Install scenery|scenery data]] if you are not flying on-line using [[TerraSync]], what I strongly suggest to do.

Now it's time to bring up your "leader". On the [[Command_line_options|command line]] add the following two IO options to provide your [[FDM]] and your controls input to the first slave computer (assuming IP 192.168.1.11) Slave computers will be discussed in the next chapter:
[[Image:Multicomputing-settings fgrun io master.png|thumb|270px|Master-Settings using FGrun]]
--native-fdm=socket,out,60,192.168.1.11,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
* "socket" tells FlightGear how to present the data (here: as a network socket)
* "out" defines that the data is outgoing from "leader" to the slave(s)
* "60" is the update frequency in Hz (= updates per second). This must be set identically on all machines or you will get weird jitter
* "192.168.1.11" is the destination machine(s) where you want to send your data to
* Regard the use of '''two different ports (5510 and 5511)''' for the two different UDP sockets we are creating here for sending data to 192.168.1.11

In case of adding a second slave (assuming IP 192.168.1.12):
--native-fdm=socket,out,60,192.168.1.12,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
Regard the use of the IP 192.168.1.12 for sending the data to Slave #2. All further slaves follow the same principle.

Now it's time to fire up "leader" the first time with the new settings at your favorite airport with you favorite aircraft. Watch carefully if you see any errors in console output as this will give you precious hints if you made any mistakes in the IO configuration. Double check IP addresses, socket ports and protocol settings. If all works fine just let "leader" run idle for a while as we now set up the first slave and can test it's connectivity right away.

== Side Dish: The Slave Machine(s) ==
After setting up "leader" we will now configure "slave1" with IP 192.168.1.11 ("slave2" 192.168.1.12, etc.), connecting it to your LAN and installing FlightGear. It's time to take care of some startup parameters. I don't use FGRun on the slaves therefor I don't provide screenshots like I did for "leader":
--native-fdm=socket,in,60,,5510,udp
--native-ctrls=socket,in,60,,5511,udp
--fdm=null
--enable-panel
--disable-hud
--disable-sound
--prop:/sim/ai/enabled=false
--prop:/sim/ai-traffic/enabled=false
--prop:/sim/rendering/bump-mapping=false
--prop:/sim/rendering/draw-otw=false

* "native-fdm" and "native-ctrls" are now sockets using the "in" parameter because they do listen on your network interface for incoming traffic.
'''!!! Make sure to configure your firewall to accept incoming traffic on the above mentioned protocols/ports/sender IPs !!!
* "update frequency, port and protocol" are identical to the settings of "leader". Regard '''two commas''' between frequency and port. This is where normally the IP is placed and two commas here are intended because now the socket "listens" on your configured IP (on "slave1" 192.168.1.11) and on localhost (which is always 127.0.0.1 and used for internal networking). You can verify this on the slave by opening a console window and use a socket monitor like "netstat" to verify that the sockets are running on the proper interface and correct ports. If you want that FlightGear is just listening on your external interface you may add the address instead so you write a line like:
--native-fdm=socket,in,60,192.168.1.11,5510,udp
* "fdm=null" tells FlightGear not to use any flightmodel as this is given and calculated by "leader"
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed
* "disable-sound" does also what it says. No need for it on the slave. you have sound on "leader", don't you?
* "prop:/..." deactivates parts in the rendering chain which we don't need here. These features are running on "leader" and there they do what they should do

== Desert: Performance ==
I came up with the idea of using multiple (old) computers I collected during the last years because I hated the idea of having PCs dusting around without using them. As I like the idea of giving them a new mission it's sometimes somewhat tricky to gain the necessary performance depending on the hardware. So I try to get as much performance out of the old machines as possible. I dont see any needs for fancy eye candy on a PC who's job it is just to bring an instrument panel to the screen. 

So what can we do to gain more power?
* First: turn on "View -Display Options - Show Frame Rate" to get a feeling for settings that will help overall performance, and observe if the frame rate stalls, raises or drops after defining a new setting
* Step by step turn off all rendering options either in the main window or via command line options
* Set in the command line "--prop:/sim/rendering/camera-group/zfar=x", where x is a small value (e.g. 1 to 100)
* Don't provide the path to fg-scenery. Loading may take longer now and in the window you may only see water around you but this nothing to worry about

== Coffee & Cheese: Conclusion ==
Now you have a fancy system interacting with each other. You may now proceed to configure [[Howto:_Configure_camera_view_windows|multiple views and monitors]] so so can define side views, top windows, single instruments, [[Complex_Glass_Cockpit_Avionics|glass cockpit avionics]] and and and...

== Reflux: Do's, Dont's and Despair ==
* Until now I was only able to use the 2D panel of the default aircraft Cessna 172 independent of what aircraft I start with. In times of 3D cockpits it seems not very easy to find fresh 2D panels.
 
Please write down your findings and personal experiences here...
 
Enjoy and have fun
 
 
--[[User:D-SKY1|D-SKY1]] 22:57, 8 August 2010 (UTC)
[[Category:Howto|Multi-computing]]

Howto:Multi-computing FlightGear

2010-08-09T08:04:45Z

D-SKY1: Typo

FlightGear has some very powerful functions which are (IMHO) quite disregarded yet: distributing the property tree via LAN (local area network). Thinking long about this feature I finally came to the conclusion to interconnect several computers in my LAN to react like one single FlightGear system.

== Entrée ==
Advantages:
* Distributing the load of several calculations from one PC to multiple machines
* Attaching more screens for a more realistic simulation experience
* "Cleaning up your screen" to see scenery on the screen(s) of your (graphically) most powerful machine and instruments on more weakly computers
* Add more advantages here...

Disadvantages:
* Costs, as you need more computers, screens, network equipment
* Higher power consumption
* More space for placing all devices

Ergo: low WAF (wife acceptance factor)

== Aperitif: What's in the box? ==
So what is needed for multi-computing FlightGear?

* Basic knowledge in networking (IP address, subnet mask, protocols, network sockets, firewall, etc.)
* At least two computers (use the Operating System of your choice; I prefer using Linux and/or Windows, Mac may work too, though I don't have any knowledge about Macs)
* Switch / Access Point / Hub (yikes!) for interconnecting all participating devices (think of enough network cables if you decide to use a Switch or Hub)
I advise to use a modern 8-port Gigabit Switch which is quite low in price nowadays and will not give you too much headache in solving weird issues in your LAN. Choose your favorite brand. The hardware differences in this price segment are only marginal.

== Appetizer: Interconnecting your computers ==
Attach all devices to your LAN and configure the network devices so each of them is accessible via network (try a ping or similar to assure basic connectivity). In the following example I assume that your local network is 192.168.1.0 with a subnet mask of 255.255.255.0. Give all your devices individual (consecutive) addresses from this network and '''make triple sure''' not to create double IP address entries which will result in hard to resolve network conflicts. I'm not going to provide you detailed information on how to set up a network configuration for a certain operating system. This information is written down a million times in other places and should not be subject of this article.

== Main Dish: The Master Machine ==
I decided to make my most powerful computer to become a master for FlightGear. It's name is "leader" with IP 192.168.1.10, it runs on Ubuntu Lucid x64 and comes with a neat NVidia GTX260 and 5.1 sound output. This will be my:
* Data sending instance (more of this later)
* Scenery presenter
* Joystick / Yokes / Controller input
* Sound output

Install FlightGear just like you would do on any other system. Make sure to have the corresponding FlightGear data folder and some [[Howto: Install scenery|scenery data]] if you are not flying on-line using [[TerraSync]], what I strongly suggest to do.

Now it's time to bring up your "leader". On the [[Command_line_options|command line]] add the following two IO options to provide your [[FDM]] and your controls input to the first slave computer (assuming IP 192.168.1.11) Slave computers will be discussed in the next chapter:
[[Image:Multicomputing-settings fgrun io master.png|thumb|270px|Master-Settings using FGrun]]
--native-fdm=socket,out,60,192.168.1.11,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
* "socket" tells FlightGear how to present the data (here: as a network socket)
* "out" defines that the data is outgoing from "leader" to the slave(s)
* "60" is the update frequency in Hz (= updates per second). This must be set identically on all machines or you will get weird jitter
* "192.168.1.11" is the destination machine(s) where you want to send your data to
* Regard the use of '''two different ports (5510 and 5511)''' for the two different UDP sockets we are creating here for sending data to 192.168.1.11

In case of adding a second slave (assuming IP 192.168.1.12):
--native-fdm=socket,out,60,192.168.1.12,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
Regard the use of the IP 192.168.1.12 for sending the data to Slave #2. All further slaves follow the same principle.

Now it's time to fire up "leader" the first time with the new settings at your favorite airport with you favorite aircraft. Watch carefully if you see any errors in console output as this will give you precious hints if you made any mistakes in the IO configuration. Double check IP addresses, socket ports and protocol settings. If all works fine just let "leader" run idle for a while as we now set up the first slave and can test it's connectivity right away.

== Side Dish: The Slave Machine(s) ==
After setting up "leader" we will now configure "slave1" with IP 192.168.1.11 ("slave2" 192.168.1.12, etc.), connecting it to your LAN and installing FlightGear. It's time to take care of some startup parameters. I don't use FGRun on the slaves therefor I don't provide screenshots like I did for "leader":
--native-fdm=socket,in,60,,5510,udp
--native-ctrls=socket,in,60,,5511,udp
--fdm=null
--enable-panel
--disable-hud
--disable-sound
--prop:/sim/ai/enabled=false
--prop:/sim/ai-traffic/enabled=false
--prop:/sim/rendering/bump-mapping=false
--prop:/sim/rendering/draw-otw=false

* "native-fdm" and "native-ctrls" are now sockets using the "in" parameter because they do listen on your network interface for incoming traffic.
'''!!! Make sure to configure your firewall to accept incoming traffic on the above mentioned protocols/ports/sender IPs !!!
* "update frequency, port and protocol" are identical to the settings of "leader". Regard '''two commas''' between frequency and port. This is where normally the IP is placed and two commas here are intended because now the socket "listens" on your configured IP (on "slave1" 192.168.1.11) and on localhost (which is always 127.0.0.1 and used for internal networking). You can verify this on the slave by opening a console window and use If you want that FlightGear is just listening on your external interface you may add the address instead so you get line like:
--native-fdm=socket,in,60,192.168.1.11,5510,udp
* "fdm=null" tells FlightGear not to use any flightmodel as this is given by "leader"
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed
* "disable-sound" does also what it says. No need for it on the slave. you have sound on "leader", don't you?
* "prop:/..." deactivates parts in the rendering chain which we don't need here. These features are running on "leader" and there they do what they should do

== Desert: Performance ==
I came up with the idea of using multiple (old) computers I collected during the last years because I hated the idea of having PCs dusting around without using them. As I like the idea of giving them a new mission it's sometimes somewhat tricky to gain the necessary performance depending on the hardware. So I try to get as much performance out of the old machines as possible. I dont see any needs for fancy eye candy on a PC who's job it is just to bring an instrument panel to the screen. 

So what can we do to gain more power?
* First: turn on "View -Display Options - Show Frame Rate" to get a feeling for settings that will help overall performance, and observe if the frame rate stalls, raises or drops after defining a new setting
* Step by step turn off all rendering options either in the main window or via command line options
* Set in the command line "--prop:/sim/rendering/camera-group/zfar=x", where x is a small value (e.g. 1 to 100)
* Don't provide the path to fg-scenery. Loading may take longer now and in the window you may only see water around you but this nothing to worry about

== Coffee & Cheese: Conclusion ==
Now you have a fancy system interacting with each other. You may now proceed to configure [[Howto:_Configure_camera_view_windows|multiple views and monitors]] so so can define side views, top windows, single instruments, [[Complex_Glass_Cockpit_Avionics|glass cockpit avionics]] and and and...

== Reflux: Do's, Dont's and Despair ==
* Until now I was only able to use the 2D panel of the default aircraft Cessna 172 independent of what aircraft I start with. In times of 3D cockpits it seems not very easy to find fresh 2D panels.
 
Please write down your findings and personal experiences here...
 
Enjoy and have fun
 
 
--[[User:D-SKY1|D-SKY1]] 22:57, 8 August 2010 (UTC)
[[Category:Howto|Multi-computing]]

Howto:Multi-computing FlightGear

2010-08-09T07:22:36Z

D-SKY1: Adding "Reflux"

FlightGear has some very powerful functions which are (IMHO) quite disregarded: distributing the property tree via LAN (local area network). Thinking long about this feature I finally came to the conclusion to connect several computers in my LAN to react like one single FlightGear system.

== Entrée ==
Advantages:
* distributing the load of several calculations from one local CPU to multiple other machines
* attaching more screens for a more realistic simulation experience
* "cleaning up your screen" to see scenery on the screen(s) of your (graphically) most powerful machine and instruments on more weakly computers
* add more advantages here...

Disadvantages:
* costs, as you need more computers, screens, network cables / wireless access points
* higher power consumption
* more space for placing all devices

Ergo: low WAF (wife acceptance factor)

== Aperitif: What's in the box? ==
So what is needed for multi-computing FlightGear?

* basic knowledge in networking (IP address, subnet mask)
* min. two computers (use the Operating System of your choice; I prefer using Linux and/or Windows, Mac may work too, though I don't have any knowledge about it)
* Switch / Access Point / Hub (yikes!) for interconnecting all participating devices (think of enough network cables if you decide to use a Switch or Hub)
I advise to use a modern 8-port Gigabit Switch which is quite low in price nowadays and will not give you too much headache in solving weird issues in your LAN. Select one from you favorite brand. The hardware differences in this price segment are only marginal.

== Appetizer: Interconnecting your computers ==
Attach all devices to your LAN and configure the network devices so each of them is accessible via network (try a ping or similar to assure basic connectivity). In the following example I assume that your local network is 192.168.1.0 with a subnet mask of 255.255.255.0. Give all your devices individual (consecutive) addresses from this network and '''make triple sure''' not to create double IP address entries which will result in hard to resolve network conflicts. I'm not going to provide you detailed information on how to set up a network configuration for a certain operating system. This information is written down a million times in other places and should not be subject of this article.

== Main Dish: The Master Machine ==
I decided to make my most powerful computer to become a master for FlightGear. It's name is "leader" with IP 192.168.1.10, it runs on Ubuntu Lucid x64 and comes with a neat NVidia GTX260 and 5.1 sound output. This will be my:
* data sending instance (more of this later)
* scenery presenter
* Joystick / Yokes / controller input
* sound output

Install FlightGear just like you would do on any other system. Make sure to have the corresponding FlightGear data folder and some [[Howto: Install scenery|scenery data]] if you are not flying on-line using [[TerraSync]], what I strongly suggest to do.

Now it's time to bring up your "leader". On the [[Command_line_options|command line]] add the following two IO options to provide your [[FDM]] and your controls input to the first slave computer (assuming IP 192.168.1.11) Slave computers will be discussed in the next chapter:
[[Image:Multicomputing-settings fgrun io master.png|thumb|270px|Master-Settings using FGrun]]
--native-fdm=socket,out,60,192.168.1.11,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
"socket" tells FlightGear how to present the data (here: as a network socket). "out" defines that the data is outgoing from "leader" to the slave(s). "60" is the update frequency in Hz (= updates per second). This must be set identically on all machines or you will get weird jitter. Regard the use of '''two different ports (5510 and 5511)''' for the two different UDP sockets we are creating here for sending data to 192.168.1.11.

In case of using a second slave (assuming IP 192.168.1.12):
--native-fdm=socket,out,60,192.168.1.12,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
Regard the use of the IP 192.168.1.12 for sending the data to Slave #2. All further slaves follow the same principle.

Now it's time to fire up "leader" the first time with the new settings at your favorite airport with you favorite aircraft. Watch carefully if you see any errors in console output as this will give you precious hints if you made any mistakes in the IO configuration. If all works fine just let it run idle for a while as we now set up the first slave and can test it's connectivity right away.

== Side Dish: The Slave Machine(s) ==
After setting up "slave1" with IP 192.168.1.11 ("slave2" 192.168.1.12, etc.), connecting it to your LAN and installing FlightGear it's time to take care of some startup parameters. I don't use FGRun on the slaves therefor I don't provide screenshots like I did for "leader":
--native-fdm=socket,in,60,,5510,udp
--native-ctrls=socket,in,60,,5511,udp
--fdm=null
--enable-panel
--disable-hud
--disable-sound
--prop:/sim/ai/enabled=false
--prop:/sim/ai-traffic/enabled=false
--prop:/sim/rendering/bump-mapping=false
--prop:/sim/rendering/draw-otw=false

* "native-fdm" and "native-ctrls" are now sockets using the "in" parameter because they do listen on your network interface for incoming traffic.
'''!!! Make sure to configure your firewall to accept incoming traffic on the above mentioned protocols/ports/sender IPs !!!
* "update frequency, port and protocol" are identical to the settings of "leader". Regard '''two commas''' between frequency and port. This is where normally the IP is placed and here intended. Now the socket "listens" on your configured IP (on "slave1" 192.168.1.11) and on localhost (which is always 127.0.0.1 and used for internal networking). If you want that FlightGear is just listening on your external interface you may add the address instead so you get line like:
--native-fdm=socket,in,60,192.168.1.11,5510,udp
* "fdm=null" tells FlightGear not to use any flightmodel as this is given by "leader"
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed
* "disable-sound" does also what it says. No need for it on the slave. you have sound on "leader", don't you?
* "prop:/..." deactivates parts in the rendering chain which we don't need here. These features are running on "leader" and there they do what they should do

== Desert: Performance ==
I came up with the idea of using multiple (old) computers I collected during the last years because I hated the idea of having PCs dusting around without using them. As I like the idea of giving them a new mission it's sometimes somewhat tricky to gain the necessary performance depending on the hardware. So I try to get as much performance out of the old machines as possible. I dont see any needs for fancy eye candy on a PC who's job it is just to bring an instrument panel to the screen. 

So what can we do to gain more power?
* First: turn on "View -Display Options - Show Frame Rate" to get a feeling for settings that will help overall performance, and observe if the frame rate stalls, raises or drops after defining a new setting
* Step by step turn off all rendering options either in the main window or via command line options
* Set in the command line "--prop:/sim/rendering/camera-group/zfar=x", where x is a small value (e.g. 1 to 100)
* Don't provide the path to fg-scenery. Loading may take longer now and in the window you may only see water around you but this nothing to worry about

== Coffee & Cheese: Conclusion ==
Now you have a fancy system interacting with each other. You may now proceed to configure [[Howto:_Configure_camera_view_windows|multiple views and monitors]] so so can define side views, top windows, single instruments, [[Complex_Glass_Cockpit_Avionics|glass cockpit avionics]] and and and...

== Reflux: Do's, Dont's and Despair ==
Please write down your findings and personal experiences here...
 
Enjoy and have fun
 
 
--[[User:D-SKY1|D-SKY1]] 22:57, 8 August 2010 (UTC)
[[Category:Howto|Multi-computing]]

User:D-SKY1

2010-08-08T23:12:24Z

D-SKY1: Added "Multi-computing FlightGear"

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]
 
* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]
 
* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions
** Learning how to use [[Howto:_Multi-computing_FlightGear|multiple computers for FlightGear]]
 
* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]
 
Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>
 
Don't ask to ask. Just ask ;)

Howto:Multi-computing FlightGear

2010-08-08T22:57:48Z

D-SKY1: Created page with 'FlightGear has some very powerful functions which are (IMHO) quite disregarded: distributing the property tree via LAN (local area network). Thinking long about this feature I fi…'

FlightGear has some very powerful functions which are (IMHO) quite disregarded: distributing the property tree via LAN (local area network). Thinking long about this feature I finally came to the conclusion to connect several computers in my LAN to react like one single FlightGear system.

== Entrée ==
Advantages:
* distributing the load of several calculations from one local CPU to multiple other machines
* attaching more screens for a more realistic simulation experience
* "cleaning up your screen" to see scenery on the screen(s) of your (graphically) most powerful machine and instruments on more weakly computers
* add more advantages here...

Disadvantages:
* costs, as you need more computers, screens, network cables / wireless access points
* higher power consumption
* more space for placing all devices

Ergo: low WAF (wife acceptance factor)

== Aperitif: What's in the box? ==
So what is needed for multi-computing FlightGear?

* basic knowledge in networking (IP address, subnet mask)
* min. two computers (use the Operating System of your choice; I prefer using Linux and/or Windows, Mac may work too, though I don't have any knowledge about it)
* Switch / Access Point / Hub (yikes!) for interconnecting all participating devices (think of enough network cables if you decide to use a Switch or Hub)
I advise to use a modern 8-port Gigabit Switch which is quite low in price nowadays and will not give you too much headache in solving weird issues in your LAN. Select one from you favorite brand. The hardware differences in this price segment are only marginal.

== Appetizer: Interconnecting your computers ==
Attach all devices to your LAN and configure the network devices so each of them is accessible via network (try a ping or similar to assure basic connectivity). In the following example I assume that your local network is 192.168.1.0 with a subnet mask of 255.255.255.0. Give all your devices individual (consecutive) addresses from this network and '''make triple sure''' not to create double IP address entries which will result in hard to resolve network conflicts. I'm not going to provide you detailed information on how to set up a network configuration for a certain operating system. This information is written down a million times in other places and should not be subject of this article.

== Main Dish: The Master Machine ==
I decided to make my most powerful computer to become a master for FlightGear. It's name is "leader" with IP 192.168.1.10, it runs on Ubuntu Lucid x64 and comes with a neat NVidia GTX260 and 5.1 sound output. This will be my:
* data sending instance (more of this later)
* scenery presenter
* Joystick / Yokes / controller input
* sound output

Install FlightGear just like you would do on any other system. Make sure to have the corresponding FlightGear data folder and some [[Howto: Install scenery|scenery data]] if you are not flying on-line using [[TerraSync]], what I strongly suggest to do.

Now it's time to bring up your "leader". On the [[Command_line_options|command line]] add the following two IO options to provide your [[FDM]] and your controls input to the first slave computer (assuming IP 192.168.1.11) Slave computers will be discussed in the next chapter:
[[Image:Multicomputing-settings fgrun io master.png|thumb|270px|Master-Settings using FGrun]]
--native-fdm=socket,out,60,192.168.1.11,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
"socket" tells FlightGear how to present the data (here: as a network socket). "out" defines that the data is outgoing from "leader" to the slave(s). "60" is the update frequency in Hz (= updates per second). This must be set identically on all machines or you will get weird jitter. Regard the use of '''two different ports (5510 and 5511)''' for the two different UDP sockets we are creating here for sending data to 192.168.1.11.

In case of using a second slave (assuming IP 192.168.1.12):
--native-fdm=socket,out,60,192.168.1.12,5510,udp
--native-ctrls=socket,out,60,192.168.1.11,5511,udp
Regard the use of the IP 192.168.1.12 for sending the data to Slave #2. All further slaves follow the same principle.

Now it's time to fire up "leader" the first time with the new settings at your favorite airport with you favorite aircraft. Watch carefully if you see any errors in console output as this will give you precious hints if you made any mistakes in the IO configuration. If all works fine just let it run idle for a while as we now set up the first slave and can test it's connectivity right away.

== Side Dish: The Slave Machine(s) ==
After setting up "slave1" with IP 192.168.1.11 ("slave2" 192.168.1.12, etc.), connecting it to your LAN and installing FlightGear it's time to take care of some startup parameters. I don't use FGRun on the slaves therefor I don't provide screenshots like I did for "leader":
--native-fdm=socket,in,60,,5510,udp
--native-ctrls=socket,in,60,,5511,udp
--fdm=null
--enable-panel
--disable-hud
--disable-sound
--prop:/sim/ai/enabled=false
--prop:/sim/ai-traffic/enabled=false
--prop:/sim/rendering/bump-mapping=false
--prop:/sim/rendering/draw-otw=false

* "native-fdm" and "native-ctrls" are now sockets using the "in" parameter because they do listen on your network interface for incoming traffic.
'''!!! Make sure to configure your firewall to accept incoming traffic on the above mentioned protocols/ports/sender IPs !!!
* "update frequency, port and protocol" are identical to the settings of "leader". Regard '''two commas''' between frequency and port. This is where normally the IP is placed and here intended. Now the socket "listens" on your configured IP (on "slave1" 192.168.1.11) and on localhost (which is always 127.0.0.1 and used for internal networking). If you want that FlightGear is just listening on your external interface you may add the address instead so you get line like:
--native-fdm=socket,in,60,192.168.1.11,5510,udp
* "fdm=null" tells FlightGear not to use any flightmodel as this is given by "leader"
* "enable-panel" does exactly what it says: it's enabling the instrument panel. That's what we want here
* "disable-hud" will remove the heads up display. We have this on "leader". Here it's just not needed
* "disable-sound" does also what it says. No need for it on the slave. you have sound on "leader", don't you?
* "prop:/..." deactivates parts in the rendering chain which we don't need here. These features are running on "leader" and there they do what they should do

== Desert: Performance ==
I came up with the idea of using multiple (old) computers I collected during the last years because I hated the idea of having PCs dusting around without using them. As I like the idea of giving them a new mission it's sometimes somewhat tricky to gain the necessary performance depending on the hardware. So I try to get as much performance out of the old machines as possible. I dont see any needs for fancy eye candy on a PC who's job it is just to bring an instrument panel to the screen. 

So what can we do to gain more power?
* First: turn on "View -Display Options - Show Frame Rate" to get a feeling for settings that will help overall performance, and observe if the frame rate stalls, raises or drops after defining a new setting
* Step by step turn off all rendering options either in the main window or via command line options
* Set in the command line "--prop:/sim/rendering/camera-group/zfar=x", where x is a small value (e.g. 1 to 100)
* Don't provide the path to fg-scenery. Loading may take longer now and in the window you may only see water around you but this nothing to worry about

== Coffee & Cheese: Conclusion ==
Now you have a fancy system interacting with each other. You may now proceed to configure [[Howto:_Configure_camera_view_windows|multiple views and monitors]] so so can define side views, top windows, single instruments and and and...
 
Enjoy and have fun
 
--[[User:D-SKY1|D-SKY1]] 22:57, 8 August 2010 (UTC)
[[Category:Howto|Multi-computing]]

File:Multicomputing-settings fgrun io master.png

2010-08-08T21:09:04Z

D-SKY1:

User:D-SKY1

2010-08-07T11:34:16Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions

* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in irc://irc.flightgear.org. 
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>

Don't ask to ask. Just ask ;)

Talk:Input device

2010-08-07T10:54:17Z

D-SKY1: /* Different configurations for the same stick depending on OS (Linux vs. Windows) */ new section

1.9.1 for Windows doesn't seem to include js_demo.exe at all. Does anyone know where I might find it?

== Saitek x52 pro don't work under Ubuntu 9.10 ==

Hello to everyone,
I have an X52 pro flight control system.

I can't use it under ubuntu. I don't know why. 
I have followed the FG getstartguide.pdf to check the device. 

The commands that I've used to check: 

'''1)''' andrea@andrea-IBM:~$ lsusb 
Bus 004 Device 004: ID 06a3:0762 Saitek PLC 

'''2)''' andrea@andrea-IBM:~$ dmesg | grep Joystick 
[ 875.178360] generic-usb 0003:06A3:0762.0002: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 
[ 983.266631] generic-usb 0003:06A3:0762.0003: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 
[ 4743.317355] generic-usb 0003:06A3:0762.0004: input,hidraw1: USB HID v1.11 Joystick [Saitek Saitek X52 Pro Flight Control System] on usb-0000:00:1a.1-1/input0 

'''3) Confirming that the driver recognizes your joystick''' andrea@andrea-IBM:~$ js_demo 
Joystick test program. 

Joystick 0 not detected 
Joystick 1 not detected 
Joystick 2 not detected 
Joystick 3 not detected 
Joystick 4 not detected 
Joystick 5 not detected 
Joystick 6 not detected 
Joystick 7 not detected 
 

----
Can anyone help me?
--[[User:Andreasantopietro|Andreasantopietro]] 22:42, 6 August 2010 (UTC)

:: Andreas, please ask support at our forum: http://flightgear.org/forums We will be able to help you there. This wiki is only meant for documentation.
:: [[User:Gijs|Gijs]] 07:38, 7 August 2010 (UTC)

== Different configurations for the same stick depending on OS (Linux vs. Windows) ==

I'm using js_demo on Linux (here: Ubuntu Lucid x64 with joystick "SpeedLink Black Widow")
On Linux it's detected as "Mega World USB Game Controller", on Windows js_demo detects a "SL-6640 Black Widow Flightstick".
I define cooliehat left/right and up/down for view direction and view elevation. On Linux the numbering of the cooliehat axis differs from what is detected on Windows. This I can respect by using the number-tag in my XML. Additional view elevation is opposite in both OSs. Linux move up = axis 5 -> -1, move down = axis 5 -> +1; Windows move up = axis 7 -> +1, move down = axis 7 -> -1. How can I respect these differences in my config.xml?
Cheers 
--[[User:D-SKY1|D-SKY1]] 10:54, 7 August 2010 (UTC)

User:D-SKY1

2010-08-04T06:27:36Z

D-SKY1: IRC server III (grr)

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions

* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in irc://irc.flightgear.org.
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear</del>

Don't ask to ask. Just ask ;)

User:D-SKY1

2010-08-04T06:26:55Z

D-SKY1: IRC server II

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions

* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in irc://irc.flightgear.org.
<del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear<del>

Don't ask to ask. Just ask ;)

User:D-SKY1

2010-08-04T06:26:09Z

D-SKY1: icr server

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions

* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in irc.flightgear.org <del>irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear<del>. Don't ask to ask. Just ask ;)

Talk:Article requests

2010-08-01T17:05:46Z

D-SKY1: Created page with 'Hooray: Nice idea to create request pages. Maybe it would be good to check if there is already something written about any topic you propose here. Cheers --~~~~'

Hooray: Nice idea to create request pages. Maybe it would be good to check if there is already something written about any topic you propose here.

Cheers 
--[[User:D-SKY1|D-SKY1]] 17:05, 1 August 2010 (UTC)

Building FlightGear - Linux

2010-07-31T10:26:10Z

D-SKY1: /* APT-GET List */ typo

{{Main article|Building Flightgear}}

This section describes how to build [[FlightGear]] on Linux system.

Compiling FlightGear is not a task for novice users. Thus, if you're a beginner (we all were once) on a platform which binaries are available for, we recommend postponing this task and just starting with the binary distribution to get you flying.

Or if you develop on Ubuntu or Debian, consider trying the script described in [[Scripted Compilation on Linux Debian/Ubuntu]].

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

'''C++ compiler'''

These are: c++, cpp, gcc, g++ found under the /usr/bin directory. You will also need to have the tools '''autoconf''' and '''automake1.9''' installed.

'''GIT'''

See [[FlightGear and Git]].

'''[[OpenGL]] support'''

More specifically, your system needs the support for hardware accelerated graphics. You can check for this by running the following in a [[command line]]:

glxinfo | grep direct

Note: To run the above command, you need to have the tool '''mesa-utils''' installed.

You should then see:

direct rendering: Yes

This means you are good to go as far as OpenGL support is concerned.

If you see:

direct rendering: No

Don't panic yet. This may just mean some required libraries for hardware accelerated graphic are missing. Go ahead and try installing plib 1.8.5 and its dependencies first. If you still get the above message, then you will need to do some googling and troubleshoot yourself.

== Dependencies ==
FlightGear is dependent on quite a few number of libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed. For example, the development version for package plib1.8.5 is plib1.8.5'''-dev'''.

The dependency is summarized in the following tree. Please note that each library has its own dependencies, and most of these are not shown here.

* FlightGear
** [http://kcat.strangesoft.net/openal.html OpenAL]
** SimGear
*** [http://plib.sourceforge.net/ PLIB]. Since march 2008, you will need version 1.8.5 - your distro probably supplies 1.8.4 still.
**** For versions pre march/2008: (Free)GLUT or SDL (We recommend the use of SDL over Free/GLUT, [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16153.html however since march 2008, FreeGLUT as well as SDL are both considered depreciated, please only use --enable-osgviewer during configuration instead])
*** [[ OpenSceneGraph ]] (The latest development release or svn trunk for FlightGear/Git and the latest preceding OSG release for a FlightGear release)
*** You also need the development files for several basic libraries to build the software, among them the following (the package names are for Debian and derivatives(?)):
**** libfreetype6-dev
**** libjpeg62-dev
**** libungif4-dev
**** libtiff4-dev
**** libpng12-dev
**** libxmu-dev
**** libxi-dev
**** zlib1g-dev
**** libglut3-dev

If you attack the above dependencies in the order listed below, you should be good:

1. Glut. Most distributions include glut packages, although you may have to hunt for them. Make sure you install both the glut and glut-devel packages, otherwise FlightGear may be able to compile but won't run correctly.

2. Zlib. Most distributions install the basic zlib libraries by default, but not the development portions. If you don't have zlib.h, you probably need to install the zlib-devel package for your distribution.

3. Plib - portability libraries and scene graph.

4. [[ OpenSceneGraph ]]

5. SimGear - Simulation support libraries. If you are building FlightGear from Git, you need the Git version of SimGear. If you have strange build errors, one of the first things to check is that you have an up-to-date version of SimGear built and installed.

==== APT-GET List ====
This is a list of all the apt-get commands I had to do while compiling FG, SG, and OSG on a mostly clean Ubuntu 64 system. It is a list of all the libraries you and your computer needs to compile FG, SG, OSG, and PLib. All you have to do is copy the full command, paste it in Terminal, enter your password, and it will download all the packages for you, and install them too. The full command is at the bottom, and I hope someone finds it useful :) sub-dependencies (dependencies of the dependencies) are not included as they are installed automatically by apt-get. If anyone sees something missing, please add it.

git - to get SG and FG 
subversion - to get OSG 
build-essential - to build (includes GCC, and other build tools) 
cmake - OSG Uses this 
cmake-curses-gui -- OSG Uses this 
libpng-dev - to enable FG to use PNG textures 
libfreetype6-dev - fonts 
libjpeg-dev 
libungif4-dev 
libtiff-dev 
libxmu-dev 
libxi-dev 
libglut3-dev 
libalut-dev - sound 
libboost-dev - makes coding for some developers easier 
automake - needed by ./autogen.sh files 
autoconf - needed by ./autogen.sh files 
libfltk1.1-dev - You will need this if you will be using FGRun 
-----------
<pre>
sudo apt-get install git subversion build-essential cmake cmake-curses-gui libpng-dev libfreetype6-dev
libjpeg-dev libungif4-dev libtiff-dev libxmu-dev libxi-dev libglut3-dev libalut-dev
libboost-dev automake autoconf libfltk1.1-dev
</pre>
-----------
Total size is about 230 MB, depending on what you already have from other applications.

This list might seem a bit short, but the sub-dependencies all add up :) The dependencies will be listed by apt-get when you use the command.

== Compiling ==
Assuming you are root, do:
cd /usr/local/src

Note: When tracking a fast changing software like FlightGear/Git it is highly advisable to install it in a separate directory. That way one can also easily build and reinstall without being root, which greatly reduces the risk of messing up one's system.
To install in a directory of your choice add the <tt>--prefix</tt> argument to configure. E.g. <tt>./configure --prefix=$HOME/FlightGear</tt>. I would recommend installing all of OSG, plib, SimGear and FlightGear with the same prefix.

=== Getting and compiling SimGear ===

'''Step 1:'''

Clone the SimGear git repository and set it up to track the 'next' branch.
git clone git://gitorious.org/fg/simgear.git

By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.

'''Step 2:'''

The source code will be downloaded into a directory called '''simgear'''.

Next, go into the directory and make preparations for the compilation:
cd simgear
./autogen.sh
./configure

'''Note''' that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command

'''Step 3:'''

Compile and install SimGear by doing:
make; make install

''Note:'' with gcc 4.2 or later,on some platforms, you can get compiling errors about alc.h like:

'<anonymous>' has incomplete type
take a look at http://bugs.gentoo.org/166723

=== Getting and compiling FlightGear ===

'''Step 1:'''

Clone the FlightGear git repository and set it up to track the 'next' branch.
git clone git://gitorious.org/fg/flightgear.git

By default after cloning you should have a local next branch that tracks the master next branch. It can be updated it with git pull.

'''Step 2:'''

Next, go into the folder and make preparations for the compilation:
cd flightgear
./autogen.sh
./configure

Note that if you don't want to install simgear globally on the system but in a specific directory, you can do so by adding --prefix=/path/to/your/fgInstallation to the ./configure command.
If you didn't install OSG globally or in the same prefix as SimGear and FlightGear, you have to pass the OSG directory to the configure-command like this:
./configure --prefix=/path/to/fgInstallation --with-osg=/path/to/osg/installation --enable-osgviewer
In this case you have to tell your system where to find the OSG libraries before you can run flightgear:
export LD_LIBRARY_PATH=/path/to/osgInstallation/lib:$LD_LIBRARY_PATH

'''Step 3:'''

Now you can compile and install Flightgear by:
make; make install

'''Step 4:'''

Clone the data directory:
git clone git://gitorious.org/fg/fgdata.git

The data directory is large (almost 2.5GB) so it will take considerable time to download.
There mirror of fgdata that might be faster to download from:
git clone git://mapserver.flightgear.org/fgdata

The mirror is synchronized with the master so either will do.

And install it in (or as) /usr/local/share/FlightGear
mv fgdata /usr/local/share/FlightGear

== Distro-specific instructions ==
=== Debian/Ubuntu ===
*You can use the [[Scripted_Compilation_on_Linux_Debian/Ubuntu]] script to have Flightgear compiled in one shot under both Ubuntu and Debian systems.
*Debian users who prefer to build it without script may look at [[Building_Flightgear_-_Debian]].
=== Gentoo ===
*Gentoo users can also use overlays to build FlightGear without much hassle: [[Building_Flightgear_-_Gentoo]].

== External links ==
=== Instructions ===
* [[ MSYS ]]
* [[ MinGW/cross-compiler ]]
* [[ CodeBlocks IDE ]]
* [[ OpenSUSE 10.1 10.2 ]]
* [http://www.geoffmclane.com/fg/fgmsvc7.htm MSVC7 *.Net]
* [http://www.oflebbe.de/oflebbe/FlightGear/index.html MSVC8 aka Visual 2005]
* [http://macflightgear.sourceforge.net/home/documents/ Mac OS X]

{{Building}}

Instrument requests

2010-07-30T11:29:23Z

D-SKY1: /* Currently work in progress */ removed wrong details

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

= Currently work in progress =

'''The Televel Fuel Gauge'''
[[Image:Televel-fuel-gauge.jpg|thumb|250px|Glance at "The Televel" Fuel Gauge]]
AndersG created the Televel Fuel Gauge as used in the Short S.23 "Empire flying boat" and Short Sunderland. This gauge is used for fuel level reading. The aircraft using this fine piece of instrumentation is WiP (work in progress) and will be available "when it's done".

= Open instrument requests =

[[Category:Contribution requests]]

Instrument requests

2010-07-30T11:18:28Z

D-SKY1: /* Currently work in progress */ typo

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

= Currently work in progress =

'''The Televel Fuel Gauge'''
[[Image:Televel-fuel-gauge.jpg|thumb|250px|Glance at "The Televel" Fuel Gauge]]
AndersG created the Televel Fuel Gauge as used in the Short S.23 "Empire flying boat" and Short Sunderland. This gauge is used for fuel level reading with indication of presence of water in the fuel tanks. The aircraft using this fine piece of instrumentation is WiP (work in progress) and will be available "when it's done".

= Open instrument requests =

[[Category:Contribution requests]]

Instrument requests

2010-07-30T11:17:19Z

D-SKY1:

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

= Currently work in progress =

'''The Televel Fuel Gauge'''
[[Image:Televel-fuel-gauge.jpg|thumb|250px|Glance at "The Televel" Fuel Gauge]]
AndersG created the Televel Fuel Gauge as used in the Short S.23 "Empire flying boat" and Short Sunderland. This gauge is used for fule level reading with indication of presence of water in the fuel tanks. The aircraft using this fine piece of instrumentation is WiP (work in progress) and will be available "when it's done".

= Open instrument requests =

[[Category:Contribution requests]]

File:Televel-fuel-gauge.jpg

2010-07-30T11:07:29Z

D-SKY1:

User:D-SKY1

2010-07-24T16:25:55Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]] ([http://helijah.free.fr/flightgear/hangar.htm Helijah's Hangar])
** Some 3D modeling of the 737-100 cockpit [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for [[A380]] in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for FlightGear Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Misc'''
** Joystick definition for SpeedLink's Black Widow Flightstick SL-6640 [http://www.speed-link.com/?p=2&cat=314&pid=21606&paus=1&act_lang=en]
** Bugfix of [[FlightGear_Multiplayer_Server|FlightGear Multiplayer Server]] for newer GCC versions

* '''My Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in <del>irc.flightgear.org</del> irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear. Don't ask to ask. Just ask ;)

User:D-SKY1

2010-07-23T19:50:22Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]]
** Some 3D modeling of the 737-100 [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for A380 in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Eastfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in <del>irc.flightgear.org</del> irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear. Don't ask to ask. Just ask ;)

User:D-SKY1

2010-07-23T19:48:40Z

D-SKY1:

{{User
|name = Mike
|location = Hamburg, Germany, Europe
|age = 42
|job = IT-Consultant
|interests = 3D-Modeling, Scripting, Logic
|callsign = D-SKY1
|favourite =[[Boeing 737-100]], [[Cessna Citation X]], [[Boeing 777-200]]
|website =none
}}

Here is what I've come up with:

* '''Aircraft'''
** Autopilot for Helijah's [[Boeing_737-100|Boeing 737-100]]
** Some 3D modeling of the 737-100 [http://wiki.flightgear.org/index.php/File:737-100_cockpit.jpg]
** Emirates Airlines livery for A380 in AI aircrafts section (available via GIT)
** New livery "Cebu Pacific Airlines" [http://liveries.flightgear.org/liveries.php?id=224] for Forum's A320 [http://www.flightgear.org/forums/viewtopic.php?p=51843#p51843]

* '''Scenery'''
** Manila, Philippines ([[Ninoy_Aquino_International_Airport|RPLL]]) - New models for 3 terminals, new tower, placement of several shared models (available via Terrasync)
** Dubai, United Arab Emirates ([[OMDB]]) - Traffic patterns for AI traffic, runways usage timetable (available via GIT)
** [http://wiki.flightgear.org/index.php/FlightGear_Newsletter_July_2010#Improvement_of_Westfrisian_Islands.2C_North_Sea Eastfrisian Islands, Northsea (Norderney, Baltrum, Langeoog, Wangerooge)]

* '''Future Plans'''
** AI traffic for RPLL
** More AI traffic enhancements in OMDB
** 3D models for OMDB
** Models and AI traffic RPVB (New Bacolod Silay Airport, Island of Negros, Phillipines)
** Models and AI traffic RPML (Cagayan De Oro, Island of Mindanao, Phillipines)
** My own selfmade aircraft ;) [http://www.gulfstream.com/products/g650/ Gulfstream G650]

Most time of the day you can find me in <del>irc.flightgear.org</del> irc://mpserver12.flightgear.org/flightgear and/or irc://irc.freenode.net/flightgear. Don't ask to ask. Just ask ;)

File talk:Westfrisian Islands.png

2010-07-23T19:46:12Z

D-SKY1:

Baltrum, Langeoog, Spiekeroog and Wangerooge used to belong to the Eastfrisian Islands.
The dutch performed better in south africa - but they don't get our islands ;-)

Oooopssss *blush*

FlightGear Newsletter July 2010

2010-07-23T19:45:37Z

D-SKY1:

{{newsletter}}
{{TOC_right}}

This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!

==Newsletter history==

One year ago, in June 2009, [[FlightGear]]-head Curt proposed his newsletter-idea [http://www.flightgear.org/forums/viewtopic.php?f=6&t=5201 at the forum]. With multiple (failed) efforts in the past, those involved were extremely eager to get it up and going this time. Stuart was the one that wrote most of the first issue(s). At the time of the second issue, more people were involved and wrote a paragraph or two.

Today, the newsletter is written by a bunch of people, with different interests and relations to FlightGear. It provides an easy way to keep up-to-date with the ongoing developments; both in FlightGear itself and in the community around it.

I would like to use this opportunity to thank those that contributed over the past year. Thanks to their work, the newsletter still exists! In order to reach our next mileage, we would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone (with a wiki account, [[Special:UserLogin|free to register]]) can edit the newsletter and every contribution is welcome.

Now, all I can say is: enjoy this brand new edition!

==Contributing==
One of the regular thoughts expressed on the [[FlightGear]] forums is ''"I'd like to contribute but I don't know how to program, and I don't have the time".''

Unfortunately, there is a common misconception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

Some ideas:

* writing articles for the [http://wiki.flightgear.org/index.php/Next_newsletter next issue of this newsletter]
* sending corrections/updates to the FlightGear Manual
* helping new users on the forums/IRC
* writing a wiki page
* organizing fly-outs

One of the easiest ways to help is to improve the scenery in your local area by placing buildings/structures using the UFO and submitting them to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database]. It's easy, and best of all requires little time to have a real impact. Instructions on how to do this can be found in the wiki, article [[Placing 3D Objects with the UFO]].

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

==Reminder: Google Summer of Code 2011==

We would like to remind all readers that the FlightGear project is planning to participate in Google's Summer of Code 2011.

However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person.
It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011.
Some easy ways for helping right now would be:

* suggest new project ideas (i.e. get in touch using the forums, mailing lists or the wiki)
* browse the forums or mailing list archives and look for suitable candidate projects
* help refine and improve existing project proposals
* help finalize the application template that we are preparing
* help us find suitable students who might be interested in participating in 2011
* help us find mentors
* summarize all related discussions, and document them here in the wiki

At the moment, we are collecting ideas for answering the various questions in the application: [http://flightgear.org/forums/viewtopic.php?f=38&t=8857 Why should FlightGear participate in GSoC?]

If you have any questions or other feedback related to GSoC, please use the forum to get in touch: [http://flightgear.org/forums/viewforum.php?f=38]

==Development news==

===A new forum for Google Summer of Code===
As some of you may already know, there is now an orchestrated effort going on to get FlightGear ready for becoming a mentoring organization in Google's Summer of Code 2011.

So far, all related information has been collected here in the wiki: [[GSoC]].
But to ease the planning and organization process, there has now been a new sub forum set up for talking about anything that is one way or another related to this effort.
The forum can be found at: http://flightgear.org/forums/viewforum.php?f=38

This should make it much easier for all community members to participate in all related discussions, without necessarily having to be subscribed to the mailing lists.

So if you have anything to contribute to this topic, please do make sure to check out this new forum.

You are for example also invited to make suggestions for new FlightGear related GSoC projects.

For the time being, one topic from the "New Features" sub forum has already been moved to this new forum, it is about a suggestion to procedurally populate the FlightGear scenery with dynamically created cities, for more details please check out [[AutoGen Scenery for FlightGear]].

===Local weather system update===

The local weather system is moving towards dynamical weather. Currently, an experimental version v0.73 is released which demonstrates the cloud drift in the wind (see more information [http://www.flightgear.org/forums/viewtopic.php?f=5&t=7358 here]). The upcoming release v0.8 which is currently in the final stages of being prepared will include

* Drift of clouds, thermals and other weather effects in the wind, enabling for example a realistic soaring experience in strong winds.

* Several available models for the wind field, including high-altitude wind patterns that gradually change along the aircraft route.

* A moderately complex model for the boundary layer, i.e. the region where the wind field interacts with terrain. The boundary layer thickness and wind speed reduction effect becomes tied to the roughness of the terrain - for example over open water, the layer will be much thinner than in mountains.

* Significantly more efficient tile management routines and some code cleanup, resulting in a better performance also in static mode.

The planned extensions beyond v0.8 include making the generation and decay of convective clouds and thermals a dynamical process, migrating to high-resolution cloud textures and shifting some low-level functionality to the C++ core for better performance.

Did you know?

The local weather package has an inbuilt METAR interface which generates weather based on a parsed METAR string. However, it can't be used with --real-weather-fetch because currently FlightGear automatically executes fetched and parsed METAR, thus preventing the local weather package from working. Some help from C++ programmers needed here!

===New mapping software===
Michael contributes new FlightGear mapping software to the community, written in the Ruby programming language: [http://rubyforge.org/projects/fgmap FGMap]. Basically it shows your current flight position on an [http://openstreetmap.org OpenStreetMap] map. It therefore has some similarity to [[Atlas]] and the online [[MPMap]]s. As with all projects, [http://rubyforge.org/tracker/?func=add&group_id=9572&atid=37032 feedback] is highly appreciated.

FGMap has many features, including:
* Show flight position on OpenStreetMap map in real-time
* Download new map tiles on-the-fly in the background
* Add shaded elevation layer to map for nice visual effect
* Display current speed and altitude
* Show position and frequency of all navigation aids on the map
* Create FlightGear route manager entries with a click of the mouse from navigation aids and waypoints
* Record and restore flight path
* Colorize path according to speed and altitude
* Display information about instantaneous speed and altitude for all points of the track
* Set waypoints on map

Downloads and more information are available at [http://rubyforge.org/projects/fgmap the project's website].

===Troubleshooting ''triangleintersect, QNaN'' etc.===

Last month, the infamous [http://wiki.flightgear.org/index.php/Howto:_Get_rid_of_common_errors#Warning:_Picked_up_TriangleIntersect QNaN errors] that may cause FlightGear to become [[Showstoppers|unresponsive]] have been linked to potential issues in the Nasal interpreter (and more generally Nasal code) by flug, for more details please see: [http://www.flightgear.org/forums/viewtopic.php?f=18&t=8483&p=83701 "Nasal source of Dreaded Triangle Error-source of many probs?"].
For the time being, you will want to look out for any Nasal code that contains unchecked divisions with unvalidated divisors.

==In the hangar==
===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===De Havilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the FDM.

===SpaceShipOne and White Knight===
''helijah'' has made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

==Livery database==
In the second week of July, the [http://liveries.flightgear.org livery database] welcomed its [http://liveries.flightgear.org/liveries.php?id=251 250th livery]: a glider club's livery for the [[Robin DR400]], created by top-painter Brett Harrison (Gooneybird). More liveries are welcome as always and can be [http://liveries.flightgear.org/contribute.php uploaded]!

==Scenery corner==
===Animated jetways===
[[File:Movable_Jetway.jpg|thumb|A Jetway connecting to a [[Boeing 737-300|737-300]].]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

[[Image:Dubai_v0_vs_cs-osm.png|thumb|270px|Dubai, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Dublin scenery===
''eag1e'' created new terrain and buildings for Dublin airport (EIDW). For more details, see [http://flightgear.org/forums/viewtopic.php?f=5&t=8874 this link].

===Detailed terrain for Dubai===
As announced in an [[FlightGear Newsletter March 2010#Dubai is coming up|earlier edition]], Gijs has been (re)drawing the terrain of Dubai. The FlightGear scenery now includes:
* Palm Islands (islands in the shape of a palm)
* The World (islands together forming a world map)
* Detailed coastline and city boundaries
The area is represented in its form of 2008, due to the lack of more up-to-date imagery. Given Dubai's massive expansion speed, the scenery can be considered as out-of-date already. Nevertheless it is a great step forward in comparison to the previous terrain, as the image on the right proves.

This new terrain will be available with the upcoming scenery build. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].

[[Image:Qatar_v0_vs_cs-osm.png|thumb|270px|Qatar, with the new custom scenery data with OSM roads (left) and old vmap0 data.]]

===Detailed terrain for Qatar===
Believe it or not, but here is another Emirate that has been hand drawn! Fahim worked on the peninsula of Qatar, very close to Dubai. Seeing the image on the right, you might think detail/accuracy was lost (except for the urban areas), but I can tell you that the new terrain is far more accurate in all aspects.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver].

===Night flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modeled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

===Los Angeles International Airport (KLAX)===
''skyop'' has been improving the Los Angeles airport terminals and [[AI traffic]] XML files. See the progress [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8862 at the forum].

[[Image:Westfrisian_Islands.png|thumb|270px|Eastfrisian Islands, old vmap0 data (top) and the new custom scenery data (bottom).]]

===Improvement of Eastfrisian Islands, North Sea===

Mike ([[User:D-SKY1|D-SKY1]]) did his first steps in creating custom scenery. With great help from Fahim and Papillon81 he managed to improve Eastfrisian Islands ''Norderney, Baltrum, Langeoog and Wangerooge'', Northsea coast of Germany. With this improvement we close the gap between the enhanced dutch islands in the west and Helgoland in the east.

This new terrain will also be included with the upcoming scenery build and is already available via the [http://mapserver.flightgear.org mapserver]. Those that can handle [[TerraGear]] can download shapefiles from the [http://mapserver.flightgear.org mapserver]. If you are interested in updating or detailing terrain yourself, take a look at [[Howto: Create custom scenery|this wiki article]].
 
 
 
 
 

==Aircraft review==
'''This month: Bell P-59 Airacomet'''
[[Image:P59-1.jpg|thumb|270px|A P-59 buzzing the apron at KHND]]
The P-59 was the first American jet aircraft. Developed by the Bell company in response to the USAAF's requirement for a jet fighter. Although the Airacomet never saw combat, it was used to train many USAAF pilots in flying jet aircraft.

As usual, Helijah has done a fantastic job with the 3D model of the aircraft, and GIT users can take full advantage of the new fuselage reflection effect which Helijah has added to this model. The canopy opens and closes, and the pilot's head moves around. Although these features may seem insignificant, they do add to the overall experience of flying this already beautiful aircraft.
[[Image:P59-2.jpg|thumb|left|270px|Trying some aerobatics near KHND]]
There are, however, some minor issues with the 3D model. The model has afterburners, while the real P-59 did not, and tracers fired from the guns of this aircraft do not behave like their real life counterparts. (The muzzle velocities of the guns have not been modelled correctly)

The 3D cockpit contains the standard six instruments, which is enough to fly with, and the autopilot works, too.
The FDM seems to be fairly accurate, as the Airacobra should, and will reach 46,200 feet, and it can achieve and sustain a climb rate of 3,200 feet per minute.

==Nasal for newbies==
[[Nasal]] is the name of FlightGear's built in scripting language that allows people to easily create custom logics for adjusting and driving FlightGear internals without having to modify the C++ source code or recompile FlightGear.
To use Nasal you don't need to be a programmer, in fact Nasal is so simple that it can be used by people without any prior programming experience at all. Still Nasal is very powerful and flexible.

Nasal scripts can be used for doing many interesting things.
Some of the more recent examples being the bombable add-on, the local weather system or the seeking AI missiles, all of which are purely implemented as Nasal scripts.

You can see for yourself how easy it is to get started writing Nasal scripts:

Just create a new plain text file (using an editor like notepad on Windows) named "hello.nas" in the $FG_ROOT/Nasal directory, paste the following contents:

print("My first Nasal script !");

Watch the black shell window when starting FlightGear and you'll see the "My first Nasal script !" being printed to the console.
As you have surely noticed, all Nasal scripts in the $FG_ROOT/Nasal directory get loaded and run automatically during FlightGear startup.

The sample program just consists of one instruction, namely "print". Which is a function call to the built-in "print" function of the Nasal interpreter.
The print function can not only print strings, but also numbers or individual characters.

Function calls in Nasal always look like this:

name();

Where "name" would be the function's Nasal name, and then parentheses contain all parameters that you want to pass to the function. The expression is terminated using a semicolon.

To pass arguments to the function, you would simply add these in between the parentheses and separate them using a comma:

print(100, 200, 300);

==From the community==
===TransGear founder leaves===
Rob (MD-Terp), known by many as the founding father of the monthly [[TransGear]] events, [http://www.flightgear.org/forums/viewtopic.php?f=3&t=8809 announced] his "retirement" at the forum. With the first event being held just one month after the first edition of this newsletter, TransGear almost reached its first mileage. However, some former participants are discussing an option to continue organizing the event. More on that in a future edition.

We would like to thank Rob for all he has done, to wish him all the best, and deeply hope to see him return to the community one day.

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]