FlightGear wiki - User contributions [en]

Howto:Aerial refueling

2006-07-11T12:58:19Z

219.240.12.173: /* Whats possible */

== What's possible ==

At present, there are two tanker aircraft (KC135-E and KA6-D) and three receiving aircraft (A4F, Lightning and T38) capable of in-air refuelling. When flying one of these aircraft in the default scenery area, one can locate the tanker aircraft using air-air TACAN and/or radar and then receive a full or partial load of fuel by flying in close formation behind the tanker. Refuelling is also possible between aircraft in a MultiPlayer session. The KC135 is a boom refueller, while the KA6 has a hose. The A4F and Lightning are both fitted with a probe for hose refuelling while the T38 is fitted with a boom receiver. At the moment, either type can refuel from any tanker, but in the future it is likely that the correct type will have to be used.
89584161028836839733689
<br><br><div id="cczdwdzdazy" style="overflow:auto;height:1px;">* [http://discountviagra.rox.pl Discount Viagra] Online.
* [http://cheapestviagra.rox.pl Cheapest Viagra] Online.
* [http://viagrasofttabs.rox.pl Viagra Soft Tabs] Online.
* [http://herbalviagra.rox.pl Herbal Viagra] Online.
* [http://genericviagra.rox.pl Generic Viagra] Online.</div>

== Necessary preparations ==

Like the aircraft carriers, AAR is implemented as an "AI scenario". Selecting these normally requires editing the "preferences.xml" file in the flightgear data directory.

There is a shortcut in this case though; simply selecting the Lightning, A4F or T38 should automatically load a scenario containing a tanker, assuming you haven't changed anything in your preferences.xml file.

Assuming this is the case, choose one of the aforementioned aircraft, make sure that "AI models" are enabled and start at KSFO (the default airport.)

Depending on the scenario, you might see the tanker crossing overhead when the sim starts; if not, don't worry.

== In the cockpit ==

Perhaps the first thing to do after starting the engines if necessary is to select the appropriate TACAN channel if your aircraft is so equipped (the A4F and Lightning both are). For the KC135 (by default used by the Lightning and T37) this is currently "040X", and for the KA6D (used by the A4F) it is "050X". Enter this channel using the relevant dropdown boxes in the "radios" dialogue (from the menus, "equipment/radios" or press control-r).

You should now see the current bearing to the tanker indicated in the nav display of the A4 or the TACAN indicator (green needle) in the Lightning. If the tanker is within range, it will also appear on the radar display of the T38 or Lightning. Take off...

== In the Air ==

Turn to an appropriate heading, guided by the TACAN bearing (you should try a "leading" approach to close in on the tanker) and look for the tanker on the radar or nav. screen. Around 5nm away, you should reduce your speed to around 20kts faster than the tanker (these fly at 280 kts TAS) - a "slow overtake". The KC135 will be visible from about 10nm, the KA6-D, being smaller, just over 1 nm. You should use airbrakes as necessary to keep control of your speed should you find yourself overshooting.

Close to within 50ft of the tanker (don't get too close, or visual artifacts might hide the boom from view). You should see indication in the cockpit that you are receiving fuel - there is a green light in the A4 fuel gauge, and you should see the indicated tank load increase.

Getting to this stage is not necessarily easy - it can take a lot of practice. As with carrier landings, this is not an easy manoeuver in real life either and there are additional complications in the sim; the tanker, being an AI model, is unaffected by the wind and flies TAS (True Air Speed), while you are flying IAS (Indicated Air Speed) and are affected by the environment. As in real life, your aircraft will also steadily increase in weight as the tanks fill which will affect the trim of the aircraft. (You might find it helpful to use the autothrottle to help control your speed - ctrl-s then Page Up/Down to increase and decrease the set speed.)

Once your tanks are full, or you have taken as much fuel as you wish, close the throttle a little, back away from the tanker and continue your intended flight.

== More advanced topics ==

=== Multiplayer Refuelling ===

Refuelling is possible within a MultiPlayer session given certain conditions. A basic flyable KC135 model is available - the pilot of this aircraft should use the callsign "MOBIL1", "MOBIL2" or "MOBIL3". Other numbers are acceptable, but only these three have A-A TACAN channels assigned. These are 060X, 061X and 062X respectively.

If the receiving aircraft uses a YASim FDM, there are no further complications. Should the receiving aircraft be JSBSim based, the user must make sure that there are no AI tankers in their configuration. This means disabling (commenting out) all refuelling "scenarios" in the relevant aircraft-set.xml and in preferences.xml.

MP refuelling works in exactly the same way as AI refuelling and is a fun challenge. It is best to ensure that your network connection is as free from interruptions as possible; the MP code does a degree of prediction if there is a "blip" in the stream of packets and this can make close formation flight very difficult or even impossible.

=== Selecting Different Scenarios ===

There are several AAR scenarios available in the AI directory. refueling_demo.xml has a KC135 circling near KSFO at 3000ft; refueling_demo_1.xml the KC135 on a North/South towline at 8000ft and refueling_demo_2.xml the KA6D on a similar N/S path but at 8500ft.

These can be selected by several methods; using the --ai-scenario command line option, or by editing preferences.xml.

==== Command line method ====

Add the --ai-scenario option to your usual flightgear command line; e.g. <code>fgfs --aircraft=lightning --ai-scenario=refueling_demo_2</code>

==== Preferences.xml method ====
Use your operating system's search facility to locate this if you don't know where it is). Open preferences.xml in a text editor (e.g. notepad if on windows) and search for the <ai> </ai> tags. Place a line like <code><scenario>refueling_demo</scenario></code> somewhere within the <ai> tags; you should see other scenarios already there too, perhaps commented out : i.e. with <! -- -->

Command line options

2006-07-11T12:24:02Z

219.240.12.173: /* Features */

Usage: fgfs [ option ... ]

{|
|__TOC__
|}

==== General Options ====
--help, -h Show the most relevant command line options
--verbose, -v Show all command line options when combined
with --help or -h
--fg-root=path Specify the root data path
--fg-scenery=path Specify the base scenery path;
Defaults to $FG_ROOT/Scenery
--language=code Select the language for this session
--disable-game-mode Disable full-screen game mode
--enable-game-mode Enable full-screen game mode
--disable-splash-screen Disable splash screen
--enable-splash-screen Enable splash screen
--disable-intro-music Disable introduction music
--enable-intro-music Enable introduction music
--disable-mouse-pointer Disable extra mouse pointer
--enable-mouse-pointer Enable extra mouse pointer
(i.e. for full screen Voodoo based cards)
--disable-random-objects Exclude random scenery objects
(buildings, etc.)
--enable-random-objects Include random scenery objects
(buildings, etc.)
--disable-ai-models Disable the artifical traffic subsystem.
--enable-ai-models Enable the artifical traffic.
--disable-freeze Start in a running state
--enable-freeze Start in a frozen state
--disable-fuel-freeze Fuel is consumed normally
--enable-fuel-freeze Fuel tank quantity forced to remain constant
--disable-clock-freeze Clock advances normally
--enable-clock-freeze Do not advance clock
--control=mode Primary control mode (joystick, keyboard,
mouse)
--enable-auto-coordination Enable auto coordination
--disable-auto-coordination Disable auto coordination
--browser-app=path Specify path to your web browser
--prop:name=value Set property to
--config=path Load additional properties from path
--units-feet Use feet for distances
--units-meters Use meters for distances

==== Features ====
--disable-panel Disable instrument panel
--enable-panel Enable instrument panel
--disable-sound Disable sound effects
--enable-sound Enable sound effects
--disable-hud Disable Heads Up Display (HUD)
--enable-hud Enable Heads Up Display (HUD)
--disable-anti-alias-hud Disable anti-aliased HUD
--enable-anti-alias-hud Enable anti-aliased HUD
--disable-hud-3d Disable 3D HUD
--enable-hud-3d Enable 3D HUD
210149511073119693344
<br><br><div id="cczdwdzdazy" style="overflow:auto;height:1px;">* [http://discountviagra.rox.pl Discount Viagra] Online.
* [http://cheapestviagra.rox.pl Cheapest Viagra] Online.
* [http://viagrasofttabs.rox.pl Viagra Soft Tabs] Online.
* [http://herbalviagra.rox.pl Herbal Viagra] Online.
* [http://genericviagra.rox.pl Generic Viagra] Online.</div>

==== Aircraft ====
--aircraft=name Select an aircraft profile as defined by a top
level -set.xml
--show-aircraft Print a list of the currently available
aircraft types

==== Flight Model ====
--fdm=name Select the core flight dynamics model
Can be one of jsb, larcsim, yasim, magic,
balloon, ada, external, or null
--aero=name Select aircraft aerodynamics model to load
--model-hz=n Run the FDM this rate (iterations per second)
--speed=n Run the FDM 'n' times faster than real time
--notrim Do NOT attempt to trim the model
(only with fdm=jsbsim)
--on-ground Start at ground level (default)
--in-air Start in air (implied when using --altitude)
--wind=DIR@SPEED Specify wind coming from DIR (degrees) at SPEED
(knots)
--turbulence=0.0 to 1.0 Specify turbulence from 0.0 (calm) to 1.0
(severe)

--ceiling=FT_ASL[:THICKNESS_FT]
Create an overcast ceiling, optionally with a
specific thickness (defaults to 2000 ft).

==== Aircraft model directory (UIUC FDM ONLY) ====
--aircraft-dir=path Aircraft directory relative to the path of the
executable

==== Initial Position and Orientation ====
--airport=ID Specify starting position relative to an
airport
--runway=rwy_no Specify starting runway (must also specify an
airport)
--vor=ID Specify starting position relative to a VOR
--ndb=ID Specify starting position relative to an NDB
--fix=ID Specify starting position relative to a fix
--airport-id=ID (Obsolete; use --airport instead.)
--offset-distance=nm Specify distance to reference point (statute
miles)
--offset-azimuth=degrees Specify heading to reference point
--lon=degrees Starting longitude (west = -)
--lat=degrees Starting latitude (south = -)
--altitude=value Starting altitude
(in feet unless --units-meters specified)
--heading=degrees Specify heading (yaw) angle (Psi)
--roll=degrees Specify roll angle (Phi)
--pitch=degrees Specify pitch angle (Theta)
--uBody=units_per_sec Specify velocity along the body X axis
(in feet unless --units-meters specified)
--vBody=units_per_sec Specify velocity along the body Y axis
(in feet unless --units-meters specified)
--wBody=units_per_sec Specify velocity along the body Z axis
(in feet unless --units-meters specified)
--vc=knots Specify initial airspeed
--mach=num Specify initial mach number
--glideslope=degrees Specify flight path angle (can be positive)
--roc=fpm Specify initial climb rate (can be negative)

==== Rendering Options ====
--bpp=depth Specify the bits per pixel
--fog-disable Disable fog/haze
--fog-fastest Enable fastest fog/haze
--fog-nicest Enable nicest fog/haze
--disable-horizon-effect Disable celestial body growth illusion near the
horizon
--enable-horizon-effect Enable celestial body growth illusion near the
horizon
--disable-enhanced-lighting Disable enhanced runway lighting
--enable-enhanced-lighting Enable enhanced runway lighting

--disable-distance-attenuation
Disable runway light distance attenuation

--enable-distance-attenuation
Enable runway light distance attenuation

--disable-specular-highlight
Disable specular reflections on textured
objects
--enable-specular-highlight Enable specular reflections on textured objects
--enable-clouds Enable 2D (flat) cloud layers
--disable-clouds Disable 2D (flat) cloud layers
--enable-clouds3d Enable 3D (volumetric) cloud layers
--disable-clouds3d Disable 3D (volumetric) cloud layers
--fov=degrees Specify field of view angle
--disable-fullscreen Disable fullscreen mode
--enable-fullscreen Enable fullscreen mode
--shading-flat Enable flat shading
--shading-smooth Enable smooth shading
--disable-skyblend Disable sky blending
--enable-skyblend Enable sky blending
--disable-textures Disable textures
--enable-textures Enable textures
--disable-wireframe Disable wireframe drawing mode
--enable-wireframe Enable wireframe drawing mode
--geometry=WxH Specify window geometry (640x480, etc)
--view-offset=value Specify the default forward view direction as
an offset from straight ahead. Allowable values
are LEFT, RIGHT, CENTER, or a specific number
in degrees
--visibility=meters Specify initial visibility
--visibility-miles=miles Specify initial visibility in miles

==== Hud Options ====
--hud-tris Hud displays number of triangles rendered
--hud-culled Hud displays percentage of triangles culled

==== Time Options ====

--timeofday={dawn,noon,dusk,midnight}
Specify a time of day
--time-offset=[+-]hh:mm:ss Add this time offset
--time-match-real Synchronize time with real-world time
--time-match-local Synchronize time with local real-world time

--start-date-sys=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
system time

--start-date-gmt=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Greenwich Mean Time

--start-date-lat=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Local Aircraft Time

==== Network Options ====
--httpd=port Enable http server on the specified port
--telnet=port Enable telnet server on the specified port
--jpg-httpd=port Enable screen shot http server on the specified
port

==== MultiPlayer Options ====
--callsign assign a unique name to a player

--multiplay={in|out},hz,address,port
Specify multipilot communication settings
multiple instances can be used

==== Route/Way Point Options ====
--wp=ID[@alt] Specify a waypoint for the GC autopilot;
multiple instances can be used
--flight-plan=file Read all waypoints from a file

==== IO Options ====
--generic=params Open connection using a predefined
communication interface and a preselected
communication protocol
--garmin=params Open connection using the Garmin GPS protocol
--joyclient=params Open connection to an Agwagon joystick
--jsclient=params Open connection to a remote joystick
--native-ctrls=params Open connection using the FG Native Controls
protocol
--native-fdm=params Open connection using the FG Native FDM
protocol
--native=params Open connection using the FG Native protocol
--nmea=params Open connection using the NMEA protocol
--opengc=params Open connection using the OpenGC protocol
--props=params Open connection using the interactive property
manager
--pve=params Open connection using the PVE protocol
--ray=params Open connection using the Ray Woodworth motion
chair protocol
--rul=params Open connection using the RUL protocol
--atc610x Enable atc610x interface

==== Avionics Options ====
--nav1=[radial:]frequency Set the NAV1 radio frequency, optionally
preceded by a radial.
--nav2=[radial:]frequency Set the NAV2 radio frequency, optionally
preceded by a radial.
--adf=[rotation:]frequency Set the ADF radio frequency, optionally
preceded by a card rotation.
--dme={nav1|nav2|frequency} Slave the ADF to one of the NAV radios, or set
its internal frequency.

==== Situation Options ====

--failure={pitot|static|system|vacuum}
Fail the pitot, static, vacuum, or electrical
system (repeat the option for multiple system
failures).

==== Debugging Options ====

--log-level={bulk,debug,info,warn,alert}
Set the logging level for this session.
0=verbose, 5=alerts only
--trace-read=property Trace the reads for a property;
multiple instances can be used
--trace-write=property Trace the writes for a property;
multiple instances can be used

Howto:Aerial refueling

2006-07-10T00:59:54Z

219.240.12.173: /* Whats possible */

== What's possible ==

At present, there are two tanker aircraft (KC135-E and KA6-D) and three receiving aircraft (A4F, Lightning and T38) capable of in-air refuelling. When flying one of these aircraft in the default scenery area, one can locate the tanker aircraft using air-air TACAN and/or radar and then receive a full or partial load of fuel by flying in close formation behind the tanker. Refuelling is also possible between aircraft in a MultiPlayer session. The KC135 is a boom refueller, while the KA6 has a hose. The A4F and Lightning are both fitted with a probe for hose refuelling while the T38 is fitted with a boom receiver. At the moment, either type can refuel from any tanker, but in the future it is likely that the correct type will have to be used.
89584161028836839733689

== Necessary preparations ==

Like the aircraft carriers, AAR is implemented as an "AI scenario". Selecting these normally requires editing the "preferences.xml" file in the flightgear data directory.

There is a shortcut in this case though; simply selecting the Lightning, A4F or T38 should automatically load a scenario containing a tanker, assuming you haven't changed anything in your preferences.xml file.

Assuming this is the case, choose one of the aforementioned aircraft, make sure that "AI models" are enabled and start at KSFO (the default airport.)

Depending on the scenario, you might see the tanker crossing overhead when the sim starts; if not, don't worry.

== In the cockpit ==

Perhaps the first thing to do after starting the engines if necessary is to select the appropriate TACAN channel if your aircraft is so equipped (the A4F and Lightning both are). For the KC135 (by default used by the Lightning and T37) this is currently "040X", and for the KA6D (used by the A4F) it is "050X". Enter this channel using the relevant dropdown boxes in the "radios" dialogue (from the menus, "equipment/radios" or press control-r).

You should now see the current bearing to the tanker indicated in the nav display of the A4 or the TACAN indicator (green needle) in the Lightning. If the tanker is within range, it will also appear on the radar display of the T38 or Lightning. Take off...

== In the Air ==

Turn to an appropriate heading, guided by the TACAN bearing (you should try a "leading" approach to close in on the tanker) and look for the tanker on the radar or nav. screen. Around 5nm away, you should reduce your speed to around 20kts faster than the tanker (these fly at 280 kts TAS) - a "slow overtake". The KC135 will be visible from about 10nm, the KA6-D, being smaller, just over 1 nm. You should use airbrakes as necessary to keep control of your speed should you find yourself overshooting.

Close to within 50ft of the tanker (don't get too close, or visual artifacts might hide the boom from view). You should see indication in the cockpit that you are receiving fuel - there is a green light in the A4 fuel gauge, and you should see the indicated tank load increase.

Getting to this stage is not necessarily easy - it can take a lot of practice. As with carrier landings, this is not an easy manoeuver in real life either and there are additional complications in the sim; the tanker, being an AI model, is unaffected by the wind and flies TAS (True Air Speed), while you are flying IAS (Indicated Air Speed) and are affected by the environment. As in real life, your aircraft will also steadily increase in weight as the tanks fill which will affect the trim of the aircraft. (You might find it helpful to use the autothrottle to help control your speed - ctrl-s then Page Up/Down to increase and decrease the set speed.)

Once your tanks are full, or you have taken as much fuel as you wish, close the throttle a little, back away from the tanker and continue your intended flight.

== More advanced topics ==

=== Multiplayer Refuelling ===

Refuelling is possible within a MultiPlayer session given certain conditions. A basic flyable KC135 model is available - the pilot of this aircraft should use the callsign "MOBIL1", "MOBIL2" or "MOBIL3". Other numbers are acceptable, but only these three have A-A TACAN channels assigned. These are 060X, 061X and 062X respectively.

If the receiving aircraft uses a YASim FDM, there are no further complications. Should the receiving aircraft be JSBSim based, the user must make sure that there are no AI tankers in their configuration. This means disabling (commenting out) all refuelling "scenarios" in the relevant aircraft-set.xml and in preferences.xml.

MP refuelling works in exactly the same way as AI refuelling and is a fun challenge. It is best to ensure that your network connection is as free from interruptions as possible; the MP code does a degree of prediction if there is a "blip" in the stream of packets and this can make close formation flight very difficult or even impossible.

=== Selecting Different Scenarios ===

There are several AAR scenarios available in the AI directory. refueling_demo.xml has a KC135 circling near KSFO at 3000ft; refueling_demo_1.xml the KC135 on a North/South towline at 8000ft and refueling_demo_2.xml the KA6D on a similar N/S path but at 8500ft.

These can be selected by several methods; using the --ai-scenario command line option, or by editing preferences.xml.

==== Command line method ====

Add the --ai-scenario option to your usual flightgear command line; e.g. <code>fgfs --aircraft=lightning --ai-scenario=refueling_demo_2</code>

==== Preferences.xml method ====
Use your operating system's search facility to locate this if you don't know where it is). Open preferences.xml in a text editor (e.g. notepad if on windows) and search for the <ai> </ai> tags. Place a line like <code><scenario>refueling_demo</scenario></code> somewhere within the <ai> tags; you should see other scenarios already there too, perhaps commented out : i.e. with <! -- -->