After loading the airbus, engines running and MCE, I tried commands. Some worked, others didn't. For instance, flaps and spoilers worked. However, baro, altitude, heading and VS didn't, even though the FO responded to my instructions. For instance, he would say set heading 185 but the heading indicator didn't move. Likewise with altitude and VS.

I'm wondering if there is a list of the functions or commands that work or do i have to go though all of them from the manuals and note the ones that work? 

Since, according to the MCE website, all 3 FsLabs airbusses are supported, I'm hoping for clarification on what is and isn't supported.

I'm running p3d 5 V1.2 MCE V 2.8.8.3 and most recent FsLabs aircraft. 

1 hour ago, acroflyer said:

After loading the airbus, engines running and MCE, I tried commands. Some worked, others didn't. For instance, flaps and spoilers worked. However, baro, altitude, heading and VS didn't, even though the FO responded to my instructions. For instance, he would say set heading 185 but the heading indicator didn't move. Likewise with altitude and VS.

I'm wondering if there is a list of the functions or commands that work or do i have to go though all of them from the manuals and note the ones that work? 

Since, according to the MCE website, all 3 FsLabs airbusses are supported, I'm hoping for clarification on what is and isn't supported.

I'm running p3d 5 V1.2 MCE V 2.8.8.3 and most recent FsLabs aircraft. 

Haven't checked with very latest releases of the buses., May want to send the "sim=whatever_is_written_there" in "aircraft.cfg" files for the 3 variants, in order to check FsLabs didn't alter the string which would cause MCE not to identify plane as the supported A3XX from FsLabs

The audio you hear as well as speech engine run within "mce.exe" as an external process for better stability of the sim.

The actions on FSL buses switches happen via "mcfslA3X.dll" which is expected to be inside \Prepar3D v5\MCE dlls\ and/or \Prepar3D v4\MCE dlls\ folder.

If you have re-installed the sim, you need to re-install MCE so it can put the files again in expected location. There is a separate dll for each supported complex plane.

FCU is fully supported.

With FSL A3XX however, because there is no SDK yet, you need to wait a few minutes before Fo can work out where to read those values from.

Once you start MCE, and assuming the plane is powered, you should see him pull heading know and increment it (just to make sure it's not at zero). He's actually working out where to read it from. When both engines are running and you start MCE, it could take 2 to 3 minutes for him to work them out. Starting from cold and dark, it will take much longer.

In general, a trained pilot wouldn't need to consult the manual.

The system is designed for flexibility. There are various ways to ask for a switch to be set.

flight director on

FD on

FD switch on

FD activate

FD two switch on

engage autopilot

autopilot switch on

activate autopilot

etc...

And if the above don't give enough flexibility, you could create your own natural speech commands that would act as if you spoke one of the built-in commands.

There is a manual listing speech commands specific to Airbuses.

Windows menu Start->Multi Crew Experience->Airbus A3XX commands.pdf

Examples

push heading knob

pull the heading knob

pull speed knob

A tell tale sign MCE not seeing the plane as the supported airbus, those commands may not be available for speech recognition. Don't assume it's your microphone or accent at fault.

 

 

 

Thanks for your explanation. I have the "mcfslA3X.dll" in my P3d 5 MCE dlls folder.I also have the FsInsider64.dll in my P3D folder. While on the ground I tried the speed, heading vs and altitude commands and gave them lots of time to respond. Only altitude worked. However, vs jumped to +1 and heading changed by 1 degree.

I'll continue to play with commands, particularly the FsLabs specific commands from the MCE A320 folder.

Glad I have MCE as it saves me a lot of mouse work on other P3D aircraft.

I'll send you the aircraft.cfg files for each aircraft and engine variants.