FlightGear: Difference between revisions

Jump to navigation Jump to search
571 bytes added ,  20 September 2008
update
(update)
Line 1: Line 1:
'''FlightGear''' is a collaborative project that aims to create a sophisticated free, completely open-source flight simulator framework.
'''FlightGear''' flight simulator is a sophisticated free, completely open-source flight simulator framework, created by volunteers of the FlightGear project.


The project was started in 1996, with the first release in 1997. The latest public release is 1.0.0 in December 2007, with specific builds for a variety of operating systems including Microsoft Windows (Win 32), Mac OS X, Linux, IRIX, and Solaris.
The project was started in 1996, with the first release in 1997. The latest public release is [[FlightGear 1.0 feature showcase|1.0.0]] in December 2007, with specific builds for a variety of operating systems including Microsoft Windows (Win 32), Mac OS X, Linux, IRIX, and Solaris. (see [[http://www.flightgear.org/Downloads/ FlightGear Download Central])


Released under the terms of the GNU General Public License, FlightGear is free software.
Released under the terms of the [[GNU General Public License]], FlightGear is free software.


==History==
==History==
Line 36: Line 36:
Early version used a FDM based on LaRCsim by NASA, which was replaced with more flexible FDM.  
Early version used a FDM based on LaRCsim by NASA, which was replaced with more flexible FDM.  


*JSBSim - the default flight dynamics model software since 2000.
*[[JSBSim]] - the default flight dynamics model software since 2000.
*YASim - another FDM using different calculation method. Introduced starting in 0.7.9 in 2002.
*[[]]YASim - another FDM using different calculation method. Introduced starting in 0.7.9 in 2002.
*UIUC - another included FDM, developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, also made use of LaRCsim.
*[[UIUC]] - another included FDM, developed by the UIUC Applied Aerodynamics Group at University of Illinois at Urbana-Champaign, also made use of LaRCsim.
*Flight Gear can also be setup to render using inputs from an external FDM source, such as from Matlab.
*Flight Gear can also be setup to render using inputs from an external FDM source, such as from [[Matlab]].
*Other custom FDM for a specific aircraft type have been written, such as for lighter than air aircraft.
*Other custom FDM for a specific aircraft type have been written, such as for lighter than air aircraft.


===FlightGear dependencies===
===FlightGear dependencies===
Unlike commercial software titles, the main output of the project is simply the release of a collection of code. To turn it into a usable program it must be compiled for a given platform. The software libraries used to create FlightGear have varied over time. The main one is [[SimGear]], which is the underlying sim engine for FlightGear. TerraGear is not a dependency, but simply a name for the default terrain data program in FlightGear. OpenAL is used for sound/audio software, including support for SDL (since 0.9.5). PLIB is used for hardware support routines, formerly used for sound support also which was taken over by OpenAL. OpenGL is used for its integrated 3D graphics routines, and other hardware acceleration (namely DirectX) is not supported. OpenSceneGraph is also integrated into FlightGear. Finally, Simple DirectMedia Layer is a software library which is used for compiling. Some of the dependencies vary depending on which platform the code is being compiled for. FlightGear users must either compile the code themselves, or find a third party to release a binary, if it is not among the ones available from the project.
Unlike commercial software titles, the main output of the project is simply the release of a collection of code. To turn it into a usable program it must be compiled for a given platform. The software libraries used to create FlightGear have varied over time. The main one is [[SimGear]], which is the underlying sim engine for FlightGear. [[TerraGear]] is not a dependency, but simply a name for the default terrain data program in FlightGear. OpenAL is used for sound/audio software, including support for SDL (since 0.9.5). PLIB is used for hardware support routines, formerly used for sound support also which was taken over by OpenAL. [[OpenGL]] is used for its integrated 3D graphics routines, and other hardware acceleration (namely DirectX) is not supported. [[OpenSceneGraph\\ is also integrated into FlightGear. Finally, [[Simple DirectMedia Layer]] is a software library which is used for compiling. Some of the dependencies vary depending on which platform the code is being compiled for. FlightGear users must either compile the code themselves, or find a third party to release a binary, if it is not among the ones available from the project.


===Networking and multi-display===
===Networking and multi-display===
Line 49: Line 49:


Several instances of FlightGear can be synchronized to allow for a [[multi-monitor]] environment. If all instances are running at the same frame rate consistently, it is possible to get good and tight synchronization between displays.
Several instances of FlightGear can be synchronized to allow for a [[multi-monitor]] environment. If all instances are running at the same frame rate consistently, it is possible to get good and tight synchronization between displays.
see [[Presentation Recipe]]


===Additional software===
===Additional software===
Line 55: Line 57:
There are programs that are either integrated into FlightGear (dependencies) or perform a function with it. Some of these are included in the release of FlightGear for a specific platform but made by the project, while others are independently distributed but are hosted by the FlightGear project.  
There are programs that are either integrated into FlightGear (dependencies) or perform a function with it. Some of these are included in the release of FlightGear for a specific platform but made by the project, while others are independently distributed but are hosted by the FlightGear project.  


One major additional software is the actual interface for launching an executable of FlightGear. For most of its early life FlightGear was only run through command line interfaces. However, the FlightGear Launch Control has been included with the ''FG launcher'' front-end since 0.9.3 in 2003. ''KFreeFlight'' is a launcher/front-end for KDE. ''FGTools'' is an alternative windows launcher front-end. ''FGKicker'' is a GTK+ based front-end.
One major additional software is the actual interface for launching an executable of FlightGear. For most of its early life FlightGear was only run through command line interfaces. However, the FlightGear Launch Control has been included with the ''[[FG launcher]]'' front-end since 0.9.3 in 2003. ''[[KFreeFlight]]'' is a launcher/front-end for KDE. ''[[FGTools]]'' is an alternative windows launcher front-end. ''[[FGKicker]]'' is a GTK+ based front-end.


Other significant programs include editors and projects for Terrain Data. ''[[Atlas]]'' is a chart/map support for FlightGear; ''[[Kelpie Flight Planner]]'' is a Java based flight planner for FlightGear. ''[[FlightGear Scenery Designer]]'' is a FlightGear scenery editor for working with terrain data. The ''[[World Custom Scenery Project]]'' is a project coordinating custom scenery efforts. Finally, ''[[TaxiDraw]]'' is an editor for airport runways and taxiways.
Other significant programs include editors and projects for Terrain Data. ''[[Atlas]]'' is a chart/map support for FlightGear; ''[[Kelpie Flight Planner]]'' is a Java based flight planner for FlightGear. ''[[FlightGear Scenery Designer]]'' is a FlightGear scenery editor for working with terrain data. The ''[[World Custom Scenery Project]]'' is a project coordinating custom scenery efforts. Finally, ''[[TaxiDraw]]'' is an editor for airport runways and taxiways.
See also [[Recommend software]]


==FlightGear code vs. binaries==
==FlightGear code vs. binaries==
Line 66: Line 70:
*Win-32 has ~138 Mb package (v0.9.10) (For Windows 98, 2000, ME, 32-bit XP)  
*Win-32 has ~138 Mb package (v0.9.10) (For Windows 98, 2000, ME, 32-bit XP)  
*Linux- pre-built packages for specific Linux distributions
*Linux- pre-built packages for specific Linux distributions
**Slackware package (v0.9.10), Fedora Core 2,3,4 packages (v0.9.10), Pardus (v0.9.10), Debian (v0.9.9)  
**[[Slackware\\ package (v0.9.10), [[Fedora Core\\ 2,3,4 packages (v0.9.10), [[Pardus\\ (v0.9.10), Debian (v0.9.9)  
*Solaris packages either for it running on either SPARC or x86 processors.
*Solaris packages either for it running on either SPARC or x86 processors.
** SPARC (v0.9.8),  x86 (v0.9.9)  
** SPARC (v0.9.8),  x86 (v0.9.9)  
*Silicon Graphics IRIX
*Silicon Graphics IRIX
**SGI binaries for (v0.9.9)  
**SGI binaries for (v0.9.9)  
*Mac OS X  
*[[Mac OS X]]]
**Mac OS 10.4 (v0.9.10)  
**Mac OS 10.4 (v0.9.10)  
**Mac OS 10.3 (v0.9.9)  
**Mac OS 10.3 (v0.9.9)  
*FreeBSD has a package for(v0.9.10)
*[[FreeBSD]] has a package for(v0.9.10)


==Critical reaction==
==Critical reaction==
''see [[FlightGear reviews]]''
Although not developed as a game in the traditional sense, FlightGear has nevertheless undergone reviews in a number of online and offline publications. ''FlightGear'' 0.9.10 received many reviews, being highlighted as an accurate simulation but requiring patience and some pre-game work. PC Magazine noted how it is designed to be easy to add new aircraft and scenery.
Although not developed as a game in the traditional sense, FlightGear has nevertheless undergone reviews in a number of online and offline publications. ''FlightGear'' 0.9.10 received many reviews, being highlighted as an accurate simulation but requiring patience and some pre-game work. PC Magazine noted how it is designed to be easy to add new aircraft and scenery.


Line 205: Line 211:


All Official aircraft for 0.9.10, with flight data model type and cockpit type listed for some such as found on the 0.9.10 CD release of FlightGear. Some aircraft are FDM only. Third party aircraft are excluded from the list (such as in additional add-ons). Aircraft in 0.9.10 installer are noted with a *, and ** for the 1.0 installer. New or heavily re-worked aircraft up to 1.0 public release, including some that came out with the 0.9.11-pre1 FlightGear(pre-release version) as well as 9.10 aircaft. Many aircraft that have not been updated no longer work, such as ones before .7.x/.8.x/.9.x as well as a number in the later releases that were not maintained to the current version depending on the model and its dependencies.  
All Official aircraft for 0.9.10, with flight data model type and cockpit type listed for some such as found on the 0.9.10 CD release of FlightGear. Some aircraft are FDM only. Third party aircraft are excluded from the list (such as in additional add-ons). Aircraft in 0.9.10 installer are noted with a *, and ** for the 1.0 installer. New or heavily re-worked aircraft up to 1.0 public release, including some that came out with the 0.9.11-pre1 FlightGear(pre-release version) as well as 9.10 aircaft. Many aircraft that have not been updated no longer work, such as ones before .7.x/.8.x/.9.x as well as a number in the later releases that were not maintained to the current version depending on the model and its dependencies.  
''Note, this list is not maintained to the latest aircraft, '''see [[Table of Models]]'' ''
''Covers data up to but not after the release of FlightGear version 1.0 in December 2007''


{| border="1" class="wikitable"
{| border="1" class="wikitable"
Line 520: Line 531:
| [[Rascal 110]] (R/C)*  || YASim, JSBSim ||
| [[Rascal 110]] (R/C)*  || YASim, JSBSim ||
|-
|-
| Malolo1  (R/C) ||
| [[Malolo1  (R/C)]] ||
|-
|-
| Manta (R/C) (FDM only) || || - ||
| Manta (R/C) (FDM only) || || - ||
|-
|-
| Ogel ||JSBSim ||  ||  || 0.9.10  
| [[Ogel]] ||JSBSim ||  ||  || 0.9.10  
|-
|-
| [[Santa Claus]] Sleigh ||  || 3d cockpit
| [[Santa Claus]] Sleigh ||  || 3d cockpit
Line 537: Line 548:
|}
|}


*Aircraft in 9.10 win-32 basic installer- [[Wright Flyer|1903 Wright Flyer]], [[Boeing 737-300]], Fairchild [[A-10]]  Thunderbolt II, [[Northrop T-38]], Messerschmitt [[Bf 109]] G14, [[Eurocopter]] [[Bo105]], [[Cessna 172]]P Skyhawk, [[Cessna 310]] , [[Cessna Citation|Cessna Citation Bravo]], [[F-16 Falcon]], [[Hawker Hunter]] GA11, [[Piper J3 Cub]], [[P-51D Mustang]], [[Piper Cherokee|Piper Cherokee Warrior II]], Rascal 110 (R/C model aircraft), UFO  (flying saucer), as well  as several developmental UIUC aircraft.


**Aircraft in 1.00 win-32 basic installer- [[787]], Fairchild [[A-10|A-10]] Thunderbolt II, Beech 1900D, Bf 109, Bo 102, Bocian 1E, C172, DH2, J3 Cub, English Electric Lightning, P-51D, PA28-161, PA34-200, Seahawk, UFO, Sopwith Camel, T-38
*Aircraft in 9.10 win-32 basic installer- [[Wright Flyer|1903 Wright Flyer]], [[Boeing 737-300]], Fairchild [[A-10]]  Thunderbolt II, [[Northrop T-38]], Messerschmitt [[Bf 109]] G14, [[Eurocopter]] [[Bo105]], [[Cessna 172]]P Skyhawk, [[Cessna 310]] , [[Cessna Citation|Cessna Citation Bravo]], [[F-16 Falcon]], [[Hawker Hunter]] GA11, [[Piper J3 Cub]], [[P-51D Mustang]], [[Piper Cherokee|Piper Cherokee Warrior II]], Rascal 110 (R/C model aircraft), UFO  (flying saucer), as well  as several developmental UIUC aircraft. (see [[FlightGear 0.9.10 aircraft]])
 
*Aircraft in 1.00 win-32 basic installer- [[787]], Fairchild [[A-10|A-10]] Thunderbolt II, Beech 1900D, Bf 109, Bo 102, Bocian 1E, C172, DH2, J3 Cub, English Electric Lightning, P-51D, PA28-161, PA34-200, Seahawk, UFO, Sopwith Camel, T-38 (see [[FlighGear 1.0 default aircraft]])


==External links==
==External links==
3,032

edits

Navigation menu