5,810
edits
Es/FlightGear Newsletter September 2011: Difference between revisions
Jump to navigation
Jump to search
Es/FlightGear Newsletter September 2011 (view source)
Revision as of 09:47, 14 May 2012
, 14 May 2012→Starting at the most appropriate parking position
| Line 42: | Line 42: | ||
=== Starting at the most appropriate parking position === | === Starting at the most appropriate parking position === | ||
At selected airports, it is now possible to let FlightGear decide at which parking it should start. You can do this by passing the commmand line option <tt>--parkpos=AVAILABLE</tt> to FlightGear. This way, you don't need to worry about the details of whether the parking is of the right type, whether it is large enough, etc etc. | At selected airports, it is now possible to let FlightGear decide at which parking it should start. You can do this by passing the commmand line option <tt>--parkpos=AVAILABLE</tt> to FlightGear. This way, you don't need to worry about the details of whether the parking is of the right type, whether it is large enough, etc etc. | ||
A partir de la posición de estacionamiento más adecuado === | |||
En los aeropuertos seleccionados, ahora es posible dejar que FlightGear decidir en qué aparcamiento debería comenzar. Usted puede hacer esto al pasar la línea de commmand <tt> opción - parkpos = DISPONIBLE </ tt> para FlightGear. De esta manera, usted no necesita preocuparse por los detalles de si el estacionamiento es del tipo correcto, si es lo suficientemente grande, etc etc | |||
However, in order to get it to work, you need to set some properties: | However, in order to get it to work, you need to set some properties: | ||
Sin embargo, con el fin de conseguir que funcione, es necesario establecer algunas propiedades: | |||
* <tt>/sim/dimensions/radius-m</tt> should be a nummeric estimate of the size of your aircraft. A small aircraft fits into a large parking, but a large aircraft does not fit into a small parking space. Because the AI part of radius is also used for slightly different purposes (prioritizing gate assignments), the given value may deviate slightly from the real aircraft's size. See [[Aircraft radii|our wiki for an overview of standard aircraft radii]] currently in use. | * <tt>/sim/dimensions/radius-m</tt> should be a nummeric estimate of the size of your aircraft. A small aircraft fits into a large parking, but a large aircraft does not fit into a small parking space. Because the AI part of radius is also used for slightly different purposes (prioritizing gate assignments), the given value may deviate slightly from the real aircraft's size. See [[Aircraft radii|our wiki for an overview of standard aircraft radii]] currently in use. | ||
* <tt>/sim/aircraft-class</tt> can be any one of "ga", "cargo", "gate", "mil-fighter", "mil-cargo", or "vtol". See [[Interactive traffic#A technical perspective|our wiki documentation]] for more information. | * <tt>/sim/aircraft-class</tt> can be any one of "ga", "cargo", "gate", "mil-fighter", "mil-cargo", or "vtol". See [[Interactive traffic#A technical perspective|our wiki documentation]] for more information. | ||
* In addition, the property <tt>/sim/aircraft-operator</tt> can be set to a three letter icao airline code. The first two properties are mandatory for the system to work, the last one is optional, but will generally result in a better parking location. | * In addition, the property <tt>/sim/aircraft-operator</tt> can be set to a three letter icao airline code. The first two properties are mandatory for the system to work, the last one is optional, but will generally result in a better parking location. | ||
* <tt> / Sim / dimensiones / radio-m </ tt> debe ser una estimación nummeric del tamaño de su avión. Un avión pequeño se adapta a un amplio aparcamiento, pero un avión grande no cabe en un espacio pequeño aparcamiento. Debido a que la parte IA de radio también se usa para propósitos levemente diferentes asignaciones de prioridad de puerta), el valor dado pueden diferir ligeramente de tamaño de la aeronave real. Ver [[radios de aeronave | nuestro wiki para una visión general de los radios de los aviones estándar]] actualmente en uso. | |||
* <tt> / Sim / aeronaves de clase </ tt> puede ser cualquiera de los "ga", "carga", "puerta", "millones de combate", "millones de carga", o "VTOL". Ver [[el tráfico interactivo # Un punto de vista técnico | nuestra documentación wiki]] para más información. | |||
* Además, la propiedad <tt> / SIM / operador de la aeronave </ tt> se puede ajustar a un código de línea aérea de la OACI de tres letras. Las primeras dos propiedades son obligatorios para que el sistema funcione, el último es opcional, pero en general se traducirá en un lugar de estacionamiento mejor. | |||
Fortunately, it is also possible to set these properties in the aircraft's configuration file. Currently, two aircraft have been updated to automatically take advantage of this new system. These are the Boeing 777-200ER, and the Embrear 170. The properties aircraft-class and aircraft-operator can also be changed by FlightGear's livery select mechanism, so that depending on whom you're flying for, you'll spawn at a different part of the airport! | Fortunately, it is also possible to set these properties in the aircraft's configuration file. Currently, two aircraft have been updated to automatically take advantage of this new system. These are the Boeing 777-200ER, and the Embrear 170. The properties aircraft-class and aircraft-operator can also be changed by FlightGear's livery select mechanism, so that depending on whom you're flying for, you'll spawn at a different part of the airport! | ||