652
edits
FGCom (before 3.0): Difference between revisions
Jump to navigation
Jump to search
m
→Using FGCom: typos rewording pointers
m (→Testing: minor typos, wording, refferences) |
m (→Using FGCom: typos rewording pointers) |
||
| Line 558: | Line 558: | ||
===Using FGCom=== | ===Using FGCom=== | ||
There are basically 3 types of FGCOM-usage: ( | There are basically 3 types of FGCOM-usage: (ref. the introduction to this wiki-page]]): | ||
*'''Normal usage at airports:''' i.e. You set | *'''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 - but 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 (except for Windows-PC's, sorry), the 123.45 will follow. You may try from time to time if these 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 - but 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 (except for Windows-PC's, sorry), the 123.45 will follow. You may try from time to time if these 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. | ||
| Line 568: | Line 568: | ||
You can add extra lines for any locations you want. e.g.: (watch the separation comas) | You can add extra lines for any locations you want. e.g.: (watch the separation comas) | ||
apt-code = DUMY (a "dummy" or your favorite, but missing, airport code) | apt-code = DUMY (a "dummy" or your favorite, but missing, airport code) | ||
KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz” or just take one of which you are sure that you do not need it in reality ( | KHz = take it out of your “FGFS-home/data/Airports/apt.dat.gz” | ||
long/lat = | or just take one of which you are sure that you do not need it in the FGFS-reality | ||
(notice that several Airports (far apart) use same frequencies! | |||
long/lat = take out of the Mpmap (or Google Map) | |||
type = whatever | type = whatever | ||
name = whatever | name = whatever | ||
| Line 587: | Line 589: | ||
**select the last entry in the sidebar on the left: "Printable version" | **select the last entry in the sidebar on the left: "Printable version" | ||
**Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply" | **Then I suggest: Menu --> File --> "Page Setup": Set to "Landscape" --> "Apply" | ||
**before printing I recommend: Menu --> File --> "Print Preview" and you see those | **before printing I recommend: Menu --> File --> "Print Preview" and you see those many many pages! | ||
**If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer | **If you really want to wast that paper: Menu --> "File" --> "Print" and it will print on your favorite printer | ||
Remember the policies: '''Private use only''' ! | Remember the policies: '''Private use only''' ! | ||
'''Joystick: ''' ref also: [[Joystick]]<br> | '''Joystick: ''' ref also: [[Joystick]]<br> | ||
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you | You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"): | ||
<axis> (instead of the usual <axis n=”3”> ) | <axis> (instead of the usual <axis n=”3”> ) | ||
<desc>Mixture</desc> | <desc>Mixture</desc> | ||
| Line 607: | Line 609: | ||
'''Joystick and PTT'''<br> | '''Joystick and PTT'''<br> | ||
If you want to assigne the PushToTalk function to your joystick, add the following (for n | If you want to assigne the PushToTalk function to your joystick, add the following (for n you have to find your own number!) | ||
<button n=" | <button n="x"> | ||
<desc>PTT - Push To Talk</desc> | <desc>PTT - Push To Talk</desc> | ||
<binding> | <binding> | ||
| Line 626: | Line 628: | ||
**Try to enforce (the usually predefined) port as option. i.e. add “-p16661” to the FGCom Start-Command | **Try to enforce (the usually predefined) port as option. i.e. add “-p16661” to the FGCom Start-Command | ||
**check the FGrun extended Options → Input/output “generic=socket..”: The port there must be the same as for the FGCom, i.e. 16661 (if it was not intentionally changed by you) | **check the FGrun extended Options → Input/output “generic=socket..”: The port there must be the same as for the FGCom, i.e. 16661 (if it was not intentionally changed by you) | ||
**You may try to change the port to e.g. UPD 5004. In this case you have to | **You may try to change the port to e.g. UPD 5004. In this case you have to watch 3 places: | ||
***add the option “-p5004” to the FGCom start-command | ***add the option “-p5004” to the FGCom start-command | ||
***also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004. | ***also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004. | ||