FlightGear wiki - User contributions [en]

Template:Gallery

2007-10-16T08:57:35Z

Cespenar:

{| border="0" style="width:720px"
|- style="height: 200px;"
{{Gallery single|aircraft={{{1|none}}}|picture={{{2}}}}}
{{Gallery single|aircraft={{{3|none}}}|picture={{{4}}}}}
{{Gallery single|aircraft={{{5|none}}}|picture={{{6}}}}}
{{Gallery single|aircraft={{{7|none}}}|picture={{{8}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{9|none}}}|picture={{{10}}}}}
{{Gallery single|aircraft={{{11|none}}}|picture={{{12}}}}}
{{Gallery single|aircraft={{{13|none}}}|picture={{{14}}}}}
{{Gallery single|aircraft={{{15|none}}}|picture={{{16}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{17|none}}}|picture={{{18}}}}}
{{Gallery single|aircraft={{{19|none}}}|picture={{{20}}}}}
{{Gallery single|aircraft={{{21|none}}}|picture={{{22}}}}}
{{Gallery single|aircraft={{{23|none}}}|picture={{{24}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{25|none}}}|picture={{{26}}}}}
{{Gallery single|aircraft={{{27|none}}}|picture={{{28}}}}}
{{Gallery single|aircraft={{{29|none}}}|picture={{{30}}}}}
{{Gallery single|aircraft={{{31|none}}}|picture={{{32}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{33|none}}}|picture={{{34}}}}}
{{Gallery single|aircraft={{{35|none}}}|picture={{{36}}}}}
{{Gallery single|aircraft={{{37|none}}}|picture={{{38}}}}}
{{Gallery single|aircraft={{{39|none}}}|picture={{{40}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{41|none}}}|picture={{{42}}}}}
{{Gallery single|aircraft={{{43|none}}}|picture={{{44}}}}}
{{Gallery single|aircraft={{{45|none}}}|picture={{{46}}}}}
{{Gallery single|aircraft={{{47|none}}}|picture={{{48}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{49|none}}}|picture={{{50}}}}}
{{Gallery single|aircraft={{{51|none}}}|picture={{{52}}}}}
{{Gallery single|aircraft={{{53|none}}}|picture={{{54}}}}}
{{Gallery single|aircraft={{{55|none}}}|picture={{{56}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{57|none}}}|picture={{{58}}}}}
{{Gallery single|aircraft={{{59|none}}}|picture={{{60}}}}}
{{Gallery single|aircraft={{{61|none}}}|picture={{{62}}}}}
{{Gallery single|aircraft={{{63|none}}}|picture={{{64}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{65|none}}}|picture={{{66}}}}}
{{Gallery single|aircraft={{{67|none}}}|picture={{{68}}}}}
{{Gallery single|aircraft={{{69|none}}}|picture={{{70}}}}}
{{Gallery single|aircraft={{{71|none}}}|picture={{{72}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{73|none}}}|picture={{{74}}}}}
{{Gallery single|aircraft={{{75|none}}}|picture={{{76}}}}}
{{Gallery single|aircraft={{{77|none}}}|picture={{{78}}}}}
{{Gallery single|aircraft={{{79|none}}}|picture={{{80}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{81|none}}}|picture={{{82}}}}}
{{Gallery single|aircraft={{{83|none}}}|picture={{{84}}}}}
{{Gallery single|aircraft={{{85|none}}}|picture={{{86}}}}}
{{Gallery single|aircraft={{{87|none}}}|picture={{{88}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{89|none}}}|picture={{{90}}}}}
{{Gallery single|aircraft={{{91|none}}}|picture={{{92}}}}}
{{Gallery single|aircraft={{{93|none}}}|picture={{{94}}}}}
{{Gallery single|aircraft={{{95|none}}}|picture={{{96}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{97|none}}}|picture={{{98}}}}}
{{Gallery single|aircraft={{{99|none}}}|picture={{{100}}}}}
{{Gallery single|aircraft={{{101|none}}}|picture={{{102}}}}}
{{Gallery single|aircraft={{{103|none}}}|picture={{{104}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{105|none}}}|picture={{{106}}}}}
{{Gallery single|aircraft={{{107|none}}}|picture={{{108}}}}}
{{Gallery single|aircraft={{{109|none}}}|picture={{{110}}}}}
{{Gallery single|aircraft={{{111|none}}}|picture={{{112}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{113|none}}}|picture={{{114}}}}}
{{Gallery single|aircraft={{{115|none}}}|picture={{{116}}}}}
{{Gallery single|aircraft={{{117|none}}}|picture={{{118}}}}}
{{Gallery single|aircraft={{{119|none}}}|picture={{{120}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{121|none}}}|picture={{{122}}}}}
{{Gallery single|aircraft={{{123|none}}}|picture={{{124}}}}}
{{Gallery single|aircraft={{{125|none}}}|picture={{{126}}}}}
{{Gallery single|aircraft={{{127|none}}}|picture={{{128}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{129|none}}}|picture={{{130}}}}}
{{Gallery single|aircraft={{{131|none}}}|picture={{{132}}}}}
{{Gallery single|aircraft={{{133|none}}}|picture={{{134}}}}}
{{Gallery single|aircraft={{{135|none}}}|picture={{{136}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{137|none}}}|picture={{{138}}}}}
{{Gallery single|aircraft={{{139|none}}}|picture={{{140}}}}}
{{Gallery single|aircraft={{{141|none}}}|picture={{{142}}}}}
{{Gallery single|aircraft={{{143|none}}}|picture={{{144}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{145|none}}}|picture={{{146}}}}}
{{Gallery single|aircraft={{{147|none}}}|picture={{{148}}}}}
{{Gallery single|aircraft={{{149|none}}}|picture={{{150}}}}}
{{Gallery single|aircraft={{{151|none}}}|picture={{{152}}}}}
|- style="height: 200px;"
{{Gallery single|aircraft={{{153|none}}}|picture={{{154}}}}}
{{Gallery single|aircraft={{{155|none}}}|picture={{{156}}}}}
{{Gallery single|aircraft={{{157|none}}}|picture={{{158}}}}}
{{Gallery single|aircraft={{{159|none}}}|picture={{{160}}}}}
|}
<noinclude>Template for an easy-to-maintain aircraft gallery. Current limit for number of aircrafts: '''80'''</noinclude>

Aircraft

2007-10-16T08:35:03Z

Cespenar: sorted case-insensitive

{{Gallery|
[[Airbus A300]]|A300.png|
[[Airbus A320]]|A320.jpg|
[[Airbus A330]]|A330.jpg|
[[Airbus A340]]|A340.jpg|
[[Airbus A380]]|A380.jpg|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Antonov AN-225]]|Antonov_AN-225.jpg|
[[Antonov An-2]]|Antonov_An-2.jpg|
[[ASW-20 sailplane]]|Asw20.jpg|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Beechcraft Model 99]]|Beech99.jpg|
[[Bell 206 JetRanger Helicopter]]|Bell_206.jpg|
[[Boeing 737]]|737-300.jpg|
[[Boeing 747]]|747.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[Cessna C172]]|Cessna_172P.jpg|
[[Cessna C182]]|Cessna_182.jpg|
[[Cessna C310]]|Cessna_C310.jpg|
[[Cessna T-37]]|Cessna_T-37.jpg|
[[CH-47 Chinook Helicopter]]|CH-47_Chinook.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Douglas A4 Skyhawk]]|Douglas_A4.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[Ecureuil AS 350 Helicopter]]|Ecureuil_AS_350.jpg|
[[Eurocopter EC135]]|Ec135.png|
[[Fairchild A-10]]|A-10.jpg|
[[Fokker 100]]|Fokker100.jpg|
[[Fokker 50]]|Fokker50.jpg|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Hawker Hunter]]|Hawker_Hunter.png|
[[Hawker Seahawk]]|Hawker_Seahawk.jpg|
[[Lockheed 1049]]|Lockheed_1049.jpg|
[[Lockheed F-104 Starfighter]]|Lockheed_F104.jpg|
[[McDonnell Douglas F-15 Eagle]]|McDonnell_Douglas_F-15.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg|
[[P-51D]]|P51d-mustang.png|
[[Paraglider]]|Paraglider.jpg|
[[Pilatus PC-7]]|Pilatus_PC-7.jpg|
[[Piper Cherokee Warrior II]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]]|Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II]]|Piper_SenecaII.jpg|
[[Saab J 35Ö Draken]]|Saab_J35.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[Siai Marchetti S.211]]|Siai_Marchetti_S211.jpg|
[[Soko J-22 Orao / IAR-93]]|J22.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Space Shuttle]]|Space_Shuttle.jpg|
[[Tupolev 154]]|Tu154.jpg|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg|
[[X24]]|X24.jpg}}

Template:Gallery

2007-10-16T08:27:08Z

Cespenar: reduced row height

{| border="0" style="width:720px"

|- style="height: 200px;"

{{Gallery single|aircraft={{{1|none}}}|picture={{{2}}}}}
{{Gallery single|aircraft={{{3|none}}}|picture={{{4}}}}}
{{Gallery single|aircraft={{{5|none}}}|picture={{{6}}}}}
{{Gallery single|aircraft={{{7|none}}}|picture={{{8}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{9|none}}}|picture={{{10}}}}}
{{Gallery single|aircraft={{{11|none}}}|picture={{{12}}}}}
{{Gallery single|aircraft={{{13|none}}}|picture={{{14}}}}}
{{Gallery single|aircraft={{{15|none}}}|picture={{{16}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{17|none}}}|picture={{{18}}}}}
{{Gallery single|aircraft={{{19|none}}}|picture={{{20}}}}}
{{Gallery single|aircraft={{{21|none}}}|picture={{{22}}}}}
{{Gallery single|aircraft={{{23|none}}}|picture={{{24}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{25|none}}}|picture={{{26}}}}}
{{Gallery single|aircraft={{{27|none}}}|picture={{{28}}}}}
{{Gallery single|aircraft={{{29|none}}}|picture={{{30}}}}}
{{Gallery single|aircraft={{{31|none}}}|picture={{{32}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{33|none}}}|picture={{{34}}}}}
{{Gallery single|aircraft={{{35|none}}}|picture={{{36}}}}}
{{Gallery single|aircraft={{{37|none}}}|picture={{{38}}}}}
{{Gallery single|aircraft={{{39|none}}}|picture={{{40}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{41|none}}}|picture={{{42}}}}}
{{Gallery single|aircraft={{{43|none}}}|picture={{{44}}}}}
{{Gallery single|aircraft={{{45|none}}}|picture={{{46}}}}}
{{Gallery single|aircraft={{{47|none}}}|picture={{{48}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{49|none}}}|picture={{{50}}}}}
{{Gallery single|aircraft={{{51|none}}}|picture={{{52}}}}}
{{Gallery single|aircraft={{{53|none}}}|picture={{{54}}}}}
{{Gallery single|aircraft={{{55|none}}}|picture={{{56}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{57|none}}}|picture={{{58}}}}}
{{Gallery single|aircraft={{{59|none}}}|picture={{{60}}}}}
{{Gallery single|aircraft={{{61|none}}}|picture={{{62}}}}}
{{Gallery single|aircraft={{{63|none}}}|picture={{{64}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{65|none}}}|picture={{{66}}}}}
{{Gallery single|aircraft={{{67|none}}}|picture={{{68}}}}}
{{Gallery single|aircraft={{{69|none}}}|picture={{{70}}}}}
{{Gallery single|aircraft={{{71|none}}}|picture={{{72}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{73|none}}}|picture={{{74}}}}}
{{Gallery single|aircraft={{{75|none}}}|picture={{{76}}}}}
{{Gallery single|aircraft={{{77|none}}}|picture={{{78}}}}}
{{Gallery single|aircraft={{{79|none}}}|picture={{{80}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{81|none}}}|picture={{{82}}}}}
{{Gallery single|aircraft={{{83|none}}}|picture={{{84}}}}}
{{Gallery single|aircraft={{{85|none}}}|picture={{{86}}}}}
{{Gallery single|aircraft={{{87|none}}}|picture={{{88}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{89|none}}}|picture={{{90}}}}}
{{Gallery single|aircraft={{{91|none}}}|picture={{{92}}}}}
{{Gallery single|aircraft={{{93|none}}}|picture={{{94}}}}}
{{Gallery single|aircraft={{{95|none}}}|picture={{{96}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{97|none}}}|picture={{{98}}}}}
{{Gallery single|aircraft={{{99|none}}}|picture={{{100}}}}}
{{Gallery single|aircraft={{{101|none}}}|picture={{{102}}}}}
{{Gallery single|aircraft={{{103|none}}}|picture={{{104}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{105|none}}}|picture={{{106}}}}}
{{Gallery single|aircraft={{{107|none}}}|picture={{{108}}}}}
{{Gallery single|aircraft={{{109|none}}}|picture={{{110}}}}}
{{Gallery single|aircraft={{{111|none}}}|picture={{{112}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{113|none}}}|picture={{{114}}}}}
{{Gallery single|aircraft={{{115|none}}}|picture={{{116}}}}}
{{Gallery single|aircraft={{{117|none}}}|picture={{{118}}}}}
{{Gallery single|aircraft={{{119|none}}}|picture={{{120}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{121|none}}}|picture={{{122}}}}}
{{Gallery single|aircraft={{{123|none}}}|picture={{{124}}}}}
{{Gallery single|aircraft={{{125|none}}}|picture={{{126}}}}}
{{Gallery single|aircraft={{{127|none}}}|picture={{{128}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{129|none}}}|picture={{{130}}}}}
{{Gallery single|aircraft={{{131|none}}}|picture={{{132}}}}}
{{Gallery single|aircraft={{{133|none}}}|picture={{{134}}}}}
{{Gallery single|aircraft={{{135|none}}}|picture={{{136}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{137|none}}}|picture={{{138}}}}}
{{Gallery single|aircraft={{{139|none}}}|picture={{{140}}}}}
{{Gallery single|aircraft={{{141|none}}}|picture={{{142}}}}}
{{Gallery single|aircraft={{{143|none}}}|picture={{{144}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{145|none}}}|picture={{{146}}}}}
{{Gallery single|aircraft={{{147|none}}}|picture={{{148}}}}}
{{Gallery single|aircraft={{{149|none}}}|picture={{{150}}}}}
{{Gallery single|aircraft={{{151|none}}}|picture={{{152}}}}}

|- style="height: 200px;"

{{Gallery single|aircraft={{{153|none}}}|picture={{{154}}}}}
{{Gallery single|aircraft={{{155|none}}}|picture={{{156}}}}}
{{Gallery single|aircraft={{{157|none}}}|picture={{{158}}}}}
{{Gallery single|aircraft={{{159|none}}}|picture={{{160}}}}}

|}

<noinclude>Template for an easy-to-maintain aircraft gallery. Current limit for number of aircrafts: '''80'''</noinclude>

Aircraft

2007-10-16T08:25:15Z

Cespenar:

{{Gallery|
[[ASW-20 sailplane]]|Asw20.jpg|
[[Airbus A300]]|A300.png|
[[Airbus A320]]|A320.jpg|
[[Airbus A330]]|A330.jpg|
[[Airbus A340]]|A340.jpg|
[[Airbus A380]]|A380.jpg|
[[Airwave Xtreme 150]]|AirwaveXtreme150.jpg|
[[Antonov AN-225]]|Antonov_AN-225.jpg|
[[Antonov An-2]]|Antonov_An-2.jpg|
[[BAC TSR-2 Prototype]]|BAC_TSR-2_Prototype.jpg|
[[Beechcraft Model 99]]|Beech99.jpg|
[[Bell 206 JetRanger Helicopter]]|Bell_206.jpg|
[[Boeing 737]]|737-300.jpg|
[[Boeing 747]]|747.jpg|
[[Boeing B-52]]|B-52F.jpg|
[[British Aerospace Harrier]]|Harrier.jpg|
[[CH-47 Chinook Helicopter]]|CH-47_Chinook.jpg|
[[Cessna C172]]|Cessna_172P.jpg|
[[Cessna C182]]|Cessna_182.jpg|
[[Cessna C310]]|Cessna_C310.jpg|
[[Cessna T-37]]|Cessna_T-37.jpg|
[[ComperSwift Comper]]|ComperSwift.jpg|
[[Douglas A4 Skyhawk]]|Douglas_A4.jpg|
[[Douglas DC-3]]|Douglas_DC3.jpg|
[[Ecureuil AS 350 Helicopter]]|Ecureuil_AS_350.jpg|
[[Eurocopter EC135]]|Ec135.png|
[[Fairchild A-10]]|A-10.jpg|
[[Fokker 100]]|Fokker100.jpg|
[[Fokker 50]]|Fokker50.jpg|
[[Fokker Dr.I]]|Fokker_DrI.jpg|
[[General Dynamics F-16]]|General_Dynamics_F16.jpg|
[[Hawker Hunter]]|Hawker_Hunter.png|
[[Hawker Seahawk]]|Hawker_Seahawk.jpg|
[[Lockheed 1049]]|Lockheed_1049.jpg|
[[Lockheed F-104 Starfighter]]|Lockheed_F104.jpg|
[[McDonnell Douglas F-15 Eagle]]|McDonnell_Douglas_F-15.jpg|
[[North American OV-10A Bronco]]|OV-10A2.jpg|
[[North American X-15]]|X15.jpg|
[[Northrop T-38]]|Northrop_T-38.jpg|
[[Northrop/McDonnell Douglas YF-23]]|YF-23.jpg|
[[P-51D]]|P51d-mustang.png|
[[Paraglider]]|Paraglider.jpg|
[[Pilatus PC-7]]|Pilatus_PC-7.jpg|
[[Piper Cherokee Warrior II]]|Piper_Cherokee_Warrior_II.png|
[[Piper J3 Cub]]|Piper_j3cub.jpg|
[[Piper PA34-200T Seneca II]]|Piper_SenecaII.jpg|
[[Saab J 35Ö Draken]]|Saab_J35.jpg|
[[Schweizer 2-33]]|Sgs233.jpg|
[[Siai Marchetti S.211]]|Siai_Marchetti_S211.jpg|
[[Soko J-22 Orao / IAR-93]]|J22.jpg|
[[Sopwith Camel]]|SopwithCamel.jpg|
[[Space Shuttle]]|Space_Shuttle.jpg|
[[Tupolev 154]]|Tu154.jpg|
[[UFO from the 'White Project' of the UNESCO]]|UFO.jpg|
[[Wright Flyer (UIUC)]]|1903_Wright_Flyer.jpg|
[[X24]]|X24.jpg}}

Howto:Submit patches

2007-10-16T08:19:34Z

Cespenar: cat

=== Patch Guidelines ===

Any invasive or non-trivial patches should preferably adhere to the following recommendations:

* Search the [http://sourceforge.net/mailarchive/forum.php?forum_id=1919 flightgear-devel list archives] ([http://www.flightgear.org/mail.html old]) for any relevant discussion and then post to the flightgear-devel mailing list describing your idea and discussing the scope of effort required.

* Try to make your patch optionally minimally invasive:
** provide compile time switches to generally enable or disable your modifications (i.e. using #ifdefs, [http://sources.redhat.com/autobook/ autoconf and automake] macros) That way, you will ensure that your patch can be easily disabled (excluded from compilation while remaining in the source tree) if it should cause trouble while any issues are addressed. This applies in particular if your patch introduces any extra dependencies (i.e. libraries).
** provide capabilities to enable or disable your code modifications at startup time or even at runtime, using command line options or preferably the PropertyTree and some simple GUI dialog to enable developers and users to decide whether they want to activate your code. That way, it can be ensured that your code doesn't interfere with any other FlightGear components. This will make potential bug tracking much easier.

* Try to carefully document those passages in your source code that:
** are non-obvious
** are hackish or workarounds
** use code where you yourself aren't entirely sure if you're doing the right thing
** are known to negatively interfere with other FlightGear code

* Try to make sure that your code isn't platform-specific. Hence, it is generally a good idea to make any contributions as cross-platform capable as possible

* If you need to print output to the terminal, make sure to use the SG_LOG logging mechanism, using the appropriate log level. Use this command sparingly, as excessive logging information has negative impact on framerate, especially on some platforms. When committing a patch, make sure you have either removed or commented out any cout or cerr statements that you have used during private debugging sessions.

=== Patch Format ===
TODO: unified diff vs. tarball (compressed archives)

=== Howto Create Patches ===

'''fg-submit script'''

As of March 2007, a bash script "fg-submit" is available that simplifies the preparation of patches that are to be submitted for commit. It can be found in '/source/scripts/tools'. It compares your changes to cvs, creates a diff file and an archive containing your changed files and the diff file. Run this script from within the CVS directory containing your changes. It's output will go to that same directory.

fg-submit should work with any flavor of Unix/Linux. Windows users may use this script from within a Cygwin bash shell, assuming the necessary Devel tools have been installed.

Usage:

$ cd $FG_ROOT/Aircraft/foo

$ fg-submit

'''TODO:'''

links to diff/patch tutorials
link to diff/patch utilities for various platforms

recommended: KDiff3 (QT based cross platform, GUI frontend to GNU diff/patch)
http://kdiff3.sourceforge.net

=== Where to Send Patches ===

'''Developers with CVS access :'''

'''FlightGear developer mailing list(subscription required)'''

(any non-trivial or larger patches should preferably not be sent by email, but rather made available by putting a tarball of your patch on some free webspace, so that people can simply download your patch if they are interested

[[Category:Development]]

Code cleanup

2007-10-16T08:18:47Z

Cespenar: cat

The purpose of this page is to provide a todo-list or check-list for anyone that wants to help clean up the Flightgear (FG) code. In addition to this list, you also want to try running FG in Valgrind, a very powerful memory debugger and profiler. http://freshmeat.net/projects/valgrind/

'''Feel free to add additional items to this page'''

Thanks -- Cameron Moore

== Major Task List ==

* Move code out of fgMainLoop() and into separate functions or source files.
* Replace system() calls in simgear/io/sg_binobj.cxx to `mkdir`
* Replace system() call in simgear/io/sg_binobj.cxx to `gzip`
* Allow aircraft to be reliably changed at runtime, without requiring a restart of FlightGear
* Implement scenery support for dynamic LOD configuration at runtime
* Optimize the 3D panel code and optionally support display list usage
* Add OpenGL bindings to the scripting language Nasal to support scripted creation of instruments like the HUD

== Persistent Checklist ==

=== Carelessness ===
* Properly allocate and deallocate memory using malloc/new/new[{][}] and free/delete/delete[{][}]. Valgrind is helpful when looking for these.

* Close any open file streams when you're through with them. Take care to not write to or close streams that aren't open. Avoid this by initializing file pointers/handles with 0 before use and verify that it is not 0 before accessing/closing.

=== Compatibility ===

* Use the SG_LOG() facilities instead of cout and printf().
* Use the SG_USING_STD() facilities instead of explicitly using std::function.
* Use the STL_* variables defined in simgear/compiler.h when including STL headers.
* When including header files, only use double-quotes when the header is in the same directory.

=== Security ===

* Use C-string functions with fixed write buffers whenever possible to avoid buffer overflows.

* Perform range/bounds checks on all data received from remote that could cause problems, especially those that specify an amount of data to be handled.

For example, use snprintf() instead of sprintf() and strncpy() instead of strcpy().

And please do not forget that snprintf and strncpy does not necessarily add a trailing 0 byte.

[[Category:Development]]

Technical Reports

2007-10-16T08:17:24Z

Cespenar: cat

__NOEDITSECTION__
The intention of this page to provide a place where people can publish their FlightGear-related technical reports. Such reports may include essays on technical issues within FlightGear, and reports on scientific experiments performed on/with FlightGear. Please note that technical reports are formal papers. They follow a proper structure and are not intended to be opened for editing.

For a more in-depth definition of technical reports, please follow [http://en.wikipedia.org/wiki/Technical_report this link].

=2006=
==March==
=== A New Architecture for FlightGear Flight Simulator ===

''AJ MacLeod, Ampere K. Hardraade, Michael Koehne, Steve Knoblock''

'''Keyword(s)''': MVC architecture; FDM Server; FDM Instance; Client

'''Abstract''': To continue improving existing features and add new ones, FlightGear must make better use of computing power. Preparing for the widespread adoption of multicore CPU architectures is an important step in FlightGear's development. Today, CPU clock rate has reached its peak. The old idea, that features can be added without regard to their effect on performance because computers will become ever faster, has ceased to hold. In addition, as more features are added, developers are inceasingly bumping up against existing limitations in the current FlightGear architecture. Now would be a good time to begin the process of restructuring FlightGear to address the above issues. This proposal decribes a new architecture for FlightGear, one which would greatly improve FlightGear's efficiency and flexibility by making extensive use of parallel processing. It is also hope that this new architecture will improve the quality of multiuser sessions, as well as providing a true support for the simulations of time-critical systems.

9 Pages

'''Full document''':
[[Media:New_FG_architecture.pdf]] (pdf)

[[Category:Development]]

Main Page

2007-10-16T08:11:19Z

Cespenar: better table

__NOTOC__
__NOEDITSECTION__
'''FlightGear''' Flight Simulator project is an open-source, multi-platform, cooperative flight simulator development project. Source code for the entire project is available ([http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/?cvsroot=FlightGear-0.9#dirlist CVS repository]) and licensed under the [http://www.gnu.org/copyleft/gpl.html GNU General Public License].

The goal of the '''FlightGear''' project is to create a sophisticated flight simulator framework for use in research or academic environments, for the development and pursuit of other interesting flight simulation ideas, and as an end-user application. We are developing a sophisticated, open simulation framework that can be expanded and improved upon by anyone interested in [[Volunteer|contributing]].

There are many exciting possibilities for an open, free flight sim. We hope that this project will be interesting and useful to many people in many areas.

'''FlightGear''' comes with a set of illustrated documentation, notably
"The Manual", which is available as
[ftp://ftp.de.flightgear.org/pub/fgfs/Docs/getstart.pdf PDF] and
[http://www.flightgear.org/Docs/getstart/getstart.html HTML]. If you
prefer to follow the 'bleeding edge' set of FlightGear instructions,
then the following articles are likely to make you happy. You will
notice that parts of this Wiki duplicate information that's already
present in "The Manual".

{|
| valign="top" |
== User Documentation ==
=== Getting Started ===
* [[ New to FlightGear ]]
* [[ Why FlightGear ]]
* [[ Features ]]
* [[ FAQ ]]
* [[ Hardware Recommendations ]]
* [[ Recommended Software ]]
* [[ Troubleshooting Problems ]]
* [[ Volunteer ]]
* [[ Real Life Experience ]]
=== Configuring Flightgear ===
* [[ Command Line Parameters ]]
* [[ Installing Scenery ]]
* [[ Improving Framerates ]]
* [[ Multiplayer Howto ]]
* [[ Linux software audio mixing with FlightGear ]]
=== Using Flightgear ===
* [[Aircraft]]
* [[ Suggested Flights ]]
* [[ Starting in the Air ]]
* [[ Instant Replay ]]
* [[ Preset Properties ]]
* [[ Realism ]]
* [[ Flying the Helicopter ]]
* [[ Doing aerotow over the net ]]
=== Interactive Scenarios ===
* [[ Carrier Howto ]]
* [[ Air-Air Refueling Howto ]]
* [[ AI Systems ]]
* [[ Interactive Traffic ]]
* [[ Soaring ]]
=== Flying Resources ===
* [[ Definitions Acronyms ]]
* [[ Getting IFR Charts ]]
* [[ Understanding Altitude ]]
* [[ Understanding Navigation ]]
* [[ Understanding Propeller Torque and P-Factor ]]
* [[ Understanding Aerodynamics ]]
* [[ Communications ]]
* [[ Weather ]]
* [[ Avionics and Instruments ]]
* [http://www.wingfiles.com/ Everything you need ]
* [http://www.faa.gov/library/manuals/ FAA Handbooks & Manuals]
| width="20px" |
| valign="top" |
== Developer Documentation ==
=== Compiling ===
* [[ Building Flightgear ]]
* [[ Building Flightgear - Windows]]
* [[ Building Terragear ]]
* [[ OpenSceneGraph ]]
* [[ Building FlightGear Launch Control ]]
=== Contributing ===
* [[ Submitting Patches ]]
* [[ Code Cleanup ]]
* [[ Development Resources ]]
* [[ Extension Support ]]
* [[ Technical Reports ]]
* [[ Changes since 0.9.10 ]]
=== Code Internals ===
* [[ Property Tree ]]
* [[ Subsystems ]]
* [[ UML Diagrams ]]
* [[ Commands ]]
* [[ FDM API ]]
* [[ Nasal scripting language ]]
* [[ File Formats ]]
* [[ Initialization Sequence ]]
=== Modeling ===
* [[ Modeling - Getting Started ]]
* [[ Modelling - FAQ ]]
* [[ Model Import and Export ]]
* [[ Modeling Resources ]]
* [[ Autopilot Tuning Resources ]]
* [[ Aircraft Information Resources ]]
* [[ Blender Ground Signs Tutorial]]
* [[ Normals and Transparency Tutorial ]]
* [[ Creating_instruments_for_FG ]]
* [[ Writing_simple_scripts_in_%22nasal%22 ]]
=== Todo ===
* [[ Long Term Goals ]]
* [[ Bugs ]]
* [[ FGFS Todo ]]
* [[:Category:Aircraft TODO]]
* [[ Feature Requests / Proposals / Ideas ]]
* [[ FlightGear Expo Checklist ]]
=== Miscellaneous ===
* [[ Glass Cockpit Projects ]]
* [[ Tutorial Resources ]]
* [[ Copyright Inquiry ]]
* [http://www.cafepress.com/fgfs_gear FlightGear - Gear]
* [[Resources]]
* [[ Sign Specification Proposal ]]
|}

Howto:Modeling Ground Signs with Blender

2007-10-16T08:06:33Z

Cespenar: cat

=== Flightgear: ground markings at the airport with Blender and XML ===

''2006-06-22''

''Roberto Inzerillo robicd at gmx dot net''

''Blender v.2.40''

''Tutorial Files (right click: Save Link As)''
* [[Media:catii-iii.ac|catii-iii.ac]]
* [[Media:catii-iii.blend|catii-iii.blend]]
* [[Media:catii-iii.xml|catii-iii.xml]]
* [[Media:catii-iii.rgb|catii-iii.rgb]]

There comes a time when you want to add a few details to an airport in order to improve realism to your flight experience. Every flight start (and ends) at the ground, on the airfield. You generally wont spend too much time there, you will immediately start at the beginning of a runway and be on air in a few seconds. But there are people who like learning how to move on the ground too, and learn how to maneuver their aircraft inside the airport. Well, in this case, having good ground signs/markings on the ground is mandatory, because most of the guiding has to be found there.

Every pilot should know what ground signs to pay attention to during every phase of the maneuvering, prior to reach the runway start. There are paintings on the ground, taxi signs on the side of each runway/taxiway, you have to care about tower radio communications and so on. Here you will learn how to build custom ground markings, the one that are painted on the ground and tell you usefull informations about what you can and cannot do during your ground maneuvering.

=== Holding position markings for CAT II/III operations ===

This lesson will teach you how to create a basic ground marking, the one that informs the pilot he has to hold during CAT II/III operations to ensure proper aircraft separation. There are generally a few taxiway signs too, which helps locating those areas also. CAT II/III separation is not that big issue within Flightgear, there's still no automatic ground traffic management, and aircraft crashing is not very expensive; but this is a real ground marking, and we will concentrate on the modelling phase, not on the functional aspects of that sign.

There is no way Flightgear could position those ground markings in an automatic way. There is no database telling where they are and how do they look like. Each airport customizes ground markings position/orientation in order to get maximum efficiency and to help pilots getting correct informations without filling the ground with too much of them. Rationalizing communication effectiveness is vital to an airport. Therefore you will create and position them manually.

When looking from the air, those CAT II/III markings look like this:

[[Image:catii-iii_markings_html_6961c87a.jpg]]

They are generally put in the middle of the runway, following the taxiway yellow line, just before the CAT II/III operations area. Here the pilot has to stop and wait for directives coming from the ATC.

It's a simple red square with a big white CAT II/III writing, it's a lot stretched so that when looking from the aircraft, taxing over there, it looks quite proportional.

=== Modelling the marking with Blender ===

That's very easy, it's a simple textured rectangle. First thing you need is the correct measurements and a nice texture to put on it. I will create this example with the same measures used at EDDF Frankfurt airport. The rectangle is 8m wide and 7m high.

I will not explain how to paint the texture because it's trivial, just make use of your preferred painting software, I used The Gimp for this one, save the file as a .rgb format, and make shure its size (pixel resolution, not bytes) is a multiple of 8, otherwise Flightgear will not load it. Here you see a JPG version of the texture as an example, download catii-iii.rgb to get the RGB version you need for texturing, it has 512x512 pixel resolution. You can use smaller ones (ex. 128X128) if you think this resolution is too high.

[[Image:catii-iii_markings_html_m11bd5b93.jpg]]

Modelling the rectangle with Blender is trivial.

Open Blender; from the main menu choose Add -> Mesh -> Plane

This add a 2units width square plane.

Our ground painting is 8m x 7m rectangle, we have to change the square dimensions.

Enter Object mode. Object -> Transform Properties

The Transform Properties window appears. Set “Size X : 4” and “Size Y: 3.5”.

Notice here that the object name is “Plane” (OB: Plane), we will use this information later.

[[Image:catii-iii_markings_html_m352e2670.jpg]]

Now you come to the texturing phase. Split the top window in two, and select UV/Image Editor for the right panel:

[[Image:catii-iii_markings_html_39a834a0.jpg]]

In the 3D View window, select UV Face Select mode, the rectangle face should be still selected, if not, select it by right clicking on the rectangle. Now, while the mouse is in the 3D View window, make shure it's a top view (Numpad 7), hit the U key, and select “From window”.

Now it's time to load the texture file. Inside the right panel, choose Image -> Open ... select the file catii-iii.rgb and hit Open Image.

[[Image:catii-iii_markings_html_m41735d75.jpg]]

We have to move the rectangle UV vertices in order to make the texture cover the entire rectangle geometry. We will now work in the UV/Image Editor window. Make shure “UVs -> Snap to Pixel” is set, that will make our life easier. Hit the B key, click and drag the mouse around the left down corner in order to select it. We are not working on the 3d model, we are working on the Uvs, that's why the rectangle in the left window maintains its geometry. Once the vertex is selected, hit the G key (Grab mode) and drag the vertex to the bottom left.

[[Image:catii-iii_markings_html_m3011a2ff.jpg]]

You will need to zoom in a little bit in order to position it precisely, use the CTRL-MMB (MMB = Middle Mouse Button) to zoom in and out, use the SHIFT+MMB to drag the view around. Hit G again, and move the UV vertex in the right position. While doing this, you can select the Textured Draw Mode and interactively see what's happening.

[[Image:catii-iii_markings_html_3b879144.jpg]]

You can select and deselect all UV vertices hitting the A key.

Now hit the A key to deselect the UV vertex; zoom out, hit B, by clicking and dragging select a new UV vertex, hit G and move it with the mouse to the correct position. Then do the same with the remaining two vertices. You will end up with the texture perfectly matching the geometry border:

[[Image:catii-iii_markings_html_3283723d.jpg]]

Now you can go back to Object Mode, make shure the object is selected and export it as AC3D formatted file.

File -> Export -> AC3D (.ac) ... enter a filename and hit “Export AC3D”.

The 3d model is ready and you can place it into your airport scenery right now. Make use of Flightgear Scenery Designer, the UFO object placing capability or whatever method you prefer.

Result being:

[[Image:catii-iii_markings_html_5db04368.jpg]]

[[Image:catii-iii_markings_html_m1758ae9f.jpg]]

We will go further and add a few details using an XML file which will describe peculiar attributes of such an object.

=== Customizing object's attributes into Flightgear using XML ===

We have three little details here that can be annoying.

1) If you activate Shadow into Flightgear and fly very close (let's say 10meters) to those CAT II/III markings, you will notice that they cast a shadow underneath, especially if the plane has been positioned more then 20cm above the ground. This is not good at all because that should represent a painting on the ground (that could not cast any shadow, there should be no free space between the painting and ground) and a useless shadow consumes GPU power too, which is not desired.

2) If you maneuver an aircraft on the ground, right above the marking, you will notice that the aircraft hits it with the wheels, and jumps a little, just like it encountered an obstacle on the ground. That is not good again, the painting should not oppose any resistance to any ground movement.

3) If you fly high above the airport area you will not really see those little red rectangles, they are too small to be noticed from a height. Nonetheless, Flightgear will still render those little objects on the ground and consume GPU power without really giving any advantage to the simulation experience. That should be avoided, we need to make Flightgear render those markings only when the aircraft is near enough to make them visible to the pilot.

We will eliminate those three cons creating a XML file that covers the issues. Please refer to Flightgear docs in order to get more informations about the usage of the XML markup language used.

You can use any text editor you prefer, fill a new empty text file with the following content and save it as catii-iii.xml in the same directory with catii-iii.ac and catii-iii.rgb.

<PropertyList>
<path>catii-iii.ac</path>

<animation>
<type>noshadow</type>
<object-name>Plane</object-name>
</animation>

<animation>
<object-name>Plane</object-name>
<enable-hot type="bool">false</enable-hot>
</animation>

<animation>
<type>range</type>
<object-name>Plane</object-name>
<min-m>0</min-m>
<max-property>/sim/rendering/static-lod/detailed</max-property>
</animation>

</PropertyList>

The <path>catii-iii.ac</path> statement means that all this refers to the 3d object file named catii-iii.ac.

Every animation transformation here applies to the the object called “Plane” inside the catii-iii.ac file (which is our marking rectangle). We could have more then one object inside the .ac file and decide which should cast a shadow and which not. Our example is very simple though, but still this statement has to be included.

1) The first “animation” transformation tells Flightgear not to apply any shadow to it.

2) The second “animation” tells Flightgear not to consider the object “Plane” as an obstacle, so any vehicle will not hit it.

3) The third “animation” tells Flightgear to render the object “Plane” only if the distance between it and the viewer is more then 0 meters and less then the value stored in Flightgear tree with the name /sim/rendering/static-lod/detailed. This value is a number that can be user customized; the default value is 1500m. When the object is more then 1500 meters distant, Flightgear will not render it; at such a distance you barely see a 8m x 7m square painting on the ground.

Now, insert the 3d object into your scenery but do not use the .ac file, make use of the .xml file instead; it will call the corresponding .ac file when needed. The following snapshot includes the yellow ILS critical area boundary stripes and the taxiway A ground marking which I made using the same technique, the only difference being those have partially transparent texture file.

[[Image:Ground_marking_full_example.jpg]]

=== Adding some realism to the texture ===

Aircraft and ground vehicles do move above those markings, that makes them dirty after a short while. I like adding a touch of realism to the textures I use into my Flightgear models. Adding some dirt to the ground marking is pretty easy. I'll show you how to modify the texture with The Gimp, you can use similar techniques with every common graphic editor.

Open up Gimp and load the file catii-iii.rgb

Create a new layer by SHIFT clicking on the left button of the Layers Dialog Box:

[[Image:catii-iii_addon_html_21146099.jpg]]

In the image window, go to: Filters -> Render -> Clouds -> Plasma ...

You can customize the Clouds rendering settings in order to get a nicely random cloud rendering. Now, you just use what I suggest in the picture and hit OK. It does not matter if it looks colored now, we will convert to greyscale and use the light values only to add some noise to the underlaying layer.

[[Image:catii-iii_addon_html_1dad0e33.jpg]]

You will get this in your image window.

[[Image:catii-iii_addon_html_m30fea806.jpg]]

Erase the saturation with: Layer -> Colors -> Desaturate

[[Image:catii-iii_addon_html_7db38b6e.jpg]]

Return to the Layers dialog box, change the clouds layer mode to Multiply and the Opacity to 40.

[[Image:catii-iii_addon_html_54e9cda0.jpg]]

I also tend not to use huge texture files, that's why I rescale it to smaller resolution; keep in mind that we need it to be a multiple of 8; in this case I decided a 256x128pixel resolution would look good enough. In the image window: Image -> Scale Image ...

[[Image:catii-iii_addon_html_23b912fa.jpg]]

Unlock the resolution proportion constrains by clicking on the little chains at the right of the Image Size resolution boxe (the chain opens up in two pieces), then set Width:256, Height:128 and hit Scale.

[[Image:catii-iii_addon_html_m19c5fb92.jpg]]

Now the image is ready to be saved with RGB format as usual, and can replace the old one. The result in Flightgear looks more realistic then the previous one, that bit of dirt smooths out the visual break caused by the perfectly clean texture used before. It integrates better with the surrounding taxiway texture.

[[Image:catii-iii_addon_html_a5eaae.jpg]]

I hope you will enjoy this little lesson. Consider this as an example, because there are a lot more things to do with the XML animations provided by Simgear to Flightgear.

[[Category:Modeling]]

Normals and Transparency Tutorial

2007-10-16T08:06:19Z

Cespenar: cat

=== Blender and AC3D: Normals, Single and Double-sided faces, Transparency ===

''2006-06-19''

''Roberto Inzerillo robicd at gmx dot net''

''Blender v.2.41 - AC3D Exporter v. 2.37a - AC3D 5.0.21''

''Tutorial Files (right click: Save Link As)''
* [[Media:box.ac|box.ac]]
* [[Media:box.blend|box.blend]]
* [[Media:Schermo.blend|schermo.blend]]
* [[Media:Schermo2.blend|schermo2.blend]]
* [[Media:Schermo3.ac|schermo3.ac]]

These short notes are aimed at providing new Blender users with a few ideas about how to work with Face-Normals and Transparency, keeping in mind what happens when you convert the model to AC3D file format in order to use it inside FlightGear.

=== Blender ===

As a first example I created a box, I removed its upper face, so I ended up with a 5 sided (A,B,C,D and E) box. That way I can look inside it.

Every face has a Normal vector that tells Blender where the face “faces”. While in Edit Mode, hit F9 (Editing), then you hit the Draw Normals buttons inside the Mesh Tools 1 panel in order to make the face Normals appear. They are short blue lines, starting from each face. I increased the Normal vector's dimension to 1.5 (NSize: 1.500) otherwise they would be too small. With default settings Blender does not display the normals.

Here you can download the [[Media:box.blend|box.blend]] file.

[[Image:blender-ac3d-normals_html_m74d3a410.jpg]]

In order to help our minds understand what normals can be, we could think each 3d face having an inside and an outside. E.g. a closed box has 6 faces, each having a side that faces the inner part of the box and a side facing outwards. In this case, each face has the normal vector pointing outwards. We consider the outer sides the positive one.

In this example I changed things a little bit. I erased the upper face and I changed face B normal vector direction. Originally, it pointed outwards like faces A,C,D and E. Now face B normal vector points inside the box.

For each face we have two sides. We will call Positive the side pointing in the normal's direction. We will call Negative the side pointing in the opposite direction.

Now, remember that in order to see normals you have to be in Edit Mode. While in Object Mode you can't see them.

[[Image:blender-ac3d-normals_html_6305e44f.jpg]]

=== AC3D ===

I exported the box to a [[Media:box.ac|box.ac]] file, in order to get you an idea how things work with other modelling software. In this case I used the AC3D file format because FGFS uses AC3D files very often, and there are a couple of things you should know about that.

[[Image:blender-ac3d-normals_html_1aa54ede.jpg]]

First thing you will notice is that while in Blender you see all faces' sides, in AC3D you see just one side of them. At first sight the exported 3d object looks messed up. Well, it's not. It's just that the AC3D eporter plugin does a conversion, result being each face of the object having a side which is transparent and the other one visible. The visible side of the face is the positive one (remember: Normal's direction). When looking at the same face from the other side, it becomes transparent.

Take a look at Face A. The face's normal was pointing to the viewer, and the face result being visible. Faces B,C,D,E all have normals pointing in the opposite direction. You can't see them, they become transparent. You have to rotate the object in order to see faces B,C,D and E. Only the positive side of each face is visible.

That's the basic behaviour of Blender and AC3D but you can customize a lot of things, as you wish.

=== Blender ===

There's a way to make Blender consider a face to be visible from both sides: you use the material property called “Double Sided” (which is set by default). But why (if that's the default) we got one-sided faces in our AC3D exported box? That's because the AC3D exporter plugin does not take into account this material attribute, it simply discards it.

[[Image:blender-ac3d-normals_html_29135093.jpg]]

But there's another setting that influences how each face is visible to the user. This is hidden inside the UV Face Select mode, default being Twosided not set. This basically affects the UV mapping process inside Blender.

[[Image:blender-ac3d-normals_html_m18adee58.jpg]]

As you see, while in UV Face Select mode you have the same view as with AC3D, you only see positive faces' sides (in this case only face A) only, the others are rendered as being transparent.

You can change this, by selecting a face and hitting the Twosides button, this will make the face visible from both directions, and you get a bonus with that: after exporting the model to AC3D format, this face will be two-sided in AC3D file also.

That's the basic way you can get double-sided faces (i.e. faces which are visible from both directions) into an .ac file from within Blender. Otherwise you will always end up having one-sided faces objects in your .ac files.

Basic behaviour of the Blender AC3D eporter plugin is to not consider the Material Attribute ”Double Sided” at all. The exporter reads the Twosided attribute instead, and sets those faces regardless this attribute. Since Twosides is off by default, the AC3D exporter plugin will export each face as one sided (i.e. only the positive side of each face will be visible) unless you change that manually.

=== Working pipeline ===

Creating an AC3D file for FGFS is very simple, customizing face visibility could be tricky; nonetheless, once you know how to do, it will be very easy.

I'll explain here how to customize polygon object's faces visibility, ready to be exported by the AC3D exporter plugin (i.e. making a few of them visible from both sides and letting the others be visible from one side only). That's needed inside FGFS sometime.

I start with a basic polygon object in Blender. The file is [[Media:schermo.blend|schermo.blend]].

[[Image:blender-ac3d-normals_html_m287d4e3f.jpg]]

As you see, the polygon object has a basic material, a default Doublesided one, but in UV Face Select mode you only see the positive sides; when looking from back they become transparent. Exporting this to AC3D file format, you get a shield whose faces are visible when seen from the positive side only.

Now, in UV Face Select mode, select a few faces (I selected all of them expect the two marked as I and II), hit the Editing (F9) button, hit the Twoside button, and finally hit the Copy Draw Mode button. This will make the selected faces UV mapping double-sided and tell (later on) the AC3D eporter plugin to consider those faces as double-sided.

[[Image:blender-ac3d-normals_html_m2b0949d2.jpg]]

Now we have a shield which is completely opaque when viewed from both sides except for a little window that is transparent when looking from inside. The file is [[Media:schermo2.blend|schermo2.blend]] .

Exporting this to AC3D format will get the file [[Media:schermo3.ac|schermo3.ac]] .

[[Image:blender-ac3d-normals_html_1b6ede36.jpg]]

[[Image:blender-ac3d-normals_html_5ba51d69.jpg]]

'''Have fun with that :-)'''

[[Category:Modeling]]

Modeling - FAQ

2007-10-16T08:03:06Z

Cespenar: cat

__NOTOC__
__NOEDITSECTION__
'''FlightGear Modelling FAQ''' contains interesting answers to FAQ.
It is work in progress...

Q: Which axis in Blender is pointing north?

A: The X-Axis will point north in FlightGear, after you have placed your model using the UFO. Please note that it can be rotated after hitting TAB.

Q: What is the unit used for models in FlightGear?

A: Models are created in Meters. So one Blender Unit will be displayed as one Meter.

Q: Blender does not export the texture reference to AC3 files! What can i do?

A: Propably you have tried to use material textures. These are not exported to AC3 files. Use UV mapped textures instead and they will appear in FlightGear! (see tutorials)

[[Category:Modeling]]

Modeling resources

2007-10-16T08:02:57Z

Cespenar: cat

This is supposed to eventually become a directory of 4D-modelling related resources (i.e. Tutorials, 3D models, textures, images, sounds etc.) that are freely available on the internet.

Please note that while many webpages offer free downloads and use of files, it may be necessary and is indeed recommended to explicitly ask the individual copyright holders for their permission to include their work within FlightGear. In order to become part of the FlightGear base package, it will be necessary to for the copyrighted work to be licensed under the GPL.

=== Tutorials ===
* http://www.gamasutra.com/features/20060622/ahearn_01.shtml
* first page of [http://www.gamasutra.com/features/20060126/ivanov_01.shtml Practical Texture Atlases]

=== Misc. ===
* http://www.m3corp.com
* http://www.help3d.com
* http://www.mr-cad.com
* http://www.3dmodelsharing.com
* http://www.pitchup.com
* http://www.primeportal.net/the_airstrip.htm (photos of aircraft details)

=== 3 Way Views ===
* http://www.stevelange.net/waco/plans.html
* http://www.fortunecity.com/marina/manatee/272
* http://www.pioneeraeroplanes.com
* http://www.theplanpage.com
* http://www.hotkey.net.au/~ue626/index.htm
* http://www.simviation.com/designresources.htm
* http://www.airwar.ru/indexe.html (en)
* http://www.airwar.ru/index.html (ru)
* http://www.dfrc.nasa.gov/gallery/graphics/index.html

=== Free 3D Models, Textures etc ===
* http://www.3dcafe.com/index.php?option=com_wrapper&Itemid=38
* http://www.amazing3d.com/modfree.html
* http://www.greatbuildings.com/types/models/models.html
* http://www.huntfor.com/3d/links/freemodels.htm
* http://www.3dlinks.com/links.cfm?categoryid=9&subcategoryid=91
* http://www.rocky3d.com/free3d.htm
* http://www.amazing3d.com/free/free.shtml
* http://free-textures.got3d.com/index.html
* http://www.3dtotal.com/home2/links/links.asp?cat=texture
* http://www.3dlinks.com/oldsite/textures_free.cfm
* http://dmoz.org/Computers/Software/Graphics/3D/Models/
* http://madmetzi.smokers-board.de/free3d.htm
* http://www.3dtotal.com/home2/links/links.asp?cat=meshes
* http://objects.povworld.org/links6.html
* http://www.creative-3d.net/free3D.cfm
* http://www.3dlinks.com/oldsite/objects_free.cfm
* http://www.grsites.com/textures

=== Free Aircraft Sounds ===
* http://rareaviation.com/spaiso.html
* http://avanimation.avsupport.com/Sound.htm
* http://www.geocities.com/CapeCanaveral/Lab/4515/other.htm
* http://www.soundrangers.com/
* http://www.audiosparx.com/sa/display/sounds.cfm?start=101&sound_group_iid=34
* http://images.military.com/Resources/ResourceSubmittedFileView?file=multimedia_sounds.htm
* http://www.aviationshoppe.com/Sounds1.html

=== Books ===
* Detail and scale series by Alwyn T. Lloyd and Bery Kinzey
* http://www.jbwholesalers.com.au/detailandscale/detailandscale.htm
* http://www.nchsinc.com/shop/BOOKS.HTM

[[Category:Modeling]]

Modeling - Getting Started

2007-10-16T08:02:32Z

Cespenar: /* Problems and Solutions */

== Important Notice for Volunteers ==

Developing scenery and models for use with scenery is an important and very visible contribution to Flightgear. New users of Flightgear often ask how they can contribute, and this is a good place to start. Try looking at some of the following:

* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to go over paper lists and airport diagrams for countries that don't publish air navigation data free online (i.e. almost everyone but the U.S.) and fill in the blanks in our navaid and airport databases.
* We need people to collect geodata to give us more accurate roads, rivers, etc., especially outside the U.S.
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

It would be helpful if people would model the area they are interested in. Generally contributions are going to be from Flightgear users who find scenery lacking in some area and choose to improve it. You are encouraged to research your own area for airport, navaid and scenery information, to contribute the data or dive right in to airport and scenery design.

== Getting Started ==

To begin, you will need to create models in a 3d modeling appliction. Two popular ones are AC3D and Blender. FlightGear can display models in several formats, any format supported by PLIB is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.

If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.

=== AC3D ===

Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to AC3D (http://www.ac3d.org) itself, or use Blender (http://www.blender.org) and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.

* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]

=== Blender ===
Blender (http://www.blender.org) is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.

* Blender Manual - http://mediawiki.blender.org/index.php/Main_Page

* An excellent forum for discussing Blender issues. - http://blenderartists.org/forum/

=== Placing Objects on Scenery ===

There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]].

The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file.

Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.

=== Finding, Creating, or Using Textures ===

Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this licence. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.

=== Generation of textured light objects in Blender ===

http://members.aon.at/mfranz/flightgear/blender-textured-lights.html

=== Import/Export of AC3D files into/from Blender ===

To work with AC3D files in Blender download the Python scripts for your Blender version:

'''Blender 2.25 to 2.27:'''
Import: http://members.aon.at/mfranz/ac-in_2-25-B.py
Export: http://members.aon.at/mfranz/ac-out_2-25-B.py

'''Blender 2.28 and later (but not 2.28c):'''
Import: http://members.aon.at/mfranz/ac3d_import.py
Export: http://members.aon.at/mfranz/ac3d_export.py

The scripts are to be executed from within the Blender application:

* Start Blender.
* Switch one of the views to "Text Editor" mode (leftmost button).
* Load the script by clicking on the "-" button and selecting "OPEN NEW".
* Execute the script by pressing ALT-P.
* Select the file to import/to export to.

'''Blender 2.32 and later (or cvs versions after 2004/01/15):'''
Import/Export: The scripts are now part of the Blender package You just need to tell Blender where the script directory is (info window) and can then find the importer/exporter in the file menu. No need to load the scripts explicitly. If you can't find the scripts directory after installing Blender, you can also download the scripts here for Blender 2.32: http://members.aon.at/mfranz/scripts.tar.gz)

== Problems and Solutions ==
[[3D Model Rotates Around Nose]]
 
[[Configuring Views in FlightGear]]

[[Category:Modeling]]

Modeling - Getting Started

2007-10-16T08:01:38Z

Cespenar: cat

== Important Notice for Volunteers ==

Developing scenery and models for use with scenery is an important and very visible contribution to Flightgear. New users of Flightgear often ask how they can contribute, and this is a good place to start. Try looking at some of the following:

* We need people to go out and take good pictures of all the buildings at their local airports, build models, and create textures (that could be different people for each task).
* We need people to go over paper lists and airport diagrams for countries that don't publish air navigation data free online (i.e. almost everyone but the U.S.) and fill in the blanks in our navaid and airport databases.
* We need people to collect geodata to give us more accurate roads, rivers, etc., especially outside the U.S.
* We need people to start modelling identifiable human-made landmarks like bridges, stadiums, and major buildings. Around the San Francisco Bay area, bridges are especially important. Once you have identified some buildings or objects you would like to have (Aircraft carriers, fuel bowsers, cars, towers, ...) you will need to check out the tools for creating and placing these objects.

It would be helpful if people would model the area they are interested in. Generally contributions are going to be from Flightgear users who find scenery lacking in some area and choose to improve it. You are encouraged to research your own area for airport, navaid and scenery information, to contribute the data or dive right in to airport and scenery design.

== Getting Started ==

To begin, you will need to create models in a 3d modeling appliction. Two popular ones are AC3D and Blender. FlightGear can display models in several formats, any format supported by PLIB is acceptable. AC3D is the most popular format for including scenery in Flightgear. Most or all of the default scenery bundled with a Flightgear release are in AC3D format.

If you do not have AC3D, Blender offers many import and export tools. See the Blender website for further information.

=== AC3D ===

Flightgear uses the ac3d model format for objects such as buildings. To create a model, you will need one of two modelling packages. Either go directly to AC3D (http://www.ac3d.org) itself, or use Blender (http://www.blender.org) and then convert via a Python script (see below). AC3D seems to be a much easier program to learn, while still being very powerful. The downside is that you have to buy a licence to get more than 14 days use.

* [http://wine.techlab.info/AC3D_Tutorials/ AC3D Modeling Tutorials]

=== Blender ===
Blender (http://www.blender.org) is more difficult to learn to use, since it is not quite as intuitive and is far more powerful. However it is GPL'd, and there are lots of tutorials to help with learning.

* Blender Manual - http://mediawiki.blender.org/index.php/Main_Page

* An excellent forum for discussing Blender issues. - http://blenderartists.org/forum/

=== Placing Objects on Scenery ===

There are several ways of doing this. The most direct way is to simply [[Adding shared models manually|add the required data by hand]].

The easiest way is to use the [[Placing 3D Objects with the UFO|UFO's object placement feature]] (in version 9.10 or higher). When operating the UFO, left-clicking the mouse anywhere on the ground will place an object, and pressing space-up or down will cycle through the models. Coordinates of placed models can then be dumped to the terminal or written to a configuration file.

Another method is to use [[FlightGear Scenery Designer]] ([http://fgsd.sourceforge.net/ Project Site]). After setting the paths to your scenery data, simply load up the area where you want to place the object. Load your .ac format model, and right click on the desired spot to place your model there. Export the modifed scenery to save it, rerun Flightgear and your model should be there.

=== Finding, Creating, or Using Textures ===

Once you have made your model building, you will want to apply some textures to it, so it looks as realistic as possible. This is possibly one of the hardest areas, as a good model with bad textures will still look bad. Since Flightgear and the scenery data are all released under the GPL, any textures that you use must also be able to be released under this licence. This will probably prevent you from just using anything you come across on the net, unless it is already under the GPL. It is quite common for people to state that their pictures or textures are free. Since Flightgear can be sold for profit, and is released on Linux distributions that are sold, check that there are no clauses stating that the item can not be sold or used for commercial use.

=== Generation of textured light objects in Blender ===

http://members.aon.at/mfranz/flightgear/blender-textured-lights.html

=== Import/Export of AC3D files into/from Blender ===

To work with AC3D files in Blender download the Python scripts for your Blender version:

'''Blender 2.25 to 2.27:'''
Import: http://members.aon.at/mfranz/ac-in_2-25-B.py
Export: http://members.aon.at/mfranz/ac-out_2-25-B.py

'''Blender 2.28 and later (but not 2.28c):'''
Import: http://members.aon.at/mfranz/ac3d_import.py
Export: http://members.aon.at/mfranz/ac3d_export.py

The scripts are to be executed from within the Blender application:

* Start Blender.
* Switch one of the views to "Text Editor" mode (leftmost button).
* Load the script by clicking on the "-" button and selecting "OPEN NEW".
* Execute the script by pressing ALT-P.
* Select the file to import/to export to.

'''Blender 2.32 and later (or cvs versions after 2004/01/15):'''
Import/Export: The scripts are now part of the Blender package You just need to tell Blender where the script directory is (info window) and can then find the importer/exporter in the file menu. No need to load the scripts explicitly. If you can't find the scripts directory after installing Blender, you can also download the scripts here for Blender 2.32: http://members.aon.at/mfranz/scripts.tar.gz)

== Problems and Solutions ==
[[ 3D Model Rotates Around Nose ]]
[[Configuring Views in FlightGear]]

[[Category:Modeling]]

Model import and export

2007-10-16T08:01:22Z

Cespenar: cat

== The Problem ==
When you create an aircraft model, generally an object like a wing is composed of other parts. A wing may consist of the wing body, the aileron, the flap and perhaps a wingtip. There may be hardware such as stays, guidelines, actuators, etc. It is desirable to export the entire wing with all its parts intact and _independent_. Some export or import tools may not support independent 'sub-objects' and will merge all the parts of a wing into single object (or 'mesh' as objects consisting of polygons are generally called in the 3d world).

What happens if you export or import using a tool that does not support sub objects? You get a wing with all its parts 'welded' together so they cannot be individually manipulated. This is not a good thing.

== FlightGear Import/Export ==
In FlightGear, a utility called '3dconvert' is bundled with the source (Windows binary available [ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/3dconvert-win32.zip here]), which has the ability to convert a number of 3d file formats. Exporting and importing 3d files for FlightGear can involve using the bundled '3dconvert', although it does not have to, given there are a number of third-party converters and import/export tools for 3d modeling applications.

It depends on a library called PLIB for making conversions between formats. As of this writing, _3dconvert_ can only open or save in formats supported by PLIB with any restrictions PLIB places on them.

This utility is dependent on the PLIB library. If you dig deep enough into PLIB documentation, you may find in a very obscure page

Non-class Functions
http://plib.sourceforge.net/ssg/non_class.html
(subject to change)

containing a table of formats PLIB is capable of opening and saving. Not all features of certain formats are supported in a given version of the library. This chart explains which formats PLIB recognizes and what features it supports. It also can tell you which features some formats lack.

The problem to solve is getting an aircraft model from GMAX's proprietary binary 3d format into a format more in keeping with the FlightGear community. Moreover, it is desirable to store 3d models in a format that has some longevity and is human readable. Those are two good reasons to get your model out from GMAX's trap.

Two major 3d design applications are AC3D and Blender. AC3D is the format FlightGear uses 'natively' for aircraft models. It is good that FlightGear uses a non-binary format for aircraft models. The AC3D model files are in 'ac' format and have an '.ac' file extension. Blender is another popular 3d modeling application, its files are in Blender format and have a '.blend' extension. Blender can import or export a number of 3d formats using Python scripts (don't worry, the scripts are easy to use and bundled with the latest version of Blender).

This tutorial will focus on Blender, because I am currently using it for my modeling.

== Getting Your Model Out of GMAX ==

An intermediate format is needed to get our model from GMAX into Blender, because GMAX cannot export non-binary 3d files. This is our first problem to solve. Fortunately, others have found a workaround for this situation. Data can be extracted from GMAX objects by writing a Maxscript (the native scripting language used in GMAX) program that collects the data and prints it to the conveniently provided "script listener" which listens to the output of scripts and displays it in a text window. The clever person can then copy the data from the window and paste into a text editor, which can then save the data into a file.

(I will not go into using GMAX plugins. These are issued by game companies that partner with GMAX and distributed software you can plug in to GMAX to export to a particular 3d format used by the game. Feel free to search for these and use them if you can find them and get them to work.)

This file can then be fed into another conversion or import tool. Either directly into a 3d modeling application or another conversion tool.

I found only one workable script for GMAX, one that displays object data in Wavefront OBJ format in the listener window. It is called {NAME HERE} and you can possibly get it {HERE} before it disappears. (See below)

Or you can try my own script that displays AC3D data in in the window.

In any case, you must go through the tedious task of copying and pasting the data. The listener window has some limit on the number of characters you can copy to the clipboard, so you will need to carefully break up the copying into several small selections for large objects.

Sorry.

Note: You may encounter a problem where the script reports an error. This is typically caused by a "grouped" object. You need to select any compound grouped objects and "ungroup" them before export.

== Getting Your Objects into Blender ==

Now that you've got your objects into an intermediate format, you need to get them into your 3d modeling application. I will focus on Blender, but it applies to other applications as well.

If you have the latest version of Blender {version} you _should_ have at least one script for importing Wavefront (.obj) format files. The scripts can be found on the File --> Import or File --> Export menus. Any import or export scripts installed should show up on these menus. Naturally, you will want to look on the Import menu. There is another OBJ filter you may encounter. I found this one limited, so skipped it for the one that seemed more full featured. The one you want is called Wavefront (.obj) and is authored by {author}.

The only step left is to import the OBJ files created by your cutting and pasting into Blender.

Each independent object in your GMAX 'scene' should be there in Blender. Try selecting a part, say the aileron. It should be separately manipulable.

== Getting your objects out of Blender ==

Roberto Inzerillo has written a page at http://www.geocities.com/robitabu/blender_ac3d_material_translation/blender.html describing some issues regarding the differences between Blender and ac3d's material formats.

== Getting the Aircraft into FlightGear ==

Suppose your object was an entire aircraft (you have a strong constitution, doing all that copying and pasting, I disassembled by aircraft into parts, exported them and reassembled them to avoid too much copying at once) or you have created one in Blender from your imported parts.

To use the aircraft in FlightGear, you export in AC format. This is available on the File --> Export menu in Blender. Look for the one called AC.

== Exporting in AC from GMAX ==

This discusses a little script I wrote to export objects from GMAX into AC3D format.

[[ gMax2AC ]]

== Additional Issues ==

Suppose the scripts to import additional 3d file formats did not exist in Blender. It only natively recognizes three formats (at time of writing), VRML 1.0, DXF, Videoscape and STL. Most are not widely in use today for 3d modeling (in my experience). DXF is a widely used standard format for CAD, but it lacks sub-object support. As far as I know, you cannot use DXF as an intermediate format and have your parts survive unmerged. (According to PLIB chart).

Here are some failed attempts:

GMAX->AC3D->VRML 1.0
using _threedeconvert_ merges objects.

Of course, if you have the Blender AC3D importer, this is unnecessary and not an issue.

GMAX-OBJ->VRML 2.0

Here I used a third-party file converter. Unfortunately, it only outputs VRML 2.0 and vanilla Blender only imports VRML1.0, which meant this is not a good path.

It just makes clear that you must be careful about which conversion tool or import/export tool you use, be sure it supports sub-objects.

What happens if objects are merged? Have fun picking all the parts of of a complex landing gear out of a single merged object!

== Why Export from GMAX? ==

Several reasons:

* GMAX is a "dead end", an application developed as a "crippled" version of a high end 3d design suite, deployed for game modding. This year (2005) all support by its make has been dropped. GMAX will only be distributed and supported within individual game environments, if at all.

* GMAX 3d files are in a proprietary binary format, which means humans cannot read them, it makes it difficult to translate to other formats because the format is only known to the developer. This reduces the "longevity" and ability to share your files.

Both of these issues add up to a situation that can leave your files "orphaned." I put hundreds of hours into my models and do not want them trapped on a "sinking ship" platform that I cannot get them out again to work on.

The official gmax website now points to the parent company AutoDesk, which apparently has discontinued or dropped support for the application.

If you go to the Discreet website (the company that released and managed GMAX)

http://www.discreet.com/products/gmax/

it takes you to

http://usa.autodesk.com/adsk/servlet/index?id=5562445&siteID=123112

which states

"As of October 6, 2005, Autodesk will no longer offer Gmax® software as a stand-alone product. If you are interested in other 3D animation, modeling, and rendering applications from Autodesk please check out Autodesk® 3ds Max® software. You can download a free 30-day trial, view product demonstrations, read customer success stories, and get more information about this powerful, versatile product."

== Maxscript Resources ==

There appears very little Maxscript material online. No tutorials, instructions, specifications, other than the official 3ds Maxscript help file I got somewhere. Many of the Maxscript sites are down, gone, password protected or otherwise unavailable. There were several versions of GMAX released, I find that many plugins and scripts are incompatible. I just don't have the time or interest for such a scattered set of resources and community, when there exist strong communities around open source applications such as Blender.

I will not be responsible for the chaotic state of these resources or their applicability or availability, but here are some helpful ones if they still exist by the time you go to them.

Chris Cookson was the author of several important Maxscript import/export scripts, which are no longer easily available.

See this thread

http://www.turbosquid.com/Forum/Index.cfm/stgAct/PostList/intThreadID/16045

for current 2005 status.

The OBJ importers are

v1.1
http://www.turbosquid.com/Forum/Index.cfm/stgAct/PostList/intThreadID/16045

v1.1a
http://pages.videotron.com/browser/Downloads/GMAX/scripts/importobj.ms

http://tutorials.city-of-doors.com/gmax.html

Mentions the 10kb limit on cut and paste from script listener.

The script mentioned here for working around this for at least one file format is here

http://nwvault.ign.com/View.php?view=Other.Detail&id=148

and still available at the time of writing. It was last updated in 2003. Perhaps you can adapt it. Good luck.

* http://nwvault.ign.com/View.php?view=other.Detail&id=149

This is a GMax-compatible Maxscript which will import and export (via the listener) ASCII mdl files...

* http://nwvault.ign.com/View.php?view=other.Detail&id=290

This Maxscript © utility will import/export Bioware's © mdl model files for Neverwinter Nights ©.

* http://nwvault.ign.com/View.php?view=other.Detail&id=604
DLA presents 'Aurora Importer' by Joco. This maxscript utility serves one function: it imports an as...

[[Category:Modeling]]

Howto:Creating 3D instruments

2007-10-16T08:00:35Z

Cespenar: cat

'''Introduction:'''
This tutorial describes the basic process of creating a 3d instrument for use in FlightGear. For now, we're assuming that you have created the actual 3d model to use and wish to include it in a cockpit and animate it. As an example, we will be animating the ITT gauge for the Fokker 50.

'''What you need:'''
You will need; a text editor (even notepad will do, but one that does syntax highlighting might help you spot typos more easily; if you're on Windows, [http://notepad-plus.sourceforge.net/uk/site.htm Notepad++] looks suitable.)

You will also need your 3d modelling package, and of course a copy of FlightGear.

'''Creating the XML file:'''
The first step is to create an XML file which will load the 3d model and animate it. There are no hard and fast rules about where these files should live or what they must be called, but we'll follow the fairly standard procedure of calling it itt.xml and placing it in the Models directory.

So, using your favourite text editor, create a file called itt.xml in the Aircraft/fokker50/Models directory (folder).

It should start like this (and please remember that case is ALWAYS important);

<?xml version="1.0"?>
<PropertyList>
</PropertyList>

Everything you will add to this file '''must''' go between the <PropertyList> tags.

Now, our file does nothing useful at this point. First of all, we want to tell FG to load the 3d model of our instrument. Add a section under <PropertyList> like this;

<path>itt.ac</path>

This is obviously the name of the 3d model file we wish to load. The model in question looks like this:

[[Image:Fokker51_ITT_screenshot1.jpg]]

'''Adding an animation:'''

As you can see, the main item to animate is the temperature needle, and its name is "needle" (you can animate either ac3d "objects" or complete "groups"). We will want to use a "rotate" animation (for more details on available animation types, see "model-howto.html" which is provided with FG in the Docs directory.)

So, we add an <animation> section to our XML file.

<pre>
<animation>
<type>rotate</type>
<object-name>needle</object-name>
</pre>

Now, we need to specify a property which will determine the amount of rotation required; in other words, the property that provides the ITT value at any one time. To find the name of this property, we need to start FlightGear in the usual manner with the correct aircraft (fokker50 in this case). Once FG has started, open the property browser (file/browse internal properties). You will see the top level of the property tree. Click on "engines" and you will see a list of engines; click on the first one (engine) and you will see a long list of properties and their current values.

[[Image:Fokker50_prop_browser_screenshot1.jpg]]

Now, we have a slight problem at this stage; the fokker50 was created before JSBSim could model turboprops, and so the ITT property is not available right now. For the purposes of this tutorial though, we'll just use the exhaust temperature instead; the process is what's important.

So, the next line in our XML file will specify the property to use;

<property>engines/engine/egt_degf</property>

Next we need to specify exactly how much that property moves the needle. There are several ways to do this, but we'll use a simple interpolation table since these are especially useful in more complicated situations. The ITT gauge is marked from 0 degC to 1200 degC; since we're having to use a value that's reported in degF for now, we'll just convert those two values. 0 degC is about 32 degF and 1200 degC is about 2192 degF. Two handy tips here; for Linux/unix users, the "units" program is truly invaluable; for everyone, google has a useful units converter; for example search for "
1200 degrees celsius in fahrenheit"

On to our table then.

<pre>
<interpolation>
<entry><ind>32</ind><dep>0</dep></entry>
<entry><ind>2192</ind><dep>230</dep></entry>
</interpolation>
</pre>

The <ind> entries are what's indicated on the gauge; the <dep> entries determine how many degrees the object will be rotated by. In this case I found that number by rotating the needle in AC3D from one end of the scale to the other and reading off the rotation value reported (see screenshot)

[[Image:Fokker50_rotation_value.jpg]]

Having configured the type of animation, the controlling property, and specified the effect of that property, we need to describe an axis and centre for the animation.

In this case, the centre is easy, because the needle centre is at the origin of the 3d model. If you wanted the rotation centre to be somewhere else, you could use your modelling app to obtain these values.

<pre>
<center>
<x-m>0</x-m>
<y-m>0</y-m>
<z-m>0</z-m>
</center>
</pre>

The axis is also very simple in this case;

<pre>
<axis>
<x>-1</x>
<y>0</y>
<z>0</z>
</axis>
</pre>

The negative sign on the x axis means that the rotation will be clockwise when viewed from the -x direction (i.e. looking "forwards")

That concludes the rotation animation and so (as always) we need to add a suitable closing tag;

<pre>
</animation>
</pre>

'''Digital display:'''
Our itt.xml file, as it stands, should now "work" in flightgear; that is, it will animate the needle object to display exhaust temperature on the first engine, in degC (despite the input property being in degF!)

However, the bottom half of the gauge contains a digital readout of the same information, and we haven't mentioned that yet. In order to only introduce one new aspect at a time, for the moment I am going to ignore the fact that our input property is in degF and simply display it using the digits; there are several ways we could display degC (or indeed any kind of value) instead, but those are probably best left to another tutorial.

Now, in order to give the illusion of a digital display, we are going to use a slightly less obvious technique than the simple rotation used for the needle. Our digits are going to come from this texture, freshly borrowed from another model in FlightGear (remember, this is open source software - don't reinvent the wheel unless it's absolutely necessary!).

[[Image:digits.jpg]]

Now, each "digit" in the 3d model is a separate rectangle, and each is mapped to the number zero on that texture. What we are going to do is use a "textranslate" animation to slide the texture along to the relevant number in each case. Here's the code for the first digit;

<pre>

<animation>
<type>textranslate</type>
<object-name>digit1</object-name>
<property>engines/engine/egt_degf</property>
<factor>0.0001</factor>
<step>1000</step>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
</pre>

As always, if you need more detailed explanations of any of these animations, remember to RTFM which in this case is the model-howto.html referred to previously.

Each subsequent digit is handled in the same way, though with the object-name, factor and step values modified accordingly.

For example, the next digit along, the "hundreds" digit;

<pre>
<animation>
<type>textranslate</type>
<object-name>digit2</object-name>
<property>engines/engine/egt_degf</property>
<factor>0.001</factor>
<step>100</step>
<axis>
<x>1</x>
<y>0</y>
<z>0</z>
</axis>
</animation>
</pre>

And so on, for the remaining two. Now, your itt instrument should display the EGT in degC using the needle, and give a "digital" readout of the same in degF.

'''Level Of Detail:'''
To prevent objects like this instrument being drawn when the aircraft is actually too far away for them to be seen anyway we use a Level Of Detail section (a "range" "animation".) Notice the <pre></pre> section; this is a comment, feel free to add them where you need a reminder of what's going on.

<pre>

<animation>
<type>range</type>
<min-m>0</min-m>
<max-m>30</max-m>
</animation>
</pre>

Now, if you've managed to stay with us the whole way through, the file should look something like this one, which you can download and compare with. [[Media:itt.xml]] Notice that under each new opening xml tag (such as <animation>) the text is indented one more level. Sensible people(!) use one tab to indent each level, others try to use various numbers of spaces to indent; whatever you use, the single most important thing is to be consistent. Consistent indentation makes the file much easier to read.

'''Including the instrument in an aircraft:'''

Now to the exciting bit, actually seeing the fruits of our labour in FlightGear!
Including our itt.xml file in the fokker50 is actually an easy step. The "model" XML file controls the 3d model; this is often called aircraftname-model.xml and nearly always lives in the aircraftname/Models directory. However, FG is very flexible and in this case, the model XML file is fokker50/Models/fokker50.xml . To avoid confusion, it would be preferable for this to be called fokker50-model.xml, and if you're creating one from scratch, please use that convention.

If we open that file in a text editor, it should look quite familiar; you will recognise the way it specifies an ac3d file, and animates the various parts of it. However, we wish to include an instrument, and that is done very simply. Below the <offsets> section, add a section like this;

<pre>

<model>
<path>Aircraft/fokker50/Models/itt.xml</path>
<offsets>
<x-m>-8.9088</x-m>
<y-m>-0.0811</y-m>
<z-m>-1.0722</z-m>
<pitch-deg>-10</pitch-deg>
</offsets>
</model>
</pre>

Those numbers can be easily obtained from your 3d modelling app; just open the aircraft model and place an object in the correct position, then use the distances here. The usual FG model coordinate system is used; x=back, y=right, z=up, from the pilot's perspective; the origin is the one in the 3d model (.ac file). The "pitch" entry is fairly obvious; pitch of zero is a completely vertical instrument, pitch of -90 is one tilted "top edge forwards" to lie flat.

Now, when you start flightgear, you should see your fully-working instrument in all its glory, situated where it ought to be! If you need to move it later, it's trivial to tweak the numbers above to suit.

[[Category:Modeling]]

3D Model rotates around the nose

2007-10-16T07:59:44Z

Cespenar: cat

A sort of "optical illusion" occurs when the 3D model origin is positioned at the nose. Often the FDM models are configured so that 0,0,0 is located at the "nose". In order to have the 3D model positioned correctly in the 3D world, it should have an origin at the "nose" as well.

The problem is this doesn't "look" right. The cause of this problem is similar to the experience of looking out the window of a stopped train and thinking you are moving when it is actually the train next to you going the other way. 3D Rendering does the same sort of thing. Since you are looking through a "2D window" on your screen you tend to lose the "fixed references" that in the real world help you see how something is really moving. In the case of the external "views" (anything not in the cockpit) of FlightGear you have to remember that the camera (and therefore your eye) is tied to the motion of the aircraft and is always focused on the point that the FDM outputs. You can move that 3D model anywhere you want and it will always appear to move around whereever you have the 3D model's origin set, regardless of where the real movement occurs.

To counteract the effect you need to tell the viewer's camera to look elsewhere. So pick a spot where you think the aircraft should look like it is rotating and then provide view "target" offsets to that location. In most cases this just means moving the target location back toward the wings of the aircraft. Keep in mind that you are merely controlling the way FlightGear renders the image. You are not moving the aircraft's location, or changing the data that drives the instruments, or affecting the way it flies. The following entries in the p51d-set.xml file add this "offset" to the various external views of the P51-D. These entries cause the external view camera to point at a location that is 3.949 meters behind the nose of the aircraft in four different views:

<view n="1">
<config>
<target-z-offset-m archive="y" type="double">3.949
</config>
</view>

<view n="2">
<config>
<target-z-offset-m archive="y" type="double">3.949
</config>
</view>

<view n="3">
<config>
<target-z-offset-m archive="y" type="double">3.949
</config>
</view>

<view n="4">
<config>
<target-z-offset-m archive="y" type="double">3.949
</config>
</view>

[[Category:Modeling]]

Category:Modeling

2007-10-16T07:57:28Z

Cespenar: created cat

Category for everything related to creating 3D-Models for FlightGear.

[[Category:Development]]

Category:Development

2007-10-16T07:56:16Z

Cespenar: created cat

Category for everything related to development of FlightGear code, modeling aircrafts, creating scenery, ...

Frequently asked questions

2007-10-15T13:57:00Z

Cespenar:

''' Feel free to make additions, changes, or corrections.'''

{| width="80%"
|__TOC__
|}

== The FAQ ==
=== Where can I get the latest version of this FAQ? ===

http://www.flightgear.org/Docs/FlightGear-FAQ.html

=== Who do I contact if I have comments about this FAQ? ===

Add your comment to this FAQ's discussion page [[Talk:FAQ]]

=== How old is this document? ===

Click the History button in the menu on the left.

=== What other important documentation should I read? ===

* [http://flightgear.org/Docs/getstart/getstart.html Getting Started Guide]
* [[New to FlightGear]]
* Also see the FlightGear/docs-mini/ directory in the source distribution for various other helpful documents.

== Distribution ==

=== Where can I get FlightGear? ===

The official download page is http://www.flightgear.org/Downloads/. Source code is our primary form of distribution, but precompiled binaries are available for Windows and SGI IRIX.

Alternatively, FlightGear is packaged for Linux by SuSE, Debian (sid), and Mandrake (Cooker) and can be directly installed through those distributions.

=== What is the password for the FTP server? ===

The FTP server uses standard anonymous login procedures. Login with the username "anonymous" and use your email address as the password. Most FTP clients and web browsers will do this automatically for you.

=== Why won't the FTP server let me in with the right login info? ===

This generally means that the server is at it's capacity. You should receive a message saying such, but your FTP client may be hiding it from you. Your options are to keep trying until a slot opens up or try connecting to one of our FTP mirrors listed at http://flightgear.org/mirrors.html.

=== Where can I find the latest development source code? ===

The latest development code is available for everyone through our CVS repository. See http://www.flightgear.org/cvsResources/ for details.

Otherwise, you can get relatively up-to-date snapshots of the development tree at ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.

=== What is SimGear, and why do I need it? ===

SimGear is a library of supporting code. SimGear is only needed if you plan on compiling FlightGear -- it is not needed to run precompiled binaries. For more information see http://www.simgear.org/.

=== Where can I fly and where do I get the scenery? ===

While the base package only comes with scenery for the San Francisco Bay area, you can currently fly just about anywhere in the world. See the "Additional Scenery" section of http://www.flightgear.org/Downloads/ for more information or go directly to our graphical downloader at http://www.flightgear.org/Downloads/world-scenery.html.

Also visit our "Places to Fly" section of the website (http://www.flightgear.org/Places/) for some help navigating to some awesome locations.

=== Where can I get different 3D models for my plane? ===

While we are working toward building our own 3D models, we have been given permission by several people to convert their models (which where originally intended for use with Microsoft Flight Simulator) to use with FlightGear.

=== How current is the data in FlightGear compared to the real world? ===

We use the same navaid and airport dataset that X-Plane uses. The current dataset can be found in the $FGROOT/Navaids/ and $FGROOT/Airports/ directories. If you have updates or corrections to the dataset, see http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html for instructions on contacting the database maintainer.

=== Where is the moving map? ===

A popular moving map display is avaliable under a separate project called Atlas. See http://atlas.sf.net/.

=== Why don't you charge money for this? ===

We could do that, since the initial download is about 132 megabytes. Especially for people who have to pay per-minute charges for internet access, buying a CD is a convenient and possibly cheaper option. Although we offer that service (see the website), we encourage other groups to redistribute it for their users, especially within an operating system distribution which makes installation even faster and easier for new users.

== Compiling ==

=== Why won't FlightGear compile? ===

Well, that depends. First make sure you are using the appropriate versions of FlightGear, SimGear, plib, zlib. If any of the packages are out of sync with the others, compilation may fail.

The FlightGear Downloads page (http://www.flightgear.org/Downloads/) should tell you what versions you need if you are trying to compile the latest stable release. If you are using a development snapshot, make sure all three packages are up-to-date.

Also ensure that you have some implementation of OpenGL with glut support with the appropriate header files. Linux users with nVidia cards should make sure you have the latest drivers from nVidia. Other Linux users make sure you have Mesa3D (http://mesa3d.org/) and your X server installed correctly.

If your problems persist, subscribe to our FlightGear-Users mailing list and let us know what problem you're having. See http://www.flightgear.org/mail.html for help with this.

=== I'm using RedHat 7, and ...? ===

Update your gcc packages. See http://redhat.com/errata/ to fix it and http://www.gnu.org/software/gcc/gcc-2.96.html for an explanation why.

== Configuring ==

=== How do I install new scenery? ===

The scenery archive files (ie. w100n30.tar.gz) should be untarred into the Scenery/Terrain directory in your $FG_ROOT.

=== How do I setup my joystick(s)? ===

FlightGear should come with a helpful program called `fgjs` that can help configure your joystick. Run `fgjs` and then copy the dot file it created into your home directory or add its contents to your existing rc file.

Also, see the README.Joystick file located in the FlightGear/docs-mini/ directory of the source distribution.

=== What format should my personal .fgfsrc file be in? ===

Your .fgfsrc file should simply be a list of command-line options with one option per line. The file is not an XML file.

If you would rather use an XML configuration file, you can add something like the following in your .fgfsrc

<code> --config=/path/to/my/config.xml</code>

Almost every option corresponds to a property, so you can choose to use whichever method best suits your needs.

== Running ==

=== Why do I get an error loading libopenal.so.0? ===

With the default installation, libopenal.so.0 is installed into /usr/local/lib. You need to ensure that that path is listed in /etc/ld.so.conf, then run `ldconfig`as root.

=== Why do I get "ssgInit called without a valid OpenGL context"? ===

In short, your GL libraries are broken. So far only Red Hat 7.x users have experienced this (see http://www.redhat.com/bugzilla/show_bug.cgi?id=18867). The only solutions are possibly complicated ones: you can either change distributions (most of us prefer Debian) or upgrade/downgrade your Mesa libs.

Why do some other GL applications work though? Well, Steve Baker (Mr. PLIB) has explained this on the plib-users list (http://www.geocrawler.com/lists/3/SourceForge/1867/0/6470648/).

=== What happened to the panel, keyboard, etc? ===

The problem is almost certainly that your base package is out of sync with FlightGear. Many configurable parts of FlightGear are defined in XML files contained in the base package.

=== Why doesn't audio work properly under Irix? ===

FlightGear (as of June 2001) uses the Portable Libraries (PLIB) for playing audio. The audio queue implementation of PLIB is far from optimal (in fact it's just wrong). This seems to work on other platforms quite well, but Irix expects things to be programmed properly.

There has been discussion about using OpenAL (http://www.openal.org/) for the next release of both PLIB and FlightGear. Tests show that the OpenAL audio implementation does the job right, meaning that these audio problems should be gone by then. In the mean time it is best to disable audio on Irix completely (by adding --disable-sound either on the command line or to your $HOME/.fgfsrc file).

=== Why is FlightGear so slow? ===

FlightGear supports hardware acceleration, but it seems not to be activated. Make sure you have OpenGL libraries installed and configured properly and make sure you have the latest drivers for your video card.

Linux users: If you are an nVidia user, follow their directions on getting your card working. For most other users, make sure Mesa is installed property and ensure that you have the appropriate kernel device drivers for your card. Most people (and distributions) use modules for their video card device drivers; run `lsmod` as root to see what modules are loaded. You should also make sure that you are loading the appropriate modules in your XF86Config and that your video device section is correct. Now try running an OpenGL application (other than FlightGear) to see how it performs. You can try the gears demo from Mesa or something like Quake3.

=== Why is my SGI machine so slow? ===

First of all, one of the most common mistakes on SGI hardware is to forget to specify --fog-fastest. On most SGI machines the EXP2 shading model isn't hardware supported resulting in frame rates below 1 frame per second (fps).

FlightGear makes extensive use of the OpenGL z-buffer feature,which on most older SGI hardware is only supported in software. This means that the CPU has to do all the z-buffer calculations in addition to the other tasks FlightGear involves (flight dynamics, scenery tracking, pushing commands into the graphics queue, etc). The following features are software rendered on low-end SGI machines (like Indy and Indigo):

* stencil and accumulation buffer
* depth queuing and depth buffering
* fogging, lighting, clipping and transforms
* texturing

This means that running FlightGear with the following options may not even get the desired result:

<code> ./runfgfs --fog-disable --shading-flat --disable-skyblend --disable-textures --disable-clouds --disable-sound --disable-panel --enable-hud --disable-anti-alias-hud </code>

I could even imagine that adding --enable-wireframe doesn't work on these machines (I would be happy to be proven wrong though).

On a machine like O2 the following options give an acceptable result:
<code>./runfgfs --fog-fastest --disable-sound</code>

Since I don't have access to other SGI hardware I can't tell which options would be appropriate for your situation.

=== How do I see the frame rate? ===

There are two ways. One way is to hide the panel without the HUD showing. To hide the panel, use Shift+P; To make the HUD disappear, use H. The second way is to use the alternative HUD by Shift+I (Use I to switch back).
=== Stuck upside down after "crash"? ===

In his infinite wisdom the FlightGear Grand Master decided that planes were to valuable to allow them to be destroyed by novice pilots who seemed to crash a lot. The fact that nobody has bothered to model crashes may have something to do with it too. :-)

The result of this as you have noticed is that with a little practice an ingenuity you can trim the ship to fly inverted along the ground.

The quick answer is to hit Ctrl+U (with the default key bindings) to warp the plane up 1000ft.

For the stubborn people out there: The trick to learn is to roll back to normal (non inverted) do this by nursing the elevator to get to about 500 feet or so and use the ailerons to snap roll 180*. This is all good avionics except for the plane not destroying itself. Remember the controls work in reverse when you are inverted and keep that airspeed up!!!

=== Why does FlightGear die on startup saying "time zone reading failed"? ===

This is probably caused by a line-ending problem in the timezone files. Win32 users can resolve the problem by downloading a DOS to UNIX conversion utility available at http://www.nottingham.ac.uk/~eazdluf/d2u.zip. Run as `d2u *.tab` from within the timezone directory to fix your timezone files.

== Hacking ==

=== What language is FlightGear written in? ===

Mostly C++ with some supporting C code that's primarily contained within SimGear.

=== How do I design a flight dynamics model for a new aircraft? ===

To define an aircraft for FlightGear's primary FDM (JSBSIM), see http://jsbsim.sf.net/.

If you want a simpler FDM to work with, try your hand at YASim, an alternative FDM. For an guide on creating a YASim aircraft, look in the FlightGear base package for Aircraft-yasim/README.yasim.

=== How do I import planes from Microsoft Flight Simulator? ===

You can import the 3D model and textures, but the flight dynamics (the .AIR file) must be completely redone for FlightGear.

If you wish to import a model made with gmax, you will need to convert it to .MDL format using Microsoft's MakeMDL SDK which is available at http://zone.msn.com/flightsim/FS02DevDeskSDK08.asp.

=== How do I import BGL scenery from Microsoft Flight Simulator? ===

See http://chiangt.virtualave.net/BGL/bgl_index.html.

=== How do I design or modify a panel? ===

See the README.xmlpanel file located in the FlightGear/docs-mini/ directory of the source distribution.
----

=== How do I place objects, like buildings, into FlightGear? ===

First, ensure that you have v0.7.7 or later, the scenery files where you plan to place the object, the actual model, and the longitude and latitude where you plan to place the object.

Now get the altitude for your point. If you don't want to calculate this yourself, start FlightGear at your location and take note of the altitude. Here's an example command:

fgfs --lat=45.50 --lon=-75.73 2>&1 | tee fgfs.log

The altitude is probably in feet, so divide the starting altitude by 3.28.

Search the output log file for the first occurrence of the string "Loading tile" and take note of the filename. In the above example, the output line looks like:

Loading tile /usr/local/Scenery/w080n40/w076n45/1712601

Copy a 3D model in a format that Plib understands to the same directory as the tile file. Edit the text file in that directory consisting of the tile name with the extension ".stg". The file will already exist if there is an airport on the tile; otherwise, you can create it from scratch. In our example, the filename is:

<code>/usr/local/Scenery/w080n40/w076n45/1712601.stg</code>

At the end of the file, add a new entry for your object, consisting of the word "OBJECT_STATIC" followed by the model name, the longitude in degrees, the latitude in degrees, the altitude in meters, and the heading in degrees. In our example the line looks like:

OBJECT_STATIC Towerax.ac -75.73 45.40 60 0

Save the changes to the .stg file, restart FlightGear, and enjoy.

NOTE: The above information was taken from the following mailing list post: http://www.geocrawler.com/archives/3/11854/2001/6/0/5991409/. See that page if this one doesn't make sense.

An alternative approach using PPE is described at http://mail.flightgear.org/pipermail/flightgear-devel/2001-December/002239.html by Norman Vine.

With Flightgear 0.9.10 there is an easy way for [[ Placing 3D Objects with the UFO ]]

See also [[ FlightGear Scenery Designer ]].

=== Where can I learn 3D programming and how do I get involved? ===

Contributing to the 2D panel doesn't require any coding at all, just a minimal knowledge of XML syntax (i.e. five minutes' worth) and good skills with drawing and/or paint programs. Every instrument on the current panel, with the partial exception of the magnetic compass, is defined entirely in XML with no custom C++ code. If you want to get started, take a look at John Check's excellent intro (http://rockfish.net/fg/README.xmlpanel).

Likewise, if you want to create a 3D cockpit for FlightGear, or to create buildings, external aircraft models, etc., your help is *desperately* needed. The only rule is to go easy on the triangles -- a model with 50,000 triangles probably won't be usable in FlightGear, and one with 5,000 triangles, only marginally. If you can design a nice 3D cockpit interior for a Cessna 172 (for example) in a 3D design program such as ac3D or ppe, we have coders who will be happy to add the support code in the C++.

If, on the other hand, you really want to get your hands dirty with C++ coding, you'll have to buy a good OpenGL book eventually. However, FlightGear uses a high-level library, plib, that hides most of the details of OpenGL. To get started with 3D C++ coding, you can take a look at the plib documentation and learn only as much OpenGL as you need, when you need it.

=== How do I add an airport? ===

You can add your airport to the $FGROOT/Airports/default.apt.gz file, but to get the airport to show up visually, you will have to rebuild the scenery around the airport. The format of the default.apt file is documented at http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html.

=== How do I generate my own scenery? ===

Yes, though it can be a difficult task. FlightGear's scenery generation is handled by a sister project, TerraGear. For more details, see http://terragear.org/.

== Flying ==

=== Where can I learn about instrument flying and navigation? ===

http://www.navfltsm.addr.com/ is a very good site for learning techniques for navigation.

[http://www.av8n.com/how/ See How It Flies] a very nice book by John S. Denker, freely accessible online

Please see [[Understanding Navigation]]

=== What is the difference between Aileron and Rudder? ===

There is a bit of info on aileron vs. rudder in the very same book...

=== Is there support for multi-player flying? ===

Yes. Both the Windows and *nix versions of FlightGear are capable of multi-player flying on FlightGear servers.

Wiki: [http://wiki.flightgear.org/flightgear_wiki/index.php?title=Multiplayer_Howto Multiplayer_Howto]

A map showing players aircfart online in real time is available:
[http://pigeond.net/flightgear/fg_server_map.html FlightGear Online Server Map]

=== Is there support for any military scenarios like dog fighting or bomb dropping? ===

No, not at this time. Most of our developers are primarily interested and focused on civilian aviation. We aren't explicitly excluding these features -- we just haven't had anyone who seriously wanted to develop these areas.

== FlightGear v0.7.6 ==

=== Why do I get an error in viewer.cxx about `exit' being undeclared? ===

This error cropped up after the release of v0.7.6. To fix the problem, add "#include <stdlib.h>" to the top of viewer.cxx.

FlightGear 1.0 hardware recommendations

2007-10-14T17:12:18Z

Cespenar: /* 3D graphic cards that are known to work */

__NOTOC__
== Recommended hardware specs ==

For example
x86 PC:

* 0.8-2 GHZ
* 512-1024 MB RAM
* 3D hardware accelerator, 128-256 MB, OpenGL 1.2 capable (2.0 even better!)
* 100 MB free HD space (1 GB for compilations recommended)
* Soundblaster compatible soundcard (optional?) - preferably with EAX support
* Gameport or USB (HID compatible) joystick/yoke and/or pedals (optional)

== 3D graphic cards that are known to work ==

* NVIDIA GeForce MX420/440 (64Mb), GeForce 4 series, GeForce FX series, GeForce 6 series, GeForce 7600
* ATI Radeon 9000/9200/9250 series, Radeon 9600/9800 series

Basically, you should be fine with any NVIDIA or ATI card that is not older than 12-18 months; however, you need to take into account that some of the newer features in FlightGear may not work as expected or may not even work altogether with older hardware. In general, 3D cards that make use of shared memory should be avoided (PCI express cards that share memory are ok). Also, if you intend to use FlightGear under Linux you may first want to check whether the driver for your card is fully supported under Linux (and your X version) or not.

Currently, you can basically forget about using any Matrox cards as FlightGear is very heavy on textures, but only the high-end matrox cards will have sufficient capabilities to deal with FlightGear's requirements.

TODO: explain PCI vs. AGP (2x,4x,8x) vs. PCI-E

== Input Hardware (Joysticks, Pedals & Yokes) known to work ==
(Please check $FG_ROOT/Input/Joysticks)

* CH PRODUCTS PRO PEDALS (USB/GAMEPORT)
* CH PRODUCTS PRO YOKE (USB/GAMEPORT)
* Logitech Attack 3 joystick (USB)
* Logitech Extreme 3d Pro (USB) (Windows and OS-X)
* Microsoft Sidewinder Precision Pro
* Saitek ST290 Pro joystick (USB)(Linux)
* Saitek X45 and Throttle (USB)(Linux, Windows)
* Rockfire Gameport to USB adaptor with 4-axis gameport joystick

== Hardware Incompatabilities ==

* Cyborg-3d-force-usb from Saitek leads to a crash under Linux

FlightGear 1.0 hardware recommendations

2007-10-14T17:11:40Z

Cespenar: /* 3D graphic cards that are known to work */

__NOTOC__
== Recommended hardware specs ==

For example
x86 PC:

* 0.8-2 GHZ
* 512-1024 MB RAM
* 3D hardware accelerator, 128-256 MB, OpenGL 1.2 capable (2.0 even better!)
* 100 MB free HD space (1 GB for compilations recommended)
* Soundblaster compatible soundcard (optional?) - preferably with EAX support
* Gameport or USB (HID compatible) joystick/yoke and/or pedals (optional)

== 3D graphic cards that are known to work ==

* NVIDIA GeForce MX420/440 (64Mb), GeForce 4 series, GeForce FX series, GeForce 6 series, GeForce 7600
* ATI Radeon 9000/9200/9250 series, Radeon 9600 series, Radeon 9800 series

Basically, you should be fine with any NVIDIA or ATI card that is not older than 12-18 months; however, you need to take into account that some of the newer features in FlightGear may not work as expected or may not even work altogether with older hardware. In general, 3D cards that make use of shared memory should be avoided (PCI express cards that share memory are ok). Also, if you intend to use FlightGear under Linux you may first want to check whether the driver for your card is fully supported under Linux (and your X version) or not.

Currently, you can basically forget about using any Matrox cards as FlightGear is very heavy on textures, but only the high-end matrox cards will have sufficient capabilities to deal with FlightGear's requirements.

TODO: explain PCI vs. AGP (2x,4x,8x) vs. PCI-E

== Input Hardware (Joysticks, Pedals & Yokes) known to work ==
(Please check $FG_ROOT/Input/Joysticks)

* CH PRODUCTS PRO PEDALS (USB/GAMEPORT)
* CH PRODUCTS PRO YOKE (USB/GAMEPORT)
* Logitech Attack 3 joystick (USB)
* Logitech Extreme 3d Pro (USB) (Windows and OS-X)
* Microsoft Sidewinder Precision Pro
* Saitek ST290 Pro joystick (USB)(Linux)
* Saitek X45 and Throttle (USB)(Linux, Windows)
* Rockfire Gameport to USB adaptor with 4-axis gameport joystick

== Hardware Incompatabilities ==

* Cyborg-3d-force-usb from Saitek leads to a crash under Linux

FlightGear 1.0 hardware recommendations

2007-10-14T17:05:32Z

Cespenar: /* Input Hardware (Joysticks, Pedals & Yokes) known to work */

__NOTOC__
== Recommended hardware specs ==

For example
x86 PC:

* 0.8-2 GHZ
* 512-1024 MB RAM
* 3D hardware accelerator, 128-256 MB, OpenGL 1.2 capable (2.0 even better!)
* 100 MB free HD space (1 GB for compilations recommended)
* Soundblaster compatible soundcard (optional?) - preferably with EAX support
* Gameport or USB (HID compatible) joystick/yoke and/or pedals (optional)

== 3D graphic cards that are known to work ==

* NVIDIA GeForce MX420/440 (64Mb), Ti4200, FX5200, 5500, 6200, 6600, 6800, 7600
* ATI RADEON 9000,9200,9250,9600,9800/PRO

Basically, you should be fine with any NVIDIA or ATI card that is not older than 12-18 months; however, you need to take into account that some of the newer features in FlightGear may not work as expected or may not even work altogether with older hardware. In general, 3D cards that make use of shared memory should be avoided (PCI express cards that share memory are ok). Also, if you intend to use FlightGear under Linux you may first want to check whether the driver for your card is fully supported under Linux (and your X version) or not.

Currently, you can basically forget about using any Matrox cards as FlightGear is very heavy on textures, but only the high-end matrox cards will have sufficient capabilities to deal with FlightGear's requirements.

TODO: explain PCI vs. AGP (2x,4x,8x) vs. PCI-E

== Input Hardware (Joysticks, Pedals & Yokes) known to work ==
(Please check $FG_ROOT/Input/Joysticks)

* CH PRODUCTS PRO PEDALS (USB/GAMEPORT)
* CH PRODUCTS PRO YOKE (USB/GAMEPORT)
* Logitech Attack 3 joystick (USB)
* Logitech Extreme 3d Pro (USB) (Windows and OS-X)
* Microsoft Sidewinder Precision Pro
* Saitek ST290 Pro joystick (USB)(Linux)
* Saitek X45 and Throttle (USB)(Linux, Windows)
* Rockfire Gameport to USB adaptor with 4-axis gameport joystick

== Hardware Incompatabilities ==

* Cyborg-3d-force-usb from Saitek leads to a crash under Linux

FlightGear 1.0 hardware recommendations

2007-10-14T17:04:42Z

Cespenar: /* 3D graphic cards that are known to work */

__NOTOC__
== Recommended hardware specs ==

For example
x86 PC:

* 0.8-2 GHZ
* 512-1024 MB RAM
* 3D hardware accelerator, 128-256 MB, OpenGL 1.2 capable (2.0 even better!)
* 100 MB free HD space (1 GB for compilations recommended)
* Soundblaster compatible soundcard (optional?) - preferably with EAX support
* Gameport or USB (HID compatible) joystick/yoke and/or pedals (optional)

== 3D graphic cards that are known to work ==

* NVIDIA GeForce MX420/440 (64Mb), Ti4200, FX5200, 5500, 6200, 6600, 6800, 7600
* ATI RADEON 9000,9200,9250,9600,9800/PRO

Basically, you should be fine with any NVIDIA or ATI card that is not older than 12-18 months; however, you need to take into account that some of the newer features in FlightGear may not work as expected or may not even work altogether with older hardware. In general, 3D cards that make use of shared memory should be avoided (PCI express cards that share memory are ok). Also, if you intend to use FlightGear under Linux you may first want to check whether the driver for your card is fully supported under Linux (and your X version) or not.

Currently, you can basically forget about using any Matrox cards as FlightGear is very heavy on textures, but only the high-end matrox cards will have sufficient capabilities to deal with FlightGear's requirements.

TODO: explain PCI vs. AGP (2x,4x,8x) vs. PCI-E

== Input Hardware (Joysticks, Pedals & Yokes) known to work ==
(Please check $FG_ROOT/Input/Joysticks)

* CH PRODUCTS PRO PEDALS (USB/GAMEPORT)
* CH PRODUCTS PRO YOKE (USB/GAMEPORT)
* Logitech Attack 3 joystick (USB)
* Logitech Extreme 3d Pro (USB) (Windows and OS-X)
* Saitek ST290 Pro joystick (USB)(Linux)
* Saitek X45 and Throttle (USB)(Linux, Windows)
* Rockfire Gameport to USB adaptor with 4-axis gameport joystick

== Hardware Incompatabilities ==

* Cyborg-3d-force-usb from Saitek leads to a crash under Linux

Autopilot tunning ressources

2007-10-14T16:55:16Z

Cespenar: REDIRECT Autopilot_Tuning_Resources

#REDIRECT [[Autopilot_Tuning_Resources]]

Martin Marietta X-24

2007-10-14T13:01:55Z

Cespenar:

Alias for x24b. x24b Alias for x24b-jsbsim. x24b-jsbsim USAF/NACA X-24B reentry testbed

{{infobox Aircraft
|image =[[Image:X24.jpg|320px]]
|name =X24
|type =
|fdm =JSBSim
|status =
|authors =Jon S. Berndt
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* aircraft has no 3d model
* 3d Cockpit:
* 3d cockpit is not available General:
* Hud is not available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Space Shuttle (FG Space Program)

2007-10-14T13:00:49Z

Cespenar:

shuttle Alias for shuttle-jsbsim.

{{infobox Aircraft
|image =[[Image:Space Shuttle.jpg|320px]]
|name =Space Shuttle
|type =
|fdm =JSBSim
|status =
|authors =Jon S. Berndt
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* aircraft has no 3d model 3d

Cockpit:

* 3d cockpit is not available

General:

* no hud available
* Because the shuttle is a glider without engines after reentry the initial starting position should be somewhere at an altidude of over 80000 feet

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

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

UFO from the 'White Project' of the UNESCO

2007-10-14T12:57:13Z

Cespenar:

{{infobox Aircraft
|image =[[Image:UFO.jpg|320px]]
|name =UFO from the 'White Project' of the UNESCO
|type =Other
|fdm =
|status =
|authors =
}}

{|
|__TOC__
|}

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

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

Wright Flyer

2007-10-14T12:56:51Z

Cespenar:

{{infobox Aircraft
|image =[[Image:1903_Wright_Flyer.jpg|320px]]
|name =Wright Flyer
|type =Historical aircraft
|fdm =
|status =
|authors =Jim Wilson (3D), Michael Selig, PhD (FDM)
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* aircraft has no shadow

3d Cockpit:

General:

* propeller is not moving/turning when engine is running at low power
* engines can't be turned off

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Historical aircraft]]
[[Category:Aircraft TODO]]s

Tupolev Tu-154 (YASim)

2007-10-14T12:56:43Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Tu154.jpg|320px]]
|name =Tupolev 154
|type =Airliner
|fdm =YASim
|status =
|authors =Ilia Pavlenko, Ilja Moderau, Denis Okan and Mike Savchenko
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* there is a small bug on the right wing when lowering the flaps
* you can see inside the hull from behind when moving the rudder to the left or right
* cockpit and passenger windows are not transparent
* wings, wheels and engines are not textured
* engine turbine does not rotate
* aircraft has no shadow
* no aircraft light available
* aircraft has no wheel well area for the landing gears
* aircraft has no bay doors for the landing gears
* no jet stream visible
* nozzle do not change shape when changing thrust (nor does the real one, so it's not a fault)
* there are no flaps when using reverse thrust

3d Cockpit:

* 3d cockpit is not available

General:

* no hud available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Sopwith Camel

2007-10-14T12:56:12Z

Cespenar:

Alias for sopwithCamel-v1-nl-uiuc sopwithCamel-v1-nl-uiuc

{{infobox Aircraft
|image =[[Image:SopwithCamel.jpg|320px]]
|name =Sopwith Camel
|type =Historical aircraft
|fdm =
|status =production
|authors =A.F.Scrub "Scrubby PC" (3D), Michael Selig (FDM)
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Soko J-22 Orao / IAR-93

2007-10-14T12:56:02Z

Cespenar:

{{infobox Aircraft
|image =[[Image:J22.jpg|320px]]
|name =Soko J-22 Orao / IAR-93
|type =Military Aircraft
|fdm =
|status =
|authors =Matevz Jekovec
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* flaps are animated but flap sound can only be barely heard
* eninge turbine does not rotate or rotation is not visible
* no cockpit light at night visible
* aircraft has no shadow
* no aircraft light available
* no jetstream visible
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust

3d Cockpit:

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* no cockpit instruments available
* cockpit is not textured
* pilot is present but not animated

General:

* engine sound in cockpit does not differ from outside engine sound
* hud can't be turned off
* engines can't be turned off

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Saab J 35Ãƒâ€“ Draken

2007-10-14T12:55:33Z

Cespenar:

<tt>SaabJ35OeDraken</tt>

{{infobox Aircraft
|image =[[Image:Saab_J35.jpg|320px]]
|name =Saab J 35Ö Draken
|type =Military aircraft
|fdm = JSBSim
|status = beta
|authors = Oliver Reischl
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

3d Cockpit:

* 3d cockpit is not available (nor is a 2d one)

General:

== External links ==

[http://en.wikipedia.org/wiki/Saab_35_Draken Wikipedia: Saab 35]

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Piper PA34-200T Seneca II

2007-10-14T12:54:52Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Piper_SenecaII.jpg|320px]]
|name =Piper PA34-200T Seneca II
|type =Civilian aircraft
|fdm =
|status =early-production
|authors =
}}

{|
|__TOC__
|}

== Introduction ==
[[Image:SenecaII_real.jpg|thumb|left|The real Seneca II]]
This is a model of a Piper PA34-200T Seneneca II. The Seneca is made by Piper since the early 1970's and some 4500 were made since then. It has six seats in a pretty large cabin, two turbocharged counterrotating engines producing 200hp up to 12,000 ft. It cruises at 170ktas in 12,000ft at 65% power. Certification for flights into known icing conditions and the nice single engine behaviour made the Seneca a popular multi engine trainer.

The model was built using the Pilots Operating Handbook, a real Seneca (D-GEJL) and some flight performance data derived in real flights.
 ,
== Features ==
=== Full functional 3d cockpit ===
[[Image:SenecaII_cockpit.jpg|thumb|left|The 3d cockpit]]
Allmost all controls, switches, gauges and indicators are implemented and functional in the cockpit. For description of the panel have a look at the [[Seneca II Panel Reference]].
 

=== Structural Icing ===
Since the Seneca provides anti- and deice equipment, I tried to model structural icing into flightgear. A little nasal script does most of the work: First it reads the property nodes under /sim/model/icing where any number of iceable elements configure the ice sensitive elements of the aircraft. Each element have a name, a sensitivity to icing, may have a salvage control and the name of a output property where the collected amount of ice is written to. After the initial configuration, a timed loop is executed every 2 seconds. It
* calculates the spread by OAT and dewpoint
* checks visibility (see remark) to tell if the aircraft is within clouds
* if the spread is below 0.1 degc and visibility is below 1000m, assumes potential icing condition and icing severity is calculated
* update all ice sensitive elements with the current icing conditions

The icing severities are defined as
{|
! severity
! inches
! per NM (still air)
|-
| NONE
| -0.3
| 80
|-
| TRACE
| 0.5
| 80
|-
| LIGHT
| 0.5
| 40
|-
| MODERATE
| 0.5
| 20
|-
| SEVERE
| 0.5
| 10
|}

The rule for calculating the severity is
{|
! OAT_min
! OAT_max
! severity_min
! severity_max
|-
| -99
| -30
| NONE
| TRACE
|-
| -30
| -20
| TRACE
| LIGHT
|-
| -20
| -12
| LIGHT
| SEVERE
|-
| -2
| -0
| NONE
| MODERATE
|-
| 0
| 999
| NONE
| NONE
|}
When oat is above zero degc, Ice melts at a rate of 0.5" per 10NM at 10degc, the warmer the faster.

== Pilot Operating Handbook ==
=== General ===
==== Engines ====
{| width="100%"
| width="50%" | Number of Engines
| width="50%" | 2
|-
|Engine Manufacturer
|Continental
|-
|Engine Model Number
|(L)TSIO-360EB
|-
|Rated Horsepower
|Sea Lever: 200, 12,000ft.: 215
|-
|Rated Speed (rpm)
|2575
|-
|Bore (inches)
|4.438
|-
|Stroke (inches)
|3.875
|-
|Displacement (cubic inches)
|360
|-
|Compression Ratio
|7.5:1
|-
|Engine Type
| Six Cylinder, Direct Drive, Horizontally Opposed, Air Cooled
|}

==== Propellers ====
{| width="100%"
| width="50%" |Number of Propellers
| width="50%" |2
|-
|Propeller Manufacturer
|Hartzell
|-
|Number of Blades
|2
|-
|Propeller Diameter
| Maximum: 76 inches, Minimum: 75 inches
|-
|Propeller Type
|Constant Speed, Hydraulically Actuated, Full Feathering
|}

==== Fuel ====
{| width="100%"
| width="50%" |Fuel Capacity (U.S.gal) (total)
| width="50%" |128
|-
|Usable Fuel (U.S.gal) (total)
|123
|-
|Minumum Grade
|100 Green or 100LL Blue Aviation Grade
|-
|}

==== Oil ====
{| width="100%"
| width="50%" |Oil Capacity (U.S.quarts) (per engine)
| width="50%" |8
|}

==== Maximum Weights ====
{| width="100%"
| width="50%" |Maximum Takeoff Weight (lbs)
| width="50%" |4570
|-
|Maximum Landing Weight (lbs)
|4362
|-
|Maximum Zero Fuel Weight (lbs) - Standard
|4000
|-
|Maximum Weight in Baggage Compartment (lbs)
|Forward: 100, Aft: 100
|}

==== Standard Airplane Weights ====
{| width="100%"
| width="50%" | Standard Empty Weight (lbs): Weight of a standard airplane including unusable fuel, full operating fluids and full oil.
| width="50%" | 2823
|-
| Maximum Useful Load (lbs): The difference between the Maximum Takeoff Weight and the Standard Empty Weight. (All weight in excess off 4000lbs must consist of fuel)
|1747
|}

==== Specific Loadings ====
{| width="100%"
| width="50%" | Wing Loading (lbs per sq ft)
| width="50%" | 22
|-
| Power Loading (lbs per hp)
| Sea Level: 11.4 - 12,000ft: 10.6
|}

=== Limitations ===
==== Airspeed Limitations ====
{| width="100%"
! width="50%" align="left" | Speed
! width="25%" align="left" | KIAS
! width="25%" align="left" | KCAS
|-
| Never Exceed Speed (VNE) - Do not exceed this speed in any operation
| 195
| 195
|-
| Maximum Structural Cruising Speed (VNO) - Do not exceed this speed except in smooth air and then only with caution.
| 163
| 165
|-
| Design Maneuvering Speed (VA) - Do not make full or abrupt control movements above this speed.
|  
|  
|-
| align="center"| At 4570 LBS G.W.
| 136
| 138
|-
| align="center"|At 3068 LBS G.W.
| 121
| 122
|-
| colspan="3" align="center" |
CAUTION

Maneuvering speed decreases at lighter weight as the effects of aerodynamic forces become more pronounced. Linear interpolation may be used for imtermediate gross weights. maneuvering speed should not be exceeded while operating in rough air.
|-
| Maximum Flaps Extended Speed (VFE) - Do not exceed this speed with flaps extended.
| 107
| 109
|-
| Maximum Gear Extended Speed (VLE) - Do not exceed this speed with landing gear extended
| 129
| 130
|-
| Maximum Landing Gear Extending Speed (VLO) - Do not extend landing gear above this speed
| 129
| 130
|-
| Maximum Landing Gear Retracting Speed (VLO) - Do not retract landing gear above this speed
| 107
| 109
|-
| Air Minimum Control Speed (VMC) - Lowes airspeed at which airplane is controllable with one engine operating and no flaps
| 66
| 69
|-
| Best Single Engine Rate of Climb Speed
| 89
| 90
|}

==== Airspeed Indicator Markings ====
{| width="100%"
! width="50%" align="left" | Marking
! width="50%" align="left" | KIAS
|-
|Green Arc (Normal Operating Range)
|63 to 163
|-
|Yellow Arc (Caution Range - Smooth Air)
|163 to 195
|-
|White Arc (Flaps Extended Range)
|61 to 107
|-
|Radial Red Line (Never Exceed - Smooth Air)
|195
|-
|Radial Red Line (Minimum Control Speed - Single Engine)
|66
|-
|Radial Blue Line (Best Rate of Climb Speed - Single Engine)
|89
|}

==== Power Plant Limitations ====
{| width="100%"
| width="50%" | Maximum Rotational Speed
| width="50%" | 2575
|-
| Maximum Manifold Pressure (Inches of Mercury)
| 40
|-
| Maximum Cylinder Head Temperature
| 460 °F
|-
| Maximum Oil Temperature
| 240 °F
|-
| Minimum Oil Pressure (red line)
| 10 PSI
|-
| Maximum Oil Pressure (red line)
| 100 PSI
|-
| colspan="2" align="center" |
NOTES

Avoid continuous operation between 2000 and 2000 RPM above 32 IN. HG. manifold pressure.

Avoid continuous ground operation between 1700 and 2100 RPM in cross and tail winds over 10 knots.
|}

==== Power Plant Instrument Markings ====
{| width="100%"
! width="50%" align="left"| Tachometer
| width="50%" |  
|-
| Green Arc (Normal Operating Range)
| 500 RPM to 2575 RPM
|-
| Red Line (Maximum)
| 2575 RPM
|-
! align="left" | Fuel Flow and Pressure
| 
|-
| Green Arc (Normal Operating Range)
| 3.5 PSI to 20 PSI
|-
| Red Line (Maximum at Sea Level)
| 25 GPH (20PSI)
|-
| Red Line (Minimum)
| 3.5 PSI
|-
! align="left" | Cylinder Head Temperature
|  
|-
| Green Arc (Normal Range)
| either 360 °F to 460 °F
|-
|  
| or 240 °F to 460 °F
|-
| Red Line (Maximum)
| 460 °F
|-
! align="left" | Oil Temperature
|  
|-
| Green Arc (Normal Operating Range)
| either 75 °F to 240 °F
|-
|  
| or 100 °F to 240 °F
|-
| Red Line (Maximum)
| 240 °F
|-
! align="left" | Oil Pressure
|  
|-
| Green Arc (Normal Operating Range)
| either 30 PSI to 80 PSI
|-
|  
| or 30 PSI to 60 PSI
|-
| Yellow Arc (Caution)
| either 80 PSI to 100 PSI
|-
|  
| or 60 PSI to 100 PSI
|-
| Red Line (Minimum)
| 10 PSI
|-
| Red Line (Maximum)
| 100 PSI
|-
! align="left" | Manifold Pressure
|  
|-
| Green Arc (Normal Operating Range)
| 10 IN. to 40 IN. HG.
|-
| Red Line (Maximum)
| 40 IN. HG.
|-
! align="left" | Exhaust Gas Temperature
|  
|-
| Red Line
| 1650 °F
|}

==== Center of Gravity Limits ====
{| width="100%"
! width="33%" align="left" | Weight Ponds
! width="33%" align="left"| Forward Limit Inches Aft of Datum
! width="34%" align="left" | Aft Limit Inches Aft of Datum
|-
|3400
|82.0
|94.6
|-
|4570
|90.6
|94.6
|}
NOTES

Straight line variation between the points given.

Datum is 78.4 inches forward of wing leading edge from the inboard edge of the inboard fuel tank.

==== Maneuver Limits ====
All intentional acrobatic maneuvers (including spins) are prohibited. Avoid abrupt maneuvers.

==== Flight Load Factor Limits ====
{| width="100%"
| width="50%" | Positive Load Factor (Maximum)
| width="50%" | 3.8 G
|-
| Negative Load Factor (Maximum)
| No inverted maneuvers approved
|-
|}

==== Types of Operations ====
The airplane is approved for the following operations when equipped in accordance with FAR 91 or FAR 135
* Day VFR
* Night VFR
* Day IFR
* Night IFR
* Icing conditions when equipped.

==== Fuel Limitations ====
The usable fuel in this aircraft is 61.5 gallons in each wing or a total of 123 gallons.

==== Gyro Pressuer Limits ====
The operating limits for the pressure system are 4.5 to 5.2 inches of mercury for all operations as indicated by the gyro pressure gauge.

==== Flight Into Known Icing Conditions ====
For flight in icing conditions the following equipment must be installed inaccordance with Piper drawings or in an FAA approved manner:
* Pneumatic wing end empennage boots
* Electrothermal propeller boots
* Electric windshield panel
* Heated pitot head
* Wing ice light
* Heated lift detectors
* Propeller spinners must be installed

==== Operating Altitude Limitations ====
Flight above 25,000 feet is not approved. Flight up to and including 25,000 feet is approved if equipped with oxygen in accordance with FAR 23.1441 and avionics in accordance with FAR 91 or FAR 135.

== Development status/Issues/Todo ==
FDM (JSBSim):
* poor single engine performance
* no EGT indication - EGT is to low
* supercharger code not realistic on low rpm
* fuel source not switchable or cuttable

FDM (YASim)
* not converging

Electrical system
* Master switch no electrical function
* Generator L/H and R/H produce the same output when on

Autopilot
* Just interfacing the generic AP, Altimatic IIIC not implemented
* LOC NORM and LOC REV not implemented
* ILS not implemented

Avionics
* GMA340: on some buttons, the first click after program start gets lost
* False frequency indication on some frequencies for nav/comm and dme. As a workaround, put the following to your .fgfsrc
--prop:/instrumentation/comm/frequencies/selected-mhz=126.8501
--prop:/instrumentation/comm/frequencies/standby-mhz=124.2201
--prop:/instrumentation/comm[1]/frequencies/selected-mhz=121.8001
--prop:/instrumentation/comm[1]/frequencies/standby-mhz=132.1201
--prop:/instrumentation/nav/frequencies/selected-mhz=111.5001
--prop:/instrumentation/nav/frequencies/standby-mhz=113.1001
--prop:/instrumentation/nav[1]/frequencies/selected-mhz=113.1001
--prop:/instrumentation/nav[1]/frequencies/standby-mhz=115.1001
--prop:/instrumentation/dme/frequencies/selected-mhz=115.8001

General:
* engine sound in cockpit does not differ from outside engine sound
* animations of structural icing on wings, stabilizer, fin, etc.missing

== External links ==
== Related content ==
* [[Seneca II Checklist]]
* [[Seneca II HOWTO]]
* [[Seneca II Panel Reference]]

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Piper J3 Cub

2007-10-14T12:54:41Z

Cespenar:

{{Mergefrom|Piper J3 Cub Operations Manual}}

{{infobox Aircraft
|image =[[Image:Piper_j3cub.jpg|320px]]
|name =Piper J3 Cub
|type =Civilian aircraft
|fdm =
|status =
|authors =David Megginson (3D, FDM), Jim Wilson (Instruments)
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* no pilot present in cockpit -
* aircraft has no shadow

3d Cockpit:

* no rudder control pedals visible
* no switches and levers available
* no elevator trim control available
* Aaltimeter can't be adjusted with the mouse
* cockpit is not textured
* no pilot present in cockpit

General:

* engine sound in cockpit does not differ from outside engine sound

Non-bugs:
* pilot door is open and partly in the the wing rods. - This is accurate, and how the J3 can be flown
* does this airplane has flaps? - No
* No electrical system, therefore no cockpit, intrument, or aircraft lights
* No HUD.

== External links ==
== Related content ==
[[Piper J3 Cub Operations Manual]]

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Piper Cherokee Warrior II

2007-10-14T12:54:15Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Piper_Cherokee_Warrior_II.png|320px]]
|name =Piper Cherokee Warrior II
|type =Civilian aircraft
|fdm =
|status =
|authors =David Megginson
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:
* propeller is not visible (transparent) when rotating
* when looking through the cockpit windows and on the instrument panel i can see the runway trough the instrument panel
* flaps are moving in steps, they are not fluxional animated
* no cockpit light at night visible
* wings and wheels are not textured
* aircraft has no shadow
* no aircraft light available

3d Cockpit:

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* cockpit instruments are available but missing on the co-pilot side
* Usual Configuration in PA28s is left-side instrumentation only; radios not implemented yet
* cockpit instruments look flat, they don't have a 3d look
* cockpit is not textured
* no pilot or co pilot present
* cockpit window has no windscreen wipers;
** PA28s are not equipped with wipers.

General:

* aircraft is not set on the correct elevation when starting flightsgear, lowest part of the aircraft is approximately 0.40 m above the ground.

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Pilatus PC-7

2007-10-14T12:54:05Z

Cespenar:

was: t6texan2 Alias for t6texan2-jsbsim.
t6texan2-jsbsim T-6A Texan II

{{infobox Aircraft
|image =[[Image:Pilatus_PC-7.jpg|320px]]
|name =Pilatus PC-7
|type =Civilian aircraft
|fdm =
|status =beta
|authors =David Culp, Erik Hofman (based on Capt. Slug 3D model)
}}

{|
|__TOC__
|}

== Development Status/Issues/Todo ==
Outside:

* no pilot in cockpit visible
* aircraft has no shadow
* no aircraft light available
* no pilor or instructor

3d Cockpit:
* no textures used

General:

* engines can't be turned off
* engine sound does not change when accelerating. This is common for turboprop engine though.
* no hud available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Paraglider

2007-10-14T12:52:31Z

Cespenar:

Alias for paraglider-jsbsim. paraglider-jsbsim paraglider

{{infobox Aircraft
|image =[[Image:Paraglider.jpg|320px]]
|name =Paraglider
|type =Glider
|fdm =JSBSim
|status =beta
|authors =David Culp (FDM), Capt. Slug (3D)
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:
* man in the paraglider is not moving his arms when steering the controls, paraglider is also not changing its shape
* man in the paraglider needs some running animation when starting from the ground
* when moving completly to the right, man turns upside down in this position paraglider is unstable

General:

* flightgear starts in unusable state because it can't find the file glider-panel.xml for the panel.

== External links ==
== Related content ==
=== Related lists ===
[[Aircraft]]

[[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Gliders]]
[[Category:Aircraft TODO]]

North American P-51 Mustang

2007-10-14T12:52:23Z

Cespenar:

{{Mergefrom|P-51D Mustang Manual}}

{{infobox Aircraft
|image =[[Image:P51d-mustang.png|320px]]
|name =P51D Mustang
|type =Military aircraft
|fdm =
|status =
|authors =Jim Wilson
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* front wheels do rotate even when airplane is standing still
* when flaps are lowerd, you can see inside the 3d model where the flaps where before
* no cockpit light at night visible
* propeller do rotate in wrong direction from some view points
* aircraft has no shadow
* landing lights and strobe lights are missing
* aircraft has no wheel well area for the landing gears

3d Cockpit:

* no cockpit light at night available
* no ruder control pedals available
* switches and levers can't be controlled with mouse
* cockpit is only partly textured (sidewalls and cockpit fron have no textures)
* no pilot present in cockpit

General:

* engine sound in cockpit does not differ from outside engine sound
* no hud available

== External links ==
== Related content ==
[[P-51D Mustang Manual]]

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Northrop/McDonnell Douglas YF-23

2007-10-14T12:51:57Z

Cespenar:

YF-23 ATF prototype (YASim FDM)
YF-23-yasim Northrop/McDonnell Douglas YF-23 ATF

{{infobox Aircraft
|image =[[Image:YF-23.jpg|320px]]
|name =Northrop/McDonnell Douglas YF-23
|type =Military Aircraft
|fdm =YASim
|status =beta
|authors =Lee Elliott
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
* Outside:
* no cockpit light at night visible
* no aircraft light available
* no jetstream visible
* weapon bay doors can't be opened

3d Cockpit

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* no cockpit instruments available
* cockpit is not textured
* no pilot present in 3d cockpit
* cockpit window has no windscreen wipers

General:

* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off
* hud can't be turned off
* when pressing the "f" and "k" key I can extend some sort of flaps (don't know the name of them) but I can't retract them back.
* cockpit is open by default, but i don't know how to close it
** Press shift-b
* aircraft has the wrong elevation (approximately 20 meter above the runway) after pressing the reset key

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Northrop T-38 Talon

2007-10-14T12:51:45Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Northrop_T-38.jpg|320px]]
|name =Northrop T-38
|type =Military aircraft
|fdm =
|status =early production
|authors =David Culp (FDM), Erik Hofman/Innis Cunningham/Capt. Slug (3D)
}}

{|
|__TOC__
|}

"In the mid-1950s, the USAF required a trainer with higher performance than the T-33 to better prepare student pilots for the latest tactical aircraft that were then coming into service. The aircraft chosen was the T-38A which offered high performance with low maintenance and operating costs. The T-38A became the USAF's first supersonic trainer." Source: [http://www.wpafb.af.mil/museum/modern_flight/mf11.htm NORTHROP T-38A "TALON"]

Read more on the Wikipedia about the [http://en.wikipedia.org/wiki/T-38_Talon T38 Talon]

The current model uses a 2D cockpit, and supports display of AI aircraft objects on an air-air radar screen. See the Aircraft/Instruments/radar.xml file for details, or fly the T-38 for a demo. Yes, the T-38 does not actually have radar, but it was chosen here to be the demonstrator aircraft for radar. It also demonstrates how instruments can be minimized and maximized in 2D panels.

== Development status/Issues/Todo ==
Outside:

* flaps are extended by default
* first cockpit seat is not solid, it can be seen through the seat when looking from behind.
* no pilot/co-pilot in cockpit visible
* aircraft has no shadow
* no aircraft light available
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust (but this aircraft doesn't have reverse thrust)

3d Cockpit:

* no textures used
* not stick, rudder, throttle gear and flap objects

General:

* engines have no sound
* engine sound in cockpit does not differ from outside engine sound
* no hud available
* no sound when toggling flaps

== External links ==
== Related content ==

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

North American X-15

2007-10-14T12:51:34Z

Cespenar:

{{infobox Aircraft
|image =[[Image:X15.jpg|320px]]
|name =North American X-15
|type =
|fdm =
|status =
|authors =Mike Hill, Jon S. Berndt (FDM), John Check
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* textures are bumpy
* flaps are not animated
* rudder, ailerons and pitch elevator are not animated
* cockpit windows are not transparent
* aircraft has no shadow
* no aircraft light available
* there is no stream behind the rocket engine visible

3d Cockpit:

* no 3d cockpit available

General:

* engines have no sound
* no hud available
* aircraft has no braking parachutes

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

McDonnell Douglas F-15E Strike Eagle

2007-10-14T12:50:54Z

Cespenar:

{{infobox Aircraft
|image =[[Image:McDonnell Douglas F-15.jpg|320px]]
|name =McDonnell Douglas F-15 Eagle
|type =Military aircraft
|fdm =
|status =alpha
|authors =Erik Hofman
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* aircraft has no 3d model

3d Cockpit:

* 3d cockpit is not available

General:

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Lockheed F-104 Starfighter

2007-10-14T12:49:14Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Lockheed_F104.jpg|320px]]
|name =Lockheed F-104 Starfighter
|type =Military aircraft
|fdm =
|status =beta
|authors =Erik Hofman
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* flaps are in wrong position by default after starting flightgear
* flaps can't be triggered
* no cockpit light at night visible
* no pilot visible
* wings are not textured
* engine turbines do not rotate or are not visible
* aircraft has no shadow
* no aircraft light available
* aircraft has no wheel well area for the landing gears
* baydoors for gears are missing
* no jetstream visible
* nozzle do not change shape when changing thrust
* there are no flaps when using reverse thrust

3d Cockpit:

* no cockpit light at night available
* no rudder/stick control in 3d cockpit available
* no ruder control pedals available
* no switches and leverls available
* no elevator trim control available
* no cockpit instruments available
* cockpit is not textured
* no pilot and co pilot present
* cockpit window has no windscreen wipers

General:

* engine sound missing during flight and on ground
* hud is not available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Hawker Sea Hawk FGA.6

2007-10-14T12:49:02Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Hawker_Seahawk.jpg|320px]]
|name =Hawker Seahawk
|type =Military aircraft
|fdm =
|status =early-production
|authors =Lee Elliott, Vivian Meazza
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:
* engine turbine does not rotate or is not visible -- see [[Hawker Hunter|Hunter]]
* nozzle do not change shape when changing thrust
** it doesn't
* there are no flaps when using reverse thrust
** there are none

3d Cockpit:

* the major part of the cockpit has no light at night available -- see Hunter
* no elevator trim control available -- see Hunter
* cockpit is not textured -- see Hunter
* pilot is not textured -- see Hunter

General:

* engine sound in cockpit does not differ from outside engine sound -- see Hunter
* engines can't be turned off
** needs improved fuel system
* no hud available
** none in real life - disabled in model

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Hawker Hunter

2007-10-14T12:48:38Z

Cespenar:

hunter-2tanks Hawker Hunter(YASim)

{{infobox Aircraft
|image =[[Image:Hawker_Hunter.png|320px]]
|name =Hawker Hunter
|type =Military aircraft
|fdm =YASim
|status =early-production
|authors =Vivian Meazza
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* aircraft is textured but hull could need a material texture (maybe we need multi texturing for that)
** possible in due course
* engine turbine does not rotate or is not visible
** only just visible from certain angles in real life
* low priority for implemenatation
* probably not worth the vertex count
* nozzle do not change shape when changing thrust
** it doesn't

3d Cockpit:

* no elevator trim control available
** controlled by the tophat on the control column in real life
* use the keyboard or joystick
* cockpit is not textured
** unlikely to be changed
* pilot is not textured
** too difficult right now

General:

* engine sound in cockpit does not differ from outside engine sound
** later
* engines can't be turned off
** needs an improved fuel system to be modelled
* no hud available
** no HUD in real life - disabled in model
* flightgear crashes when using hunter-2tanks alias

== External links ==
== Related content ==

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

General Dynamics F-16 Fighting Falcon

2007-10-14T12:48:29Z

Cespenar:

f16-3d General Dynamics F-16 w. 3d cockpit

{{infobox Aircraft
|image =[[Image:General_Dynamics_F16.jpg|320px]]
|name =General Dynamics F16
|type =Military aircraft
|fdm =
|status =early-production
|authors =Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error.
* no cockpit light at night visible
* no pilot and co pilot visible
* engine turbines do not rotate
* strobe and landing lights are available and bound to the right properties, but the properties are not triggered by any key stroke.
* nozzle do not change shape when changing thrust

3d Cockpit:

* no cockpit light at night available
* rudder/stick control is available but it is not animated
** Note: The stick in the F-16 doesn't move at all because it is driven by the pressure pushed on the stick, not the movement itself. So this is NOT an error.
* switches and leverls available but can't be triggered with the mouse
* no cockpit instruments available
* cockpit is only barely textured
* no pilot present in 3d cockpit

General:

* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off
* hud can't be turned off

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Fokker Dr.I

2007-10-14T12:48:19Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Fokker_DrI.jpg|320px]]
|name =Fokker Dr.I
|type =Historical aircraft
|fdm =
|status =production
|authors =Michael Selig (FDM), Erik Hofman (3D model)
}}

{|
|__TOC__
|}

== Development Status/Issues/Todo ==
== External links ==
== Related Content ==

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

Fokker 50

2007-10-14T12:48:07Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Fokker50.jpg|320px]]
|name =Fokker 50
|type =Airliner
|fdm =
|status =beta
|authors =Erik Hofman
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* passenger windows are not transparent - wings and engines are not textured
* aircraft has no shadow
* no aircraft light available

3d Cockpit:

* 3d cockpit is not available

General:

* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off
* hud is not available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]

Fokker 100

2007-10-14T12:47:34Z

Cespenar:

{{infobox Aircraft
|image =[[Image:Fokker100.jpg|320px]]
|name =Fokker 100
|type =Airliner
|fdm =
|status =beta
|authors =Erik Hofman
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Outside:

* aircraft is barely textured (wings are not textured)
* engine turbines do not rotate
* aircraft has no shadow
* no aircraft light available
* no jetstream visible
* there are no flaps when using reverse thrust (the animation is there but not implemented in the FDM)

3d Cockpit:

* 3d cockpit is not available

General:

* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off
* hud is not available

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:Aircraft TODO]]