652
edits
OpenRadarGuide: Difference between revisions
Jump to navigation
Jump to search
m
Typos and minor updates
(→Operating: Note for bug that minimizes screen at start up on OSX) |
m (Typos and minor updates) |
||
| Line 66: | Line 66: | ||
For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start. | For all data there are standard values given as defaults. If you do change any values, they will be saved and presented to you during the next start. | ||
<br /> | <br /> | ||
If this is the very first time you start | If this is the very first time you start OpenRadar, then you have to verify your “Settings” first, thus click onto the “Settings”-tab: | ||
=== OpenRadar-Welcome - Settings === | === OpenRadar-Welcome - Settings === | ||
| Line 78: | Line 78: | ||
<br /> | <br /> | ||
:'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar | :'''a) Internal:''' FGCom(s) are started and controlled internally by OpenRadar | ||
::For this mode you have to define all available fields to tell | ::For this mode you have to define all available fields to tell OpenRadar where your FGcom resides and what options shall be used: | ||
::'''Path:''' Here you define where your FGcom is installed. | ::'''Path:''' Here you define where your FGcom is installed. | ||
:::In the following some examples: | :::In the following some examples: | ||
| Line 95: | Line 95: | ||
|} | |} | ||
::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar''' | ::::'''*) for OSX this does not apply because you will be starting FgCom in a Terminal window before starting OpenRadar''' | ||
</small> | |||
::'''Executable:''' Here you define the program-name that shall be started | ::'''Executable:''' Here you define the program-name that shall be started | ||
:::*For Windows: "fgcom.exe" or "anyName.bat" | :::*For Windows: "fgcom.exe" or "anyName.bat" | ||
:::*for Linux: "fgcom" or "anyName.sh" | :::*for Linux: "fgcom" or "anyName.sh" | ||
:::*OSX: ''again for OSX this doe not apply'' | :::*OSX: ''again for OSX this doe not apply'' | ||
::'''Server:''' There are 2 FGcom-servers available as of today: | ::'''Server:''' There are 2 FGcom-servers available as of today: | ||
::*delta384.server4you.de <small>''(we do suggest this one)''</small> | ::*delta384.server4you.de <small>''(we do suggest this one)''</small> | ||
::*fgcom.flightgear.org.uk | ::*fgcom.flightgear.org.uk | ||
::'''Client:''' | ::'''Client:''' must always be “localhost” | ||
::'''FGcom Ports:''' The here defined values are crucial for the operation because: | ::'''FGcom Ports:''' The here defined values are crucial for the operation because: | ||
::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !! | ::*They are the only connection between the OpenRadar and FGcom. So you must define those the same in OpenRadar as well as in FGcom !! | ||
| Line 113: | Line 112: | ||
:'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port. | :'''b) External:''' OpenRadar controls a manually started instance of FGcom - via the defined Port. | ||
::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.: | ::For this one you only need to define where that FGcom is running and what the connecting port is. e.g.: | ||
::*'''Client:''' | ::*'''Client:''' localhost | ||
::::<small>If you want to run FGcom on a different PC you must define here the IP of the remote PC and you must start FGCOM on that PC with the option -s, | |||
:::::e.g. "fgcom -Sdelta384.server4you.de -p16662 -i1 -o1 -s192.168.178.23" </small> | |||
::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)'' | ::*'''FGcom Ports:''' 16661,16662 ''(if e.g. 2 FGcom instances were started)'' | ||
<br /> | <br /> | ||
| Line 128: | Line 129: | ||
:If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source! | :If your airport is too small to be in that worldwide list, you can provide the code of another bigger airport with METAR data nearby in the sector.property file. But be aware that then your customers weather-settings may differ to yours, because they may use the standard FGFS-METAR-Source! | ||
Please click on the verify button to have your settings checked | |||
Please click on the verify button to have your settings checked prior to returning to the left/primary tab: | |||
===Select Airport=== | ===Select Airport=== | ||
| Line 406: | Line 408: | ||
<br /> <br /> | <br /> <br /> | ||
---- | ---- | ||
== Related content == | |||
* [[OpenRadar|The Design-Rules for OpenRadar]] | |||
* [[OpenRadar: Editing routes|Editing STAR/SID routes]] | |||
* [[OpenRadarKnownIssues|FAQ / Known Issues]] | |||
[[Category:Air Traffic Control]] | |||
[[Category:Java]] | |||
[[Category:OpenRadar| ]] | |||
[[Category:OpenRadar|Guide]] | [[Category:OpenRadar|Guide]] | ||