https://wiki.flightgear.org/w/api.php?action=feedcontributions&user=Alfo&feedformat=atomFlightGear wiki - User contributions [en]2024-03-29T04:55:05ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_August_2012&diff=52500FlightGear Newsletter August 20122012-08-02T18:56:00Z<p>Alfo: /* Updated aircraft */ ATC-FS update</p>
<hr />
<div>{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== Development news ==<br />
<br />
=== Canvas News ===<br />
<br />
=== Mailing list digest ===<br />
<br />
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Interview with a contributor (NAME) ==<br />
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].<br />
<br />
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.<br />
<br />
=== New hangers ===<br />
<br />
A new hanger is now available which is updated every Tue, Wed and Thursday with development updates, FlightGear news, tutorials and videos. Feel free to visit it here: http://lukeaflightg.blogspot.co.uk/<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
<br />
==== [[ATC-FS]] ====<br />
The Air Traffic Control tool ATC-FS got an update. The old radar screen was replaced by a radar screen, which can display fixes, navaids and ILS localizers. This new radar is resizable, so you can use your big screen more efficient.<br />
<br />
[[Image:ATC-FS.jpg|1000px]]<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== Airports ===<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Did you know? ===<br />
Did you know that the FlightGear project dates back to a discussion among a group of net citizens in 1996 resulting in a proposal written by David Murr? The original proposal is still available<br />
from the FlightGear website and can be found [http://www.flightgear.org/proposal-3.0.1 on the FlightGear website]. Read it, you'll learn a lot about FlightGears' roots which still lead the project spirit.<br />
<br />
=== Contributing ===<br />
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. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter|2012 08]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=52498ATC-FS2012-08-02T18:28:51Z<p>Alfo: /* Left Radar Panel */ Correct image link</p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.jpg<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Beta (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
'''ATC-FS''' (ATC, with flightstrips) is an [[air traffic control]] (ATC) aircraft, with the purpose to help an ATC controller keeping track of the aircraft around his airport as well as helping him guide the aircraft on approach and departure and aircraft just passing through his airspace. It can be added to FlightGear just as a regular aircraft and is built with XML and nasal.<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| r<br />
| Toggle radar screen<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + Z<br />
| Lower your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick an entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
{| class="wikitable"<br />
|Callsign<br />
|Flightrules<br />
|Departure<br />
|Assigned heading<br />
|Assigned speed<br />
|Info<br />
|-<br />
|colspan="2"|Aircraft Model<br />
|Destination<br />
|Assigned altitude<br />
|Communication method<br />
|Route<br />
|}<br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Left Radar Panel ==<br />
<br />
[[Image:ATC-FS-left.jpg|frame|none|alt=image]]<br />
<br />
# Two buttons for ATIS actions. The 'ATIS' button sends a ATIS message to the multiplayer chat. 'Info' button changes the information state and sends the new ATIS message. Right of the button you can see the current information state, in this screenshot 'B'.<br />
# All important weather information. Dew is Dewpoint, Vis is Visibility.<br />
# Checkboxes to control the information in the radar. Data will show more information for all items in the map.<br />
# Settings button will open the dialog to configure ATC-FS and the active runways. Below this button, the active runways are listed. 'To all' button will open a chat message directed to all airmen.<br />
# The Tracking section shows information about the currently tracked aircraft. The 'Toggle' button will toggle visual tracking.<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]<br />
<br />
= External links =<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16168 ATC-FS alpha] topic at the official forum.<br />
<br />
[[Category:Air_Traffic_Control]]<br />
[[Category:Aircraft]]<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=52497ATC-FS2012-08-02T18:28:11Z<p>Alfo: ATC-FS beta version</p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.jpg<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Beta (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
'''ATC-FS''' (ATC, with flightstrips) is an [[air traffic control]] (ATC) aircraft, with the purpose to help an ATC controller keeping track of the aircraft around his airport as well as helping him guide the aircraft on approach and departure and aircraft just passing through his airspace. It can be added to FlightGear just as a regular aircraft and is built with XML and nasal.<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| r<br />
| Toggle radar screen<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + Z<br />
| Lower your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick an entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
{| class="wikitable"<br />
|Callsign<br />
|Flightrules<br />
|Departure<br />
|Assigned heading<br />
|Assigned speed<br />
|Info<br />
|-<br />
|colspan="2"|Aircraft Model<br />
|Destination<br />
|Assigned altitude<br />
|Communication method<br />
|Route<br />
|}<br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Left Radar Panel ==<br />
<br />
[[Image:ATC-FS-radar.jpg|frame|none|alt=image]]<br />
<br />
# Two buttons for ATIS actions. The 'ATIS' button sends a ATIS message to the multiplayer chat. 'Info' button changes the information state and sends the new ATIS message. Right of the button you can see the current information state, in this screenshot 'B'.<br />
# All important weather information. Dew is Dewpoint, Vis is Visibility.<br />
# Checkboxes to control the information in the radar. Data will show more information for all items in the map.<br />
# Settings button will open the dialog to configure ATC-FS and the active runways. Below this button, the active runways are listed. 'To all' button will open a chat message directed to all airmen.<br />
# The Tracking section shows information about the currently tracked aircraft. The 'Toggle' button will toggle visual tracking.<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]<br />
<br />
= External links =<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16168 ATC-FS alpha] topic at the official forum.<br />
<br />
[[Category:Air_Traffic_Control]]<br />
[[Category:Aircraft]]<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-left.jpg&diff=52496File:ATC-FS-left.jpg2012-08-02T18:21:02Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS Beta left panel
|Source = fgfs
|Date = 2012-08-2
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS Beta left panel<br />
|Source = fgfs<br />
|Date = 2012-08-2<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|cc-by-sa-3.0}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS.jpg&diff=52495File:ATC-FS.jpg2012-08-02T18:12:04Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS beta screenshot
|Source = fgfs
|Date = 2012-08-2
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS beta screenshot<br />
|Source = fgfs<br />
|Date = 2012-08-2<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|cc-by-sa-3.0}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=FGCom_(before_3.0)&diff=51312FGCom (before 3.0)2012-06-28T11:28:11Z<p>Alfo: /* Using FGCom */ Change airport frequency range</p>
<hr />
<div>{{cleanup}}<br />
<br />
{{Infobox Software<br />
| title = FGCom<br />
| logo = <br />
| image = <br />
| alt = <br />
| developedby = Holger Wirtz, Martin Spott, Csaba Halasz<br />
| initialrelease = <br />
| latestrelease = <br />
| writtenin = <br />
| os = <br />
| platform = <br />
| developmentstatus = Active (2007-)<br />
| type = <br />
| license = [[GNU General Public License]]<br />
| website = http://sourceforge.net/projects/fgcom/<br />
}}<br />
'''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 [[Howto: Multiplayer|multiplayer]] events, like:<br />
<br />
* Flying in groups, see the [http://www.flightgear.org/forums/viewforum.php?f=10 multiplayer events forum]<br />
** Invite friends to a guided sightseeing tour in your most beloved area or do “Fly In's”<br />
** Do military training like [[Howto: Air-Air Refueling|“Air-Air-Refuelling”]], “Dog fights”, “Escort flights”, etc. <br />
* Offering additional services at an airport like [[Air traffic control|ATC]], [[Vehicle|snowplows, pushbacks]], [[FlightGear Race|racing-events]] etc.<br />
* Have a [[Dual control|real time flighttraining]] (e.g. pilot in Hongkong, teacher in Sydney), do [[Soaring|Glider-towing]], ask for on-line support during flight or just ask somebody flying a plane of interest about specifics.<br />
* Or just sit in a cockpit in Germany while sightseeing San Francisco in a [[Cessna C172|C172]], voice-chat with a Texan in a plane I dreamed of as a boy ([[Lockheed Constellation|Super Constellation]]) and both getting information from a New Zealand guy (it shall be a wonderful island – but do real people live there? He said: Yes!!).<br />
* And much more!<br />
<br />
You can even use it in models without radios - just use the standard FlightGear [[menu]] (<tt>Equipment > Radio Settings</tt>).<br />
<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 ==<br />
=== Prequisites ===<br />
==== Hardware Requirements ====<br />
If you are satisfied with the operation and responsetimes of your current FlightGear installation, then you should see no significant difference after adding the FGCom. If your FlightGear 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 FlightGear command-window.<br />
<br />
For details see the [http://www.flightgear.org/hardwarereq.html common hardware and driver requirements].<br />
<br />
Of course you will also need a connection to the internet for this real-time, worldwide voice communication.<br />
<br />
==== Software requirements ====<br />
{| border="1"<br />
|align="center" width="90px" |'''FlightGear''' ||The basic [[FlightGear]] Flight Simulation installation. This must be installed prior to installing FGCom ''(except if installing the Linux "Git complete" version which can install FGCom and FlightGear concurrently)''.<br />
|-<br />
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of 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 />
|}<br />
<br />
==== Nice to have ====<br />
{| border="1" cellpadding="10"<br />
|align="center" width="90px" | '''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<br />
|-<br />
|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 information. 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.<br />
|-<br />
|align="center" |'''SkyVector'''||[http://skyvector.com/ SkyVector] is a standalone Browser-Application. It does present a fantastic Fight-Planning tool, showing similar aspects like the "MPMap" - but is based on a an real Aeronatical map ("Sectional"). On it you can graphically plan you routs - see the "Help Video"-Icon in the Top-Menubar.<br />
But it does not directly link into FGFS, MPMap or Multiplayer -- and it covers only the domestic USA.<br />
|-<br />
|align="center" |'''Atlas'''||[[Atlas]] displays the current position of your airplane on an landscape type of map together with navigational information. It derives its data direct out of the installed FGFS databases. So you do not need any connections to the Internet.<br />
|-<br />
|align="center" |'''Festival'''||[http://www.flightgear.org/Docs/getstart/getstartch5.html#x10-1080005.7 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. <br />
|}<br />
<br />
=== Installing FGCom ===<br />
==== Install on Linux ====<br />
For Linux-Systems there are three ways to install:<br />
<br />
# '''Downloading from the “Distributor” (Debian, Ubuntu, Red Hat, Suse, etc.).''' <br />
#* '''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.<br />
#* '''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.<br />
#* '''Installation:''' Follow the usual procedures of your distributer on how to install additional packages.<br />
# '''Installing a “Git complete”''' <br />
#* '''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.<br />
#* '''Disadvantage:''' No automated maintenance available. The handling is a little different from the standard Menu-driven practice.<br />
#* '''Installation:''' [[Scripted Compilation on Linux Debian/Ubuntu]]<br />
# '''Compiling it locally:'''<br />
#* '''Advantage:''' After a successful installation it is integrated into the system like a package from the distributor.<br />
#* '''Disadvantage:''' No automated maintenance available. Also the user should have some basic knowledge of his system and its devices.<br />
#* '''Installation:''' [http://code.google.com/p/fgcomgui/wiki/Linux_Installation instructions]<br />
<br />
Then continue with testing on [[FGCOM Testing]].<br />
<br />
==== Install on Mac ====<br />
<br />
'''MacFlightGear 1.9.1/2.0.0'''<br /><br />
You can download the "MacFlightGear"-Application from the [http://www.flightgear.org/Downloads/binary.shtml#mac FlightGear download-center]. The current version 2.0.0 of the code does contain the FGCom and works for OSX >= 10.5. (with OSX versions < 10.5 you will end up with a generic "bus error" message).<br />
<br />
==== Install on Windows ====<br />
Please use the Windows installation description, available through [[FGCOM for Windows]].<br />
<br />
=== Testing ===<br />
During testing we will test/adjust:<br />
# the basic FGCom functions without FlightGear<br />
# FGCom together with FlightGear<br />
# the microphone and loudspeaker system<br />
<br />
For these tests please refer to [[FGCOM Testing]].<br />
<br />
=== Functional test & user briefing ===<br />
Experiences pointed out, that the cooperation between FGCom and FlightGear works more reliable, if FlightGear is started first. So we will start with setting up a flight-test-environment:<br />
<br />
==== Start FlightGear ====<br />
We suggest to use [[FGRun]] 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 FGCom-operation:<br />
<br />
If you don't have an icon available to start FGrun, then start FlightGear manually:<br />
<br />
# Start a [[Command line|command-window]]<br />
# Change into the directory in which FGFS was installed<br />
# Execute the following command or something similar<br />
{|<br />
! style="background:#efefef" | Linux<br />
|fgrun<br />
|-<br />
! style="background:#efefef" | Linux Git:<br />
|cd ~/fgfs<br />sh ./run_fgrun.sh <br />
|- <br />
! style="background:#efefef" | Windows<br />
|C:<br />cd 'C:\Program Files\Flightgear\win32'<br />fgrun.exe<br />
|}<br />
<br />
Wait for the program window to start and then define:<br />
<br />
# Start by '''choosing an airplane'''. For this first try we suggest the [[Cessna C172]]P, 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 />
# 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".[[File:FGrun_base.jpg|thumb|Basic & multiplayer options]]<br />
# Define the '''Multiplayer options:''' (see [[Howto: Multiplayer]] for details).<br />
#* “AI models” must be activated in order to see all traffic<br />
#* “Multiplayer” must be activated<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 and not as overcrowded as mpserver02) - you might try which server gives you the best response-times.<br />
#* Insert your “Callsign:” (max. 7 characters)<br />
#* define the “in” and “out” ports both with the standard “5000”<br />
#* With "Load/Save as" you may build up yourself a library of settings for different airports.<br />→ Click "Advanced".[[File:FGrun_IP.jpg|thumb|Advanced: Initial Position]]<br />
# In the “'''Advanced Options'''” check the following sections (click/select them in the left column):<br />
#* General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).<br />
#* Features: “AI Traffic” should be activated already<br />
#* 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 />
#** ''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.[[File:MPmap.jpg|thumb|[[MPMap]]]]<br />
# Open the '''[http://mpmap01.flightgear.org MPMap]'''<br />
#* if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”<br />
#* click on “nav”<br />
#* disable all options except “apt code”<br />
#* type “KPAO” into the filed “Navaids lookup”<br />
#* hit ENTER or click onto the reading-glass symbol<br />
#* click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”<br />
#* 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” <br />
#* then zoom into the airport<br />
#* set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen<br />
#* type those long/lat values into the field below and also the wanted heading of the plane while parking[[File:FGrun_net.jpg|thumb|Advanced: Network]]<br />
# '''Network:''' 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 />
#* 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".<br />
#* If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type<br />
<br />
{|<br />
! style="background:#efefef" | OS<br />
! style="background:#efefef" | to type<br />
! style="background:#efefef" | cap.<br />
! style="background:#efefef" | returned values<br />
|-<br />
! style="background:#efefef" | Linux <br />
|ifconfig <br />
|eth0<br />
|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 <br />
|- <br />
! style="background:#efefef" | Windows<br />
|ipconfig /all <br />
|et <br />
|Physikalische Adresse . . . . . . : 00-16-E6-40-AB-BF<br />
<br />DHCP aktiviert. . . . . . . . . . : Ja <br />
<br />Autokonfiguration aktiviert . . . : Ja <br />
<br />IP-Adresse. . . . . . . . . . . . : '''192.168.178.20''' <br />
<br />Subnetzmaske. . . . . . . . . . . : 255.255.255.0 <br />
<br />IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4<br />
|}<br />
#* '''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 “,”!![[File:FGrun_IO.jpg|thumb|Advanced: Input/Output]]<br />
# '''Input/Output:''' <br />
#* You do need a "generic" line as shown, because '''this defines the interface between FlightGear and FGCom'''.<br />
#** To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.<br />
#** Editing an existing line: Start by clicking onto the existing one, then change as required.<br />
#** Deleting an existing line: Click onto the line to be deleted, then hit "Delete"<br />
# '''Avionics:''' let us define: <br />
{|<br />
! style="background:#efefef" | Nav1:<br />
| 114.10 <br />
| San Jose VOR<br />
|-<br />
! style="background:#efefef" | Nav2: <br />
| 115.80 <br />
| SF VOR<br />
|-<br />
! style="background:#efefef" | ADF: <br />
| 379 <br />
| Brijj, beacon at SF<br />
|}<br />
#* And activate DME to Nav1<br />
#* There is no field to input COM-radios, but remember them for setting them later manually:<br />
{|<br />
! style="background:#efefef" | Com1<br />
| 118.60 <br />
| Paolo Alto<br />
|-<br />
! style="background:#efefef" | Com2 <br />
| 120.50 <br />
| San Francisco<br />
|}<br />
<br />
# '''Properties:''' <br />
#* Here you can define any presetting for any values in the FGFS. See e.g.: <tt>File > Browse Internal Properties</tt> in the FlightGear [[menu]].[[File:FGrun_prop.jpg|thumb|Advanced: Properties]]<br />
#* 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 />
#** Input a new line: Just hit “New” and type your string.<br />
#** Edit a line: Be sure first to click onto an existing item and then edit this “Property”<br />
#** Delete a line: Click onto the line to be deleted then hit "Delete"<br />
# Hit “OK” → “Run” and watch FlightGear 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 />
<br />
==== Start FGCom ====<br />
Open a [[Command line|command-window]] and change into the directory in which FGCom was installed (probably the same as FlightGear) and start FGCom. Do not use any other options than the server address “-Sfgcom.flightgear.org.uk”:<br />
{|<br />
! style="background:#efefef" |Linux <br />
|fgcom -Sfgcom.flightgear.org.uk <br />
|"-Sfgcom..." with capital "S"<br />
|-<br />
! style="background:#efefef" |Linux Git<br />
| cd ~/fgfs<br />sh ./run_fgcom.sh <br />
| for this “Git complete” you do not need to specify the server address, because it is embedded in the script-file.<br />
|- <br />
! style="background:#efefef" |Windows <br />
|cd 'C:\Program Files\Flightgear\win32'<br />fgcom.exe -Sfgcom.flightgear.org.uk <br />
|"-Sfgcom..." with capital "S"<br />
|}<br />
For the following test position this command-window somewhere, where you can monitor it throughout the test.<br />
<br />
The first response should be:<br />
/fgcom - a communication radio based on VoIP with IAX/Asterisk <br />
(c)2007 by H. Wirtz <wirtz@dfn.de> <br />
Version 1.2.2 build 206M <br />
Using iaxclient library Version SVN 206M <br />
<br />
Successfully parsed command-line options. <br />
Reading list of airports...done. <br />
Initializing IAX client as guest:xxxxxxxxxxx@fgcom.flightgear.org.uk<br />
If your printout up to that line is different go back to chapter [[FGCOM#Test the basic function|Test the basic function]]<br />
<br />
{|<br />
|+<br />
|-<br />
|width="300"| ||<br />
|-<br />
|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: ||<br />
|-<br />
|<br />
Selected frequency: 119.650 <br />
Call rejected by remote<br />
|<br />
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.<br />
|-<br />
|2) Switch COM1 to 118.60 (needed at Palo Alto):<br />
|-<br />
|<br />
Selected frequency: 118.600 <br />
Hanging up call 0 <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) <br />
|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 />
|-<br />
|<br />3) Press your PTT (PushToTalk on space-bar and joystick, as available):<br />
|-<br />
|<br />
[SPEAK] unmute mic, mute speaker <br />
[LISTEN] mute mic, unmute speaker <br />
[SPEAK] unmute mic, mute speaker <br />
[LISTEN] mute mic, unmute speaker <br />
|Only in between “SPEAK” and “LISTEN” you are able to talk to others.<br />
|-<br />
|<br />Now lets set/verify the other Radios:<br />
* COM2 = 120.50 San Francisco<br />
* NAV1 = 114.10 San Jose<br />
* NAV2 = 115.80 San Francisco<br />
4) Pressing Upper+Space will switch to the next radio: '''NAV1'''<br />
|-<br />
|<br />
Radio-Select: NAV1 <br />
Selected frequency: 114.100 <br />
Hanging up call 0 <br />
Call rejected by remote <br />
[LISTEN] mute mic, unmute speaker <br />
|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 />
|-<br />
|<br />5) Pressing Upper+Space once more switches to '''COM2'''<br />
|-<br />
|<br />
Radio-Select: COM2 <br />
Selected frequency: 120.500 <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (29.1 km) <br />
[LISTEN] mute mic, unmute speaker <br />
Call 0 accepted <br />
Call 0 answered<br />
|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 />
|-<br />
|<br />6) Pressing Upper+Space once more switches to '''NAV2'''<br />
|-<br />
|<br />
Radio-Select: NAV2 <br />
Selected frequency: 115.800 <br />
Hanging up call 0 <br />
Airport SAN FRANCISCO VOR-DME (SFO VOR at 115.800 MHz) is in range (28.5 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
[LISTEN] mute mic, unmute speaker <br />
|And Yes: The SF VOR is just a little closer than the airport(center)<br />
|-<br />
|<br />7) Pressing Upper+Space once more brings back '''COM1''':<br />
|-<br />
|<br />
Radio-Select: COM1 <br />
Selected frequency: 118.600 <br />
Hanging up call 0 <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.6 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
[LISTEN] mute mic, unmute speaker <br />
|-<br />
|<br />8) Lets us start and continue flying in the direction about 130°:<br />
|-<br />
|<br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.4 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.2 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 0.7 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.3 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 1.9 km) <br />
Airport Palo Alto (KPAO Tower at 118.600 MHz) is in range ( 2.4 km) <br />
|notice that you first come closer (to the center of the airport) and after that getting away<br />
|- <br />
|<br />9) Let's switch to '''COM2''' (San Francisco) and watch: <br />
|-<br />
|<br />
Radio-Select: COM2 <br />
Selected frequency: 120.500 <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (37.8 km) <br />
Call 0 accepted <br />
Call 0 answered <br />
[LISTEN] mute mic, unmute speaker <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (38.6 km) <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (39.5 km) <br />
.. <br />
Airport San Francisco Intl (KSFO TWR at 120.500 MHz) is in range (49.7 km) <br />
Hanging up call 0 <br />
Radio-Select: NAV2 <br />
Selected frequency: 115.800 <br />
Call rejected by remote <br />
[LISTEN] mute mic, unmute speaker <br />
|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!<br />
|}<br />
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 />
<br />
=== Using FGCom ===<br />
There are basically three types of FGCom-usage:<br />
* '''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 100 km (about 54 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 />
* 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 />
* 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 />
<br />
=== Supplemantery Information ===<br />
==== Tips and Tricks ====<br />
===== Airport missing in FGCom: =====<br />
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 <br />
KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl<br />
You can add extra lines for any locations you want. e.g.: (watch the separation comas)<br />
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code)<br />
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz”<br />
or just take one of which you are sure that you do not need it in the FGFS-reality<br />
(notice that several Airports (far apart) use same frequencies!<br />
long/lat = take out of the Mpmap (or Google Map)<br />
type = whatever<br />
name = whatever<br />
''(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 =====<br />
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.<br />
* For windows you can use "WordPad"<br />
* For Linux the "gedit" works fine<br />
<br />
===== Copying-Printing this WIKI-Page''' =====<br />
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:<br />
<br />
* to copy:<br />
** select in the Browser-Menu: "File" --> "Save Page as.. "<br />
* to print:<br />
** go to the [http://wiki.flightgear.org/index.php?title=FGCOM&printable=yes printable version].<br />
** Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply"<br />
** before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages!<br />
** If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer<br />
<br />
<br />
===== Joystick compatibility between Operating Systems: =====<br />
{{Main article|Joystick}}<br />
<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"):<br />
<axis> (instead of the usual <axis n=”3”> )<br />
<desc>Mixture</desc> <br />
<number> <br />
<unix>3</unix> <br />
<mac>5</mac> <br />
<windows>5</windows> <br />
</number> <br />
<binding> <br />
<command>nasal</command> <br />
<script>controls.mixtureAxis()</script> <br />
</binding> <br />
</axis><br />
<br />
===== Assign PTT to joystick =====<br />
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)<br />
<button n="x"> <br />
<desc>PTT - Push To Talk</desc> <br />
<binding> <br />
<command>nasal</command> <br />
<script>controls.ptt(1)</script> <br />
</binding> <br />
<mod-up> <br />
<binding> <br />
<command>nasal</command> <br />
<script>controls.ptt(0)</script> <br />
</binding> <br />
</mod-up> <br />
</button><br />
<br />
==== Helpful internet adresses ====<br />
'''World-Time:''' <br />
* [http://www.timeanddate.com/worldclock/custom.html?sort=1 standard deviations]<br />
* [http://www.timezoneconverter.com/cgi-bin/tzc.tzc direct conversions]<br />
<br />
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 /><br />
*: Some programs need Decimal Lon/Lat values, others the Degrees/Minutes/Sec. Just convert it.<br /><br /><br />
* '''Miles, km, feet, etc. etc. ...''': http://www.convertunits.com/<br />
*: If like to avoid troubles (like NASA lost a satellite because of it) just look it up.<br />
<br />
'''Ports needed'''<br />
<br />
In case of problems over the internet you might check that the the following ports are allowed:<br />
1314 TCP if the Festival-Server is used for Text/Sound <br />
2005 UDP Vcp-Stream<br />
4569 UDP FGCom VoIP, (Inter-Asterisk eXchange)<br />
5000 UDP in/out Multiplayer (VPN Sftw.)<br />
5001 UDP Enable HTTP-server<br />
5002 UDP Enable property server<br />
5003 UDP Enable Screen-Shot services<br />
5004 UDP (may be used as a spare)<br />
5505 UDP Terra Sync<br />
16661 UDP FGCom listening to FGFS, usually “local host” only<br />
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).<br />
<br />
==== Commandline Parameters ====<br />
fgcom --help<br />
returns the following useful info<br />
fgcom - a communication radio based on VoIP with IAX/Asterisk<br />
(c)2007 by H. Wirtz <wirtz@dfn.de><br />
Version 1.2.2 build 163M<br />
Using iaxclient library Version SVN 163M<br />
<br />
OPTION DESCRIPTION<br />
<br />
-d, -debug, --debug= show debugging information<br />
-S, -voipserver, --voipserver= voip server to connect to (default: 'fgcom1.parasitstudio.de')<br />
-s, -fgserver, --fgserver= network device to connect to (default: 'localhost')<br />
-p, -port, --port= where we should listen to FG (default: '16661')<br />
-a, -airport, --airport= airport-id (ICAO) for ATC-mode<br />
-f, -frequency, --frequency= frequency for ATC-mode<br />
-U, -user, --user= username for VoIP account (default: 'guest')<br />
-P, -password, --password= password for VoIP account (default: 'guest')<br />
-i, -mic, --mic= mic input level (0.0 - 1.0)<br />
-o, -speaker, --speaker= speaker output level (0.0 - 1.0)<br />
-b, -mic-boost, --mic-boost= enable mic boost<br />
-l, -list-audio, --list-audio= list audio devices<br />
-r, -set-audio-in, --set-audio-in= use <devicename> as audio input<br />
-k, -set-audio-out, --set-audio-out= use <devicename> as audio output<br />
-c, -codec, --codec= use codec <codec> as transfer codec (default: 'u')<br />
<br />
Available codecs:<br />
u - ulaw (default and best codec because the mixing is based onto ulaw)<br />
a - alaw<br />
g - gsm<br />
s - speex<br />
7 - G.723<br />
<br />
Mode 1: client for COM1 of flightgear:<br />
$ fgcom<br />
- connects fgcom to fgfs at localhost:16661<br />
$ fgcom -sother.host.tld -p23456<br />
- connects fgcom to fgfs at other.host.tld:23456<br />
<br />
Mode 2: client for an ATC at <airport> on <frequency>:<br />
$ fgcom -aKSFO -f120.500<br />
- sets up fgcom for an ATC radio at KSFO 120.500 MHz<br />
<br />
Note that /home/hcs/src/fgcom/trunk/src/fgcom starts with a guest account unless you use -U and -P!<br />
<br />
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 ==<br />
{{Main article|Howto: Set up a FGCom server}}<br />
<br />
== External links ==<br />
* [http://sourceforge.net/projects/fgcom/ fgcom(SourceForge-Project)] Subversion is [http://fgcom.svn.sourceforge.net/ available here]. If you haven't used Subversion before, you might find it easier to fetch a [http://fgcom.svn.sourceforge.net/viewvc/fgcom/?view=tar archive] instead.<br />
* latest source available here (?): http://code.google.com/p/fgcomgui/<br />
<br />
=== Deprecated or broken links ===<br />
* [http://squonk.abacab.org/dokuwiki/fgcom Old Official website] <br />
* [http://squonk.abacab.org/dokuwiki/fgcom-manual Manual]<br />
<br />
== Status ==<br />
* '''March, 2009:'''<br />
Adding User-Information for installing, using, maintaining FGCOM on different platforms.<br />
<br />
* '''18 November, 2008:'''<br />
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)<br />
* '''31 October, 2008:''' <br />
<br />
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:<br />
''#include STL_STRING''<br />
<br />
I guess that such constant must point to the STL library include file but I am not sure.<br />
I revert to the '''r148''' SVN version which successfully compiles.<br />
<br />
Command to get such version is: ''svn co -r148 svn://svn.dfn.de:/fgcom/trunk fgcom-r148''<br />
<br />
* '''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.<br />
<br />
* '''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 />
== Related content ==<br />
* [[FlightGear related projects]]<br />
* [[FGComGui]]<br />
<br />
[[Category:Software]]<br />
[[fr:FGCom]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_June_2012&diff=51178FlightGear Newsletter June 20122012-06-25T15:15:24Z<p>Alfo: /* New software tools and projects */ MPRecorder</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== Development news ==<br />
=== 2.8.0 release preparations ===<br />
{{Main article|Release plan}}<br />
Since the feature freeze on June 17, no new features may be pushed to our [[Git]] repositories. Aircraft outside the base package can still receive updates till July 17, when release branches will be created from the repositories. That is basically the birth of a new release. From then on only bug fixes will be accepted. <br />
<br />
Thanks to the branching, development for the next-next release (3.0.0?) can start right away; even before 2.8.0 is released. <br />
<br />
=== Rembrandt controls ===<br />
[[File:Rembrandt dialog.png|thumb|left]]<br />
A special [[Project Rembrandt|Rembrandt]] dialog has been created, to give the user full control over Rembrandt's rich feature set. The dialog can be reached via <tt>View > Rendering Options</tt>. By adjusting the various options, the framerate impact can be decreased.<br />
<br />
=== Taxiway signs support improved ===<br />
Flightgear does now better support the taxiway signs syntax of the apt.dat 850 spec.<br />
Christian implemented the new specs and got rid of some old cruft along the way. The signs are also rendered now with a 3D case around and we support double sided signs as well!<br />
[[File:3d sign front.png|320px|left|Taxiway sign, front side]]<br />
[[File:3d sign back.png|320px|right|Taxiway sign, back side]]<br />
Emilian updated the signs textures to have some shading on top, which improves the overall appearance a lot. Also, Now it is possible to make use of new special types, such as {critical}, {safety}, {no-entry} and {hazard}. See the [[Signs|Signs entry]] for more details.<br />
[[File:3d sign special.png|320px|left|special sign variants]]<br />
<br />
James was able to improve the rendering code considerably. The signs are now rendered per stg file into one geometry. This reduces the amount of geodes a lot.<br />
<br />
=== Mailing list digest ===<br />
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Interview with a contributor (NAME) ==<br />
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice monthly). These snapshots depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].<br />
<br />
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
=== MP Map desktop application ===<br />
<br />
Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google).<br />
<br />
http://almien.co.uk/flightgear/map/multiplayer/<br />
<br />
[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]<br />
<br />
OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos. <br />
<br />
Features available in this map include:<br />
* Historical tracks ("breadcrumbs") showing movement of aircraft over time <br />
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible<br />
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.<br />
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.<br />
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them<br />
<br />
<br />
<br />
=== [[MPRecorder]] ===<br />
<br />
[[MPRecorder]] is a new developed tool to record and replay multiplayer activities. By using normal aircrafts while replaying a flight, you can easily create other views and record better videos.<br />
<br />
In the following video you can see a lot of non standard views, recorded with the help of MPRecorder.<br />
{{#ev:youtube|FCgBhIgjOmo|400|Flightgear MPRecorder example video at St. Barths}}<br />
<br />
== FlightGear add-ons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
All the way back in May 2011, we adopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
==== Glaser-Dirks DG-101G ====<br />
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== Airports ===<br />
====London Gatwick in 850====<br />
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.<br />
<br />
[[File:Gatwick-850-version.png|640px]]<br />
<br />
Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].<br />
<br />
====Berlin-Tempelhof (EDDI/THF)====<br />
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.<br />
<br />
The Berlin Tempelhof airport was opened officially on 8 October 1923, but there was aviation activity in this area before. In 1909 the Wright brothers showed their flyer there. During the 1920's it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during the Second World War. Work on the modern building was started in 1936, but was not finished until the end of the war, when it became a U.S. military base. It became famous during the Berlin airlift of 1948-49. In the 1950's it was opened to civilian flights, and in 1993 it ceased to be a military base. The airport was closed on 30 October 2008.<br />
<br />
Tempelhof airbase was not only an airport, but also a small independent town in the city of Berlin. It had its own power plant, waterworks, garbage incinerator, a railway siding, sporting facilities, barbecue area, and plant nursery. The aim is to have the airport area and the adjacent surroundings as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities have been modelled and send to the repository. The main building is in work. It's modeled partly based on original construction drawings and it is textured with photos of the real thing.<br />
<br />
If you ever had the opportunity to arrive there by plane, you may remember the impressive experience of rolling with your plane under this mighty roof construction and walking away freely on the apron, even as a normal passenger. This gives a good impression of what aviation was like in former days.<br />
<br />
Since you can't have this experience any longer in real life, maybe we will have it in FlightGear someday. But be patient: since it claims to be among the twenty largest buildings of the world, it will take some time to finish it.<br />
<br />
Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].<br />
<br />
[[File:EDDI3.jpg|640px]]<br />
[[File:EDDI1.jpg|640px]]<br />
[[File:EDDI2.jpg|640px]]<br />
<br />
<br />
<br />
===Düsseldorf International (EDDL)===<br />
[[Düsseldorf International Airport]] is Germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.<br />
<br />
[[File:EDDL-generic1.jpg|640px]]<br />
[[File:EDDL-night.jpg|640px]]<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
<br />
== Hardware reviews==<br />
Stuart has reviewed the Saitek Pro Flight Cessna controls for FlightGear. These are officially licensed controls intended to mimic Cessna singles like the 172 as closely as possible. See what he thought in his [[Hardware Review: Saitek Pro Flight Cessna controls|review]]. <br />
<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.<br />
<br />
In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:<br />
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:<br />
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by clicking the Edit button at the top of the page.<br />
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
Lukea visited London Gatwick (EGKK) with the new 850 apt.dat installed<br />
{{#ev:youtube|uPOq1p5BD30|400|This is an embedded video!}}<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt><br />
<br />
Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.<br />
<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
==== FlightGear at the National Museum of Flight, Scotland ====<br />
[[File:FlightGear demo at museum.jpg|thumb|FlightGear at the Museum of Flight, Scotland]]<br />
Stuart Buchanan (stuart on the forum), ran a booth showing off FlightGear at the "Robots Live" event at the National Museum of Flight at East Fortune, Scotland, on Sunday 17th May. About 100 people tried landing an F-35C on a carrier, lots of flyers were handed out, and many compliments were received on the quality of the simulator. Demoing FG at an event at your local aviation museum is a great way to spread the word about FG. See our [[FlightGear Expo Checklist]] for guidance on how you can go about it. <br />
<br />
==== FSweekend 2012 ====<br />
With still several months to go, the FlightGear FSweekend team got the confirmation that [[FSweekend 2012]], the world's largest flight simulation event, will take place on '''3 and 4 November 2012''', at the usual location: Aviodrome museum ([[Lelystad Airport]], the Netherlands). <br />
<br />
[[File:FSweekend banner 2012.jpg|left|270px]]<br />
Until recently it was unsure whether the event would take place this year, because the museum announced its bankruptcy the Monday after last year's weekend. Aviodrome closed its doors by the end of 2011. Luckily a company was found that took over the museum and its collection; leading to the reopening earlier this year. The reopened museum is more attractive for children, as well as the average person (not just the true aviation enthusiastic). <br />
<br />
The museum entrance fee gives you access to both the FSweekend and the museum. So when you've seen enough virtual stuff, there are plenty of real aircraft to discover. The FlightGear team would appreciate it if you are able to travel to Lelystad!<br />
<br />
Facebook users can join [http://www.facebook.com/events/315742308452348 the event's page] to stay up to date and connect to other visitors.<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
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. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=MPRecorder&diff=51177MPRecorder2012-06-25T15:05:57Z<p>Alfo: Created page with "{{Infobox Software | title = MPRecorder | logo = | image = | alt = | developedby = Markus ..."</p>
<hr />
<div>{{Infobox Software<br />
| title = MPRecorder<br />
| logo = <br />
| image = <br />
| alt = <br />
| developedby = Markus Pargmann<br />
| initialrelease = 0.1<br />
| latestrelease = 0.1<br />
| writtenin = Python 3<br />
| os = All with python3 support (only tested on linux)<br />
| platform = <br />
| developmentstatus = Active<br />
| type = <br />
| license = [[GNU General Public License]]<br />
| website = http://fgfs.allfex.org/mprecorder/<br />
}}<br />
MPRecorder is a tool to record and replay multiplayer activities, including chat and all aircraft properties that are transferred in multiplayer. In difference to the integrated flightgear replay support, you can record and replay multiple aircrafts. Also the standard recording quality is most times much higher (10 updates per second). You can use any view you want for video recording, because all replays are in multiplayer, so you can use normal aircrafts while replaying a flight.<br />
<br />
== MPRecorder example video ==<br />
This is an example video of a landing in St. Barths using MPRecorder to record other views. I am usually not making videos so this is far away from being perfect, but I think you can get an impression.<br />
<br />
{{#ev:youtube|FCgBhIgjOmo|600|Flightgear MPRecorder example video at St. Barths}}<br />
<br />
== Features ==<br />
<br />
* Record/Replay multiple flights at the same time<br />
* Record multiplayer activity within 100nm<br />
* Each pilot recording stored in <USER_HOME>/.fgfsrec<br />
* Replays in multiplayer (You can use UFO to record or watch the flight)<br />
* Replay multiple recordings at the same time<br />
* low/high quality replays<br />
<br />
== Record ==<br />
<br />
Simple command to record at an airport:<br />
./recorder.py -c rec record --lat 18.040707 --lon -63.110125<br />
<br />
== Replay ==<br />
<br />
Simple command to replay a single recorded flight:<br />
./recorder.py -c alfo replay ~/.fgfsrec/2012_06_24_10_05_alfo<br />
<br />
Replay starting at second 42:<br />
./recorder.py -c alfo replay --at 42 ~/.fgfsrec/2012_06_24_10_05_alfo<br />
<br />
Replay a complete multiplayer event (All recordings in one directory) while preserving the start times of each recorded flight:<br />
./recorder.py -c alfo replay ~/.fgfsrec/<br />
<br />
Replay of multiple recordings starting at the same time:<br />
./recorder.py -c alfo replay ~/.fgfsrec/2012_06_24_10_05_alfo ~/.fgfsrec/2012_06_24_10_00_alfo<br />
<br />
Replay of multiple recordings, the second replay starts after 10 seconds:<br />
./recorder.py -c alfo replay ~/.fgfsrec/2012_06_24_10_05_alfo ~/.fgfsrec/2012_06_24_10_00_alfo:10<br />
<br />
== Help ==<br />
<br />
% ./recorder.py --help<br />
usage: recorder.py [-h] [-s SERVER] -c CALLSIGN {record,replay} ...<br />
<br />
positional arguments:<br />
{record,replay} To record flights<br />
record Record the activities at a given position<br />
replay Replay one or more files in multiplayer<br />
<br />
optional arguments:<br />
-h, --help show this help message and exit<br />
-s SERVER, --server SERVER<br />
SERVER the recorder should use<br />
-c CALLSIGN, --callsign CALLSIGN<br />
Callsign for the recorder. In replay mode this is used<br />
as prefix for the id of the replay<br />
<br />
% ./recorder.py record --help<br />
usage: recorder.py record [-h] --lon LON --lat LAT<br />
<br />
optional arguments:<br />
-h, --help show this help message and exit<br />
--lon LON<br />
--lat LAT<br />
<br />
% ./recorder.py replay --help<br />
usage: recorder.py replay [-h] [-a STARTTIME] [-d]<br />
PATH[:STARTTIME] [PATH[:STARTTIME] ...]<br />
<br />
positional arguments:<br />
PATH[:STARTTIME] Path to a file or directory with replays combined with<br />
an optional relative start time in seconds for all<br />
recordings found at that path.<br />
<br />
optional arguments:<br />
-h, --help show this help message and exit<br />
-a STARTTIME, --at STARTTIME<br />
Start the replay at second x<br />
-d, --hq High quality replay. This can lead to lagging when<br />
replaying big multiplayer events.<br />
<br />
[[Category:Software]]<br />
[[Category:GPL software]]<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=D%C3%BCsseldorf_International_Airport&diff=51021Düsseldorf International Airport2012-06-16T11:38:13Z<p>Alfo: /* Flightgear scenery */ Update download urll</p>
<hr />
<div>{{infobox Airport<br />
|name = Düsseldorf International Airport<br />
|image =EDDL-generic1.jpg<br />
|alt =147ft<br />
|iata =DUS<br />
|icao =EDDL<br />
|type =Public<br />
|city =Düsseldorf, Germany<br />
|owner =Flughafen Düsseldorf GmbH<br />
|website =http://www.duesseldorf-airport.com/<br />
|runway= 05R/23L<br />
|length= 3000 m<br />
|material= Concrete<br />
|runway2= 05L/23R<br />
|length2= 2700 m <br />
|material2= Concrete<br />
}}<br />
[[File:EDDL-generic2.jpg|thumb|270px]]<br />
<br />
== Description ==<br />
Düsseldorf International is the third largest airport in germany. It has two runways of 2700m and 3000m length. The usage of the second runway (05L/23R) is limited by a contract with the land NRW. The main active runway direction is 23.<br />
<br />
The airport has three terminals, A, B and C. The two major airlines at this airport are AirBerlin (mainly terminal B) and Lufthansa (terminal A). Terminal C is used for flights to and from states which are not in the schengen agreement or airlines that are not related to Lufthansa or AirBerlin.<br />
<br />
The biggest aircrafts you can see at this airport are A340 and 777. There are no regular flights of 747s or A380s, although both are allowed to land at EDDL.<br />
<br />
For further information see http://en.wikipedia.org/wiki/D%C3%BCsseldorf_International_Airport<br />
<br />
== Flightgear scenery ==<br />
<br />
* Detailed apt850 airport layout<br />
:* Taxiways<br />
:* Taxilights<br />
:* Detailed ground layout of apron and taxiways<br />
:* Lots of signs (taxiway and parking positions)<br />
:* Airport roads<br />
* Generic Buildings (hangars, jetways etc.)<br />
* Airport tower and untextured terminal<br />
* Corine + openstreetmap scenery<br />
* Authors<br />
:* Markus Pargmann<br />
:* TeXnicer (first scenery version from 2009 with airport tower and terminal)<br />
:* Thanks to D-EKEW for corine scenery generation<br />
* '''Download'''<br />
:* EDDL only: http://fgfs.allfex.org/eddl/0.2/eddl.zip<br />
:* luxembourg scenery repository: https://gitorious.org/flightgear-custom-scenery/luxembourg<br />
<br />
<br />
[[Category:Airports in Germany]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_June_2012&diff=51020FlightGear Newsletter June 20122012-06-16T11:36:35Z<p>Alfo: /* Düsseldorf International (EDDL) */ Corine update</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== Development news ==<br />
<br />
<br />
<br />
=== Mailing list digest ===<br />
<br />
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Interview with a contributor (NAME) ==<br />
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].<br />
<br />
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google)<br />
<br />
http://almien.co.uk/flightgear/map/multiplayer/<br />
<br />
[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]<br />
<br />
OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos. <br />
<br />
Features available in this map include:<br />
* Historical tracks ("breadcrumbs") showing movement of aircraft over time <br />
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible<br />
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.<br />
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.<br />
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
==== Glaser-Dirks DG-101G ====<br />
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== Airports ===<br />
====London Gatwick in 850====<br />
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.<br />
<br />
[[File:Gatwick-850-version.png|640px]]<br />
<br />
Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].<br />
<br />
====Berlin-Tempelhof (EDDI/THF)====<br />
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.<br />
<br />
The Berlin Tempelhof airport was opened officially on 8 October 1923. But there was aviation activity on this area before. 1909 the Wright brothers show there flyer there for example. During the 1920ties it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during WW II. The today building was started in 1936, but was never finished until the end of the war. After the second world war it first became a base of the U.S. military until 1993. In the 1950ties it was also opened for civilian flights. It became famous during the Berlin airlift 1948-49. The airport was closed on 30 October 2008.<br />
<br />
Tempelhof airbase was an airport of course, but also a small independent town in the city of Berlin. They had a an own power plant, waterworks, garbage incineration, a railway side track, sporting facilities, bbq-area and a plant nursery. The aim is to have the airport areal and the near surrounding as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities are modeled and send to the repository. The main building is in work. It's model partly based on original construction drawings and it is textured with photos of the real thing.<br />
<br />
If you ever have had the opportunity to arrive there by plane you may have get the impressive experience to roll with your plane under this mighty roof construction and walk away freely on the apron, even as a normal passenger. This gives a good impression how aviation has been in the former days.<br />
<br />
Since you can't have this experience any more in real live, may be we will have it in FlightGear some day. But be patient: Since it's told to be under the twenties't largest buildings of the world, it will take some time to finish it.<br />
<br />
Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].<br />
<br />
[[File:EDDI3.jpg|640px]]<br />
[[File:EDDI1.jpg|640px]]<br />
[[File:EDDI2.jpg|640px]]<br />
<br />
<br />
<br />
===Düsseldorf International (EDDL)===<br />
[[Düsseldorf International Airport]] is germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings. The scenery was generated with corine and openstreetmap.<br />
<br />
[[File:EDDL-generic1.jpg|640px]]<br />
[[File:EDDL-night.jpg|640px]]<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.<br />
<br />
In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:<br />
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:<br />
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by cliking the Edit button at the top of the page.<br />
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt><br />
<br />
Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.<br />
<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
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. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:EDDL-night.jpg&diff=51019File:EDDL-night.jpg2012-06-16T11:34:42Z<p>Alfo: </p>
<hr />
<div></div>Alfohttps://wiki.flightgear.org/w/index.php?title=D%C3%BCsseldorf_International_Airport&diff=51018Düsseldorf International Airport2012-06-16T11:31:07Z<p>Alfo: EDDL corine update</p>
<hr />
<div>{{infobox Airport<br />
|name = Düsseldorf International Airport<br />
|image =EDDL-generic1.jpg<br />
|alt =147ft<br />
|iata =DUS<br />
|icao =EDDL<br />
|type =Public<br />
|city =Düsseldorf, Germany<br />
|owner =Flughafen Düsseldorf GmbH<br />
|website =http://www.duesseldorf-airport.com/<br />
|runway= 05R/23L<br />
|length= 3000 m<br />
|material= Concrete<br />
|runway2= 05L/23R<br />
|length2= 2700 m <br />
|material2= Concrete<br />
}}<br />
[[File:EDDL-generic2.jpg|thumb|270px]]<br />
<br />
== Description ==<br />
Düsseldorf International is the third largest airport in germany. It has two runways of 2700m and 3000m length. The usage of the second runway (05L/23R) is limited by a contract with the land NRW. The main active runway direction is 23.<br />
<br />
The airport has three terminals, A, B and C. The two major airlines at this airport are AirBerlin (mainly terminal B) and Lufthansa (terminal A). Terminal C is used for flights to and from states which are not in the schengen agreement or airlines that are not related to Lufthansa or AirBerlin.<br />
<br />
The biggest aircrafts you can see at this airport are A340 and 777. There are no regular flights of 747s or A380s, although both are allowed to land at EDDL.<br />
<br />
For further information see http://en.wikipedia.org/wiki/D%C3%BCsseldorf_International_Airport<br />
<br />
== Flightgear scenery ==<br />
<br />
* Detailed apt850 airport layout<br />
:* Taxiways<br />
:* Taxilights<br />
:* Detailed ground layout of apron and taxiways<br />
:* Lots of signs (taxiway and parking positions)<br />
:* Airport roads<br />
* Generic Buildings (hangars, jetways etc.)<br />
* Airport tower and untextured terminal<br />
* Corine + openstreetmap scenery<br />
* Authors<br />
:* Markus Pargmann<br />
:* TeXnicer (first scenery version from 2009 with airport tower and terminal)<br />
:* Thanks to D-EKEW for corine scenery generation<br />
* '''Download'''<br />
:* EDDL only: http://fgfs.allfex.org/eddl/0.1/eddl.zip<br />
:* luxembourg scenery repository: https://gitorious.org/flightgear-custom-scenery/luxembourg<br />
<br />
<br />
[[Category:Airports in Germany]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:EDDL-generic2.jpg&diff=51017File:EDDL-generic2.jpg2012-06-16T11:27:53Z<p>Alfo: uploaded a new version of &quot;File:EDDL-generic2.jpg&quot;: corine + update</p>
<hr />
<div>2009/03/14</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:EDDL-generic1.jpg&diff=51016File:EDDL-generic1.jpg2012-06-16T11:17:53Z<p>Alfo: uploaded a new version of &quot;File:EDDL-generic1.jpg&quot;: latest EDDL version, corine</p>
<hr />
<div>{{File information<br />
|date= 2009-03-14<br />
}}<br />
<br />
[[Category:FlightGear exterior screenshots]]<br />
[[Category:FlightGear scenery screenshots]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=FlightGear_Newsletter_June_2012&diff=50960FlightGear Newsletter June 20122012-06-11T20:37:06Z<p>Alfo: /* Scenery corner */ EDDL</p>
<hr />
<div><br />
{{newsletter}}<br />
{{TOC_right|limit=2}}<br />
<br />
''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 news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''<br />
<br />
== Development news ==<br />
<br />
<br />
<br />
=== Mailing list digest ===<br />
<br />
(by far the easiest option to populate the newsletter with contents is copying/pasting stuff from the forum and the mailing list or the git logs)<br />
<br />
=== Forum digest ===<br />
<br />
=== Git digest ===<br />
<br />
=== Getting involved as a programmer ===<br />
<br />
Please see [[Howto:Start core development]]<br />
<br />
== Interview with a contributor (NAME) ==<br />
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''<br />
<br />
* How long have you been involved in FlightGear?<br />
* What are your major interests in FlightGear?<br />
* What project are you working on right now?<br />
* What do you plan on doing in the future?<br />
* Are you happy with the way the FlightGear project is going?<br />
* What do you enjoy most about developing for FlightGear?<br />
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?<br />
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?<br />
<br />
More questions are being collected here: [[Interview questions]].<br />
<br />
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX <br />
<br />
== Snapshot releases ==<br />
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshos depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].<br />
<br />
The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].<br />
<br />
== Nasal for newbies ==<br />
<br />
== New software tools and projects ==<br />
<br />
Development has started on a multiplayer map (similar to [[MPMap]] but as a desktop application rather than a web page, and using [[OpenStreetMap]] instead of Google)<br />
<br />
http://almien.co.uk/flightgear/map/multiplayer/<br />
<br />
[[File:Screenshot-FlightGear multiplayer map-1.png|400px|KSFO during a quiet period]]<br />
<br />
OpenStreetMap data tends to be quite good for airports, since OSM have the option of using Bing aerial imagery and runway/taxiway/stand numbers tend to be readily visible from aerial photos. <br />
<br />
Features available in this map include:<br />
* Historical tracks ("breadcrumbs") showing movement of aircraft over time <br />
* Label decluttering, meaning that in a crowded area each aircraft's label will be visible, and each aircraft symbol will be visible<br />
* Colour schemes: stationary aircraft are grey, and you can give each aircraft symbol its own random colour to distinguish them in a crowded space. When you select an aircraft its label and trail will become bright red.<br />
* Selected aircraft: click on an aircraft (or vehicle)'s label, and some details will appear on right of screen - track, groundspeed, etc.<br />
* Measure distances between any two vehicles - select one and then the other and tick "measure" to see continuously-updated bearing and distance between them<br />
<br />
== FlightGear addons and mods ==<br />
<br />
== In the hangar ==<br />
<br />
All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.<br />
<br />
=== New aircraft ===<br />
<br />
=== Updated aircraft ===<br />
==== Glaser-Dirks DG-101G ====<br />
The winching and aerotowing rope that was discussed in the [[FlightGear Newsletter February 2012#Glider winch launching ropes|February newsletter]] is now available for the [[Glaser-Dirks DG-101G]] from Git.<br />
<br />
=== Liveries ===<br />
<br />
== Scenery corner ==<br />
=== Airports ===<br />
====London Gatwick in 850====<br />
Islandmonkey has been working to make the already-great airport of [[London Gatwick Airport|London Gatwick (EGKK)]] 850 apt.dat layout.<br />
<br />
[[File:Gatwick-850-version.png|640px]]<br />
<br />
Download link is [https://dl.dropbox.com/s/y640k6sk5307l6p/Gatwick850.zip?dl=1 here].<br />
<br />
====Berlin-Tempelhof (EDDI/THF)====<br />
User Frank (aka fmg) is currently working on [[Berlin Tempelhof Airport]] (EDDI/THF) scenery ([[FlightGear Newsletter January 2012#Airport of the month|airport of the month January]]), what is declared to be the "Mother of all airports" by the British architect Sir Norman Foster.<br />
<br />
The Berlin Tempelhof airport was opened officially on 8 October 1923. But there was aviation activity on this area before. 1909 the Wright brothers show there flyer there for example. During the 1920ties it was the one of the busiest airports in Europe. The old terminal was originally constructed in 1927 and was destroyed during WW II. The today building was started in 1936, but was never finished until the end of the war. After the second world war it first became a base of the U.S. military until 1993. In the 1950ties it was also opened for civilian flights. It became famous during the Berlin airlift 1948-49. The airport was closed on 30 October 2008.<br />
<br />
Tempelhof airbase was an airport of course, but also a small independent town in the city of Berlin. They had a an own power plant, waterworks, garbage incineration, a railway side track, sporting facilities, bbq-area and a plant nursery. The aim is to have the airport areal and the near surrounding as complete as possible to bring a bit of the special atmosphere of this place to FlightGear. Most of the technical facilities are modeled and send to the repository. The main building is in work. It's model partly based on original construction drawings and it is textured with photos of the real thing.<br />
<br />
If you ever have had the opportunity to arrive there by plane you may have get the impressive experience to roll with your plane under this mighty roof construction and walk away freely on the apron, even as a normal passenger. This gives a good impression how aviation has been in the former days.<br />
<br />
Since you can't have this experience any more in real live, may be we will have it in FlightGear some day. But be patient: Since it's told to be under the twenties't largest buildings of the world, it will take some time to finish it.<br />
<br />
Some impressions of the project and the progress can be seen in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=15378 the forum topic] and in [http://www.youtube.com/watch?v=u9Ctdn-xPcI this YouTube video].<br />
<br />
[[File:EDDI3.jpg|640px]]<br />
[[File:EDDI1.jpg|640px]]<br />
[[File:EDDI2.jpg|640px]]<br />
<br />
<br />
<br />
===Düsseldorf International (EDDL)===<br />
[[Düsseldorf International Airport]] is germany's third largest airport. It was updated to a highly detailed ap850 ground layout with signs and generic buildings.<br />
<br />
[[File:EDDL-generic1.png|640px]]<br />
[[File:EDDL-generic2.png|640px]]<br />
<br />
== Aircraft of the month ==<br />
== Airport of the month ==<br />
== Screenshot of the month ==<br />
<br />
== Suggested flights ==<br />
== Aircraft reviews ==<br />
<br />
== Wiki updates ==<br />
As part of a big cleanup, 2,000 inactive accounts have been deleted. Those accounts were never used for anything. Most of them had rather dubious names, normally created by spambots. The total number of users is now {{NUMBEROFUSERS}}.<br />
<br />
In order to keep the wiki database clean and small, it's important that all editors try to apply the following tips as much as possible:<br />
* Limit the number of edits. One edit containing a big edit is better than several smaller edits (to one article). Every time someone saves an edit, the entire article is saved in history and thus the database. The following tips can help you minimise your edit count:<br />
** Do not edit an article on a per-section base (by clicking the <nowiki>[edit]</nowiki> link next to a header). If you would like to make edits in multiple sections of the same article, simply edit the entire article by cliking the Edit button at the top of the page.<br />
** Preview your edit(s) before saving, by clicking the preview button. Especially check for red links to non existing articles (usually the result of typos).<br />
<br />
===New articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
</DynamicArticleList><br />
===New aircraft articles===<br />
<DynamicArticleList><br />
type=new<br />
count=10<br />
categoryRoot=Aircraft<br />
</DynamicArticleList><br />
===Most popular newsletters===<br />
<DynamicArticleList><br />
type=hot<br />
count=5<br />
categoryRoot=FlightGear Newsletter<br />
</DynamicArticleList><br />
<br />
== Community news ==<br />
=== FlightGear on YouTube ===<br />
<br />
=== New tutorials and screencasts ===<br />
=== Forum news ===<br />
=== Multiplayer ===<br />
Thanks to Yves for setting up a multiplayer server in Switzerland, the total number of available servers is now 14! The host adress of the new server is: <tt>mpserver14.flightgear.org</tt><br />
<br />
Please refer to [[Howto:Set up a multiplayer server]] if you are interested in setting up a server yourself.<br />
<br />
=== Virtual airlines ===<br />
=== FlightGear events ===<br />
<br />
== Useful links ==<br />
== And finally ... ==<br />
=== Contributing ===<br />
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. <br />
<br />
For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].<br />
<br />
=== Call for volunteers ===<br />
* The [[OpenRadar]] project is looking for a new maintainer.<br />
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.<br />
<br />
=== Did you know ===<br />
<br />
[[Category:FlightGear Newsletter]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=D%C3%BCsseldorf_International_Airport&diff=50958Düsseldorf International Airport2012-06-11T19:59:08Z<p>Alfo: scenery update and some content</p>
<hr />
<div>{{infobox Airport<br />
|name = Düsseldorf International Airport<br />
|image =EDDL-generic1.png<br />
|alt =147ft<br />
|iata =DUS<br />
|icao =EDDL<br />
|type =Public<br />
|city =Düsseldorf, Germany<br />
|owner =Flughafen Düsseldorf GmbH<br />
|website =http://www.duesseldorf-airport.com/<br />
|runway= 05R/23L<br />
|length= 3000 m<br />
|material= Concrete<br />
|runway2= 05L/23R<br />
|length2= 2700 m <br />
|material2= Concrete<br />
}}<br />
[[File:EDDL-generic2.png|thumb|270px]]<br />
<br />
== Description ==<br />
Düsseldorf International is the third largest airport in germany. It has two runways of 2700m and 3000m length. The usage of the second runway (05L/23R) is limited by a contract with the land NRW. The main active runway direction is 23.<br />
<br />
The airport has three terminals, A, B and C. The two major airlines at this airport are AirBerlin (mainly terminal B) and Lufthansa (terminal A). Terminal C is used for flights to and from states which are not in the schengen agreement or airlines that are not related to Lufthansa or AirBerlin.<br />
<br />
The biggest aircrafts you can see at this airport are A340 and 777. There are no regular flights of 747s or A380s, although both are allowed to land at EDDL.<br />
<br />
For further information see http://en.wikipedia.org/wiki/D%C3%BCsseldorf_International_Airport<br />
<br />
== Flightgear scenery ==<br />
<br />
* Detailed apt850 airport layout<br />
:* Taxiways<br />
:* Taxilights<br />
:* Detailed ground layout of apron and taxiways<br />
:* Lots of signs (taxiway and parking positions)<br />
:* Airport roads<br />
* Generic Buildings (hangars, jetways etc.)<br />
* Airport tower and untextured terminal<br />
* Authors<br />
:* Markus Pargmann<br />
:* TeXnicer (first scenery version from 2009 with airport tower and terminal)<br />
* '''Download''' http://fgfs.allfex.org/eddl/0.1/eddl.zip<br />
<br />
<br />
[[Category:Airports in Germany]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=D%C3%BCsseldorf_International_Airport&diff=50957Düsseldorf International Airport2012-06-11T19:34:41Z<p>Alfo: save test</p>
<hr />
<div>{{infobox Airport<br />
|name = Düsseldorf International Airport<br />
|image =EDDL-generic1.png<br />
|alt =<br />
|iata =DUS<br />
|icao =EDDL<br />
|type =Public<br />
|city =Düsseldorf, Germany<br />
|owner =Flughafen Düsseldorf GmbH<br />
|website =http://www.duesseldorf-airport.com/<br />
|runway= 05R/23L<br />
|length= 3000 m<br />
|material= Concrete<br />
|runway2= 05L/23R<br />
|length2= 2700 m <br />
|material2= Concrete<br />
}}<br />
[[File:EDDL-generic2.png|thumb|270px]]<br />
<br />
[[Category:Airports in Germany]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:EDDL-generic2.png&diff=50951File:EDDL-generic2.png2012-06-11T10:32:30Z<p>Alfo: Second view on updated EDDL</p>
<hr />
<div>Second view on updated EDDL</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:EDDL-generic1.png&diff=50950File:EDDL-generic1.png2012-06-11T10:30:48Z<p>Alfo: Updated EDDL scenery</p>
<hr />
<div>Updated EDDL scenery</div>Alfohttps://wiki.flightgear.org/w/index.php?title=Multiplayer_protocol&diff=50496Multiplayer protocol2012-05-26T11:00:03Z<p>Alfo: time and lag are doubles!</p>
<hr />
<div>== The messages ==<br />
<br />
All messages are composed of XDR encoded data. (see [http://www.faqs.org/rfcs/rfc1832.html RFC 1832] for a complete description of XDR). XDR basically means: All data is in network byte order and aligned to the nearest multiple of 4 bytes. Strings are encoded as a zero-terminated array of characters,aligned to the nearest multiple of 4 bytes. Floating point numbers (32 or 64 bit) must be encode in the IEEE standard.<br />
<br />
== The header ==<br />
The header is always 32 bytes long and contains the following fields in exactly that order:<br />
<br />
|'''Magic'''|'''Version'''|'''MsgId'''|'''MsgLen'''|'''ReplyAddress'''|'''ReplyPort'''|'''Callsign'''|'''Data'''|<br />
<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
|Magic:<br />
|4 bytes, always 0x46474653 ("FGFS")<br />
|-<br />
|Version:<br />
|4 bytes, protocol version, currently 0x00010001 (1.1)<br />
|-<br />
|MsgId:<br />
|4 bytes, defines what data is appended to the header. Can be 0x00000001 for chat messages (deprecated) or<br /><br />
0x00000007 for position data<br />all other values are outdated and ignored<br />
|-<br />
|MsgLen:<br />
|4 bytes, the length of the data. '''Important:''' This is not in bytes, see the description of STRING field at the end for more information.<br />
|-<br />
|ReplyAddress:<br />
|4 bytes, deprecated and ignored<br />
|-<br />
|ReplyPort:<br />
|4 bytes, deprecated and ignored<br />
|-<br />
|Callsign:<br />
|8 bytes, zero terminated array of characters representing<br />
the user callsign<br />
|}<br />
<br />
== Data of chat messages ==<br />
The data for chat messages is a zero terminated array of characters. The MsgLen field in the header represents its length. The maximum length is defined to be 256 bytes.<br />
<br />
== Data of position messages ==<br />
The data of position data is more complicated and looks like this:<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
|ModelName<br />
|96 bytes, zero terminated array of characters representing the aircraft model used by the user<br />
|-<br />
|time<br />
|8 bytes, representing the time when this message was generated double<br />
|-<br />
|lag || 8 bytes, time offset for network lag double<br />
|-<br />
|PosX || 8 bytes, XDR encoded double value, X-ccordinate of users<br /><br />
position wrt the earth centered frame<br />
|-<br />
|PosY || 8 bytes, XDR encoded double value, Y-ccordinate of users<br /><br />
position wrt the earth centered frame<br />
|-<br />
|PosZ || 8 bytes, XDR encoded double value, z-ccordinate of users<br />
position wrt the earth centered frame<br />
|-<br />
|OriX || 4 bytes, XDR encoded float value, X-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|OriY || 4 bytes, XDR encoded float value, Y-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|OriZ || 4 bytes, XDR encoded float value, Z-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|VelX || 4 bytes, XDR encoded float value, velocity of the user in X direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|VelY || 4 bytes, XDR encoded float value, velocity of the user in Y direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|VelZ || 4 bytes, XDR encoded float value, velocity of the user in Z direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|pad || up to 8 bytes for padding the data to a multiple of 8 bytes<br />
|}<br />
<br />
This data is followed by '''property-values''', which are encoded in the form '''ID'''|'''Value'''<br />
<br />
The following properties are transmitted, but not necessarily all present and not in this order:<br />
<br />
'''Important:''' This table is outdated. Please have a look in the flightgear sources at src/MultiPlayer/multiplaymgr.cxx<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
!ID !! Property || Type(*)<br />
|-<br />
|100 || "surface-positions/left-aileron-pos-norm" || FLOAT<br />
|-<br />
|101 || "surface-positions/right-aileron-pos-norm" || FLOAT<br />
|-<br />
|102 || "surface-positions/elevator-pos-norm" || FLOAT<br />
|-<br />
|103 || "surface-positions/rudder-pos-norm" || FLOAT<br />
|-<br />
|104 || "surface-positions/flap-pos-norm" || FLOAT<br />
|-<br />
|105 || "surface-positions/speedbrake-pos-norm" || FLOAT<br />
|-<br />
|106 || "gear/tailhook/position-norm" || FLOAT<br />
|-<br />
|107 || "gear/launchbar/position-norm" || FLOAT<br />
|-<br />
|108 || "gear/launchbar/state" || STRING<br />
|-<br />
|109 || "gear/launchbar/holdback-position-norm" || FLOAT<br />
|-<br />
|110 || "canopy/position-norm" || FLOAT<br />
|-<br />
|111 || "surface-positions/wing-pos-norm" || FLOAT<br />
|-<br />
|112 || "surface-positions/wing-fold-pos-norm" || FLOAT<br />
|-<br />
|200 || "gear/gear[0]/compression-norm" || FLOAT<br />
|-<br />
|201 || "gear/gear[0]/position-norm" || FLOAT<br />
|-<br />
|210 || "gear/gear[1]/compression-norm" || FLOAT<br />
|-<br />
|211 || "gear/gear[1]/position-norm" || FLOAT<br />
|-<br />
|220 || "gear/gear[2]/compression-norm" || FLOAT<br />
|-<br />
|221 || "gear/gear[2]/position-norm" || FLOAT<br />
|-<br />
|230 || "gear/gear[3]/compression-norm" || FLOAT<br />
|-<br />
|231 || "gear/gear[3]/position-norm" || FLOAT<br />
|-<br />
|240 || "gear/gear[4]/compression-norm" || FLOAT<br />
|-<br />
|241 || "gear/gear[4]/position-norm" || FLOAT<br />
|-<br />
|300 || "engines/engine[0]/n1" || FLOAT<br />
|-<br />
|301 || "engines/engine[0]/n2" || FLOAT<br />
|-<br />
|302 || "engines/engine[0]/rpm" || FLOAT<br />
|-<br />
|310 || "engines/engine[1]/n1" || FLOAT<br />
|-<br />
|311 || "engines/engine[1]/n2" || FLOAT<br />
|-<br />
|312 || "engines/engine[1]/rpm" || FLOAT<br />
|-<br />
|320 || "engines/engine[2]/n1" || FLOAT<br />
|-<br />
|321 || "engines/engine[2]/n2" || FLOAT<br />
|-<br />
|322 || "engines/engine[2]/rpm" || FLOAT<br />
|-<br />
|330 || "engines/engine[3]/n1" || FLOAT<br />
|-<br />
|331 || "engines/engine[3]/n2" || FLOAT<br />
|-<br />
|332 || "engines/engine[3]/rpm" || FLOAT<br />
|-<br />
|340 || "engines/engine[4]/n1" || FLOAT<br />
|-<br />
|341 || "engines/engine[4]/n2" || FLOAT<br />
|-<br />
|342 || "engines/engine[4]/rpm" || FLOAT<br />
|-<br />
|350 || "engines/engine[5]/n1" || FLOAT<br />
|-<br />
|351 || "engines/engine[5]/n2" || FLOAT<br />
|-<br />
|352 || "engines/engine[5]/rpm" || FLOAT<br />
|-<br />
|360 || "engines/engine[6]/n1" || FLOAT<br />
|-<br />
|361 || "engines/engine[6]/n2" || FLOAT<br />
|-<br />
|362 || "engines/engine[6]/rpm" || FLOAT<br />
|-<br />
|370 || "engines/engine[7]/n1" || FLOAT<br />
|-<br />
|371 || "engines/engine[7]/n2" || FLOAT<br />
|-<br />
|372 || "engines/engine[7]/rpm" || FLOAT<br />
|-<br />
|380 || "engines/engine[8]/n1" || FLOAT<br />
|-<br />
|381 || "engines/engine[8]/n2" || FLOAT<br />
|-<br />
|382 || "engines/engine[8]/rpm" || FLOAT<br />
|-<br />
|390 || "engines/engine[9]/n1" || FLOAT<br />
|-<br />
|391 || "engines/engine[9]/n2" || FLOAT<br />
|-<br />
|392 || "engines/engine[9]/rpm" || FLOAT<br />
|-<br />
|800 || "rotors/main/rpm" || FLOAT<br />
|-<br />
|801 || "rotors/tail/rpm" || FLOAT<br />
|-<br />
|810 || "rotors/main/blade[0]/position-deg" || FLOAT<br />
|-<br />
|811 || "rotors/main/blade[1]/position-deg" || FLOAT<br />
|-<br />
|812 || "rotors/main/blade[2]/position-deg" || FLOAT<br />
|-<br />
|813 || "rotors/main/blade[3]/position-deg" || FLOAT<br />
|-<br />
|820 || "rotors/main/blade[0]/flap-deg" || FLOAT<br />
|-<br />
|821 || "rotors/main/blade[1]/flap-deg" || FLOAT<br />
|-<br />
|822 || "rotors/main/blade[2]/flap-deg" || FLOAT<br />
|-<br />
|823 || "rotors/main/blade[3]/flap-deg" || FLOAT<br />
|-<br />
|830 || "rotors/tail/blade[0]/position-deg" || FLOAT<br />
|-<br />
|831 || "rotors/tail/blade[1]/position-deg" || FLOAT<br />
|-<br />
|900 || "sim/hitches/aerotow/tow/length" || FLOAT<br />
|-<br />
|901 || "sim/hitches/aerotow/tow/elastic-constant" || FLOAT<br />
|-<br />
|902 || "sim/hitches/aerotow/tow/weight-per-m-kg-m" || FLOAT<br />
|-<br />
|903 || "sim/hitches/aerotow/tow/dist" || FLOAT<br />
|-<br />
|904 || "sim/hitches/aerotow/tow/connected-to-property-node" || BOOL<br />
|-<br />
|905 || "sim/hitches/aerotow/tow/connected-to-ai-or-mp-callsign" || STRING<br />
|-<br />
|906 || "sim/hitches/aerotow/tow/brake-force" || FLOAT<br />
|-<br />
|907 || "sim/hitches/aerotow/tow/end-force-x" || FLOAT<br />
|-<br />
|908 || "sim/hitches/aerotow/tow/end-force-y" || FLOAT<br />
|-<br />
|909 || "sim/hitches/aerotow/tow/end-force-z" || FLOAT<br />
|-<br />
|930 || "sim/hitches/aerotow/is-slave" || BOOL<br />
|-<br />
|931 || "sim/hitches/aerotow/speed-in-tow-direction" || FLOAT<br />
|-<br />
|932 || "sim/hitches/aerotow/open" || BOOL<br />
|-<br />
|933 || "sim/hitches/aerotow/local-pos-x" || FLOAT<br />
|-<br />
|934 || "sim/hitches/aerotow/local-pos-y" || FLOAT<br />
|-<br />
|935 || "sim/hitches/aerotow/local-pos-z" || FLOAT<br />
|-<br />
|1001 || "controls/flight/slats" || FLOAT<br />
|-<br />
|1002 || "controls/flight/speedbrake" || FLOAT<br />
|-<br />
|1003 || "controls/flight/spoilers" || FLOAT<br />
|-<br />
|1004 || "controls/gear/gear-down" || FLOAT<br />
|-<br />
|1005 || "controls/lighting/nav-lights" || FLOAT<br />
|-<br />
|1006 || "controls/armament/station[0]/jettison-all" || BOOL<br />
|-<br />
|1100 || "sim/model/variant" || INT<br />
|-<br />
|1101 || "sim/model/livery/file" || STRING<br />
|-<br />
|1200 || "environment/wildfire/data" || STRING<br />
|-<br />
|10001 || "sim/multiplay/transmission-freq-hz" || STRING<br />
|-<br />
|10002 || "sim/multiplay/chat" || STRING<br />
|-<br />
|10100 || "sim/multiplay/generic/string[0]" || STRING<br />
|-<br />
|10101 || "sim/multiplay/generic/string[1]" || STRING<br />
|-<br />
|10102 || "sim/multiplay/generic/string[2]" || STRING<br />
|-<br />
|10103 || "sim/multiplay/generic/string[3]" || STRING<br />
|-<br />
|10104 || "sim/multiplay/generic/string[4]" || STRING<br />
|-<br />
|10105 || "sim/multiplay/generic/string[5]" || STRING<br />
|-<br />
|10106 || "sim/multiplay/generic/string[6]" || STRING<br />
|-<br />
|10107 || "sim/multiplay/generic/string[7]" || STRING<br />
|-<br />
|10108 || "sim/multiplay/generic/string[8]" || STRING<br />
|-<br />
|10109 || "sim/multiplay/generic/string[9]" || STRING<br />
|-<br />
|10110 || "sim/multiplay/generic/string[10]" || STRING<br />
|-<br />
|10111 || "sim/multiplay/generic/string[11]" || STRING<br />
|-<br />
|10112 || "sim/multiplay/generic/string[12]" || STRING<br />
|-<br />
|10113 || "sim/multiplay/generic/string[13]" || STRING<br />
|-<br />
|10114 || "sim/multiplay/generic/string[14]" || STRING<br />
|-<br />
|10115 || "sim/multiplay/generic/string[15]" || STRING<br />
|-<br />
|10116 || "sim/multiplay/generic/string[16]" || STRING<br />
|-<br />
|10117 || "sim/multiplay/generic/string[17]" || STRING<br />
|-<br />
|10118 || "sim/multiplay/generic/string[18]" || STRING<br />
|-<br />
|10119 || "sim/multiplay/generic/string[19]" || STRING<br />
|-<br />
|10200 || "sim/multiplay/generic/float[0]" || FLOAT<br />
|-<br />
|10201 || "sim/multiplay/generic/float[1]" || FLOAT<br />
|-<br />
|10202 || "sim/multiplay/generic/float[2]" || FLOAT<br />
|-<br />
|10203 || "sim/multiplay/generic/float[3]" || FLOAT<br />
|-<br />
|10204 || "sim/multiplay/generic/float[4]" || FLOAT<br />
|-<br />
|10205 || "sim/multiplay/generic/float[5]" || FLOAT<br />
|-<br />
|10206 || "sim/multiplay/generic/float[6]" || FLOAT<br />
|-<br />
|10207 || "sim/multiplay/generic/float[7]" || FLOAT<br />
|-<br />
|10208 || "sim/multiplay/generic/float[8]" || FLOAT<br />
|-<br />
|10209 || "sim/multiplay/generic/float[9]" || FLOAT<br />
|-<br />
|10210 || "sim/multiplay/generic/float[10]" || FLOAT<br />
|-<br />
|10211 || "sim/multiplay/generic/float[11]" || FLOAT<br />
|-<br />
|10212 || "sim/multiplay/generic/float[12]" || FLOAT<br />
|-<br />
|10213 || "sim/multiplay/generic/float[13]" || FLOAT<br />
|-<br />
|10214 || "sim/multiplay/generic/float[14]" || FLOAT<br />
|-<br />
|10215 || "sim/multiplay/generic/float[15]" || FLOAT<br />
|-<br />
|10216 || "sim/multiplay/generic/float[16]" || FLOAT<br />
|-<br />
|10217 || "sim/multiplay/generic/float[17]" || FLOAT<br />
|-<br />
|10218 || "sim/multiplay/generic/float[18]" || FLOAT<br />
|-<br />
|10219 || "sim/multiplay/generic/float[19]" || FLOAT<br />
|-<br />
|10300 || "sim/multiplay/generic/int[0]" || INT<br />
|-<br />
|10301 || "sim/multiplay/generic/int[1]" || INT<br />
|-<br />
|10302 || "sim/multiplay/generic/int[2]" || INT<br />
|-<br />
|10303 || "sim/multiplay/generic/int[3]" || INT<br />
|-<br />
|10304 || "sim/multiplay/generic/int[4]" || INT<br />
|-<br />
|10305 || "sim/multiplay/generic/int[5]" || INT<br />
|-<br />
|10306 || "sim/multiplay/generic/int[6]" || INT<br />
|-<br />
|10307 || "sim/multiplay/generic/int[7]" || INT<br />
|-<br />
|10308 || "sim/multiplay/generic/int[8]" || INT<br />
|-<br />
|10309 || "sim/multiplay/generic/int[9]" || INT<br />
|-<br />
|10310 || "sim/multiplay/generic/int[10]" || INT<br />
|-<br />
|10311 || "sim/multiplay/generic/int[11]" || INT<br />
|-<br />
|10312 || "sim/multiplay/generic/int[12]" || INT<br />
|-<br />
|10313 || "sim/multiplay/generic/int[13]" || INT<br />
|-<br />
|10314 || "sim/multiplay/generic/int[14]" || INT<br />
|-<br />
|10315 || "sim/multiplay/generic/int[15]" || INT<br />
|-<br />
|10316 || "sim/multiplay/generic/int[16]" || INT<br />
|-<br />
|10317 || "sim/multiplay/generic/int[17]" || INT<br />
|-<br />
|10318 || "sim/multiplay/generic/int[18]" || INT<br />
|-<br />
|10319 || "sim/multiplay/generic/int[19]" || INT<br />
|}<br />
<br />
<br />
(*) The types are XDR encoded as follows:<br />
<br />
INT 4 bytes, send unconditionally<br />
<br />
FLOAT: 4 bytes, send unconditionally<br />
<br />
BOOL: 4 bytes, send unconditionally<br />
<br />
STRING [LEN|STR|PAD]:<br />
LEN: 4 bytes, length of the decoded string<br />
STR: LEN*4 bytes, encoded string.<br />
PAD: n*4 bytes, padding.<br />
<br />
'''Important'''<br />
Due to a bug, all bytes in the STRING field are sent as 4byte ints (not in the header or the position message). So STR has length LEN*4 and padding (4-LEN%4)*4 bytes, if LEN%4 != 0.<br />
<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=Multiplayer_protocol&diff=50462Multiplayer protocol2012-05-24T15:47:44Z<p>Alfo: /* The header */</p>
<hr />
<div>== The messages ==<br />
<br />
All messages are composed of XDR encoded data. (see [http://www.faqs.org/rfcs/rfc1832.html RFC 1832] for a complete description of XDR). XDR basically means: All data is in network byte order and aligned to the nearest multiple of 4 bytes. Strings are encoded as a zero-terminated array of characters,aligned to the nearest multiple of 4 bytes. Floating point numbers (32 or 64 bit) must be encode in the IEEE standard.<br />
<br />
== The header ==<br />
The header is always 32 bytes long and contains the following fields in exactly that order:<br />
<br />
|'''Magic'''|'''Version'''|'''MsgId'''|'''MsgLen'''|'''ReplyAddress'''|'''ReplyPort'''|'''Callsign'''|'''Data'''|<br />
<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
|Magic:<br />
|4 bytes, always 0x46474653 ("FGFS")<br />
|-<br />
|Version:<br />
|4 bytes, protocol version, currently 0x00010001 (1.1)<br />
|-<br />
|MsgId:<br />
|4 bytes, defines what data is appended to the header. Can be 0x00000001 for chat messages (deprecated) or<br /><br />
0x00000007 for position data<br />all other values are outdated and ignored<br />
|-<br />
|MsgLen:<br />
|4 bytes, the length of the data. '''Important:''' This is not in bytes, see the description of STRING field at the end for more information.<br />
|-<br />
|ReplyAddress:<br />
|4 bytes, deprecated and ignored<br />
|-<br />
|ReplyPort:<br />
|4 bytes, deprecated and ignored<br />
|-<br />
|Callsign:<br />
|8 bytes, zero terminated array of characters representing<br />
the user callsign<br />
|}<br />
<br />
== Data of chat messages ==<br />
The data for chat messages is a zero terminated array of characters. The MsgLen field in the header represents its length. The maximum length is defined to be 256 bytes.<br />
<br />
== Data of position messages ==<br />
The data of position data is more complicated and looks like this:<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
|ModelName<br />
|96 bytes, zero terminated array of characters representing the aircraft model used by the user<br />
|-<br />
|time<br />
|8 bytes, representing the time when this message was generated<br />
|-<br />
|lag || 8 bytes, time offset for network lag<br />
|-<br />
|PosX || 8 bytes, XDR encoded double value, X-ccordinate of users<br /><br />
position wrt the earth centered frame<br />
|-<br />
|PosY || 8 bytes, XDR encoded double value, Y-ccordinate of users<br /><br />
position wrt the earth centered frame<br />
|-<br />
|PosZ || 8 bytes, XDR encoded double value, z-ccordinate of users<br />
position wrt the earth centered frame<br />
|-<br />
|OriX || 4 bytes, XDR encoded float value, X-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|OriY || 4 bytes, XDR encoded float value, Y-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|OriZ || 4 bytes, XDR encoded float value, Z-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|VelX || 4 bytes, XDR encoded float value, velocity of the user in X direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|VelY || 4 bytes, XDR encoded float value, velocity of the user in Y direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|VelZ || 4 bytes, XDR encoded float value, velocity of the user in Z direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|pad || up to 8 bytes for padding the data to a multiple of 8 bytes<br />
|}<br />
<br />
This data is followed by '''property-values''', which are encoded in the form '''ID'''|'''Value'''<br />
<br />
The following properties are transmitted, but not necessarily all present and not in this order:<br />
<br />
'''Important:''' This table is outdated. Please have a look in the flightgear sources at src/MultiPlayer/multiplaymgr.cxx<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
!ID !! Property || Type(*)<br />
|-<br />
|100 || "surface-positions/left-aileron-pos-norm" || FLOAT<br />
|-<br />
|101 || "surface-positions/right-aileron-pos-norm" || FLOAT<br />
|-<br />
|102 || "surface-positions/elevator-pos-norm" || FLOAT<br />
|-<br />
|103 || "surface-positions/rudder-pos-norm" || FLOAT<br />
|-<br />
|104 || "surface-positions/flap-pos-norm" || FLOAT<br />
|-<br />
|105 || "surface-positions/speedbrake-pos-norm" || FLOAT<br />
|-<br />
|106 || "gear/tailhook/position-norm" || FLOAT<br />
|-<br />
|107 || "gear/launchbar/position-norm" || FLOAT<br />
|-<br />
|108 || "gear/launchbar/state" || STRING<br />
|-<br />
|109 || "gear/launchbar/holdback-position-norm" || FLOAT<br />
|-<br />
|110 || "canopy/position-norm" || FLOAT<br />
|-<br />
|111 || "surface-positions/wing-pos-norm" || FLOAT<br />
|-<br />
|112 || "surface-positions/wing-fold-pos-norm" || FLOAT<br />
|-<br />
|200 || "gear/gear[0]/compression-norm" || FLOAT<br />
|-<br />
|201 || "gear/gear[0]/position-norm" || FLOAT<br />
|-<br />
|210 || "gear/gear[1]/compression-norm" || FLOAT<br />
|-<br />
|211 || "gear/gear[1]/position-norm" || FLOAT<br />
|-<br />
|220 || "gear/gear[2]/compression-norm" || FLOAT<br />
|-<br />
|221 || "gear/gear[2]/position-norm" || FLOAT<br />
|-<br />
|230 || "gear/gear[3]/compression-norm" || FLOAT<br />
|-<br />
|231 || "gear/gear[3]/position-norm" || FLOAT<br />
|-<br />
|240 || "gear/gear[4]/compression-norm" || FLOAT<br />
|-<br />
|241 || "gear/gear[4]/position-norm" || FLOAT<br />
|-<br />
|300 || "engines/engine[0]/n1" || FLOAT<br />
|-<br />
|301 || "engines/engine[0]/n2" || FLOAT<br />
|-<br />
|302 || "engines/engine[0]/rpm" || FLOAT<br />
|-<br />
|310 || "engines/engine[1]/n1" || FLOAT<br />
|-<br />
|311 || "engines/engine[1]/n2" || FLOAT<br />
|-<br />
|312 || "engines/engine[1]/rpm" || FLOAT<br />
|-<br />
|320 || "engines/engine[2]/n1" || FLOAT<br />
|-<br />
|321 || "engines/engine[2]/n2" || FLOAT<br />
|-<br />
|322 || "engines/engine[2]/rpm" || FLOAT<br />
|-<br />
|330 || "engines/engine[3]/n1" || FLOAT<br />
|-<br />
|331 || "engines/engine[3]/n2" || FLOAT<br />
|-<br />
|332 || "engines/engine[3]/rpm" || FLOAT<br />
|-<br />
|340 || "engines/engine[4]/n1" || FLOAT<br />
|-<br />
|341 || "engines/engine[4]/n2" || FLOAT<br />
|-<br />
|342 || "engines/engine[4]/rpm" || FLOAT<br />
|-<br />
|350 || "engines/engine[5]/n1" || FLOAT<br />
|-<br />
|351 || "engines/engine[5]/n2" || FLOAT<br />
|-<br />
|352 || "engines/engine[5]/rpm" || FLOAT<br />
|-<br />
|360 || "engines/engine[6]/n1" || FLOAT<br />
|-<br />
|361 || "engines/engine[6]/n2" || FLOAT<br />
|-<br />
|362 || "engines/engine[6]/rpm" || FLOAT<br />
|-<br />
|370 || "engines/engine[7]/n1" || FLOAT<br />
|-<br />
|371 || "engines/engine[7]/n2" || FLOAT<br />
|-<br />
|372 || "engines/engine[7]/rpm" || FLOAT<br />
|-<br />
|380 || "engines/engine[8]/n1" || FLOAT<br />
|-<br />
|381 || "engines/engine[8]/n2" || FLOAT<br />
|-<br />
|382 || "engines/engine[8]/rpm" || FLOAT<br />
|-<br />
|390 || "engines/engine[9]/n1" || FLOAT<br />
|-<br />
|391 || "engines/engine[9]/n2" || FLOAT<br />
|-<br />
|392 || "engines/engine[9]/rpm" || FLOAT<br />
|-<br />
|800 || "rotors/main/rpm" || FLOAT<br />
|-<br />
|801 || "rotors/tail/rpm" || FLOAT<br />
|-<br />
|810 || "rotors/main/blade[0]/position-deg" || FLOAT<br />
|-<br />
|811 || "rotors/main/blade[1]/position-deg" || FLOAT<br />
|-<br />
|812 || "rotors/main/blade[2]/position-deg" || FLOAT<br />
|-<br />
|813 || "rotors/main/blade[3]/position-deg" || FLOAT<br />
|-<br />
|820 || "rotors/main/blade[0]/flap-deg" || FLOAT<br />
|-<br />
|821 || "rotors/main/blade[1]/flap-deg" || FLOAT<br />
|-<br />
|822 || "rotors/main/blade[2]/flap-deg" || FLOAT<br />
|-<br />
|823 || "rotors/main/blade[3]/flap-deg" || FLOAT<br />
|-<br />
|830 || "rotors/tail/blade[0]/position-deg" || FLOAT<br />
|-<br />
|831 || "rotors/tail/blade[1]/position-deg" || FLOAT<br />
|-<br />
|900 || "sim/hitches/aerotow/tow/length" || FLOAT<br />
|-<br />
|901 || "sim/hitches/aerotow/tow/elastic-constant" || FLOAT<br />
|-<br />
|902 || "sim/hitches/aerotow/tow/weight-per-m-kg-m" || FLOAT<br />
|-<br />
|903 || "sim/hitches/aerotow/tow/dist" || FLOAT<br />
|-<br />
|904 || "sim/hitches/aerotow/tow/connected-to-property-node" || BOOL<br />
|-<br />
|905 || "sim/hitches/aerotow/tow/connected-to-ai-or-mp-callsign" || STRING<br />
|-<br />
|906 || "sim/hitches/aerotow/tow/brake-force" || FLOAT<br />
|-<br />
|907 || "sim/hitches/aerotow/tow/end-force-x" || FLOAT<br />
|-<br />
|908 || "sim/hitches/aerotow/tow/end-force-y" || FLOAT<br />
|-<br />
|909 || "sim/hitches/aerotow/tow/end-force-z" || FLOAT<br />
|-<br />
|930 || "sim/hitches/aerotow/is-slave" || BOOL<br />
|-<br />
|931 || "sim/hitches/aerotow/speed-in-tow-direction" || FLOAT<br />
|-<br />
|932 || "sim/hitches/aerotow/open" || BOOL<br />
|-<br />
|933 || "sim/hitches/aerotow/local-pos-x" || FLOAT<br />
|-<br />
|934 || "sim/hitches/aerotow/local-pos-y" || FLOAT<br />
|-<br />
|935 || "sim/hitches/aerotow/local-pos-z" || FLOAT<br />
|-<br />
|1001 || "controls/flight/slats" || FLOAT<br />
|-<br />
|1002 || "controls/flight/speedbrake" || FLOAT<br />
|-<br />
|1003 || "controls/flight/spoilers" || FLOAT<br />
|-<br />
|1004 || "controls/gear/gear-down" || FLOAT<br />
|-<br />
|1005 || "controls/lighting/nav-lights" || FLOAT<br />
|-<br />
|1006 || "controls/armament/station[0]/jettison-all" || BOOL<br />
|-<br />
|1100 || "sim/model/variant" || INT<br />
|-<br />
|1101 || "sim/model/livery/file" || STRING<br />
|-<br />
|1200 || "environment/wildfire/data" || STRING<br />
|-<br />
|10001 || "sim/multiplay/transmission-freq-hz" || STRING<br />
|-<br />
|10002 || "sim/multiplay/chat" || STRING<br />
|-<br />
|10100 || "sim/multiplay/generic/string[0]" || STRING<br />
|-<br />
|10101 || "sim/multiplay/generic/string[1]" || STRING<br />
|-<br />
|10102 || "sim/multiplay/generic/string[2]" || STRING<br />
|-<br />
|10103 || "sim/multiplay/generic/string[3]" || STRING<br />
|-<br />
|10104 || "sim/multiplay/generic/string[4]" || STRING<br />
|-<br />
|10105 || "sim/multiplay/generic/string[5]" || STRING<br />
|-<br />
|10106 || "sim/multiplay/generic/string[6]" || STRING<br />
|-<br />
|10107 || "sim/multiplay/generic/string[7]" || STRING<br />
|-<br />
|10108 || "sim/multiplay/generic/string[8]" || STRING<br />
|-<br />
|10109 || "sim/multiplay/generic/string[9]" || STRING<br />
|-<br />
|10110 || "sim/multiplay/generic/string[10]" || STRING<br />
|-<br />
|10111 || "sim/multiplay/generic/string[11]" || STRING<br />
|-<br />
|10112 || "sim/multiplay/generic/string[12]" || STRING<br />
|-<br />
|10113 || "sim/multiplay/generic/string[13]" || STRING<br />
|-<br />
|10114 || "sim/multiplay/generic/string[14]" || STRING<br />
|-<br />
|10115 || "sim/multiplay/generic/string[15]" || STRING<br />
|-<br />
|10116 || "sim/multiplay/generic/string[16]" || STRING<br />
|-<br />
|10117 || "sim/multiplay/generic/string[17]" || STRING<br />
|-<br />
|10118 || "sim/multiplay/generic/string[18]" || STRING<br />
|-<br />
|10119 || "sim/multiplay/generic/string[19]" || STRING<br />
|-<br />
|10200 || "sim/multiplay/generic/float[0]" || FLOAT<br />
|-<br />
|10201 || "sim/multiplay/generic/float[1]" || FLOAT<br />
|-<br />
|10202 || "sim/multiplay/generic/float[2]" || FLOAT<br />
|-<br />
|10203 || "sim/multiplay/generic/float[3]" || FLOAT<br />
|-<br />
|10204 || "sim/multiplay/generic/float[4]" || FLOAT<br />
|-<br />
|10205 || "sim/multiplay/generic/float[5]" || FLOAT<br />
|-<br />
|10206 || "sim/multiplay/generic/float[6]" || FLOAT<br />
|-<br />
|10207 || "sim/multiplay/generic/float[7]" || FLOAT<br />
|-<br />
|10208 || "sim/multiplay/generic/float[8]" || FLOAT<br />
|-<br />
|10209 || "sim/multiplay/generic/float[9]" || FLOAT<br />
|-<br />
|10210 || "sim/multiplay/generic/float[10]" || FLOAT<br />
|-<br />
|10211 || "sim/multiplay/generic/float[11]" || FLOAT<br />
|-<br />
|10212 || "sim/multiplay/generic/float[12]" || FLOAT<br />
|-<br />
|10213 || "sim/multiplay/generic/float[13]" || FLOAT<br />
|-<br />
|10214 || "sim/multiplay/generic/float[14]" || FLOAT<br />
|-<br />
|10215 || "sim/multiplay/generic/float[15]" || FLOAT<br />
|-<br />
|10216 || "sim/multiplay/generic/float[16]" || FLOAT<br />
|-<br />
|10217 || "sim/multiplay/generic/float[17]" || FLOAT<br />
|-<br />
|10218 || "sim/multiplay/generic/float[18]" || FLOAT<br />
|-<br />
|10219 || "sim/multiplay/generic/float[19]" || FLOAT<br />
|-<br />
|10300 || "sim/multiplay/generic/int[0]" || INT<br />
|-<br />
|10301 || "sim/multiplay/generic/int[1]" || INT<br />
|-<br />
|10302 || "sim/multiplay/generic/int[2]" || INT<br />
|-<br />
|10303 || "sim/multiplay/generic/int[3]" || INT<br />
|-<br />
|10304 || "sim/multiplay/generic/int[4]" || INT<br />
|-<br />
|10305 || "sim/multiplay/generic/int[5]" || INT<br />
|-<br />
|10306 || "sim/multiplay/generic/int[6]" || INT<br />
|-<br />
|10307 || "sim/multiplay/generic/int[7]" || INT<br />
|-<br />
|10308 || "sim/multiplay/generic/int[8]" || INT<br />
|-<br />
|10309 || "sim/multiplay/generic/int[9]" || INT<br />
|-<br />
|10310 || "sim/multiplay/generic/int[10]" || INT<br />
|-<br />
|10311 || "sim/multiplay/generic/int[11]" || INT<br />
|-<br />
|10312 || "sim/multiplay/generic/int[12]" || INT<br />
|-<br />
|10313 || "sim/multiplay/generic/int[13]" || INT<br />
|-<br />
|10314 || "sim/multiplay/generic/int[14]" || INT<br />
|-<br />
|10315 || "sim/multiplay/generic/int[15]" || INT<br />
|-<br />
|10316 || "sim/multiplay/generic/int[16]" || INT<br />
|-<br />
|10317 || "sim/multiplay/generic/int[17]" || INT<br />
|-<br />
|10318 || "sim/multiplay/generic/int[18]" || INT<br />
|-<br />
|10319 || "sim/multiplay/generic/int[19]" || INT<br />
|}<br />
<br />
<br />
(*) The types are XDR encoded as follows:<br />
<br />
INT 4 bytes, send unconditionally<br />
<br />
FLOAT: 4 bytes, send unconditionally<br />
<br />
BOOL: 4 bytes, send unconditionally<br />
<br />
STRING [LEN|STR|PAD]:<br />
LEN: 4 bytes, length of the decoded string<br />
STR: LEN*4 bytes, encoded string.<br />
PAD: n*4 bytes, padding.<br />
<br />
'''Important'''<br />
Due to a bug, all bytes in the STRING field are sent as 4byte ints (not in the header or the position message). So STR has length LEN*4 and padding (4-LEN%4)*4 bytes, if LEN%4 != 0.<br />
<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=Multiplayer_protocol&diff=50461Multiplayer protocol2012-05-24T15:37:43Z<p>Alfo: Describe the byte sent as 4byte bug in the multiplayer protocol</p>
<hr />
<div>== The messages ==<br />
<br />
All messages are composed of XDR encoded data. (see [http://www.faqs.org/rfcs/rfc1832.html RFC 1832] for a complete description of XDR). XDR basically means: All data is in network byte order and aligned to the nearest multiple of 4 bytes. Strings are encoded as a zero-terminated array of characters,aligned to the nearest multiple of 4 bytes. Floating point numbers (32 or 64 bit) must be encode in the IEEE standard.<br />
<br />
== The header ==<br />
The header is always 32 bytes long and contains the following fields in exactly that order:<br />
<br />
|'''Magic'''|'''Version'''|'''MsgId'''|'''MsgLen'''|'''ReplyAddress'''|'''ReplyPort'''|'''Callsign'''|'''Data'''|<br />
<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
|Magic:<br />
|4 bytes, always 0x46474653 ("FGFS")<br />
|-<br />
|Version:<br />
|4 bytes, protocol version, currently 0x00010001 (1.1)<br />
|-<br />
|MsgId:<br />
|4 bytes, defines what data is appended to the header. Can be 0x00000001 for chat messages (deprecated) or<br /><br />
0x00000007 for position data<br />all other values are outdated and ignored<br />
|-<br />
|MsgLen:<br />
|4 bytes, the lenght of the data in bytes<br />
|-<br />
|ReplyAddress:<br />
|4 bytes, deprecated and ignored<br />
|-<br />
|ReplyPort:<br />
|4 bytes, deprecated and ignored<br />
|-<br />
|Callsign:<br />
|8 bytes, zero terminated array of characters representing<br />
the user callsign<br />
|}<br />
<br />
== Data of chat messages ==<br />
The data for chat messages is a zero terminated array of characters. The MsgLen field in the header represents its length. The maximum length is defined to be 256 bytes.<br />
<br />
== Data of position messages ==<br />
The data of position data is more complicated and looks like this:<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
|ModelName<br />
|96 bytes, zero terminated array of characters representing the aircraft model used by the user<br />
|-<br />
|time<br />
|8 bytes, representing the time when this message was generated<br />
|-<br />
|lag || 8 bytes, time offset for network lag<br />
|-<br />
|PosX || 8 bytes, XDR encoded double value, X-ccordinate of users<br /><br />
position wrt the earth centered frame<br />
|-<br />
|PosY || 8 bytes, XDR encoded double value, Y-ccordinate of users<br /><br />
position wrt the earth centered frame<br />
|-<br />
|PosZ || 8 bytes, XDR encoded double value, z-ccordinate of users<br />
position wrt the earth centered frame<br />
|-<br />
|OriX || 4 bytes, XDR encoded float value, X-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|OriY || 4 bytes, XDR encoded float value, Y-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|OriZ || 4 bytes, XDR encoded float value, Z-orientation of the user wrt the earth centered frame, stored in the angle axis representation where the angle is coded into the axis length<br />
|-<br />
|VelX || 4 bytes, XDR encoded float value, velocity of the user in X direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|VelY || 4 bytes, XDR encoded float value, velocity of the user in Y direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|VelZ || 4 bytes, XDR encoded float value, velocity of the user in Z direction wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AV3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional angular velocity vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|LA3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional linear accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA1 || 4 bytes, XDR encoded float value, 1. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA2 || 4 bytes, XDR encoded float value, 2. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|AA3 || 4 bytes, XDR encoded float value, 3. part of the three dimensional angular accelaration vector<br /><br />
wrt the earth centered frame measured in the earth centered frame<br />
|-<br />
|pad || up to 8 bytes for padding the data to a multiple of 8 bytes<br />
|}<br />
<br />
This data is followed by '''property-values''', which are encoded in the form '''ID'''|'''Value'''<br />
<br />
The following properties are transmitted, but not necessarily all present and not in this order:<br />
<br />
'''Important:''' This table is outdated. Please have a look in the flightgear sources at src/MultiPlayer/multiplaymgr.cxx<br />
{| class="prettytable" border="1px" cellspacing="0" cellpadding="2"<br />
!ID !! Property || Type(*)<br />
|-<br />
|100 || "surface-positions/left-aileron-pos-norm" || FLOAT<br />
|-<br />
|101 || "surface-positions/right-aileron-pos-norm" || FLOAT<br />
|-<br />
|102 || "surface-positions/elevator-pos-norm" || FLOAT<br />
|-<br />
|103 || "surface-positions/rudder-pos-norm" || FLOAT<br />
|-<br />
|104 || "surface-positions/flap-pos-norm" || FLOAT<br />
|-<br />
|105 || "surface-positions/speedbrake-pos-norm" || FLOAT<br />
|-<br />
|106 || "gear/tailhook/position-norm" || FLOAT<br />
|-<br />
|107 || "gear/launchbar/position-norm" || FLOAT<br />
|-<br />
|108 || "gear/launchbar/state" || STRING<br />
|-<br />
|109 || "gear/launchbar/holdback-position-norm" || FLOAT<br />
|-<br />
|110 || "canopy/position-norm" || FLOAT<br />
|-<br />
|111 || "surface-positions/wing-pos-norm" || FLOAT<br />
|-<br />
|112 || "surface-positions/wing-fold-pos-norm" || FLOAT<br />
|-<br />
|200 || "gear/gear[0]/compression-norm" || FLOAT<br />
|-<br />
|201 || "gear/gear[0]/position-norm" || FLOAT<br />
|-<br />
|210 || "gear/gear[1]/compression-norm" || FLOAT<br />
|-<br />
|211 || "gear/gear[1]/position-norm" || FLOAT<br />
|-<br />
|220 || "gear/gear[2]/compression-norm" || FLOAT<br />
|-<br />
|221 || "gear/gear[2]/position-norm" || FLOAT<br />
|-<br />
|230 || "gear/gear[3]/compression-norm" || FLOAT<br />
|-<br />
|231 || "gear/gear[3]/position-norm" || FLOAT<br />
|-<br />
|240 || "gear/gear[4]/compression-norm" || FLOAT<br />
|-<br />
|241 || "gear/gear[4]/position-norm" || FLOAT<br />
|-<br />
|300 || "engines/engine[0]/n1" || FLOAT<br />
|-<br />
|301 || "engines/engine[0]/n2" || FLOAT<br />
|-<br />
|302 || "engines/engine[0]/rpm" || FLOAT<br />
|-<br />
|310 || "engines/engine[1]/n1" || FLOAT<br />
|-<br />
|311 || "engines/engine[1]/n2" || FLOAT<br />
|-<br />
|312 || "engines/engine[1]/rpm" || FLOAT<br />
|-<br />
|320 || "engines/engine[2]/n1" || FLOAT<br />
|-<br />
|321 || "engines/engine[2]/n2" || FLOAT<br />
|-<br />
|322 || "engines/engine[2]/rpm" || FLOAT<br />
|-<br />
|330 || "engines/engine[3]/n1" || FLOAT<br />
|-<br />
|331 || "engines/engine[3]/n2" || FLOAT<br />
|-<br />
|332 || "engines/engine[3]/rpm" || FLOAT<br />
|-<br />
|340 || "engines/engine[4]/n1" || FLOAT<br />
|-<br />
|341 || "engines/engine[4]/n2" || FLOAT<br />
|-<br />
|342 || "engines/engine[4]/rpm" || FLOAT<br />
|-<br />
|350 || "engines/engine[5]/n1" || FLOAT<br />
|-<br />
|351 || "engines/engine[5]/n2" || FLOAT<br />
|-<br />
|352 || "engines/engine[5]/rpm" || FLOAT<br />
|-<br />
|360 || "engines/engine[6]/n1" || FLOAT<br />
|-<br />
|361 || "engines/engine[6]/n2" || FLOAT<br />
|-<br />
|362 || "engines/engine[6]/rpm" || FLOAT<br />
|-<br />
|370 || "engines/engine[7]/n1" || FLOAT<br />
|-<br />
|371 || "engines/engine[7]/n2" || FLOAT<br />
|-<br />
|372 || "engines/engine[7]/rpm" || FLOAT<br />
|-<br />
|380 || "engines/engine[8]/n1" || FLOAT<br />
|-<br />
|381 || "engines/engine[8]/n2" || FLOAT<br />
|-<br />
|382 || "engines/engine[8]/rpm" || FLOAT<br />
|-<br />
|390 || "engines/engine[9]/n1" || FLOAT<br />
|-<br />
|391 || "engines/engine[9]/n2" || FLOAT<br />
|-<br />
|392 || "engines/engine[9]/rpm" || FLOAT<br />
|-<br />
|800 || "rotors/main/rpm" || FLOAT<br />
|-<br />
|801 || "rotors/tail/rpm" || FLOAT<br />
|-<br />
|810 || "rotors/main/blade[0]/position-deg" || FLOAT<br />
|-<br />
|811 || "rotors/main/blade[1]/position-deg" || FLOAT<br />
|-<br />
|812 || "rotors/main/blade[2]/position-deg" || FLOAT<br />
|-<br />
|813 || "rotors/main/blade[3]/position-deg" || FLOAT<br />
|-<br />
|820 || "rotors/main/blade[0]/flap-deg" || FLOAT<br />
|-<br />
|821 || "rotors/main/blade[1]/flap-deg" || FLOAT<br />
|-<br />
|822 || "rotors/main/blade[2]/flap-deg" || FLOAT<br />
|-<br />
|823 || "rotors/main/blade[3]/flap-deg" || FLOAT<br />
|-<br />
|830 || "rotors/tail/blade[0]/position-deg" || FLOAT<br />
|-<br />
|831 || "rotors/tail/blade[1]/position-deg" || FLOAT<br />
|-<br />
|900 || "sim/hitches/aerotow/tow/length" || FLOAT<br />
|-<br />
|901 || "sim/hitches/aerotow/tow/elastic-constant" || FLOAT<br />
|-<br />
|902 || "sim/hitches/aerotow/tow/weight-per-m-kg-m" || FLOAT<br />
|-<br />
|903 || "sim/hitches/aerotow/tow/dist" || FLOAT<br />
|-<br />
|904 || "sim/hitches/aerotow/tow/connected-to-property-node" || BOOL<br />
|-<br />
|905 || "sim/hitches/aerotow/tow/connected-to-ai-or-mp-callsign" || STRING<br />
|-<br />
|906 || "sim/hitches/aerotow/tow/brake-force" || FLOAT<br />
|-<br />
|907 || "sim/hitches/aerotow/tow/end-force-x" || FLOAT<br />
|-<br />
|908 || "sim/hitches/aerotow/tow/end-force-y" || FLOAT<br />
|-<br />
|909 || "sim/hitches/aerotow/tow/end-force-z" || FLOAT<br />
|-<br />
|930 || "sim/hitches/aerotow/is-slave" || BOOL<br />
|-<br />
|931 || "sim/hitches/aerotow/speed-in-tow-direction" || FLOAT<br />
|-<br />
|932 || "sim/hitches/aerotow/open" || BOOL<br />
|-<br />
|933 || "sim/hitches/aerotow/local-pos-x" || FLOAT<br />
|-<br />
|934 || "sim/hitches/aerotow/local-pos-y" || FLOAT<br />
|-<br />
|935 || "sim/hitches/aerotow/local-pos-z" || FLOAT<br />
|-<br />
|1001 || "controls/flight/slats" || FLOAT<br />
|-<br />
|1002 || "controls/flight/speedbrake" || FLOAT<br />
|-<br />
|1003 || "controls/flight/spoilers" || FLOAT<br />
|-<br />
|1004 || "controls/gear/gear-down" || FLOAT<br />
|-<br />
|1005 || "controls/lighting/nav-lights" || FLOAT<br />
|-<br />
|1006 || "controls/armament/station[0]/jettison-all" || BOOL<br />
|-<br />
|1100 || "sim/model/variant" || INT<br />
|-<br />
|1101 || "sim/model/livery/file" || STRING<br />
|-<br />
|1200 || "environment/wildfire/data" || STRING<br />
|-<br />
|10001 || "sim/multiplay/transmission-freq-hz" || STRING<br />
|-<br />
|10002 || "sim/multiplay/chat" || STRING<br />
|-<br />
|10100 || "sim/multiplay/generic/string[0]" || STRING<br />
|-<br />
|10101 || "sim/multiplay/generic/string[1]" || STRING<br />
|-<br />
|10102 || "sim/multiplay/generic/string[2]" || STRING<br />
|-<br />
|10103 || "sim/multiplay/generic/string[3]" || STRING<br />
|-<br />
|10104 || "sim/multiplay/generic/string[4]" || STRING<br />
|-<br />
|10105 || "sim/multiplay/generic/string[5]" || STRING<br />
|-<br />
|10106 || "sim/multiplay/generic/string[6]" || STRING<br />
|-<br />
|10107 || "sim/multiplay/generic/string[7]" || STRING<br />
|-<br />
|10108 || "sim/multiplay/generic/string[8]" || STRING<br />
|-<br />
|10109 || "sim/multiplay/generic/string[9]" || STRING<br />
|-<br />
|10110 || "sim/multiplay/generic/string[10]" || STRING<br />
|-<br />
|10111 || "sim/multiplay/generic/string[11]" || STRING<br />
|-<br />
|10112 || "sim/multiplay/generic/string[12]" || STRING<br />
|-<br />
|10113 || "sim/multiplay/generic/string[13]" || STRING<br />
|-<br />
|10114 || "sim/multiplay/generic/string[14]" || STRING<br />
|-<br />
|10115 || "sim/multiplay/generic/string[15]" || STRING<br />
|-<br />
|10116 || "sim/multiplay/generic/string[16]" || STRING<br />
|-<br />
|10117 || "sim/multiplay/generic/string[17]" || STRING<br />
|-<br />
|10118 || "sim/multiplay/generic/string[18]" || STRING<br />
|-<br />
|10119 || "sim/multiplay/generic/string[19]" || STRING<br />
|-<br />
|10200 || "sim/multiplay/generic/float[0]" || FLOAT<br />
|-<br />
|10201 || "sim/multiplay/generic/float[1]" || FLOAT<br />
|-<br />
|10202 || "sim/multiplay/generic/float[2]" || FLOAT<br />
|-<br />
|10203 || "sim/multiplay/generic/float[3]" || FLOAT<br />
|-<br />
|10204 || "sim/multiplay/generic/float[4]" || FLOAT<br />
|-<br />
|10205 || "sim/multiplay/generic/float[5]" || FLOAT<br />
|-<br />
|10206 || "sim/multiplay/generic/float[6]" || FLOAT<br />
|-<br />
|10207 || "sim/multiplay/generic/float[7]" || FLOAT<br />
|-<br />
|10208 || "sim/multiplay/generic/float[8]" || FLOAT<br />
|-<br />
|10209 || "sim/multiplay/generic/float[9]" || FLOAT<br />
|-<br />
|10210 || "sim/multiplay/generic/float[10]" || FLOAT<br />
|-<br />
|10211 || "sim/multiplay/generic/float[11]" || FLOAT<br />
|-<br />
|10212 || "sim/multiplay/generic/float[12]" || FLOAT<br />
|-<br />
|10213 || "sim/multiplay/generic/float[13]" || FLOAT<br />
|-<br />
|10214 || "sim/multiplay/generic/float[14]" || FLOAT<br />
|-<br />
|10215 || "sim/multiplay/generic/float[15]" || FLOAT<br />
|-<br />
|10216 || "sim/multiplay/generic/float[16]" || FLOAT<br />
|-<br />
|10217 || "sim/multiplay/generic/float[17]" || FLOAT<br />
|-<br />
|10218 || "sim/multiplay/generic/float[18]" || FLOAT<br />
|-<br />
|10219 || "sim/multiplay/generic/float[19]" || FLOAT<br />
|-<br />
|10300 || "sim/multiplay/generic/int[0]" || INT<br />
|-<br />
|10301 || "sim/multiplay/generic/int[1]" || INT<br />
|-<br />
|10302 || "sim/multiplay/generic/int[2]" || INT<br />
|-<br />
|10303 || "sim/multiplay/generic/int[3]" || INT<br />
|-<br />
|10304 || "sim/multiplay/generic/int[4]" || INT<br />
|-<br />
|10305 || "sim/multiplay/generic/int[5]" || INT<br />
|-<br />
|10306 || "sim/multiplay/generic/int[6]" || INT<br />
|-<br />
|10307 || "sim/multiplay/generic/int[7]" || INT<br />
|-<br />
|10308 || "sim/multiplay/generic/int[8]" || INT<br />
|-<br />
|10309 || "sim/multiplay/generic/int[9]" || INT<br />
|-<br />
|10310 || "sim/multiplay/generic/int[10]" || INT<br />
|-<br />
|10311 || "sim/multiplay/generic/int[11]" || INT<br />
|-<br />
|10312 || "sim/multiplay/generic/int[12]" || INT<br />
|-<br />
|10313 || "sim/multiplay/generic/int[13]" || INT<br />
|-<br />
|10314 || "sim/multiplay/generic/int[14]" || INT<br />
|-<br />
|10315 || "sim/multiplay/generic/int[15]" || INT<br />
|-<br />
|10316 || "sim/multiplay/generic/int[16]" || INT<br />
|-<br />
|10317 || "sim/multiplay/generic/int[17]" || INT<br />
|-<br />
|10318 || "sim/multiplay/generic/int[18]" || INT<br />
|-<br />
|10319 || "sim/multiplay/generic/int[19]" || INT<br />
|}<br />
<br />
<br />
(*) The types are XDR encoded as follows:<br />
<br />
INT 4 bytes, send unconditionally<br />
<br />
FLOAT: 4 bytes, send unconditionally<br />
<br />
BOOL: 4 bytes, send unconditionally<br />
<br />
STRING [LEN|STR|PAD]:<br />
LEN: 4 bytes, length of the decoded string<br />
STR: LEN*4 bytes, encoded string.<br />
PAD: n*4 bytes, padding.<br />
<br />
'''Important'''<br />
Due to a bug, all bytes in the STRING field are sent as 4byte ints (not in the header or the position message). So STR has length LEN*4 and padding (4-LEN%4)*4 bytes, if LEN%4 != 0.<br />
<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS.png&diff=48792File:ATC-FS.png2012-05-01T13:21:56Z<p>Alfo: uploaded a new version of &quot;File:ATC-FS.png&quot;: better to use a daylight screenshot</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS in use.<br />
|Source = Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48753ATC-FS2012-04-30T08:44:50Z<p>Alfo: /* Flightstrip */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
'''ATC-FS''' (ATC, with flightstrips) is an [[air traffic control]] (ATC) aircraft, with the purpose to help an ATC controller keeping track of the aircraft around his airport as well as helping him guide the aircraft on approach and departure and aircraft just passing through his airspace. It can be added to FlightGear just as a regular aircraft and is built with XML and nasal.<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
{| class="wikitable"<br />
|Callsign<br />
|Flightrules<br />
|Departure<br />
|Assigned heading<br />
|Assigned speed<br />
|Info<br />
|-<br />
|colspan="2"|Aircraft Model<br />
|Destination<br />
|Assigned altitude<br />
|Communication method<br />
|Route<br />
|}<br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS toggles the flightstrip list on the right of the screen. TO ALL opens a compose window to all airmen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]<br />
<br />
= External links =<br />
* [http://www.flightgear.org/forums/viewtopic.php?f=4&t=16168 ATC-FS alpha] topic at the official forum.<br />
<br />
[[Category:Air_Traffic_Control]]<br />
[[Category:Aircraft]]<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48748ATC-FS2012-04-30T08:20:21Z<p>Alfo: /* Related content */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS toggles the flightstrip list on the right of the screen. TO ALL opens a compose window to all airmen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]<br />
<br />
<br />
[[Category:Air_Traffic_Control]]<br />
[[Category:Aircraft]]<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48747ATC-FS2012-04-30T08:19:53Z<p>Alfo: /* Related content */</p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS toggles the flightstrip list on the right of the screen. TO ALL opens a compose window to all airmen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]<br />
<br />
<br />
[[Category:Air_Traffic_Control]]<br />
[[Category:Aircrafts]]<br />
[[Category:Multiplayer]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48745ATC-FS2012-04-30T08:16:47Z<p>Alfo: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS toggles the flightstrip list on the right of the screen. TO ALL opens a compose window to all airmen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]<br />
* [[Category:Air_Traffic_Control]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48744ATC-FS2012-04-30T08:12:47Z<p>Alfo: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS toggles the flightstrip list on the right of the screen. TO ALL opens a compose window to all airmen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways. To setup the localizer offset/heading correctly, change the localizer before opening this dialog. Then click on the runway and write the localizer heading and localizer offset into the input fields above.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-settings.png&diff=48743File:ATC-FS-settings.png2012-04-30T08:09:01Z<p>Alfo: uploaded a new version of &quot;File:ATC-FS-settings.png&quot;: == Summary ==
{{File information
|Description = ATC-FS settings
|Source = FGFS Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS settings dialog<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-radar.png&diff=48742File:ATC-FS-radar.png2012-04-30T08:05:17Z<p>Alfo: uploaded a new version of &quot;File:ATC-FS-radar.png&quot;: == Summary ==
{{File information
|Description = ATC-FS radar
|Source = FGFS Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS radar<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48741ATC-FS2012-04-30T08:04:09Z<p>Alfo: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS toggles the flightstrip list on the right of the screen. TO ALL opens a compose window to all airmen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-fsedit.png&diff=48740File:ATC-FS-fsedit.png2012-04-30T08:00:11Z<p>Alfo: uploaded a new version of &quot;File:ATC-FS-fsedit.png&quot;: == Summary ==
{{File information
|Description = ATC-FS flightstrip editor
|Source = FGFS screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS flightstrip editor<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48739ATC-FS2012-04-30T07:59:05Z<p>Alfo: </p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS will open the flightstrips list on the right of the screen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading and offset of the localizer guideline. Next to the runway field the ILS of the current runway is shown.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The Next ATC and Handoff button are useful for multi ATC environments. So when a pilot leaves your airspace and you want to give the next ATC some information about the pilot, you can enter the name of the next ATC and click 'Handoff'. This will immediately send a message with destination and altitude of the pilot. Also the Leave Airspace message is composed and the pilot is set to uncontrolled.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=ATC-FS&diff=48738ATC-FS2012-04-30T07:41:22Z<p>Alfo: Created page with "{{infobox Aircraft |image = ATC-FS.png |name = ATC-FS |type = ATC |authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</..."</p>
<hr />
<div>{{infobox Aircraft<br />
|image = ATC-FS.png<br />
|name = ATC-FS<br />
|type = ATC<br />
|authors = <ul><li>Markus Pargmann</li><li>Based on ATCs by<ul><li>Joe Emmerich</li><li>Rob Shearman</li><li>Syd Adams</li><li>Csaba Halasz</li></ul></li></ul><br />
|status = Alpha (under development)<br />
|fgname = atc-fs<br />
|download = http://gitorious.org/atc-fs/atc-fs/archive-tarball/master<br />
|development = http://gitorious.org/atc-fs/atc-fs<br />
|version = Alpha<br />
}}<br />
<br />
= Help =<br />
<br />
{| class="prettytable"<br />
!Key<br />
!Function<br />
|-<br />
| Up/Down<br />
| Radar range increase/decrease<br />
|-<br />
| Left/Right<br />
| Previous/Next target<br />
|-<br />
| c<br />
| Compose message to target<br />
|-<br />
| t<br />
| Start flightstrip editor for target<br />
|-<br />
| Ctrl + J/K<br />
| Rotate localizer left/right<br />
|-<br />
| Ctrl + G/H<br />
| Decrease/Increase localizer offset<br />
|-<br />
| Ctrl + L<br />
| Toggle localizer guideline<br />
|-<br />
| Ctrl + A<br />
| Raise your position<br />
|-<br />
| Ctrl + T<br />
| Toggle visual target tracking<br />
|-<br />
| Ctrl + F<br />
| Font selector<br />
|}<br />
<br />
== Flightstrip List ==<br />
<br />
Always click on the callsigns in the list to pick a entry. If the clicked entry is not your current target, it is first selected as target. Another click will open the flightstrip editor.<br />
<br />
=== Flightstrip ===<br />
<br />
A flightstrip contains the following information in exactly that order:<br />
<br />
<table><br />
<thead><br />
<tr class="header"><br />
<th align="left">Callsign</th><br />
<th align="left">Flightrules</th><br />
<th align="left">Departure</th><br />
<th align="left">Assigned heading</th><br />
<th align="left">Assigned speed</th><br />
<th align="left">Info</th><br />
</tr><br />
</thead><br />
<tbody><br />
<tr class="odd"><br />
<td align="left">Aircraft Model</td><br />
<td align="left"></td><br />
<td align="left">Destination</td><br />
<td align="left">Assigned altitude</td><br />
<td align="left">Communication method</td><br />
<td align="left">Route</td><br />
</tr><br />
</tbody><br />
</table><br />
<br />
This is an example:<br />
<br />
[[Image:ATC-FS-flightstrip.png|frame|none|alt=image]]<br />
<br />
=== Flightstrip order ===<br />
<br />
In the flightstrip list the flightstrips are ordered by the state of the flight. They are grouped under following categories:<br />
<br />
; Approach<br />
: Flightstrips ordered by range ascending.<br />
; Land<br />
: Flightstrips ordered by range ascending.<br />
; Taxi<br />
: Flightstrips ordered by callsign.<br />
; Park<br />
: Flightstrips ordered by callsign.<br />
; Takeoff<br />
: Flightstrips ordered by range descending.<br />
; Departure<br />
: Flightstrips ordered by range descending.<br />
; Overflight<br />
: Flightstrips ordered by callsign.<br />
; Untracked<br />
: Subgroups which show exactly where a untracked pilot is and what he is doing. This should make it easier to detect inbound pilots.<br />
<br />
<br />
== Radar ==<br />
<br />
[[Image:ATC-FS-radar.png|frame|none|alt=image]]<br />
<br />
The yellow marked areas are interactive.<br />
<br />
# Information about runways and weather. The complete Rwys field is interactive and will open the ATC-FS settings dialog. The Temp field shows as first item the temperature as second the dewpoint.<br />
# Two interactive ATIS items. The left one (“ATIS”) will send the current ATIS information via chat. The second one shows the current letter representing the ATIS status. For runway changes or significant weather changes, click on this letter. It will switch to the next state (e.g. B to C) and send the ATIS information via chat.<br />
# FLIGHTS will open the flightstrips list on the right of the screen.<br />
# Here you can see different information about the currently tracked pilot. The Callsign field is interactive and will open the flightstrip edit dialog.<br />
# Elements to change the localizer position (the small line starting in the center of the radar). However, this will be reset as soon as you switch the target. (The localizer is set by the runway information for each pilot).<br />
<br />
<br />
== ATC-FS Settings ==<br />
<br />
This dialog gives you the possibility to adjust font, runway and ATC settings and most important to change the active runways.<br />
<br />
[[Image:ATC-FS-settings.png|frame|none|alt=image]]<br />
<br />
# Identifier for yourself. This will be appended to every chat message. It should contain your callsign. Else flightgear inserts your callsign at the beginning of each chat message.<br />
# This is the normal font configuration.<br />
# List of available runways.<br />
# Here you can see and modify the details about a runway, after you clicked on it at the available runways.<br />
# This will save the runway settings entered on the left. If you changed an existing runway, it will replace the old data. If you entered a new runway, this runway will show up in the available runways List after saving (Runway identifier has to be different).<br />
# Deletes an runway. First click on the runway in the available runways list, then delete it with this button.<br />
# Activate the chosen runway.<br />
# Deactivate the chosen runway.<br />
# List of active runways. In the flightstrip edit dialog you can choose one of the active runways. Also those runways are included in the ATIS information.<br />
<br />
<br />
== Flightstrip Editor ==<br />
<br />
[[Image:ATC-FS-fsedit.png|frame|none|alt=image]]<br />
<br />
In the flightstrip editor you can change all important settings for a pilot. Beside changing the information visible in the flightstrip list, you can generate chat messages or define routes for future use.<br />
<br />
# Here you can change the language for the generated chat messages. The languages are customizable in the directory ‘atc-fs/messages/’. To add a new language, copy the en.lang file and translate all messages. Then add the new language to the ‘languages’ file, one language per line.<br />
# To define a new heading, change this field and press enter. the dialog will compute the direction of the turn and compose a message for that.<br />
# Altitude field. Similar to the heading field. Beside normal numbers in unit feet, it can handel the FL prefix and calculate the real altitude (only for calculation, FL notation will be always visible for the user).<br />
# Speed field, similar to heading.<br />
# Here you can choose the communication method. Default is ‘Chat’, which will cause the composed messages to be sent after clicking ‘OK/Send’. The other possibilities (FGCOM and Mumble) will not send any chat messages. But the main purpose is to remind you about the communication method on days with much traffic.<br />
# The ‘Info’ field is free to use. Type whatever you want and it is always displayed in the flightstrip list.<br />
# Runway field. You can choose one of the active runways for this pilot. The first time you call this dialog for a pilot, a runway is randomly set. This also sets the heading of the localizer guideline.<br />
# Beside the runway field you have several other route information. You can always enter them and they will show up if the pilots are in the matching category or you print them via the button. For example ‘Initial’ is meant for the initial route information after takeoff. It is visible in the flightstrip list if the pilot is in ‘Takeoff’ catefory. Clicking ‘Initial route’ generates a message for this route information.<br />
# The first row of this second section shows the current category of the pilot. Changing the category will move the flightstrip in the flightstrip list. By default the pilot is in the overflight category. The transition between some of the categories is automatic: Land - Taxi and Takeoff - Departure. This is decided by range and velocity of the pilot.<br />
# Below the category radio buttons you can see a lot of normal buttons. All of them generate Chat messages for special events. They will use the data about the pilot given above this section. Just experiment what messages are generated. No message is sent before you click ‘Send’.<br />
# This is the direct control section. It bypasses the direction calculations and directly generates the correct command. This creates the possibility to instruct left/right turns that are bigger than 180 degrees.<br />
# Here you can change the chat message you generated via the buttons, or you can simply type a manual message. For fast chatting: The default button of this dialog is ‘OK/Send’, so after entering data you can directly send and exit the dialog by pressing enter two times. The other button ‘OK/Not Send’ is not default but gives you the possibility to apply changes without sending the generated chat message.<br />
<br />
= Related content =<br />
* [[ATC Tutorial]]<br />
* [[ATC-aircraft|ATC1/2 aircraft]]<br />
* [[Howto:_Be_a_controller|Howto: Be a controller]]</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-fsedit.png&diff=48736File:ATC-FS-fsedit.png2012-04-30T07:18:56Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS flightstrip editor
|Source = FGFS Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS flightstrip editor<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-flightstrip.png&diff=48735File:ATC-FS-flightstrip.png2012-04-30T07:17:41Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS example flightstrip
|Source = FGFS Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS example flightstrip<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-radar.png&diff=48734File:ATC-FS-radar.png2012-04-30T07:16:25Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS radar
|Source = FGFS Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS radar<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS-settings.png&diff=48733File:ATC-FS-settings.png2012-04-30T07:14:17Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS settings dialog
|Source = FGFS Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS settings dialog<br />
|Source = FGFS Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfohttps://wiki.flightgear.org/w/index.php?title=File:ATC-FS.png&diff=48732File:ATC-FS.png2012-04-30T07:12:18Z<p>Alfo: == Summary ==
{{File information
|Description = ATC-FS in use.
|Source = Screenshot
|Date = 2012-04-30
|Author = alfo
}}</p>
<hr />
<div>== Summary ==<br />
== Summary ==<br />
{{File information<br />
|Description = ATC-FS in use.<br />
|Source = Screenshot<br />
|Date = 2012-04-30<br />
|Author = alfo<br />
}}<br />
== Licensing ==<br />
{{self|GFDL|cc-by-sa-all|migration=redundant}}</div>Alfo