Ca/FlightGear: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 5: Line 5:
|logosize          = 200px
|logosize          = 200px
|image            = Boeing 777-200ER cockpit.jpg
|image            = Boeing 777-200ER cockpit.jpg
|alt              = The cockpit of the [[Boeing 777-200ER]]
|alt              = Cabina del [[Boeing 777-200ER]]
|developedby      = FlightGear developers & contributors
|developedby      = Desenvolupadors i contribuïdors de FlightGear
|initialrelease    = July 17, 1997
|initialrelease    = 17 jul 1997
|latestrelease    = {{current release|full}} ({{#time: j F Y |{{current release|fulldate}}}})
|latestrelease    = {{current release|full}} ({{#time: j F Y |{{current release|fulldate}}}})
|writtenin        = C and C++
|writtenin        = C i C++
|os                = Windows, Mac OS X, Linux, and FreeBSD<ref>{{cite web|url=http://www.flightgear.org/download/main-program/|title=http://www.flightgear.org/download/main-program/|accessdate=February 15, 2015}}</ref>
|os                = Windows, Mac OS X, Linux, i FreeBSD<ref>{{cite web|url=http://www.flightgear.org/download/main-program/|title=http://www.flightgear.org/download/main-program/|accessdate=February 15, 2015}}</ref>
|platform          = Cross-platform
|platform          = Multiplataforma
|developmentstatus = Active (1996-present)
|developmentstatus = Actiu (1996-actualitat)
|type              = Flight simulator
|type              = Simulador de vol
|license          = [[GNU General Public License]]
|license          = [[GNU General Public License]]
|website          = http://www.flightgear.org/
|website          = http://www.flightgear.org/
Line 27: Line 27:
{{main article|FlightGear History}}
{{main article|FlightGear History}}


FlightGear development started with an online proposal in 1996, using custom 3D graphics code. Development of an [[OpenGL]] based version was spearheaded by Curtis Olson starting in 1997. Many people have contributed to the project in the years since its inception.
El desenvolupament de FlightGear va començar amb una proposta en línia el 1996, utilitzant codi personalitzat de gràfics en 3D. El desenvolupament d'una versió basada en [[OpenGL]] va ser encapçalat per Curtis Olson iniciant-se el 1997. Moltes persones han contribuït al projecte des dels seus inicis.


FlightGear incorporated other open-source resources, including the LaRCsim flight model from NASA, and freely available elevation data. The first working binaries, using OpenGL for 3D graphic code, came out in 1997. Enthusiastic development of newer versions for several years resulted in progressively more stable and advanced versions. By 2001, the team was releasing new beta versions regularly, and by 2005, the maturity of software lead to more widespread reviews, and increased popularity. 2007 marked a formal transition out of beta development with the release of version 1.0.0, ten years after FlightGear's first release in 1997.
FlightGear va incorporar altres recursos de codi obert, inclòs el model de vol LaRCsim de la NASA, i dades d'elevació disponibles lliurement. Els primers binaris funcionals, utilitzant el codi gràfic OpenGL per a 3D, van sortir a la llum el 1997. El desenvolupament entusiasta de les versions més recents durant diversos anys va resultar en versions progressivament més estables i avançades. L'any 2001, l'equip publicava regularment noves versions beta i, per a l'any 2005, la maduresa del programari va conduir a revisions més esteses i una major popularitat. El 2007 va marcar una transició formal del desenvolupament beta amb l'alliberament de la versió 1.0.0, deu anys després del primer llançament de FlightGear el 1997.


[[File:FG-A-10.jpg|thumb|270px|3D Cockpit panel for [[A-10]] in version 1.0.0 in 2008]]
[[File:FG-A-10.jpg|thumb|270px|Panell de cabina en 3D d'un [[A-10]] en la versió 1.0.0 el 2008]]


In 2008, version 1.9.0 of FlightGear included a major change from [[PLIB]] to [[OSG]], which caused the temporarily loss of some features like 3D clouds and shadows, while newly added features, such as particles, imparted another degree of realism to the simulation.   
El 2008, la versió 1.9.0 de FlightGear va incloure un canvi important de [[PLIB]] a [[OSG]], que va provocar la pèrdua temporal d'algunes característiques com núvols 3D i ombres, mentre que s'afegien noves funcions, com les partícules, es va assolir un millor grau de realisme a la simulació.   


== Software ==
== Programari ==


The simulation engine in FlightGear is called [[SimGear]]. It is used both as an end-user application and in academic and research environments, for the development and pursuit of flight simulation ideas.
The simulation engine in FlightGear is called [[SimGear]]. It is used both as an end-user application and in academic and research environments, for the development and pursuit of flight simulation ideas.
Line 54: Line 54:
* 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 ===
=== Dependències ===
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.


== Hardware ==
== Maquinari ==
Hardware needed for FlightGear is narrowed to machines that support [[OpenGL]] and 3D hardware acceleration, with NVIDIA hardware having better support. Early versions had support for 3dfx cards, though this dropped as hardware requirements increased.
Hardware needed for FlightGear is narrowed to machines that support [[OpenGL]] and 3D hardware acceleration, with NVIDIA hardware having better support. Early versions had support for 3dfx cards, though this dropped as hardware requirements increased.


Line 68: Line 68:
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.  Finally, ''[[WorldEditor]]'' 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.  Finally, ''[[WorldEditor]]'' is an editor for airport runways and taxiways.


=== Aircraft ===
=== Aeronaus ===
{{Main article|Table of models}}
{{Main article|Table of models}}


Line 75: Line 75:
[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]
[[File:EHAM.jpg|thumb|270px|[[Boeing 737-300|Boeing 733]] docked in the [[EHAM]] scenery]]


=== Scenery ===
=== Escenari ===
{{Main article|Scenery}}
{{Main article|Scenery}}
FlightGears [[world scenery]] project contains elevation and landclass data of the enitre world. Objects -like terminals, windmills and bridges- are collected in the [[FlightGear Scenery Database|Scenery Database]].
FlightGears [[world scenery]] project contains elevation and landclass data of the enitre world. Objects -like terminals, windmills and bridges- are collected in the [[FlightGear Scenery Database|Scenery Database]].


=== Networking and multi-display ===
=== Xarxa i multipantalla ===
Several networking options allow FlightGear to communicate with other instances of FlightGear. A [[Multiplayer Howto|multiplayer]] protocol is available for using FlightGear on a local network in a multi aircraft environment. This could be used for formation flight or [[ATC|control tower]] simulation. Multiplayer was soon expanded to allow playing over the internet. Other features include a Google maps based moving up that allows users to observe where other players are.
Several networking options allow FlightGear to communicate with other instances of FlightGear. A [[Multiplayer Howto|multiplayer]] protocol is available for using FlightGear on a local network in a multi aircraft environment. This could be used for formation flight or [[ATC|control tower]] simulation. Multiplayer was soon expanded to allow playing over the internet. Other features include a Google maps based moving up that allows users to observe where other players are.


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.


== FlightGear code vs. binaries ==
== Codi contra binaris ==
Unlike most commercial software, the project release dates only apply to a release of code, not an executable program. To create a runnable program the code must be compiled, which requires several specific libraries, including some general ones and, in some cases some platform specific ones. However, since this too difficult for most mainstream users, other contributors will work to make binaries available for a specific platform and operating system. These packages vary in their stability, performance, dependencies, and how up to date they are with the code base. For example, some older binaries work on Mac OS 9 but newer releases require specific Mac OS X versions.
Unlike most commercial software, the project release dates only apply to a release of code, not an executable program. To create a runnable program the code must be compiled, which requires several specific libraries, including some general ones and, in some cases some platform specific ones. However, since this too difficult for most mainstream users, other contributors will work to make binaries available for a specific platform and operating system. These packages vary in their stability, performance, dependencies, and how up to date they are with the code base. For example, some older binaries work on Mac OS 9 but newer releases require specific Mac OS X versions.


Line 91: Line 91:
Binaries for other platforms such as IRIX are no longer supported, although pre-1.0 releases may work and can be found in the [[FlightGear Git|git source code repositories]].
Binaries for other platforms such as IRIX are no longer supported, although pre-1.0 releases may work and can be found in the [[FlightGear Git|git source code repositories]].


==Applications and usages==
==Aplicacions i usos==
{{Main article|Professional and educational FlightGear users}}
{{Main article|Professional and educational FlightGear users}}
FlightGear has been used and is being used in a wide range of projects in academia, industry (including NASA) and home-built cockpits.
FlightGear has been used and is being used in a wide range of projects in academia, industry (including NASA) and home-built cockpits.


== Reviews ==
== Anàlisis ==
{{Main article|FlightGear Reviews}}
{{Main article|FlightGear Reviews}}


== External links ==
== Enllaços externs ==
{{Main article|Links}}
{{Main article|Links}}
* {{Wikipedia|FlightGear}}
* {{Wikipedia|FlightGear}}
* [http://www.flightgear.org Official website]
* [http://www.flightgear.org Lloc web oficial]
* [http://forum.flightgear.org/ Forums]
* [http://forum.flightgear.org/ Fòrums]
* [http://code.google.com/p/flightgear-bugs/ Bug tracker]
* [http://code.google.com/p/flightgear-bugs/ Errors]
* [http://www.flightgear.org/proposal-3.0.1 Original FlightGear Proposal]
* [http://www.flightgear.org/proposal-3.0.1 Proposta de FlightGear Original]


{{Appendix}}
{{Appendix}}
449

edits