652
edits
FGCom (before 3.0): Difference between revisions
Jump to navigation
Jump to search
→Tips and Tricks: add PTT hints
(add description of Prereqs, Installation Linux + Windows) |
(→Tips and Tricks: add PTT hints) |
||
| Line 189: | Line 189: | ||
ToBeDefined | ToBeDefined | ||
====Tips and Tricks==== | ====Tips and Tricks==== | ||
'''PTT''' (Push To Talk) | |||
*'''if the FGCom Command-window initiates, but does not respond to any COMM or PTT activity:''' | |||
**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) | |||
**You may try to change the port to e.g. UPD 5004. In this case you have to change at 2 places: | |||
***add the option “-p5004” to the FGCom start-command | |||
***also change the value in the FGrun (“Wizard”) → Advanced Options → Input/output to 5004. | |||
***and you may have to tell your Firewall to allow port UPD 5004<br><br> | |||
*'''if in the FGCom Command-Window the Airport indication is ok''', | |||
**but when hitting the PTT it does not appear: | |||
***[LISTEN] mute mic, unmute speaker | |||
***[SPEAK] unmute mic, mute speaker</nowiki> <br> | |||
**Be sure the FGFS window is the active window. Move the Mouse-Pointer into the FlightGear-Window and click once, then try again (while the Mouse-Pointer remains in that window! Some systems do change the “active Window” according to where the mouse is!) | |||
**Check the “''YourPlane''-set.xml” file in your FGFS/data/Aircraft/YourPlane directory: If you find a line “<key n="32">” then this plane is intentionally using “key 32” (Space) for something other than the PTT. Known planes that do that as of Feb. 2009 are: an2, bluebird-base, ogel, OV10.., seafireIIc, spitfireIIa, ufo. | |||
--[[User:Jomo|Jomo]] 13:34, 11 March 2009 (EDT) | |||
ToBeDefined | ToBeDefined | ||