flyblueskies

Reporting an update... I just had two really good flights with NATIVE ATC working really well. I hope I'm not jinxing it... The first with KMFD (Flightsim TO airport) to KSKY (asobo airport). The second with KSEE (Flightsim TO airport) to KRNM (Flightsim TO airport). MCE and NATIVE ATC worked really well together. The only thing I did, was to reinstall MCE 3.1.49 and use Simco64_ldr.exe v2.4.05. That combination is working well so far.

Just an FYI. I could not use MCE version 3.1.56 for Native ATC. It would not work with any version of Simco64_ldr.exe. I had to reinstall MCE version 3.1.49 and then use Simco64_ldr.exe v2.4.0.5 in order to use Native ATC. NOTE: I used only Asobo airports. I did not use any free or purchased airports.

Which version of Simco64_ldr.exe do I need to use Native ATC?

OK, no go to add the increased delay. I upgraded to MCE 3.1.56 and still the same problem. However, what I am seeing is that the entire line in RED appears for a split second, then immediately reduces to a partial 1st letter. That partial first letter does appear to stay longer...but the entire line is missing.

I'll give this a try...but, it definitely is not 3 seconds now. It's there for a flash, just long enough to know it recognized something...and then it's gone. I'll add the above and hopefully, it'll stay on longer than the flash I currently see. Any thoughts on Native ATC not working (well, or not at all) when using non-asobo airports?

Thank you Gerald, in this case it is the Black Square Baron in MSFS 2024.

I have Show Commands in FS checked and my spoken commands do show up in RED at the top left of the screen. But, they flash so fast that I can't read them...is there a setting to keep them up longer? Also, I thought I'd share more information specific to KMFD. If I use the standard built in KMFD, MCE works well when using the built in ATC. But, if I use KMFD from Flightsim.to (https://flightsim.to/addon/14335/kmfd-mansfield-lahm-regional-airport), which is only for MSFS 2020, but does work in MSFS 2024. MCE doesn't work well with ATC at the airport. For KMFD from Flightsim.to, I modify the manifest.json to add "package_order_hint": "BESPOKE_AIRPORT_PATCH", . If I don't do this, approach information does not show up in the GTN 750 (or other gps radios). This places the airport above navigraph-nav-base Now, all navigation approaches show up in MFSF 2024. I'm showing this in case this affects MCE. I really appreciate your help with this.

Ok, I was trying to remember the command "confirm ATC options" to read the ATC menu out loud. Just wondering, is there any variation of 'confirm ATC options' in case I don't remember the exact words? Anyway, I understand what you're saying and I think its great that you're dynamically updating the ATC response. For the most part, it's working well when using with VFR ATC. If it doesn't respond, I usually request option one or option two, etc. This seems to 'jump start' it. Then, after a while, MCE starts to respond by sending the correct keys to ATC.

@Parme Are you using AAO to communicate with Native ATC?

Lorby helped my out with this: https://www.avsim.com/forums/topic/700277-ptt-setup-for-altitude-command-in-msfs-2024/#findComment-5814359

This morning I had a VFR flight from KPOV to KERI where MCE/Native ATC worked extremely well! I couldn't be happier! Then, this afternoon, I took VFR flight from KERI to KMFD, and I simply could not get MCE to work with Native ATC...it was extremely frustrating. I decided to have MCE control the comms, which he gladly took. I then asked him to request TAXI depart straight out...his reply was I very much doubt ATC will know what you're talking about (or something to that effect). I have no idea why he did not think it would work! I have to keep guessing at the reason, start over, or just give up. Hence my request, is there anyway to set an option which explains why MCE does not like this request? Anything that will help me understand what I'm doing wrong or MCE expects in order for this ATC comm to work would be greatly appreciated... EDIT: Actually, it would really be neat if I could ask the FO why not and he would actually tell me the reasons...

Ok, I see what you're talking about now. I added the button as you described (but I used Please instead of commit). It works too. Again, thanks for all your help!

Ok, I thought I did that first. I did click the green MAN button below the Key Down Event (but it was already chosen anyway). I may have simply pasted the script in without choosing RPN first...not sure. I'll try again the way you describe...but it is working the way I set it up the second time, including updating the G1000 altitude in MSFS 2024.

I figured it out...I had to create the commit script (instead of dropping into event box): Then I updated my commit button to use the script (see Key Down Event:) Once I did this, my RPN Script processing window displayed the scripts correctly: I really appreciate your help with this!

Ok, I've got it somewhat working. It is now capturing the altitude without pressing the PTT button. But, it is not activating the script to pass the altitude to MSFS 2024. Here's what I have: The COMMIT RPN: The voice command to activate my Altitude Script, passing to MSFS 2024: The voice Recognition of my Altitude! button event (as shown above): My Voice Recognition of COMMIT: My VoiceApG1000Alt script: My Script Processing Window, which shows the script above did not process: Not sure if this is enough information to help figure out what I'm doing wrong or need to add...