I have MCE V 2.9.00 and the latest MSFS 2020 (1.13.16) and I cannot get MCE to use Native ATC. The PRESS TO TALK button works OK. When I ask MCE to confirm ATC options, MCE reports NO ATC OPTIONS AVAILABLE yet. However, when displaying ATC, all options are there.

Not sure if I have something set incorrectly (such as Multi Player) etc., but this appeared happen with the latest MSFS 2020 update.

1 hour ago, flyblueskies said:

I have MCE V 2.9.00 and the latest MSFS 2020 (1.13.16) and I cannot get MCE to use Native ATC. The PRESS TO TALK button works OK. When I ask MCE to confirm ATC options, MCE reports NO ATC OPTIONS AVAILABLE yet. However, when displaying ATC, all options are there.

Not sure if I have something set incorrectly (such as Multi Player) etc., but this appeared happen with the latest MSFS 2020 update.

It has been reported via e-mail

Will be looked at as an urgent matter

Thank you Gerald!

I mainly fly GA using untowered airports. While I have PF3, for me, using built in ATC works very well for my general flying.

I appreciate the time you put in to help us!

Hi Gerald,

I have MCE V 2.9.00 and the latest MSFS 2020 (1.13.16) and I cannot get MCE to use Native ATC.

 ATC not responding, Co-pilot acknowledges me, but no interactions with MSFS 2020.

Regards Brian

(BJ from OZ)

Same here wondering if theirs any progress on this issue.

I also have the same issue.

 

OK guys. Should be sorted in this patch

If already up to date with V2.9.0.0 only need to replace "Simco64_Ldr.exe" in \Multi Crew Experience\ installation folder.

Report back and state which exact MSFS version you're running. Steam or Microsoft distribution, Standard, Premium or Ultimate.

 

HI, All works perfectly now I have: MSFS 2020 (1.13.16) Ultimate edition, Store version.

Great work thanks.

Confirm that it does work. I have the Microsoft Standard distribution edition

I did notice an issue...flying from KWYS to KBZN. After taking off I handed comms to the FO. On my way to KBZN, I selected KBZN from the nearest airport list. At this point, the FO kept going between tuning comm1 to ATIS then back to TOWER then back to ATIS...this kept repeating over and over. I noticed that ATIS is in slot 1, then he after tuning to ATIS, TOWER then takes slot 1 and so the FO tunes to TOWER, then ATIS takes over slot 1....well  you get the idea. Not sure if you can do something about this or not. To stop this, I have to take the comms back and handle the comms myself (which is OK).

Anyway, MCE is communicating with NATIVE ATC now!

Thanks!

On 2/24/2021 at 1:24 AM, flyblueskies said:

Confirm that it does work. I have the Microsoft Standard distribution edition

I did notice an issue...flying from KWYS to KBZN. After taking off I handed comms to the FO. On my way to KBZN, I selected KBZN from the nearest airport list. At this point, the FO kept going between tuning comm1 to ATIS then back to TOWER then back to ATIS...this kept repeating over and over. I noticed that ATIS is in slot 1, then he after tuning to ATIS, TOWER then takes slot 1 and so the FO tunes to TOWER, then ATIS takes over slot 1....well  you get the idea. Not sure if you can do something about this or not. To stop this, I have to take the comms back and handle the comms myself (which is OK).

Anyway, MCE is communicating with NATIVE ATC now!

Thanks!

 I can confirm I just had this hapen to me also today, Exactlly as described above not the same airport but FO kept switching frequencies till I took over control of the radio.

The dev has been quiet on this topic for a while, got any updates? Havent used the copilot since last week , a real bummer...

On 2/23/2021 at 8:24 PM, flyblueskies said:

Confirm that it does work. I have the Microsoft Standard distribution edition

I did notice an issue...flying from KWYS to KBZN. After taking off I handed comms to the FO. On my way to KBZN, I selected KBZN from the nearest airport list. At this point, the FO kept going between tuning comm1 to ATIS then back to TOWER then back to ATIS...this kept repeating over and over. I noticed that ATIS is in slot 1, then he after tuning to ATIS, TOWER then takes slot 1 and so the FO tunes to TOWER, then ATIS takes over slot 1....well  you get the idea. Not sure if you can do something about this or not. To stop this, I have to take the comms back and handle the comms myself (which is OK).

Anyway, MCE is communicating with NATIVE ATC now!

Thanks!

I reported this exact same issue a week prior and the dev tried to convince me i didnt know what i was talking about, and that i must be wrong.

On 2/25/2021 at 8:48 AM, exocet72 said:

 I can confirm I just had this hapen to me also today, Exactlly as described above not the same airport but FO kept switching frequencies till I took over control of the radio.

Thanks for reporting.

Should be sorted in latest patch

Now, when he sees "Tune ATIS" he won't select it unless you tell him "switching to ATIS", "dial ATIS on radio one" etc..