FS++

Good find. Obviously, this is helping MSFS. MCE only cares whether the options are showing on screen. For instance, if you start a flight to runway, engines running, it won't find anything becaose the options aren't there (clearance for takeoff already granted). Once it locks on their location is can then track the changes. With regards previous menu... In IFR, when Fo has the comms he typically reacts to - [Tune whateverA-atc on XXX.XXX], - Contact whatever_atc, -Acknowledge_whatever. It's tricky with VFR flights as it's not obvious what you expect him to do, not to mention he's not actually pressing PTT when transmitting, just ambient static noise played. How are you typically asking him to handle ATC. Is is with commands such as "ask for flight following", "reply to atc"?

One has to balance functionality and performance. Although it could be tempting to keep cheking whether the ATC meny has changes every second, we don;t do that. Instead, when you hold PTT down to transmit is when a query is made to Simco64_Ldr.exe to check whether options have changed and send new ones to MCE. ALso happens when you ask "confirm atc options". We'll check what's happening when Fo is handling ATC and how often he checks for the menu changes.

For those of you eager to fly the LevelUp B737-900ER and B737-700, grab the updated file that makes it possible for Multi-Crew X-Plane package to fully support them. Grab the patch Manually replace file inside C;\Program Files (x86)\Multi Crew X-Plane\ installation folder. The plane is freeware and can be downloaded from this link: 737NG Series for X-Plane 12 - Aircraft - Threshold It's from the same Author of the ZIBO (737-800)

Thanks for the follow-up Evenually, use this freshly uploaded exe file that is tested with latest MSFS 2024 Beta. Native ATC has always been a black box, even in FSX or Prepar3d. No SDK, no documentation anyhwhere. Even AI won't help here. We have worked it out years ago for every sim. with different approaches in each case and now stable for FSX, Prepar3DMSFS 2020. Just have to accept, every now and then it may break when MSFS is updated. Also, on slow machine, if you ask too eraly for "confirm atc options", it may seem like it won't work, bu it could be just still searching for them. So give it a reasonable 2 minutes after the MCE UI appears, before asking and ensure battery is on as soon as possible. In my case. takes about 1 min to 1 and a hal min. May take less if you have a 5 GHZ CPU Regarding flashing text.... I never experienced that. Things that come to mind, pehaps using an overlay hidden window that is superimposing itself on the sim window or something. I really have no idea. Eventually, use MCE as the sole add-on, then fire he others one at a time until you get the flashing. None of our software performs drawing operation in the sim. The command display window is just a floating tiny window with transparent background sitting at the top left corner and only visible when there is a need to show the command which requires enabling the feature in the first place. Please keep reporting whenever it breaks. Thanks .

Yep, can do via the mce.ini. Default is 3 seconds. You can set it to 5 seconds as follows.. [OPTIONS] DisplayTime=5000

This sort of plane is treated like default Cessna or similar. You could use the mce.ini to tweak dialling pace as it's artificial delay to mimic real world. [PACE] ActionDelay=1500 //The simulated delay that takes place before FO takes action. Values from 0 to 4000 milliseconds) MCPdial=100 //The pace at which FO increments or decrements MCP values from 100 to 250 milliseconds). Doesn't apply to some aircraft where the value is hard coded ButtonPress=800 //The simulated time in milliseconds it takes the FO to flip a single switch. Values 500 to 2500 are accepted VoxKeyAction=1000 //The delay in milliseconds between two consecutive VoxKey actions. Valid entries 0 to 4000. You could try... MCPdial=30 That should make it 3 times faster. Don't use zero

VoiceAttack is more useful to other games where the command set you have to create is in the hundreds, and hope MSFS doesn't lose your key assignements. Besides this, you would be creating 2 instances of the speech engine, one for MCE and another for VoiceAttack. A long time ago, we created a tool called VoxKey which is like a free copy of VoiceAttack, only dedicated to MSFS, Prepar3D, FSX and X-Plane. Windows Start->Multi Crew Experience->Voxkey. There are different profiles. One per simulator. For MSFS, you need to open and edit <FS2020.vkp> profile and transfer some of your VoiceAttack commands there. Do not add anything to do with dialling or cockpit switching as they are already built-in. VoxKey is just an editor. When done adding commands, close it. When MCE starts, it looks up the relevant profile for the currently running flight sim it supposrts and will make those commands available for speech recognition using the same instance of the speech engine used by MCE. So, no, we aren't going to dismantle this core functionality in MCE. In real life, dialling is incremental and should remain so. Dialling pace varies from one plane to another. It's very fast with PMDG planes because they have an efficient SDK. Decent across many supported planes. It is slow on some. Which plane are we talking about?

There are other commands such as "what about ATC options". Having said that, we realized a long time ago that voice control wouldn;t be fun if you have to pause and think hard about what to say. Therefore in addition to the tens of thousands (yes I mean it) of built-in commands that will cater for most variations in speech so you don't have to create any, for the odd speech command you utter twice and notice the crew isn't trained to understand it, see this tread on how to create custom speech commands, tie them to built-in ones and speaking the custom command will act as if you've spoken the one MCE understands. It means you can have own command, in any language and doesn't have to mean anything in any language like "deeg dag doo", associate it to "confirm atc options" and voila. See this thread on how to do that. This is software that learns. https://www.avsim.com/forums/topic/630003-command-for-terrain-radar/

In a nutshell, to achieve useful integration with native ATC, MCE will try to locate those options you see on the screen (ATC window). Unfortunately, the location isn't static and will change for every run of the sim. And when you've already worked out how to find them, every now and then following major sim update (including Beta), we need to work out what changed and how to get them back. It's not "say something and some key is sent to the sim", hat wouldn't be reliable. Once MCE UI shows up, and assuming there is at least one option listed, please allow for up to 2 minutes for it to find the ATC info. After that ask co-pilot "confirm ATC options". If it found them, should hear a TTS voice read out the content of the window aloud. If it still says "no atc options available yet" after 5 minutes, it's very likely caused by breaking changes in the sim. The beauty when you get the info, co-pilot will see something ike 1 - [ Tune Kennedy ground on xxx.xxx] and other fequenciews to tune. Those frequencies are saved along with the control centers they are associated with, speech engine ATC context is dynamically updated so it can easily recognize speech like "going to Kennedy ground", "tune Frankfurt tower on radio one", "over to ground" or your own transmission like "Kennedt ground, JetBlue two five seven is ready for taxi" will be easily recognized as the center name you're tuned to is expected by the speech engine. Imagine the alternative, putting 26000 airport names in speech grammar and hoping for the best. We'll be looking at the most recent Beta that broke it and update files if required.

One way to sort out item 2) is to set your headset as the default audio out in Windows Control Panel, sounds settings

There is a separate Voxkey profile for each simulator. For MSFS 2024 & 2020, you need to open "FS2020.vkp" (might be called "FS2020 Demo.vkp") profile and add custom commands to that one. When MCE loads, it looks up the relevant profile for the currently running flight sim.

It will be a while for this one as the plate is full. If you own the plane, start a thread on their forum. If there is enough interest for a crew, it may take priority.

New package (V3.1.56) is now available for download. Adds support for Inibuilds A340 and fully tested with iFly 737 MAX SP1

Just received a message from iFly regarding release of SP1 for the 737MAX which is already supported. We'd rather not have to release 2 updates in the space of a week. Therefore, a few daya will be needed to check MCE integration with the MAX is as good as before, then a full package update will follow by mid-next week and will also support Inibuilds A340

It's been works in progress for a while now. We should have the first package that fully supports it by the end of next week. To same level as support for all Inibuilds A310/A300-600, A320, A330 & A350