FlightGear wiki - User contributions [en]

FSweekend 2012

2012-10-28T15:03:25Z

Xiii: /* Booth information */ OS detail

[[File:FSweekend banner 2012.jpg|right]]
This wiki page lists all information related to [[FlightGear]]'s [[FSweekend]] 2012 attendance, as well as information for those that would like to pay a virtual visit. FlightGear will be represented by a team of regular FlightGear developers.

<font size="5">'''<daysuntil in="days">03-November-2012</daysuntil>''' until the FSweekend</font> at 3&4 November 2012.

== Booth information ==

=== Equipment Checklist ===
[[File:C172MiniCockpit1.jpg|144px|right]]
[[File:Anaglyph-glasses.jpg|right]]
* CH Yoke (GdR)
* CH Rudder Pedals (GdR)
* One Linux/MS W7 based PC (AB)
** Core i7 + GTX 680 + 24"
** Saitek X52 throttle and stick
* C172P Panel (FGPanel Demo) with driving PC (TB)
* One Linux-based PC (DT)
** Three monitors
** Saitek Joystick
** Saitek Rudder Pedals
** Headset
** Sound system
* Projector screen and projector (DT)
* Pairs of anaglyph 3D-glasses:
** One (GdR)
** One (DT)
* Business cards

'''Maybe:'''
* Thomas Krenn machine with 10 monitors (MS)

== Flight information ==
=== Airports ===
[[File:EHLE_schipholgebouw.png|thumb|270px|The old terminal of Schiphol (1928), now located at EHLE.]]
Activities will mainly take place at and around [[Amsterdam Airport Schiphol]] (EHAM), [[Lelystad Airport]] (EHLE), [[Volkel Air Base]] (EHVK) and the [[VU University Medical Center|VU University Medical Center Helipad]] (EH0001).

=== Charts ===
All charts that you may have to use on your flights are available at http://ais-netherlands.nl (AIS Publications > Integrated Package). Please note that these are the most up to date charts available, so certain situations might not have been changed in FlightGear (EHAM, EHLE and EHVK taxiways should be correct though).

Parking positions have been created for most of the Dutch airports including EHAM, EHRD, EHVK and EHLE (A1-A6, B1 and B2).

All named airports are for civil usage, except for [[Volkel Air Base]] (EHVK). This base will be occupied by the (AI) F-16 squadrons and likely one setup in Lelystad. Feel free to join with your F-16 or other Dutch/NATO [[:Category:Military aircraft|military aircraft]].

=== Weather information ===
Reallife weather information can be found at the KNMI (Dutch Meteorological institute) website.
* [http://knmi.nl/actueel/metar.html METAR] current weather at airports
* [http://knmi.nl/waarschuwingen_en_verwachtingen/luchtvaart/nederlandse_vliegveldverwachtingen.html TAF] expected weather at airports
If the weather is really bad, it is likely that the FSweekend guys will use a preset weather scenario.

=== Scenery ===
For FSweekend 2012 we're planning to show consistent Scenery which has been available for testing before the show and doesn't require manual fiddling on-stage. That way we can safely show the latest scenery on every machine. Please make sure everything is in the database well before November ;-)

== External links==
* [http://www.fsweekend.com Official FSweekend website]
* [http://www.facebook.com/events/315742308452348/ Facebook event page]
* [https://plus.google.com/u/0/events/ctr3pnig5mnp9q94p23gvcc8vus Google+ event page]

[[Category:FSweekend]]

FSweekend 2012

2012-10-23T09:11:48Z

Xiii: added xiii's PC in Equipment Checklist

[[File:FSweekend banner 2012.jpg|right]]
This wiki page lists all information related to [[FlightGear]]'s [[FSweekend]] 2012 attendance, as well as information for those that'd like to pay a virtual visit. FlightGear will be represented by a team of regular FlightGear developers and users.

<font size="5">'''<daysuntil in="days">03-November-2012</daysuntil>''' until the FSweekend</font> at 3&4 November 2012.

== Booth information ==

=== Equipment Checklist ===
* CH Yoke (GdR)
* CH Rudder Pedals (GdR)
* Core i7 + GTX 680 + X52 throttle and stick + 24" (AB)
* Pairs of anaglyph 3D-glasses:
** One (GdR)
** One (DT)
* Business cards

'''Maybe:'''
* Thomas Krenn machine with 10 monitors (MS)

====15 years anniversary====
This year it's 15 (!) years ago that the first version of FlightGear was released (July 17, 1997). To celebrate this event, we might bring some special goodies to the booth:

* Balloons with logo to cheer up our booth.
* One (old) computer running a very old version (preferably the very first version) of FlightGear.

== Flight information ==
=== Airports ===
[[File:EHLE_schipholgebouw.png|thumb|270px|The old terminal of Schiphol (1928), now located at EHLE.]]
Activities will mainly take place at and around [[Amsterdam Airport Schiphol]] (EHAM), [[Lelystad Airport]] (EHLE), [[Volkel Air Base]] (EHVK) and the [[VU University Medical Center|VU University Medical Center Helipad]] (EH0001).

=== Charts ===
All charts that you may have to use on your flights are available at http://ais-netherlands.nl (AIS Publications > Integrated Package). Please note that these are the most up to date charts available, so certain situations might not have been changed in FlightGear (EHAM, EHLE and EHVK taxiways should be correct though).

Parking positions have been created for most of the Dutch airports including EHAM, EHRD, EHVK and EHLE (A1-A6, B1 and B2).

All named airports are for civil usage, except for [[Volkel Air Base]] (EHVK). This base will be occupied by the (AI) F-16 squadrons and likely one setup in Lelystad. Feel free to join with your F-16 or other Dutch/NATO [[:Category:Military aircraft|military aircraft]]. For EHVK specific departure and recovery procedures please visit http://cenor.org/pages/proc_eh.html and dowload the corresponding .pdf file.

=== Weather information ===
Reallife weather information can be found at the KNMI (Dutch Meteorological institute) website.
* [http://knmi.nl/actueel/metar.html METAR] current weather at airports
* [http://knmi.nl/waarschuwingen_en_verwachtingen/luchtvaart/nederlandse_vliegveldverwachtingen.html TAF] expected weather at airports
If the weather is really bad, it is likely that the FSweekend guys will use a preset weather scenario.

=== Scenery ===
For FSweekend 2012 we're planning to show consistent Scenery which has been available for testing before the show and doesn't require manual fiddling on-stage. That way we can safely show the latest scenery on every machine. Please make sure everything is in the database well before November ;-)

== External links==
* [http://www.fsweekend.com Official FSweekend website]
* [http://www.facebook.com/events/315742308452348/ Facebook event page]

[[Category:FSweekend]]

Improving real close formation flight

2012-07-23T21:13:01Z

Xiii: i.e. shall be written in italic

==The movies==

First of all, I'd like to show you what's possible to achieve in Flightgear:

[http://www.youtube.com/watch?v=LyBUPlf5NSw diamond formation flight]

[http://www.youtube.com/watch?v=2eGOdBsd8Os F-4 training in TFFG]

Next is, how was it made:

* take a plane with a JSBsim fdm (Yasim is buggy when it comes to display plane in the future cf [http://code.google.com/p/flightgear-bugs/issues/detail?id=202 this bug report] ;
* setup a local fgms on another PC ;
* fly the first plane, sending to the local fgms, and record the outgoing UDP packet from the PC running Flightgear (Wireshark software with some adapted rules) ;
* cheat the Flightgear source code (src/AIModel/AIMultiplayer.cxx and .hxx) to make the other planes displayed in the future, using the already present prediction system (and try to smooth the rubber band phenomenon) ;
* find the best value that matches your configuration ;
* now start Flightgear with the second plane, start recording again the UDP packets, and play again the previously recorded packets. Now it's time to show your flying skills!
* do this again with the number 3 and 4, and during the 4th run record the video to have a first camera view ;
* take the [[UFO]] (the video assistant was broken for me) and do another camera view ;
* make the movie, and voilà...

== Record replay mechanism ==

As described above, external softs were used to record and replay the planes: Wireshark, tcprewrite and tcpreplay.
Maybe there's a way to do this from Flightgear, but it was the easiest for me.

How: The outgoing UDP packets from the FG machine are recorded (FG run with an input port different from the output port), while sending to a local fgms on another PC.
After some tcprewrite magic, the recorded file is ready to be sent again to fgms from the FG machine, and this time the record will include the replayed packet as well as the new FG session (which use a different input port).

After the last run, the file include the 4 planes together, ready to be sent again any time to the local fgms. Now we can play it several time to have different camera views...

== Multiplayer patch ==

The patch used was [http://janodesbois.free.fr/flightgear/lag-adjust/mp-lag_22jui2012.diff this one]. It creates two properties in each mp plane:

* controls/compensate-lag (bool) used to make the system work, or keep the old behaviour
* controls/player-lag: the time to change the displayed time (referenced from the received packet time) a positive value display in the future (here I used 0.12) and a negative make the display be late, allowing to be more smooth in case of jitter (for the UFO pass, it was -0.2).
I plan to have the user set the server lag for this property (or better a nasal part) , for that I need some tests with others pilots.

For Windows users, I can provide a modified binary, along with the needed DLL, if you want to have a go and test it (32 or win64 ), just get in touch...
Mac or Linux users have to compile the patched version :)

===How FG currently deal with MP packets===

I am far from being a C++ developer, but I can understand how it works, and I can try some easy code cheat. I will try to explain what I know, but keep in mind english in not my native language :) .
For now, the received MP packets are first ordered by sending time , and then FG tries to keep the MP displaying in a manner that we are always before the last packet, to have only a linear interpolation between two packets to do.
(That means for a 10 packets/s speed, we display the plane at least where it was 1/10s before the last packet..
The packets of no more use are then dropped from the stack.

===Lag===

In the case of multiplayer flight, we see the other plane retarded by:
* the transmission lag (travel time between the sender and the receiver )
* the lag added by the MP displaying code (more than 0.1s)

If we want a good formation flight, we need to display the other planes in the future, in my setup, I needed to display other planes 0.12 s in the future.
If you want to have a look at this lag effect, simply use 127.0.0.1 as server, [http://janodesbois.free.fr/fg_screens/lag_test/f4n_normal_lag.png then you will see your plane], together with your AI counterpart, far behind once you've got some speed.
With the patch and after some fine tuning, you can have [http://janodesbois.free.fr/fg_screens/lag_test/f4n-compensated_lag.png a better matching].

[http://janodesbois.free.fr/fg_screens/lag_test/refuel.jpg Example with two MP planes in refuelling action]

===Jitter===

The records were made on a local network, so the lag was here, but the jitter was minimal. What happens when we add jitter to the UDP packet, ''i.e.'' when the time taken to travel from a player to another varies?
The multiplayer code has got a basic prediction system, but it is nearly never used, if the packets are retarded, FG makes the plane "waiting in the sky" and if they suddenly regain a fast lag travel, we will see the plane accelerating. This is what is called "rubber band phenomenon" among formation flightgear pilots, the thing that makes a refuelling impossible, or break a tow in a glider session...
It is possible to address this jitter, by using the sending packets time, and guessing what is due to jitter, and what is due to clock drift between the sender/receiver, but for now I lack the skills. My patch just try to make the time adjustment system more smooth, thus using more the prediction system.

A thing to consider here is to choose the same server, and one which give minimal jitter.

===Existing prediction system===

Just a few words about the system used to display the planes in the future.
It consists of Euler steps, starting from the last packet position and using the MP plane velocity and rotation data
* It works only without wind for Yasim aircrafts, as the speed transmitted in the UDP packet is the speed in the air mass and not in the reference frame as the JSBsim planes do.
* It was not intended to be used intensively, we always compute from the last packet position, and that charges the CPU if we try to predict to far in the future.
* This look OK on straight line, but the more you rotate, the more jumpy the displayed plane become, see for example the top of the cuban half figure in [http://www.youtube.com/watch?v=2eGOdBsd8Os the second video] (0'36), where this effect is clearly visible in number4 internal view. Note that all the external views were made with the UFO, with a display of the plane in the past, so no prediction system is at use.

== Next step ==

The next step is to try this with real mutiplayers, to see what's good, and what's wrong :)

==TODO list==

* Write a nasal part, to choose which planes to display in the future: on a distance base, from a "friend/wingman list, go more in the past when no direct interaction is needed (with camera/ufo, if we are just observer)
* Try something to guess what is jitter and what is clock drift ...
* Improve the prediction system, by using a dt approach instead of starting from last packet time at each computation
* Find what value is needed depending on the server ping, and the frequency of packet sending to have planes concordant positions from each player point of view.

[[Category:Multiplayer]]

Improving real close formation flight

2012-07-23T20:15:15Z

Xiii: Typos, caps, and space between sections.

==The movies==

First of all, I'd like to show you what's possible to achieve in Flightgear:

[http://www.youtube.com/watch?v=LyBUPlf5NSw diamond formation flight]

[http://www.youtube.com/watch?v=2eGOdBsd8Os F-4 training in TFFG]

Next is, how was it made:

* take a plane with a JSBsim fdm (Yasim is buggy when it comes to display plane in the future cf [http://code.google.com/p/flightgear-bugs/issues/detail?id=202 this bug report] ;
* setup a local fgms on another PC ;
* fly the first plane, sending to the local fgms, and record the outgoing UDP packet from the PC running Flightgear (Wireshark software with some adapted rules) ;
* cheat the Flightgear source code (src/AIModel/AIMultiplayer.cxx and .hxx) to make the other planes displayed in the future, using the already present prediction system (and try to smooth the rubber band phenomenon) ;
* find the best value that matches your configuration ;
* now start Flightgear with the second plane, start recording again the UDP packets, and play again the previously recorded packets. Now it's time to show your flying skills!
* do this again with the number 3 and 4, and during the 4th run record the video to have a first camera view ;
* take the [[UFO]] (the video assistant was broken for me) and do another camera view ;
* make the movie, and voilà...

== Record replay mechanism ==

As described above, external softs were used to record and replay the planes: Wireshark, tcprewrite and tcpreplay.
Maybe there's a way to do this from Flightgear, but it was the easiest for me.

How: The outgoing UDP packets from the FG machine are recorded (FG run with an input port different from the output port), while sending to a local fgms on another PC.
After some tcprewrite magic, the recorded file is ready to be sent again to fgms from the FG machine, and this time the record will include the replayed packet as well as the new FG session (which use a different input port).

After the last run, the file include the 4 planes together, ready to be sent again any time to the local fgms. Now we can play it several time to have different camera views...

== Multiplayer patch ==

The patch used was [http://janodesbois.free.fr/flightgear/lag-adjust/mp-lag_22jui2012.diff this one]. It creates two properties in each mp plane:

* controls/compensate-lag (bool) used to make the system work, or keep the old behaviour
* controls/player-lag: the time to change the displayed time (referenced from the received packet time) a positive value display in the future (here I used 0.12) and a negative make the display be late, allowing to be more smooth in case of jitter (for the UFO pass, it was -0.2).
I plan to have the user set the server lag for this property (or better a nasal part) , for that I need some tests with others pilots.

For Windows users, I can provide a modified binary, along with the needed DLL, if you want to have a go and test it (32 or win64 ), just get in touch...
Mac or Linux users have to compile the patched version :)

===How FG currently deal with MP packets===

I am far from being a C++ developer, but I can understand how it works, and I can try some easy code cheat. I will try to explain what I know, but keep in mind english in not my native language :) .
For now, the received MP packets are first ordered by sending time , and then FG tries to keep the MP displaying in a manner that we are always before the last packet, to have only a linear interpolation between two packets to do.
(That means for a 10 packets/s speed, we display the plane at least where it was 1/10s before the last packet..
The packets of no more use are then dropped from the stack.

===Lag===

In the case of multiplayer flight, we see the other plane retarded by:
* the transmission lag (travel time between the sender and the receiver )
* the lag added by the MP displaying code (more than 0.1s)

If we want a good formation flight, we need to display the other planes in the future, in my setup, I needed to display other planes 0.12 s in the future.
If you want to have a look at this lag effect, simply use 127.0.0.1 as server, [http://janodesbois.free.fr/fg_screens/lag_test/f4n_normal_lag.png then you will see your plane], together with your AI counterpart, far behind once you've got some speed.
With the patch and after some fine tuning, you can have [http://janodesbois.free.fr/fg_screens/lag_test/f4n-compensated_lag.png a better matching].

[http://janodesbois.free.fr/fg_screens/lag_test/refuel.jpg Example with two MP planes in refuelling action]

===Jitter===

The records were made on a local network, so the lag was here, but the jitter was minimal. What happens when we add jitter to the UDP packet, i.e. when the time taken to travel from a player to another varies?
The multiplayer code has got a basic prediction system, but it is nearly never used, if the packets are retarded, FG makes the plane "waiting in the sky" and if they suddenly regain a fast lag travel, we will see the plane accelerating. This is what is called "rubber band phenomenon" among formation flightgear pilots, the thing that makes a refuelling impossible, or break a tow in a glider session...
It is possible to address this jitter, by using the sending packets time, and guessing what is due to jitter, and what is due to clock drift between the sender/receiver, but for now I lack the skills. My patch just try to make the time adjustment system more smooth, thus using more the prediction system.

A thing to consider here is to choose the same server, and one which give minimal jitter.

===Existing prediction system===

Just a few words about the system used to display the planes in the future.
It consists of Euler steps, starting from the last packet position and using the MP plane velocity and rotation data
* It works only without wind for Yasim aircrafts, as the speed transmitted in the UDP packet is the speed in the air mass and not in the reference frame as the JSBsim planes do.
* It was not intended to be used intensively, we always compute from the last packet position, and that charges the CPU if we try to predict to far in the future.
* This look OK on straight line, but the more you rotate, the more jumpy the displayed plane become, see for example the top of the cuban half figure in [http://www.youtube.com/watch?v=2eGOdBsd8Os the second video] (0'36), where this effect is clearly visible in number4 internal view. Note that all the external views were made with the UFO, with a display of the plane in the past, so no prediction system is at use.

== Next step ==

The next step is to try this with real mutiplayers, to see what's good, and what's wrong :)

==TODO list==

* Write a nasal part, to choose which planes to display in the future: on a distance base, from a "friend/wingman list, go more in the past when no direct interaction is needed (with camera/ufo, if we are just observer)
* Try something to guess what is jitter and what is clock drift ...
* Improve the prediction system, by using a dt approach instead of starting from last packet time at each computation
* Find what value is needed depending on the server ping, and the frequency of packet sending to have planes concordant positions from each player point of view.

[[Category:Multiplayer]]

General Dynamics F-16/Development

2012-07-04T11:12:09Z

Xiii: Radar fixed

This page will organize the development efforts for the F-16. See [[F16]].

=Efforts=

==Personnel==
Erik Hofman has kindly granted username: Blackbird to continue development on the F-16 model. This page was created to organize all development for this aircraft.

==Focus==
Development will attempt to accurately model the FlightGear F-16. Since the documentation for the MLU and F-16 C Block 50 variant is available in the form of the MLU manuals, many aspects of the current aircraft can be improved.

=System Development=

;High Priority
*Bind cockpit keys/buttons
*MFD/DED XML and Nasal scripts
** left MFD: radar works as expected <del>but is not displayed</del> ''FIXED in 2.8 GIT 20120704-10:50''.
*Steerpoint management
*EWMS for chaff/flare deployment
*MMC and CADC outputs (airspeed, GPS, system altitude, hack times, etc.)

;Medium Priority
*Optimize nasal code(better scripting, OOP)
*IFF, transponder
*VHF/UHF radios, TACAN, IFF
*FCR in MFD format
*RWR: needs some kind of point of view animation (ie. move the P.O.V. on click on the RWR so the whole screen can be seen). Works as expected.

;Low Priority
*Improve Cockpit Models
*Improve Textures

==Avionics==

;Units
*AIFF (Advanced Identification Friend or Foe)
*MMC (Modular Mission Computer)
*UFC (Upfront Controls)
*GPS (Global Positioning System)
*EUPDG/MFDS (Enhanced Upgraded Programmable Display Generator)
*SMS (Stores Management Set)
*IDM (Integrated Data Modem)
*CADC (Central Air Data Computer)
*INU (Inertial Navigation Unit)
*EWMS (Electronic Warfare Management System)
*FCR (Fire Control Radar)

;TDL
*Unified Logic development for ALL systems
*MFD Buttons
*MFD Display
*Steerpoint Management
*TACAN
*IDM/Radio Integration

;Progress
*UFC buttons enabled, Nasal page/key handler, XML display
*MFD Nasal page/key handler, XML display

;Resources
*[[Howto:Coding a Boeing CDU]]
*[[Howto:Implement a Control Display Unit]]
*[[Nasal CDU Framework]]
*[[Nasal Display Matrix Framework]]

==Electrical==

;TDL
*Create buses and components for avionics units, lighting, and other systems
*Link panel buttons to relevant switches
*Update loops to run only when electrical power is supplied

;Progress
*Nasal-Based Electrical System integrated into f16-set.xml

;Resources
*A Nasal-Based Electrical System for Flightgear, v 1.1 by Gary "Buckaroo" Neely - [http://www.buckarooshangar.com/flightgear/electrical_1.html]

==Hydraulics==

==Fuel==

==Failures==

==Original TDL==
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
** This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
** Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)

TDL FDM:
* Startup sequence
* Main U/C is above ground.
* Vibration when accelerating on the runway for takeof.

TDL Outside
* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)

TDL Cockpit and systems:
* HSI 3d model and textures.
* internal/external lighting panel.
* FMD's buttons pick animation. Define a logic in the FMD interactivity ?
* ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
* HUD modes:
** A/A mode
** Basic nav mode (those could be a first step in order to provide usability in short term)

Sounds: (Low priority)
* Establish a list of all sounds that can be produced by the F-16 and its driver:

Cockpit:
** switches
** knobs
** levers
** buttons
** wheels (ICP)
** rudder pedals
** ejection seat
** canopy **implemented**
** canopy lock **implemented**

Audio:
** "bitching betty"
*** missile launch
*** warning **implemented**
*** chaff/flare
*** jammer
** RWR
*** radar signature identification sounds
**** radar spike
**** radar lock
** gear horn (currently implemented as alert?)

Pilot:
** breathing
** movement
** brevity comms

External-sounds:
** engine **implemented**
** landing gear
*** up
*** down
*** broken
** ordnance
*** jettison store(s)
*** bomb drop
*** missile launch
*** 20mm cannon **implemented**
** damage
*** airframe overstress
*** gun hit
*** explosion
** Mid air refueling
*** refueling door
**** open
**** close
*** tank boom (tanker aircraft)
**** connect
**** disconnect

General Dynamics F-16/Development

2012-07-03T23:12:26Z

Xiii: checked the radar and RWR

This page will organize the development efforts for the F-16. See [[F16]].

=Efforts=

==Personnel==
Erik Hofman has kindly granted username: Blackbird to continue development on the F-16 model. This page was created to organize all development for this aircraft.

==Focus==
Development will attempt to accurately model the FlightGear F-16. Since the documentation for the MLU and F-16 C Block 50 variant is available in the form of the MLU manuals, many aspects of the current aircraft can be improved.

=System Development=

;High Priority
*Bind cockpit keys/buttons
*MFD/DED XML and Nasal scripts
** left MFD: radar works as expected but is not displayed.
*Steerpoint management
*EWMS for chaff/flare deployment
*MMC and CADC outputs (airspeed, GPS, system altitude, hack times, etc.)

;Medium Priority
*Optimize nasal code(better scripting, OOP)
*IFF, transponder
*VHF/UHF radios, TACAN, IFF
*FCR in MFD format
*RWR: needs some kind of point of view animation (ie. move the P.O.V. on click on the RWR so the whole screen can be seen). Works as expected.

;Low Priority
*Improve Cockpit Models
*Improve Textures

==Avionics==

;Units
*AIFF (Advanced Identification Friend or Foe)
*MMC (Modular Mission Computer)
*UFC (Upfront Controls)
*GPS (Global Positioning System)
*EUPDG/MFDS (Enhanced Upgraded Programmable Display Generator)
*SMS (Stores Management Set)
*IDM (Integrated Data Modem)
*CADC (Central Air Data Computer)
*INU (Inertial Navigation Unit)
*EWMS (Electronic Warfare Management System)
*FCR (Fire Control Radar)

;TDL
*Unified Logic development for ALL systems
*MFD Buttons
*MFD Display
*Steerpoint Management
*TACAN
*IDM/Radio Integration

;Progress
*UFC buttons enabled, Nasal page/key handler, XML display
*MFD Nasal page/key handler, XML display

;Resources
*[[Howto:Coding a Boeing CDU]]
*[[Howto:Implement a Control Display Unit]]
*[[Nasal CDU Framework]]
*[[Nasal Display Matrix Framework]]

==Electrical==

;TDL
*Create buses and components for avionics units, lighting, and other systems
*Link panel buttons to relevant switches
*Update loops to run only when electrical power is supplied

;Progress
*Nasal-Based Electrical System integrated into f16-set.xml

;Resources
*A Nasal-Based Electrical System for Flightgear, v 1.1 by Gary "Buckaroo" Neely - [http://www.buckarooshangar.com/flightgear/electrical_1.html]

==Hydraulics==

==Fuel==

==Failures==

==Original TDL==
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
** This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
** Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)

TDL FDM:
* Startup sequence
* Main U/C is above ground.
* Vibration when accelerating on the runway for takeof.

TDL Outside
* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)

TDL Cockpit and systems:
* HSI 3d model and textures.
* internal/external lighting panel.
* FMD's buttons pick animation. Define a logic in the FMD interactivity ?
* ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
* HUD modes:
** A/A mode
** Basic nav mode (those could be a first step in order to provide usability in short term)

Sounds: (Low priority)
* Establish a list of all sounds that can be produced by the F-16 and its driver:

Cockpit:
** switches
** knobs
** levers
** buttons
** wheels (ICP)
** rudder pedals
** ejection seat
** canopy **implemented**
** canopy lock **implemented**

Audio:
** "bitching betty"
*** missile launch
*** warning **implemented**
*** chaff/flare
*** jammer
** RWR
*** radar signature identification sounds
**** radar spike
**** radar lock
** gear horn (currently implemented as alert?)

Pilot:
** breathing
** movement
** brevity comms

External-sounds:
** engine **implemented**
** landing gear
*** up
*** down
*** broken
** ordnance
*** jettison store(s)
*** bomb drop
*** missile launch
*** 20mm cannon **implemented**
** damage
*** airframe overstress
*** gun hit
*** explosion
** Mid air refueling
*** refueling door
**** open
**** close
*** tank boom (tanker aircraft)
**** connect
**** disconnect

Talk:General Dynamics F-16/Development

2012-07-02T21:11:18Z

Xiii: xiii woud be happy to participate

Hi Blackbird,

I did already a bit of work on the f16 cockpit: central pedestal, RWR, radar, pilot's seat... I didn't check recently if all of this is in a good shape, but I'd be very happy to participate again on this model, specially if the project is well managed. With chance you can join me on IRC #flightgear (european TZ) or by email at "alexis dot bory at gmail dot com". My refs: [co-]author of A-10, A-6E, f-14b, E-2C, Vinson carrier...

[[User:Xiii|Xiii]] 17:11, 2 July 2012 (EDT)

Talk:Project Rembrandt

2012-06-03T20:22:19Z

Xiii: /* feed back on models */

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* <del>The bloom effect is a bit too much IHMO</del>. will it be settable per object ? ''(In my case it was too much because of bad and avoidable interaction between legacy emissiveness and rembrandt lights)''
* <del>SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value.</del> Seen the rendering dialog with a SSAO effect slider. Well done Fred.
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png
* Found some problems with transparent layers partially disappearing when yawing or pitching the view direction. If you like to test (an can stand the tomcat) try launching the f-14b, check that the HSD screen in on and displays the TID (radar) symbology. you'll see the radar sweep angle displayed with dashed lines, pitch the view, or move it to the side and you should see the lines disappear.
** http://www.maison-capestang.com/fg/f-14b/radar-20120603a.png What is expected.
** http://www.maison-capestang.com/fg/f-14b/radar-20120603b.png The sweep angle border lines and some of the aircrafts symbology (differents objects with transparent textures) disappear. Note at the bottom of the screen a piece of aircraft symbology, not overlaying the green and emissive background).

BTW: the f-14b in git has now plenty of nice light effects, try the switch and dimmers on the right console: http://www.maison-capestang.com/fg/f-14b/f-14b-right-console-light-panel.png note also the power switches on the DISPLAY panel (3 switches on the bottom row labeled POWER) for HUD, HSI and HSD.

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

Interesting: If you register an emissive object as transparent, it keeps its colored config. The following works with rembrandt: green emissive opaque object.

<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>screen-bkg</object-name>
</effect>
<animation>
<object-name>screen-bkg</object-name>
<type>material</type>
<emission>
<factor-prop>sim/model/f-14b/controls/VDI/contrast</factor-prop>
<red>0.0</red>
<green>0.7</green>
<blue>0.0</blue>
</emission>
</animation>

And it is realy cool news. But, but.... there are zbuffering issues (I suppose so because some overlaying transparent objects appears and disapear when the view pitch or yaw change).

[[User:Xiii|Xiii]] 03:57, 20 May 2012 (EDT)

Talk:Project Rembrandt

2012-06-03T20:21:40Z

Xiii: link to sceenshots

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* <del>The bloom effect is a bit too much IHMO</del>. will it be settable per object ? ''(In my case it was too much because of bad and avoidable interaction between legacy emissiveness and rembrandt lights)''
* <del>SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value.</del> Seen the rendering dialog with a SSAO effect slider. Well done Fred.
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png
* Found some problems with transparent layers partially disappearing when yawing or pitching the view direction. If you like to test (an can stand the tomcat) try launching the f-14b, check that the HSD screen in on and displays the TID (radar) symbology. you'll see the radar sweep angle displayed with dashed lines, pitch the view, or move it to the side and you should see the lines disappear.
** http://www.maison-capestang.com/fg/f-14b/radar-20120603a.png What is expected.
** http://www.maison-capestang.com/fg/f-14b/radar-20120603b.png The sweep angle border lines and some of the aircrafts symbology (differents objects with transparent textures) disapear. Note at the bottom of the screen a piece of aircraft symbology, not overlaying the green and emissive background).

BTW: the f-14b in git has now plenty of nice light effects, try the switch and dimmers on the right console: http://www.maison-capestang.com/fg/f-14b/f-14b-right-console-light-panel.png note also the power switches on the DISPLAY panel (3 switches on the bottom row labeled POWER) for HUD, HSI and HSD.

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

Interesting: If you register an emissive object as transparent, it keeps its colored config. The following works with rembrandt: green emissive opaque object.

<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>screen-bkg</object-name>
</effect>
<animation>
<object-name>screen-bkg</object-name>
<type>material</type>
<emission>
<factor-prop>sim/model/f-14b/controls/VDI/contrast</factor-prop>
<red>0.0</red>
<green>0.7</green>
<blue>0.0</blue>
</emission>
</animation>

And it is realy cool news. But, but.... there are zbuffering issues (I suppose so because some overlaying transparent objects appears and disapear when the view pitch or yaw change).

[[User:Xiii|Xiii]] 03:57, 20 May 2012 (EDT)

Talk:Project Rembrandt

2012-06-03T19:14:24Z

Xiii: /* feed back on models */

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* <del>The bloom effect is a bit too much IHMO</del>. will it be settable per object ? ''(In my case it was too much because of bad and avoidable interaction between legacy emissiveness and rembrandt lights)''
* <del>SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value.</del> Seen the rendering dialog with a SSAO effect slider. Well done Fred.
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png
* Found some problems with transparent layers partially disappearing when yawing or pitching the view direction. If you like to test (an can stand the tomcat) try launching the f-14b, check that the HSD screen in on and displays the TID (radar) symbology. you'll see the radar sweep angle displayed with dashed lines, pitch the view, or move it to the side and you should see the lines disappear.

BTW: the f-14b in git has now plenty of nice light effects, try the switch and dimmers on the right console: http://www.maison-capestang.com/fg/f-14b/f-14b-right-console-light-panel.png note also the power switches on the DISPLAY panel (3 switches on the bottom row labeled POWER) for HUD, HSI and HSD.

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

Interesting: If you register an emissive object as transparent, it keeps its colored config. The following works with rembrandt: green emissive opaque object.

<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>screen-bkg</object-name>
</effect>
<animation>
<object-name>screen-bkg</object-name>
<type>material</type>
<emission>
<factor-prop>sim/model/f-14b/controls/VDI/contrast</factor-prop>
<red>0.0</red>
<green>0.7</green>
<blue>0.0</blue>
</emission>
</animation>

And it is realy cool news. But, but.... there are zbuffering issues (I suppose so because some overlaying transparent objects appears and disapear when the view pitch or yaw change).

[[User:Xiii|Xiii]] 03:57, 20 May 2012 (EDT)

Talk:Project Rembrandt

2012-06-03T18:12:30Z

Xiii: /* feed back on models */

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* <del>The bloom effect is a bit too much IHMO</del>. will it be settable per object ? ''(In my case it was too much because of bad and avoidable interaction between legacy emissiveness and rembrandt lights)''
* <del>SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value.</del> Seen the rendering dialog with a SSAO effect slider. Well done Fred.
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png
* Found some problems with transparent layers partially disappearing when yawing or pitching the view direction. If you like to test (an can stand the tomcat) try launching the f-14b, check that the HSD screen in on and displays the TID (radar) symbology. you'll see the radar sweep angle displayed with dashed lines, pitch the view, or move it to the side and you should see the lines disappear.

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

Interesting: If you register an emissive object as transparent, it keeps its colored config. The following works with rembrandt: green emissive opaque object.

<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>screen-bkg</object-name>
</effect>
<animation>
<object-name>screen-bkg</object-name>
<type>material</type>
<emission>
<factor-prop>sim/model/f-14b/controls/VDI/contrast</factor-prop>
<red>0.0</red>
<green>0.7</green>
<blue>0.0</blue>
</emission>
</animation>

And it is realy cool news. But, but.... there are zbuffering issues (I suppose so because some overlaying transparent objects appears and disapear when the view pitch or yaw change).

[[User:Xiii|Xiii]] 03:57, 20 May 2012 (EDT)

Howto:Multiplayer

2012-05-23T13:44:11Z

Xiii: /* Servers */ I stopped the mail service a while ago

With the '''multiplayer''' function of [[FlightGear]] you are able to see other pilots and vice-versa. This makes it possible to fly in formation, [[Howto: Air-Air Refueling|connect to tankers]] controlled by real people or contact real [[ATC]]ers to ask for landing/takeoff clearence.

Multiplay may cause extreme [[Howto: Improve Framerates|framerate]] drops during loading of aircraft models. Especially heavy models can cause severe lag. Therefore, it is suggested to fly in locations other than [[KSFO]], where there are fewer pilots flying around.

== Servers ==
'''Please Note:''' The multiplayer servers are interconnected; you '''do not''' need to connect to a specific server in order to see other pilots who are on that server. For best performance, you should connect to the server that is geographically closest to you, has the lowest latency (ping time) or is the least busy.

{| class="prettytable" border="1px solid" cellspacing="0" cellpadding="2" style="border-collapse: collapse;"
! style="background:#efefef" |Server
! style="background:#efefef" |Location
! style="background:#efefef" |[http://fgfs.i-net.hu/modules/fgtracker/ Tracked]
! style="background:#efefef" |Maintainer
! style="background:#efefef" |[[IRC]] Name
! style="background:#efefef" |[http://flightgear.org/forums Forum] Name
! style="background:#efefef" |Comments
|-
|mpserver01.flightgear.org
|Germany
|Yes
|Oliver Schroeder
|os
|
|
|-
|mpserver02.flightgear.org
|Kansas, USA
|
|Sabin
|S-GECKO
|S-GECKO
|
|-
|mpserver03.flightgear.org
|Germany
|Yes
|Tobias Marx
|DocMarten
|
|
|-
|mpserver04.flightgear.org
|UK
|Yes
|Jon Stockill
|Nav
|JonS
|
|-
|mpserver05.flightgear.org
|Chicago, USA
|Yes
|Brant
|IonCannon218
|
|
|-
|mpserver06.flightgear.org
|Berlin, Germany
|Yes
|Sven Teichmann
|
|D-SAMI
|Unlimited traffic
|-
|mpserver07.flightgear.org
|Wisconsin, USA
|Yes
|Tom Betka
|TB
|
|
|-
|mpserver08.flightgear.org
|Frankfurt am Main, Germany
|Yes
|Roland
|Quix0r
|Quix0r
|10 TByte traffic, mostly short pings
|-
|mpserver09.flightgear.org
|Köln, Germany
|Yes
|Daniel Vigano
|Fauchi95
|
|
|-
|mpserver10.flightgear.org
|Montpellier, France
|Yes
|Alexis Bory
|xiii
|xiii
|
|-
|mpserver11.flightgear.org
|Vilnius, Lithuania
|Yes
|Darius
|
|ffg
|
|-
|mpserver12.flightgear.org
|Amsterdam, the Netherlands
|No
|Rob
|evilslut
|evilslut
|
|-
|mpserver13.flightgear.org
|Grenoble, France
|Yes
|Charles Ingels
|charles
|cbz-026
|
|}

Use [http://mpmap01.flightgear.org/mpstatus/ this], [http://mpmap02.flightgear.org/mpstatus/ this] or [http://flightgear.mxchange.org/mpstatus/ this] link to check if the MP servers are online. Locations of the servers are also available at [http://maps.google.nl/maps/ms?hl=nl&ie=UTF8&msa=0&msid=108788649448915642705.000481c029e653a30807c Google Maps].

If you are interested in hosting your own multiplayer server, you may want to check out [[Howto: Set up a multiplayer server]].
[[File:MP_Server.jpg|thumb|300px|[[MPMap]] screenshot]]
=== Multiplayer Map ===
{{Main article|MPMap}}

There is a very nice online map which displays the location of online pilots at [http://mpmap01.flightgear.org mpmap01] and/or [http://mpmap02.flightgear.org mpmap02]. You will also find this useful to check that you are successfully connecting to the server.

== Multiple connections per computer ==
It is possible to run multiple FlightGear instances on a single computer and connect them all to the multiplayer network. However, this requires some extras to keep in mind:
* both instances use the same out-port.
* one instance uses in port=5001, the other port 5002.
* and of course should both instances have unique callsigns.

== Using the Windows launcher / FGRun ==
[[File:Multiplayer.jpg|thumb|300px|Multiplayer options in [[FlightGear Wizard|FG Launcher]]]]
# Select your [[aircraft]] and starting airport as normal in [[FlightGear Launch Control|FGRun]].
# On the next screen, tick the "Multiplayer" box. Also tick the "AI models" box or you will not be able to see the other pilots' aircraft.
#* '''Callsign:''' of your choice. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether it is already in use or not. Do not pick a callsign that is already used!
#* '''Hostname:''' enter <tt>mpserverXX.flightgear.org</tt> (with <tt>XX</tt> being the [[#Servers|server number]]).
#* '''In/Out:''' set both ports to 5000.
# Click run and you'll soon be flying with other pilots!

To confirm that it's working, you can go to the multiplayer map at; http://mpmap02.flightgear.org/ (in Hong Kong). Once FlightGear has started, you will notice chat messages that say "Hello" indicating pilots that are online and then as they join (you can change this message by editing the <tt><chat type="string">Hello</chat></tt> line in <tt>[[$FG ROOT]]/preferences.xml</tt>). You may wish to use a different server (i.e. "Hostname" entry).

For more advanced settings, the <tt>Advanced > Network</tt> tab can be opened. You are able to remove the in or out lines only through this method for example.

== Using fgfs from the command line ==
First, for those who are very impatient and have a vague idea about what they're doing, the basic arguments to pass to fgfs for multiplayer are these;

--multiplay=out,10,server.ip.address,5000
--callsign=anything

where 5000 is the port number the server is listening on (which is 5000 for the official servers).

If you for some reason need to specify which local port and/or interface FlightGear should use add the following argument:

--multiplay=in,10,your.ip.address,portnumber

where portnumber is usually 5000 and your.ip.address is the ip address of the network interface being used by FG to connect to the server - even if that's a local 192.168 type address. You can also leave your.ip.address blank. FlightGear will then listen on all network interfaces:

--multiplay=in,10,,5000

''If you are using fgrun, please note that fgrun expects you to enter a valid (non-loopback, i.e. not 127.0.0.1) IP address or hostname for the local network interface.''

Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

=== Now, going more slowly for those who are completely lost... ===
Try the above first, and if it doesn't work, read on.

First of all, you need to know the IP address of the network interface you'll be using for multiplayer FG. If your Internet connection is via an ADSL modem that plugs directly into your computer with a USB connection, you should be able to find your IP address by visiting http://www.whatismyip.com . Please note that your ISP might not give you the same IP address each time - if MP stops working, check this first.

Otherwise, your connection is likely via some kind of router that connects to your computer via an RJ-45, or "Ethernet" connector (similar shape to most Western telephone plugs), or by a wireless link. You need to find the IP address of that network interface.

* Under '''linux''', this can be found by logging in as root and typing "ifconfig". You may find more than one interface listed, beginning with "lo" - ignore that one. You should have something like "eth0" or "wlan0" also listed - look through this block of text for "inet addr". This will be followed directly by the number you're looking for, e.g. "inet addr:192.168.0.150"
* Under '''Windows XP''' or '''Vista''', click start, run, and type "cmd". In the terminal window which appears, type "ipconfig" This should show you your IP address - write it down.
* With '''Windows 98''', click start, run, and type "winipcfg" to get information about your IP address.

This section _ought_ to be unnecessary now with recent versions of the FG server. If you have problems though, it won't hurt to follow through.

Now, all (!) that remains is to configure your router to forward UDP port 5000 to the IP address you've just found. This is not something that can be described in step-by-step detail, because each manufacturer's configuration interfaces differ greatly. Some tips are given here - if you get stuck, ask nicely on the [[FlightGear IRC channel]] for help (details on the flightgear website).

You should know how to log on to your router's configuration page, usually via a web browser. You are looking for settings pertaining to "port forwarding" "virtual server" "Forwarding Rules" or similar. When you have found the relevant settings, you need to add a rule that forwards port 5000 to the IP address you discovered earlier. If there is a choice given, ensure it is UDP ports that are forwarded. If there is no choice, you may assume that both TCP and UDP are being forwarded. Save your configuration, and most routers will probably then need to be rebooted to apply the changes.

Note: (for BSD users) If you are using a ADSL modem, you might have to put the port forward command into the ppp.conf file rather than firewall. This is because the firewall script will only run each time the machine is booted rather than the ppp line coming back online.

Finally, start FG using the command line given right at the start (if you're using the windows launcher you will find entry boxes for Multiplayer arguments - insert the relevant details there). You will end up with something like this;

fgfs --callsign=test --multiplay=in,10,192.168.0.2,5000 --multiplay=out,10,mpserver05.flightgear.org,5000 \
--airport=KSFO --runway=28R --aircraft=hunter

Choose your own callsign - this is currently limited to seven characters. Check [http://fgfs.i-net.hu/modules/fgtracker/ this page] to see whether your callsign is already in use or not. Do not pick a callsign that is already used, as that will create problems!

Once you have started FG, you should, if others are flying, see messages in the terminal from which FG was started, similar to the following;

Initialising john51a using 'Aircraft/ufo/Models/ufo.xml'
FGMultiplayRxMgr::ProcessRxData - Add new player. IP: 10.0.0.36,
Call: john51a,model: Aircraft/ufo/Models/ufo.xml

You MUST give your local, behind-the-router IP address for MultiPlayer to work. Trust me on this one!

You should check that your firewall is not causing problems - either turn it off _temporarily_ or add an exception to allow incoming connections on port 5000.

If it's still just not working for you, ask nicely on the [[FlightGear IRC channel]] and someone should be able to assist.

== Multiplayer Chat ==
{{Main article|Chat Menu}}

To chat with other pilots, go to the "Network" menu and select "Chat" or "Chat Menu" at the bottom of the menu. Note that the other pilots may not have their chat box open nor chat messages enabled, so they may not see your messages.

The shortcut for chatting is "_" (underscore) and it brings up a small window where you can type. By default, other people's messages are displayed at the top of Flightgear's window for a few seconds, but it will appear for a much longer time in the window at <tt>Network > Chat</tt>. So if you think you have missed anything, go check there.

'''NOTE:''' Multiplayer chat is not supported by FlightGear 0.9.10 or older.

== Coping with abusive behaviour ==
Should you become victim of abusive or annoying behaviour by any pilot you have option to ignore him or her. To activate the ignore function open the Network->"Pilot list" dialog and click the ignore button next to the pilot's call sign. In FlightGear 2.0.0 this will prevent chat messages from the ignored pilot from appearing and in FlightGear GIT of 21 May 2010 and later it will additionally prevent his aircraft from appearing.

'''NOTE:''' The ignore function is supported by FlightGear 2.0.0 or later.

== Related content ==
* [[FlightGear Multiplayer Server]]
* [[Howto: Set up a multiplayer server]]
* [[Multiplayer protocol]]
[[de:Howto: Multiplayer]]
[[es:Howto: Multijugador]]
[[fr:Howto: Multijoueur]]
[[nl:Howto: Multiplayer]]
[[pl: Konfiguracja trybu multiplayer]]

[[Category:Multiplayer]]
[[Category:Howto|Multiplayer]]

How the Nasal GC works

2012-05-22T18:39:47Z

Xiii: /* The pool manager */ typo

= Problem =
The [[Nasal]] language is a dynamic programming language, where memory is not manually allocated and freed by the programmer, but instead the Nasal virtual machine automatically allocates memory from so called "memory pools", every so often these memory pools must be checked, to see how many references (i.e. objects like variables) are still reachable, so that the unreachable ones can be removed from the memory pool and/or so that memory blocks in each pool can be allocated or freed. This is called "garbage management" or "garbage collection".

The current Nasal garbage collector (GC) is known to affect the frame rate in FlightGear and occasionally causes stutter (increased frame spacing) under certain circumstances (i.e. under heavy load, due to complex scripts - such as the [[Bombable]] addon or the local weather system.

This is largely attributed to the GC being a fairly simple sequential [http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)#Copying_vs._mark-and-sweep_vs._mark-and-don.27t-sweep mark/sweep collector], which needs to stop all operations, mark all reachable objects and free unreachable objects in an exclusive, single-threaded, fashion.

In other words, the time spent in the GC is proportial to the number of active objects (i.e. lines of code), even for objects which may not be running or active - just loaded. For additional background information, please see [[Improving Nasal]].

= Objective =
Provide a basic introduction to garbage collection and document how the existing Nasal GC scheme works, so that it can be fully understood, before alternatives (fixes/improvements) or additional implementations are added (feedback and contributions are encouraged and appreciated!).

Also, come up with an approach to generalize the Nasal GC API such that additional GC schemes can be easily implemented next to the native Nasal GC, providing an option to select a custom/experimental GC implementation at startup. Ideally, this should be possible by using a switch property during fgfs startup - such as --prop:/sim/nasal-gc=custom

= Suggested readings =
The wikipedia article on garbage collection contains some pretty good general GC information: http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)

In addition, the following online presentations provide a basic introduction to garbage collection:

* [http://lua-users.org/wiki/GarbageCollectionInRealTimeGames Garbage Collection in realtime games]
* [http://msdn.microsoft.com/en-us/library/ms973837.aspx Garbage Collector Basics and Performance Hints]
* http://www.memorymanagement.org/glossary/g.html#garbage.collection
* [http://www.slideshare.net/toantvo/garbage-collector-9434996 Garbage Collection Basics]
* http://www.slideshare.net/khuonganpt/basic-garbage-collection-techniques
* http://www.slideshare.net/achinth/garbage-collection-algorithms
* [http://www.slideshare.net/tinoubao/takano Unified Theory of Garbage Collection]
* [http://waww.iecc.com/gclist/GC-faq.htmlhttp://www.iecc.com/gclist/GC-faq.html GC FAQ]
* [http://www.iecc.com/gclist/GC-algorithms.html GC algorithms]
* http://www.cs.kent.ac.uk/people/staff/rej/gc.html

{{#ev:youtube|rp8PvFvSO_c|600|Lecture on GC (45 minutes)}}

= Mark/Sweep =

When using a mark-and-sweep collector, unreachable objects are not immediately reclaimed. Instead, garbage is allowed to accumulate until all available memory has been exhausted. When that happens, the execution of the program is suspended temporarily while the mark-and-sweep algorithm collects all the garbage. Once all unreferenced objects have been reclaimed, the normal execution of the program can resume.

Obviously, the main disadvantage of the mark-and-sweep approach is the fact that that normal program execution is suspended while the garbage collection algorithm runs. In particular, this can be a problem in a program that must satisfy real-time execution constraints (like a flight simulator). For example, an interactive application that uses mark-and-sweep garbage collection becomes unresponsive periodically.

The mark-and-sweep algorithm is called a tracing garbage collector because is traces out the entire collection of objects that are directly or indirectly accessible by the program. The objects that a program can access directly are those objects which are referenced by local variables on the processor stack as well as by any static variables that refer to objects. In the context of garbage collection, these variables are called the roots . An object is indirectly accessible if it is referenced by a field in some other (directly or indirectly) accessible object. An accessible object is said to be live . Conversely, an object which is not live is garbage.

The mark-and-sweep algorithm consists of two phases: In the first phase, it finds and marks all accessible objects. The first phase is called the mark phase. In the second phase, the garbage collection algorithm scans through the heap and reclaims all the unmarked objects. The second phase is called the sweep phase.

The mark/sweep algorithm can also be easily expressed using pseudo code, i.e. in Nasal itself:

<syntaxhighlight lang="php">

var garbageCollect = func (roots) {
foreach(var root; roots) {
mark(root);
}
sweep();
}

</syntaxhighlight>

The mark() function would just recursively check (i.e. calling itself) if the "marked" flag is set or not, and make sure to set the mark bit for all referenced objects:

<syntaxhighlight lang="php">

var mark = func (obj) {
if (!obj.marked) {
obj.marked=1;
foreach( var referenced; referenced_by(obj) )
mark(referenced);
}
}
</syntaxhighlight>

Finally, the sweep() function (reap() in the Nasal GC), will free all unreachable objects and reclaim the memory:

<syntaxhighlight lang="php">

var sweep = func {
foreach(var obj; allocated_objects) {
if (obj.marked) obj.marked=0;
else reclaim(obj);
}
}

</syntaxhighlight>

Nasal's implementation of sweep() ( called reap() ) works such that it is always executed for a handful of different type-specific memory pools. In addition, it also makes sure to allocate new memory if required.

= Pool storage =
A [http://en.wikipedia.org/wiki/Memory_pool memory pool] is basically a preallocated region of memory, which is dynamically resized. The Nasal GC works such that it manages a handful of global memory pools for all native Nasal types (strings, functions, vectors, hashes etc). At the moment, the hard coded defaults ensure that 25-50% of additional object "slots" (memory blocks) are kept available during each execution of reap() [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line287].

Whenever new memory is requested to create a new type (such as a vector or a string), the available memory in the corresponding pool will be checked, reachable objects will be marked, and dead objects will be removed from all pools using a mark/sweep collector, new memory blocks will be allocated if necessary. All of this happens atomically, i.e. single-threaded.

== Memory blocks ==

[[File:NasalBlockStruct.png|thumb|450px|Nasal Block structure]]

A Nasal memory pool consists of memory blocks.

A memory block is a [http://en.wikipedia.org/wiki/Linked_list#Linear_and_circular_lists singly linked list]: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line10

[[File:NasalNewBlockCallgraph.png|thumb|400px|Callgraph for newBlock()]]

Each block contains a field to store its size, a pointer to the allocated memory, and another pointer to the next block.

<syntaxhighlight lang="C">
struct Block {
int size; // size of the block
char* block; // pointer to the memory region
struct Block* next; // pointer to the next block
};
</syntaxhighlight>

New memory blocks are allocated using newBlock() and the memory is initialized with 0: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line150

<syntaxhighlight lang="C">
static void newBlock(struct naPool* p, int need)
{
int i;
struct Block* newb;
if(need < MIN_BLOCK_SIZE) need = MIN_BLOCK_SIZE;
// allocate a new Block
newb = naAlloc(sizeof(struct Block));
// initialize the Block
newb->block = naAlloc(need * p->elemsz); // number of elements * size of element
newb->size = need; // set block size
// memory blocks are circular linked lists:
newb->next = p->blocks;
p->blocks = newb;
naBZero(newb->block, need * p->elemsz);

if(need > p->freesz - p->freetop) need = p->freesz - p->freetop;
p->nfree = 0;
p->free = p->free0 + p->freetop;
// mark all new blocks as unreachable and add them to the pool's free list
for(i=0; i < need; i++) {
// initialize each new new memory blocks by setting up an naRef (the container for all Nasal references)
struct naObj* o = (struct naObj*)(newb->block + i*p->elemsz);
o->mark = 0;
p->free[p->nfree++] = o;
}
p->freetop += need;
}
</syntaxhighlight>

== Nasal memory pools ==

For each of the 7 Nasal data types, there is a separate storage pool available, declared as part of the "Globals" structure.

As can be seen, each storage pool is addressed by its enum index (0..6): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line65
<syntaxhighlight lang="C">
enum { T_STR, T_VEC, T_HASH, T_CODE, T_FUNC, T_CCODE, T_GHOST, NUM_NASAL_TYPES }; // V. important that this come last!
</syntaxhighlight>

For example, '''globals->pools[T_VEC]''' refers to the storage pools for vectors:

<syntaxhighlight lang="C">
globals->pools[T_VEC];
</syntaxhighlight>

The 7 storage pools are declared in code.h as part of the "Globals" structure, line 39: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line39

The relevant part is:

<syntaxhighlight lang="C">
struct Globals {
// Garbage collecting allocators:
struct naPool pools[NUM_NASAL_TYPES];
int allocCount;
// Dead blocks waiting to be freed when it is safe
void** deadBlocks;
int deadsz;
int ndead;
//...
};
</syntaxhighlight>

So, we have these pools:

* globals->pools[T_STR]
* globals->pools[T_VEC]
* globals->pools[T_HASH]
* globals->pools[T_CODE]
* globals->pools[T_FUNC]
* globals->pools[T_CCODE]
* globals->pools[T_GHOST]

== The Globals structure ==

[[File:NasalGlobalsStruct.png|thumb|500px|Nasal Globals structure]]

The complete Globals structure looks like this:
<syntaxhighlight lang="C">
struct Globals {
// Garbage collecting allocators:
struct naPool pools[NUM_NASAL_TYPES];
int allocCount;
// Dead blocks waiting to be freed when it is safe
void** deadBlocks;
int deadsz;
int ndead;

// Threading stuff

int nThreads;

int waitCount;

int needGC;

int bottleneck;

void* sem;

void* lock;

// Constants

naRef meRef;

naRef argRef;

naRef parentsRef;

// A hash of symbol names
naRef symbols;
naRef save;
struct Context* freeContexts;
struct Context* allContexts;
};
</syntaxhighlight>

== The naPool structure ==

[[File:NasalnaPoolStruct.png|thumb|400px|Nasal naPool structure]]

The structure keeping all pool-related information is named "naPool", the layout of the naPool structure can be seen in data.h, line 172: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line172
<syntaxhighlight lang="C">
struct naPool {
int type; // one of T_STR, T_VEC, T_HASH etc
int elemsz; // size of each element - determined via naTypeSize(T_*)
struct Block* blocks;
void** free0; // pointer to the alloced buffer
int freesz; // size of the alloced buffer
void** free; // current "free frame"
int nfree; // down-counting index within the free frame
int freetop; // curr. top of the free list
};
</syntaxhighlight>

Each memory pool is initialized using naGC_init(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line175

<syntaxhighlight lang="C">
void naGC_init(struct naPool* p, int type)
{
p->type = type;
p->elemsz = naTypeSize(type);
p->blocks = 0;
p->free0 = p->free = 0;
p->nfree = p->freesz = p->freetop = 0;
reap(p);
}
</syntaxhighlight>

As can be seen, "elemsz" just stores the size of each type-specific structure, so that it can be used for new allocations.

naGC_init is called in initGlobals() in code.c for each Nasal type (T_STR, T_VEC etc): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.c#line170
<syntaxhighlight lang="C">
for(i=0; i<NUM_NASAL_TYPES; i++)
naGC_init(&(globals->pools[i]), i);
</syntaxhighlight>

The size of a memory pool is determined using poolsize(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line186

<syntaxhighlight lang="C">
static int poolsize(struct naPool* p)
{
int total = 0;
struct Block* b = p->blocks;
while(b) { total += b->size; b = b->next; }
return total;
}
</syntaxhighlight>

The function poolsize() just iterates over all memory blocks in the pool, and computes the total size of the pool by adding up the "size" field of all blocks in the linked list.

= Allocating Nasal types =

All Nasal types (scalars, vectors, hashes, funcs, ghosts) are allocated via wrappers in [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c misc.c].

These wrappers are:
* naNewString(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line77
* naNewVector(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line87
* naNewHash(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line94
* naNewCode(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line101
* naNewCCode(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line106
* naNewFunc(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line113
* naNewGhost(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line122
* naNewGhost2(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line135

All of these wrappers are really just helpers on top of naNew(), they just set up type-specific information and initialize each Nasal type properly.
For instance, first naNew() is called for the given context, along with the type info (to set up the size properly)- and then each type is initialized:
<syntaxhighlight lang="C">
// The naNew* helpers are just wrappers to set up type-specific structures, after allocating the memory using naNew()
naRef naNewString(struct Context* c)
{
naRef s = naNew(c, T_STR);
PTR(s).str->emblen = 0;
PTR(s).str->data.ref.len = 0;
PTR(s).str->data.ref.ptr = 0;
PTR(s).str->hashcode = 0;
return s;
}
</syntaxhighlight>

= naNew() =

As can be seen, the key allocator function is [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line66 naNew()].
All memory allocations done via the naNew*() helpers will first of all set up memory using naNew().

naNew() is really just a fancy malloc() replacement, i.e. it's just getting passed the Nasal execution context, and the nasal type (which is mapped to the size of the requested memory region using naTypeSize()).

The naNew() function is also implemented in misc.c, see [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line122 line 66]:

<syntaxhighlight lang="C">
naRef naNew(struct Context* c, int type)
{
naRef result;
if(c->nfree[type] == 0)
c->free[type] = naGC_get(&globals->pools[type],
OBJ_CACHE_SZ, &c->nfree[type]);
result = naObj(type, c->free[type][--c->nfree[type]]);
naTempSave(c, result);
return result;
}
</syntaxhighlight>

First, the conditional checks if there's any free memory in the Nasal storage pools for the requested Nasal data type, if there isn't any free memory left, new memory is assigned to the contexts->free[type] pool via naGC_get().

'''Note:''' naGC_get() is the only function which really manages all memory pools and which triggers the GC. Allocations via naNew()* will end up calling naNew() and naNew() ends up calling naGC_get() '''always'''.

For the time being, OBJ_CACHE_SZ can be ignored, it's defined in code.h, line 12: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line12
<syntaxhighlight lang="C">
// Number of objects (per pool per thread) asked for using naGC_get().
// The idea is that contexts can "cache" allocations to prevent thread
// contention on the global pools. But in practice this interacts
// very badly with small subcontext calls, which grab huge numbers of
// cached objects and don't use them, causing far more collections
// than necessary. Just leave it at 1 pending a rework of the
// collector synchronization.
#define OBJ_CACHE_SZ 1
</syntaxhighlight>

The final argument to the naGC_get() function is a pointer to to the context's nfree[type] member which is updated by the function.

Next, a new naRef structure is set up using the allocated naObj memory and the type info:

<syntaxhighlight lang="C">
result = naObj(type, c->free[type][--c->nfree[type]]);
</syntaxhighlight>

<syntaxhighlight lang="C">
naRef naObj(int type, struct naObj* o)
{
naRef r;
SETPTR(r, o);
o->type = type;
return r;
}
</syntaxhighlight>

= The GC interface =

[[File:Nasal-gc.png|thumb|650px|Nasal GC]]

TODO: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line204

* void naGC_init(struct naPool* p, int type);
* struct naObj** naGC_get(struct naPool* p, int n, int* nout);
* void naGC_swapfree(void** target, void* val); (used for vector/hash resizing)
* void naGC_freedead();
* void naiGCMark(naRef r);
* void naiGCMarkHash(naRef h);

= The pool manager =

[[File:NasalNaGetCallgraph.png|thumb|550px|Callgraph for naGC_get()]]

All high level type allocators (naNewString, naNewVector, naNewHash etc) make use of the naNew() call introduced earlier.

naNew() doesn't directly allocate new memory from the heap using naAlloc(), but instead use the naGC_get() helper which manages memory from the global pools (i.e. preallocated memory for each type).

For each native Nasal data type (scalars, vectors, hashes, funcs etc) , there are separate memory pools in globals->pools[n]. The index (n) is one of T_VEC, T_HASH, T_FUNC etc.

The naGC_get() pool "manager" is located in gc.nas line 194: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line194

<syntaxhighlight lang="C">
struct naObj** naGC_get(struct naPool* p, int n, int* nout)
{
struct naObj** result;
naCheckBottleneck();
LOCK();
while(globals->allocCount < 0 || (p->nfree == 0 && p->freetop >= p->freesz)) {
globals->needGC = 1;
bottleneck();
}
if(p->nfree == 0)
newBlock(p, poolsize(p)/8);
n = p->nfree < n ? p->nfree : n;
*nout = n;
p->nfree -= n;
globals->allocCount -= n;
result = (struct naObj**)(p->free + p->nfree);
UNLOCK();
return result;
}
</syntaxhighlight>

As can be seen, the garbage collector itself is triggered by setting the global "needGC" flag to 1 in the globals structure and then calling the bottleneck() function: [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line199].

In line 209, the memory region from the global pool is cast back to a pointer (struct naObj**): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line209
the "nout" parameter is just there to update c->nfree[type] with the amount of free memory.

In other words, whenever new Nasal types are allocated, new memory from one of the 7 Nasal pools is requested. All of these allocation requests are channeled through naNew() and finally naGC_get(). naGC_get() is the de facto memory manager in Nasal, all memory management is triggered here - new memory block allocations for each pool, as well as garbage collection via the bottleneck() call.

This also means that we basically just need to provide an alternate naGC_get() function, next to the existing one, to add support for alternate GC schemes.

= Disabling the current GC =

The overhead caused by managing the memory pools and constantly scanning the heap (mark/reap) can be examined by modifying the naGC_get() function such that it no longer uses any pool memory, but directly allocates via malloc()/naAlloc() - without ever freeing any memory (i.e. leaking). While the fgfs process will eventually get killed this way, the GC will be basically switched off.

<syntaxhighlight lang="C">
struct naObj** naGC_get(struct naPool* p, int n, int* nout)
{
struct naObj** result;
naCheckBottleneck();
LOCK();
#define LEAKY
#ifndef LEAKY
while(globals->allocCount < 0 || (p->nfree == 0 && p->freetop >= p->freesz)) {
globals->needGC = 1;
bottleneck();
}
if(p->nfree == 0)
newBlock(p, poolsize(p)/8);
n = p->nfree < n ? p->nfree : n;
*nout = n;
p->nfree -= n;
globals->allocCount -= n;
result = (struct naObj**)(p->free + p->nfree);
#else
result = (struct naObj**) naAlloc( naTypeSize(n) );
#endif
UNLOCK();
return result;
}
</syntaxhighlight>

= bottleneck() =

[[File:NasalCheckBottleneckCallerGraph.png|thumb|450px|Callergraph of naCheckBottleneck()]]
[[File:NasalCheckBottleneckCallgraph.png|thumb|400px|Callgraph of naCheckBottleneck()]]

Whenever new memory from one of the global pools is being requested via naGC_get(), naCheckBottleneck() will also be invoked:

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line121

<syntaxhighlight lang="C">
void naCheckBottleneck()
{
if(globals->bottleneck) { LOCK(); bottleneck(); UNLOCK(); }
}
</syntaxhighlight>

This checks if globals->bottleneck is true, and if it is, it makes sure that the bottleneck() function is only invoked after acquiring a lock.

[[File:NasalBottleneckCallgraph.png|thumb|550px|Callgraph of bottleneck()]]

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line99
<syntaxhighlight lang="C">
// Must be called with the main lock. Engages the "bottleneck", where
// all threads will block so that one (the last one to call this
// function) can run alone. This is done for GC, and also to free the
// list of "dead" blocks when it gets full (which is part of GC, if
// you think about it).
static void bottleneck()
{
struct Globals* g = globals;
g->bottleneck = 1;
while(g->bottleneck && g->waitCount < g->nThreads - 1) {
g->waitCount++;
UNLOCK(); naSemDown(g->sem); LOCK();
g->waitCount--;
}
if(g->waitCount >= g->nThreads - 1) {
freeDead();
if(g->needGC) garbageCollect();
if(g->waitCount) naSemUp(g->sem, g->waitCount);
g->bottleneck = 0;
}
}
</syntaxhighlight>

The actual garbage collection takes place in [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line114 line 114] where dead objects from the memory pool are freed, and the garbageCollect() function is called if globals.needGC is true.

= garbageCollect() =

[[File:NasalGarbageCollectCallgraph.png|thumb|550px|Callgraph of garbageCollect()]]

This is the function that does the mark/sweep part using mark() to recursively mark reachable objects, and reap() to collect unreachable objects.

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line35

<syntaxhighlight lang="C">
// Must be called with the big lock!
static void garbageCollect()
{
int i;
struct Context* c;
globals->allocCount = 0;
c = globals->allContexts;
while(c) {
for(i=0; i<NUM_NASAL_TYPES; i++)
c->nfree[i] = 0;
for(i=0; i < c->fTop; i++) {
mark(c->fStack[i].func);
mark(c->fStack[i].locals);
}
for(i=0; i < c->opTop; i++)
mark(c->opStack[i]);
mark(c->dieArg);
marktemps(c);
c = c->nextAll;
}
mark(globals->save);
mark(globals->symbols);
mark(globals->meRef);
mark(globals->argRef);
mark(globals->parentsRef);
// Finally collect all the freed objects
for(i=0; i<NUM_NASAL_TYPES; i++)
reap(&(globals->pools[i]));
// Make enough space for the dead blocks we need to free during
// execution. This works out to 1 spot for every 2 live objects,
// which should be limit the number of bottleneck operations
// without imposing an undue burden of extra "freeable" memory.
if(globals->deadsz < globals->allocCount) {
globals->deadsz = globals->allocCount;
if(globals->deadsz < 256) globals->deadsz = 256;
naFree(globals->deadBlocks);
globals->deadBlocks = naAlloc(sizeof(void*) * globals->deadsz);
}
globals->needGC = 0;
}
</syntaxhighlight>

For each invocation of garbageCollect(), the following takes place:
* For each context:
** The counter for each type-specific pool will be reset to 0 in line 43: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line43
** for each stack frame of the given context, all reachable locals and functions will be marked as reachable in line 45: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line45
** All instructions in the opcode stack will be marked as reachable from top to bottom in line 49: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line49
** mark(die->Arg)
** temporary variables are marked reachable
* root references (constants) are marked reachable in line56: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line56
* foreach Nasal data type:
** unreachable objects are then collected in line 62: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line62
* dead blocks are freed and new memory is allocated in line: 66 https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line66
* the needGC flag is set to 0

= mark() =

[[File:NasalMarkCallgraph.png|thumb|400px|Callgraph of mark()]]

All reachable objects are recursively marked using tagged naRef structures [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line50], so that unreachable objects can be collected (i.e. because the reftag bit is not set) and freed.

TOOD: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line223
<syntaxhighlight lang="C">

</syntaxhighlight>

= reap() =

[[File:NasalReapCallgraph.png|thumb|450px|Callgraph for reap()]]

This is the collector function called by garbageCollect() which also frees elements and allocates new blocks for the specified pool:

<syntaxhighlight lang="C">
// Collects all the unreachable objects into a free list, and
// allocates more space if needed.
static void reap(struct naPool* p)
{
struct Block* b;
int elem, freesz, total = poolsize(p);
freesz = total < MIN_BLOCK_SIZE ? MIN_BLOCK_SIZE : total;
freesz = (3 * freesz / 2) + (globals->nThreads * OBJ_CACHE_SZ);
if(p->freesz < freesz) {
naFree(p->free0);
p->freesz = freesz;
p->free = p->free0 = naAlloc(sizeof(void*) * p->freesz);
}
p->nfree = 0;
p->free = p->free0;
for(b = p->blocks; b; b = b->next)
for(elem=0; elem < b->size; elem++) {
struct naObj* o = (struct naObj*)(b->block + elem * p->elemsz);
if(o->mark == 0)
freeelem(p, o);
o->mark = 0;
}
p->freetop = p->nfree;
// allocs of this type until the next collection
globals->allocCount += total/2;
// Allocate more if necessary (try to keep 25-50% of the objects
// available)
if(p->nfree < total/4) {
int used = total - p->nfree;
int avail = total - used;
int need = used/2 - avail;
if(need > 0)
newBlock(p, need);
}
}
</syntaxhighlight>

=swapfree() =
[[File:NasalGC swapfreeCallgraph.png|thumb|450px|Callgraph of swapfree()]]

= freeelem() =

[[File:NasalFreeelemCallgraph.png|thumb|Callgraph of freeelem()]]

Frees individual elements and adds freed pointers to the globals free list, implemented in gc.c: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line137
<syntaxhighlight lang="C">
static void freeelem(struct naPool* p, struct naObj* o)
{
// Clean up any intrinsic storage the object might have...
switch(p->type) {
case T_STR: naStr_gcclean ((struct naStr*) o); break;
case T_VEC: naVec_gcclean ((struct naVec*) o); break;
case T_HASH: naiGCHashClean ((struct naHash*) o); break;
case T_CODE: naCode_gcclean ((struct naCode*) o); break;
case T_GHOST: naGhost_gcclean((struct naGhost*)o); break;
}
p->free[p->nfree++] = o; // ...and add it to the free list
}
</syntaxhighlight>

= Type destructors =
Will be called by freelem(), implemented for all native Nasal types:

* strings (T_STR): naStr_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/string.c#line113]
* vectors (T_VEC): naVec_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/vector.c#line22]
* hashes (T_HASH): naiGCHashClean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/hash.c#line221]
* code (T_CODE): naCode_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line126]
* ghosts (T_GHOST): naGhost_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line131]

= Contexts =

[[File:NasalContextStruct.png|thumb|500px|Nasal Context structure]]

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line71
<syntaxhighlight lang="C">
struct Context {

// Stack(s)

struct Frame fStack[MAX_RECURSION];

int fTop;

naRef opStack[MAX_STACK_DEPTH];

int opFrame; // like Frame::bp, but for C functions

int opTop;

int markStack[MAX_MARK_DEPTH];

int markTop;

// Free object lists, cached from the global GC

struct naObj** free[NUM_NASAL_TYPES];

int nfree[NUM_NASAL_TYPES];

// GC-findable reference point for objects that may live on the

// processor ("real") stack during execution. naNew() places them

// here, and clears the array each instruction

struct naObj** temps;

int ntemps;

int tempsz;

// Error handling

jmp_buf jumpHandle;

char error[128];

naRef dieArg;

// Sub-call lists

struct Context* callParent;

struct Context* callChild;

// Linked list pointers in globals

struct Context* nextFree;

struct Context* nextAll;

void* userData;

};
</syntaxhighlight>

= Stack frames =
https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line32

= Tagged structures =
https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line84

= Core allocations =
All core memory allocation takes place via wrappers in [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line8 misc.c]:

<syntaxhighlight lang="C">
void naFree(void* m) { free(m); }
void* naAlloc(int n) { return malloc(n); }
void* naRealloc(void* b, int n) { return realloc(b, n); }
void naBZero(void* m, int n) { memset(m, 0, n); }
</syntaxhighlight>

[[Category:Core developer documentation]]
[[Category:Nasal]]

How the Nasal GC works

2012-05-22T18:26:26Z

Xiii: /* Mark/Sweep */ typo

= Problem =
The [[Nasal]] language is a dynamic programming language, where memory is not manually allocated and freed by the programmer, but instead the Nasal virtual machine automatically allocates memory from so called "memory pools", every so often these memory pools must be checked, to see how many references (i.e. objects like variables) are still reachable, so that the unreachable ones can be removed from the memory pool and/or so that memory blocks in each pool can be allocated or freed. This is called "garbage management" or "garbage collection".

The current Nasal garbage collector (GC) is known to affect the frame rate in FlightGear and occasionally causes stutter (increased frame spacing) under certain circumstances (i.e. under heavy load, due to complex scripts - such as the [[Bombable]] addon or the local weather system.

This is largely attributed to the GC being a fairly simple sequential [http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)#Copying_vs._mark-and-sweep_vs._mark-and-don.27t-sweep mark/sweep collector], which needs to stop all operations, mark all reachable objects and free unreachable objects in an exclusive, single-threaded, fashion.

In other words, the time spent in the GC is proportial to the number of active objects (i.e. lines of code), even for objects which may not be running or active - just loaded. For additional background information, please see [[Improving Nasal]].

= Objective =
Provide a basic introduction to garbage collection and document how the existing Nasal GC scheme works, so that it can be fully understood, before alternatives (fixes/improvements) or additional implementations are added (feedback and contributions are encouraged and appreciated!).

Also, come up with an approach to generalize the Nasal GC API such that additional GC schemes can be easily implemented next to the native Nasal GC, providing an option to select a custom/experimental GC implementation at startup. Ideally, this should be possible by using a switch property during fgfs startup - such as --prop:/sim/nasal-gc=custom

= Suggested readings =
The wikipedia article on garbage collection contains some pretty good general GC information: http://en.wikipedia.org/wiki/Garbage_collection_(computer_science)

In addition, the following online presentations provide a basic introduction to garbage collection:

* [http://lua-users.org/wiki/GarbageCollectionInRealTimeGames Garbage Collection in realtime games]
* [http://msdn.microsoft.com/en-us/library/ms973837.aspx Garbage Collector Basics and Performance Hints]
* http://www.memorymanagement.org/glossary/g.html#garbage.collection
* [http://www.slideshare.net/toantvo/garbage-collector-9434996 Garbage Collection Basics]
* http://www.slideshare.net/khuonganpt/basic-garbage-collection-techniques
* http://www.slideshare.net/achinth/garbage-collection-algorithms
* [http://www.slideshare.net/tinoubao/takano Unified Theory of Garbage Collection]
* [http://waww.iecc.com/gclist/GC-faq.htmlhttp://www.iecc.com/gclist/GC-faq.html GC FAQ]
* [http://www.iecc.com/gclist/GC-algorithms.html GC algorithms]
* http://www.cs.kent.ac.uk/people/staff/rej/gc.html

{{#ev:youtube|rp8PvFvSO_c|600|Lecture on GC (45 minutes)}}

= Mark/Sweep =

When using a mark-and-sweep collector, unreachable objects are not immediately reclaimed. Instead, garbage is allowed to accumulate until all available memory has been exhausted. When that happens, the execution of the program is suspended temporarily while the mark-and-sweep algorithm collects all the garbage. Once all unreferenced objects have been reclaimed, the normal execution of the program can resume.

Obviously, the main disadvantage of the mark-and-sweep approach is the fact that that normal program execution is suspended while the garbage collection algorithm runs. In particular, this can be a problem in a program that must satisfy real-time execution constraints (like a flight simulator). For example, an interactive application that uses mark-and-sweep garbage collection becomes unresponsive periodically.

The mark-and-sweep algorithm is called a tracing garbage collector because is traces out the entire collection of objects that are directly or indirectly accessible by the program. The objects that a program can access directly are those objects which are referenced by local variables on the processor stack as well as by any static variables that refer to objects. In the context of garbage collection, these variables are called the roots . An object is indirectly accessible if it is referenced by a field in some other (directly or indirectly) accessible object. An accessible object is said to be live . Conversely, an object which is not live is garbage.

The mark-and-sweep algorithm consists of two phases: In the first phase, it finds and marks all accessible objects. The first phase is called the mark phase. In the second phase, the garbage collection algorithm scans through the heap and reclaims all the unmarked objects. The second phase is called the sweep phase.

The mark/sweep algorithm can also be easily expressed using pseudo code, i.e. in Nasal itself:

<syntaxhighlight lang="php">

var garbageCollect = func (roots) {
foreach(var root; roots) {
mark(root);
}
sweep();
}

</syntaxhighlight>

The mark() function would just recursively check (i.e. calling itself) if the "marked" flag is set or not, and make sure to set the mark bit for all referenced objects:

<syntaxhighlight lang="php">

var mark = func (obj) {
if (!obj.marked) {
obj.marked=1;
foreach( var referenced; referenced_by(obj) )
mark(referenced);
}
}
</syntaxhighlight>

Finally, the sweep() function (reap() in the Nasal GC), will free all unreachable objects and reclaim the memory:

<syntaxhighlight lang="php">

var sweep = func {
foreach(var obj; allocated_objects) {
if (obj.marked) obj.marked=0;
else reclaim(obj);
}
}

</syntaxhighlight>

Nasal's implementation of sweep() ( called reap() ) works such that it is always executed for a handful of different type-specific memory pools. In addition, it also makes sure to allocate new memory if required.

= Pool storage =
A [http://en.wikipedia.org/wiki/Memory_pool memory pool] is basically a preallocated region of memory, which is dynamically resized. The Nasal GC works such that it manages a handful of global memory pools for all native Nasal types (strings, functions, vectors, hashes etc). At the moment, the hard coded defaults ensure that 25-50% of additional object "slots" (memory blocks) are kept available during each execution of reap() [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line287].

Whenever new memory is requested to create a new type (such as a vector or a string), the available memory in the corresponding pool will be checked, reachable objects will be marked, and dead objects will be removed from all pools using a mark/sweep collector, new memory blocks will be allocated if necessary. All of this happens atomically, i.e. single-threaded.

== Memory blocks ==

[[File:NasalBlockStruct.png|thumb|450px|Nasal Block structure]]

A Nasal memory pool consists of memory blocks.

A memory block is a [http://en.wikipedia.org/wiki/Linked_list#Linear_and_circular_lists singly linked list]: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line10

[[File:NasalNewBlockCallgraph.png|thumb|400px|Callgraph for newBlock()]]

Each block contains a field to store its size, a pointer to the allocated memory, and another pointer to the next block.

<syntaxhighlight lang="C">
struct Block {
int size; // size of the block
char* block; // pointer to the memory region
struct Block* next; // pointer to the next block
};
</syntaxhighlight>

New memory blocks are allocated using newBlock() and the memory is initialized with 0: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line150

<syntaxhighlight lang="C">
static void newBlock(struct naPool* p, int need)
{
int i;
struct Block* newb;
if(need < MIN_BLOCK_SIZE) need = MIN_BLOCK_SIZE;
// allocate a new Block
newb = naAlloc(sizeof(struct Block));
// initialize the Block
newb->block = naAlloc(need * p->elemsz); // number of elements * size of element
newb->size = need; // set block size
// memory blocks are circular linked lists:
newb->next = p->blocks;
p->blocks = newb;
naBZero(newb->block, need * p->elemsz);

if(need > p->freesz - p->freetop) need = p->freesz - p->freetop;
p->nfree = 0;
p->free = p->free0 + p->freetop;
// mark all new blocks as unreachable and add them to the pool's free list
for(i=0; i < need; i++) {
// initialize each new new memory blocks by setting up an naRef (the container for all Nasal references)
struct naObj* o = (struct naObj*)(newb->block + i*p->elemsz);
o->mark = 0;
p->free[p->nfree++] = o;
}
p->freetop += need;
}
</syntaxhighlight>

== Nasal memory pools ==

For each of the 7 Nasal data types, there is a separate storage pool available, declared as part of the "Globals" structure.

As can be seen, each storage pool is addressed by its enum index (0..6): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line65
<syntaxhighlight lang="C">
enum { T_STR, T_VEC, T_HASH, T_CODE, T_FUNC, T_CCODE, T_GHOST, NUM_NASAL_TYPES }; // V. important that this come last!
</syntaxhighlight>

For example, '''globals->pools[T_VEC]''' refers to the storage pools for vectors:

<syntaxhighlight lang="C">
globals->pools[T_VEC];
</syntaxhighlight>

The 7 storage pools are declared in code.h as part of the "Globals" structure, line 39: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line39

The relevant part is:

<syntaxhighlight lang="C">
struct Globals {
// Garbage collecting allocators:
struct naPool pools[NUM_NASAL_TYPES];
int allocCount;
// Dead blocks waiting to be freed when it is safe
void** deadBlocks;
int deadsz;
int ndead;
//...
};
</syntaxhighlight>

So, we have these pools:

* globals->pools[T_STR]
* globals->pools[T_VEC]
* globals->pools[T_HASH]
* globals->pools[T_CODE]
* globals->pools[T_FUNC]
* globals->pools[T_CCODE]
* globals->pools[T_GHOST]

== The Globals structure ==

[[File:NasalGlobalsStruct.png|thumb|500px|Nasal Globals structure]]

The complete Globals structure looks like this:
<syntaxhighlight lang="C">
struct Globals {
// Garbage collecting allocators:
struct naPool pools[NUM_NASAL_TYPES];
int allocCount;
// Dead blocks waiting to be freed when it is safe
void** deadBlocks;
int deadsz;
int ndead;

// Threading stuff

int nThreads;

int waitCount;

int needGC;

int bottleneck;

void* sem;

void* lock;

// Constants

naRef meRef;

naRef argRef;

naRef parentsRef;

// A hash of symbol names
naRef symbols;
naRef save;
struct Context* freeContexts;
struct Context* allContexts;
};
</syntaxhighlight>

== The naPool structure ==

[[File:NasalnaPoolStruct.png|thumb|400px|Nasal naPool structure]]

The structure keeping all pool-related information is named "naPool", the layout of the naPool structure can be seen in data.h, line 172: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line172
<syntaxhighlight lang="C">
struct naPool {
int type; // one of T_STR, T_VEC, T_HASH etc
int elemsz; // size of each element - determined via naTypeSize(T_*)
struct Block* blocks;
void** free0; // pointer to the alloced buffer
int freesz; // size of the alloced buffer
void** free; // current "free frame"
int nfree; // down-counting index within the free frame
int freetop; // curr. top of the free list
};
</syntaxhighlight>

Each memory pool is initialized using naGC_init(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line175

<syntaxhighlight lang="C">
void naGC_init(struct naPool* p, int type)
{
p->type = type;
p->elemsz = naTypeSize(type);
p->blocks = 0;
p->free0 = p->free = 0;
p->nfree = p->freesz = p->freetop = 0;
reap(p);
}
</syntaxhighlight>

As can be seen, "elemsz" just stores the size of each type-specific structure, so that it can be used for new allocations.

naGC_init is called in initGlobals() in code.c for each Nasal type (T_STR, T_VEC etc): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.c#line170
<syntaxhighlight lang="C">
for(i=0; i<NUM_NASAL_TYPES; i++)
naGC_init(&(globals->pools[i]), i);
</syntaxhighlight>

The size of a memory pool is determined using poolsize(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line186

<syntaxhighlight lang="C">
static int poolsize(struct naPool* p)
{
int total = 0;
struct Block* b = p->blocks;
while(b) { total += b->size; b = b->next; }
return total;
}
</syntaxhighlight>

The function poolsize() just iterates over all memory blocks in the pool, and computes the total size of the pool by adding up the "size" field of all blocks in the linked list.

= Allocating Nasal types =

All Nasal types (scalars, vectors, hashes, funcs, ghosts) are allocated via wrappers in [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c misc.c].

These wrappers are:
* naNewString(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line77
* naNewVector(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line87
* naNewHash(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line94
* naNewCode(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line101
* naNewCCode(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line106
* naNewFunc(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line113
* naNewGhost(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line122
* naNewGhost2(): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line135

All of these wrappers are really just helpers on top of naNew(), they just set up type-specific information and initialize each Nasal type properly.
For instance, first naNew() is called for the given context, along with the type info (to set up the size properly)- and then each type is initialized:
<syntaxhighlight lang="C">
// The naNew* helpers are just wrappers to set up type-specific structures, after allocating the memory using naNew()
naRef naNewString(struct Context* c)
{
naRef s = naNew(c, T_STR);
PTR(s).str->emblen = 0;
PTR(s).str->data.ref.len = 0;
PTR(s).str->data.ref.ptr = 0;
PTR(s).str->hashcode = 0;
return s;
}
</syntaxhighlight>

= naNew() =

As can be seen, the key allocator function is [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line66 naNew()].
All memory allocations done via the naNew*() helpers will first of all set up memory using naNew().

naNew() is really just a fancy malloc() replacement, i.e. it's just getting passed the Nasal execution context, and the nasal type (which is mapped to the size of the requested memory region using naTypeSize()).

The naNew() function is also implemented in misc.c, see [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line122 line 66]:

<syntaxhighlight lang="C">
naRef naNew(struct Context* c, int type)
{
naRef result;
if(c->nfree[type] == 0)
c->free[type] = naGC_get(&globals->pools[type],
OBJ_CACHE_SZ, &c->nfree[type]);
result = naObj(type, c->free[type][--c->nfree[type]]);
naTempSave(c, result);
return result;
}
</syntaxhighlight>

First, the conditional checks if there's any free memory in the Nasal storage pools for the requested Nasal data type, if there isn't any free memory left, new memory is assigned to the contexts->free[type] pool via naGC_get().

'''Note:''' naGC_get() is the only function which really manages all memory pools and which triggers the GC. Allocations via naNew()* will end up calling naNew() and naNew() ends up calling naGC_get() '''always'''.

For the time being, OBJ_CACHE_SZ can be ignored, it's defined in code.h, line 12: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line12
<syntaxhighlight lang="C">
// Number of objects (per pool per thread) asked for using naGC_get().
// The idea is that contexts can "cache" allocations to prevent thread
// contention on the global pools. But in practice this interacts
// very badly with small subcontext calls, which grab huge numbers of
// cached objects and don't use them, causing far more collections
// than necessary. Just leave it at 1 pending a rework of the
// collector synchronization.
#define OBJ_CACHE_SZ 1
</syntaxhighlight>

The final argument to the naGC_get() function is a pointer to to the context's nfree[type] member which is updated by the function.

Next, a new naRef structure is set up using the allocated naObj memory and the type info:

<syntaxhighlight lang="C">
result = naObj(type, c->free[type][--c->nfree[type]]);
</syntaxhighlight>

<syntaxhighlight lang="C">
naRef naObj(int type, struct naObj* o)
{
naRef r;
SETPTR(r, o);
o->type = type;
return r;
}
</syntaxhighlight>

= The GC interface =

[[File:Nasal-gc.png|thumb|650px|Nasal GC]]

TODO: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line204

* void naGC_init(struct naPool* p, int type);
* struct naObj** naGC_get(struct naPool* p, int n, int* nout);
* void naGC_swapfree(void** target, void* val); (used for vector/hash resizing)
* void naGC_freedead();
* void naiGCMark(naRef r);
* void naiGCMarkHash(naRef h);

= The pool manager =

[[File:NasalNaGetCallgraph.png|thumb|550px|Callgraph for naGC_get()]]

All high level type allocators (naNewString, naNewVector, naNewHash etc) make use of the naNew() call introduced earlier.

naNew() doesn't directly allocate new memory from the heap using naAlloc(), but instead use the naGC_get() helper which manages memory from the global pools (i.e. preallocated memory for each type).

For each native Nasal data type (scalars, vectors, hashes, funcs etc) , there are separate memory pools in globals->pools[n]. The index (n) is one of T_VEC, T_HASH, T_FUNC etc.

The naGC_get() pool "manager" is located in gc.nas line 194: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line194

<syntaxhighlight lang="C">
struct naObj** naGC_get(struct naPool* p, int n, int* nout)
{
struct naObj** result;
naCheckBottleneck();
LOCK();
while(globals->allocCount < 0 || (p->nfree == 0 && p->freetop >= p->freesz)) {
globals->needGC = 1;
bottleneck();
}
if(p->nfree == 0)
newBlock(p, poolsize(p)/8);
n = p->nfree < n ? p->nfree : n;
*nout = n;
p->nfree -= n;
globals->allocCount -= n;
result = (struct naObj**)(p->free + p->nfree);
UNLOCK();
return result;
}
</syntaxhighlight>

As can be seen, the garbage collector itself is triggered by setting the global "needGC" flag to 1 in the globals structure and then calling the bottleneck() function: [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line199].

In line 209, the memory region from the global pool is cast back to a pointer (struct naObj**): https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line209
the "nout" paramter is just there to update c->nfree[type] with the amount of free memory.

In other words, whenever new Nasal types are allocated, new memory from one of the 7 Nasal pools is requested. All of these allocation requests are channeled through naNew() and finally naGC_get(). naGC_get() is the de facto memory manager in Nasal, all memory management is triggered here - new memory block allocations for each pool, as well as garbage collection via the bottleneck() call.

This also means that we basically just need to provide an alternate naGC_get() function, next to the existing one, to add support for alternate GC schemes.

= Disabling the current GC =

The overhead caused by managing the memory pools and constantly scanning the heap (mark/reap) can be examined by modifying the naGC_get() function such that it no longer uses any pool memory, but directly allocates via malloc()/naAlloc() - without ever freeing any memory (i.e. leaking). While the fgfs process will eventually get killed this way, the GC will be basically switched off.

<syntaxhighlight lang="C">
struct naObj** naGC_get(struct naPool* p, int n, int* nout)
{
struct naObj** result;
naCheckBottleneck();
LOCK();
#define LEAKY
#ifndef LEAKY
while(globals->allocCount < 0 || (p->nfree == 0 && p->freetop >= p->freesz)) {
globals->needGC = 1;
bottleneck();
}
if(p->nfree == 0)
newBlock(p, poolsize(p)/8);
n = p->nfree < n ? p->nfree : n;
*nout = n;
p->nfree -= n;
globals->allocCount -= n;
result = (struct naObj**)(p->free + p->nfree);
#else
result = (struct naObj**) naAlloc( naTypeSize(n) );
#endif
UNLOCK();
return result;
}
</syntaxhighlight>

= bottleneck() =

[[File:NasalCheckBottleneckCallerGraph.png|thumb|450px|Callergraph of naCheckBottleneck()]]
[[File:NasalCheckBottleneckCallgraph.png|thumb|400px|Callgraph of naCheckBottleneck()]]

Whenever new memory from one of the global pools is being requested via naGC_get(), naCheckBottleneck() will also be invoked:

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line121

<syntaxhighlight lang="C">
void naCheckBottleneck()
{
if(globals->bottleneck) { LOCK(); bottleneck(); UNLOCK(); }
}
</syntaxhighlight>

This checks if globals->bottleneck is true, and if it is, it makes sure that the bottleneck() function is only invoked after acquiring a lock.

[[File:NasalBottleneckCallgraph.png|thumb|550px|Callgraph of bottleneck()]]

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line99
<syntaxhighlight lang="C">
// Must be called with the main lock. Engages the "bottleneck", where
// all threads will block so that one (the last one to call this
// function) can run alone. This is done for GC, and also to free the
// list of "dead" blocks when it gets full (which is part of GC, if
// you think about it).
static void bottleneck()
{
struct Globals* g = globals;
g->bottleneck = 1;
while(g->bottleneck && g->waitCount < g->nThreads - 1) {
g->waitCount++;
UNLOCK(); naSemDown(g->sem); LOCK();
g->waitCount--;
}
if(g->waitCount >= g->nThreads - 1) {
freeDead();
if(g->needGC) garbageCollect();
if(g->waitCount) naSemUp(g->sem, g->waitCount);
g->bottleneck = 0;
}
}
</syntaxhighlight>

The actual garbage collection takes place in [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line114 line 114] where dead objects from the memory pool are freed, and the garbageCollect() function is called if globals.needGC is true.

= garbageCollect() =

[[File:NasalGarbageCollectCallgraph.png|thumb|550px|Callgraph of garbageCollect()]]

This is the function that does the mark/sweep part using mark() to recursively mark reachable objects, and reap() to collect unreachable objects.

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line35

<syntaxhighlight lang="C">
// Must be called with the big lock!
static void garbageCollect()
{
int i;
struct Context* c;
globals->allocCount = 0;
c = globals->allContexts;
while(c) {
for(i=0; i<NUM_NASAL_TYPES; i++)
c->nfree[i] = 0;
for(i=0; i < c->fTop; i++) {
mark(c->fStack[i].func);
mark(c->fStack[i].locals);
}
for(i=0; i < c->opTop; i++)
mark(c->opStack[i]);
mark(c->dieArg);
marktemps(c);
c = c->nextAll;
}
mark(globals->save);
mark(globals->symbols);
mark(globals->meRef);
mark(globals->argRef);
mark(globals->parentsRef);
// Finally collect all the freed objects
for(i=0; i<NUM_NASAL_TYPES; i++)
reap(&(globals->pools[i]));
// Make enough space for the dead blocks we need to free during
// execution. This works out to 1 spot for every 2 live objects,
// which should be limit the number of bottleneck operations
// without imposing an undue burden of extra "freeable" memory.
if(globals->deadsz < globals->allocCount) {
globals->deadsz = globals->allocCount;
if(globals->deadsz < 256) globals->deadsz = 256;
naFree(globals->deadBlocks);
globals->deadBlocks = naAlloc(sizeof(void*) * globals->deadsz);
}
globals->needGC = 0;
}
</syntaxhighlight>

For each invocation of garbageCollect(), the following takes place:
* For each context:
** The counter for each type-specific pool will be reset to 0 in line 43: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line43
** for each stack frame of the given context, all reachable locals and functions will be marked as reachable in line 45: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line45
** All instructions in the opcode stack will be marked as reachable from top to bottom in line 49: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line49
** mark(die->Arg)
** temporary variables are marked reachable
* root references (constants) are marked reachable in line56: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line56
* foreach Nasal data type:
** unreachable objects are then collected in line 62: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line62
* dead blocks are freed and new memory is allocated in line: 66 https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line66
* the needGC flag is set to 0

= mark() =

[[File:NasalMarkCallgraph.png|thumb|400px|Callgraph of mark()]]

All reachable objects are recursively marked using tagged naRef structures [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line50], so that unreachable objects can be collected (i.e. because the reftag bit is not set) and freed.

TOOD: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line223
<syntaxhighlight lang="C">

</syntaxhighlight>

= reap() =

[[File:NasalReapCallgraph.png|thumb|450px|Callgraph for reap()]]

This is the collector function called by garbageCollect() which also frees elements and allocates new blocks for the specified pool:

<syntaxhighlight lang="C">
// Collects all the unreachable objects into a free list, and
// allocates more space if needed.
static void reap(struct naPool* p)
{
struct Block* b;
int elem, freesz, total = poolsize(p);
freesz = total < MIN_BLOCK_SIZE ? MIN_BLOCK_SIZE : total;
freesz = (3 * freesz / 2) + (globals->nThreads * OBJ_CACHE_SZ);
if(p->freesz < freesz) {
naFree(p->free0);
p->freesz = freesz;
p->free = p->free0 = naAlloc(sizeof(void*) * p->freesz);
}
p->nfree = 0;
p->free = p->free0;
for(b = p->blocks; b; b = b->next)
for(elem=0; elem < b->size; elem++) {
struct naObj* o = (struct naObj*)(b->block + elem * p->elemsz);
if(o->mark == 0)
freeelem(p, o);
o->mark = 0;
}
p->freetop = p->nfree;
// allocs of this type until the next collection
globals->allocCount += total/2;
// Allocate more if necessary (try to keep 25-50% of the objects
// available)
if(p->nfree < total/4) {
int used = total - p->nfree;
int avail = total - used;
int need = used/2 - avail;
if(need > 0)
newBlock(p, need);
}
}
</syntaxhighlight>

=swapfree() =
[[File:NasalGC swapfreeCallgraph.png|thumb|450px|Callgraph of swapfree()]]

= freeelem() =

[[File:NasalFreeelemCallgraph.png|thumb|Callgraph of freeelem()]]

Frees individual elements and adds freed pointers to the globals free list, implemented in gc.c: https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line137
<syntaxhighlight lang="C">
static void freeelem(struct naPool* p, struct naObj* o)
{
// Clean up any intrinsic storage the object might have...
switch(p->type) {
case T_STR: naStr_gcclean ((struct naStr*) o); break;
case T_VEC: naVec_gcclean ((struct naVec*) o); break;
case T_HASH: naiGCHashClean ((struct naHash*) o); break;
case T_CODE: naCode_gcclean ((struct naCode*) o); break;
case T_GHOST: naGhost_gcclean((struct naGhost*)o); break;
}
p->free[p->nfree++] = o; // ...and add it to the free list
}
</syntaxhighlight>

= Type destructors =
Will be called by freelem(), implemented for all native Nasal types:

* strings (T_STR): naStr_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/string.c#line113]
* vectors (T_VEC): naVec_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/vector.c#line22]
* hashes (T_HASH): naiGCHashClean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/hash.c#line221]
* code (T_CODE): naCode_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line126]
* ghosts (T_GHOST): naGhost_gcclean [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/gc.c#line131]

= Contexts =

[[File:NasalContextStruct.png|thumb|500px|Nasal Context structure]]

https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line71
<syntaxhighlight lang="C">
struct Context {

// Stack(s)

struct Frame fStack[MAX_RECURSION];

int fTop;

naRef opStack[MAX_STACK_DEPTH];

int opFrame; // like Frame::bp, but for C functions

int opTop;

int markStack[MAX_MARK_DEPTH];

int markTop;

// Free object lists, cached from the global GC

struct naObj** free[NUM_NASAL_TYPES];

int nfree[NUM_NASAL_TYPES];

// GC-findable reference point for objects that may live on the

// processor ("real") stack during execution. naNew() places them

// here, and clears the array each instruction

struct naObj** temps;

int ntemps;

int tempsz;

// Error handling

jmp_buf jumpHandle;

char error[128];

naRef dieArg;

// Sub-call lists

struct Context* callParent;

struct Context* callChild;

// Linked list pointers in globals

struct Context* nextFree;

struct Context* nextAll;

void* userData;

};
</syntaxhighlight>

= Stack frames =
https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/code.h#line32

= Tagged structures =
https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/data.h#line84

= Core allocations =
All core memory allocation takes place via wrappers in [https://gitorious.org/fg/simgear/blobs/next/simgear/nasal/misc.c#line8 misc.c]:

<syntaxhighlight lang="C">
void naFree(void* m) { free(m); }
void* naAlloc(int n) { return malloc(n); }
void* naRealloc(void* b, int n) { return realloc(b, n); }
void naBZero(void* m, int n) { memset(m, 0, n); }
</syntaxhighlight>

[[Category:Core developer documentation]]
[[Category:Nasal]]

Talk:Project Rembrandt

2012-05-20T08:29:04Z

Xiii: /* feed back on models */

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* <del>The bloom effect is a bit too much IHMO</del>. will it be settable per object ? ''(In my case it was too much because of bad and avoidable interaction between legacy emissiveness and rembrandt lights)''
* SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value. http://www.maison-capestang.com/fg/E-2C/ssao-on-off.png
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

Interesting: If you register an emissive object as transparent, it keeps its colored config. The following works with rembrandt: green emissive opaque object.

<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>screen-bkg</object-name>
</effect>
<animation>
<object-name>screen-bkg</object-name>
<type>material</type>
<emission>
<factor-prop>sim/model/f-14b/controls/VDI/contrast</factor-prop>
<red>0.0</red>
<green>0.7</green>
<blue>0.0</blue>
</emission>
</animation>

And it is realy cool news. But, but.... there are zbuffering issues (I suppose so because some overlaying transparent objects appears and disapear when the view pitch or yaw change).

[[User:Xiii|Xiii]] 03:57, 20 May 2012 (EDT)

Talk:Project Rembrandt

2012-05-20T07:57:46Z

Xiii: /* feed back on models */

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* <del>The bloom effect is a bit too much IHMO</del>. will it be settable per object ? ''(In my case it was too much because of bad and avoidable interaction between legacy emissiveness and rembrandt lights)''
* SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value. http://www.maison-capestang.com/fg/E-2C/ssao-on-off.png
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

Interesting: If you register an emissive object as transparent, it keeps its colored config. The following works with rembrandt: green emissive opaque object.

<effect>
<inherits-from>Effects/model-transparent</inherits-from>
<object-name>screen-bkg</object-name>
</effect>
<animation>
<object-name>screen-bkg</object-name>
<type>material</type>
<emission>
<factor-prop>sim/model/f-14b/controls/VDI/contrast</factor-prop>
<red>0.0</red>
<green>0.7</green>
<blue>0.0</blue>
</emission>
</animation>

And it is realy cool news.

[[User:Xiii|Xiii]] 03:57, 20 May 2012 (EDT)

Talk:Project Rembrandt

2012-05-17T21:44:18Z

Xiii: modeler comments

Hi.

Like I mentioned in my email, I have made modifications to CameraGroup to allow much more camera options in preferences.xml. Currently supporting: multiple cameras & render orders, render to texture, multiple render targets, binding of render target textures for other cameras, floating point textures, post processing & chaining of effects.

So basically I think most your stuff could be handled with this system (though it still has some bugs and seems to cause crashes in libGL...)

Anyways, when you think you have the system running well enough, so that it would be time for cleanup, please give me a message and let's see if this work can be combined. Meanwhile, if you're interested, my git repo is at [https://gitorious.org/~zan/fg/zans-flightgear/commits/newcameras gitorious repository].

What I wonder about your work, is how you handle the separation of geometry, i.e. that the geometry pass does not draw transparent objects like clouds? I was trying to add this to my system, and got it to sort of work (via pre-render callbacks) but it was ugly. I'm going to add an option in preferences.xml to select, which geometry (either render bin numbers or transparent/opaque etc) to render, which would allow multiple lights easily.

[[User:Zan|Zan]] 04:36, 20 December 2011 (EST)
:: Also see [http://flightgear.org/forums/viewtopic.php?f=6&t=13798&p=140379&hilit=#p140299 here] (forum thread).--[[User:Hooray|Hooray]] 07:13, 20 December 2011 (EST)

The cloud and the sky were removed from the main scenegraph (in renderer.cxx) and added as simple group nodes in the lighting camera (the stage before the display stage) before applying the ambient pass. I put banners in CameraGroup so it is easy to spot the different structures for each stage (CameraGroup::BuildGBufferCamera - a bit misnamed now).

Also don't forget most of state attributes are set in terrain-default.eff and model-default.eff

--[[User:Fredb|Fredb]] 16:01, 20 December 2011 (EST)

You write about the transparent objects: ''In a cull callback attached to the Geometry camera, after the scenegraph traversal, the transparent bins are removed from the render stage and saved in a temporary collection.'' I have to tell you, when I made my modifications to the cameras, I was also thinking about deferred shader, and ended up with the exactly same method what you seem to be using! I just never found time to correctly implement it. I'm impressed that we both separately ended up with this same method!
[[User:Zan|Zan]] 15:58, 15 January 2012 (EST)
:So now I know I am on the right track ;-)
:Regards
:--[[User:Fredb|Fredb]] 08:32, 16 January 2012 (EST)

== Models modification log ==
{{cquote|Change KSFO_light.xml to apt-light.xml|Fredb}}
Why that? KSFO_light.xml is a special model, made for KSFO by Don Lavelle. Just like EHAM also has custom light poles. And EDDF. There are quite some actually...

[[User:Gijs|Gijs]] 15:04, 3 January 2012 (EST)

: Hi Gijs. Could you explain in what they are different and why there are only ten of then while there are more than 50 apt-light in KSFO ?
:--[[User:Fredb|Fredb]] 15:30, 3 January 2012 (EST)

:: They are two completely different models. Just compare them in Blender (or whatever editor). The KSFO_light ones match better with the real ones at KSFO (one of the differences is that the KSFO ones are grey/brown, rather than red/white striped). I don't know why only a few are placed, the red/white ones should be replaced (will talk to Jon on IRC in a minute).
:: Now that you're working on spot lights, it's important to realize that we (will) have many light pole models, simply because there are many variants in real life... ;)
:: [[User:Gijs|Gijs]] 17:42, 3 January 2012 (EST)

Because of this: "Add a spot light animation" - testing real lights now?
That would be great!

--[[User:HHS|HHS]] 15:09, 3 January 2012 (EST)

=== feed back on models ===

''Howdy Fred, wonderful work. There are still plenty of thing to do, plenty about which modelers will rant, as usual, but let me tell you how much I appreciate what you have done with rembrandt. Now some <del>rants</del> comments:''

* I worked on the f-14b cockpit and added 3 point lights to enlighten the space. No problem there, I managed (more or less) to keep the light volume inside the cockpit and this wasn't easy, and I linked the lights intensity to the instruments lights slider. the instruments have (since a long time) their own emission (material animation) but they just lose the color, so instead of being red lighted, they are now white. http://www.maison-capestang.com/fg/f-14b/f-14-inside-lighting-20120517.png
* The bloom effect is a bit too much IHMO. will it be settable per object ?
* SSAO is also a bit strong, it would be nice to test several strength on different models before settling a default value. http://www.maison-capestang.com/fg/E-2C/ssao-on-off.png
* No major problems with converting of referencing the transparencies, but the sky is much darker than the terrain horizon when seen through the propellers with transparency (material animation). http://www.maison-capestang.com/fg/E-2C/through-the-propellers.png

[[User:Xiii|Xiii]] 17:44, 17 May 2012 (EDT)

FlightGear Newsletter August 2011

2011-08-28T12:20:22Z

Xiii: /* New Aircraft */ added the Hawkeye

{{newsletter}}
{{TOC_right|limit=2}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome. So if you know about any FlightGear related projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== New FlightGear Version Finally Released ==
On August 17 after a year and a half of hard work, [http://www.flightgear.org/announcements/flightgear-v2-4-0-released/ FlightGear v2.4 has finally been released!] Thanks to the key developers that took the lead to overhaul the FlightGear release plan and create a regular release cycle. Thanks also to each and every developer in every portion of the FlightGear community who have contributed to make FlightGear such a success! [http://www.flightgear.org/download/ Please click here to jump to the download page.]
Starting with the v2.4 release, the development of FlightGear will now follow the [[Release Plan]], which will act as a guideline in upcoming development and regular releases of the FlightGear simulator in the form of a six-month development cycle. In other words, if this Release Plan's suggestions are followed thoroughly, stable releases of the simulator will be created twice a year, on the 17th of February and August.

== FlightGear.org Main Website Updated ==
Along with the [http://www.flightgear.org/announcements/flightgear-v2-4-0-released/ v2.4 release], the [http://www.flightgear.org FlightGear.org] web site has seen a complete overhaul during the month of August. The new website is based on "wordpress" which supports multiple editors and allows for much easier editing and updating of content. One interesting feature of wordpress is the ability to create "posts" and then allow anyone to add their own comments (pending approval.) Newsletter contributors (and anyone else) are invited to create a "post" for the main flightgear.org web site. This is a great way to promote your own project and do so in a context that allows more paragraphs, more detail, and more pictures than can fit in a newsletter article. So please continue to submit newsletter articles, but also please consider developing a longer version for the main web site!

== Development news ==

=== AI/ATC interactions ===
[[File:Ehamrwyblock.png|thumb| Heavily congested taxiways at Schiphol after the 777-200 had been blocking active runway 24 for nearly 4 hours.]]
While the preparations for our upcoming release are still going on, development for the next release has already started. In early august code changes were committed, which allow FlightGear users to interact with an artifically intelligent ATC system. Currently it is possible to request startup clearance, permission for push back, as well as taxi-clearances. A brand new, and highly experimental, ground network visualization system makes it possible to taxi from parking to runway along the route given by ATC. Hold position and resume taxi instructions can be be given in order to avoid collisions with other (AI controlled) aircraft. Hand-off to a tower controller, as well as more interactive take offs, are in the planning stages. The aim is to have all stages of IFR commercial aviation traffic under ATC control before the release of flightgear 2.6.0, which is planned for early 2012.

== Nasal for newbies ==
== New software Tools and Projects ==
=== TerraMaster ===
[http://code.google.com/p/terramaster TerraMaster] is a Java-based application that lets you pick-and-choose which scenery tiles you would like to sync with the FG scenery server. Ideal for those people who prefer to TerraSync preflight rather than inflight.
== FlightGear Addons and Mods ==
== In the Hangar ==
=== New Aircraft ===
[[File:A310-snap.png|thumb| Mahan Air A310-300 over Schiphol.]]
Icecode and Star a few months ago started the development of the [http://wiki.flightgear.org/Airbus_A310-300 Airbus A310-300]. The latest version of the model includes a detailed cockpit and a realistic YAsim FDM. You can view the development progress [http://www.flightgear.org/forums/viewtopic.php?f=4&t=12790 here].

==== TECNAM P.92 ECHO ====
[[File:Tecnam-P92.PNG|200px|thumb| Tecnam-P92.]]
A french team who likes to be called "The Flightgear France patrol" has been working on many aircrafts. It is composed of many specialists in various fields (3D, texture, FDM, nasal, xml, sound...).
The France patrol is proud to offer you a new airplane: the Tecnam-P92. It is probably the best ultralight aircraft available by now in Flightgear. All the instruments, electrical systems and most of the sound are realistically simulated.
You can download this airplane in [http://helijah.free.fr/flightgear/hangar.htm Helijah's hangar] here as well as in the GIT repository.
This team is currently working on other planes and helos, such as the R44, DC3 C-47 and D510. Those aircrafts can also be found in Helijah's hangar and in GIT.

==== GRUMMAN E-2C HAWKEYE ====
[[File:Grumman-E-2C-early-model-20110626.png|200px|thumb| Grumman E-2C Hawkeye.]]
At that time being the bird is in a very early stage of development, but with a little bit of time it could become a very nice carrier based flying ATC, needing (1) a Pilot to stay on station flying flat "8s" against the wind and (2) a skilled Air Controller to "control" the kind of nasty boys one can usually see around the Nimitz. Right now, the model available in Git is very crude (but the Landing gear) and the FDM isn't completely tuned. There is the minimal set of instruments, but no lights and no fancy details in the cockpit yet. Anyway she can already land and take of from a carrier (with day light). This model is coming out of xiii's factory, so be sure it will be over detailed and accurately modeled :-)

=== Updated aircraft ===
=== Liveries ===
== Scenery corner ==
=== Airports ===
I have started a few models on Helgoland with the airport terminal building (EDXH) with the nearby shop and Mobile home park.

It is hard to find photos of local landmarks, or interesting buildings there. Anyone who has visited Helgoland and is prepared to show me their photos could make a valuable contribution here. The church would be a welcome addition.

If you know of any such photos on the internet, which cannot be found by searching with the obvious names, details would also be welcome.

Any help much appreciated.

VicMar

== Aircraft of the month ==

The Bombardier CRJ700 series was reviewed as this week/month's feature aircraft. You can read the full review at our wiki's [[Bombardier CRJ700 series#Aircraft of the Week.2FMonth|Bombardier CRJ700 series]] article.

== Airport of the month ==
== Screenshot of the month ==
== Suggested flights ==
Set your plane at LPLA. This was an emergency landing site for the space shuttle so you will have plenty of room to take off.
We will have to fly an odd pattern. The reason for that: If you don't fly to high you will have some amazing views.

Fly towards and over LPPD. Look out the window and enjoy the view.
Head out towards LPHR. If you feel LPHR coming near, look out the window good, you might have to pull your plane up.

Happy flying!

== Aircraft reviews ==
== Wiki updates ==
== Community news ==

[http://wiki.flightgear.org/User:Longfly Longfly] is very proud and happy to announce the first official release of the "FlightgGear aircraftlist". After eight months of development it contains exactly '''491 different aircrafts''' for FlightGear with screenshots (click on the thumbnails – not everyone is working yet) and download-links.

Because it is a very long list (6127 lines of code and many images) it may take very long to load on some slow computers. So I'll implement five subpages with always 100 planes. There is also a filter, so you can get a better overview of your favorite planes.

The list should be complete but if an aircraft is missing I urge you to report it to me [http://flightgear.bplaced.de/index.php/flugzeugliste/report-a-missing-plane (pm or forum post or mail)] – Thanks! Furthermore feedback, criticism and new ideas are always very welcome in [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10536&start=45 the forum threat].

Here it is: [http://flightgear.bplaced.de/aircraftlist/ '''www.flightgear.bplaced.de/aircraftlist/''']

Have fun exploring it!

=== Stunt Fridays Monthly Video Challenge ===
Stunt Friday, originally a weekly event, is a monthly event where participants compete to record videos of a given stunt, and compete to create the most interesting video and stunt.
The challenge for August involved landing an aircraft at the notoriously infamous former Kai Tak international airport in Hong Kong.
[[User:Alphamedia|Andrew Yokoyama ("kyokoyama")]] won this month's challenge with a crosswind landing of a BAe Concorde in a storm and heavy crosswinds.

* [http://www.youtube.com/watch?v=HnwFduqGHNM&feature=relmfu Announcement Video]
* [http://www.youtube.com/watch?v=rMX_30khbXg Winner Announcement Video]
* [http://www.youtube.com/watch?v=P21z6aFYeA4 Winning Video: BAe Concorde, British Airways]

* [http://www.youtube.com/watch?v=JKxI1wYHBy4 Kyokoyama's First Video: B777, Custom Livery]
* [http://www.youtube.com/watch?v=6x3vQ6O6Iek&feature=player_embedded Ernest1984's Video: B787, House Livery]
* [http://www.youtube.com/watch?v=sXLy5GTuE30 CatchatyouFG's Video: A340, Cathay Pacific Airlines]
* [http://www.youtube.com/watch?v=bRoDzuR2rlo&feature=related Youssef's Video: B777, KLM]
* [http://www.youtube.com/watch?v=OkXr36GglEo&feature=player_embedded abc45's First Video: A320, Philippines Airlines]
* [http://www.youtube.com/watch?v=3fxxyFUyyAU&feature=player_embedded abc45's Second Video: A380, Singapore Airlines]
* [http://s979.photobucket.com/albums/ae271/MTshoot/?action=view&current=KaiTak13.mp4 E-Savageair's Video: B747, Cathay Pacific Airlines]

=== FlightGear on YouTube ===
=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== And finally ... ==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

== Did you know==

{{Template:Newsletternav}}

File:Grumman-E-2C-early-model-20110626.png

2011-08-28T12:02:15Z

Xiii:

Grumman A-6E

2011-08-06T13:11:24Z

Xiii: /* Operating Instructions */ remove next section title, will come latter

{{infobox Aircraft
|image =A-6E.jpg
|caption = The "Intruder"
|name =Grumman A-6E Intruder
|type =Attack aircraft
|authors =Alexis Bory
|fdm =YASim
|status =Beta
|fgname =A-6E
}}

The Grumman A-6 Intruder is available for FlightGear, and is capable of air-to-air refueling and landing on the carrier in that version. It features a high-quality 3D cockpit, avionics, and exterior model.

The FG model is modeled with [[Tactical Air Navigation]]

== About the aircraft ==
The '''A-6 Intruder''' is an American twin jet-engine, mid-wing attack aircraft built by Grumman Aerospace. In service between 1963 and 1997, the Intruder was designed as an all-weather replacement for the piston-engined A-1 Skyraider medium attack aircraft. A specialized electronic warfare derivative, the EA-6B Prowler, remains in service as of May 2008. As the A-6 was slated for retirement, its precision strike mission was taken over by the now retired F-14 Tomcat equipped with LANTIRN, which has subsequently passed on the role to the F/A-18E/F Super Hornet.

An A-6E Intruder is on display at the [[National Air and Space Museum]].

== Aircraft help ==
{| class="prettytable"
!Key
!Function
|-
|c
|Canopy open/close command
|-
|C
|Catapult launch command
|-
|k/j
|Air Brakes open/close
|-
|L
|Carrier Launch-bar engage
|-
|o/O
|Hook up/down
|-
|f/F
|Wing Fold up/down
|}

== Operating Instructions ==

=== Landing ===

==== Carrier Landing pattern ====
[[File:A-6E-carrier-landing-pattern-ng.png]]

== Development status/Issues/Todo ==
'''Outside:'''
* Fix the relatively massive "hiccup" in elevator

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

== External links ==
* [http://en.wikipedia.org/wiki/A-6_Intruder Wikipedia's article on the A-6 Intruder]
* [http://croo.murgl.org/fgfs/A-6E/A-6E-A-6E-20071101.tgz Download the development version of the A-6E (11/01/2007)]
* [http://www.youtube.com/watch?v=EKELqBGVsqw A-6 flight - Dynamic water effect in FlightGear] ([http://www.youtube.com/watch?v=EKELqBGVsqw&hd=1 720p]) - August 18, 2009

{{Grumman}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Grumman A-6E

2011-08-06T12:59:01Z

Xiii: added cairrier landing instruction

{{infobox Aircraft
|image =A-6E.jpg
|caption = The "Intruder"
|name =Grumman A-6E Intruder
|type =Attack aircraft
|authors =Alexis Bory
|fdm =YASim
|status =Beta
|fgname =A-6E
}}

The Grumman A-6 Intruder is available for FlightGear, and is capable of air-to-air refueling and landing on the carrier in that version. It features a high-quality 3D cockpit, avionics, and exterior model.

The FG model is modeled with [[Tactical Air Navigation]]

== About the aircraft ==
The '''A-6 Intruder''' is an American twin jet-engine, mid-wing attack aircraft built by Grumman Aerospace. In service between 1963 and 1997, the Intruder was designed as an all-weather replacement for the piston-engined A-1 Skyraider medium attack aircraft. A specialized electronic warfare derivative, the EA-6B Prowler, remains in service as of May 2008. As the A-6 was slated for retirement, its precision strike mission was taken over by the now retired F-14 Tomcat equipped with LANTIRN, which has subsequently passed on the role to the F/A-18E/F Super Hornet.

An A-6E Intruder is on display at the [[National Air and Space Museum]].

== Aircraft help ==
{| class="prettytable"
!Key
!Function
|-
|c
|Canopy open/close command
|-
|C
|Catapult launch command
|-
|k/j
|Air Brakes open/close
|-
|L
|Carrier Launch-bar engage
|-
|o/O
|Hook up/down
|-
|f/F
|Wing Fold up/down
|}

== Operating Instructions ==

=== Landing ===

==== Carrier Landing pattern ====
[[File:A-6E-carrier-landing-pattern-ng.png]]

==== Carrier Landing Speed ====

== Development status/Issues/Todo ==
'''Outside:'''
* Fix the relatively massive "hiccup" in elevator

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

== External links ==
* [http://en.wikipedia.org/wiki/A-6_Intruder Wikipedia's article on the A-6 Intruder]
* [http://croo.murgl.org/fgfs/A-6E/A-6E-A-6E-20071101.tgz Download the development version of the A-6E (11/01/2007)]
* [http://www.youtube.com/watch?v=EKELqBGVsqw A-6 flight - Dynamic water effect in FlightGear] ([http://www.youtube.com/watch?v=EKELqBGVsqw&hd=1 720p]) - August 18, 2009

{{Grumman}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

File:A-6E-carrier-landing-pattern-ng.png

2011-08-06T12:57:07Z

Xiii: A-6 Intruder standard carrier landing pattern

A-6 Intruder standard carrier landing pattern

Grumman F-14 Tomcat

2011-05-07T08:31:17Z

Xiii: /* Weapons operation */

{{infobox Aircraft
|image =F-14.jpg
|name =F-14 Tomcat
|type =Interceptor/multi-role Fighter aircraft
|livery =U.S. Navy
|authors =Enrique Laso, Alexis Bory (cockpit)
|status =Production
|fdm =YASim
|3dcockpit = √
|carrier = √
|fgname = f-14b
}}
The '''Grumman F-14 Tomcat''' is a supersonic, twin-engine, two-seat, variable geometry wing [[aircraft]]. The F-14 was the United States Navy's primary maritime air superiority fighter, fleet defense interceptor and tactical reconnaissance platform from 1974 to 2006. It later performed precision strike missions once it was integrated with the Low Altitude Navigation and Targeting Infrared for Night [http://en.wikipedia.org/wiki/LANTIRN LANTIRN] system. The F-14 was developed after the collapse of the [http://en.wikipedia.org/wiki/F-111B F-111B] project, and was the first of the American teen-series fighters which were designed incorporating the experience of air combat in Vietnam against MiGs.

It entered service in 1972 with the U.S. Navy, replacing the [[McDonnell F4 Phantom II]]. It was later exported to the former Imperial Iranian Air Force in 1976, during a time when the US still had good relations with Iran. It was retired from the active U.S. Navy fleet on 22 September 2006, having been replaced by the [[F/A-18 Hornet|F/A-18E/F Super Hornet]]. As of 2007, it remains in service only with the Islamic Republic of Iran Air Force.

== Keyboard Controls ==
=== Flight Controls ===
{| class="prettytable"
|Home
|Increase elevator trim
|-
|End
|Decrease elevator trim
|-
|] or f
|Lower flaps
|-
|[ or F
|Raise flaps
|-
|s
|Increase speed brakes
|-
|S
|Decrease speed brakes
|-
|Ctrl-b
|Toggle speed brakes
|-
|k
|Increase speed brakes
|-
|j
|Decrease speed brakes
|-
|}

[[File:F-14_cockpit.jpg|thumb|270px|Cockpit of the F-14.]]
[[File:SunsetF-14.png|270px|thumb|right|A nice scene with the F-14.]]

=== Automatic Flight Controls ===
{| class="prettytable"
|a
|Toggle APC (Landing Automatic Power Control)
|-
|Ctrl-d
|Toggle DLC (Landing Direct Lift Control)
|-
|d
|DLC increase
|-
|D
|DLC decrease
|-
|Ctrl-t
|Toggle [http://en.wikipedia.org/wiki/Aircraft_flight_control_systems AFCS] (Defaut Attitude Mode)
|-
|Ctrl-a
|Enable AFCS Altitude Mode
|-
|*
|Engage AFCS Altitude Mode
|-
|Ctrl-h
|Enable AFCS Heading Mode
|-
|Ctrl-s
|Toggle ground spoilers armed
|}

=== HSD - radar and RWR ===
{| class="prettytable"
|h
|Cycles through HSD modes: radar - compas - ECM (RWR)
|-
|E
|Decrease Radar Range
|-
|R
|Increase Radar Range
|-
|Ctrl-r
|Toggles Radar Standby Mode. In standby mode the radar doesn't emit and the "STAND BY" words are displayed on the HSD screen when in TID mode. (FIXME replaced by "q" in git)
|}

=== Carrier operations ===
{| class="prettytable"
|O
|Lower the hook
|-
|o
|Raise the hook
|-
|L
|Engage launch bar
|-
|C
|Release catapult
|-
|}
=== Weapons ===
{| class="prettytable"
|Ctrl-w
|Cycle through MasterArm modes.
|-
|w
|Cycle Stick Weapon Mode Selector
|-
|Ctrl-m
|Toggle AIM-9 selection
|-
|e
|Trigger M61A1 Vulcan or AIM-9s
|-
|}
=== Miscellaneous ===
{| class="prettytable"
|c
|Toggle canopy and access ladder
|-
|u
|Toggle refuelling probe
|-
|w
|Cycle armament selector
|-
|Ctrl-o
|Toggle oversweep (on ground only, otherwise sweep is automatic)
|-
|Ctrl-v
|Toggle between RIO (Radar Intercept Officer) and pilot view
|-
|}

== Aircraft help ==
=== On Shore Takeoff ===
* With wings on over sweep position (parking position) the elevator command is inhibited... just in case...
* Check air brake in.
* Fuel level: The Flightgear F-14 has a '''10% fuel''' level and no external load '''at start up'''. This means the aircraft will be very light and have a strong tendency to raise the nose when accelerating on the runway. With less weight on the nose wheel, the nose wheel steering loose its efficiency. If the pilot use afterburners for take off, the loose of nose wheel steering efficiency is increased (afterburners are not necessary for take off). '''Set a suitable fuel level before take off.'''
* Flaps: Set full flaps.
* Elevators: The pilot will need to maintain a correct (leveled) attitude using the stick. Push the stick forward to prevent nose pitching up at the beginning of the take off run, release slightly as speed increase, pull smoothly when reaching rotation speed (150kts).
* Rudder: Currently the FDM use a small rudder rate of move to damp some nasty oscillations when the rudder is not moved enough smoothly. '''If not anticipated''', this delay will cause overshooting the desired rudder effect, then a strong counter action on the rudder will be applied by the pilot on the rudder with again an overshoot... That's a typical [http://en.wikipedia.org/wiki/Pilot-induced_oscillation pilot-induced oscillation]. To avoid this set a small amount of rudder, wait for the effect, see if it's enough, then add a small amount of rudder again if needed... when doing so the pilot will prefer increasing the power smoothly. Now the aircraft will quickly gain speed while covering the runway and the rudder effect will increase, thus decreasing the needed delay and the amount of pressure on the stick to match the desired effect.

=== Autopilot Operation ===
* The main mode is '''Attitude Hold Mode''', '''Ctrl-t'''. Other Modes need this main mode activated before being selected. Switching off '''Attitude Mode''' disables all other modes . When in '''Attitude Mode''', the autopilot disengages whenever a certain pressure is put on the stick, and it reengages when the stick is back in the center position . '''Attitude Hold Mode''' will hold pitch attitudes up to plus or minus 30 degrees, and bank angles up to plus or minus 60 degrees.
* It shall be switched off for aerobatics and inverted flight .

==== Autopilot Altitude Mode ====
* Once in the Attitude Mode, you can select '''Altitude Mode''' by hitting '''Ctrl-a''', then the '''AP REF''' indicator, (left of the '''VDI''') will illuminate, when at the desired altitude using normal stick control, engage by hitting '''*''', (asterisk) . The autopilot will then maintain your altitude.
'''CAUTION''' - at high speeds, it is imperative to stabilize your aircraft prior to engaging Altitude Mode !

==== Autopilot Heading Mode ====
* Once in the Attitude Mode, you can select '''Heading Mode''' by hitting '''Ctrl-h''' . After maneuvering the aircraft into the desired reference heading, release the control stick at a bank angle of less than 5 degrees . The autopilot will then hold the aircraft on the selected heading.

* Autopilot needs '''SAS''' channels to be engaged, which is the default . '''SAS''' Pitch and Roll channels may be disengaged by actuating switches located on the '''AFCS''' ('''Automatic/Analog Flight Control System''') panel .[[File:F-14b-sas-switches.png|thumb|270px|SAS Panel.]]

=== Landing Automatic Power Control, (APC) Operation ===
* The '''APC''' is a closed loop system that automatically regulates basic engine thrust to maintain the aircraft at an optimum approach angle of attack for landing .
* Prior to engage '''APC''', gear handle must be down with weight off wheels, and the throttles must be set between 98 percent rpm and 68 percent rpm, (as shown on the panel gauges).
* Type '''a''' to toggle the '''APC on/off'''. APC is also disengaged by setting the throttles to MIL, (98 percent rpm) or idle, (68 percent rpm) or raising the landing gear handle or when weight on the wheels .
* When disengaged the '''AUTO THROT''' caution light, (on the left side of the HUD) illuminates for 10 seconds .

=== Landing Direct Lift Control, (DLC) Operation ===
* During landing approaches, the spoilers and horizontal stabilizers can be controlled simultaneously to provide glidepath correction without changing power setting or angle of attack.

=== Ground Spoilers Operation ===
* Ground spoilers (that is [http://en.wikipedia.org/wiki/Elevon elevons] used as air-brake ) provide additional drag immediately after the touch down. Before the landing, arm the ground spoilers by hitting '''Ctrl-s''' . After the aircraft hits the runway, pull the throttle to idle, then the spoilers (elevons) get fully deployed.

=== Weapons operation ===

At the moment, only the gun and the AIM-9s are operational, others ordinances are displayed under the wing, their weight is correct but they aren't usable.

You must have the latest F-14B package from [[Git]] for weapons operations.

* '''Gun:''' At startup, the ammunition store is filled with 675 round. It's not possible to refill without quiting FG. To fire the M61A1 Vulcan:
** Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available (:AHa). Having the HUD in this mode is not mandatory though there won't be any symbolics available for the gun in other HD modes.
** Select Gun mode with the Stick Weapon Mode Selector (w). A pipper, the G symbol with a number showing approximately the remaining rounds x 100 and a closure rate scale are displayed in the HUD. The closure rate scale is active only if a target is locked by the radar with TWS AUTO mode (diamond on the HUD).
** Switch Master Arm on, the X on the G symbol means Master Arm off or in training mode.
** Press e to fire the gun.

* '''Sidewinders:''' Crudely modeled on AIM-9L available data.
** Select a weapons set using the menu: Tomcat Controls > Fuel and Stores: "FAD light" has 4 sidewinders, "FAD", "FAD heavy" and "Bombcat" have 2 of them.
** Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available (:AHa).
** Select SW mode with the Stick Weapon Mode Selector (w).
** Switch to the back seater's view (Ctrl-v).
** Select pylons 1 and 8, down position, on the Armament panel, on RIO's right console. A shortcut toggles these two switches so you can select or deselect all AIM-9 in one keyboard stroke (Ctrl-m) without leaving pilot's view.
** Switch back to the pilot's view (Ctrl-v).
** Switch Master Arm on, you ear the search signal of the seeker head, a low volume buzz sound.
** Now prior to be fired, the AIM-9 must have a lock on a target. For the time being only Multiplayers and AI tankers can be locked. The minimal lock distance is 10 NM, the target must be aproximately inside a 80° cone centered on datum line. When locked, the signal buzz volume becomes louder. For best results try to shoot (e) at a 3 to 6 NM range and with the target centered on the aircraft velocity vector. The missile will explode at the smaller distance possible. However if this distance is above 70 meters, it will continue its trajectory without guidance.

== Pilot's Cockpit ==
[[File:F-14b-pilots-display-control-panel.jpg|thumb|270px|Pilot's Display Control Panel.]]
=== Displays Control Panel ===
* The Display Control Panel is located on the right side of the pilot's main panel, under the Hook lever. The '''3 botom switches''' respectively turn the '''VDI''', '''HUD''' and '''HSD''' displays '''on/off'''. The '''HSD MODE''' switch is also available, it selects '''NAV''' or '''TID''' or '''ECM''' mode. This can also be achieved by cycling through these 3 modes with the "'''h'''" key. (''Note: the '''NAV MODE''' push buttons - '''TO''', '''CRUISE''', '''A/A''', '''A/G''', '''LDG''' - are not operational yet.'')
** '''VDI: Vertical Display Indicator'''. Shows the aircraft attitude in roll and pitch, with an artifitial horizon and magnetic heading.
** '''HUD: Head UP Display'''.
** '''HSD: Horizontal Situation Display'''. HSD shows either:
*** in '''NAV''' mode: compas with navigation indications,
*** in '''TID''' mode (Tactical Information Display): an horizontal representation of the tactical situation (that is information provided by the RIO from what he sees in his radar displays).
*** in '''ECM''' mode: a representation of radar threats around the aircraft.

=== VHF ===
* Located on the RIO's left console, 3 bands: 30-88 MHz, 108-174 MHz, 225-400 MHz. Modes '''TR''' and '''TR-G''' set '''COMM1'''. Mode '''DF''' sets '''NAV1''', that is '''Direction Finder''' displayed with the single needle in both '''BDHIs''' (Bearing, Distance, Heading Indicator) . You have Comm *or* DF. Storing frequencies (up to 20 channels) '''a - PRESET''' select the desired channel, '''b - READ''' tune the desired frequency, '''c - LOAD''' stores the frequency in the previously selected channel.

=== UHF ===
* Located on the pilot's left console, 225-400 Mhz. ADF is not enabled on this radio.

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
=== Links ===
* http://en.wikipedia.org/wiki/F-14 - F-14 Tomcat
* http://www.globalsecurity.org/military/systems/aircraft/f-14.htm - F-14 Tomcat
* http://www.fas.org/programs/ssp/man/uswpns/air/fighter/f14.html - F-14 Tomcat
* http://www.anft.net/f-14/f14-specification.htm - Home of M.A.T.S.
* http://www.navyair.com/LSO_NATOPS_Manual.pdf - NATOPS LANDING SIGNAL OFFICER MANUAL

{{Grumman}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]

Fairchild Republic A-10 Thunderbolt II

2010-12-18T21:19:21Z

Xiii: /* External links */ - removed obsolete external link

{{infobox Aircraft
|image =A-10.jpg
|caption = The "Warthog"
|name =A-10 Thunderbolt II
|type =Military Aircraft
|authors =Lee Elliott, Alexis Bory
|fdm =YASim
|status =Beta
|fgname =A-10
|download =http://croo.murgl.org/fgfs/index.html
}}
The [[FlightGear]] '''Fairchild A-10 Thunderbolt II''' (aka '''Warthog''') offers a wide variety of features and controls. Special features include the ability to simulate ordnance use, and a detailed 3D textured cockpit. Many of the A-10's flight systems are modeled as well, such as support for [[Tactical Air Navigation]] (TACAN).

==About the aircraft==
"This is Fairchild-Republic A-10, also named Warthog. It's a U.S. single-seat, twin-engine, very robust jet aircraft designed for ground attack."

== User's Manual ==
In the current version, the aircraft simulation begins with the aircraft powered down.

The electrical power systems and the [[APU]]'s operation are simulated to a large extent. [[Howto: Air-Air Refueling|Air to air refueling]] is also implemented.

The navigation instruments are [[TACAN]], [[ILS]] and also a [[VHF]] so you can have homing on a [[VOR]] station.

Several external loads are available and the [[HUD]] provides a [[CCIP]] (Continuous Computed Impact Point).

=== Electrical power with APU starting procedure ===
[[Image:A-10-electrical-power-control-panel.jpg|thumb|Electrical control panel]]
At FlightGear startup, both electrical power and [[APU]] are shut down and there is no external power supplied.

Everything is asleep...

You, might see, early on, some needles spinning back on the engines gauges panel and the [[VSI]]... this is only a software initialization artifact.

So, look at the right console, there is a panel with 6 switches, that's the Main Electrical Control Panel. Hit Ctrl-c and you will have a view of where to click...

Let's connect the battery: switch on the battery switch. A few indicators should light up, but not all of them. Now with the battery connected you can start the [[APU]].

The [[APU]] start/stop switch is located near the throttle on the left console. Switch it on. Now check the [[APU]]'s tachometer and EGT on the engine gauge panel.

If the [[APU]] has started successfuly you should see the EGT (Exhaust Gas Temperature) rapidly climb to 800/900°C and then stabilize when the RPMs reach 60%.

[[Image:A-10-throttle-engine-start.jpg|thumb|Throttle, engines operation and APU panel]]

Now the [[APU]] has sufficient RPMs to provide electrical power through its generator. So let's turn on the [[APU]] generator. This one is on the main electrical control panel, upper left corner of the electrical control panel, right console again.

With the [[APU]] generator powered up most of the instruments receive electrical power and now the [[AOA]] indexer lights up and the [[HSI]] (the compass) and ADI (artificial horizon) look much better.

At 85% RPM the [[APU]] supplies enough bleed air to start the engines.

[[Image:engine-gauges.jpg|thumb|APU running, Engines gauges at stop.]]

=== Engines starting procedure ===
Now that we have minimum electrical power and bleed air supplied by the APU, starting the engines is straight forward.

Just click on one of the throttle rails (Ctrl-c to see them), the throttle will move from stop to idle and the engine start. Wait for the starting cycle light to turn off, turn on the corresponding generator and repeat with the second engine.

Now the complete electrical circuit is powered and you can stop the APU to save some fuel. It wont be useful anymore. (This could change with future development of engines failures...)

=== Fuel System ===
FlightGear A-10 starts with all internal tanks full.

2 wing tanks (left and right), 2 fuselage tanks: left main (aft) linked to left system and right main (forward) linked to right system, up to 3 external tanks (2 wings and 1 fuselage).

Normally the left wing and left main tanks feed the left engine and the APU. The right wing and right main tanks feed the right engine. The two feed lines can be interconnected by opening the cross feed valve ('''E''' switch).

The wing boost pumps ('''G''' switch) supply the respective engines until the wing tanks are empty, then the wing boost pumps automatically shut off. The main boost pumps then supply the respective engines with the remainder fuel in main tanks.

In case of a wing tank boost pump failure, the wing tank fuel will gravity feed its respective main tank if the main tank fuel level is below 600 lbs. Check valves prevent reverse fuel flow from the main tanks to the wing tanks.

In case of a main tank boost pump failure, the affected engine will suction-feed from the affected tank for all power setting up to an altitude of nearly 10,000 feet.

Unequal fuel level between left (aft) main and right (forward) main tank (imbalance superior 750 lbs) will cause a longitudinal CG shift that may exceed allowable limits. In this case, opening the valve "tank gate" create a link between the two main tanks.

Fuel from the external tanks is transfered to the wing or main tanks by pressure from the bleed air system. Wing tanks can be topped when the fuel level is below 1590 lbs.
Main tanks can be topped when the fuel level is below 3034 lbs.
The cycling is repeated until fuel is depleted from the external wing tanks first, and external fuselage tank secondly.

For negative G flight, collector tanks will supply the engine with sufficient fuel for 10 seconds operation at MAX power.

With fully loaded fuel tanks and a full load of armament, the A-10 is heavy--about 50,000 pounds. At this weight the plane is quite difficult to fly. Symptoms you would notice are difficult to take off, difficulty gaining altitude, difficult to maneuver without triggering stall warnings or actual stalls.

To avoid these problems, if you choose to equip the plane with full armament you may wish to fill the tanks only half full or so--the plane becomes much easier to fly and half fuel is still enough for a reasonably long flight.

[[Image:A-10-fuel-control-doc.jpg|thumb|Fuel Control panel.]]

The '''Fuel Control panel''' is located on the forward part of left console. 1 lever, 4 push buttons and 8 switches are functional.

(<b>A</b>) Fill Disable buttons, left and right wings tanks. Here fill disabled (button up showing red stripe). Refuel disabled for the wings tanks.

(<b>B</b>) Fill Disable buttons, left and right main tanks (practically forward and aft fuselage tanks). Here fill enabled (button down hidding red stripe). Refuel enabled for the main tanks.

(<b>C</b>) Refuel Receiver Door lever.

(<b>D</b>) External Tanks switches, Wings and Fuselage. Set to OFF to un-pressurize external tanks

(<b>E</b>) Cross Feed switch, allow any operating boost pump to feed both engines.

(<b>F</b>) Tank Gate switch, open a valve linking the left (aft) and right (forward) main fuel tanks.

(<b>G</b>) .

(<b>H</b>) .

=== HUD ===
[[Image:A-10-hud-control-panel.jpg|thumb|HUD Control panel]]

The Head Up Display is turned off by default at aircraft startup. To turn it on electrical power on at least one of the three generator is needed as it isn't wired to the battery.

The '''HUD Control panel''' is located on the upper left corner of the main instrument panel. Three knobs are functional.

(<b>A</b>) Mode Selector Switch: OFF, TEST (standard display), NAV (standard display), CCIP (standard display + Countinuous Computed Impact Point), CCRP (standard display), EXP (standard display), STBY (standard display). Actually you will mostly use NAV and CCIP as other modes are not modeled yet. See later in Weapons System about reticles use.

(<b>B</b>) INTEN knob: Adjust the HUD luminosity.

(<b>C</b>) DEPR knob: Changes the vertical position of the primary aiming reticle in the HUD, There is a digital index in the HUD showing its position, range from -1.00 to 1.00 followed by the letter "D".

'''HUD Symbology:'''

[[Image:A-10-hud-symbology.jpg|thumb|HUD Symbology]]

(<b>D</b>) Pitch ladder.

(<b>E</b>) Indicated Air Speed, Kts.

(<b>F</b>) Primary Aiming Reticle.

(<b>G</b>) Horizon Line

(<b>H</b>) Primary Aiming Reticle Digital index.

(<b>I</b>) Magnetic Heading Tape.

(<b>J</b>) Indicated Altitude in feet (ASL).

(<b>K</b>) Radar Altitude in feet (AGL) followed by letter "R".

(<b>I</b>) Aircraft Pitch in degrees, boxed.

(<b>M</b>) Total Velocity Vector indicator.

(<b>N</b>) Pointer showing the rudders deflection.

=== Weapons system ===
[[Image:A-10-arm-1.jpg|thumb|Armament panel]]
Be sure to have energy before trying to use the armament panel. The gun's rounds counter (<b>A</b>) should be lighted in blue and the HUD should be active.

There is actually 2 AIM-9 and the gun.

First of all push up the Master Switch to ARM (<b>B</b>).

For the gun, push up the Gun Rate Switch to HI (right of the rounds counter). You should have on the left side of the main panel a red light indicating 'Gun Ready'. Press key 'e' on the keyboard to fire the gun.

For AIM-9, turn (<b>C</b>) the AIM-9 Mode Knob to SEL (click on the right side of the knob). Now a big circle appears on the HUD symbology, that the searching aera of the AIM-9. Now select Pylon #11, you should ear the seeker sound. This sound is audible only when an AIM-9 is available, selected and searching. Press key ',' to fire the AIM-9.

(In Flightgear, the key ',' is usaly used for left brake, in the A-10 a nasal script intercepts the binding for weapons release, this is not a definitive solution).

You can also choose to fly without the AIM-9s ans the ECM pod, press Tab or Ctrl-I on the keyboard to display the config menu.

== External links ==
* [http://croo.murgl.org/fgfs/AG-demo/index.html A-10 Ground bombing demo--tanks on a bombing range in Nevada]
* [http://brenthugh.com/flightgear/Sun_Valley_Tank_Invasion1.zip Several ground bombing scenarios suitable for the A-10, involving moving and static tank formations, explodable M1 Abrams tanks, etc.]

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
* [[FlightGear 1.0 default aircraft]]

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]
[[Fr:Fairchild A-10]]]

Grumman F-14 Tomcat

2010-12-13T22:44:10Z

Xiii: /* HSD - radar and RWR */

{{infobox Aircraft
|image =F-14.jpg
|name =F-14 Tomcat
|type =Interceptor/multi-role Fighter aircraft
|livery =U.S. Navy
|authors =Enrique Laso, Alexis Bory (cockpit)
|status =Production
|fdm =YASim
|3dcockpit = √
|carrier = √
|fgname = f-14b
}}
The '''Grumman F-14 Tomcat''' is a supersonic, twin-engine, two-seat, variable geometry wing [[aircraft]]. The F-14 was the United States Navy's primary maritime air superiority fighter, fleet defense interceptor and tactical reconnaissance platform from 1974 to 2006. It later performed precision strike missions once it was integrated with the Low Altitude Navigation and Targeting Infrared for Night [http://en.wikipedia.org/wiki/LANTIRN LANTIRN] system. The F-14 was developed after the collapse of the [http://en.wikipedia.org/wiki/F-111B F-111B] project, and was the first of the American teen-series fighters which were designed incorporating the experience of air combat in Vietnam against MiGs.

It entered service in 1972 with the U.S. Navy, replacing the [[McDonnell F4 Phantom II]]. It was later exported to the former Imperial Iranian Air Force in 1976, during a time when the US still had good relations with Iran. It was retired from the active U.S. Navy fleet on 22 September 2006, having been replaced by the [[F/A-18 Hornet|F/A-18E/F Super Hornet]]. As of 2007, it remains in service only with the Islamic Republic of Iran Air Force.

==Keyboard Controls==
===Flight Controls===
{| class="prettytable"
|Home
|Increase elevator trim
|-
|End
|Decrease elevator trim
|-
|] or f
|Lower flaps
|-
|[ or F
|Raise flaps
|-
|s
|Increase speed brakes
|-
|S
|Decrease speed brakes
|-
|Ctrl-b
|Toggle speed brakes
|-
|k
|Increase speed brakes
|-
|j
|Decrease speed brakes
|-
|}

[[Image:F-14_cockpit.jpg|thumb|270px|Cockpit of the F-14.]]
[[File:SunsetF-14.png|270px|thumb|right|A nice scene with the F-14.]]

===Automatic Flight Controls===
{| class="prettytable"
|a
|Toggle APC (Landing Automatic Power Control)
|-
|Ctrl-d
|Toggle DLC (Landing Direct Lift Control)
|-
|d
|DLC increase
|-
|D
|DLC decrease
|-
|Ctrl-t
|Toggle [http://en.wikipedia.org/wiki/Aircraft_flight_control_systems AFCS] (Defaut Attitude Mode)
|-
|Ctrl-a
|Enable AFCS Altitude Mode
|-
|*
|Engage AFCS Altitude Mode
|-
|Ctrl-h
|Enable AFCS Heading Mode
|-
|Ctrl-s
|Toggle ground spoilers armed
|}

===HSD - radar and RWR===
{| class="prettytable"
|h
|Cycles through HSD modes: radar - compas - ECM (RWR)
|-
|E
|Decrease Radar Range
|-
|R
|Increase Radar Range
|-
|Ctrl-r
|Toggles Radar Standby Mode. In standby mode the radar doesn't emit and the "STAND BY" words are displayed on the HSD screen when in TID mode. (FIXME replaced by "q" in git)
|}

===Carrier operations===
{| class="prettytable"
|O
|Lower the hook
|-
|o
|Raise the hook
|-
|L
|Engage launch bar
|-
|C
|Release catapult
|-
|}
===Weapons===
{| class="prettytable"
|Ctrl-w
|Cycle through MasterArm modes.
|-
|w
|Cycle Stick Weapon Mode Selector
|-
|Ctrl-m
|Toggle AIM-9 selection
|-
|e
|Trigger M61A1 Vulcan or AIM-9s
|-
|}
===Miscellaneous===
{| class="prettytable"
|c
|Toggle canopy and access ladder
|-
|u
|Toggle refuelling probe
|-
|w
|Cycle armament selector
|-
|Ctrl-o
|Toggle oversweep (on ground only, otherwise sweep is automatic)
|-
|Ctrl-v
|Toggle between RIO (Radar Intercept Officer) and pilot view
|-
|}

==Aircraft help==
===On Shore Takeoff===
* With wings on over sweep position (parking position) the elevator command is inhibited... just in case...
* Check air brake in.
* Fuel level: The Flightgear F-14 has a '''10% fuel''' level and no external load '''at start up'''. This means the aircraft will be very light and have a strong tendency to raise the nose when accelerating on the runway. With less weight on the nose wheel, the nose wheel steering loose its efficiency. If the pilot use afterburners for take off, the loose of nose wheel steering efficiency is increased (afterburners are not necessary for take off). '''Set a suitable fuel level before take off.'''
* Flaps: Set full flaps.
* Elevators: The pilot will need to maintain a correct (leveled) attitude using the stick. Push the stick forward to prevent nose pitching up at the beginning of the take off run, release slightly as speed increase, pull smoothly when reaching rotation speed (150kts).
* Rudder: Currently the FDM use a small rudder rate of move to damp some nasty oscillations when the rudder is not moved enough smoothly. '''If not anticipated''', this delay will cause overshooting the desired rudder effect, then a strong counter action on the rudder will be applied by the pilot on the rudder with again an overshoot... That's a typical [http://en.wikipedia.org/wiki/Pilot-induced_oscillation pilot-induced oscillation]. To avoid this set a small amount of rudder, wait for the effect, see if it's enough, then add a small amount of rudder again if needed... when doing so the pilot will prefer increasing the power smoothly. Now the aircraft will quickly gain speed while covering the runway and the rudder effect will increase, thus decreasing the needed delay and the amount of pressure on the stick to match the desired effect.

===Autopilot Operation===
* The main mode is '''Attitude Hold Mode''', '''Ctrl-t'''. Other Modes need this main mode activated before being selected. Switching off '''Attitude Mode''' disables all other modes . When in '''Attitude Mode''', the autopilot disengages whenever a certain pressure is put on the stick, and it reengages when the stick is back in the center position . '''Attitude Hold Mode''' will hold pitch attitudes up to plus or minus 30 degrees, and bank angles up to plus or minus 60 degrees.
* It shall be switched off for aerobatics and inverted flight .

====Autopilot Altitude Mode====
* Once in the Attitude Mode, you can select '''Altitude Mode''' by hitting '''Ctrl-a''', then the '''AP REF''' indicator, (left of the '''VDI''') will illuminate, when at the desired altitude using normal stick control, engage by hitting '''*''', (asterisk) . The autopilot will then maintain your altitude.
'''CAUTION''' - at high speeds, it is imperative to stabilize your aircraft prior to engaging Altitude Mode !

====Autopilot Heading Mode====
* Once in the Attitude Mode, you can select '''Heading Mode''' by hitting '''Ctrl-h''' . After maneuvering the aircraft into the desired reference heading, release the control stick at a bank angle of less than 5 degrees . The autopilot will then hold the aircraft on the selected heading.

* Autopilot needs '''SAS''' channels to be engaged, which is the default . '''SAS''' Pitch and Roll channels may be disengaged by actuating switches located on the '''AFCS''' ('''Automatic/Analog Flight Control System''') panel .[[Image:F-14b-sas-switches.png|thumb|270px|SAS Panel.]]

===Landing Automatic Power Control, (APC) Operation===
* The '''APC''' is a closed loop system that automatically regulates basic engine thrust to maintain the aircraft at an optimum approach angle of attack for landing .
* Prior to engage '''APC''', gear handle must be down with weight off wheels, and the throttles must be set between 98 percent rpm and 68 percent rpm, (as shown on the panel gauges).
* Type '''a''' to toggle the '''APC on/off'''. APC is also disengaged by setting the throttles to MIL, (98 percent rpm) or idle, (68 percent rpm) or raising the landing gear handle or when weight on the wheels .
* When disengaged the '''AUTO THROT''' caution light, (on the left side of the HUD) illuminates for 10 seconds .

===Landing Direct Lift Control, (DLC) Operation===
* During landing approaches, the spoilers and horizontal stabilizers can be controlled simultaneously to provide glidepath correction without changing power setting or angle of attack.

===Ground Spoilers Operation===
* Ground spoilers (that is [http://en.wikipedia.org/wiki/Elevon elevons] used as air-brake ) provide additional drag immediately after the touch down. Before the landing, arm the ground spoilers by hitting '''Ctrl-s''' . After the aircraft hits the runway, pull the throttle to idle, then the spoilers (elevons) get fully deployed.

===Weapons operation===

At the moment, only the gun and the AIM-9s are operational, others ordinances are displayed under the wing, their weight is correct but they aren't usable.

You must have the latest F-14B package from [[Git]] for weapons operations.

* '''Gun:''' At startup, the ammunition store is filled with 675 round. It's not possible to refill without quiting FG. To fire the M61A1 Vulcan:
** Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available (:AHa). Having the HUD in this mode is not mandatory though there won't be any symbolics available for the gun in other HD modes.
** Select Gun mode with the Stick Weapon Mode Selector (w). A pipper, the G symbol with a number showing approximately the remaining rounds x 100 and a closure rate scale are displayed in the HUD. The closure rate scale is active only if a target is locked by the radar with TWS AUTO mode (diamond on the HUD).
** Switch Master Arm on, the X on the G symbol means Master Arm off or in training mode.
** Press e to fire the gun.

* '''Sidewinders:''' Crudely modeled on AIM-9L available data.
** Select a weapons set using the menu: Tomcat Controls > Fuel and Stores: "FAD light" has 4 sidewinders, "FAD", "FAD heavy" and "Bombcat" have 2 of them.
** Select HUD A/A Mode on the Display panel, on pilot's right console. A multikey shortcut is also available (:AHa).
** Select SW mode with the Stick Weapon Mode Selector (w).
** Switch to the back seater's view (Ctrl-v).
** Select pylons 1 and 8, down position, on the Armament panel, on RIO's right console. A shortcut toggles these two switches so you can select or deselect all AIM-9 in one keyboard stroke (Ctrl-m) without leaving pilot's view.
** Switch back to the pilot's view (Ctrl-v).
** Switch Master Arm on, you ear the search signal of the seeker head, a low volume buzz sound.
** Now prior to be fired, the AIM-9 must have a lock on a target. For the time being only Multiplayers and AI tankers can be locked. The minimal lock distance is 10 NM, the target must be aproximately inside a 80° cone centered on datum line. When locked, the signal buzz volume becomes louder. For best results try to shoot at a 3 to 6 NM range and with the target centered on the aircraft velocity vector. The missile will explode at the smaller distance possible. However if this distance is above 70 meters, it will continue its trajectory without guidance.

==Pilot's Cockpit==
[[Image:F-14b-pilots-display-control-panel.jpg|thumb|270px|Pilot's Display Control Panel.]]
===Displays Control Panel===
* The Display Control Panel is located on the right side of the pilot's main panel, under the Hook lever. The '''3 botom switches''' respectively turn the '''VDI''', '''HUD''' and '''HSD''' displays '''on/off'''. The '''HSD MODE''' switch is also available, it selects '''NAV''' or '''TID''' or '''ECM''' mode. This can also be achieved by cycling through these 3 modes with the "'''h'''" key. (''Note: the '''NAV MODE''' push buttons - '''TO''', '''CRUISE''', '''A/A''', '''A/G''', '''LDG''' - are not operational yet.'')
** '''VDI: Vertical Display Indicator'''. Shows the aircraft attitude in roll and pitch, with an artifitial horizon and magnetic heading.
** '''HUD: Head UP Display'''.
** '''HSD: Horizontal Situation Display'''. HSD shows either:
***in '''NAV''' mode: compas with navigation indications,
***in '''TID''' mode (Tactical Information Display): an horizontal representation of the tactical situation (that is informations provided by the RIO from what he sees in his radar displays).
***in '''ECM''' mode: a representation of radar threats around the aircraft.

===VHF===
* Located on the RIO's left console, 3 bands: 30-88 MHz, 108-174 MHz, 225-400 MHz. Modes '''TR''' and '''TR-G''' set '''COMM1'''. Mode '''DF''' sets '''NAV1''', that is '''Direction Finder''' displayed with the single needle in both '''BDHIs''' (Bearing, Distance, Heading Indicator) . You have Comm *or* DF. Storing frequencies (up to 20 channels) '''a - PRESET''' select the desired channel, '''b - READ''' tune the desired frequency, '''c - LOAD''' stores the frequency in the previously selected channel.

===UHF===
* Located on the pilot's left console, 225-400 Mhz. ADF is not enabled on this radio.

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
=== Links ===
* http://en.wikipedia.org/wiki/F-14 - F-14 Tomcat
* http://www.globalsecurity.org/military/systems/aircraft/f-14.htm - F-14 Tomcat
* http://www.fas.org/programs/ssp/man/uswpns/air/fighter/f14.html - F-14 Tomcat
* http://www.anft.net/f-14/f14-specification.htm - Home of M.A.T.S.
* http://www.navyair.com/LSO_NATOPS_Manual.pdf - NATOPS LANDING SIGNAL OFFICER MANUAL

{{Grumman}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]

Dual control

2010-08-31T21:12:55Z

Xiii: Replaced CVS by Git (some checks on 2.0 availability are still needed)

'''Dual Control''' is a system for [[FlightGear]] that adds basic support for shared control of an [[aircraft]] over the FlightGear [[Multiplayer Howto|multiplayer network]].

'''Note:''' [[FlightGear 1.9.0]] or later is needed to use Dual Control.

==Aircraft==

Currently there are a small number of aircraft with dual control support:
* [[Zeppelin NT]], pilot and copilot (<tt>ZLT-NT</tt>, <tt>ZLT-NT-copilot</tt>). Available in FlightGear 1.9.0 and later.
* [[Blackburn Buccaneer]], pilot and systems officer (<tt>buccaneer</tt>, <tt>buccaneer-obs</tt>). Available in FlightGear 1.9.0 or later.
* [[Grumman_F-14_Tomcat]], pilot and RIO (<tt>f-14b</tt>, <tt>f-14b-bs</tt>). Available in FlightGear 2.0 or later.
* [[Submarine_Scout]], pilot and observer (<tt>Submarine_Scout</tt>, <tt>Submarine_Scout-observer</tt>). Available in FlightGear/Git.
* [[Boeing 747-400]], pilot flying and pilot monitoring (<tt>747-400</tt>, <tt>747-400-fo</tt>). Available in FlightGear/Git.
* [[Storch|Fieseler Fi 156 Storch]], pilot and passenger (<tt>Fi-156-de</tt>, <tt>Fi-156-passenger</tt>). Available in FlightGear/Git.
* [[ASK-13 sailplane|Schleicher ASK-13 glider]], pilot and passenger (<tt>ask13</tt>, <tt>ask13-passenger</tt>). Available in FlightGear/Git.
* c172p Skyhawk, pilot and copilot (<tt>c172p-pilot</tt> and <tt>c172p-copilot</tt>). Based on David Megginson's [[Cessna C172|c172p]] single control aircraft. Available from [http://www.gidenstam.org/FlightGear/DualControl/Aircraft the dual-control aircraft hangar]. The tar.gz archive for the aircraft should be extracted in $FG_ROOT/Aircraft/.

To connect the pilot and copilot selects each other in the Copilot dialog (FlightGear/Git) or set properties as explained in the usage instructions below.

Dual control enables a pilot and copilot to jointly fly the aircraft over the FlightGear multiplayer network. Depending on the aircraft the pilot and copilot have shared control over primary flight controls, throttle, mixture and so on. Exactly which controls are shared varies between the aircraft but usually include elevator trim, flaps, brakes, cockpit switches, the radio stack and some instrument settings. The copilot usually has a subset of the full instrumentation (also depending on the aircraft), usually including airspeed, altimeter, VSI, HSI, turn coordinator, engine RPM and the radio stack. Typically Nav/Comm 1 and the first VOR indicator is best controlled by the pilot, while Nav/Comm 2 and the corresponding VOR indicator is faster for the copilot.

<center>
[[Image:ZLT-NT-dual.jpg]]
</center>
<center>
''Side-by-side presentation of the Zeppelin NT pilot's (left) and copilot's (right) views.''
</center>

==Usage instruction==
The system consists of two "aircraft":

The pilot uses a special variant of the c172p, <tt>c172p-pilot</tt>. The pilot needs to specify the callsign of the copilot (other copilots will be ignored).
For the Zeppelin NT the aircraft names are <tt>ZLT-NT</tt> and <tt>ZLT-NT-copilot</tt>, respectively.

In the current version the pilot and copilot can select each other in their Co/Pilot selection dialogs available from the "Zeppelin NT/c172p-dual-control"->"MP-(Co)Pilot" menus.

Alternatively the relevant properties can be set from the command line or via the property browser.

'''Pilot usage example:'''
fgfs --aircraft=c172p-pilot --prop:/sim/remote/pilot-callsign="someone"

The copilot uses a special "aircraft", c172p-copilot, which piggybacks on the designated pilot and captures the local control inputs. A current limitation is that only the cockpit views are jitter free. There is also a noticeable delay between control inputs and effect, since they are passed via the the multiplayer protocol. The severity of this delay depend on round trip time and some other factors - the delay seems significantly longer than the round trip time itself which is due to buffering in the MP protocol receiver. That said, I have flown successfully as copilot in a setup with 100-120ms round trip time between both pilot and server and copilot and server (total delay >500ms). Landing is a bit exciting in that case, however.

'''Copilot usage example:'''
fgfs --aircraft=c172p-copilot --prop:/sim/remote/pilot-callsign="anybody"
Note: External views are jitter prone for the copilot.

== Developer information ==

The main part of the Dual Control system is a set of generic [[Nasal scripting language|Nasal]] modules and modified instrument files that form the core of the networked shared control functionality. See the link below for some more information.

==External links==

* [http://www.gidenstam.org/FlightGear/DualControl The main page for the Dual Control system.] Check here for the latest information.

[[Category:FlightGear feature]]

[[es:Control dual]]

FlightGear Newsletter August 2010

2010-08-31T19:33:04Z

Xiii: /* In the hangar */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome.''

==Development news==
===More realistic textures on mountains===
Shader-artist Gral picked up a new project, after his forest and grassland improvements. This time he improves the look of our mountains a lot, thanks to some "elevation and slope detecting" shaders. They replace the vegetation with rocks above a certain elevation or on steep faces. Transition between the different terrain types are extremely smooth, especially when compared to the usual landcover-transition (eg. between land and ocean) in FlightGear.

[http://www.flightgear.org/forums/viewtopic.php?f=5&t=9183 The forum] provides you with more information, screenshots and updates.

===Major updates to the AI system===
This month, FlightGear's AI system has received a major update. Until recently, FlightGear contained two major AI systems, oftentimes leading to much confusion. Although one of the systems had been scheduled for deprecation for a long time, early this month the decision was made to remove this system from FlightGear altogether. The other system, known as the AIModels system, has recently also undergone a major revision. One of the weakest aspects the latter system was that aircraft never performed a reasonable approach, but basically just plummeted out of the skies, only to pretend making a reasonable landing (and usually ending up several miles short of the runway).

The revised code generates much more realistic approach paths, and ensures that arrivals will start almost instantly after program start. In addition, the approach paths are set up in such a way that aircraft will be lined up with 90 seconds of flight time (or more) between them. During the revision, several bugs were solved, resulting in a much more stable AI system.

==In the hangar==
Several [[aircraft]] that have been around in FlightGear for many years got updates this month. There is a huge number of aircraft in the FlightGear hangar (over 300!), and while new aircraft are always welcome, there are many existing aircraft that would benefit from some spit-and-polish. Creating a completely new aircraft to a high standard represents a monumental amount of work. Those wanting to contribute, but without the time available to create a truly world-class aircraft from scratch might want to consider improving a favourite aircraft from the hangar instead. The effects are more immediate, and you can improve it one piece at a time.

===AC-130 Spectre===
Jack Mermod has recently begun transforming Emmanuel Barranger's [[Lockheed C-130 Hercules]] into a AC-130 'Spectre' Gunship. The gunship has been released, but will have many more updates to come.

So far, the gunship has been equipped with the following:
* Two GAU-12 25mm guns
* One 40mm L/60 Bofors cannon
* Accurately modeled and functioning flares
* AN/ALQ-196 jammer and other electronic countermeasures
* a Battle Management Station, from where weapons can be armed and fired
* Several screens(in the Battle Management Station) which will display information, radar input, gun camera feeds, and ammunition stats in following releases
* MANY liveries

You can see the AC-130 topic and download the aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=9074&st=0&sk=t&sd=a&start=75#p92617 here].

[[File:CRJ-900.jpg|thumb|250px|The Bombardier CRJ-900 in [[Blender]].]]
===Bombardier CRJ-900===
After working on the [[Airbus A320|A320]], [[User:Skyop|Skyop]] is creating his first aircraft- the [[Bombardier CRJ-900]]- from scratch. The basic model has been completed- tasks still to do include UV mapping the model, animating its components, and adding in other features to make the CRJ-900 suitable for [[FlightGear 2.0.0]]

===Douglas A-4F Skyhawk===
On a smaller scale to Hal's improvements to the Mustang, Stuart Buchanan has been making a number of changes to the venerable [[Douglas A-4 Skyhawk|A4-F Skyhawk]], or "Scooter". Rather than change the existing A-4F Blue Angels model, Stuart has instead modelled a normal Navy A-4F with dual drop-tanks. As well as some minor [[FDM]] tweaking, improvements include a completely new exterior and 3D [[cockpit]], and some more accurate flight control systems including auto-deploying spoilers. The A-4F is an interesting [[Aircraft carrier|carrier]]-based light attack aircraft, designed on the principle of simplicity and lightness by Edward Heinmann. In particular, by making the wings short, they didn't need to be folded for storage on carriers, which meant they didn't need complex wing folds, and hence were lighter and stronger.

[[File:b29s-bombs.jpg|thumb|250px|B-29s dropping their load.]]
[[File:B-29-bomb-impact.jpg|thumb|250px|Ash plumes rise up from the bombed spot.]]
===B-29 Superfortress===
Coming soon. There is a major refurbishment of the Submodel code in the pipeline which will resurect and, hopefully, speed up some old facilities.

The M47-A2 incendiary bombs have been linked to the wildfire system, and generate multiple fires. Unfortunately, at present the hit on framerate is huge. So this might well not make Git. A cut-down version might be feasible. It remains the case that the submodels are not visible over MP.

<font size=4>STOP PRESS</font>

It's in GIT now! The formation is now a 4-ship diamond. The M47-A2 and the M-17 bombs both create wildfires on impact. BEWARE, the wildfires may cause an unacceptable framerate drop after a while, and FG may eventually crash. If you disable Wildfires in the dropdown menu at some point before this happens, you will get most, but not all, of the framerate back.

===Eurofighter Typhoon===
Some pretty major work has been accomplished on the [[Eurofighter Typhoon|Typhoon]] by almursi - some fiddly FDM work has now made it actually behave like one of the most agile fighters in the world, its performance envelope is now roughly equivalent to its real-world counterpart, and a good deal of the missing textures have been added. Algernon has accomplished some rather more minor work, with authentic scale navigation lights added and strobes and beacon in development along with a custom electrical system to power them. Whilst there is still a lot to do, including the flight control system which prevents the aircraft from performing beyond the pilots physical limits - how about 14g turns?! - the feedback on the latest release has been really positive. Try it yourself and post some feedback in the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=1460&start=90|Eurofighter Typhoon thread] on the Aircraft Development board.

===Fokker 100===
Another aircraft that has been updated recently is the [[Fokker 100]]. It now has a 3D cockpit and a rudimentary equipment failure control system, as well as a much-improved FDM and Autopilot. At the moment, the Equipment Failure System can only cause engine fires and flap failure. Several new liveries have been made as well. Authors who contributed to this latest phase in development include (in no particular order) Erik Hofman, Thomas Ito-Haigh, Gary Neely, and Skyop.

===Helijah Hangar updates===
Helijah updates his hangar with new aircraft (mostly WW2) very regulary and pushes them to Git. This month's list includes:
{| class="vatop"
|width="200" |
* BV-170
* B-35 Peacemaker
* CA-12
* Me 209V1
|width="200" |
* Me P.1101
* Breguet 19
* Caudron GIII
* Caudron GIV
|}

===North American P-51D Mustang===
Hal V. Engel has made some massive improvements to the [[P-51D Mustang|P51-D]]. Using NACA (the pre-cursor to NASA) published data, he's produced a very impressive [[JSBSim]] FDM. He's also made a number of improvements to the 3D cockpit and the engine systems. Those who enjoy their WWII warbirds will be very interested indeed. Your correspondent has still to manage a take-off from the runway without at least one bounce, but can report that the landing characteristics, while not benign, are at least manageable. This is an aircraft that will really repay some effort on the part of the pilot to get to know, and almost certainly represents the most accurate warbird FDM we have available.

===AIM-9 Sidewinders on the F-14B Tomcat===

Guided missiles are now available for the [[Grumman F-14 Tomcat|Grumman F-14B Tomcat]] in Git. At the moment, only AIM-9s are functional.
They lock on the nearest MP or AI target, like in the SEAM mode (Sidewinder Expanded Acquisition Mode) and they follow a constant angle trajectory. When used with Bombable script they have a quite certain effect on the Zeros. When used against an MP aircraft, you will only see the missile explosion and a message with the hit range can be displayed trough MP. The author, Xiii, would like to add this feature to the A-10 and maybe the f16 which both use the same nasal framework. But it may take a long-long time. (And don't forget to read the f-14b README.help prior to use the Sidewinders!)

== Scenery corner ==
===Animated jetways finalized===
An exciting new feature comes to FlightGear with the completion of [[User:Skyop|Skyop's]] [[Howto: Animated jetways|animated jetway system]]. The first airport to implement it is none other than KLAS. [[Howto: Animated jetways#Usage|A slight fix]] is required to see the jetways.

To use the system, taxi to an animated jetway and park your aircraft with your nosegear on the "T" at the end of the marking line. Click the jetway, and if your aircraft has the appropriate values in its <tt>-set.xml</tt> file, the jetway will extend and raise/lower itself to your door! Updated <tt>-set.xml</tt> files for the [[Boeing 737-300]], [[Boeing 747-400]], and [[Boeing 777-200ER]] can be downloaded from [http://www.flightgear.org/forums/viewtopic.php?t=8728&start=90#p91826 this post] of the development thread.

Unfortunately, there are still a few unresolved issues with the jetways. The biggest being that they currently cannot operate independently.

[[File:KLAS.jpg|thumb|right|250px|A Southwest Airlines [[Boeing 737-300]] parked at Concourse B at KLAS. Concourse C is visible in the background.]]
===Las Vegas McCarran International Airport===
[[User:Skyop|Skyop]] has modeled Concourse A, Concourse B, Concourse C, and the Charter International Terminal at Las Vegas McCarran International Airport (KLAS). Unfortunately, the new Concourse D could not be modeled as there was no [[GPL]]-compatible satellite imagery available. You can obtain the new terminals via [[TerraSync]].

===Reno International Airport===
<font color="red" size="5">??</font>

== Wiki updates ==
===Aerial refueling articles===
The [[Howto: Aerial refueling|aerial refueling howto]] has been updated and slightly cleaned up, to increase its readability. In addition to that, a developers howto has been written, to provide an easy to understand article on [[Howto: Implement aerial refueling capability|how to implement aerial capability]] on aircraft.

[[Image:Anaglyphic2.jpg|thumb|250px|Red-Green Anaglyph OSG Render in action.]]
===Anaglyph: FlightGear in 3D===
We all know that certain cinemas show certain movies in 3D. Most of the time the spectators wear those weird looking pairs of Red-Green or Red-Cyan glasses. These glasses divide the two (colored) layers on the screen between our two eyes; thus creating the effect of 3D. Since the switch to [[OSG]], FlightGear is able to generate such images as well!

[[Anaglyph (3D)|This new wiki article]] explains how to obtain or create a oar of 3D-glasses and how to configure FlightGear.

===How do I commit changes to Git on Windows?===
Three months after our big move to [[Git]], there finally is a tutorial on how to commit changes to Git on a Windows based computer! This allows every FlightGear user/developer to get their edits up in the official FlightGear repository. Let's hope that this will stimulate more people to start developing and sharing their work with the rest of the world.

Read the article at [[FlightGear Git on Windows#Commiting changes]].

===Nasal articles===
In the aftermath of a [http://www.flightgear.org/forums/viewtopic.php?f=30&t=8995 forum topic], work has been started on expanding the number of [[Nasal]] related articles at the wiki. These articles should help (new) developers to understand the scripting language and eventually write their own scripts.

All Nasal articles are collected in a [[:Category:Nasal|special category]]. More articles are welcome, as always, so feel free to share your Nasal knowledge!

===What kind of bindings are there?===
FlightGear supports a large range of [[bindings]], which are actions that happen on clicking certain objects/menus. For example, when you click the gear lever in the [[Boeing 777]], a binding actually "transmits" the command to the gear. Another example that is widely used is an autopilot rotary knob (eg. for setting the heading). When you click these knobs with your mouse, bindings define what properties are changed and with what steps.

Work has began on collecting all those bindings in a single document. Check out [[Bindings|the list]]!

== Community news ==
=== FlightGear on YouTube ===
* A [http://www.youtube.com/watch?v=-1pI8bIOxYA wonderful example] of the possibilities and power of FlightGear, in which FlightGear is connected to some avionics equipment (including flight displays and EICAS).
* Chances are big that you never saw anything like what is done in [http://www.youtube.com/watch?v=ISiia1syhTM this video], before. These people connected a radio controller vehicle to their computer and visualized its movements with FlightGear's [[jeep]].
* Our home-director, Oscar, uploaded a [http://www.youtube.com/watch?v=a-40ocTyVGY nice video] summarising the KLM fleet in FlightGear.
* In case you have missed it, a [http://www.dailymotion.com/video/x5i0i0_brest_videogames video showing photorealistic scenery] in Brest.
* Despite the bad graphics (clouds and smoke), this [http://www.youtube.com/watch?v=t90qRgczJ-o Red Bull Air Race video] shows once again what an enormous range of different things one can do in FlightGear. A [http://www.youtube.com/watch?v=oQQDL7jaScQ second video] was uploaded as well.
* A new flightgear promo has been uploaded by 'TheMasterofmod'. This [http://www.youtube.com/watch?v=gwFJcu5I4is Promotional Video] focus' on Military Operations and the extensive possibilities with military craft in Flightgear.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== New way to contact mpserver maintainers===
After multiple complaints from the community about the difficulty to get in contact with FlightGear [[Howto: Multiplayer|multiplayer]] server maintainers, a mailingsystem is being set up. So far, only mpserver10 is known to be correctly set up for the new system.

You can contact the maintainer of server10 via admin@mpserver10.flightgear.org. Other servers are expected to be set up soon.

=== Relaunch of TransGear Airways ===
This month saw the first event of the resurrected [[TransGear Airways]]. The event was planned by Lukosius and Redneck. Redneck and Jomo provided [[air traffic control]] services. The event was well received and attended by registered TGA pilots and other unregistered pilots as well. Details are available on the [http://transgear.treborlogic.com official site]. The September event will be the first event scheduled using Yourgod's scheduling software which will allow pilots to plan their own routes within the event.

=== Update on FlightProSim ===
Thanks in part to ''jackmermod'', the FlightGear community now has [http://flightgear.org/forums/viewtopic.php?f=3&t=8225&start=45#p90830 access] to the source code of the much-discussed [[FlightProSim]], which will allow for a better and more thorough investigation of the simulator. Browsing through the source directory structure has so far given promising results, but compiling the program itself has been problematic.

==And finally==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

[[Category:FlightGear Newsletter|2010 08]]

FlightGear Newsletter August 2010

2010-08-31T19:27:20Z

Xiii: /* AIM-9 Sidewinders on the F-14B Tomcat */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome.''

==Development news==
===More realistic textures on mountains===
Shader-artist Gral picked up a new project, after his forest and grassland improvements. This time he improves the look of our mountains a lot, thanks to some "elevation and slope detecting" shaders. They replace the vegetation with rocks above a certain elevation or on steep faces. Transition between the different terrain types are extremely smooth, especially when compared to the usual landcover-transition (eg. between land and ocean) in FlightGear.

[http://www.flightgear.org/forums/viewtopic.php?f=5&t=9183 The forum] provides you with more information, screenshots and updates.

===Major updates to the AI system===
This month, FlightGear's AI system has received a major update. Until recently, FlightGear contained two major AI systems, oftentimes leading to much confusion. Although one of the systems had been scheduled for deprecation for a long time, early this month the decision was made to remove this system from FlightGear altogether. The other system, known as the AIModels system, has recently also undergone a major revision. One of the weakest aspects the latter system was that aircraft never performed a reasonable approach, but basically just plummeted out of the skies, only to pretend making a reasonable landing (and usually ending up several miles short of the runway).

The revised code generates much more realistic approach paths, and ensures that arrivals will start almost instantly after program start. In addition, the approach paths are set up in such a way that aircraft will be lined up with 90 seconds of flight time (or more) between them. During the revision, several bugs were solved, resulting in a much more stable AI system.

==In the hangar==
Several [[aircraft]] that have been around in FlightGear for many years got updates this month. There is a huge number of aircraft in the FlightGear hangar (over 300!), and while new aircraft are always welcome, there are many existing aircraft that would benefit from some spit-and-polish. Creating a completely new aircraft to a high standard represents a monumental amount of work. Those wanting to contribute, but without the time available to create a truly world-class aircraft from scratch might want to consider improving a favourite aircraft from the hangar instead. The effects are more immediate, and you can improve it one piece at a time.

===AC-130 Spectre===
Jack Mermod has recently begun transforming Emmanuel Barranger's [[Lockheed C-130 Hercules]] into a AC-130 'Spectre' Gunship. The gunship has been released, but will have many more updates to come.

So far, the gunship has been equipped with the following:
* Two GAU-12 25mm guns
* One 40mm L/60 Bofors cannon
* Accurately modeled and functioning flares
* AN/ALQ-196 jammer and other electronic countermeasures
* a Battle Management Station, from where weapons can be armed and fired
* Several screens(in the Battle Management Station) which will display information, radar input, gun camera feeds, and ammunition stats in following releases
* MANY liveries

You can see the AC-130 topic and download the aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=9074&st=0&sk=t&sd=a&start=75#p92617 here].

[[File:CRJ-900.jpg|thumb|250px|The Bombardier CRJ-900 in [[Blender]].]]
===Bombardier CRJ-900===
After working on the [[Airbus A320|A320]], [[User:Skyop|Skyop]] is creating his first aircraft- the [[Bombardier CRJ-900]]- from scratch. The basic model has been completed- tasks still to do include UV mapping the model, animating its components, and adding in other features to make the CRJ-900 suitable for [[FlightGear 2.0.0]]

===Douglas A-4F Skyhawk===
On a smaller scale to Hal's improvements to the Mustang, Stuart Buchanan has been making a number of changes to the venerable [[Douglas A-4 Skyhawk|A4-F Skyhawk]], or "Scooter". Rather than change the existing A-4F Blue Angels model, Stuart has instead modelled a normal Navy A-4F with dual drop-tanks. As well as some minor [[FDM]] tweaking, improvements include a completely new exterior and 3D [[cockpit]], and some more accurate flight control systems including auto-deploying spoilers. The A-4F is an interesting [[Aircraft carrier|carrier]]-based light attack aircraft, designed on the principle of simplicity and lightness by Edward Heinmann. In particular, by making the wings short, they didn't need to be folded for storage on carriers, which meant they didn't need complex wing folds, and hence were lighter and stronger.

[[File:b29s-bombs.jpg|thumb|250px|B-29s dropping their load.]]
[[File:B-29-bomb-impact.jpg|thumb|250px|Ash plumes rise up from the bombed spot.]]
===B-29 Superfortress===
Coming soon. There is a major refurbishment of the Submodel code in the pipeline which will resurect and, hopefully, speed up some old facilities.

The M47-A2 incendiary bombs have been linked to the wildfire system, and generate multiple fires. Unfortunately, at present the hit on framerate is huge. So this might well not make Git. A cut-down version might be feasible. It remains the case that the submodels are not visible over MP.

<font size=4>STOP PRESS</font>

It's in GIT now! The formation is now a 4-ship diamond. The M47-A2 and the M-17 bombs both create wildfires on impact. BEWARE, the wildfires may cause an unacceptable framerate drop after a while, and FG may eventually crash. If you disable Wildfires in the dropdown menu at some point before this happens, you will get most, but not all, of the framerate back.

===Eurofighter Typhoon===
Some pretty major work has been accomplished on the [[Eurofighter Typhoon|Typhoon]] by almursi - some fiddly FDM work has now made it actually behave like one of the most agile fighters in the world, its performance envelope is now roughly equivalent to its real-world counterpart, and a good deal of the missing textures have been added. Algernon has accomplished some rather more minor work, with authentic scale navigation lights added and strobes and beacon in development along with a custom electrical system to power them. Whilst there is still a lot to do, including the flight control system which prevents the aircraft from performing beyond the pilots physical limits - how about 14g turns?! - the feedback on the latest release has been really positive. Try it yourself and post some feedback in the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=1460&start=90|Eurofighter Typhoon thread] on the Aircraft Development board.

===Fokker 100===
Another aircraft that has been updated recently is the [[Fokker 100]]. It now has a 3D cockpit and a rudimentary equipment failure control system, as well as a much-improved FDM and Autopilot. At the moment, the Equipment Failure System can only cause engine fires and flap failure. Several new liveries have been made as well. Authors who contributed to this latest phase in development include (in no particular order) Erik Hofman, Thomas Ito-Haigh, Gary Neely, and Skyop.

===Helijah Hangar updates===
Helijah updates his hangar with new aircraft (mostly WW2) very regulary and pushes them to Git. This month's list includes:
{| class="vatop"
|width="200" |
* BV-170
* B-35 Peacemaker
* CA-12
* Me 209V1
|width="200" |
* Me P.1101
* Breguet 19
* Caudron GIII
* Caudron GIV
|}

===North American P-51D Mustang===
Hal V. Engel has made some massive improvements to the [[P-51D Mustang|P51-D]]. Using NACA (the pre-cursor to NASA) published data, he's produced a very impressive [[JSBSim]] FDM. He's also made a number of improvements to the 3D cockpit and the engine systems. Those who enjoy their WWII warbirds will be very interested indeed. Your correspondent has still to manage a take-off from the runway without at least one bounce, but can report that the landing characteristics, while not benign, are at least manageable. This is an aircraft that will really repay some effort on the part of the pilot to get to know, and almost certainly represents the most accurate warbird FDM we have available.

===AIM-9 Sidewinders on the F-14B Tomcat===

Guided missiles are now available for the Tomcat in Git. At the moment, only AIM-9s are functional.
They lock on the nearest MP or AI target, like in the SEAM mode (Sidewinder Expanded Acquisition Mode) and they follow a constant angle trajectory. When used with Bombable script they have a quite certain effect on the Zeros. When used against an MP aircraft, you will only see the missile explosion and a message with the hit range can be displayed trough MP. The author, Xiii, would like to add this feature to the A-10 and maybe the f16 which both use the same nasal framework. But it may take a long-long time. (And don't forget to read the f-14b README.help prior to use the Sidewinders!)

== Scenery corner ==
===Animated jetways finalized===
An exciting new feature comes to FlightGear with the completion of [[User:Skyop|Skyop's]] [[Howto: Animated jetways|animated jetway system]]. The first airport to implement it is none other than KLAS. [[Howto: Animated jetways#Usage|A slight fix]] is required to see the jetways.

To use the system, taxi to an animated jetway and park your aircraft with your nosegear on the "T" at the end of the marking line. Click the jetway, and if your aircraft has the appropriate values in its <tt>-set.xml</tt> file, the jetway will extend and raise/lower itself to your door! Updated <tt>-set.xml</tt> files for the [[Boeing 737-300]], [[Boeing 747-400]], and [[Boeing 777-200ER]] can be downloaded from [http://www.flightgear.org/forums/viewtopic.php?t=8728&start=90#p91826 this post] of the development thread.

Unfortunately, there are still a few unresolved issues with the jetways. The biggest being that they currently cannot operate independently.

[[File:KLAS.jpg|thumb|right|250px|A Southwest Airlines [[Boeing 737-300]] parked at Concourse B at KLAS. Concourse C is visible in the background.]]
===Las Vegas McCarran International Airport===
[[User:Skyop|Skyop]] has modeled Concourse A, Concourse B, Concourse C, and the Charter International Terminal at Las Vegas McCarran International Airport (KLAS). Unfortunately, the new Concourse D could not be modeled as there was no [[GPL]]-compatible satellite imagery available. You can obtain the new terminals via [[TerraSync]].

===Reno International Airport===
<font color="red" size="5">??</font>

== Wiki updates ==
===Aerial refueling articles===
The [[Howto: Aerial refueling|aerial refueling howto]] has been updated and slightly cleaned up, to increase its readability. In addition to that, a developers howto has been written, to provide an easy to understand article on [[Howto: Implement aerial refueling capability|how to implement aerial capability]] on aircraft.

[[Image:Anaglyphic2.jpg|thumb|250px|Red-Green Anaglyph OSG Render in action.]]
===Anaglyph: FlightGear in 3D===
We all know that certain cinemas show certain movies in 3D. Most of the time the spectators wear those weird looking pairs of Red-Green or Red-Cyan glasses. These glasses divide the two (colored) layers on the screen between our two eyes; thus creating the effect of 3D. Since the switch to [[OSG]], FlightGear is able to generate such images as well!

[[Anaglyph (3D)|This new wiki article]] explains how to obtain or create a oar of 3D-glasses and how to configure FlightGear.

===How do I commit changes to Git on Windows?===
Three months after our big move to [[Git]], there finally is a tutorial on how to commit changes to Git on a Windows based computer! This allows every FlightGear user/developer to get their edits up in the official FlightGear repository. Let's hope that this will stimulate more people to start developing and sharing their work with the rest of the world.

Read the article at [[FlightGear Git on Windows#Commiting changes]].

===Nasal articles===
In the aftermath of a [http://www.flightgear.org/forums/viewtopic.php?f=30&t=8995 forum topic], work has been started on expanding the number of [[Nasal]] related articles at the wiki. These articles should help (new) developers to understand the scripting language and eventually write their own scripts.

All Nasal articles are collected in a [[:Category:Nasal|special category]]. More articles are welcome, as always, so feel free to share your Nasal knowledge!

===What kind of bindings are there?===
FlightGear supports a large range of [[bindings]], which are actions that happen on clicking certain objects/menus. For example, when you click the gear lever in the [[Boeing 777]], a binding actually "transmits" the command to the gear. Another example that is widely used is an autopilot rotary knob (eg. for setting the heading). When you click these knobs with your mouse, bindings define what properties are changed and with what steps.

Work has began on collecting all those bindings in a single document. Check out [[Bindings|the list]]!

== Community news ==
=== FlightGear on YouTube ===
* A [http://www.youtube.com/watch?v=-1pI8bIOxYA wonderful example] of the possibilities and power of FlightGear, in which FlightGear is connected to some avionics equipment (including flight displays and EICAS).
* Chances are big that you never saw anything like what is done in [http://www.youtube.com/watch?v=ISiia1syhTM this video], before. These people connected a radio controller vehicle to their computer and visualized its movements with FlightGear's [[jeep]].
* Our home-director, Oscar, uploaded a [http://www.youtube.com/watch?v=a-40ocTyVGY nice video] summarising the KLM fleet in FlightGear.
* In case you have missed it, a [http://www.dailymotion.com/video/x5i0i0_brest_videogames video showing photorealistic scenery] in Brest.
* Despite the bad graphics (clouds and smoke), this [http://www.youtube.com/watch?v=t90qRgczJ-o Red Bull Air Race video] shows once again what an enormous range of different things one can do in FlightGear. A [http://www.youtube.com/watch?v=oQQDL7jaScQ second video] was uploaded as well.
* A new flightgear promo has been uploaded by 'TheMasterofmod'. This [http://www.youtube.com/watch?v=gwFJcu5I4is Promotional Video] focus' on Military Operations and the extensive possibilities with military craft in Flightgear.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== New way to contact mpserver maintainers===
After multiple complaints from the community about the difficulty to get in contact with FlightGear [[Howto: Multiplayer|multiplayer]] server maintainers, a mailingsystem is being set up. So far, only mpserver10 is known to be correctly set up for the new system.

You can contact the maintainer of server10 via admin@mpserver10.flightgear.org. Other servers are expected to be set up soon.

=== Relaunch of TransGear Airways ===
This month saw the first event of the resurrected [[TransGear Airways]]. The event was planned by Lukosius and Redneck. Redneck and Jomo provided [[air traffic control]] services. The event was well received and attended by registered TGA pilots and other unregistered pilots as well. Details are available on the [http://transgear.treborlogic.com official site]. The September event will be the first event scheduled using Yourgod's scheduling software which will allow pilots to plan their own routes within the event.

=== Update on FlightProSim ===
Thanks in part to ''jackmermod'', the FlightGear community now has [http://flightgear.org/forums/viewtopic.php?f=3&t=8225&start=45#p90830 access] to the source code of the much-discussed [[FlightProSim]], which will allow for a better and more thorough investigation of the simulator. Browsing through the source directory structure has so far given promising results, but compiling the program itself has been problematic.

==And finally==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

[[Category:FlightGear Newsletter|2010 08]]

FlightGear Newsletter August 2010

2010-08-31T19:23:38Z

Xiii: /* In the hangar */ F-14B AIM-9 missiles

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome.''

==Development news==
===More realistic textures on mountains===
Shader-artist Gral picked up a new project, after his forest and grassland improvements. This time he improves the look of our mountains a lot, thanks to some "elevation and slope detecting" shaders. They replace the vegetation with rocks above a certain elevation or on steep faces. Transition between the different terrain types are extremely smooth, especially when compared to the usual landcover-transition (eg. between land and ocean) in FlightGear.

[http://www.flightgear.org/forums/viewtopic.php?f=5&t=9183 The forum] provides you with more information, screenshots and updates.

===Major updates to the AI system===
This month, FlightGear's AI system has received a major update. Until recently, FlightGear contained two major AI systems, oftentimes leading to much confusion. Although one of the systems had been scheduled for deprecation for a long time, early this month the decision was made to remove this system from FlightGear altogether. The other system, known as the AIModels system, has recently also undergone a major revision. One of the weakest aspects the latter system was that aircraft never performed a reasonable approach, but basically just plummeted out of the skies, only to pretend making a reasonable landing (and usually ending up several miles short of the runway).

The revised code generates much more realistic approach paths, and ensures that arrivals will start almost instantly after program start. In addition, the approach paths are set up in such a way that aircraft will be lined up with 90 seconds of flight time (or more) between them. During the revision, several bugs were solved, resulting in a much more stable AI system.

==In the hangar==
Several [[aircraft]] that have been around in FlightGear for many years got updates this month. There is a huge number of aircraft in the FlightGear hangar (over 300!), and while new aircraft are always welcome, there are many existing aircraft that would benefit from some spit-and-polish. Creating a completely new aircraft to a high standard represents a monumental amount of work. Those wanting to contribute, but without the time available to create a truly world-class aircraft from scratch might want to consider improving a favourite aircraft from the hangar instead. The effects are more immediate, and you can improve it one piece at a time.

===AC-130 Spectre===
Jack Mermod has recently begun transforming Emmanuel Barranger's [[Lockheed C-130 Hercules]] into a AC-130 'Spectre' Gunship. The gunship has been released, but will have many more updates to come.

So far, the gunship has been equipped with the following:
* Two GAU-12 25mm guns
* One 40mm L/60 Bofors cannon
* Accurately modeled and functioning flares
* AN/ALQ-196 jammer and other electronic countermeasures
* a Battle Management Station, from where weapons can be armed and fired
* Several screens(in the Battle Management Station) which will display information, radar input, gun camera feeds, and ammunition stats in following releases
* MANY liveries

You can see the AC-130 topic and download the aircraft [http://www.flightgear.org/forums/viewtopic.php?f=4&t=9074&st=0&sk=t&sd=a&start=75#p92617 here].

[[File:CRJ-900.jpg|thumb|250px|The Bombardier CRJ-900 in [[Blender]].]]
===Bombardier CRJ-900===
After working on the [[Airbus A320|A320]], [[User:Skyop|Skyop]] is creating his first aircraft- the [[Bombardier CRJ-900]]- from scratch. The basic model has been completed- tasks still to do include UV mapping the model, animating its components, and adding in other features to make the CRJ-900 suitable for [[FlightGear 2.0.0]]

===Douglas A-4F Skyhawk===
On a smaller scale to Hal's improvements to the Mustang, Stuart Buchanan has been making a number of changes to the venerable [[Douglas A-4 Skyhawk|A4-F Skyhawk]], or "Scooter". Rather than change the existing A-4F Blue Angels model, Stuart has instead modelled a normal Navy A-4F with dual drop-tanks. As well as some minor [[FDM]] tweaking, improvements include a completely new exterior and 3D [[cockpit]], and some more accurate flight control systems including auto-deploying spoilers. The A-4F is an interesting [[Aircraft carrier|carrier]]-based light attack aircraft, designed on the principle of simplicity and lightness by Edward Heinmann. In particular, by making the wings short, they didn't need to be folded for storage on carriers, which meant they didn't need complex wing folds, and hence were lighter and stronger.

[[File:b29s-bombs.jpg|thumb|250px|B-29s dropping their load.]]
[[File:B-29-bomb-impact.jpg|thumb|250px|Ash plumes rise up from the bombed spot.]]
===B-29 Superfortress===
Coming soon. There is a major refurbishment of the Submodel code in the pipeline which will resurect and, hopefully, speed up some old facilities.

The M47-A2 incendiary bombs have been linked to the wildfire system, and generate multiple fires. Unfortunately, at present the hit on framerate is huge. So this might well not make Git. A cut-down version might be feasible. It remains the case that the submodels are not visible over MP.

<font size=4>STOP PRESS</font>

It's in GIT now! The formation is now a 4-ship diamond. The M47-A2 and the M-17 bombs both create wildfires on impact. BEWARE, the wildfires may cause an unacceptable framerate drop after a while, and FG may eventually crash. If you disable Wildfires in the dropdown menu at some point before this happens, you will get most, but not all, of the framerate back.

===Eurofighter Typhoon===
Some pretty major work has been accomplished on the [[Eurofighter Typhoon|Typhoon]] by almursi - some fiddly FDM work has now made it actually behave like one of the most agile fighters in the world, its performance envelope is now roughly equivalent to its real-world counterpart, and a good deal of the missing textures have been added. Algernon has accomplished some rather more minor work, with authentic scale navigation lights added and strobes and beacon in development along with a custom electrical system to power them. Whilst there is still a lot to do, including the flight control system which prevents the aircraft from performing beyond the pilots physical limits - how about 14g turns?! - the feedback on the latest release has been really positive. Try it yourself and post some feedback in the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=1460&start=90|Eurofighter Typhoon thread] on the Aircraft Development board.

===Fokker 100===
Another aircraft that has been updated recently is the [[Fokker 100]]. It now has a 3D cockpit and a rudimentary equipment failure control system, as well as a much-improved FDM and Autopilot. At the moment, the Equipment Failure System can only cause engine fires and flap failure. Several new liveries have been made as well. Authors who contributed to this latest phase in development include (in no particular order) Erik Hofman, Thomas Ito-Haigh, Gary Neely, and Skyop.

===Helijah Hangar updates===
Helijah updates his hangar with new aircraft (mostly WW2) very regulary and pushes them to Git. This month's list includes:
{| class="vatop"
|width="200" |
* BV-170
* B-35 Peacemaker
* CA-12
* Me 209V1
|width="200" |
* Me P.1101
* Breguet 19
* Caudron GIII
* Caudron GIV
|}

===North American P-51D Mustang===
Hal V. Engel has made some massive improvements to the [[P-51D Mustang|P51-D]]. Using NACA (the pre-cursor to NASA) published data, he's produced a very impressive [[JSBSim]] FDM. He's also made a number of improvements to the 3D cockpit and the engine systems. Those who enjoy their WWII warbirds will be very interested indeed. Your correspondent has still to manage a take-off from the runway without at least one bounce, but can report that the landing characteristics, while not benign, are at least manageable. This is an aircraft that will really repay some effort on the part of the pilot to get to know, and almost certainly represents the most accurate warbird FDM we have available.

===AIM-9 Sidewinders on the F-14B Tomcat===

Guided missiles are now available for the Tomcat in Git. At the moment, only AIM-9s are fonctionnal.
They lock on the nearest MP or AI target, like in the SEAM mode (Sidewinder Expanded Acquisition Mode) and they follow a constant angle trajectory. When used with Bombable script they have a quite certain effect on the Zeros. When used against an MP aircraft, you will only see the missile explosion and a message whith the hit range can be displayed trough MP. The author, Xiii, would like to add this feature to the A-10 and maybe the f16 which both use the same nasal framework. But it may take a long-long time. (And don't forget to read the f-14b README.help prior to use the Sidewinders!)

== Scenery corner ==
===Animated jetways finalized===
An exciting new feature comes to FlightGear with the completion of [[User:Skyop|Skyop's]] [[Howto: Animated jetways|animated jetway system]]. The first airport to implement it is none other than KLAS. [[Howto: Animated jetways#Usage|A slight fix]] is required to see the jetways.

To use the system, taxi to an animated jetway and park your aircraft with your nosegear on the "T" at the end of the marking line. Click the jetway, and if your aircraft has the appropriate values in its <tt>-set.xml</tt> file, the jetway will extend and raise/lower itself to your door! Updated <tt>-set.xml</tt> files for the [[Boeing 737-300]], [[Boeing 747-400]], and [[Boeing 777-200ER]] can be downloaded from [http://www.flightgear.org/forums/viewtopic.php?t=8728&start=90#p91826 this post] of the development thread.

Unfortunately, there are still a few unresolved issues with the jetways. The biggest being that they currently cannot operate independently.

[[File:KLAS.jpg|thumb|right|250px|A Southwest Airlines [[Boeing 737-300]] parked at Concourse B at KLAS. Concourse C is visible in the background.]]
===Las Vegas McCarran International Airport===
[[User:Skyop|Skyop]] has modeled Concourse A, Concourse B, Concourse C, and the Charter International Terminal at Las Vegas McCarran International Airport (KLAS). Unfortunately, the new Concourse D could not be modeled as there was no [[GPL]]-compatible satellite imagery available. You can obtain the new terminals via [[TerraSync]].

===Reno International Airport===
<font color="red" size="5">??</font>

== Wiki updates ==
===Aerial refueling articles===
The [[Howto: Aerial refueling|aerial refueling howto]] has been updated and slightly cleaned up, to increase its readability. In addition to that, a developers howto has been written, to provide an easy to understand article on [[Howto: Implement aerial refueling capability|how to implement aerial capability]] on aircraft.

[[Image:Anaglyphic2.jpg|thumb|250px|Red-Green Anaglyph OSG Render in action.]]
===Anaglyph: FlightGear in 3D===
We all know that certain cinemas show certain movies in 3D. Most of the time the spectators wear those weird looking pairs of Red-Green or Red-Cyan glasses. These glasses divide the two (colored) layers on the screen between our two eyes; thus creating the effect of 3D. Since the switch to [[OSG]], FlightGear is able to generate such images as well!

[[Anaglyph (3D)|This new wiki article]] explains how to obtain or create a oar of 3D-glasses and how to configure FlightGear.

===How do I commit changes to Git on Windows?===
Three months after our big move to [[Git]], there finally is a tutorial on how to commit changes to Git on a Windows based computer! This allows every FlightGear user/developer to get their edits up in the official FlightGear repository. Let's hope that this will stimulate more people to start developing and sharing their work with the rest of the world.

Read the article at [[FlightGear Git on Windows#Commiting changes]].

===Nasal articles===
In the aftermath of a [http://www.flightgear.org/forums/viewtopic.php?f=30&t=8995 forum topic], work has been started on expanding the number of [[Nasal]] related articles at the wiki. These articles should help (new) developers to understand the scripting language and eventually write their own scripts.

All Nasal articles are collected in a [[:Category:Nasal|special category]]. More articles are welcome, as always, so feel free to share your Nasal knowledge!

===What kind of bindings are there?===
FlightGear supports a large range of [[bindings]], which are actions that happen on clicking certain objects/menus. For example, when you click the gear lever in the [[Boeing 777]], a binding actually "transmits" the command to the gear. Another example that is widely used is an autopilot rotary knob (eg. for setting the heading). When you click these knobs with your mouse, bindings define what properties are changed and with what steps.

Work has began on collecting all those bindings in a single document. Check out [[Bindings|the list]]!

== Community news ==
=== FlightGear on YouTube ===
* A [http://www.youtube.com/watch?v=-1pI8bIOxYA wonderful example] of the possibilities and power of FlightGear, in which FlightGear is connected to some avionics equipment (including flight displays and EICAS).
* Chances are big that you never saw anything like what is done in [http://www.youtube.com/watch?v=ISiia1syhTM this video], before. These people connected a radio controller vehicle to their computer and visualized its movements with FlightGear's [[jeep]].
* Our home-director, Oscar, uploaded a [http://www.youtube.com/watch?v=a-40ocTyVGY nice video] summarising the KLM fleet in FlightGear.
* In case you have missed it, a [http://www.dailymotion.com/video/x5i0i0_brest_videogames video showing photorealistic scenery] in Brest.
* Despite the bad graphics (clouds and smoke), this [http://www.youtube.com/watch?v=t90qRgczJ-o Red Bull Air Race video] shows once again what an enormous range of different things one can do in FlightGear. A [http://www.youtube.com/watch?v=oQQDL7jaScQ second video] was uploaded as well.
* A new flightgear promo has been uploaded by 'TheMasterofmod'. This [http://www.youtube.com/watch?v=gwFJcu5I4is Promotional Video] focus' on Military Operations and the extensive possibilities with military craft in Flightgear.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== New way to contact mpserver maintainers===
After multiple complaints from the community about the difficulty to get in contact with FlightGear [[Howto: Multiplayer|multiplayer]] server maintainers, a mailingsystem is being set up. So far, only mpserver10 is known to be correctly set up for the new system.

You can contact the maintainer of server10 via admin@mpserver10.flightgear.org. Other servers are expected to be set up soon.

=== Relaunch of TransGear Airways ===
This month saw the first event of the resurrected [[TransGear Airways]]. The event was planned by Lukosius and Redneck. Redneck and Jomo provided [[air traffic control]] services. The event was well received and attended by registered TGA pilots and other unregistered pilots as well. Details are available on the [http://transgear.treborlogic.com official site]. The September event will be the first event scheduled using Yourgod's scheduling software which will allow pilots to plan their own routes within the event.

=== Update on FlightProSim ===
Thanks in part to ''jackmermod'', the FlightGear community now has [http://flightgear.org/forums/viewtopic.php?f=3&t=8225&start=45#p90830 access] to the source code of the much-discussed [[FlightProSim]], which will allow for a better and more thorough investigation of the simulator. Browsing through the source directory structure has so far given promising results, but compiling the program itself has been problematic.

==And finally==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

[[Category:FlightGear Newsletter|2010 08]]

Fr/Accueil

2010-06-19T17:43:51Z

Xiii: cosmetics

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:100%; color:#000"|


{| style="width:100%; border:solid 0px; background:none;"
|style="width:100%; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Bienvenue sur le Wiki de FlightGear !</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">nous en sommes actuellement à [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>

[[file:de.gif|link=:de:Hauptseite]]
[[file:en.gif|link=:en:Main Page]]
[[file:es.gif|link=:es:Portada]]
[[file:fi.gif|link=:fi:Etusivu]]
[[file:fr.gif|link=:fr:Accueil]]
[[file:nl.gif|link=:nl:Hoofdpagina]]
[[file:pl.gif|link=:pl:Strona główna]]
[[file:pt.gif|link=:pt:Página principal]]
[[file:zh.gif|link=:zh:Main Page]]
|}


|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[Help:Tutorial|Modifier]] '''·''' [[Help:Contents|Aide]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|Toutes les pages]] '''·''' [[Special:Search|Chercher
]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Flight Simulator</h2>
|-
|style="color:#000;"|
[[Image:FGlogo.jpg|left]] '''[[FlightGear]] Flight Simulator''' est un simulateur de vol open-source sophistiqué et fonctionnel, créé et maintenu entièrement par des volontaires. Le code source complet est accessible par [[Git]], sous une licence libre [[GNU General Public License]]. La [[FlightGear 1.9.1|version 1.9.1]] de FlightGear date du 25 janvier 2009.

Le projet [[FlightGear]] propose un environnement de développement de simulateur de vol sophistiqué, pour une utilisation académique ou a des fins de recherche, il permet le développement d'autres idées intéressantes en simulation de vol, et est aussi accessible à l'utilisateur lambda. Toute personne intéressée peut [[Volunteer|contribuer]] à l'ajout de fonctionnalités ou à l'amélioration de FlightGear. Il existe de plus de nombreux [[FlightGear related projects|projets connexes]] ([http://www.flightgear.org/links.html projects]).

FlightGear est doté d'une documentation illustrée, parmi laquelle "Le Manuel", disponible en [http://mapserver.flightgear.org/getstart.pdf PDF] et [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. Ce Wiki à été lancé en 2006, et couvre actuellement une bonne partie des sujets liés à FlightGear. La fonctionnalité multi-langue est plus récente (été 2009) et pour le moment seulement une petite partie est traduite.

'''Veuillez sélectionner un portail :'''

{|style="background:none;"
|style="font-size:95%; padding-left:10px; padding-right:20px; margin:0px; vertical-align: top; text-align:left; white-space:nowrap; color:#000;"|
* [[Portal:Developer|Développeur]]
** [[Portal:Developer/3D Modelers|Modélisation 3D]]
** [[Portal:Developer/Aircraft|Aéronef]]
** [[Portal:Developer/Scenery|Paysage]]
|style="font-size:95%; padding-left:20px; margin:0px; vertical-align: top; text-align: left; border-left: 2px solid #d9e2e2; white-space:nowrap; color:#000;"|
* [[fr/Portal:Utilisateur|Utilisateur]]
* [[Portal:Pilot|Pilote]]
|}

===== '''Si vous êtes nouveau ici, jetez un oeil sur le [[Help:Contents|manuel]] avant de créer ou d'éditer un article!''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Pour commencer</h2>
|-
|style="color:#000;"|
* [[:fr:Foire aux questions|FAQ]]
* [[:fr:Howto: Débarrassez-vous des erreurs les plus fréquentes|Messages d'erreur communs]]
* [[:fr:Howto: Multijoueur|Multijoueur]]
* [[:fr:Nouveau sur flightgear|Introduction à FlightGear]]
* [[Troubleshooting Problems|Dépannage]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Utilisation de FlightGear</h2>
|-
|style="color:#000;"|
* [[:fr:Avions|Aéronefs]]
* [[:fr:Piloter l'hélicoptère|Piloter l'hélicoptère]]
* [[:fr:Table des modèles|Liste des modèles]]
'''[[Portal:User|Plus...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Développement de FlightGear</h2>
|-
|style="color:#000;"|
* [[:fr:Compiler FlightGear sous GNU/Linux|Compiler FlightGear]]
* [[Building_terragear-cs_in_Ubuntu_64|Compiler Terragear sous Ubuntu 64 bits]]
* [[FlightGear Package Manager]]
'''[[Portal:Developer|Plus...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Nouvelles</h2>
|-
|style="color:#000;"|
* [[FlightGear Newsletter {{MONTHNAME|{{LASTMONTHNAME}}}} {{CURRENTYEAR}}|Bulletin d'information de {{MONTHNAME|{{LASTMONTHNAME}}}} {{CURRENTYEAR}}]] ([[:Category:FlightGear Newsletter|archives]])

* '''January 25 2009:''' [[FlightGear 1.9.1]]
* '''December 22 2008:''' [[FlightGear 1.9.0]]
* '''October 27th 2008:''' [[World Scenery 1.01]]
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Image de la semaine</h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Le saviez-vous...</h2>
|-
|style="color:#000;"|
{{Did you know}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Promotion de FlightGear</h2>
|-
|style="color:#000;"|
* [[FlightGear Reviews|Évaluations de FlightGear]]
* [[FlightGear Videos|Vidéos de FlightGear]]

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[de:Hauptseite]]
[[en:Main Page]]
[[es:Portada]]
[[fi:Etusivu]]
[[nl:Hoofdpagina]]
[[pt:Página principal]]

Fr/Nouveau sur flightgear

2010-06-19T17:37:31Z

Xiii: Remove CVS references

''Certaines parties de cet article n'ont pas été mise à jours depuis 2008''

== Pour commencer ==
=== Configuration matériel ===
Pour que Flightgear tourne de façon fluide, il vous faut une carde graphique supportant les drivers OpenGL. OpenGL 2,0 ou plus récent est requis pour faire tourner FG 2,0 et les versions ultérieures. La plupart des ordinateurs modernes supportent OpenGL, mais si vous avez des problèmes avec un taux d'image par seconde trop bas, allez voir [[Hardware Recommendations]] pour plus d'informations.

=== Obtenir FlightGear ===
You may download the latest files from [http://www.flightgear.org/Downloads/ FlightGear Downloads] page. Choose the source or binary files appropriate for your particular system. Or, depending on level technical expertise you may choose the [[Git]] version if you wish to work with a development version of FlightGear. The Git version typically has more features and can be required by the some the latest developmental aircraft, but can be unstable and is more complicated to acquire and install.

=== Installer sur Windows ===
After installing FlightGear on Windows a dialog box appears to define file locations.

The first line asks for FlightGear Executable. Use the browse button to navigate to the location of fgfs.exe (in the default setup that is <tt>C:\Program Files\FlightGear\bin\win32\fgfs.exe</tt>).

The second line asks for [[$FG_ROOT|FlightGear Root]]. Use the browse button to navigate to the <tt>data/</tt> directory or enter the location of the 'data' directory (in the defualt setup that is <tt>C:\Program Files\FlightGear\data</tt>). This will populate the scenery box as well.

Once you have defined these default settings, continue the installation as explained below.

==== Installer sur Mac OS X ===
Installing [[FlightGear Mac OS X|FlightGear on Mac OS X]] is very simple. Just drag and drop the FlightGear icon to the <tt>/Applications</tt> folder. That's it. The first time you launch FlightGear, its icon on the Dock bounces for several seconds while loading aircraft and airport info. When the GUI launcher appears, select an aircraft and and airport by clicking the "Gear" buttons at the right of the names. Pressing "Start flight" will launch the simulator. You can configure more options using the GUI launcher. see http://macflightgear.sourceforge.net/home/documents/users-guide/ for more details.

If you want to launch flightgear using command-line, launch <tt>/Applications/Utilities/Terminal.app</tt> and type the following.

cd /Applications/FlightGear.app/Contents/Resources
./fgfs --options.....

The [[$FG_ROOT]] and [[$FG_SCENERY]] are not set on Mac OS X. If you want to specify these variables yourself for command-line use, run the followings on Terminal.app:

FG_ROOT=/Applications/FlightGear.app/Contents/Resources/data
FG_SCENERY=$FG_ROOT/Scenery

After launching the GUI launcher, you will have the alias to [[$FG_ROOT]] at $HOME/Documents/Flightgear/<version> so you can browse the data folder using Finder.

=== Configurer OpenGL ===
FlightGear runs best with current [[OpenGL]] video drivers. If you are having trouble running FlightGear smoothly, see [[Configuring OpenGL]] for more information.

=== Télécharger des scènes ===
A limited set of [[scenery]] comes installed with FlightGear, which consists of the area surrounding [[San Francisco International Airport|KSFO]].

In FlightGear, scenery is divided into two kinds of data: Objects and Terrain. Objects are the buildings, bridges and radio towers, etc. that represent three-dimensional structures. Terrain represents the contours, elevations and type of ground you fly over.

All object data goes in an Objects directory and all terrain data goes in a Terrain directory. The location of the scenery and its sub-directories depends on your particular installation.

To download Objects and Terrain for FlightGear, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page. On this page follow the link to download scenery from the map. Choose a block from the map where you will by flying. Once the package has downloaded, extract into your FlightGear scenery directory.

The scenery packages available from the FlightGear website contain both Objects and Terrain for the locations.

You may obtain additional and more up to date scenery Objects as they become available through the [http://scenemodels.flightgear.org/ FlightGear Scenery Database].

Information beyond this brief overview is available in [[Installing Scenery]] and [[Downloading New Flightgear Scenery for Windows XP]]

=== Télécharger des avions ===
To download additional [[aircraft]] for FlightGear individually, go to the FlightGear website and navigate to the [http://www.flightgear.org/Downloads/ Downloads] page, then choose [Aircraft Downloads http://flightgear.org/Downloads/aircraft-2.0.0/].

Once the aircraft package has downloaded, decompress and extract the archived files onto your computer. You may extract to a temporary directory and move them, or extract directly into the Aircraft directory in FlightGear. This is typically <tt>[[$FG_ROOT]]/data/Aircraft</tt>.

See also [[Installing Aircraft]] for more documentation.

=== Starting FlightGear ===
Many users choose to start FlightGear from the command line ("console" or "shell" as it is known to Unix users). Alternatively some use graphical interfaces such as [[FlightGear Launch Control|Fgrun]] (FlightGear Launch Control).

To start FlightGear type on the command line:

fgfs

and hit enter. This will start FlightGear.

If FlightGear fails to start, it is likely the compiled FlightGear binary software is not in your path. If you know Unix, you may add the location of the binary to your path and try starting again. Otherwise, you may find the location of the 'fgfs' binary and enter an absolute path to it like

/usr/games/fgfs

The location depends on your particular system and choices you made during compile and installation.

It is important to understand when not using a graphical interface to start FlightGear, your interaction will be entirely from the command line. To see available aircraft, you specify an option on the command line. To specify an aircraft, an airport, multiplayer server, etc. you add an option to the command line when starting FlightGear. Please consult the list of [[ Command Line Parameters ]]. The parameters are also useful to those starting FlightGear from [[ FlightGear Launch Control ]] graphical interface, as it allows you to specify parameters. If you are using FlightGear 1.0.0 this list may be useful [[FlightGear 1.0 aircraft names for command line]].

=== Montrer les avons disponibles ===
From the command line:

fgfs --show-aircraft

displays a list of available (installed) aircraft.

=== Choisir un avion ===
From the command line:

fgfs --aircraft=foo

where foo is the name of the folder the aircraft files live in. See also [[Command Line Parameters]].

=== Voler en multijoueur via internet ===
{{Main article|Howto: Multiplayer}}

=== Utiliser le clavier et la souris ===
Users with limited access to a [[joystick]] or other controllers sometimes use the keyboard or mouse to control their aircraft. Using the keyboard to fly can be difficult and the mouse is recommended over the keyboard. Other adjustments may be made with the keyboard.

To get help with keyboard commands, with FlightGear running, go to the Help [[Menubar|menu]], look under Basic Keys (for simulator related commands) and Common Aircraft Keys (for commands universal to all aircraft) and Aircraft Help for key commands specific to your aircraft. A chart displaying what each key does will display.

To use the mouse to fly the aircraft, right click and move the mouse to direct the aircraft, right click again to look around, click again to return to normal.

=== La première fois dans le cockpit ===
Finding your way around the cockpit can be daunting the first time.

Where is the 'virtual cockpit?' Not all FlightGear aircraft come with an interior, including a virtual cockpit. (Due to FlightGear being used by various research projects, some aircraft may not even come with an exterior model. Remember, FlightGear is very flexible.) A 2D panel may display over the 3d cockpit if one exists. You may turn this off using the View menu. Otherwise, you should be sitting in the virtual cockpit when FlightGear starts, as long as the Cockpit View is selected.

You may find it difficult to read some of the displays, dials and gauges on the instrument panel. Use the Zoom keys to zoom in on an instrument. The 'x' and Shift-X keys control eyepoint zoom in the Cockpit View. Use the joystick hat (or other controller assigned to this function) to pan the eyepoint to the instrument you wish to read. Then zoom in.

Alternate Method: Click the right mouse button until you get a cursor with two arrows (like this <=>). You can now move your view around the cockpit. Press 'x' and Shift-X to zoom in and out.

'''Note:''' Some functions, such as starter or magneto, may be difficult to use or lack "hotspots" to control with your mouse. Especially when flying an aircraft model that is still undergoing development. In this case, look for equivalent controls on a 2D panel or resort to the keyboard. The keyboard controls always work according to the assignments listed on the Help Menu (unless reassigned by an aircraft or configuration). Go to the main window menu, click Help, then click Basic Keys or Common Aircraft Keys.

One of the first steps I take on entering an unfamiliar cockpit is to press Ctrl-C to highlight all the "hotspots" on the 3d cockpit instrument panel. This enables you to easily see where to place the mouse to operate an instrument's controls, buttons, knobs, etc.

Many aircraft offer a help menu specific to that aircraft on the Aircraft Help menu (go to Help, then Aircraft Help.
[[File:[[File:Exemple.jpg]]]]

== Faire son premier vol ==
One of the most frequent questions novice pilots ask about any flight sim, but more so to FlightGear, is "why is my aircraft turning left all the time?" Although it could be due to wind gusts crossing the runway, it is more likely due to the increased realism FlightGear provides. In a certain other flight simulator, some settings are turned down to make the aircraft easier to fly. This reduces effects such as propeller torque and p-factor, which may be the cause of the tendency to turn to the left (to figure out which effect, you may read more in [[Understanding Propeller Torque and P-Factor ]]).

Despite marketing slogans to the contrary, some flight simulators are aimed at a casual game player market, and ship with their "realism" turned down. The realism is always turned up in FlightGear.

FlightGear offers a great deal of realism, which may be confusing to first time pilots.

* "Left Turning Syndrome" for the previously mentioned reasons.
* Compass Turning Error: A compass, when subjected to the forces of flight, tends to turn in the opposite direction for a brief period before settling on the correct heading. This is not a malfunction.
* The Vertical Speed Indicator is also subject to error.
* The Horizontal Situation Indicator is driven by a gyroscope (that is why it's sometimes called a Directional Gyroscope), which is subject to a phenomenon called gyro drift. For a number of reasons, the gyro will drift from its current heading and must be periodically (about every 15 minutes) calibrated to agree with the magnetic compass heading.

Many forces act on an aircraft in flight as well as on the instruments and systems used for control and navigation, and may be counter-intuitive. Pilots must learn to recognize these phenomena and compensate for their effects. FlightGear models instrument errors that exist in the real world.

=== Voler en utilisant l'aide électronique et le pilote automatique ===
To make this very clear for new users: Some aircraft require you to use the autopilot available from the Autopilot menu, which is the original FlightGear autopilot. This is a '''generic''' autopilot and as such, many aircraft come with their own '''specific''' autopilot, frequently a model of the real life one. '''For aircraft that provide their own autopilot in the cockpit, you must use the autopilot controls available in the virtual cockpit'''. This means clicking on the instrument panel in the virtual cockpit. The Autopilot menu will be grayed out and unavailable when the aircraft supplies its own autopilot (generally).

FlightGear, as of version 0.9.9, comes with a "built-in" autopilot. The Autopilot dialog accessible from the FlightGear toolbar in the main FlightGear window _does not work with all aircraft_. It only works with aircraft that a) do not specify an autopilot, or b) aircraft that use the default autopilot. When an aircraft does not specify an autopilot, the default is used.

For aircraft that supply their own autopilot, you must use the autopilot controls in the 2D or virtual cockpit. The Cessna comes with a KAP140 autopilot in its virtual cockpit. You _cannot use_ the Autopilot dialog with this aircraft. It has no effect. You must use the autopilot device in the panel.

For help with navigation see [[Understanding Navigation]]

=== Navigation et aéroports ===
When you first start FlightGear, whether from the command line or the graphical interface, you may wonder how to determine what airports are available. Fgrun displays a list of airports, but you will not see details such as Tower or ILS frequencies. You will not find a map showing VORs and their frequencies. Short of finding an actual sectional map for the area you wish to fly, what can you do?

[http://maps.google.com Google Maps] and the [[MPMap|FlightGear Online Map for multiplayers]] are both good resources as well as the FlightGear [http://fgfs.i-net.hu/modules/fgplanner/ Community Flight Planner].

== Obtenir de l'aide ==

=== Chat ===
The quickest way to get help with FlightGear is to join in the chat room [[FlightGear IRC channel]].

=== Groupe de discussion via courriel ===
The documentation for FlightGear is sketchy and undergoing constant change as new features are developed. This makes chat the best place to find answers to problems getting FlightGear to run.

=== Documents ===
The ways for users to get help with FlightGear are:

* Documents bundled with the release package.
* [http://flightgear.org/forums FlightGear Forum]
* [[FlightGear IRC channel]]
* [[Malinglists|FlightGear users mailing list]].

== Pour en savoir plus ==
This page is designed to give the user the essential things they need to know about using FG for the first time.

You now know enough to get started with FlightGear. To learn more, you may wish to start at the main page of this wiki and read the more detailed Getting Started section, or Using FlightGear section or study the Flying Resources to learn more about flight instruments and how to navigate and fly your aircraft.

Also, note that those using the Git version of FlightGear may choose to update their aircraft files through the Git system.

The following are some issues raised by new users of FlightGear. More detailed troubleshooting and answers can be found in [[Troubleshooting Problems]] and the [[FAQ]].

=== Je ne veux pas compresser flightgear que dois-je faire? ===
[http://www.flightgear.org/Downloads/ Our website] offers precompiled binaries for download and install on a variety of systems. Current platforms are Windows, Linux, Solaris, SGI, Mac OSX and FreeBSD. These are offered as a convienence and availablility may vary at times.

Note: FlightGear is highly configurable through editable [[XML]] files. You are free, and encouraged to, make changes to aircraft flight models and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. The flight model is not defined in a binary file. It is easy to modify (given enough knowledge). Although the install is binary, most of FlightGear's system is open to configuration through XML files and [[NASAL scripting]].

=== Est-ce qu'il y a un manuel a imprimé? ===
You are invited to read "[[The Manual]]" online as [http://www.flightgear.org/Docs/getstart/getstart.html HTML]
or download a [http://mapserver.flightgear.org/getstart.pdf PDF] for viewing with Acrobar Reader or printing.

"The Manual" is not always up to date with recent developments but provides a good start for beginners.

== Voulez-vous nous aider ? ==
{{Main article|Volunteer}}

=== Testeur ===
* [[Building Flightgear|Build]] the latest GIT code or download snapshots (link)
* File Bug Reports

=== Debugging & Profiling ===
* Running FlightGear via valgrind to track down memory leaks

=== Aider facilement la communauté ===
* Help new users with downloading, compiling, installing and running FlightGear (http://www.flightgear.org/forums or on IRC)
* Provide Ideas & Suggestions, see: [[Feature Requests / Proposals / Ideas]]
* Help clean up this wiki
* Help provide new contents for missing wiki pages

=== Développement ===
* Writing documentation! Everyone is welcome to contribute to "The Manual"; having at least a little experience with LaTeX makes the task easier. Please contact the authors of The Manual if you would like to add corrections or whole chapters, you may also simply use this wiki to contribute fixes, modifications and new contents.
* C/C++ Coding:
** provide source code cleanups (i.e. help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
** provide bug fixes [[Bugs]]
** provide enhanced features [[Feature Requests / Proposals / Ideas]]
** provide new features
** get involved in any of the other FlightGear-affiliated projects
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Scenery development

[[de:Neu bei FlightGear]]
[[es:Nuevo para FlightGear]]
[[fr:Nouveau sur flightgear]]
[[en:New to FlightGear]]

Fr/Accueil

2010-06-19T16:49:30Z

Xiii: remove CVS reference

{| style="width:100%; background:#efefef; margin-top:1.2em; border:1px solid #d9e2e2;"
|style="width:100%; color:#000"|


{| style="width:100%; border:solid 0px; background:none;"
|style="width:100%; text-align:center; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;">Bienvenue sur le Wiki de FlightGear !</div>
<div id="articlecount" style="width:100%; text-align:center; font-size:85%;">nous en sommes actuellement à [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>

[[file:de.gif|link=:de:Hauptseite]]
[[file:en.gif|link=:en:Main Page]]
[[file:es.gif|link=:es:Portada]]
[[file:fi.gif|link=:fi:Etusivu]]
[[file:fr.gif|link=:fr:Accueil]]
[[file:nl.gif|link=:nl:Hoofdpagina]]
[[file:pl.gif|link=:pl:Strona główna]]
[[file:pt.gif|link=:pt:Página principal]]
[[file:zh.gif|link=:zh:Main Page]]
|}


|style="width:11%; font-size:95%; color:#000;"|
|}
{|style="width:100%; background:none; margin:-.8em 0 -.7em 0;"
|style="font-size:95%; padding:10px 0; margin:0px; text-align:left; white-space:nowrap; color:#000;"| [[Help:Tutorial|Modifier]] '''·''' [[Help:Contents|Aide]]
|style="font-size:95%; padding:10px 0; margin:0px; text-align: right; white-space:nowrap; color:#000;"| [[Special:Allpages|Toutes les pages]] '''·''' [[Special:Search|Chercher
]]
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Flight Simulator</h2>
|-
|style="color:#000;"|
[[Image:FGlogo.jpg|left]] '''[[FlightGear]] Flight Simulator''' est un simulateur de vol open-source sophistiqué et fonctionnel, créé et maintenu entièrement par des volontaires. Le code source complet est accessible par [[GIT]], sous une licence libre [[GNU General Public License]]. La [[FlightGear 1.9.1|version 1.9.1]] de FlightGear date du 25 janvier 2009.

Le projet [[FlightGear]] propose un environnement de développement de simulateur de vol sophistiqué, pour une utilisation académique ou a des fins de recherche, il permet le développement d'autres idées intéressantes en simulation de vol, et est aussi accessible à l'utilisateur lambda. Toute personne intéressée peut [[Volunteer|contribuer]] à l'ajout de fonctionnalités ou à l'amélioration de FlightGear. Il existe de plus de nombreux [[FlightGear related projects|projets connexes]] ([http://www.flightgear.org/links.html projects]).

FlightGear est doté d'une documentation illustrée, parmi laquelle "Le Manuel", disponible en [http://mapserver.flightgear.org/getstart.pdf PDF] et [http://www.flightgear.org/Docs/getstart/getstart.html HTML]. Ce Wiki à été lancé en 2006, et couvre actuellement une bonne partie des sujets liés à FlightGear. La fonctionnalité multi-langue est plus récente (été 2009) et pour le moment seulement une petite partie est traduite.

'''Veuillez sélectionner un portail :'''

{|style="background:none;"
|style="font-size:95%; padding-left:10px; padding-right:20px; margin:0px; vertical-align: top; text-align:left; white-space:nowrap; color:#000;"|
* [[Portal:Developer|Développeur]]
** [[Portal:Developer/3D Modelers|Modélisation 3D]]
** [[Portal:Developer/Aircraft|Aéronef]]
** [[Portal:Developer/Scenery|Paysage]]
|style="font-size:95%; padding-left:20px; margin:0px; vertical-align: top; text-align: left; border-left: 2px solid #d9e2e2; white-space:nowrap; color:#000;"|
* [[fr/Portal:Utilisateur|Utilisateur]]
* [[Portal:Pilot|Pilote]]
|}

===== '''Si vous êtes nouveau ici, jetez un oeil sur le [[Help:Contents|manuel]] avant de créer ou d'éditer un article!''' =====
|-
|}
|}


{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Pour commencer</h2>
|-
|style="color:#000;"|
* [[:fr:Foire aux questions|FAQ]]
* [[:fr:Howto: Débarrassez-vous des erreurs les plus fréquentes|Messages d'erreur communs]]
* [[:fr:Howto: Multijoueur|Multijoueur]]
* [[:fr:Nouveau sur flightgear|Introduction à FlightGear]]
* [[Troubleshooting Problems|Dépannage]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Utilisation de FlightGear</h2>
|-
|style="color:#000;"|
* [[:fr:Avions|Aéronefs]]
* [[:fr:Piloter l'hélicoptère|Piloter l'hélicoptère]]
* [[:fr:Table des modèles|Liste des modèles]]
'''[[Portal:User|Plus...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Développement de FlightGear</h2>
|-
|style="color:#000;"|
* [[:fr:Compiler FlightGear sous GNU/Linux|Compiler FlightGear]]
* [[Building_terragear-cs_in_Ubuntu_64|Compiler Terragear sous Ubuntu 64 bits]]
* [[FlightGear Package Manager]]
'''[[Portal:Developer|Plus...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Nouvelles</h2>
|-
|style="color:#000;"|
* [[FlightGear Newsletter {{MONTHNAME|{{LASTMONTHNAME}}}} {{CURRENTYEAR}}|Bulletin d'information de {{MONTHNAME|{{LASTMONTHNAME}}}} {{CURRENTYEAR}}]] ([[:Category:FlightGear Newsletter|archives]])

* '''January 25 2009:''' [[FlightGear 1.9.1]]
* '''December 22 2008:''' [[FlightGear 1.9.0]]
* '''October 27th 2008:''' [[World Scenery 1.01]]
|-
|}
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Image de la semaine</h2>
|-
|style="color:#000;"|
{{POTW/{{CURRENTYEAR}}-{{CURRENTWEEK}}}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Le saviez-vous...</h2>
|-
|style="color:#000;"|
{{Did you know}}
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Promotion de FlightGear</h2>
|-
|style="color:#000;"|
* [[FlightGear Reviews|Évaluations de FlightGear]]
* [[FlightGear Videos|Vidéos de FlightGear]]

|-
|}
|}

__NOTOC__
__NOEDITSECTION__

[[de:Hauptseite]]
[[en:Main Page]]
[[es:Portada]]
[[fi:Etusivu]]
[[nl:Hoofdpagina]]
[[pt:Página principal]]

Livery over MP

2010-06-19T16:45:38Z

Xiii: remove CVS reference

[[Image:Livery_selection_dialog.jpg|thumb|270px|The livery selection dialog of the [[Sikorsky S76C]].]]

On this page we describe how you make use of a script to get a '''livery selection dialog''' for a [[Aircraft|plane]] in [[FlightGear]]. To get new liveries, you need to have them available with this script.

'''If you want to add a new livery to a plane that already makes use of the livery select system, you'll only have to follow the steps under [[#Models/Liveries|Models/Liveries]].'''

==Files==
There are a few files we need to make (or edit), namely:
* <tt>dr400-set.xml</tt>
* <tt>Models/dr400.xml</tt>
* <tt>Nasal/liveries.nas</tt>
We also have to make a new directory to store our liveries in. Let's make it <tt>Aircraft/DR400/Models/Liveries</tt>.

===Models/Liveries===
For every livery we need to make a file. Let's say we got a Rescue livery, we then need to make a file called Rescue.xml in our <tt>Models/Liveries</tt> directory. When a particular livery gets selected, its XML file is copied to the aircraft's property tree. On the pilot's side this is the main property tree <tt>/</tt>, and on all remote machines on the MP network it's one of the multiplayer branches in <tt>/ai/models/multiplayer[]</tt>. The structure of livery XML files is completely free. There just has to be a property containing a name for the selection dialog, and <tt>aircraft.livery.init()</tt> must be told which it is. By default it is <tt>sim/model/livery/name</tt>.

<?xml version="1.0"?><nowiki>
</nowiki>
<PropertyList>
<sim>
<model>
<livery>
<name type="string">Default</name>
<texture>texture.rgb</texture>
</livery>
</model>
</sim>
</PropertyList>

===Models/dr400.xml===
The first part is related to the nasal script. <tt>("Aircraft/DR400/Models/Liveries");</tt> points FlightGear to the directory where we store our liveries. This is a different directory for every plane, but there should be only one folder for one plane, containing all the liveries for that plane. Add the following code to your models .xml file:

<nasal>
<load>
var livery_update = aircraft.livery_update.new("Aircraft/DR400/Models/Liveries");
</load><nowiki>
</nowiki>
<unload>
livery_update.stop();
</unload>
</nasal>

The second part is very important and probably the hardest of all. We need to set which parts of the model should change when you select a new livery. To find the object-names, you could make use of software like [[Blender]] or [[AC3D]]. The <tt><texture>S76livery.rgb</texture></tt> part points FlightGear to the livery that should be shown on startup.

'''Warning: be sure you don't have a slash (/) in front of sim/model/livery in the <property-base> tag! Otherwise, all planes will get the same livery!'''

<animation>
<type>material</type>
<object-name>LHgeardoor</object-name>
<object-name>RHgeardoor</object-name>
<object-name>S76C</object-name>
<object-name>RF.door</object-name>
<object-name>LF.door</object-name>
<object-name>Rr.Door</object-name>
<object-name>Lr.Door</object-name>
<object-name>RHbaggage</object-name>
<object-name>LHbaggage</object-name>
<object-name>RHfrtgeardoor</object-name>
<object-name>LHfrtgeardoor</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>texture.rgb</texture>
</animation>

===Nasal/liveries.nas===
The only thing you might change in the nasal file is the directory of the liveries. If you don't have the livery name in <tt>sim/model/livery/name</tt>, then you have to add this as second function argument.

aircraft.livery.init("Aircraft/DR400/Models/Liveries");

===dr400-set.xml===
The follow part is really important. If this is not included, the livery changes will not be visible over MP!

<model>
<path>Aircraft/DR400/models/dr400.xml</path>
<livery>
<file type="string"/>
</livery>
</model>

If you want the default livery be something else than the first in the list, replace the file type part with the following, containing the Models/Liveries/....xml file name of the approperiate livery.

<file type="string">ANA</file>

To make a nice button in the [[menubar]] we need to add the following code, just above the <tt></sim></tt> tag.

<menubar>
<default>
<menu n="100">
<label>Robin DR 400</label>
<enabled type="bool">true</enabled>
<item>
<label>Select Livery</label>
<binding>
<command>nasal</command>
<script>aircraft.livery.dialog.open()</script>
</binding>
</item>
</menu>
</default>
</menubar>

==Multiple texture files per livery==
Some models use multiple textures file (eg. seperate files for wings and fuselage). Every texture needs it own property. You can add as many textures as you like.

The given examples are based on the [[Boeing 787]].

===Models/Liveries===
Instead of just one texture we have to deal with multiple ones now.

<?xml version="1.0"?><nowiki>
</nowiki>
<PropertyList>
<sim>
<model>
<livery>
<name type="string">All Nippon Airways</name>
<texture>ANA-Livery.rgb</texture>
</livery>
<lights>
<texture>ANA-Lights.rgb</texture>
</lights>
</model>
</sim>
</PropertyList>

Remember the names (<livery> and <lights>), as you will need them in the model file in the next step.

===Models/787.xml===
<animation>
<type>material</type>
<object-name>wipers</object-name>
<property-base>sim/model/livery</property-base>
<texture-prop>texture</texture-prop>
<texture>ANA-Livery.rgb</texture>
</animation>

<animation>
<type>material</type>
<object-name>lightedfin_0</object-name>
<property-base>sim/model/lights</property-base>
<texture-prop>texture</texture-prop>
<texture>ANA-Lights.rgb</texture>
</animation>

===Performance Improvements===
For livery changing it seems to be important to parent all objects with the same texture. In Blender select all objects and press "ctr-p" to make it parent to the last selected. E.g.: fuselage and doors with the same texture: select at first the doors and then at last the fuselage and press "ctr-p".

Also prevent transparency where possible- it will prevent lags during switching the views. See also the f14b as an very good example!

==Testing==
To ensure that your livery setup works correctly over MP, start two instances of FlightGear locally, one with

fgfs --multiplay=out,10,localhost,5702 --multiplay=in,10,localhost,5701

and one with

fgfs --multiplay=out,10,localhost,5701 --multiplay=in,10,localhost,5702

==Sharing your liveries==
Ofcourse you want other people to use and enjoy your liveries as much as you do. Therefore, other users should be able to download them.

We have some FlightGear hosts, where you can upload your liveries to:
* [http://liveries.flightgear.org FlightGear Liveries] largest FG repository with (almost) all available liveries, based on real aircraft.
* [http://unitedfreeworld.com UnitedFreeWorld] repository with lots of liveries (and scenery/aircraft), both realistic and fictional.

[[Category:Aircraft enhancement]]
[[Category:Modeling]]
[[Category:Menubar]]

Howto:Carrier

2010-06-19T16:42:42Z

Xiii: typo

==Features==
[[Image:Carrier3.jpg|thumb|300px|The Nimitz carrier in the San Fransisco bay]]

* Start FG with your chosen aircraft placed on the aircraft carrier "Nimitz" or "Eisenhower"
* Engage the launchbar in the steam catapult
* Have the carrier set course into the prevailing wind direction and attempt to get wind speed over the deck at a suitable value for launch
* Launch from the deck when ready
* Set the TACAN reciever in the aircraft to Nimitz's channel (029Y) and have the heading and range to the carrier displayed on the cockpit instruments
* Land on the deck and be halted by the arrestor cables
* Taxi onto the deck elevators, operate them and park on the hangar deck (0.9.10 and later)

You can start FlightGear with the command line or GUI. To position your [[aircraft]] on the carrier at startup, use the following [[Command Line Parameters|command line options]]. Note the upper-case "N" in Nimitz and the fact that the scenario comes in front of carrier! You can copy-paste this (he slash will make it look like one line):
fgfs \
--ai-scenario=nimitz_demo
--carrier=Nimitz \
--aircraft=seahawk \

Note that several FG aircraft are carrier capable, but the [[Hawker Seahawk|Seahawk]] is possibly the easiest to fly to begin with.

If you are using the Windows or OSX launcher to run FG, you should find a text entry box in the gui that allows you to specify command line options, add the above options there. Linux or Cygwin users can just add them to their usual startup command; ``fgfs --carrier=Nimitz --aircraft=seahawk'. Please note the uppercase ``N' in ``Nimitz'.

In the [[FlightGear Wizard]]: go to Advanced... > Properties and make a new property with
sim/ai/scenario[0]=nimitz_demo --carrier=Nimitz

With version 1.0.0 there comes a special box for the carriers on the Airport selection page of the Wizard.

==Takeoff==
[[Image:Carrier1.jpg|thumb|300px|The [[Hawker Seahawk|Seahawk]] aircraft ready for takeoff]]
Once FlightGear has started, you should ensure that the parking brakes are off, ease the plane a little way down the catapult pressing ``L' to engage the launchbar (this might be best done from an external view initially.) You should notice the aircraft being pulled into alignment with the catapult and see the strops appear and hold down the aircraft. This will only happen if your aircraft is close enough to the correct spot on the catapult; as a rough guide, for the default parking position the seahawk's nose should be rougly level with the deck observation bubble.

To get the carrier into as good a position as possible for launch, select the ``ATC/AI' menu, then check the ``Turn into wind' box under the ``AI Carrier' section.

You should now notice the carrier begin to pick up speed and turn into the wind, and naturally the deck may tilt somewhat as it turns. You should wait for this maneuver to finish and the deck to return to level before moving on to the next stage.
[[Image:Carrier6.jpg|thumb|300px|'''1:''' The takeoff part of the carrier with the catapults
'''2:''' The land part of the carrier with the wires]]
Being engaged to the catapult, you should spool up the engines to full power, ensure the brakes are off and that all flight controls are in a suitable position for launch. When ready, press ``C' to release the catapult. Your aircraft will be hurled forward off the deck, and you should be able to raise the undercarriage and climb slowly away, being careful to avoid stalling.

==Land==
Actually finding the carrier in a vast expanse of open water can be very difficult, especially if visibility is poor. To assist with this task, the carriers are equipped with [[TACAN]], which allows a suitably-equipped aircraft (Seahawk at present) to obtain a range and bearing to the carrier. First, you must set the appropriate TACAN channel, 029Y in this case, in the radios dialogue (ctrl-r or choose Equipment/Radio Settings from the FG [[menubar]]). You should, if within range, notice the DME instrument show your distance from the carrier, and the ADF instrument (next to the DME in the seahawk) should indicate a bearing to the carrier. Turn to the indicated heading and you should see the DME dial indicate your closing in on the carrier.

{|
! Carrier || Scenario || TACAN
|-
| Nimitz || nimitz_demo || 029Y
|-
| Eisenhower || nimitz_demo || 030Y
|-
| Clemenceau || clemenceau_demo || 026Y
|-
| Foch || foch_demo || 026X
|-
| Akagi || akagi || N/A
|}

This is the most difficult part of the operation, as in real life. You might well find Andy Ross' [[A-4F Skyhawk Operations Manual]] useful here. Basically, though, you should use the TACAN to locate the carrier, and line up with the rear of the deck. As this part of the deck is at an angle to the course of the vessel, you may need to correct your alignment often. Ensure that the aircraft is in the correct configuration for approach (the Help/Aircraft Help menu should contain useful data for your aircraft) and that the gear and the arrestor hook are down.
[[Image:Carrier5.jpg|thumb|300px|The Fresnel Lens Optical landing System]]
As you approach you should see, on the left hand side of the deck, a set of brightly coloured lights - called the Fresnel Lens Optical landing System (FLOLS). This indicates your position on the landing glideslope. You will see a horizontal row of green lights, and when approximately on the glideslope, an orange light ( known in some circles as the ``meatball') approximately in line with the green lights. When approaching correctly, the meatball appears in line with the green lights. If you are high it is above, and when low it is below. If you are very low the meatball turns red. If you fly to keep the meatball aligned you should catch number 3 wire.

Carrier landings are often described as ``controlled crashes' and you shouldn't waste your time attempting to flare and place the aircraft gently on the deck like you would with a conventional landing - ensuring that you catch the wires is the main thing.

Immediately your wheels touch the deck, you should open the throttles to full power, in case you have missed the wires and need to ``go around' again; the wires will hold the aircraft if you have caught them, even at full power.

If you wish, you can then (with 0.9.10 and later) raise the elevators from the ATC/AI menu, taxy onto one of the elevators, lower it (uncheck the box on the menu and don't worry, they are VERY slow...) and taxy off into the hangar.

Don't be discouraged if you don't succeed at first with carrier landings - it's not an easy maneouver to master. If after a little practice you find the Seahawk too easy, you could move on to the Seafire for more of a challenge!

==Related content==
* [[Carrier over MP]] to find out how you could control the carrier and/or use the carrier over the multiplayer network.

[[Category:Howto|Carrier]]

Howto:Carrier

2010-06-19T16:41:28Z

Xiii: Remove old status statement, kill CVS references, anonymify :-) well, put an A-6E on the deck and AJ comes back.

==Features==
[[Image:Carrier3.jpg|thumb|300px|The Nimitz carrier in the San Fransisco bay]]

* start FG with your chosen aircraft placed on the aircraft carrier "Nimitz" or "Eisenhower"
* Engage the launchbar in the steam catapult
* Have the carrier set course into the prevailing wind direction and attempt to get wind speed over the deck at a suitable value for launch
* Launch from the deck when ready
* Set the TACAN reciever in the aircraft to Nimitz's channel (029Y) and have the heading and range to the carrier displayed on the cockpit instruments
* Land on the deck and be halted by the arrestor cables
* Taxi onto the deck elevators, operate them and park on the hangar deck (0.9.10 and later)

You can start FlightGear with the command line or GUI. To position your [[aircraft]] on the carrier at startup, use the following [[Command Line Parameters|command line options]]. Note the upper-case "N" in Nimitz and the fact that the scenario comes in front of carrier! You can copy-paste this (he slash will make it look like one line):
fgfs \
--ai-scenario=nimitz_demo
--carrier=Nimitz \
--aircraft=seahawk \

Note that several FG aircraft are carrier capable, but the [[Hawker Seahawk|Seahawk]] is possibly the easiest to fly to begin with.

If you are using the Windows or OSX launcher to run FG, you should find a text entry box in the gui that allows you to specify command line options, add the above options there. Linux or Cygwin users can just add them to their usual startup command; ``fgfs --carrier=Nimitz --aircraft=seahawk'. Please note the uppercase ``N' in ``Nimitz'.

In the [[FlightGear Wizard]]: go to Advanced... > Properties and make a new property with
sim/ai/scenario[0]=nimitz_demo --carrier=Nimitz

With version 1.0.0 there comes a special box for the carriers on the Airport selection page of the Wizard.

==Takeoff==
[[Image:Carrier1.jpg|thumb|300px|The [[Hawker Seahawk|Seahawk]] aircraft ready for takeoff]]
Once FlightGear has started, you should ensure that the parking brakes are off, ease the plane a little way down the catapult pressing ``L' to engage the launchbar (this might be best done from an external view initially.) You should notice the aircraft being pulled into alignment with the catapult and see the strops appear and hold down the aircraft. This will only happen if your aircraft is close enough to the correct spot on the catapult; as a rough guide, for the default parking position the seahawk's nose should be rougly level with the deck observation bubble.

To get the carrier into as good a position as possible for launch, select the ``ATC/AI' menu, then check the ``Turn into wind' box under the ``AI Carrier' section.

You should now notice the carrier begin to pick up speed and turn into the wind, and naturally the deck may tilt somewhat as it turns. You should wait for this maneuver to finish and the deck to return to level before moving on to the next stage.
[[Image:Carrier6.jpg|thumb|300px|'''1:''' The takeoff part of the carrier with the catapults
'''2:''' The land part of the carrier with the wires]]
Being engaged to the catapult, you should spool up the engines to full power, ensure the brakes are off and that all flight controls are in a suitable position for launch. When ready, press ``C' to release the catapult. Your aircraft will be hurled forward off the deck, and you should be able to raise the undercarriage and climb slowly away, being careful to avoid stalling.

==Land==
Actually finding the carrier in a vast expanse of open water can be very difficult, especially if visibility is poor. To assist with this task, the carriers are equipped with [[TACAN]], which allows a suitably-equipped aircraft (Seahawk at present) to obtain a range and bearing to the carrier. First, you must set the appropriate TACAN channel, 029Y in this case, in the radios dialogue (ctrl-r or choose Equipment/Radio Settings from the FG [[menubar]]). You should, if within range, notice the DME instrument show your distance from the carrier, and the ADF instrument (next to the DME in the seahawk) should indicate a bearing to the carrier. Turn to the indicated heading and you should see the DME dial indicate your closing in on the carrier.

{|
! Carrier || Scenario || TACAN
|-
| Nimitz || nimitz_demo || 029Y
|-
| Eisenhower || nimitz_demo || 030Y
|-
| Clemenceau || clemenceau_demo || 026Y
|-
| Foch || foch_demo || 026X
|-
| Akagi || akagi || N/A
|}

This is the most difficult part of the operation, as in real life. You might well find Andy Ross' [[A-4F Skyhawk Operations Manual]] useful here. Basically, though, you should use the TACAN to locate the carrier, and line up with the rear of the deck. As this part of the deck is at an angle to the course of the vessel, you may need to correct your alignment often. Ensure that the aircraft is in the correct configuration for approach (the Help/Aircraft Help menu should contain useful data for your aircraft) and that the gear and the arrestor hook are down.
[[Image:Carrier5.jpg|thumb|300px|The Fresnel Lens Optical landing System]]
As you approach you should see, on the left hand side of the deck, a set of brightly coloured lights - called the Fresnel Lens Optical landing System (FLOLS). This indicates your position on the landing glideslope. You will see a horizontal row of green lights, and when approximately on the glideslope, an orange light ( known in some circles as the ``meatball') approximately in line with the green lights. When approaching correctly, the meatball appears in line with the green lights. If you are high it is above, and when low it is below. If you are very low the meatball turns red. If you fly to keep the meatball aligned you should catch number 3 wire.

Carrier landings are often described as ``controlled crashes' and you shouldn't waste your time attempting to flare and place the aircraft gently on the deck like you would with a conventional landing - ensuring that you catch the wires is the main thing.

Immediately your wheels touch the deck, you should open the throttles to full power, in case you have missed the wires and need to ``go around' again; the wires will hold the aircraft if you have caught them, even at full power.

If you wish, you can then (with 0.9.10 and later) raise the elevators from the ATC/AI menu, taxy onto one of the elevators, lower it (uncheck the box on the menu and don't worry, they are VERY slow...) and taxy off into the hangar.

Don't be discouraged if you don't succeed at first with carrier landings - it's not an easy maneouver to master. If after a little practice you find the Seahawk too easy, you could move on to the Seafire for more of a challenge!

==Related content==
* [[Carrier over MP]] to find out how you could control the carrier and/or use the carrier over the multiplayer network.

[[Category:Howto|Carrier]]

Grumman F-14 Tomcat

2010-06-19T16:34:58Z

Xiii: kill CVS definitively

{{infobox Aircraft
|image =F-14.jpg
|name =F-14 Tomcat
|type =Interceptor/multi-role Fighter aircraft
|livery =U.S. Navy
|authors =Enrique Laso, Alexis Bory (cockpit)
|status =Production
|fdm =YASim
|3dcockpit = √
|carrier = √
|fgname = f-14b
}}
The '''Grumman F-14 Tomcat''' is a supersonic, twin-engine, two-seat, variable geometry wing [[aircraft]]. The F-14 was the United States Navy's primary maritime air superiority fighter, fleet defense interceptor and tactical reconnaissance platform from 1974 to 2006. It later performed precision strike missions once it was integrated with the Low Altitude Navigation and Targeting Infrared for Night [http://en.wikipedia.org/wiki/LANTIRN LANTIRN] system. The F-14 was developed after the collapse of the [http://en.wikipedia.org/wiki/F-111B F-111B] project, and was the first of the American teen-series fighters which were designed incorporating the experience of air combat in Vietnam against MiGs.

It entered service in 1972 with the U.S. Navy, replacing the [[McDonnell F4 Phantom II]]. It was later exported to the former Imperial Iranian Air Force in 1976, during a time when the US still had good relations with Iran. It was retired from the active U.S. Navy fleet on 22 September 2006, having been replaced by the [[F/A-18 Hornet|F/A-18E/F Super Hornet]]. As of 2007, it remains in service only with the Islamic Republic of Iran Air Force.

==Keyboard Controls==
===Flight Controls===
{| class="prettytable"
|Home
|Increase elevator trim
|-
|End
|Decrease elevator trim
|-
|] or f
|Lower flaps
|-
|[ or F
|Raise flaps
|-
|s
|Increase speed brakes
|-
|S
|Decrease speed brakes
|-
|Ctrl-b
|Toggle speed brakes
|-
|k
|Increase speed brakes
|-
|j
|Decrease speed brakes
|-
|}

[[Image:F-14_cockpit.jpg|thumb|270px|Cockpit of the F-14.]]
[[File:SunsetF-14.png|270px|thumb|right|A nice scene with the F-14.]]

===Automatic Flight Controls===
{| class="prettytable"
|a
|Toggle APC (Landing Automatic Power Control)
|-
|Ctrl-d
|Toggle DLC (Landing Direct Lift Control)
|-
|d
|DLC increase
|-
|D
|DLC decrease
|-
|Ctrl-t
|Toggle [http://en.wikipedia.org/wiki/Aircraft_flight_control_systems AFCS] (Defaut Attitude Mode)
|-
|Ctrl-a
|Enable AFCS Altitude Mode
|-
|*
|Engage AFCS Altitude Mode
|-
|Ctrl-h
|Enable AFCS Heading Mode
|-
|Ctrl-s
|Toggle ground spoilers armed
|}

===HSD - radar and RWR===
{| class="prettytable"
|h
|Cycles through HSD modes: radar - compas - ECM (RWR)
|-
|E
|Decrease Radar Range
|-
|R
|Increase Radar Range
|-
|Ctrl-r
|Toggles Radar Standby Mode. In standby mode the radar doesn't emit and the "STAND BY" words are displayed on the HSD screen when in TID mode.
|}

===Carrier operations===
{| class="prettytable"
|O
|Lower the hook
|-
|o
|Raise the hook
|-
|L
|Engage launch bar
|-
|C
|Release catapult
|-
|}

===Miscellaneous===
{| class="prettytable"
|e
|Toggle canopy and access ladder
|-
|u
|Toggle refuelling probe
|-
|w
|Cycle armament selector
|-
|Ctrl-o
|Toggle oversweep (on ground only, otherwise sweep is automatic)
|-
|Ctrl-v
|Toggle between RIO (Radar Intercept Officer) and pilot view
|-
|}

==Aircraft help==
===On Shore Takeoff===
* With wings on over sweep position (parking position) the elevator command is inhibited... just in case...
* Check air brake in.
* Fuel level: The Flightgear F-14 has a '''10% fuel''' level and no external load '''at start up'''. This means the aircraft will be very light and have a strong tendency to raise the nose when accelerating on the runway. With less weight on the nose wheel, the nose wheel steering loose its efficiency. If the pilot use afterburners for take off, the loose of nose wheel steering efficiency is increased (afterburners are not necessary for take off). '''Set a suitable fuel level before take off.'''
* Flaps: Set full flaps.
* Elevators: The pilot will need to maintain a correct (leveled) attitude using the stick. Push the stick forward to prevent nose pitching up at the beginning of the take off run, release slightly as speed increase, pull smoothly when reaching rotation speed (150kts).
* Rudder: Currently the FDM use a small rudder rate of move to damp some nasty oscillations when the rudder is not moved enough smoothly. '''If not anticipated''', this delay will cause overshooting the desired rudder effect, then a strong counter action on the rudder will be applied by the pilot on the rudder with again an overshoot... That's a typical [http://en.wikipedia.org/wiki/Pilot-induced_oscillation pilot-induced oscillation]. To avoid this set a small amount of rudder, wait for the effect, see if it's enough, then add a small amount of rudder again if needed... when doing so the pilot will prefer increasing the power smoothly. Now the aircraft will quickly gain speed while covering the runway and the rudder effect will increase, thus decreasing the needed delay and the amount of pressure on the stick to match the desired effect.

===Autopilot Operation===
* The main mode is '''Attitude Hold Mode''', '''Ctrl-t'''. Other Modes need this main mode activated before being selected. Switching off '''Attitude Mode''' disables all other modes . When in '''Attitude Mode''', the autopilot disengages whenever a certain pressure is put on the stick, and it reengages when the stick is back in the center position . '''Attitude Hold Mode''' will hold pitch attitudes up to plus or minus 30 degrees, and bank angles up to plus or minus 60 degrees.
* It shall be switched off for aerobatics and inverted flight .

====Autopilot Altitude Mode====
* Once in the Attitude Mode, you can select '''Altitude Mode''' by hitting '''Ctrl-a''', then the '''AP REF''' indicator, (left of the '''VDI''') will illuminate, when at the desired altitude using normal stick control, engage by hitting '''*''', (asterisk) . The autopilot will then maintain your altitude.
'''CAUTION''' - at high speeds, it is imperative to stabilize your aircraft prior to engaging Altitude Mode !

====Autopilot Heading Mode====
* Once in the Attitude Mode, you can select '''Heading Mode''' by hitting '''Ctrl-h''' . After maneuvering the aircraft into the desired reference heading, release the control stick at a bank angle of less than 5 degrees . The autopilot will then hold the aircraft on the selected heading.

* Autopilot needs '''SAS''' channels to be engaged, which is the default . '''SAS''' Pitch and Roll channels may be disengaged by actuating switches located on the '''AFCS''' ('''Automatic/Analog Flight Control System''') panel .[[Image:F-14b-sas-switches.png|thumb|270px|SAS Panel.]]

===Landing Automatic Power Control, (APC) Operation===
* The '''APC''' is a closed loop system that automatically regulates basic engine thrust to maintain the aircraft at an optimum approach angle of attack for landing .
* Prior to engage '''APC''', gear handle must be down with weight off wheels, and the throttles must be set between 98 percent rpm and 68 percent rpm, (as shown on the panel gauges).
* Type '''a''' to toggle the '''APC on/off'''. APC is also disengaged by setting the throttles to MIL, (98 percent rpm) or idle, (68 percent rpm) or raising the landing gear handle or when weight on the wheels .
* When disengaged the '''AUTO THROT''' caution light, (on the left side of the HUD) illuminates for 10 seconds .

===Landing Direct Lift Control, (DLC) Operation===
* During landing approaches, the spoilers and horizontal stabilizers can be controlled simultaneously to provide glidepath correction without changing power setting or angle of attack.

===Ground Spoilers Operation===
* Ground spoilers (that is [http://en.wikipedia.org/wiki/Elevon elevons] used as air-brake ) provide additional drag immediately after the touch down. Before the landing, arm the ground spoilers by hitting '''Ctrl-s''' . After the aircraft hits the runway, pull the throttle to idle, then the spoilers (elevons) get fully deployed.

==Pilot's Cockpit==
[[Image:F-14b-pilots-display-control-panel.jpg|thumb|270px|Pilot's Display Control Panel.]]
===Displays Control Panel===
* The Display Control Panel is located on the right side of the pilot's main panel, under the Hook lever. The '''3 botom switches''' respectively turn the '''VDI''', '''HUD''' and '''HSD''' displays '''on/off'''. The '''HSD MODE''' switch is also available, it selects '''NAV''' or '''TID''' or '''ECM''' mode. This can also be achieved by cycling through these 3 modes with the "'''h'''" key. (''Note: the '''NAV MODE''' push buttons - '''TO''', '''CRUISE''', '''A/A''', '''A/G''', '''LDG''' - are not operational yet.'')
** '''VDI: Vertical Display Indicator'''. Shows the aircraft attitude in roll and pitch, with an artifitial horizon and magnetic heading.
** '''HUD: Head UP Display'''.
** '''HSD: Horizontal Situation Display'''. HSD shows either:
***in '''NAV''' mode: compas with navigation indications,
***in '''TID''' mode (Tactical Information Display): an horizontal representation of the tactical situation (that is informations provided by the RIO from what he sees in his radar displays).
***in '''ECM''' mode: a representation of radar threats around the aircraft.

===VHF===
* Located on the RIO's left console, 3 bands: 30-88 MHz, 108-174 MHz, 225-400 MHz. Modes '''TR''' and '''TR-G''' set '''COMM1'''. Mode '''DF''' sets '''NAV1''', that is '''Direction Finder''' displayed with the single needle in both '''BDHIs''' (Bearing, Distance, Heading Indicator) . You have Comm *or* DF. Storing frequencies (up to 20 channels) '''a - PRESET''' select the desired channel, '''b - READ''' tune the desired frequency, '''c - LOAD''' stores the frequency in the previously selected channel.

===UHF===
* Located on the pilot's left console, 225-400 Mhz. ADF is not enabled on this radio.

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
=== Links ===
* http://en.wikipedia.org/wiki/F-14 - F-14 Tomcat
* http://www.globalsecurity.org/military/systems/aircraft/f-14.htm - F-14 Tomcat
* http://www.fas.org/programs/ssp/man/uswpns/air/fighter/f14.html - F-14 Tomcat
* http://www.anft.net/f-14/f14-specification.htm - Home of M.A.T.S.
* http://www.navyair.com/LSO_NATOPS_Manual.pdf - NATOPS LANDING SIGNAL OFFICER MANUAL

{{Grumman}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]

AI Systems

2010-04-03T19:55:52Z

Xiii: typo

{{Out of date}}

Read the latest document at http://cvs.flightgear.org/viewvc/data/Docs/AI_doc.html?view=markup

== AI Systems in FlightGear ==
[[FlightGear]] has a number of more or less independently operating systems for simulating semi- intelligent interaction with the environment. Because there oftentimes exists some confusion regarding to which system does what, one should take notice of the differences between them: The major distinction is that between an older ATC/AI system, and a newer AIModels system. The AIModels system can, in turn, be controlled in at least three different ways; directly, using a script, through the multiplayer system, and through a subsystem known as the traffic manager.

To enable/disable the ATC/AI system: use --prop:/sim/ai-traffic/enabled=[1|0]
To enable/disable the AIModels system: use --prop:/sim/ai/enabled=[1|0]

== ATC/AI ==
The [[ATC|Air Traffic Control]] system simulates interaction between the user and a number of AI controlled cessna and piper aircraft. This system can be controlled using the GUI from within FlightGear. The ATC/AI system is no longer maintained and marked for deprecation. Recent reports have indicated that the ATC/AI system may be causing numerical computation problems in some cases, resulting in a flurry of NaN warning messages on the FlightGear console. If you experience this, you might consider shutting down the ATC/AI system

For airports with a tower frequency, if that frequency is tuned in to your radio, you may contact ATC.

To obtain the tower frequencies for an airport within range of ATC, go to the ATC/AI menu, choose Frequencies to display the dialog. If there are any airports within 40nm range, a button with the airport designation will appear. Click see the frequencies. Tune the tower frequency in on the COM1 radio and then hit the single quote key to open the ATC window.

Points:
* Untowered airports are not supported in any way by ATC.
* You must be within 40 nautical miles of an ATC facility (towered airport with tower frequencies) to contact ATC.

== AI Models ==
Starting with FlightGear version 0.9.4 you can place AI objects in the "FlightGear world". In version 0.9.4 the AI objects can be defined in the preferences.xml file, or in an airplane's *-set.xml file. In later versions they are defined in a "scenario file" only. The types of AI objects you can have are airplanes, ships, thunderstorms, thermals/sinks, static and ballistic objects. AI objects have some things in common: The have a location in the "FlightGear world", they can have an associated exterior 3D model, and they can move according to an internal [[FDM]] (flight dynamics model). As of now, these objects are created at simulator start-up by adding some XML code to a scenario file. The scenario file must be in the data/AI directory. You select which scenario files you want to use by naming it in the preferences.xml file. The preferences.xml file has an entry that looks like this (FlightGear versions newer than 0.9.4, including CVS):

<ai>
<enabled type="bool">true</enabled>
<scenario>aircraft_demo</scenario>
</ai>

The above bit of XML enables the AI system and selects a scenario file called aircraft_demo.xml.

''Notes:
*XML tags are <i>case-sensitive</i>.
*Introducing certain characters into the XML file, even as part of a comment, will cause the file to choke. These include &, <, and --.''

The scenario file contains one entry for each AI object. The entry specifies what kind of object to create, what its initial conditions will be, and optionally (for aircraft and ships) a flight plan. The entry for a sailboat could look like this:

<entry>
<type>ship</type>
<model>models/geometry/sailboat.xml</model>
<speed-ktas type="double">12.0</speed-ktas>
<altitude-ft type="double">0.0</altitude-ft>
<longitude type="double">-122.33333</longitude>
<latitude type="double">37.61667</latitude>
<heading type="double">20.0</heading>
</entry>

Most of the parameters are self-explanitory. The "type" of object can be one of "aircraft", "ship", "carrier", "thunderstorm", "thermal", "ballistic" or "static". The rest of the items give the AI object a model, a starting location, and a starting speed and direction. You use the <MODEL> item to give the object any valid exterior model. You can even make the ship look like an airplane if you want! Note that the speed of the AI object is true airspeed, and since AI aircraft and ships don't feel wind or current then this also the ground speed. The "ship" type can also have a <RUDDER> value specified, which will cause the ship to move in a circle (HINT: use small values, five degrees or less, and right rudder is positive). Here is an example of how to create an aircraft AI object:


<entry>
<type>aircraft</type>
<class>light</class>
<model>Aircraft/a4/Models/a4-blue.xml</model>
<speed-ktas type="double">320.0</speed-ktas>
<altitude-ft type="double">7000.0</altitude-ft>
<longitude type="double">-122.6</longitude>
<latitude type="double">37.9</latitude>
<heading type="double">210.0</heading>
<bank type="double">-15.0</bank>
</entry>

It looks much the same as the ship AI code. There are two differences, the <class> item and the <bank> item. If the class is set to "tanker" the airplane will allow you to refuel if you can get close behind it. The bank is of course similar to the ship's rudder. In the above example the A-4 will be orbiting to the left at 15 degrees of bank. You can also create a ship or airplane with a flight plan. In this case the object will follow the flight plan, and then delete itself when it reaches the end. The flight plans are kept in data/Data/AI/FlightPlans. To create an airplane with a flightplan do this:

<entry>
<type>aircraft</type>
<class>jet-transport</class>
<model>Aircraft/737/Models/737.xml</model>
<flightplan>ksfo_ils28l.xml</flightplan>
</entry>

To make a thunderstorm, use this:


<entry>
<type>storm</type>
<model>Models/Geometry/thunderstorm.xml</model>
<speed-ktas type="double">20.0</speed-ktas>
<altitude-ft type="double">4000.0</altitude-ft>
<latitude type="double">37.3917</latitude>
<longitude type="double">-122.2817</longitude>
<heading type="double">90</heading>
</entry>

There's not much to it. No, they don't turn :) To create a thermal, use this:

<entry>
<type>thermal</type>
<latitude type="double">37.61633</latitude>
<longitude type="double">-122.38334</longitude>
<strength-fps type="double">8.33</strength-fps>
<diameter-ft type="double">4000</diameter-ft>
<height-msl>6000</height-msl>
<model>Models/Geometry/thermalcap.xml</model>
</entry>

The AI thermals don't move, they are invisible, and they don't "lean" downwind. The <strength-fps> defines the maximum vertical velocity of the airmass at the center of the thermal. The strength decreases to zero at the thermal's edge. A
model can be assigned to the thermal, and usually this will be a small cloud to mark the thermal's location. To create a sink, just give a "thermal" a negative strength, and give it a null model. Please see the demo scenario (thermal_demo.xml) for examples.

A ballistic AI object starts with an initial azimuth, elevation and speed, then follows a ballistic path from there (with air resistance and wind included). Try this:

<entry>
<type>ballistic</type>
<model>Models/Geometry/rocket.xml</model>
<speed-fps type="double">500.0</speed-fps>
<altitude-ft type="double">50.0</altitude-ft>
<longitude type="double">-122.39</longitude>
<latitude type="double">37.62</latitude>
<heading type="double">200.0</heading>
<azimuth type="double">70.0</azimuth>
<elevation type="double">45.0</elevation>
</entry>

Note that the speed is now in feet per second.

The AI storm objects can be displayed on weather radar. See the Aircraft/Instruments/wxradar.xml file for details. The AI aircraft objects can be displayed on radar. See the Aircraft/Instruments/radar.xml file for details.

You can make your own AI scenario file, called say my_scenario.xml, and cut/paste entries from the other scenario files to build an AI scenario as complicated as you like.

The following how-to shows you how to animate a tail-dragger airplane so that its pitch attitude looks proper for the AI aircraft's airpeed. This is not needed for aircraft with tricycle landing gear.

=== Using Interpolation Tables ===
Interpolation tables are very handy for effecting animations that are non-linear in relation to the property they are referenced to.

They save the use of factors, offsets and min/max values.

For example; relating flap extension to airspeed of an AI model. Typically an aircraft will extend flaps on final approach to control Indicated Airspeed (IAS) and stall speed to affect a low speed controlled landing. Upon touchdown the extra lift efficiency introduced by the flaps is no longer required or desirable, hence the flaps will be retracted ASAP after touch down.

This is relatively simple in a sim aircraft as the /surface-positions/flap-pos-norm property is a normalised indicator of the flap setting chosen by the pilot.

AI aircraft have no pilots to control flaps nor does the flight plan <flaps-down>true/false</flaps-down> parameter effect the /AI property tree parameter, a relationship to the IAS is the next best choice.

To effect this relationship (IAS/flap-position) using factors/offsets and min/max would be quite difficult and non-intuitive. Using interpolation tables allows the following scenario to be setup very easily and intuitively:

: '''C172P'''
{| border="1"
|-
| Max
| 123 KIAS
|-
| Cruise
| 90 KIAS
|-
| Stall (no flaps)
| 50 KIAS
|-
| Flaps
| 0, 10, 20, 30 deg.
|-
| Approach
| 90 KIAS
|-
| 10° flaps
| 90 KIAS
|-
| 20° flaps
| 70 KIAS
|-
| 30° flaps
| 60 KIAS
|-
| Flare & touch down
| 50 KIAS
|-
| Brake
| 45 KIAS
|-
| Retract flaps
| 45 KIAS
|}

'''Table IAS/flap extension'''
{| border="2"
|+
| IAS (kt) || Flaps
|-
| 90
| 0
|-
| 70 - 89
| 10
|-
| 60-69
| 20
|-
| 45-59
| 30
|-
| < 45
| 0
|}

When the pilot extends the flaps "one notch" they will extend to "10°" etc. In the property tree, these 4 steps will typically be normalised to 0.00, 0.33, 0.66, 1.00. This will differ from aircraft to aircraft. If the aircraft does not have equal extensions for each "notch" of flaps, the values observed may be; 0.00, 0.10, 0.30, 0.66, 1.00. Modeling this non-linear extension using "factor, offset, min/max" would be extremely difficult if not impossible. Modeling it using interpolation tables is very easy, as you shall see.

For sim animations, the actual physical rotation of the control surface in the real world needs to be researched; this may reveal a linear or non-linear relationship between "nominal flap extension indicator" and physical rotation of the surface. That is, "10 degrees of flap" might only involve rotating the flap surface 5 degrees around its axis in the wing structure. In our 0,10,20,30 scenarios, assuming a linear relationship, 30 degrees of flap would result in the flap being rotated 15 degrees around its wing axis. Therefore the normalised /surface-positions/flap-pos-norm property would have a factor of 15 applied to the rotate animation

The way to change a linear relationship that uses "factor, offset, min/max" in the sim animation to a interpolation table in the AI animation is best understood by examining how "factor, offset, min/max" approach works:

# Take normalised value of the flaps (0=retracted, 1=extended)
# Apply the factor.
# Apply the offset
# Apply the min/max values

e.g.
factor=60
offset= -30
min=-10
max+10

these figures are nonsense but are used to illustrate a point:

flaps retracted(0°) = 0 x 60 = 0, (offset=-30) = -30, (min= -10) = -10
flaps extended(10°) = 0.33 x 60 = 20, (offset=-30) = -10, (min= -10) = -10
flaps extended(20°) = 0.66 x 60 = 40, (offset=-30) = 10, (min= -10/max=10) = 10
flaps extended(30°) = 1.00 x 60 = 60, (offset=-30) = 30, (max=10) = 10

more realistically, offset and min max are not used for flaps, only a factor.

say 27°, this represents the maximum rotation of the 3-D component in the model around its defined axis.

flaps retracted(0°) = 0 x 27 = 0
flaps extended(10°) = 0.33 x 27 = 9
flaps extended(20°) = 0.66 x 27 = 18
flaps extended(30°) = 1.00 x 27 = 27

from this it can be seen that the 3-D object will be rotated 0°, 9°, 18° & 27° to represent the 0°, 10°, 20° & 30° deployment of the flaps.

Relating this back to the speeds above:

{| border="1"
|+
| IAS (kt)
| <rotate> value
|-
| 0
| 0
|-
| 44
| 0
|-
| 45
| 27
|-
| 59
| 27
|-
| 60
| 18
|-
| 69
| 18
|-
| 70
| 9
|-
| 89
| 9
|-
| 90
| 0
|-
| 100
| 0
|}

this gives a stepped effect, where the movement is limited to 1knt of airspeed. That is the 3-D object will linearly move from 9° to 18° while the aircraft looses speed from 70 knots to 69 knots. This behaviour will make the need for an upper and lower limit of a stepped value obvious.

a simplified table of:

{| border="1"
|+
| IAS (kt)
| <rotate> value
|-
| 0
| 0
|-
| 45
| 27
|-
| 60
| 18
|-
| 70
| 9
|-
| 90
| 9
|-
| 100
| 0
|}

will cause the flaps to start extending at the rate of 1/45 x 27 degrees per knot of airspeed gained until 45 knots when the rate of change will adjust to the new gradient. This is not how flaps behave, but can be used to good effect with "tail dragger" animations where at a certain IAS the tail starts rising, maybe at an increasing rate, until flying attitude is reached when it stops rising any further. The tail rising is not a stepped function of IAS.

Now we have the basic ideas behind interpolation tables, the question is how are they implemented…answer;…easy ….an example of the stepped flaps animation above

<interpolation>
<entry><ind>0.000></ind><dep>0.000</dep></entry>
<entry><ind>44.00></ind><dep>0.000</dep></entry>
<entry><ind>45.00></ind><dep>27.00</dep></entry>
<entry><ind>59.00></ind><dep>27.00</dep></entry>
<entry><ind>59.00></ind><dep>27.00</dep></entry>
<entry><ind>60.00></ind><dep>18.00</dep></entry>
<entry><ind>69.00></ind><dep>18.00</dep></entry>
<entry><ind>70.00></ind><dep>9.000</dep></entry>
<entry><ind>89.00></ind><dep>9.000</dep></entry>
<entry><ind>90.00></ind><dep>0.000</dep></entry>
<entry><ind>100.0></ind><dep>0.000</dep></entry>
</interpolation>

Here endth Interpolation tables 101
:-Dene

=== Submodels ===
Submodels are AI ballistic objects that emanate from, fall from, or launch from the user aircraft. They are presently used to model smoke, contrails, flares, tracers, bombs, drop tanks and flight path markers.

Submodels are controlled by the submodel manager. The manager reads a submodel configuration file at the start of the sim session. This configuration file is written by the aircraft author and defines all the submodels for that particular aircraft.

As an example examine the submodels file in the Aircraft/737-300 directory. This file creates two submodels which will become the airplane's left and right engine contrails. Each contrail needs its own submodel definition because the contrails begin at different locations. Each contrail consists of a train of individual "puff" models that are released in rapid succession as long as the "trigger" property is true. We ensure an unlimited supply of puffs by setting the "count" parameter to -1. The individual puffs, being AIBallistic objects, will follow their own ballistic paths once released. In this case we have used the "bouyancy" parameter to negate gravity in the ballistic path. The puffs have been given a life span of eight seconds. At cruising speed the [[Boeing 737|737]] will thus have about 400 puffs behind it at any moment.

=== Multiplayer Controlled Traffic ===

FlightGear's multiplayer system also makes use of the AIModels subsystem. See the [[Multiplayer]] page for more information.

=== Traffic Manager Controlled Traffic ===
Traffic Manager Controlled Input to the AIModels subsystem is also known as Interactive Traffic. See: [[Interactive Traffic]] for more information.

==External links==
* [http://www.xs4all.nl/~dtalsma/flightgear.html The FlightGear AI aircraft download page]

[[Category:FlightGear feature]]

FlightGear Newsletter March 2010

2010-03-22T18:27:39Z

Xiii: /* FlightGear wiki moved to a new server */ typo

{{newsletter}}

Welcome to the March 2010 edition of the [[FlightGear]] Newsletter.

==From the developers==
===Shader experiments===
[[Image:Experimental_Shaders_Urban.jpg|thumb|270px|The experimental urban effect. Notice how the 2D city textures appear to be 3D!]]
FlightGear developer Fred has been experimenting with the [[shaders]] recently. Altough he is not yet completely satisfied with the results, they are worth to be watched.
*[http://www.youtube.com/watch?v=kUyH-4c0-qM Landmass effect]
*[http://www.youtube.com/watch?v=wYb1Vy-uTS0 Urban effect]
*[http://www.youtube.com/watch?v=t7OeU80vtR8 Urban sunrise to sunset]

===Map Dialog===
[[File:map1.png|thumb|Basic map display]]
James is working on a GUI navigational map, which shows information from the GPS and navigation/airport database in a dialog box - similar to the map windows in other flight-simulators. The results aren't as beautiful as [[Atlas]], but are useful for quickly finding a nearby airport or VOR, and for graphically showing waypoints from a route. The code is also a test platform for creating in-panel cockpit displays using similar technology in the near future, and it's already possible to switch the map to show the aircraft track (from the GPS) heading 'up' the screen. In the mode the map can be used as simple navigation display, to stay on a route or align with a localizer.

See [[Map|this wiki page]] for further information on the current status (and bugs) of the code, and some basic instructions.

==In the hangar==

==Scenery Corner==

==Wiki News==
===FlightGear wiki moved to a new server===
Probably all of you have noticed the fast amount of 503 errors that showed up lately. The reason for this was that we received a lot of visitors each day, more than the server could handle. After three months, the wiki was finally moved to a new server on the 10th of March. From now on, there should be no more 503 errors popping up. Please [[Help:Contents|contact the wiki admin]] if they do, or if any other problems arise.

==Community News==

===Changes in the Forums===

Gijs de Rooy has become an administrator at the [http://flightgear.org/forums/index.php FlightGear Forums]. As well moderating the forums, Gijs has already made some significant improvements to the Forum organization.

===Another multiplay server===
Thanks to Charles Ingels (cbz026), there is another [[Howto: Multiplayer|multiplayer]] server in France! This brings the total number of servers to 13, of which 10 in Europe, two in North-America and one in Asia.

Again, we would like to emphasize the importance of connecting to the correct server. The multiplayer servers are interconnected, so you do not need to connect to a specific server in order to see other pilots who are on that server. However, since server02 is overloaded (too many people use that one), not all pilots are shared between the servers. For best performance it is very important connect to the server that is geographically closest to you, has the lowest latency (ping time) or is the least busy.

The complete list of servers and more information about multiplayer is available in the [[Howto: Multiplayer|Multiplayer howto]].

[[Category:FlightGear Newsletter|2010 03]]

FGCom (before 3.0)

2010-03-19T17:42:05Z

Xiii: fix typo

'''FGCom''' is an addon for [[FlightGear]]. With FGCom (and the infrastructure behind it), FlightGear now has a realtime voice communication system which enriches the FlightGear capabilities, especially for Multiplayer events, like:
*flying in groups (see e.g. the '''Forum Multiplayer Events''' on http://www.flightgear.org/forums/):
**invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”
**do military training like [[Howto: Air-Air Refueling|“Air-Air-Refuelling”]], “Dog fights”, “Escort flights”, etc.
*offering additional services at an airport like [[Air traffic control|ATC]], [[Vehicle|Snowplows, Pushbacks]], [[FlightGear Race|Racing-Events]] etc.
*have a [[Dual control|real time flighttraining]] (e.g. pilot in Hongkong, teacher in Sydney) or do [[Soaring|Glider-towing]] or just ask for on-line support during flight or just ask somebody flying a plane of interest about specifics
*or e.g. just sit in a cockpit in Germany while sightseeing San Francisco in a C172, voice-chatting with a Texan in a plane I dreamed of as a boy (Super Constellation), and both getting informations from a New Zealand guy (it shall be a wonderful island – but do real people live there? He said: Yes!!).
*etc.
You can even use it in models without radios - just use the standard FlightGear menu --> Equipment --> Radio Settings.<br>

In the future FGCom surely will extend further and surely will get a “Speech to Text” capability in order to also integrate the Text-based automated ATC-routines inside FlightGear.

<br><br>
=='''The Client installation'''==
===Prequisites===
====Hardware Requirements====
If you are satisfied with the operation and responsetimes of your current FGFS installation, then you should see no significant difference after adding the FGCom. If your FGFS installation runs already a little marginal, then you might experience some delays when many new airplane-models etc. must be loaded. This may happen when starting up at a busy airport. You can monitor/verify such a "short-time overload" in the FGFS command-window.

For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html

Of course you will also need a connection to the Internet for this real-time, worldwide voice communication.

<br>
====Software Requirements====
{| style="width:75%" border="1"
|+
|-
|align="center" width="100" |'''FGFS''' ||The basic Flight-Gear-Flight-Simulation installation. This must be installed prior to installing the FGCom ''(except if installing the Linux "CVS complete" version which can install FGCom and FGFS concurrently)''.
ref.: http://www.flightgear.org/
|-
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of the FGFS. As the name says, it enables communication of several players via a chat-function (until now per keyboard - now also with this vocal interface: FGCom).
|}
<br>
====Nice to have====
{| style="width:75%" border="1"
|+
|-
|align="center" | '''FGrun'''||This [[FlightGear Launch Control]] (also known as FG-Wizard), is a graphical front end to start the FGFS. This makes it very easy to startup the FGFS with all it's possible options. In some newer distributions this is already part of the basic FGFS installation package
|-
|align="center" |'''MPMap'''||[[MPMap]] is a pure browser application based on Google Maps, so it does not need any installation, except a Web-Browser. With MPMap you can watch all Multiuser-planes worldwide on a road-map, satellite picture or a composite of both. It includes most of the airports, navigational aids, and current weather informations. So it can be used for preflight planning, without having the FGFS started or even installed. But it needs a constant connection to the INTERNET - on the other hand you can do your preflight planning anywhere where there is a PC, connected to the INTERNET.
|-
|align="center" |'''Runwayfinder'''||This standalone Browser-Application( http://www.runwayfinder.com ) does present a fantastic Fight-Planning tool, showing similar aspects like the "MPMap" but adds an Aeronatical map. It does not link to FGFS or MPMap or Multiplayer -- and covers only the domestic USA.
|-
|align="center" |'''Atlas'''||[[Atlas]] displays the current position of your airplane on an landscape type of map together with navigational informations. It derives its data direct out of the installed FGFS databases. So you do not need any connections to the INTERNET.
|-
|align="center" |'''Festival'''||Festival is a TTS (Text To Speech) system that can convert all in the FGFS displayed written text (ATC, Chat, etc.) into speech and put it on your loudspeakers. ref.: http://www.flightgear.org/Docs/getstart/getstartch5.html#x10-790005.6
|}
<br>
===Installing FGCom===
====Install on Linux====
For Linux-Systems there are 3 ways to install:

'''1) Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).'''
*'''Advantage:''' This is the easiest way and ensures that maintenance and services for this package and all concurrencies to it are provided automatically for a reasonable time-frame.
*'''Disadvantage:''' The availability of those packages is usually very late and most Distributors do not cover all FGFS-features. To our knowledge none of the Distributors has an FGCom package available as of March 2009.
*'''Installation:''' Follow the usual procedures of your distributer on how to install additional packages.
<br>
'''2) Installing a “CVS complete”'''
*'''Advantage:''' It is the very easiest form of installation and installs in one step all prerequisite/companion modules (FGFS, FGrun, FGcom, PLIB, OSG, Simgear, AT). Also it can be added and removed from the system without disturbing the rest of the system (Libraries, Menus, Structures, etc.). It was tested on several Ubuntu and Debian systems.
*'''Disadvantage:''' No automated maintenance available. The handling is a little different from the standard Menu-driven practice.
*'''Installation:''' http://wiki.flightgear.org/index.php/Scripted_Compilation_on_Linux_Debian/Ubuntu
<br>
'''3) Compiling it locally: ''' http://code.google.com/p/fgcomgui/wiki/Linux_Installation
*'''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.
*'''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and it's devices.
*'''Installation:''' See the Instruction on: http://code.google.com/p/fgcomgui/wiki/Linux_Installation
<br>
'''Then continue with testing on: ''' http://wiki.flightgear.org/Index.php/FGCOM_Testing
<br>

====Install on Windows====
Please use the Windows-Installation description on http://wiki.flightgear.org/index.php/FGCOM_for_Windows

<br>
====Install on Mac====
You can download the "MAC OSX Binary" from the FGFS download-center ( http://www.flightgear.org/Downloads/binary.shtml#mac ). The current version of the code does contain the FGCOM.

But '''you do need OS X 10.5''' as prerequisite. With lower versions you will end up with a generic "bus error" message!

<br>
===Testing===
During testing
#we will test the basic FGCOM-functions without the FGFS
#after that we test the FGCOM together with the FGFS
#finally we test/adjust the Microphone and Loudspeaker system

For these tests please see the [[FGCOM_Testing|FGCOM_Testing]]

<br>
===Functional Test + User Briefing===

Experiences pointed out, that the cooperation FGCom/FGFS works more reliable, if the FGFS gets started first. So we will start with setting up a flight-test-environment:
====Start the FGFS====
We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), you also get the correct writing for all the command-options (in case you later want to start from a command-line and/or out of a script). In the following we will just point out those commands which are significant for the FGCom-operation:

If you don't have an Icon available to start the FGrun, then
*use a [[Command line|command-window]]
*change into the directory in which FGFS was installed
*and start the program from there:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs<br>sh ./run_fgrun.sh
|-
||for Std. Linux e.g.: ||fgrun
|-
||for Windows e.g.: ||D:<br>cd 'C:\Program Files\Flightgear\win32'<br>fgrun.exe
|-
||for Mac: || ||
|}
Wait for the Program-Window to start and then define:<br><br>
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]]<br>
→ Click “Next”<br><br>
'''2)''' As '''starting place''' please define the airport KPAO (Palo Alto) runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br>
→ Click “Next”<br><br>
'''3)''' Define the '''Multiplayer options:''' (ref. wiki [[Howto: Multiplayer]] for details)
{|
|+
|-
|width=610|[[image:FGrun_base.jpg|thumb|left|600px|Basic + Multiplayer Options]]
|“AI models” must be activated in order to see all traffic
<br><br>“Multiplayer” must be activated
<br><br>type “'''mpserverXX.flightgear.org'''” into the field “Hostname:”, replace “XX” with the server number nearest you - select it in http://pigeond.net/flightgear/mpstatus/. Actually it does not matter which server you take (as long as it is online) - you might try which server gives you the best response-times.
<br><br>Insert your “Callsign:” (max. 7 characters)
<br><br>define the “in” and “out” ports both with the standard “5000”
<br><br>With "Load/Save as" you may build up yourself a library of settings for different airports.
|}→ Click “Advanced”<br>
'''4)''' In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
#General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
#Features: “AI Traffic” should be activated already
#Initial Position:
{|
|+
|-
|width=420|[[image:FGrun_IP.jpg|thumb|left|400px|Advanced: Initial Position]]
|
You may define here an unique “starting/parking” position outside a runway. Thus you could avoid starting on top of another player, because most of them pile up at the end of a runway. You can look up a position in the MPMap: ''(see next item)''
<br><br><br>''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.
|}
Open http://mpmap01.flightgear.org
{|
|+
|-
|width=510|[[image:MPmap.jpg|thumb|left|500px|Preflight]]
|
*if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”
*click on “nav”
*disable all options except “apt code”
*type “KPAO” into the filed “Navaids lookup”
*hit ENTER or click onto the reading-glass symbol
*click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”
*now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”
*then zoom into the airport
*set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen
*type those long/lat values into the field below and also the wanted heading of the plane while parking
|}
'''5) Network:'''
{|
|+
|-
|width=420|[[image:FGrun_net.jpg|thumb|left|400px|Preflight]]
|Those data you have already predefined on the Base-Page. But in case you have network-problems (may be due to many PC's on a home-network with even more LAN-cards) you may specify here your actual IP-Adress.
<br><br>WARNING: When saving these settings and reloading them again, FGrun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
|}
If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type
{|border="1"
|+
|width="100"|OS
|width="75"|'''to type'''
|width="40"|Cap. ||returned values
|-
||for linux: ||ifconfig ||eth0 ||
Link encap:Ethernet HWaddr 00:1d:92:80:a6:ab
<br>inet addr:'''192.168.178.23''' Bcast:192.168.178.255 Mask:255.255.255.0
|-
||for Windows: ||ipconfig /all ||et ||
Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF
<br>DHCP aktiviert. . . . . . . . . . : Ja
<br>Autokonfiguration aktiviert . . . : Ja
<br>IP-Adresse. . . . . . . . . . . . : '''192.168.178.20'''
<br>Subnetzmaske. . . . . . . . . . . : 255.255.255.0
<br>IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|-
||for Mac: || || ||
|}
The '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!!

'''6) Input/Output:'''
{|
|+
|-
|width=420|[[image:FGrun_IO.jpg|thumb|left|400px|Preflight]]
|You do need a "generic" line as shown, because '''this defines the interface between FGFS and FGCom'''.
<br><br><br>
To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.<br><br>
Editing an existing line: Start by clicking onto the existing one, then change as required.<br><br>
Deleting an existing Line: Click onto the line to be deleted, then hit "Delete"

|}

'''7) Avionics:''' let's define:
{|
|+
|-
|width="50"|
|width="60"|Nav1:
|width="100"|114.10 ||San Jose VOR
|-
| ||Nav2: || 115.80 ||SF VOR
|-
| ||ADF: || 379 || Brijj, beacon at SF
|}
and activate: DME to Nav1<br><br>
There is no field to input COM-radios, but remember them for setting them later manually:
{|
|+
|-
|width="50"|
|width="60" |Com1
|width="100" |118.60 ||Paolo Alto
|-
| ||Com2 || 120.50 || San Francisco
|}

'''8) Properties:'''
Here you can define any presetting for any values in the FGFS.<br>see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”
{|
|+
|-
|width=520|[[image:FGrun_prop.jpg|thumb|left|500px|Preflight]]
|
e.g. I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
<br><br>Input a new line: Just hit “New” and type your string.
<br><br>Edit a line: Be sure first to click onto an existing item and then edit this “Property”
<br><br>Delete a line: Click onto the line to be deleted then hit "Delete"
|}
Hit “OK” → “Run” and watch the FGFS starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.<br>

====Start the FGCom====
Open a [[Command line|command-window]] and change into the directory in which FGCom was installed (probably the same as the FGFS) and start the FGCom. Do not use any other options than the server address “-Sfgcom.flightgear.org.uk”:
{|border="1"
|+
|-
|width="150"|for linux CVS e.g.:
|width="250"|cd ~/fgfs<br>sh ./run_fgcom.sh
||for this “CVS complete” you do not need to specify the server address, because it is embedded in the script-file.
|-
||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Windows e.g.: ||cd 'C:\Program Files\Flightgear\win32'<br>fgcom.exe -Sfgcom.flightgear.org.uk ||"-Sfgcom..." with capital "S"
|-
||for Mac: || ||
|}
For the following test position this command-window somewhere, where you can monitor it throughout the test.

The first response should be:
/fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 206M
Using iaxclient library Version SVN 206M

Successfully parsed command-line options.
Reading list of airports...done.
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk
If your printout up to that line is different go back to chapter [[FGCOM#Test the basic function|Test the basic function]]

{|
|+
|-
|width="300"| ||
|-
|1) If, due to a prior flight, COM1 was set to anything else but 118.600 (e.g. to 119.650) you will see the following 2 lines added to the initialization of the FGCom-window: ||
|-
|
Selected frequency: 119.650
Call rejected by remote
|
Instead of “119.650” there will be shown the last used frequency. In this case the source of the nearest ATC-Freq. 119.650 is more than 50km away from your actual position of the airplane, so FGCom rejects a connection to it. If the last frequency used would have been within 50 km you get an indication very similar to the next item.
|-
|2) Switch COM1 to 118.60 (needed at Palo Alto):
|-
|
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
|This last line will be repeated according the to time span you defined in the “Input/Output” command “--generic=socket,in,'''10''',,5500,tcp”, you may change that value later according to your preferences.
|-
|<br>3) Press your PTT (PushToTalk on space-bar and joystick, as available):
|-
|
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
[SPEAK] unmute mic, mute speaker
[LISTEN] mute mic, unmute speaker
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.
|-
|<br>Now lets set/verify the other Radios:
*COM2 = 120.50 San Francisco
*NAV1 = 114.10 San Jose
*NAV2 = 115.80 San Francisco
4) Pressing Upper+Space will switch to the next radio: '''NAV1'''
|-
|
Radio-Select: NAV1
Selected frequency: 114.100
Hanging up call 0
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|Compare this to the NAV2 indication 2 steps later: something is wrong – and it wasn't your fault: Although this NAV is valid (see ...FGFS/data/Airports/apt.dat.gz), it is missing in the FGCom listing .../FGCom/positions.txt. I encountered this problem several times, as well for Airports as also for VOR's. If this happens with your most beloved airport you can add those missing data with a text-editor. But before changing be sure to save the original data somewhere - just in case!
|-
|<br>5) Pressing Upper+Space once more switches to '''COM2'''
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km)
[LISTEN] mute mic, unmute speaker
Call 0 accepted
Call 0 answered
|That looks OK: San Francisco is about 29 km away<br><br>watch the “km” instead of miles!<br>'''10 km''' = '''6.2137 mi'''
|-
|<br>6) Pressing Upper+Space once more switches to '''NAV2'''
|-
|
Radio-Select: NAV2
Selected frequency: 115.800
Hanging up call 0
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|And Yes: The SF VOR is just a little closer than the airport(center)
|-
|<br>7) Pressing Upper+Space once more brings back '''COM1''':
|-
|
Radio-Select: COM1
Selected frequency: 118.600
Hanging up call 0
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
|-
|<br>8) Lets us start and continue flying in the direction about 130°:
|-
|
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km)
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km)
|notice that you first come closer (to the center of the airport) and after that getting away
|-
|<br>9) Let's switch to '''COM2''' (San Francisco) and watch:
|-
|
Radio-Select: COM2
Selected frequency: 120.500
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km)
Call 0 accepted
Call 0 answered
[LISTEN] mute mic, unmute speaker
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km)
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km)
..
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km)
Hanging up call 0
Radio-Select: NAV2
Selected frequency: 115.800
Call rejected by remote
[LISTEN] mute mic, unmute speaker
|That means: at about 50KM we are getting out of range and thus the on COM2 active SF getts terminated. Notice that also the inactive NAV2 gets terminated, because it exceeded the allowable range at about the same time!
|}
10) You could turn now and watch the opposite: At about the same distance those two will become active again (automatically, if you did not change the settings).
<br><br>
If you got here without any (technical) problems your FGCom is fully functional. Have fun when using it.

<br>

===Using FGCom===
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]):
*'''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through the "'" (UpperCase#) and/or the Chat-Menus). In addition you then can talk to anybody in a radius of about 50 km (about 30 miles) around the airport, may that be friends, a maintained FGCOM-ATC/Twr-Operator, airport utilities, etc.. Be aware that as of April 2009 only very few planes are using the FGCOM for ATC-purposes - thus you should always use the ATC-Chat "keyboard"-procedures to announce arrivals/departures/taxiing etc. in addition. (We hope that may change in some future!)<br><br>
*The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and not yet "overcrowded!). Also when traveling you might want to listen on the 122.75 for others who want to contact you (or reverse). When there is much "talk" on the 122.75 you might just arrange with your partner to switch to 123.45 - and return to 122.75 afterward. As of April 2009 the 122.75 is already operational for this application, the 123.45 will follow soon. You may try from time to time if this limitations still exist.<br><br>
*Finally you can manipulate the frequency-tables (positions.txt in your FGFS/FGCOM local directory) and define an own frequency for special events. e.g. a Flight-School at one airport with maybe multiple student-groups. Of course those are local manipulations on your own PC, which you have to agree on with your (planned to be) partners in advance.

<br>
===Supplemantery Informations===
====Tips and Tricks====
<ol>
=====Airport missing in FGCom:=====
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line
KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
You can add extra lines for any locations you want. e.g.: (watch the separation comas)
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code)
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz”
or just take one of which you are sure that you do not need it in the FGFS-reality
(notice that several Airports (far apart) use same frequencies!
long/lat = take out of the Mpmap (or Google Map)
type = whatever
name = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''
<br><br>
=====Editing FGCOM-Data-Files=====
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
*For windows you can use "WordPad"
*For Linux the "gedit" works fine
<br>
=====Copying-Printing this WIKI-Page'''=====
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )
*to copy:
**select in the Browser-Menu: "File" --> "Save Page as.. "
*to print:
**select the last entry in the sidebar on the left: "Printable version"
**Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"
**before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!
**If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer


<br><br>
=====Joystick compatibility between Operating Systems:=====
ref also: [[Joystick]]<br>
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):
<axis> (instead of the usual <axis n=”3”> )
<desc>Mixture</desc>
<number>
<unix>3</unix>
<mac>5</mac>
<windows>5</windows>
</number>
<binding>
<command>nasal</command>
<script>controls.mixtureAxis()</script>
</binding>
</axis>

<br><br>
=====assign PTT to Joystick and PTT=====
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
<button n="x">
<desc>PTT - Push To Talk</desc>
<binding>
<command>nasal</command>
<script>controls.ptt(1)</script>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>controls.ptt(0)</script>
</binding>
</mod-up>
</button>

====Helpfull INTERNET Adresses====
'''World-Time:'''
*for standard deviations:http://www.timeanddate.com/worldclock/custom.html?sort=1
*for direct conversions: http://www.timezoneconverter.com/cgi-bin/tzc.tzc
Especially for multiplayer events you should define all times in the internationally used GMT (Greenwich Meantime). Just pick up your deviation from GMT and memorize it. If everybody does it, we could avoid a lot of misunderstandings.<br><br>
'''Decimal to Degree''' http://www.hbnweb.de/mathematik/grad-dezimal.html <br>
Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it.<br><br>
'''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/
<br>If like to avoid troubles (like e.g. NASA lost a satellite because of it) just look it up.

'''Ports needed'''<br>
In case of problems over the INTERNET you might check that the the following ports are allowed:
1314 TCP if the Festival-Server is used for Text/Sound
2005 UDP Vcp-Stream
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)
5000 UDP in/out Multiplayer (VPN Sftw.)
5001 UDP Enable HTTP-server
5002 UDP Enable property server
5003 UDP Enable Screen-Shot services
5004 UDP (may be used as a spare)
5505 UDP Terra Sync
16661 UDP FGCom listening to FGFS, usually “local host” only
Also consider that some modern modems do already provide a firewall. If in addition to that you use a local firewall in your PC, than you might expect an unhealthy competition between those two concurrent firewalls. In case of problems you should deactivate one of those (usually the one inside the PC, especially if several PCs are connected via that modem).

====Commandline Parameters====
fgcom --help
returns the following useful info
fgcom - a communication radio based on VoIP with IAX/Asterisk
(c)2007 by H. Wirtz <wirtz@dfn.de>
Version 1.2.2 build 163M
Using iaxclient library Version SVN 163M

OPTION DESCRIPTION

-d, -debug, --debug= show debugging information
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')
-s, -fgserver, --fgserver= network device to connect to (default: 'localhost')
-p, -port, --port= where we should listen to FG (default: '16661')
-a, -airport, --airport= airport-id (ICAO) for ATC-mode
-f, -frequency, --frequency= frequency for ATC-mode
-U, -user, --user= username for VoIP account (default: 'guest')
-P, -password, --password= password for VoIP account (default: 'guest')
-i, -mic, --mic= mic input level (0.0 - 1.0)
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)
-b, -mic-boost, --mic-boost= enable mic boost
-l, -list-audio, --list-audio= list audio devices
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')

Available codecs:
u - ulaw (default and best codec because the mixing is based onto ulaw)
a - alaw
g - gsm
s - speex
7 - G.723

Mode 1: client for COM1 of flightgear:
$ fgcom
- connects fgcom to fgfs at localhost:16661
$ fgcom -sother.host.tld -p23456
- connects fgcom to fgfs at other.host.tld:23456

Mode 2: client for an ATC at <airport> on <frequency>:
$ fgcom -aKSFO -f120.500
- sets up fgcom for an ATC radio at KSFO 120.500 MHz

Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!

Also note that the current server (fgcom.flightgear.co.uk) works with guest account, so '''do not use -U or -P'''

<br><br>

=='''Server installation'''==

For running a FGCOM server you need Asterisk and depending on the amount of users much bandwith and CPU power. Because of putting pilots and ATCs in a VoIP conference the server-admin has to assure that there is enough network and cpu power to avoid drop-outs of the voice stream.

===Prerequirements===

Install Asterisk on top of your favorite distribution. Please refer to installation manuals (e.g. [[http://www.asteriskguru.com/|Asterisk-Guru]]) you can find on the net. You do not need H.323 or SIP because the fgcom client uses IAX2 as VoIP signaling protocol. Only if you think about connecting external VoIP applications to FGCOM you should consider to activate H.323 or SIP (but this is not the scope of this small howto).

Notice: You need to install the zaptel driver modules - even if you won't use any hardware for telecom interfacing. You need the ztdummy kernel module for the asterisk conference application MeetMe() because it simulates a hardware clock needed by this application. Further development of FGCOM might use app_conference which don't needs any timing device.

For now we want to use /etc/asterisk as the base configuration directory.

===Setting up the radio frequencies===

The radio frequencies are "simple" Conferences and realized due to the Asterisk application MeetMe().

====Part 1: General configuration====

First you have to set up the general configuration of the system. Put the following at the top of your "extensions.conf" file:

[general]
static=yes
writeprotect=yes
;
[globals]
;
[macro-com]
exten => s,1,Answer()
exten => s,n,MeetMe(${MACRO_EXTEN},qd)
exten => s,n,Hangup()
;
[macro-echo]
exten => s,1,Answer()
exten => s,n,Echo()
exten => s,n,Hangup()
;
[guest]
; ATC-Help
exten => 01-ZZZZ-911.000,1,Macro(com)
exten => 012525252591100,1,Dial(Local/01-ZZZZ-911.000)
exten => 01-ZZZZ-910.000,1,Macro(echo)
exten => 012525252591000,1,Dial(Local/01-ZZZZ-910.000)
;
[default]
include => guest
;
; Code:
; 01 - FlightGear
; 02 - Microsoft Flight-Simulator
; 03 - ...
;
; Air2Air
exten => 01-ZZZZ-123.450,1,Macro(com)
exten => 012525252512345,1,Dial(Local/01-ZZZZ-123.450)
exten => 01-ZZZZ-122.750,1,Macro(com)
exten => 012525252512275,1,Dial(Local/01-ZZZZ-122.750)

====Part 2: Adding your favorite (all?) frequencies====

For this you have simply to create an extension for every touple of airport/frequency in extensions.conf. The following is an example for Berlin-Tempelhof (EDDI). The information comes from the file "apt.dat.gz" of your FlightGear installation.

; EDDI ATIS 126.020 - Berlin Tempelhof
exten => 01-EDDI-126.020,1,Macro(com)
exten => 010403030812602,1,Dial(Local/01-EDDI-126.020)
;
; EDDI BERLIN DEP 120.620 - Berlin Tempelhof
exten => 01-EDDI-120.620,1,Macro(com)
exten => 010403030812062,1,Dial(Local/01-EDDI-120.620)
;
; EDDI BERLIN DIRECTOR 121.120 - Berlin Tempelhof
exten => 01-EDDI-121.120,1,Macro(com)
exten => 010403030812112,1,Dial(Local/01-EDDI-121.120)
;
; EDDI BERLIN ARR 126.420 - Berlin Tempelhof
exten => 01-EDDI-126.420,1,Macro(com)
exten => 010403030812642,1,Dial(Local/01-EDDI-126.420)
;
; EDDI GND 121.950 - Berlin Tempelhof
exten => 01-EDDI-121.950,1,Macro(com)
exten => 010403030812195,1,Dial(Local/01-EDDI-121.950)
;
; EDDI TWR 119.570 - Berlin Tempelhof
exten => 01-EDDI-119.570,1,Macro(com)
exten => 010403030811957,1,Dial(Local/01-EDDI-119.570)
;
; EDDI BERLIN DIRECTOR 136.100 - Berlin Tempelhof
exten => 01-EDDI-136.100,1,Macro(com)
exten => 010403030813610,1,Dial(Local/01-EDDI-136.100)
;
; EDDI TWR 118.100 - Berlin Tempelhof
exten => 01-EDDI-118.100,1,Macro(com)
exten => 010403030811810,1,Dial(Local/01-EDDI-118.100)
;
; EDDI BERLIN DEP 119.500 - Berlin Tempelhof
exten => 01-EDDI-119.500,1,Macro(com)
exten => 010403030811950,1,Dial(Local/01-EDDI-119.500)
;
; EDDI BERLIN ARR 119.620 - Berlin Tempelhof
exten => 01-EDDI-119.620,1,Macro(com)
exten => 010403030811962,1,Dial(Local/01-EDDI-119.620)

What does the above mean? There are two lines (three with the comment) for each frequency: The first one sets up an extension named "01-EDDI-119.500". Yes, for VoIP you can use textual extensions but be careful if you want to setup your Asterisk-Server with POTS (=Plain old telephone service). Therefor you need the second line which is the same as above but without dashes and the letters in the decimal representation of the ASCII Code. The second line does only a "rewrite" of the numerical representation to the textual one.

For setting up all airports you can write your own simple script. But this maybe also not needed in further versions of FGCOM.

After editing the extensions.conf file you have to reload the extensions file (e.g. "asterisk -rx extensions reload").

You can add further nice goodies to your extensions.conf: MorseCode() for morsing the code of the VOR (MorseCode() will only work in Asterisk >= 1.4), Recording of metar data and playing this recording back when using the frequency of the metar information, ...

===Setting up user accounts===

The user accounts are located in the file iax.conf (and perhaps also in sip.conf, but this is not necessary). The top of the file should look like this:

[general]
bandwith=low
disallow=lpc10
jitterbuffer=yes
forcejitterbuffer=no
tos=lowdelay
autokill=yes
disallow=all
allow=alaw
allow=gsm
allow=ilbc
allow=g726
allow=ulaw
language=en
maxauthreq=10
context=guest
;
[guest]
type=user
username=guest
context=guest
qualify=yes
callerid=Guest IAX User
host=dynamic
;

You may want to disallow more codecs or want to allow additional codecs (such as speex). But have in mind that the internal mixing of the conferences are done in "ulaw". But "ulaw" needs about 80 kBit/s because it does no compression. So you have to think about what's better for you: less bandwidth (per user) and more CPU usage or more bandwidth (per user) and less CPU usage... you should also consider the "sound" of some codecs may not have the 'real radio sound'.

For each user you have to add a bunch of lines to your iax.conf file:

[<USERNAME>]
type=user
username=<USERNAME>
secret=<PASSWORD>
context=default
host=dynamic
nat=yes
notransfer=yes

You just have to fill in the <USERNAME> and <PASSWORD>. After each change you have to reload the configuration (e.g. "asterisk -rx reload chan_iax2.so"). Perhaps you want to write scripts for automatic configuration and so on. But be warned: Further versions of fgcom may use the multiplayer servers for getting usernames and position data and you have to change your scripts.

===Problems?===

If you have problems you can contact me via email at "dcoredump AT gmail.com".

<br><br>
=='''External links'''==
* [http://squonk.abacab.org/dokuwiki/fgcom Old Official website]
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]
* [http://sourceforge.net/projects/fgcom/ fgcom(SourceForge-Project)]

<br><br>
==Development==

TODO
<br><br>
=='''Status'''==
*'''March, 2009:'''
Adding User-Informations for installing, using, maintaining FGCOM on different platforms.

*'''18 November, 2008:'''
Latest SVN (rev 163) has the compile problems fixed. Also we have a '''new server: fgcom.flightgear.org.uk'''. User accounts not required (ie. do '''not''' use -U or -P)
*'''31 October, 2008:'''

The latest SVN release at this time is the '''r149''' which does not compile due to a constant that is not defined (STL_STRING). Such constant appears at line 57 in the file ''src/fgcom_init.cpp'' which is:
''#include STL_STRING''

I guess that such constant must point to the STL library include file but I am not sure.
I revert to the '''r148''' SVN version which successfully compiles.

Command to get such version is: ''svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148''

* '''19 June, 2008:''' Currently the server is <u>down</u> due to hardware problems. It is unknown when the service comes back because he currently has no time to fix the problems.

* '''22 November 2007:''' Due to heavy development at this time there may be some differences between the information on the web pages and the installation. Please follow the discussions on the FlightGear development list!

<br><br>
=='''See also'''==
*[[FlightGear related projects]]

[[Category:Software]]

File:F-14b-sas-switches.png

2010-03-14T21:28:05Z

Xiii:

Grumman F-14 Tomcat

2010-03-14T21:27:19Z

Xiii: Added SAS panel image

{{infobox Aircraft
|image =F-14.jpg
|name =F-14 Tomcat
|type =Interceptor/multi-role Fighter aircraft
|livery =U.S. Navy
|authors =Enrique Laso, Alexis Bory (cockpit)
|status =Production
|fdm =YASim
|3dcockpit = √
|carrier = √
|fgname = f-14b
}}
The '''Grumman F-14 Tomcat''' is a supersonic, twin-engine, two-seat, variable geometry wing [[aircraft]]. The F-14 was the United States Navy's primary maritime air superiority fighter, fleet defense interceptor and tactical reconnaissance platform from 1974 to 2006. It later performed precision strike missions once it was integrated with the Low Altitude Navigation and Targeting Infrared for Night [http://en.wikipedia.org/wiki/LANTIRN LANTIRN] system. The F-14 was developed after the collapse of the [http://en.wikipedia.org/wiki/F-111B F-111B] project, and was the first of the American teen-series fighters which were designed incorporating the experience of air combat in Vietnam against MiGs.

It entered service in 1972 with the U.S. Navy, replacing the [[McDonnell F4 Phantom II]]. It was later exported to the former Imperial Iranian Air Force in 1976, during a time when the US still had good relations with Iran. It was retired from the active U.S. Navy fleet on 22 September 2006, having been replaced by the [[F/A-18 Hornet|F/A-18E/F Super Hornet]]. As of 2007, it remains in service only with the Islamic Republic of Iran Air Force.

==Keyboard Controls==
===Flight Controls===
{| class="prettytable"
|Home
|Increase elevator trim
|-
|End
|Decrease elevator trim
|-
|] or f
|Lower flaps
|-
|[ or F
|Raise flaps
|-
|s
|Increase speed brakes
|-
|S
|Decrease speed brakes
|-
|Ctrl-b
|Toggle speed brakes
|-
|'''*note*'''
| Speed brakes have a different increase/decrease key assignment in a coming release and on CVS
|-
|k
|Increase speed brakes
|-
|j
|Decrease speed brakes
|-
|}

[[Image:F-14_cockpit.jpg|thumb|270px|Cockpit of the F-14.]]
[[File:SunsetF-14.png|270px|thumb|right|A nice scene with the F-14.]]

===Automatic Flight Controls===
{| class="prettytable"
|a
|Toggle APC (Landing Automatic Power Control)
|-
|Ctrl-d
|Toggle DLC (Landing Direct Lift Control)
|-
|d
|DLC increase
|-
|D
|DLC decrease
|-
|Ctrl-t
|Toggle [http://en.wikipedia.org/wiki/Aircraft_flight_control_systems AFCS] (Defaut Attitude Mode)
|-
|Ctrl-a
|Enable AFCS Altitude Mode
|-
|*
|Engage AFCS Altitude Mode
|-
|Ctrl-h
|Enable AFCS Heading Mode
|-
|Ctrl-s
|Toggle ground spoilers armed
|}

===HSD - radar and RWR===
{| class="prettytable"
|h
|Cycles through HSD modes: radar - compas - ECM (RWR)
|-
|E
|Decrease Radar Range
|-
|R
|Increase Radar Range
|-
|Ctrl-r
|Toggles Radar Standby Mode. In standby mode the radar doesn't emit and the "STAND BY" words are displayed on the HSD screen when in TID mode.
|}

===Carrier operations===
{| class="prettytable"
|O
|Lower the hook
|-
|o
|Raise the hook
|-
|L
|Engage launch bar
|-
|C
|Release catapult
|-
|}

===Miscellaneous===
{| class="prettytable"
|e
|Toggle canopy and access ladder
|-
|u
|Toggle refuelling probe
|-
|w
|Cycle armament selector
|-
|Ctrl-o
|Toggle oversweep (on ground only, otherwise sweep is automatic)
|-
|Ctrl-v
|Toggle between RIO (Radar Intercept Officer) and pilot view
|-
|}

==Aircraft help==
===On Shore Takeoff===
* With wings on over sweep position (parking position) the elevator command is inhibited... just in case...
* Check air brake in.
* Fuel level: The Flighfgear F-14 has a '''10% fuel''' level and no external load '''at start up'''. This means the aircraft will be very light and have a strong tendency to raise the nose when accelerating on the runway. With less weight on the nose wheel, the nose wheel steering loose its efficiency. If the pilot use afterburners for take off, the loose of nose wheel steering efficiency is increased (afterburners are not necessary for take off). '''Set a suitable fuel level before take off.'''
* Flaps: Set full flaps.
* Elevators: The pilot will need to maintain a correct (leveled) attitude using the stick. Push the stick forward to prevent nose pitching up at the begining of the take off run, release slightly as speed increase, pull smoothly when reaching rotation speed (150kts).
* Rudder: Currently the FDM use a small rudder rate of move to damp some nasty oscillations when the rudder is not moved enough smoothly. '''If not anticipated''', this delay will cause overshooting the desired rudder effect, then a strong counter action on the rudder will be applied by the pilot on the rudder with again an overshoot... That's a typical [http://en.wikipedia.org/wiki/Pilot-induced_oscillation pilot-induced oscillation]. To avoid this set a small amount of rudder, wait for the effect, see if it's enough, then add a small amount of rudder again if needed... when doing so the pilot will prefer increasing the power smoothly. Now the aircraft will quickly gain speed while covering the runway and the rudder effect will increase, thus decreasing the needed delay and the amount of pressure on the stick to match the desired effect.

===Autopilot Operation===
* The main mode is '''Attitude Hold Mode''', '''Ctrl-t'''. Other Modes need this main mode activated before being selected. Switching off '''Attitude Mode''' disables all other modes . When in '''Attitude Mode''', the autopilot disengages whenever a certain pressure is put on the stick, and it reengages when the stick is back in the center position . '''Attitude Hold Mode''' will hold pitch attitudes up to plus or minus 30 degrees, and bank angles up to plus or minus 60 degrees.
* It shall be switched off for aerobatics and inverted flight .

====Autopilot Altitude Mode====
* Once in the Attitude Mode, you can select '''Altitude Mode''' by hitting '''Ctrl-a''', then the '''AP REF''' indicator, (left of the '''VDI''') will illuminate, when at the desired altitude using normal stick control, engage by hitting '''*''', (asterisk) . The autopilot will then maintain your altitude.
'''CAUTION''' - at high speeds, it is imperative to stabilize your aircraft prior to engaging Altitude Mode !

====Autopilot Heading Mode====
* Once in the Attitude Mode, you can select '''Heading Mode''' by hitting '''Ctrl-h''' . After maneuvering the aircraft into the desired reference heading, release the control stick at a bank angle of less than 5 degrees . The autopilot will then hold the aircraft on the selected heading.

* Autopilot needs '''SAS''' channels to be engaged, which is the default . '''SAS''' Pitch and Roll channels may be disengaged by actuating switches located on the '''AFCS''' ('''Automatic/Analog Flight Control System''') panel .[[Image:F-14b-sas-switches.png|thumb|270px|SAS Panel.]]

===Landing Automatic Power Control, (APC) Operation===
* The '''APC''' is a closed loop system that automatically regulates basic engine thrust to maintain the aircraft at an optimum approach angle of attack for landing .
* Prior to engage '''APC''', gear handle must be down with weight off wheels, and the throttles must be set between 98 percent rpm and 68 percent rpm, (as shown on the panel gauges).
* Type '''a''' to toggle the '''APC on/off'''. APC is also disengaged by setting the throttles to MIL, (98 percent rpm) or idle, (68 percent rpm) or raising the landing gear handle or when weight on the wheels .
* When disengaged the '''AUTO THROT''' caution light, (on the left side of the HUD) illuminates for 10 seconds .

===Landing Direct Lift Control, (DLC) Operation===
* During landing approaches, the spoilers and horizontal stabilizers can be controled simultaneously to provide glidepath correction without changing power setting or angle of attack.

===Ground Spoilers Operation===
* Ground spoilers (that is [http://en.wikipedia.org/wiki/Elevon elevons] used as air-brake ) provide additional drag immediately after the touch down. Before the landing, arm the ground spoilers by hitting '''Ctrl-s''' . After the aircraft hits the runway, pull the throttle to idle, then the spoilers (elevons) get fully deployed.

==Pilot's Cockpit==
[[Image:F-14b-pilots-display-control-panel.jpg|thumb|270px|Pilot's Display Control Panel.]]
===Displays Control Panel===
* The Display Control Panel is located on the right side of the pilot's main panel, under the Hook lever. The '''3 botom switches''' respectively turn the '''VDI''', '''HUD''' and '''HSD''' displays '''on/off'''. The '''HSD MODE''' switch is also available, it selects '''NAV''' or '''TID''' or '''ECM''' mode. This can also be achieved by cycling through these 3 modes with the "'''h'''" key. (''Note: the '''NAV MODE''' push buttons - '''TO''', '''CRUISE''', '''A/A''', '''A/G''', '''LDG''' - are not operational yet.'')
** '''VDI: Vertical Display Indicator'''. Shows the aircraft attitude in roll and pitch, with an artifitial horizon and magnetic heading.
** '''HUD: Head UP Display'''.
** '''HSD: Horizontal Situation Display'''. HSD shows either:
***in '''NAV''' mode: compas with navigation indications,
***in '''TID''' mode (Tactical Information Display): an horizontal representation of the tactical situation (that is informations provided by the RIO from what he sees in his radar displays).
***in '''ECM''' mode: a representation of radar threats around the aircraft.

===VHF===
* Located on the RIO's left console, 3 bands: 30-88 MHz, 108-174 MHz, 225-400 MHz. Modes '''TR''' and '''TR-G''' set '''COMM1'''. Mode '''DF''' sets '''NAV1''', that is '''Direction Finder''' displayed with the single needle in both '''BDHIs''' (Bearing, Distance, Heading Indicator) . You have Comm *or* DF. Storing frequencies (up to 20 channels) '''a - PRESET''' select the desired channel, '''b - READ''' tune the desired frequency, '''c - LOAD''' stores the frequency in the previously selected channel.

===UHF===
* Located on the pilot's left console, 225-400 Mhz. ADF is not enabled on this radio.

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]
=== Links ===
* http://en.wikipedia.org/wiki/F-14 - F-14 Tomcat
* http://www.globalsecurity.org/military/systems/aircraft/f-14.htm - F-14 Tomcat
* http://www.fas.org/programs/ssp/man/uswpns/air/fighter/f14.html - F-14 Tomcat
* http://www.anft.net/f-14/f14-specification.htm - Home of M.A.T.S.
* http://www.navyair.com/LSO_NATOPS_Manual.pdf - NATOPS LANDING SIGNAL OFFICER MANUAL

{{Grumman}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]

Using TerraGear

2009-12-08T22:48:20Z

Xiii: /* Elevation data */ Update the new location of SRTM .hgt files

{{WIP}}
[[Image:Terragearprocesschart.png|thumb|TerraGear Process Flow Chart]]

The terrain used in [[FlightGear]] (the land over which one flies, its texturing (by land usage type), the rivers and lakes and so forth) are generated by software from a sister project called [[TerraGear]]. TerraGear is used to read in geographical data (descriptions of ground elevations, land cover (usage) information, airport locations and layouts, and so forth) and output terrain over which one can fly.

For a variety of reasons, you might want to build terrain yourself, rather than downloading it from the available scenery on FlightGear. For instance, if you use [[TaxiDraw]] to modify/improve information about an [[:Category:Airports|airport]]'s taxiway/apron layout, you might wish to see how that modified airport would look in the scenery before deciding you're happy with the results. Maybe the official scenery is too detailed for your slow machine, and you'd like to build terrain using a digital elevation model (DEM) with poorer resolution, to decrease the number of polygons and thus improve your framerates. Or maybe you've got a fantastically fast machine, and you want to build your own terrain using higher-resultion vector data (vmap1, Tiger, osm) to get better roads/streams. For all these reasons, learning how to use TerraGear is a good idea.

==Obtaining TerraGear==
You can either build TerraGear yourself, or download a pre-compiled binary. The later is the easiest and advised for starters.

* '''Building TerraGear''' is explained in [[Building TerraGear|this article]].
* '''Downloading TerraGear binaries'''
*# Download the latest TerraGear-cs-Win32-....zip file from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/.
*# Create or choose a base directory, which you will subsequently use to work with the TerraGear tools.
*# Unzip the package into a sub-directory named <tt>Terragear/</tt> in the base directory.

==Using TerraGear==
Before you start, you need to decide which area of scenery you want to build, as a rectangle defined in terms of latitute and longitude. The smaller the area of scenery you generate, the smaller the amount of data you will need, and the less CPU time it will take. For example, if you are just interested in generating a new airport layou at 12.3W 34.4N, then simply generating the scenery between 12W 34N and 11W 35N would be sufficient.

Write down the bounding box (minimum and maximum longitude and latitude) for the scenery you want to generate. Remember that West and South are negative - i.e. 4W 10S would be -4, -10. Try not to get mixed up, otherwise you'll end up generating scenery or airports on the other side of the planet!

You'll be dealing with multiple different types of data in various formats. Create a new directory for your scenery work. Underneath this, create the following sub-directories:

* '''data/''' - for raw and pre-processed data (eg elevation files)
* '''output/''' - for the scenery files you will create
* '''work/''' - for data that has been processed (eg by shape-decode) and is ready to be munged into scenery
Terragear needs three different pieces of information to generate scenery.

* The elevation of the land (provided by SRTM)
* The location and layout of airports (provided by apt.dat)
* Whether a given lat/lon is sea, land, city, forest, town, road, railway (provided by VMAP0)
We'll deal with each of these data types in turn, from how to get hold of the data, through pre-processing. Finally, we'll describe how to bring it together into data that FlightGear can use.

The order in which we complete these steps is important- for example the airport data relies on the elevation data to determine the elevation of the airports.

===Obtaining and processing data===
Terragear needs three different pieces of information to generate scenery.

* The elevation of the land (provided by SRTM)
* The location and layout of airports (provided by apt.dat)
* Whether a given lat/lon is sea, land, city, forest, town, road, railway (provided by VMAP0)

'''<u>Please note:</u> for inclussion in the official FlightGear scenery, all data <u>must</u> come from [[GNU GPL]] compatible sources! The in this article stated sources can be used.'''

====Elevation data====
The best elevation data currently available is from the Shuttle Radar Topography Mission (SRTM). There are two types of SRTM data:
* Highly accurate 1-arcsecond resolution data, known as SRTM-1, for the USA
* Less accurate 3-arcsecond data, known as SRTM-3, for the rest of the world.
From now on, we'll assume you are using SRTM-3 data. Unless otherwise noted, the process for SRTM-1 is identical.

You can get download the appropriate data from http://dds.cr.usgs.gov/srtm/. You want all .hgt.zip files covering your region of interest. Depending on the size of your scenery, there may be quite a few. Download them to <tt>data/SRTM-30/</tt> in your base directory. (The reason why the directories are called SRTM-30 is because genapts will look for a few known, hardcoded directories in it's working directory. SRTM-30 is one of them and this is the least confusing in that list.)

Now we've got the data, we need to convert it into something of use to TerraGear. First, you need to unzip each of the .hgt files. After that, open the commandline (<tt>Run > cmd.exe</tt>) and change into the base directory (<tt>cd .../.../TerraGear</tt>).
* '''NOTE:''' If you want to create a batch-file, replace <tt>%f</tt> with <tt>%%f</tt>, see [http://technet.microsoft.com/en-us/library/bb490909.aspx]
* '''NOTE:''' For SRTM-1 data, replace the <tt>3</tt> by a <tt>1</tt> in the first argument to hgtchop

Then type this:
for %f in (./data/SRTM-30/*.hgt) do ./Terragear/hgtchop.exe 3 %f ./work/SRTM-30

Now you will get a lot of .arr.gz files in your work/SRTM-3/ directory. We need to convert these to the .fit.gz format. Run the commandline again with
* '''NOTE:''' the space and dot at the and are important!

./Terragear/terrafit.exe .

====Airport data====
Now we've got elevation data, we can generate our airports. First, create a <tt>data/airports/</tt> directory and copy in your apt.dat file. This may be direct from your FlightGear data package (though you'll need to unzip it), or it may be one that you've modified with [[TaxiDraw]].

The command to create airports is "genapts". Run it without any arguments to see the various command-line options.

If it is simply run with a specified apt.dat and work directory, it will generate airport layouts for every airport in the file, which can take a long time.

If you are just creating a single airport and you know the ICAO ID (e.g. [[KSFO]], EGPH, EG32), use is as follows from your root scenery directory (i.e. the directory above your data, work and output directories). If you use an apt.dat file with one single airport in it you should omit the "--airport" parameter.

genapts --input=data/airports/apt.dat --work=./work --airport=<AIRPORT_ID>

If you are generating a larger set of scenery, then you can specify the minimum and maximum longitude and latitude.

Genapts will create two sub-directories in your work directory:
* AirportArea/
* AirportObj/

These contain the definitions of the airport layout and any objects present (e.g. windsocks).

====Landuse data====
The final piece of data we need to generate is the landuse data. In general, this is taken from the VMAP0 dataset as shapefiles from the scenery database mapserver, but other sources can be used and are used.

The landuse data can be split into a number of different types:

* '''Landmass''' separates the land from the sea. It is used as a mask for all other data. The most commonly used is the VMAP0 Landmass, but GSHHS can also be used.
* '''Land use data:''' defines whether a piece of land is forest, urban, sand, lava, glacier etc. These are usually VMAP0 data, defined as polygons.
* '''Line data:''' includes railroads, streams, roads. Typically VMAP0, but also Open Street Map for roads.
* '''Point data:''' is currently only used for defining towns.

By far the easiest way to get this data is to download shape-files from the wonderful [http://mapserver.flightgear.org MapServer]. This provides access to a database of information, and allows you to download the specifi shapefiles for your scenery area. Click on the Download Shapefiles link (or go direct: http://mapserver.flightgear.org/download.psp). Enter in the bounding box of the scenery you want to generate, select the shapefiles you want, and click download. For your first scenery generation, you want all of the ones listed under VMap0 (with prefix v0_).

Download each of them into a <tt>data/shapefiles/</tt> directory.

You can load these shapefiles into a GIS editor such as [[QGIS]] or GRASS to view and edit. This is a good idea to verify you have the correct files! Later on, you can experiment with replacing various shapefiles with other versions (GSHHS for coastline, OSM for roads etc.).

You now need to decode these into TerraGear format. This is done with the shape-decode command.

There are three important command-line arguments to shape-decode:
* the filename of the shapefile (without the .shp extension) you want to decode
* the directory you want to write the data to
* the material type to use.

Each of the shapefiles maps onto one of the material types defined in your materials.xml files. The mapping is pretty obvious, e.g. v0_mixedcroppasturecover maps to MixedCropPastureCover. Note that the material types are case-sensitive, so it is a good idea to have your materials.xml file to hand so you can check. The exception is v0_landmass, which MUST be mapped onto the type Default.

Additionally, there are a number of optional arguments, to indicate the width of line data (for roads, streams, railways), how large to make point data (for towns) and how long the longest straight line is allowed to be.

For example, to decode the v0_landmass shapefile, you use the following command:

shape-decode --max-segment 500 data/shapefiles/v0_landmass work/Landmass Default

To create streams of width 10 metres

shape-decode --max-segment 500 --line-width 10 data/shapefiles/v0_stream work/Stream Stream

To generate some towns about 1km across

shape-decode --point-width 500 data/shapefiles/v0_town work/Town Town

Run this command for each shapefile in the set.

==Generating scenery==
You will now have a work directory looking something like this:

AirportArea SRTM-30
AirportObj Stream
Bog IrrCropPastureCover Town
Lake Urban Landmass
Railroad DryCropPastureCover Road
EvergreenBroadCover Marsh Sand
MixedCropPastureCover ScrubCover
GrassCover MixedForestCover Shared

Now we can actually generate the scenery. This is done by the fgfs-construct command. Run the command with "--help" to get usage information.

We need to define:
* the work (--work-dir) and output (--output-dir) directories
* the center of the scenery we want to generate (--lat, --lon)
* the radius (--xdist, --ydist) from which to generate
* All the work directories to include in the scenery.

For example:
fgfs-construct --work-dir=./work --output-dir=./output --lon=55 --lat=60 --xdist=3 --ydist=3 \
AirportArea SRTM-30 AirportObj Stream Bog IrrCropPastureCover Town Lake Urban Landmass Railroad \
DryCropPastureCover Road EvergreenBroadCover Marsh Sand MixedCropPastureCover ScrubCover GrassCover \
MixedForestCover

When this finishes, the output directory will contain a scenery sub-tree.

Point to it by setting either [[$FG_SCENERY]] or by using the --fg-scenery command-line option to fgfs, and give your new scenery a try!

==Troubleshooting==
Below is a list of common problems and solutions. If in doubt - Google it. Many problems (particularly when compiling TerraGear) have been hit before:

* Crashes in genapts. Sometimes genapts will crash when dealing with a particular airport. In that case, try running it again with the --start-id argument to start at the airport it failed on, and the --nudge argument which tries to nudge the calculations in the right direction.
* fgfs-construct Killed. The fgfs-construct process may kill itself if it is using too many system resources. Increasing the values for setrlimit in src/BuildTiles/Main/main.cxx is the best solution.
* Airports appear in the bottom of holes, or there are spaces between the airports and the scenery. This typically happens when genapts is unable to find the correct elevation data, or the elevation data changed between running genapts and shape-decode. Try generating a single airport in your scenery area using genapts, and look at the output. In particular, make sure there is a work/SRTM-30 directory.
* Only the airports appear in the scenery. There are three typical causes for this:
** You didn't download the correct shapefiles for the area.
** You haven't run shape-decode on the v0_landmass shapefile as Default
** You didn't include the correct directories in fgfs-construct.
* Generate scenery includes data removed from the shapefiles. If you are editing shapefiles, you need to delete the appropriate work subdirectory before running shape-decode. Otherwise your changes will be in addition to those already present.
* All the scenery is flat and at sea-level. Typically this is because you didn't include any elevation data in your fgfs-construct command. Make sure there's a STRM-30 directory included in the command-line.
* All terrain copies the material of a certain shapefile. You have probably forgotten to put each of the downloaded shapefiles in a seperate directory inside the Data/shapefiles directory.

{{Terra}}

[[Category:Scenery enhancement]]

Grumman A-6E

2009-10-15T18:46:28Z

Xiii: /* Aircraft help */

{{infobox Aircraft
|image =A-6E.jpg
|caption = The "Intruder"
|name =Grumman A-6E Intruder
|type =Attack aircraft
|authors =Alexis Bory
|fdm =YASim
|status =Beta
|fgname =<tt>A-6E</tt>
}}

The Grumman A-6 Intruder is available for FlightGear 1.0, and is capable of air-to-air refueling and landing on the carrier in that version. It features a high-quality 3D cockpit, avionics, and exterior model.

The FG model is modeled with [[Tactical Air Navigation]]

==About the aircraft==
The '''A-6 Intruder''' is an American twin jet-engine, mid-wing attack aircraft built by Grumman Aerospace. In service between 1963 and 1997, the Intruder was designed as an all-weather replacement for the piston-engined A-1 Skyraider medium attack aircraft. A specialized electronic warfare derivative, the EA-6B Prowler, remains in service as of May 2008. As the A-6 was slated for retirement, its precision strike mission was taken over by the now retired F-14 Tomcat equipped with LANTIRN, which has subsequently passed on the role to the F/A-18E/F Super Hornet.

An A-6E Intruder is on display at the [[National Air and Space Museum]].

==Aircraft help==
{| class="prettytable"
!Key
!Function
|-
|c
|Canopy open/close command
|-
|C
|Catapult launch command
|-
|k/j
|Air Brakes open/close
|-
|L
|Carrier Launch-bar engage
|-
|o/O
|Hook up/down
|-
|f/F
|Wing Fold up/down
|}

== Development status/Issues/Todo ==
'''Outside:'''
* Fix the relatively massive "hiccup" in elevator

== External links ==
* [http://en.wikipedia.org/wiki/A-6_Intruder Wikipedia's article on the A-6 Intruder]
* [http://croo.murgl.org/fgfs/A-6E/A-6E-A-6E-20071101.tgz Download the development version of the A-6E (11/01/2007)]

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Grumman}}

[[Category:Aircraft]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

Autopilot PID controller tuning resources

2009-10-01T21:06:51Z

Xiii: /* FlightGear PID Controller */

The [[FlightGear]] [[Autopilot]] is a modular system based on PID controllers. Here are some tips to help tuning such a controller. There is lot of documentation all over the Internet about how to tune the parameters, having this you will have to figure out how the Flightgear PID controller implementation works.

First of all, have a look at the code where you will see the algorithm wich is used for our autopilot. Checking existing autopilot configurations in Flightgear aircraft will also help.

There is actually a doc about filters in Flightgear documentation. Filters can be applied on input or ouput values, in other words, before and after the PID controller (execution).

=== FlightGear PID Controller ===
Knowing the algorithm is mandatory, certain values are forbidden, for example they can lead to a division by zero. Then you will have to understand where the parameters apply to act on the choosen correction module. See the schema which is a good reminder while testing.

[[Image:pid_controler.png|thumb|PID parameter's application]]
[[Image:pid_cotroler_data_graph.png|thumb|Datas of an Auto-trim PID Controler displayed as graphs]]

You can find good explanations on how to practically tune the controller. [http://en.wikipedia.org/wiki/PID_controller Wikipedia's article on the PID Controler]

=== Getting graphs of Controler action ===
While it's possible to tune a PID controller by testing directly the aircraft behaviour under the autopilot control, it can be really useful to get everything in graphical view.

First of all you'll have to turn the PID Controller's debug mode on. That is in the autopilot.xml you are working on. (I didn't try to turn on more than one PID controller's debugging support at the same time).

Then you will get 6 new values displayed on the console at each FG loop. You will need to catch them and format the values in one line. Here is an exemple of a parser script written in Perl:

<pre>
#!/usr/bin/perl -w
# prints: "input reference P I D output"

while (<STDIN>) {
if ($_ =~ /input\s=\s(-*\d+.*)\sref\s=\s(-*\d+.*)/) {
print STDOUT "$1 $2 ";
} elsif ($_ =~ /P:(-*\d+.*)\sI:(-*\d+.*)\sD:(-*\d+.*)/) {
print STDOUT "$1 $2 $3";
} elsif ($_ =~ /output\s=\s(.*)/) {
print STDOUT " $1\n";
}
}
</pre>

Then you can write them in a file...

<pre>
alexis@linear:~/fgfs$ /usr/local/bin/fgfs 2>&1 | ./PIDcontroler_parser.pl > my_file
</pre>

If you use Linux, You can run Kst simultaneously to read the datas on the fly and watch them displayed together in real time while testing the aircraft.

* [http://kst.kde.org/ Kst, real-time large-dataset viewing and plotting tool]

== Alternative Method ==
As an alternative to using the controller's debug output you can use the built in logging system of Flightgear. This can be configured through the preferences.xml file, or at runtime via the File->Logging menu option.

To tune a controller you would typically display the setpoint property and the controlled property in the same graph. Another property that is interresting too look at is the actuating property, wich can be for example the aileron control or the elevator control.
[[Category:Resource]]

Portal:Developer

2009-09-23T17:27:43Z

Xiii: return to english version

{{PortalMenu}}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">The Developer Portal</h2>
|-
|style="color:#000;"|
This portal is for developers contributing to FlightGear. If you want to help with FlightGears development, it's a good idea to subscribe yourself to the [http://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear devel] mailing list. The [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-devel list archive] is also available and should be searched before posting the same question.<br><br>
'''Please choose a sub-portal:'''
* [[Portal:Developer/3D Modelers|3D Modelers]]
* [[Portal:Developer/Aircraft|Aircraft]]
* [[Portal:Developer/Scenery|Scenery]]<br><br>
'''The FlightGear project is looking for organizations/individuals who would be willing to help sponsor a fulltime project coordinator/manager to help oversee the overall development process If you are interested in helping or have anything else to contribute to this issue, please subscribe to the the [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11813.html FlightGear Devel mailing list] to discuss details.''' (Note that the FlightGear project can apply for free funding/sponsoring with [http://www.nlnet.nl nlnet]-applications are to be sent [http://www.nlnet.nl/foundation/request/index.html here]-you can help prepare a template for applying: [[Funding Application]])
|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Current Events, Efforts/Branches & Work in Progress</h2>
|-
|style="color:#000;"|
*[[FlightGear Package Manager]] (New! Alpha release of [[Java]]/[[XML]] package manager!)
*[[Walk View‎]] (New! walk view code!)
*[[FlightGear Contest]]
'''[[Work in progress|More...]]'''

|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Latest Organizational Issues</h2>
|-
|style="color:#000;"|
* [[ Project Infrastructure Enhancements ]]
* [[Google Summer of Code Candidate Projects]] - application template to allow community members to prepare a possible application to decrease the effort required to actually apply
* [[Programming Resources]]
* [[ Tools of the Trade ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">FlightGear Issues</h2>
|-
|style="color:#000;"|
* [[Pending Patches]] (2 listed for the moment)
* [[Segfaults]] - Reproducible Critical Bugs in FlightGear
* [[Showstoppers]] - Annoying Issues in FlightGear
* [[FlightGear Glitches]] (graphical/scenery related glitches)
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Improvement Initiatives</h2>
|-
|style="color:#000;"|
* [[Improving Helicopter Realism]]
* [[Improving Glider Realism]]
* [[Improving Airliner Realism]]
* [[Improving RC/UAV Realism]]
* [[Usability Improvements]] (list of related feature requests)
* [[Eye Candy & Effects]] (list of related feature requests)
'''[[:Category:Code_Cleanup|More...]]'''

|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Compiling</h2>
|-
|style="color:#000;"|
* [[ Building FlightGear - Linux]]
* [http://macflightgear.sourceforge.net/home/documents/how-to-build-flightgear-cvs-on-mac-os-x/ Building FlightGear - Mac OS X]
* [[ Building FlightGear - Windows]]
* [[ Building FlightGear Launch Control ]]
* [[ Building Terragear ]]
* [[ Keeping FlightGear (win32) up to date without compiling]]
* [[ OpenSceneGraph ]]
* [[ Using TortoiseCVS with FlightGear ]]
* [[ FlightGear and Git ]]

|-
|}

|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Contributing</h2>
|-
|style="color:#000;"|
* [[Howto:Extending Nasal]]
* [[Howto:Creating new Subsystems]]
* [[Howto:Working with the Property Tree API]]
* [[ Code Cleanup ]]
* [[ Contributor Repositories ]] mirrors, branches and forks privately maintained by contributors
* [[ Submitting Patches ]]
* [[ Technical Reports ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Code Internals</h2>
|-
|style="color:#000;"|
* [[Command Parameters]]
* [[ File Formats ]]
* [[ Initialization Sequence ]]
* [[ Nasal scripting language ]]
* [[ Property Tree ]]
* [[ UML Diagrams ]]
* [[ YASim ]]
* [[ FlightGear 1.0 aircraft names for command line‎|1.0.0 a/c names for command line]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Todo</h2>
|-
|style="color:#000;"|
* [[ Bugs ]]
* [[ Feature Requests / Proposals / Ideas ]]
* [[ FGFS Todo ]]
* [[ FlightGear Expo Checklist ]]
* [[ Long Term Goals ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Done</h2>
|-
|style="color:#000;"|
* [[ Changes since 0.9.10 ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">HowTos</h2>
|-
|style="color:#000;"|

* [[Howto: Set up a multiplayer server|Set up a multiplayer server]]
'''[[:Category:Howto|More...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Nasal scripting</h2>
|-
|style="color:#000;"|
* [[ Nasal FAQ ]]
* [[ Nasal scripting language ]]
* [[ Nasal Snippets ]]
* [[ Nasal Modules ]]
* [[ Nasal Style Guide ]]
* [[ Writing simple scripts in %22nasal%22 ]]
* [[ Walk View‎]]
* [[Howto: Nasal in scenery object XML files]]
* [[Howto:Extending Nasal]]
|}
|}

__NOTOC__
__NOEDITSECTION__

== Developer Documentation ==
=== RFC Topics ===
'''Clarification:''' In its current form, the RFC section is exclusively based on and covered by previous mailing list and forum discussions (as well as various wiki entries), as such it is not supposed to reflect work in progress (RFC="Request For Comments" and not WIP), but is rather to be seen as an attempt to provide comprehensive analyses and summaries of key issues identified in various FlightGear related discussions and feature requests (which are to be linked to in the corresponding resource sections, if that didn't yet take place, it's because of most of these RFCs being indeed WIP).

Thus, RFC entries are not meant to imply anyone "working" on any of these issues, in fact only because an RFC entry is listed here doesn't necessarily mean that work on that particular issue is prioritized or generally endorsed by the FlightGear community.
These RFC documents are however intended to hopefully help increase and maintain awareness of long-standing issues and challenges affecting FlightGear's evolution and overall development progress in order to solicit community feedback about possible approaches to address these in an efficient and structured fashion.
Anybody is welcome to comment on, help refine and develop new strategies to tackle the challenges presented in these and future RFCs.

* [[Autopilot Enhancements]] - enhancing the autopilot infrastructure.
* [[Backwards Compatibility Initiative]] - discussing possible ways to improve FlightGear's backwards compatibility.
* [[Distributed Interactive Simulation|Multiplayer Enhancements]] - discussing possible steps to enhance FlightGear's Multiplayer support.
* [[FDM engine feature standardization]] - discussing possible steps to standardize feature support of mainstream FlightGear FDM engines.
* [[FlightGear Glass Cockpits]] - discussing required infrastructure changes to enable non-developers to easily access FlightGear-internals in order to enable them to model complex glass cockpit-type aircraft instrumentation systems.
* [[FlightGear Headless]] - discussing required steps to enable FlightGear to be used as its own regression testing framework
* [[FlightGear Sessions]] - discussing possible steps to finally allow aircraft to be reliably switched at runtime.
* [[Formalizing Aircraft Status]] - discussing suggestions about how to more properly describe aircraft development status.
* [[Keyboard function priority list]] - reorganizing FlightGear keybindings.
* [[Next Generation Scenery ]] - revamping the FG scenery engine.
* [[Property Tree Reorganization]] - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions).
* [[Recommended Property Tree Enhancements]] - discussing possible property tree enhancements to help ensure integrity of crucial runtime state.
* [[Recommended Project Policies]] - discussing recommended policies for future contributions to the project.
* [[Simplifying Aircraft Deployment]] - identifying potential steps to simplify deployment of FlightGear aircraft.

General Dynamics F-16 Fighting Falcon

2009-06-03T14:02:17Z

Xiii: /* Keyboard Controls */ cosmetics

{{infobox Aircraft
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = Production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = f16
}}

==Keyboard Controls==
'''Flight Controls'''
{| class="prettytable"
|Ctrl-b
|: Toggles speed brake
|-
|Delete
|: Toggles FBW (Fly by Wire) override
|}
'''Miscellaneous'''
{| class="prettytable"
|Ctrl-f
|: Triggers flare release
|-
|Ctrl-h
|: Toggles arrester hook
|-
|C
|: Toggles canopy
|-
|e
|: Fires the cannon
|-
|}
'''Radar'''
{| class="prettytable"
|Ctrl-n
|: Toggles Radar RWS / TWS AUTO Modes
|-
|E
|: Decreases Radar Range
|-
|R
|: Increases Radar Range
|-
|q
|: Toggles Radar Standby Mode
|-
|}

== Development status/Issues/Todo ==
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
**This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
**Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)

TDL FDM:
* Main U/C is above ground.
* Vibration when accelerating on the runway for takeof.

TDL Outside
* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)

TDL Cockpit and systems:
* HSI 3d model and textures.
* internal/external lighting panel.
* FMD's buttons pick animation. Define a logic in the FMD interactivity ?
* ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
* HUD modes:
** A/A mode
** Basic nav mode (those could be a first step in order to provide usability in short term)

Sounds: (Low priority)
* Establish a list of all sounds that can be produced by the F-16 and its driver:

Cockpit:
**switches
**knobs
**levers
**buttons
**wheels (ICP)
**rudder pedals
**ejection seat
**canopy **implemented**
**canopy lock **implemented**

Audio:
**"bitching betty"
***missile launch
***warning **implemented**
***chaff/flare
***jammer
**RWR
***radar signature identification sounds
****radar spike
****radar lock
**gear horn (currently implemented as alert?)

Pilot:
**breathing
**movement
**brevity comms

External-sounds:
**engine **implemented**
**landing gear
***up
***down
***broken
**ordnance
***jettison store(s)
***bomb drop
***missile launch
***20mm cannon **implemented**
**damage
***airframe overstress
***gun hit
***explosion
**Mid air refueling
***refueling door
****open
****close
***tank boom (tanker aircraft)
****connect
****disconnect

== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft|F-16 Falcon]]
[[Category:Aircraft TODO]]
[[Category:Military aircraft]]

Grumman F-14 Tomcat

2009-05-30T20:56:16Z

Xiii: cosmetics

General Dynamics F-16 Fighting Falcon

2009-05-28T09:38:19Z

Xiii:

{{infobox Aircraft
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = early-production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = <tt>f16</tt>, <tt>f16-3d</tt> (3d cockpit), <tt>f16at</tt> (F-16AT), <tt>f16-mlu</tt> (F-16AM)
}}

{|
|__TOC__
|}

==Keyboard Controls==
'''Flight Controls'''
{| class="prettytable"
|Ctrl-b
|toggle speed brake
|-
|Delete
|Toggle FBW (Fly By Wire) override
|}
'''Miscellaneous'''
{| class="prettytable"
|Ctrl-f
|trigger flare release
|-
|Ctrl-h
|toggle arrester hook
|-
|C
|Toggle canopy
|-
|e
|Fire the cannon
|-
|}
'''Radar'''
{| class="prettytable"
|Ctrl-n
|Toggles Radar RWS / TWS AUTO Modes
|-
|E
|Decrease Radar Range
|-
|R
|Increase Radar Range
|-
|q
|Toggles Radar Standby Mode
|-
|}

== Development status/Issues/Todo ==
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
**This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
**Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)

TDL FDM:
* Main U/C is above ground.
* Vibration when accelerating on the runway for takeof.

TDL Outside
* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)

TDL Cockpit and systems:
* HSI 3d model and textures.
* internal/external lighting panel.
* FMD's buttons pick animation. Define a logic in the FMD interactivity ?
* ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
* HUD modes:
** A/A mode
** Basic nav mode (those could be a first step in order to provide usability in short term)

Sounds:

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft|F-16 Falcon]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

General Dynamics F-16 Fighting Falcon

2009-05-28T08:28:38Z

Xiii: /* Development status/Issues/Todo */

{{infobox Aircraft
|image = General_Dynamics_F16.jpg
|name = General Dynamics F16
|type = Military aircraft
|fdm = JSBSim
|status = early-production
|authors = Erik Hofman, Martin "Pegasus" Schmitt (panel textures)
|fgname = <tt>f16</tt>, <tt>f16-3d</tt> (3d cockpit), <tt>f16at</tt> (F-16AT), <tt>f16-mlu</tt> (F-16AM)
}}

{|
|__TOC__
|}

== Development status/Issues/Todo ==
Issues to be fixed shortly:
* The first time the user change the view (ie. by hiting "v") there is a 10/15 seconds pause.
**This seems to be due to the liveries textures. Removing the Livery choice and all associated entry in the -set file doesn't change the delay. Then reducing and flatening (remove alpha channel) the main texture f16.rgb from 2048 to 1024 px reduce the delay to 6/7 sec, then flatening the transparent logo texture f16-trans.rgb reduce the delay to 3/sec.
**Solution: switch to PNG textures, remove transparency on logos or even remove logos. Use a different mapping layout with 4 x 1024^2 textures instead of 1 x 2048^2 texture. Optimize surface usage in the textures, flaten textures as much as possible. (see much more complicated and detailled f-14b which doesn't suffer delay)

TDL FDM:
* Main U/C is above ground.
* Vibration when accelerating on the runway for takeof.

TDL Outside
* flaps are in wrong position and can't be triggered.
** that's because the f16 is flight computer controlled, so this is correct and NOT an error. (this to be moved in flight documentation)
* pilot's shoulder patch is empty. (remove ?)
* engine turbines do not rotate (is it useful ?)

TDL Cockpit and systems:
* HSI 3d model and textures.
* internal/external lighting panel.
* FMD's buttons pick animation. Define a logic in the FMD interactivity ?
* ICP better texture. buttons pick animation. Define a logic in the ICP interactivity ?
* HUD modes:
** A/A mode
** Basic nav mode (those could be a first step in order to provide usability in short term)

Sounds:

== External links ==
== Related content ==
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

[[Category:Aircraft|F-16 Falcon]]
[[Category:Military aircraft]]
[[Category:Aircraft TODO]]

General Dynamics F-16 Fighting Falcon

2009-05-27T21:58:21Z

Xiii: /* Development status/Issues/Todo */