FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 09:24, 1 October 2009

1,439 bytes removed ,  1 October 2009
m
→‎Supplemantery Informations: moved some troubelshooting parts to FGCOM_Testing
m (1st part of restructuring due to now 3 Parts: FGCOM, FGCOM for WIndows, FGCOM_Testing)
m (→‎Supplemantery Informations: moved some troubelshooting parts to FGCOM_Testing)
Line 423: Line 423:
===Supplemantery Informations===
===Supplemantery Informations===
====Tips and Tricks====
====Tips and Tricks====
'''Airport missing in FGCom:'''<br>
<ol>
=====Airport missing in FGCom:=====
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line  
In case your favorite airport does not show up in the FGCOM (command-window), although you can tune your COMM to it, you can add it to your data-file “'''positions.txt'''” in your fgcom directory. See e.g. the line  
   KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
   KSFO,120.500,37.616630,-122.385478,TWR,San Francisco Intl
Line 434: Line 435:
  type    = whatever
  type    = whatever
  name    = whatever
  name    = whatever
''(of course those definition are only known to your own PC and last only until the next data update!)''<br>
''(of course those definition are only known to your own PC and last only until the next data update!)''
 
<br><br>
'''Editing'''<br>
=====Editing FGCOM-Data-Files=====
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
If you edit Textfiles (e.g. Radio-listings) or xml-files you might not see line-endings when using your standard editor.
*For windows you can use "WordPad"
*For windows you can use "WordPad"
*For Linux the "gedit" works fine<br>
*For Linux the "gedit" works fine
 
<br>
'''Copying-Printing this WIKI-Page'''<br>
=====Copying-Printing this WIKI-Page'''=====
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
If you absolutely want to have a local copy of this on your PC or need a hard-copy, then:
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )
*goto this page: ( http://wiki.flightgear.org/index.php/FGCOM )
Line 453: Line 454:
Remember the policies: '''Private use only''' !
Remember the policies: '''Private use only''' !


'''Joystick: ''' ref also: [[Joystick]]<br>
<br><br>
=====Joystick compatibility between Operating Systems:=====
ref also: [[Joystick]]<br>
You may use the same joystick-definitions across all Operating-Systems: But you may need to change the assigned numbers - your joystick-vendor might have done that for you already. Check e.g. (Unix, Mac, Win having assigned different "numbers"):
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”> )
Line 468: Line 471:
  </axis>
  </axis>


'''Joystick and PTT'''<br>
<br><br>
If you want to assigne the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
=====assign PTT to Joystick and PTT=====
If you want to assign the PushToTalk function to your joystick, add the following (for n you have to find your own number!)
  <button n="x">  
  <button n="x">  
   <desc>PTT - Push To Talk</desc>  
   <desc>PTT - Push To Talk</desc>  
Line 484: Line 488:
  </button>
  </button>


'''PTT Problems''' (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 watch 3 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.


====Solving Audio-Problems====
====Solving Audio-Problems====
Line 628: Line 619:


<br><br>
<br><br>
=='''Server installation'''==
=='''Server installation'''==


Jomo
652

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/15671"

Navigation menu