229
edits
Spoken ATC: Difference between revisions
Jump to navigation
Jump to search
→Tips
(→Tips) |
|||
| Line 89: | Line 89: | ||
== | == A realistic behavior == | ||
To achieve realistic behavior, follow a logical sequence of communications, viz.: | To achieve realistic behavior, follow a logical sequence of communications, viz.: | ||
* Contact GND (or TWR) prior to taxiing. | * Contact GND (or TWR) prior to taxiing. | ||
| Line 96: | Line 96: | ||
* Contact APP (if available) prior to enter the CTR. | * Contact APP (if available) prior to enter the CTR. | ||
* etc, etc. | * etc, etc. | ||
== On screen voice == | |||
If the writen messages bother you, when binding (see above) you can call the function as | |||
<syntaxhighlight lang="xml"> | |||
<script> <![CDATA[ spoken_atc.speak(n); ]]> </script> </syntaxhighlight> | |||
with '''n''' seconds you want, even 0 meaning no messages at all.<br /> | |||
= Phraseology customization = | = Phraseology customization = | ||