229
edits
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
'''Spoken ATC''' allows the pilot to listen to the directives of the ''Air Traffic Controller''. | |||
[[ ---- Page under construction ----]] | [[ ---- Page under construction ----]] | ||
Line 49: | Line 49: | ||
APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).<br /> | APP stations will give a vector to the runway threshold in use (if you are far from there) or order to contact TWR (if you are inside the CTR).<br /> | ||
TWR stations will give instructions to join pattern or make direct final (depending on your position).<br /> | TWR stations will give instructions to join pattern or make direct final (depending on your position).<br /> | ||
= Tips = | |||
== a realistic behavior == | |||
To achieve a realistic behavior, follow a logical sequence of communications, viz.: | |||
* - Contact GND (or TWR) prior to taxiing. | |||
* - Contact TWR prior to take-off or land. | |||
* - Contact DEP (if available) after take-off to leave the CTR. | |||
* - Contact APP (if available) prior to enter the CTR. | |||
* etc, etc. | |||
== Phraseology customization == | |||
You can customize the phraseology by editing the "''phraseology.nas''" file (only lines 44 to 82, please!).<br /> | |||
The file includes abundant commented lines to help you understand how to do it.<br /> | |||
Besides that, you can call the ''phrase_test()'' function to check your customization at runtime.<br /> | |||
=== phrase_test() function === | |||
You can ... (TODO) | |||
== On screen voice == | |||
If the gui.popupTip() messages bother you, when binding (see above) you can call the function as | |||
<script>spoken_atc.speak('''n''')</script> | |||
with '''n''' seconds you want.<br /> | |||
= = | |||
<big> And remember this is '''VFR''': heed the instructions of the ATC but '''keep your eyes wide open !'''</big> |
edits