ATC...

Requests...
To listen the ATC you must request first. See the Requests section for the available requests. If the ATC still not talk, have a look to the FAQ...

ATC Type...
The ATC you talk with can belong to one of the following kind of control areas. The ATC type is edited in the flight planner through a dropdown list.
As in real life, the clearances or information the ATC will give depend on the kind of ATC it is: you cannot have a taxi clearance from a CENTER or DEPARTURE controller!
The ATC Type is also used to build the callsign of the ATC in the messages. ATC callsign (for example Dallas) and ATC Type (Departure) are concatenated to build the whole callsign (Dallas Departure).

APPROACH or DEPARTURE
At this stage there is no much difference in terms of ATC behaviour between Approach and Departure. Select the one you want for the spoken callsign. When talking to that type of ATC...

• VFR flight becomes VFR special 
• Landing information (not clearance) can be delivered
• APPROACH can ask for holding patterns (only IFR)
• Can deliver flight clearance (see Taxi chart section)

CENTER or FIS

• VFR remains VFR
• Are just supposed to answer (always approving!) to transit in, report, altitude change requests
• One day, they will give some traffic information

GROUND

• Deliver taxi clearance

INFO

• Same behaviour than CENTER and FIS
• Not that this Type is used as a "tag" when editing the runways in a Taxi chart

TMA

• VFR become VFR special randomly (See Constants section to modify the probability of being turned into VFR special )
• Similar to APPROACH and DEPARTURE behaviours

TOWER

• VFR flight becomes VFR special if you requested to land or if you are within a STAR or a SID
• Can deliver pretty much everything

ATC behavior...
Many things can be improved in the way the ATC gives you clearances. That the most interesting part of the plugin to program! So feel free to give me feedbacks...
WIP...

Why the ATC does not talk?

• If everything goes right with the app, the Debug display should indicate everything you need to understand why the ATC is not talking. Look at the ATC COM1 CANNOT SPEAK text. If everything goes right, this text should be followed by the reason why it is not talking. See Debug display for the different cases...
• If ATC COM1 CANNOT SPEAK is not displayed but EXPECTED STATE is displayed, check the following:

• The synthesis voices of your OS are working fine
• Make sure ATC is enabled (ATC menu item is green and not red)
• Make sure the ATC is not paused (V3.0)

Radio communications...

EasyATC is an interactive air traffic control tool: you need first to talk to the ATC to hear him talking to you. To talk to the ATC, you must request through keyboard inputs. But like in real life, if you request to the wrong frequency, no one will answer (if the frequency is not used in the area you fly) or the ATC will probably not be able to deliver the clearance you expect.
So you need to set your radio COMMs properly. At this stage, only the COMM1 is processed by EasyATC. COMM2 is for later improvements.

This is all you have to know about radio communications in EasyATC...

• Set frequencies on COMM1 only!
• In most of the planes (almost all planes, probably...) a switch is used to enable/disable the COMM1 sound. So make sure COMM1 is not muted
• You can set your COMM1 to any of the frequencies that are edited in the flight plan. Not necessary the one of the closer waypoint.
• When the waypoint of the frequency you talk to is too far, the ATC will not hear you (see VHF range for example). Note that in this case, the Debug text will indicate that you are too far from the given ATC.
• Once you have set your COMM1, you must request first in order to "awake" the ATC. When flying, the Transit in request is usually the more appropriate way to contact an ATC. If you are on ground, ready to start your flight, flight clearance, taxi clearance and take-off clearance are the ones you should use.
• Once you have talked at least once to the ATC, he can talk to you later on, even if you don't request anymore : he stays in contact with you!... until he leaves you...
• The ATC can close the communication in the following cases:
• You are close to the maximum theorical VHF range from the airport (or the closest waypoint) with the frequency you curently talk to
• You are approaching a waypoint with a different frequency (or no frequency edited in the flight plan) so the ATC clears you to change the frequency, and says goodbye
• The ATC is not authorised to deliver the clearance you ask for and he knows the frequency of the ATC you should contact. This case occurs when you have a Taxi chart in your flight plan and, for example, you ask for a flight clearance to the Ground control! The ATC will then say "you are not talking to the appropriate control. Contact Approach [or Departure] on nnn.nn" because APPROACH ATC is the one that is authorised to deliver flight clearances.
• Note that there is for sure some bugs if you "play" too much with your COMM1. For example, if you contact an ATC, and then change your COMM1 frequency a few seconds, when you set it back to the ATC frequency, you will need to awake him again by requesting...