Jarkko

Details and how to fix:

And please read my previous post again. ATC program AIRAC support and flight planning are two completely different things. VoxATC for example has no way to generate a route or a flight plan for you. You have to create it outside of VoxATC (just like PF3). But... Unlike PF3, VoxATC has full AIRAC support. After you have imported your flight plan, ATC will automatically know all the real world approaches, SIDs/STARs, transitions, speed and altitude restrictions. Real ATC should know these things and this is what VoxATC, Pilot2ATC and ProATC are able to do (because of the AIRAC support)

AIRAC support and flight planning are two totally different things. Programs like VoxATC, Pilot2ATC and ProATC have true AIRAC support. This means that the ATC is aware of the current real world approaches, SIDS/STARs, transitions and all of their speed and altitude restrictions automatically (without user interaction). This is somethings that VoxATC users have gotten used to but something that PF3 is unable to provide.

PF3 doesn't have AIRAC support so it might not be a suitable option for VoxATC users.

You will have to start descending to FL070 and also keep flying the holding pattern.

I took the plunge and upgraded from ASN to AS16. Only one flight done, but it was enjoyable. At least similar performance as ASN, maybe even better. Early days, but not buyers regret so far.

This is a bit worrying, I still use the GTX 580.

I also have the upgrade ready for checkout, but afraid to click order. Any suggestions?

Please explain.

My thoughts exactly I wonder if the SimAir contest winner are still simmers?

This is not true. In the new version, you can add any airline to the database, real or fictional. I've even made instructions on the forums how to add Alaska Airlines to the database in the new version. Also the 3rd party voice sets have voice version of Alaska. Just add the correct ICAO code and callsign to the database and you are good to go. No need to hack your own wav files.

The flight plan info is your digital ATIS (D-ATIS).

European airports have started to support Constant Descent Operations in order to save fuel and reduce noise. So unlike STARs in US that end with vectors, STARs in Europe contain "merge points" that allow the aircraft calculate optimal descent profile and skip vectors. An example from ENGM: "ENGM STAR is based on Point Merge System (PMS) and accommodates Basic Continuous Descent Operations (B- CDO). Each STAR contains segments forming a curved sequencing leg equidistant from the Merge Point (MP). The sequencing leg shall be regarded as a delay manoeuvre for use during periods with heavy traffic. All STAR procedures are described from the start point via intermediate waypoints to the MP, from where an instrument approach procedure commences. Arriving aircraft established on the STAR can expect clearance direct to MP when traffic permits. Succeeding aircraft will subsequently be cleared direct to MP when sufficient spacing to preceding aircraft is obtained. Hence, a precise sequencing can be achieved whilst the aircraft maintain own navigation (LNAV). When cleared direct to MP and also having received an instrument approach clearance, the aircraft shall follow the transition from MP to final as stated in the relevant instrument approach procedure.” - ENGM AD 2.22 Flight Procedures" So if traffic permits, you won't receive vectors.

I would advise that you would be join the official support forum. These questions have been covered there. Thanks!

Like explained 7 posts up. This is not interaction between AI and ATC, but generic real world ATC chatter. User can choose to have the generic ATC chatter on or off (will not affect interaction between ATC and AI).