FGCom (before 3.0): Difference between revisions

Jump to navigation Jump to search

FGCom (before 3.0) (view source)

Revision as of 07:54, 31 October 2013

47 bytes removed ,  31 October 2013
m
→‎Functional test & user briefing: review chp. "Start FlightGear"
m (→‎Functional test & user briefing: review chp. "Start FlightGear")
Line 138: Line 138:
#* '''Disadvantage:''' There may be only a engineering test version available (as of today) - use that with care!
#* '''Disadvantage:''' There may be only a engineering test version available (as of today) - use that with care!
#* '''Installation:'''You can download the needed "Standalone FGCOM".zip from http://fgcom.flightgear.org/download/.
#* '''Installation:'''You can download the needed "Standalone FGCOM".zip from http://fgcom.flightgear.org/download/.


=== Functional test & user briefing ===
=== Functional test & user briefing ===
Experiences pointed out, that the cooperation between FGCom and FlightGear works more reliable, if FlightGear is started first. So we will start with setting up a flight-test-environment:
To insure that we can differentiate between troubles
* that may be caused by the FGFS
* and those caused by FGCom
we will also describe the FGFS-Start and it's, for this test needed, settings in detail.
 
Experiences pointed out, that the cooperation between FGCom and FlightGear works more reliable, if FlightGear is started first. So we will start with setting up FGFS first:


==== Start FlightGear ====
==== Start FlightGear ====
{{note|All of this has nothing to do with FGCom until the "--generic" paragraph (which is deprecated, see Talk page) }}
To set all required and/or proposed settings for this first functional test, we suggest to use
We suggest to use [[FGRun]] to define required and/or proposed settings, in order to avoid typo-errors etc. If you keep the “Show command line” active (compare item 3 following), 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 FGCom-operation:
*for Windows and Linux [[FGRun]]
*which for MAC-OSX is the integrated "GUI Launcher"
In the following we will just point out those commands which are significant for the FGCom-operation:


If you don't have an icon available to start FGrun, then start FlightGear manually:
If you don't have an icon available to start FGrun, then start it manually:


# Start a [[Command line|command-window]]
# Start a [[Command line|command-window]]
# Change into the directory in which FGFS was installed
# Change into the directory in which FGFS was installed
# Execute the following command or something similar
# Execute the following command or something similar
{|
::{|
! style="background:#efefef" | Linux
! style="background:#efefef" | Linux
|fgrun
|fgrun
|-
|-
! style="background:#efefef" | Linux Git:
|cd ~/fgfs<br />sh ./run_fgrun.sh
|-
! style="background:#efefef" | Windows
! style="background:#efefef" | Windows
|C:<br />cd 'C:\Program Files\Flightgear\win32'<br />fgrun.exe
|C:<br />cd 'C:\Program Files\Flightgear\win32'<br />fgrun.exe
Line 163: Line 168:


Wait for the program window to start and then define:
Wait for the program window to start and then define:
<ol>
<li> Start by '''choosing an airplane'''. For this first try we suggest the [[Cessna C172]]P, so we have a common understanding in the following. Also be aware of some airplane-designers reassigning keyboard-keys (e.g. the “space-bar” which is used as PTT, may activate a "BombDrop" in a Fighter-jet!), thus you may not have the PTT-key (“Push To Talk”) available.  See [[FGCOM#Tips and Tricks]].<br />→ Click "Next".
</li><li> 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 />→ Click "Next".[[File:FGrun_base.jpg|thumb|Basic & multiplayer options]]
</li><li> Define the '''Multiplayer options:''' (see [[Howto: 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 server number nearest you - select it in http://mpserver15.flightgear.org/mpserverstatus/. Actually it does not matter which server you take (as long as it is online and not as overcrowded as mpserver02) - 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”
* With "Load/Save as" you may build up yourself a library of settings for different airports.<br />→ Click "Advanced".[[File:FGrun_IP.jpg|thumb|Advanced: Initial Position]]
</li><li> In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
* General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
* Features: “AI Traffic” should be activated already
* 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: ''(see next item)''
** ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.[[File:MPmap.jpg|thumb|[[MPMap]]]]
</li><li> Open the '''[http://mpmap02.flightgear.org MPMap]'''
* if the control-panel is not visible click onto "FGMap | mpserver02: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”
* now you could/should support your preflight planning by clicking onto the wedge in the upper right corner after the airport name and then analyse 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[[File:FGrun_net.jpg|thumb|Advanced: Network]]
</li><li> '''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.
* WARNING: When saving these settings and reloading them again, FGRun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
* If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type


# Start by '''choosing an airplane'''. For this first try we suggest the [[Cessna C172]]P, 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".
::{|
# 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 />→ Click "Next".[[File:FGrun_base.jpg|thumb|Basic & multiplayer options]]
# Define the '''Multiplayer options:''' (see [[Howto: 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 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 and not as overcrowded as mpserver02) - 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”
#* With "Load/Save as" you may build up yourself a library of settings for different airports.<br />→ Click "Advanced".[[File:FGrun_IP.jpg|thumb|Advanced: Initial Position]]
# In the “'''Advanced Options'''” check the following sections (click/select them in the left column):
#* General: Those settings were defined before. Check “Control”, if needed select your input device (Joystick, Keyboard, or Mouse).
#* Features: “AI Traffic” should be activated already
#* 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: ''(see next item)''
#** ''Be aware that any data defined here override already predefined data (e.g. also an airport and runway). So '''do not forget''' to change/delete the here defined positions if some time you want to start from another airport.'' Of course you may save/reload settings for different airports, see "Load/save as" on the main window.[[File:MPmap.jpg|thumb|[[MPMap]]]]
# Open the '''[http://mpmap01.flightgear.org MPMap]'''
#* 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 upper 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[[File:FGrun_net.jpg|thumb|Advanced: Network]]
# '''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.
#* WARNING: When saving these settings and reloading them again, FGRun might replace the given IP-Nr. by the PC-name. As of March 2009 you then have to replace that again with the IP-Nr. So use it only if you have to - first try it by adding nothing between the ",,". Keep it as "in,10,,5000".
#* If you need to '''define the unique IP-Address''', open a [[Command line|command-window]] and type
 
{|
! style="background:#efefef" | OS
! style="background:#efefef" | OS
! style="background:#efefef" | to type
! style="background:#efefef" | to type
Line 214: Line 219:
<br />IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
<br />IP-Adresse. . . . . . . . . . . . : fe80::216:e6ff:fe40:abbf%4
|}
|}
#* '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!![[File:FGrun_IO.jpg|thumb|Advanced: Input/Output]]
:: '''192.168.178.23''' (or '''20''') is the number you would have to input between the two commas. Be very careful and double-check that you do not mistype “.” and “,”!![[File:FGrun_IO.jpg|thumb|Advanced: Input/Output]]
# '''Input/Output:'''  
</li><li> '''Input/Output:'''  
#* You do need a "generic" line as shown, because '''this defines the interface between FlightGear and FGCom'''.
* You do need a "generic" line as shown, because '''this defines the interface between FlightGear and FGCom'''.
#** To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.
** To input a new line: Start by selecting “generic” in the field “Protocol”. Then hit “New” and define the rest as shown.
#** Editing an existing line: Start by clicking onto the existing one, then change as required.
** Editing an existing line: Start by clicking onto the existing one, then change as required.
#** Deleting an existing line: Click onto the line to be deleted, then hit "Delete"
** Deleting an existing line: Click onto the line to be deleted, then hit "Delete"
#* For fgo or the command line add --generic=socket,out,10,localhost,16661,udp,fgcom to the command line options
* For fgo or the command line add --generic=socket,out,10,localhost,16661,udp,fgcom to the command line options
# '''Avionics:''' let us define:
</li><li> '''Avionics:''' let us define:
{|
::{|
! style="background:#efefef" | Nav1:
! style="background:#efefef" | Nav1:
| 114.10  
| 114.10  
Line 235: Line 240:
| Brijj, beacon at SF
| Brijj, beacon at SF
|}
|}
#* And activate DME to Nav1
* And activate DME to Nav1
#* There is no field to input COM-radios, but remember them for setting them later manually:
* There is no field to input COM-radios, but remember them for setting them later manually:
{|
::{|
! style="background:#efefef" | Com1
! style="background:#efefef" | Com1
| 118.60  
| 118.60  
Line 246: Line 251:
| San Francisco
| San Francisco
|}
|}
</li><li> '''Properties:'''
* Here you can define any presetting for any values in the FGFS. See e.g.: <tt>File > Browse Internal Properties</tt> in the FlightGear [[menu]].[[File:FGrun_prop.jpg|thumb|Advanced: Properties]]
* I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
** Input a new line: Just hit “New” and type your string.
** Edit a line: Be sure first to click onto an existing item and then edit this “Property”
** Delete a line: Click onto the line to be deleted then hit "Delete"
</li></ol>
Hit “OK” → “Run” and watch FlightGear starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.


# '''Properties:'''
#* Here you can define any presetting for any values in the FGFS. See e.g.: <tt>File > Browse Internal Properties</tt> in the FlightGear [[menu]].[[File:FGrun_prop.jpg|thumb|Advanced: Properties]]
#* I personally do not want the plane to start rolling without me telling it to. So I set the parking break as default at startup.
#** Input a new line: Just hit “New” and type your string.
#** Edit a line: Be sure first to click onto an existing item and then edit this “Property”
#** Delete a line: Click onto the line to be deleted then hit "Delete"
# Hit “OK” → “Run” and watch FlightGear starting. If screen-place allows you may want to pull the shown "FGFS Report-Window" to the side and watch how busy your PC is while loading the other multi-player models.


==== Start FGCom ====
==== Start FGCom ====
Jomo
652

edits

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

Navigation menu