652
edits
m (→Runway Settings: update "runway" chapter) |
m (→Flight Strip Manager: review the Stripe-section) |
||
| Line 244: | Line 244: | ||
====='''Flight Strip Manager'''===== | ====='''Flight Strip Manager'''===== | ||
[[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]] | [[File:OpenRadar-Stripes.png|thumb|right|200px|Handling the Flight-Stripes]] | ||
Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). | Paper Flight Strips are the ATCs help to coordinate his traffic. In reality those strips contain many details about the flight, that we do not have (yet). Based on vertical space-limitations we have gathered the most critical informations into 2 lines, which are automatically initiated and controlled by the program. Those are: | ||
:{| class="wikitable" style="text-align:center" | |||
|- | |||
|Target UID||Aircraft Type||direction to it | |||
|- | |||
|distance||IAS+GND speed||Altitude (FL)||current heading|| | |||
|} | |||
In addition the user may add some more informations in additional lines. We urge you to reduce these additional lines to a minimum, because already with 2 lines the list will become that long, that you must scroll constantly! These lines will be saved as target-data and inserted each time a new stripe is created for that target! We suggest to maintain some target-data and some flight data for all frequent visitors. See as a suggestion several 3rd lines in the example: | |||
"ILS VOR FGC NRE || GED MTR" | |||
<br /><small>This pilot knows how to use ILS, VOR, FGcom, the newRunway at EDDF || he is advised to approach via VOR GED and MTR.</small> | |||
"ILS VOR FGC NRE || KJFK 280° f510" | |||
<br /><small>This pilot also can use ILS, VOR, FGcom, NRE || and will depart to JFK on a straight course of 280° on FL510"</small> | |||
You are absolutely free to define your own codes and whatever. You enter/edit those data by opening the "'''''Note Editor'''''" with a right mouse-click onto the stripe. At the bottom of this editor you can also select in which '''''additional language''''' the "standard commands" shall be transmitted to that target. Always exit that Editor with the ENTER-key in order to transfer the data to the stripe! | |||
''' | You can manipulate the listing of the flight strips: | ||
The | *New radar-targets always appear at the end of the list on the right side | ||
The | *You can move them in vertical order by drag and drop | ||
*You can place them in three horizontal columns (left, middle and right) either by dragging them with the hold-down mouse button or by mouse-clicks left or right of the stripes | |||
*with the "'''''AUTO'''''"-button at the upper edge of this area you can define that the stripes will be sorted automatically into groups according to their left/center/right position. This may be very irritating at first - so you may want to switch that "AUTO" off at first usages! | |||
*The radar-targets will change their color according to the horizontal position of the stripe: | |||
**the radar-targets for stripes at the right side will be '''green''' - these are all targets when initialized! | |||
**the radar-targets for stripes in the center will be '''yellow''' | |||
**the radar-targets for stripes at the left side will be '''cyan''' | |||
On the radar-map the "cyan targets" will overlay the "yellow targets" - and the "yellow targets" will overlay the "green" ones! | |||
<br /> <br /> | |||
You cannot change these combinations of color and position -- but you might define your own definition of what the position means! We suggest the following: | |||
:'''''green''''' = right = initial position: Means not yet defined or not under my control (e.g. passing through on high altitude, is controlled by another ATC, etc.) | |||
:'''''yellow''''' = center = I expect him to get under my control when in range (e.g. 60 mi), or he may be transfered to me by another ATC soon, etc. He may become a danger to the traffic controlled by me if he continues uncontrolled! | |||
:'''''cyan''''' = left = under my control (light cyan when active in the MPchat input-line!) | |||
Again: That is a proposal - you can define your on assignments! | |||
You can apply the following mouse-actions onto the stripes as well as onto the radar-targets: | |||
*a '''''single left''''' mouse-click '''''selects/activities''''' 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 '''''center''''' mouse-click opens the '''''Note Editor''''' (see above) | |||
*a '''''right''''' mouse-click will '''''filter''''' the MPchat-message-list to show only the messages of this target. This is similar to using the "ALL VIS" buttons above the message-list | |||
*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 disturbe the radar-views. | |||
== Useful Features == | == Useful Features == | ||
edits