292
edits
| Line 135: | Line 135: | ||
#Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. | #Below it, bottom left, you see the '''MPchat Area''' for the FlightGear multiplayer chat feature. | ||
#On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are | #On the right side you see the '''Service Area''' with 4 subparts. From top to bottom those are | ||
##'''Status | ##'''Status Information''' | ||
##'''COM-Radios''' <small>''(only if you have defined one or more)''</small> | ##'''COM-Radios''' <small>''(only if you have defined one or more)''</small> | ||
##'''Runway Manager''' to set up runways used | ##'''Runway Manager''' to set up runways used | ||
| Line 191: | Line 191: | ||
*OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. | *OpenRadar will always set the ATC-name <small>(as it appears on the very top of the service area - see the following chapter)</small> in front of the message. | ||
Below that entry-line is the scrollable list of sent messages. In that list the messages of the selected user are colored cyan. With the button "'''''VIS'''''" you may filter to see only the messages of the | Below that entry-line is the scrollable list of sent messages. In that list the messages of the selected user are colored cyan. With the button "'''''VIS'''''" you may filter to see only the messages of the visible users - with "'''''ALL'''''" you see the messages of all contacts in range again. | ||
You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care! | You may enlarge that area by grabbing the upper edge with the left mouse-button and move it upward. Of course that will reduce the size of the radar-screen -- so use it with care! | ||
| Line 207: | Line 207: | ||
*Miles: The distance between the target and the mouspointer. | *Miles: The distance between the target and the mouspointer. | ||
*min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small> | *min: The time the target needs to get to that mousepointed area - '''IF''' the speed remains steady as is!! <small>In this example there is given a "n/a" (not available) which most probably means the plane is not moving (may be parked)!</small> | ||
</li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. | </li><li>The fourth line shows the mostly needed weather information '''Wind''', '''Pressure''' and '''Visibility'''. If you hover your mouse over it, you can see the complete last METAR-message received, in it's original form. <small>(For help ref to http://wiki.flightgear.org/METAR#METAR)</small>. Please note that these values are similar to ATIS information: METAR directions is given in TRUE, ATIS in magnetic... | ||
</li></ol> | </li></ol> | ||
====='''COM-Radios'''===== | ====='''COM-Radios'''===== | ||
| Line 222: | Line 222: | ||
|COM0||Ctrl||NumOff+Num0 | |COM0||Ctrl||NumOff+Num0 | ||
|- | |- | ||
|COM1|| | |COM1||SHIFT||NumOff+Num1 | ||
|- | |- | ||
|COM2|| ||NumOff+Num2 | |COM2|| ||NumOff+Num2 | ||
| Line 259: | Line 259: | ||
"ILS VOR FGC NRW || GED MTR" | "ILS VOR FGC NRW || GED MTR" | ||
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the | <br /><small>This pilot knows how to use ILS, VOR, FGcom, the new Runway at EDDF || he is advised to approach via VOR GED and MTR.</small> | ||
"ILS VOR FGC NRW || KJFK 280° f510" | "ILS VOR FGC NRW || KJFK 280° f510" | ||
| Line 284: | Line 284: | ||
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets: | You can apply the following mouse-actions onto the stripes as well as onto the radar-targets: | ||
*a '''''single left''''' mouse-click '''''selects/ | *a '''''single left''''' mouse-click '''''selects/activates''''' it, i.e. its radar-target becomes "light cyan" and its UID is set into the MPchat input-line. In addition its listed messages in the MPchat-list become colored cyan! | ||
*a '''''double left''''' mouse-click '''''centers''''' the radar-map onto that target - thus it is easy to spot! The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center! | *a '''''double left''''' mouse-click '''''centers''''' the radar-map onto that target - thus it is easy to spot! The selection of any of the "preset zoom levels" (GROUND, TOWER, APP, Sector) will reset the map-position again to its center! | ||
*a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above) | *a '''''center''''' mouse-click opens the '''''Note Editor''''' (see above) | ||
*a '''''right''''' mouse-click | *a '''''right''''' mouse-click shows the dialog to choose pre-defined ATC messages to be sent to the current contact | ||
*a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views. | *a '''''CTRL+left''''' mouse-click will define that target as '''''neglected'''''. Thus his radar-target will become just a light gray color, that will not overlay or otherwise disturb the radar-views. | ||
edits