August 22, 20205 yr On 8/20/2020 at 1:23 AM, igorbischi said: I Completely agree. ATC is useless (the lack of transition level/altitude management drive me crazy...), as it was in FSX. In P3D I use pro-atc or RC4, but I don't think we well see any of them on MSFS. Pilot2ATC already works with FSUIPC7 but Simconnect known stutters make it a mess. Once Asobo resolves this we have P2ATC. Joe Joe (Southern California) System: I9-9900KS @5.1Ghz/ Corsair H115i / Gigabyte A-390 Master / EVGA RTX 2080 Ti FTW3 Hybrid w 11Gb / Trident 32Gb DDR4-3200 C14 / Evo 970 2Tb M.2 / Samsung 40inch TV 40ku6300 4K w/ Native 30 hz capability / Corsair AX850 PS / VKB Gunfighter Pro / Virpil MongoosT-50 Throttle / MFG Crosswind Pedals / LINDA, VoiceAttack, ChasePlane, AIG AI, MCE, FFTF, Pilot2ATC, HP Reverb G2
August 22, 20205 yr You should get instructions from ATC if you are passing through A, C, D or E airspace. If your flightplan passes through A, C, D or E airspace, announce to the Airfield or area ATC your position, altitude and heading. I haven't had any warnings of other traffic yet, nor specific heading or altitude instructions.
August 22, 20205 yr Just tested again, no vectors given on approach: Approach ATC "Continue present heading. Expect vectors for ILS approach RWY15" Tower ATC: "Cleared ILS approach RWY15" Tower ATC: "Cleared to land RWY15" Overall, a tiny little bit better than FSX, but not (yet?) what I expected. And the Azure Voice isn't that impressive either, so many stations are just called "Center", omitting the actual name: "Conact Center on 112-75", but text reads "Frankfurt Center". Oh well, let's see... Edited August 22, 20205 yr by Nik_LSZH
Archived
This topic is now archived and is closed to further replies.