FGCom (before 3.0): Difference between revisions

Open a [[command|command-window]] and change into the directory in which FGCom was installed (probably the same as the FGFS) and start the FGCom. Do not use any other options than the server address “-sfgcom.flightgear.org.uk”, so  that we all see the same indications throughout this description:

||for Std. Linux e.g.: ||fgcom -Sfgcom.flightgear.org.uk<br>sh ./run_fgcom.sh || "-Sfgcom..." with capital "S"

||for Windows e.g.: ||D:<br>cd \flightgear<br>fgcom -sfgcom.flightgear.org.uk || "-sfgcom..." with small "s"

You should then see:

We suggest to use the FGrun ([[FlightGear Launch Control]]) to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” (compare item 3) active, 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 the FGCom-operation:

:use a command-window (like above for the FGCom)  

:change into the directory in which FGFS was installed  

:and start the program from there:

||for Mac: || ToBeDefined ||

'''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 won't have the  PTT-key (“Push To Talk”) available. See [[Tips/Tricks]])<br>  

'''2)''' As '''starting place''' we suggest KPAO-13 (Livermore), so we all see the same messages in the following reports. A second reason is of course that KPAO comes already with the basic scenery-package, and thus is available for everybody.<br>

'''3)''' Define the '''Multiplayer options:''' (see wiki “Multiplayer” for details)

 

 

 

#“AI models” must be activated in order to see all traffic

#“Multiplayer” must be activated

#type “mpserverXX.flightgear.org” into the field “Hostname:”, replace “XX” with the available server number nearest you. 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.

#Insert your “Callsign:” (max. 7 characters)

#define the “in” and “out” ports both with the standard “5000”

#→ Click “Advanced”<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:

##open http://mpmap01.flightgear.org

##if the control-panel is not visible click onto "FGMap | mpserver01:5000 | pilots: 7”

##click on “nav”

##disable all options except “apt code”

##type “KPAO” into the filed “Navaids lookup”

##hit ENTER or click onto the reading-glass symbol

##click onto the appearing line “Airport KPAO Palo Alto Arpt Of Santa Clara Co”

##now you could/should support your preflight planning by clicking onto the wedge in the right corner after the airport name and then analyze all data given under “info”, “atc”, metar”, and “links”  

##then zoom into the airport

##set the mouse over the wanted “Parking lot” and read that position in the upper right corner of the screen

##type those long/lat values into the field below and also the wanted heading of the plane while parking

 

 

'''5) 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. If you need it, open an [[Command-window|command]] and type

The  '''192.168.178.23''' (or '''20''') is the number you would have to input between the to commas. Be very careful and double-check that you do not mistype “.” and “,”!!

'''6) Input/Output:''' This defines the interface between FGFS and FGCom.  

 

|width="70"|  

|width="70"|Nav1:

There is no field to input COM-radios, but remember them for manual setting later:

|width="70"|  

|width="70" |Com1

'''8) Properties:''' Here you can define any presetting for any values in the FGFS<br>see e.g.: FGFS-menu-bar --> File --> “Browse Internal Properties”

 

 

e.g. I personally do not want the plane to start rolling without me telling it. So I set the parking break as default at startup.

:Input new: Just hit “New” and type your string.

:Edit: Be sure first to click onto an existing item and then edit this “Property”