652
edits
FGCom (before 3.0): Difference between revisions
Jump to navigation
Jump to search
m
just beaty operations
m (minor changes and hid the "Private use only" sentence.) |
m (just beaty operations) |
||
| Line 21: | Line 21: | ||
For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html | For details see the FGFS common hardware and driver requirements on http://www.flightgear.org/hardwarereq.html | ||
Of course you will also need a connection to the Internet for worldwide voice communication | Of course you will also need a connection to the Internet for this real-time, worldwide voice communication. | ||
<br> | <br> | ||
| Line 31: | Line 31: | ||
ref.: http://www.flightgear.org/ | ref.: http://www.flightgear.org/ | ||
|- | |- | ||
|align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of the FGFS. As the name says, it enables communication of several players via a chat-function (keyboard | |align="center" |'''Multiplayer'''||[[Howto: Multiplayer|“Multiplayer”]] is not an installable program but an integrated function of the FGFS. As the name says, it enables communication of several players via a chat-function (until now per keyboard - now also with this vocal interface: FGCom). | ||
|} | |} | ||
<br> | <br> | ||
| Line 111: | Line 111: | ||
<br> | <br> | ||
===Testing=== | ===Testing=== | ||
During testing we will | During testing | ||
#we will test the basic FGCOM-functions without the FGFS | |||
#after that the FGCOM together with the FGFS | #after that we test the FGCOM together with the FGFS | ||
# | #finally we test/adjust the Microphone and Loudspeaker system | ||
For these tests please see the [[FGCOM_Testing|FGCOM_Testing]] | For these tests please see the [[FGCOM_Testing|FGCOM_Testing]] | ||
| Line 142: | Line 142: | ||
|} | |} | ||
Wait for the Program-Window to start and then define:<br><br> | Wait for the Program-Window to start and then define:<br><br> | ||
'''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]] | '''1)''' Start by '''choosing an airplane'''. For this first try we suggest the c172p, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar”), thus you may not have the PTT-key (“Push To Talk”) available. See [[FGCOM#Tips and Tricks]]<br> | ||
→ Click “Next”<br><br> | → Click “Next”<br><br> | ||
'''2)''' As '''starting place''' please define the airport KPAO (Palo Alto) runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br> | '''2)''' As '''starting place''' please define the airport KPAO (Palo Alto) runway 13, so we all see the same messages in the following reports. A second reason for KPAO is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br> | ||
| Line 153: | Line 153: | ||
|“AI models” must be activated in order to see all traffic | |“AI models” must be activated in order to see all traffic | ||
<br><br>“Multiplayer” must be activated | <br><br>“Multiplayer” must be activated | ||
<br><br>type | <br><br>type “'''mpserverXX.flightgear.org'''” into the field “Hostname:”, replace “XX” with the server number nearest you - select it in http://pigeond.net/flightgear/mpstatus/. Actually it does not matter which server you take (as long as it is online) - you might try which server gives you the best response-times. | ||
<br><br>Insert your “Callsign:” (max. 7 characters) | <br><br>Insert your “Callsign:” (max. 7 characters) | ||
<br><br>define the “in” and “out” ports both with the standard “5000” | <br><br>define the “in” and “out” ports both with the standard “5000” | ||
| Line 416: | Line 416: | ||
===Using FGCom=== | ===Using FGCom=== | ||
There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]): | There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]): | ||
*'''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through the "'" (UpperCase#) and/or the Chat-Menus. In addition you then can talk to anybody in a radius of about 50 km (about 30 miles) around the airport, may that be friends, a maintained FGCOM-ATC/Twr-Operator, airport utilities, etc.. Be aware that as of April 2009 only very few planes are using the FGCOM for ATC-purposes - thus you should always use the ATC-Chat "keyboard"-procedures to announce arrivals/departures/taxiing etc. in addition. (We hope that may change in some future!)<br><br> | *'''Normal usage at airports:''' i.e. You set your radio to the airport as usual. Thus you are set up for the usual ATC-(keyboard)-procedures (either through the "'" (UpperCase#) and/or the Chat-Menus). In addition you then can talk to anybody in a radius of about 50 km (about 30 miles) around the airport, may that be friends, a maintained FGCOM-ATC/Twr-Operator, airport utilities, etc.. Be aware that as of April 2009 only very few planes are using the FGCOM for ATC-purposes - thus you should always use the ATC-Chat "keyboard"-procedures to announce arrivals/departures/taxiing etc. in addition. (We hope that may change in some future!)<br><br> | ||
*The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and not yet "overcrowded!). Also when traveling you might want to listen on the 122.75 for others who want to contact you (or reverse). When there is much "talk" on the 122.75 you might just arrange with your partner to switch to 123.45 - and return to 122.75 afterward. As of April 2009 the 122.75 is already operational for this application, the 123.45 will follow soon. You may try from time to time if this limitations still exist.<br><br> | *The '''AirToAir frequencies (122.75 and 123.45)''' are ideal for all Multiplayer events. They are without any range-limitations - and not yet "overcrowded!). Also when traveling you might want to listen on the 122.75 for others who want to contact you (or reverse). When there is much "talk" on the 122.75 you might just arrange with your partner to switch to 123.45 - and return to 122.75 afterward. As of April 2009 the 122.75 is already operational for this application, the 123.45 will follow soon. You may try from time to time if this limitations still exist.<br><br> | ||
*Finally you can manipulate the frequency-tables (positions.txt in your FGFS/FGCOM local directory) and define an own frequency for special events. e.g. a Flight-School at one airport with maybe multiple student-groups. Of course those are local manipulations on your own PC, which you have to agree on with your (planned to be) partners in advance. | *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. | ||