Why my requests are not said nor displayed?

• Make sure the EasyATC/Preferences/Commands.txt file exists, is not corrupted and all the commands you want to use have a valid value (not equal to -1)
• If you can read the requests inthe Message box but you don't hear them, check that the Pilot's voice is not disabled.
• Note that the pilot's automatic readback can be enabled/disabled. If disabled, you need to press a key to readback.

Why the ATC is not clearing me to land?

• Make sure you are landing in the right direction. Ask a landing clearance if needed and pay attention on the runway heading. Depending on the wind direction, the take-off runway can be different from the planned runway.
• The ATC says the clearance:
• You just have triggered a FAF or a MAPT waypoint (IFR stuff)
• If not, when the distance from your plane to the airport is lower than about 2.5 miles (actually, it depends on the triggers min, max, and minimum for airport Constants)

Why the ATC is not clearing me to take-off?

• Have a look on how the radio comunications are handled in EasyATC
• First, there is two clearances before starting a flight: a flight clearance and a take-off clearance. If you have a taxi chart, see the Taxi chart article for how requesting flight, taxi and take-off.
• First of all, make sure you have asked for a flight clearance. If you don't use any Taxi chart, you must ask this flight clearance to the ATC of the airport you are on (usually a Tower). If you use a Taxi chart for this airport, you must ask the flight clearance to the APRON waypoint.
• Check that you are using the right runway! Ask a take-off clearance and pay attention on the runway heading the ATC gives. Depending on the wind direction, the take-off runway can be different from the planned runway.
• If you are not using a taxi chart, you must be on the right side of the expected runway with the same heading (+/- about 10 degrees). Make sure the coordinates of the airport are as close as possible to the middle of the runway you want to take-off from: to know if you are ready for take-off, EasyATC processes the coordinates and heading of your plane with the coordinates of the airport and the heading of the expected take-off runway. 
• If you have a taxi clearance (see Taxi chart section), make sure you are within the trigger limit of the taxi waypoint (0.1 Nm by default, this value is displayed in the Debug text)
• You must trigger the airport
• You must talk to the appropriate ATC: any ATC that have the same CallSign that the aiport. For example if you take-off from Lima, you must contact a Lima ATC (Lima Tower or Lima Approach or Lima Departure). Note that Centers and FIS don't deliver take-off clearance.
• Finally, if you cannot have a take-off clearance, you can take-off and do a transit-in clearance after take-off (wait 10 seconds after leaving the ground to make sure the ATC is informed by X-Plane that you are now flying): everything should become normal for the rest of your flight. Don't hesitate to post your flight plan on the EasyATC forums so that I can found where the issue comes from.

Why the ATC expected flight segment is not the one I'm currently flying?

• In IFR or VFR special, you have to make sure you trigger correctly the track you currently fly. In VFR, this should never occur (please report as a bug). See Debug display to know the flight mode you are in.
• Make sure you don't have two tracks superimposed or very close from each other. In this case EasyATC can encounter some difficulties in selecting the right one
• Try a Transit-out request (the ATC could then release you to VFR)
• Fly back to the waypoint and make sure you trigger it: in the Debug display Distance must be lower than Trigger, and your altitude must be close to the edited altitude in the flight plan.
• If this waypoint is an airport you are supposed to land on in the flight plan, you MUST land to make the ATC expecting the next flight segment.

Why the ATC is speaking continuously, randomly?

• Make sure the keys you use for requesting are not used for any other purpose in any other application. Let's say you change the flaps position of your plane with the F key, when you will press this key, you will probably request for a flight clearance (because in the defaults settings, the F key is used to request flight clearance).
• Note that you can have the same problem with any other application than X-Plane: once EasyATC is running and the ATC is enabled, every keyboard input is handled, whatever EasyATC has the focus or not !
• Make sure you have at least two different voices installed so that the pilot and the ATC speaks with different voices. If not, it sounds like a horrible monolog!

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...

Region flight plan...

For the ones who don't want to spend time on creating flight plans, EasyATC can process Region flight plan. A region flight plan is a list of all the airports you want to be able to contact, to land on or to take-off from. I call this "region" but you can put in this flight plan all the airports you want, from Heathrow to JFK airport or Cambera airport in Asutralia!
The ATC will not expect a lot from you. Then, when flying in VFR, you are fully free to fly where you want.
When approaching one of the airports in the flight plan, just ask for a landing clearance (that will be approved in any case) and land! Once on the ground, you can ask for a take-off and fly to one of the other airports...
Some things to know...

• You can abort a landing by using the Transit Out request. (this works whatever the flight plan is, region or not)
• The ATC will not give you the frequency of the next waypoint when you leave the airspace of an airport. In a region flight plan, the waypoints are not supposed to be waypoints but just a list of available airports.
• Note that to consider a flight plan as a Region flight plan, EasyATC process the whole flight plan: if ALL the waypoints are airports, the flight plan is a region one. If there is at least ONE single waypoint that is not an airport, the flight plan is a "normal" one.