Es/Preguntas frecuentes: Difference between revisions

Jump to navigation Jump to search

Es/Preguntas frecuentes (view source)

Revision as of 17:05, 6 October 2009

25,084 bytes removed ,  6 October 2009
no edit summary
No edit summary
Line 1: Line 1:
{{Languages|FAQ}}
=== ¿ Por qué FlightGear no quiere compilar ? ===
Destinos frecuentes de ayuda: [[Aircraft/es|Aeronaves]], [[Howto: Multiplayer/es|Ayuda Multijugador]], [[Installing Scenery|Instalar Escenarios]], [[Flying the helicopter/es| Volar el Helicóptero]].


'''Esta lista de FAQ Preguntas y Respuestas Frecuentes, no ha sido significativamente actualizada desde 2006.'''<br/>
Bien, esto depende. Primero asegurate que estas usando las apropiadas versiones de FlightGear, [[SimGear]], plib, zlib. Si alguno de estos paquetes estan fuera de sincronía con los otros, la compilación puede fallar. Mira también [[Building FlightGear]]


''' Sientete libre de hacer aportaciones, cambios, o correcciones.'''
La página de descargas de FlightGear (http://www.flightgear.org/Downloads/) podría decirte que versión necesitas si estas intentando compilar la última publicación estable. Si usas "instantaneas" de desarrollo, asegurate de que los tres paquetes estén actualizados.


== La  FAQ ==
Asegurate que también tienes algunas implementaciones de OpenGL con superabundante soporte para los apropiados archivos de cabecera. Los usuarios deGNU/Linux con tarjetas nVidia deben asegurarse de tener los ultimos drivers de nVidia. Otros usuarios de GNU/Linux se aseguraran de tener Mesa3D (http://mesa3d.org/) y su servidor X instalado correctamente.
=== ¿ Donde puedo conseguir la ultima versión de esta FAQ ? ===
Si tus problemas persisten, subscribete a nuestra lista de correo de Usuarios de FlightGear y haznos saber que poblema estas teniendo. Mira en http://www.flightgear.org/mail.html para ayudar con esto.
 
http://www.flightgear.org/Docs/FlightGear-FAQ.html
 
=== ¿ Con quién puedo contactar si tengo comentarios sobre esta  FAQ? ===
 
Aporta tu comentario a esta página de discusión de la FAQ [[Talk:FAQ]]
 
=== ¿ Es muy antiguo este documento ? ===
 
Haz Click en el botón Historia in el menu de la izquierda.
 
=== ¿ Que otra documentación importante debo leer ? ===
 
* [http://flightgear.org/Docs/getstart/getstart.html Guia de Primeros Pasos]
* [[New to FlightGear/es|Nuevo en FlighGear]]
* Mira también tambien en el directorio de la distribución fuente para otros varios documentos de ayuda FlightGear/docs-mini/.
* Mira también la otra [http://www.flightgear.org/Docs/FAQ.shtml FAQ]
 
== Distribución ==
 
=== Donde puedo conseguir FlightGear? ===
 
La página oficial de descarga es http://www.flightgear.org/Downloads/. Código Fuente es nuestra forma primaria de distribución, pero binarios precompilados estan disponibles para Windows y SGI IRIX.
 
Alternativamente, FlightGear es empaquetado para GNU/Linux en SuSE, Debian (sid), y Mandrake (Cooker) y puede ser directamente instalado a través de estas distribuciones. De todas formas hoy en dia desde cualquier sistema GNU/Linux se puede instalar FlightGear fácilmente solo tienes que usar el menú Aplicaciones/Añadir y Quitar. O bien dentro buscas en la sección juegos o bien haces una busqueda. Luego con un solo click lo tendrás instalado.
 
=== Instalar FlightGear en Ubuntu? ===
 
FlightGear puede ser instalado directamente desde el Gestor de Paquetes Synaptic.
Abrir el Gestor de Paquetes Synaptic, buscar FlightGear y seguir las instrucciones. Para Ubuntu 7.10 tendrás la capacidad de instalar Flight Gear 9.10
 
 
=== ¿ Que hay si quiero intalar FlightGear 1.0, o versión posterior en Ubuntu? ===
 
Primero instala WINE desde Synaptic, luego ejecuta el instalador FGSetup con un click en el botón derecho y selecionando abrir con WINE. Ya simplemente sigue las instrucciones. Todo parece ir bien y es bastante rápido excepto para el primer arranque de pantalla donde la lista de aeronaves no esta visible. Para información de WINE mira en http://www.winehq.org/
 
=== ¿ Que es la palabra de paso (password) para el servidor FTP ? ===
 
El servidor FTP usa procedimientos estandar de login anonimo. Identificandose con el nombre de usuario "anonymous" y usa tu dirección de correo electronico como palabra de paso. La mayoria de los clientes FTP y navegadores de red hacen esto automáticamnete por ti.
 
=== ¿ Por qué el servidor FTP no quiere dejarme entrar con la información de identificación correcta (login)? ===
 
Generalmente esto significa que el servidor está em el limite de su capacidad. Deberias recibir un mensaje diciendo esto, pero tu cliente FTP puede que te lo oculte. Tus opciones son las de seguir intentando hasta que se abra un espacio o intertarlo conectando con unos de nuestros servidores espejo de FTP listados en http://flightgear.org/mirrors.html.
 
=== ¿ Donde puedo encontrar el último código fuente de desarrollo? ===
 
El último código de desarollo está disponible para cualquiera a travás de nuestro repositorio CVS. Mira en http://www.flightgear.org/cvsResources/ para más detalle.
 
Por otro lado, puedes conseguir 'pantallazos relativamente actualizados del arbol de desarrollo en ftp://flightgear.sourceforge.net/pub/flightgear/Devel/Snapshots/.
 
=== ¿ Que es SimGear, y porqué lo necesito ? ===
 
[[SimGear]] es una libreria de código de soporte. SimGear es solo necesario si planeas compilar FlightGear -- no es necesario para ejecutar binarios pre-compilados. Para más información mira en http://www.simgear.org/. Nota: Cuando se compila FlightGear es muy importante tener la versión equivalente de SimGear.
 
=== ¿ Donde puedo volar y donde puedo conseguir el escenario ? ===
 
Mientras que el paquete base viene solo con el escenaria para el area de la Bahia de San Francisco, actualmente puedes volar en cualquier lugar del mundo. Mira la sección de "Escenarios adicionales" de http://www.flightgear.org/Downloads/ para más información o ve directamente a nuestra utilidad gráfica de descargas de escenarios http://www.flightgear.org/Downloads/world-scenery.html.
 
Visita también nuestra sección "Lugares para Volar" del sitio web (http://www.flightgear.org/Places/) para ayuda de navegación en lugares sorprendentes. (mira también [[Installing Sceneryes/es|Instalar Escenarios]])
 
=== ¿ Donde puedo conseguir diferentes modelos 3D de aviones ? ===
 
Las aeronaves oficiales de FlightGear se pueden encontrar en http://www.flightgear.org/Downloads/aircraft/ . Otras aeronaves en desarrollo se pueden encontran en el [[CVS]], y otras más se pueden encontrar de terceras partes en [[FlightGear hangars| hangares FlightGear]].
 
=== ¿ Como de actualizados estan los datos en FlightGear comparando con el mundo actual ? ===
 
Usamos el mismo juego de datos de ayudas a la navegación que usa X-Plane. El conjunto de datos actual puede encontrarse en los directorios $FGROOT/Navaids/ y $FGROOT/Airports/. Si tienes actualizaciones o correcciones del juego de datos, mira en http://www.flightgear.org/Docs/AirNav/AptNavFAQ.FlightGear.html para instrucciones de contacto con el mantenimiento de la base de datos.
 
=== Donde está el mapa movil? ===
 
Un popular mapa de movimiento está disponible bajo dos proyectos separados llamados [[Atlas]] (mira en http://atlas.sf.net/) y tambien, [[MPmap]] que es un mapa online para multijugador.
 
=== ¿ Por qué no cobraís dinero por esto ? ===
 
FlightGear puede ser descargado grátis desde muchos sitios incluyendo el sitio de FlightGear, pero tambien puede ser comprado en un CD. Aunque ofrecemos este servicio (mira el sitio web), animamos a otros grupos a redistribuirlo para sus usuarios, especialmente entre distribuciones de sistemas operativos las cuales hacen más rápida y fácil la instalación para los nuevos usuarios.
 
Ocasionlmente puedes ver FlightGear en venta en anuncios de páginas y sitios web comerciales bajo otro nombre. Esto puede ser hecho legítimamente, tan allá como los terminos de la licencia mantiene y el costo podria tener el valor si algunas caracteristicas de valor añadido como escenarios adicionales, aeronaves o soporte despues de compra estan incluidos. Desafortunadamente, en la mayoria de los casos que se han visto hasta la fecha parecen se r justamente alguien intentando hacer dinero vendiendo algo que es gratis y no proveiendo un valor añadido real.
 
=== ¿ Como puedo dar los primeros pasos con FlightGear ?===
 
FlightGear [[FlightGear 1.0.0|version 1.0]] puede ser descargado en [http://www.flightgear.org/Downloads/ Central de Descargas], pero la mayoria de las  [[aircraft/es|aeronaves]] necesitan ser separadamente descargadas. [http://www.flightgear.org/Downloads/aircraft/ Aquí] e instalarlas manualmente (mira también [[FlightGear 1.0 default aircraft|FlightGear 1.0 aeronaves por defecto]]). Ten en cuenta los requerimientos del sistema! También, comprueba [[New to FlightGear/es|Nuevo en FlightGear]].
 
== Compiling ==
{{main article|Building Flightgear}}
 
=== ¿ Por qué FlightGear no quieres compilar ? ===
 
Bien, esto depende. Primero asegurate que estas usando las apropiadas versiones de FlightGear, [[SimGear]], plib, zlib. Si alguno de estos paquetes estan fuera de sincronia con los otros, la compilación puede fallar. Mira tambi-en [[Building FlightGear]]
 
La página de descargas de FlightGear (http://www.flightgear.org/Downloads/) podría decirte que versión necesitas si estas intentando compilar la última publicación estable. 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 and the [[Joystick]]-page on the wiki.
 
=== What format should my personal .fgfsrc file be in? ===
 
Your .fgfsrc file should simply be a list of [[Command Line Parameters|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? ===
 
On the menu select View, Rendering Options , then check the box
that says Show Frame Rate
 
=== How do I toggle panel settings? ===
 
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 too 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.
 
=== Why won't the latest versions of some aircraft work in Flight Gear 9.10? ===
 
The latest FlightGear aircraft need to use some files such as new instrument files only released with [[FlightGear 1.0|version 1.0]]. If you are stuck with an older version of FlightGear you can try downloading an earlier version of the aircraft here : http://web.archive.org/web/20060204211745/www.flightgear.org/Downloads/aircraft/
or here:http://ftp.riken.go.jp/pub/FreeBSD/distfiles/flightgear-aircrafts/
 
== 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 planes by using the 3D Convert utility which will convert
the MSFS 3d model to a format used by Flight Gear. You have to add the
animations and parts.
 
Also, although you can import the 3D model and textures, 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 in a 3D design program such as [[AC3D]] or [[PPE]], there may be 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 ==
 
=== Why won't my engine(s) start? ===
 
====Starting engine in single-engine aircraft====
Aircraft vary in their starting procedure.  Some may have an auto-start sequence menu entry or instructions in the aircraft help menu (Press "?").
 
But in general to start the engine on a piston-engine type aircraft, you need:
 
# Fuel - You can run out of fuel, of course, but for certain aircraft, FlightGear may load it with no fuel, making it impossible to start the engines.  Check this in the menu Equipment/Fuel and Payload.
# Correct mixture (generally "rich", ie red knob all the way in)
# Magnetos on (R, L, or both--generally select "both")
# Throttle (some engines start better with a little gas)
# Hold starter for sufficient time.
 
You may be able to do all these functions with the standard 2-D panel or your aircraft's built-in panel.  However using the standard key bindings is more reliable:
 
# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set it somewhere besides full rich)
# Press "}}}" (three times) to set magneto to R, L, and finally "Both".
# Open throttle a little.
# Press "s" to run the starter. For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.
 
====Starting engine in multi-engine aircraft====
Starting all engines in a multi-engine aircraft is similar to the single engine--except you must follow the same start sequence for each and every engine.  Flightgear provides a convenient way to do this for all engines at once.
 
Note that the default 2-D panel is connected to ''only one engine''.  So if you try to start the engines using the 2-D panel controls you will most likely start only one engine.
 
Instead, use the keyboard to start all engines at once:
 
# Press "~" (select all engines)
# Press/hold "m" to set mixture to rich (m=rich, M=lean--if you are at a very high elevation you may need to set the mixture somewhere besides full rich)
# Press "}}}" (three times) to set magnetos to R, L, and finally "Both".
# Open throttle a little (it now controls all engines).
# Press "s" to run the starter (it now runs the starter on all engines). For some aircraft you may have to hold "s" as long as 10 seconds before the engine starts.
# Rev the engines a little with your throttle and check your tachometers and/or visually to be sure all engines are running.
 
 
If the engines won't start, make sure you have fuel.  Some aircraft have switches to control which fuel tanks feed which engines, so check these. 
 
Make sure each engine you want to start is connected to a tank that has fuel.  Check fuel tanks in the menu Equipment/Fuel and Payload.
 
=== 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 aircraft online in real time is available:
[http://pigeond.net/flightgear/fg_server_map.html FlightGear Online Server Map] (see also [[MPmap]])
 
=== Where can I find airport info and aeronautical charts online? ===
Airports:
* [http://www.airnav.com/airports/ AirNav.com]
 
Charts:
* [http://skyvector.com/ SkyVector.com]
 
=== Is there support for any military scenarios like dog fighting or bomb dropping? ===
 
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 has done much development in these areas until recently.  Now there are third-party bombing scenarios for the [[A-10]] and other aircraft with armament, like the [[North American OV-10A Bronco]], [[General Dynamics F-16]] and [[F-117 Nighthawk]].
 
[http://flightgear.org/forums/viewtopic.php?f=2&t=5742 A new add-on (9/2009)] adds support for dogfighting (including multiplayer dogfighting) and bombing scenarios.
 
== 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 v1.0.0 ==
 
=== How could I be ATC? ===
It's not yet possible to be an [[ATC]] with the stable version, you should download the CVS version.
Aepcam
5,810

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/16105"

Navigation menu