Hi again. Some more observations regarding the FBW A32NX (still experimental):

1) The ECAM pushbuttons only worked for once where my PM was able to to cycle happily through the pages. The other times PM confirms but nothing happens regardless of what button press you request. 

2) The flight control check seems to ignore rudder (I have separated tiller and rudder) 

3) The Airbus specific callouts work wonderfully and I'm on my way to getting it pretty accurate. Thanks for supporting the aircraft that well, 

4) Question: Is it possible for the PM to announce "ALT *"? 

5) Question: Is there a way to get the Airbus split checklist logic into MCE ('down to the line' vs 'below the line'). I have currently built separate lists (e. g. 'before takeoff down to the line check' and 'before takeoff below the line check'). Is there any way to get it closer to real Airbus phraseology? 

6) Suggestion: Instead of having my PM nagging endlessly during a checklist item would it be possible for the PM to challenge ONCE and then afterwards just let it go? 

7) Last question: Is there a switch in the config to get rid of Mark, Paul, Rob, and all the other ramp managers? I use Pushback toolbar and I am happy with those voices. 

Thanks again and thanks for some feedback! 

Best regards 

Christopher 

On 4/10/2022 at 10:45 PM, djxmdjxm said:

Hi again. Some more observations regarding the FBW A32NX (still experimental):

1) The ECAM pushbuttons only worked for once where my PM was able to to cycle happily through the pages. The other times PM confirms but nothing happens regardless of what button press you request. 

If the FlybyWire is your favorite plane, ensure it is set as the first plane MSFS loads on startup. Do not load that plane after loading another complex plane with tons of lvars like Aerosoft CRJ (which is also fully supported)

2) The flight control check seems to ignore rudder (I have separated tiller and rudder) 

It is meant to be checked. However, sometimes issues with rudder calibration may cause FO not to see the expected deflection.

3) The Airbus specific callouts work wonderfully and I'm on my way to getting it pretty accurate. Thanks for supporting the aircraft that well, 

You're welcome. Always a pleasure to read feedback.

4) Question: Is it possible for the PM to announce "ALT *"? 

FO is meant to make all FMA announcements (at least he does with Developer edition). Unless option "FMA callouts" was disabled in MCE advanced options, or the Experimental edition uses different vars.

5) Question: Is there a way to get the Airbus split checklist logic into MCE ('down to the line' vs 'below the line'). I have currently built separate lists (e. g. 'before takeoff down to the line check' and 'before takeoff below the line check'). Is there any way to get it closer to real Airbus phraseology? 

MCE is designed for real world pilots, with the possibility to assign own airline checklist, not to mention customize flows to ANY airline. You could do that yourself.

Whatever checklist sections are found in custom checklist, the headers act like trigger sentences. See document "How to customize checklist". Do not edit checklists found in MCE installation folder. Rather have your own in \My Documents\ (or anywhere else, then assign custom checlist via the MCE checklist tab

To trigger a section, speak section_header + word "checlist" or "check"

Example "before takeoff down to the line check" will work, provided you have a section header "before takeoff down to the line"

6) Suggestion: Instead of having my PM nagging endlessly during a checklist item would it be possible for the PM to challenge ONCE and then afterwards just let it go? 

There is a limit as to how many times he challenges. Use option "strict checkist" so that he doesn't keep challenging too much.

7) Last question: Is there a switch in the config to get rid of Mark, Paul, Rob, and all the other ramp managers? I use Pushback toolbar and I am happy with those voices. 

Affirmative.

In "Advanced options" panel, click <View config".

mce.ini will open in Notepad. Ensure you have

[RAMP]

Nogreeting=1

Since ramp agents only react when you ask them to provide a service, that should be enough to suppress their presence. Restart MCE for changes to take effect.

Thanks again and thanks for some feedback! 

My pleasure.

Best regards 

Christopher 

No worries Christopher.

Experimental Edition woll be looked at next week.

Meanwhile, replies are embedded in your post

Edited April 12, 20224 yr by FS++

Thanks a lot! Will implement your input. 

Regarding item 1) 

I normally just load one airplane during an msfs session. So the ECAM button issue might have some other cause. 

Hi again, 

just a hopefully simple request:

WHEN running a voxscript flow. WHEN there is an unrecognised command. 

AS IS: MCE shows error message in top left corner of the screen that a command was not recognised. 

Requests: MCE shows error message in top left corner of the screen that a command was not recognised. AND it shows which exact command was not recognised. 

For some reason I can say "set parking brake" -  but I can not use it in a voxscript. "engage parking brake" seems to work though. That makes identifying the culprit command a little tedious sometimes. 

Thanks for looking into it. Or most probably you already have a working solution. 

2 hours ago, djxmdjxm said:

Hi again, 

just a hopefully simple request:

WHEN running a voxscript flow. WHEN there is an unrecognised command. 

AS IS: MCE shows error message in top left corner of the screen that a command was not recognised. 

Requests: MCE shows error message in top left corner of the screen that a command was not recognised. AND it shows which exact command was not recognised. 

For some reason I can say "set parking brake" -  but I can not use it in a voxscript. "engage parking brake" seems to work though. That makes identifying the culprit command a little tedious sometimes. 

Thanks for looking into it. Or most probably you already have a working solution. 

Could be a typo (like break instead of brake) in the script. select command, click edit and type the correct command.

You could identify the command by going to the screen showing the commands part of a flow and testing them one by one.

In MSFS, be it with FlyBywire or Aerosoft CRJ, if you click the <Command> button in Voxscript panel, you should see a listbox containing some of the available commands for those specific planes. You can either speak them or add them to custom flows if you wish. It's even possible to get the FO to execute a flow silently and while he is at it, order him to dial something or set the odd additional switch via a diect command.

The "set parking brake" is intuitive and quite ommand so should be part of stock grammar. We'll make sure it does.

Now here is something little known and yet vey powerful and not available in any other speech based product.

You can educate the co-pilot to understand ANY of your natural talk, as follows.

Here is an example.

There are dozens of speech commands to notify the cabin crew about you intending to leave shortly so they can make sure the doors are closed. Let's assume you find it hard to memorize one of those trigger sentences like "cabin crew prepare for gate departure" and prefer to say "cabin crew captain speaking we are about to depart" (or anything else you may want to say and not even refer to cabin crew).

In "Command" tab, click <Voxscript> button

In "Voxscript overview", click <New> as if you are about to create a new task for Fo to execute".

Type your custom sentence whatever it is and click OK

At this point, it will be added to the list of tasks, speech engine will recognize it, but MCE wouldn't know what to make of it.

Select the custom command and click <Edit>

In next screen, enable "Verbose" option so it doesn't get executed silently, then click <Edit script commands>

On a custom flow, you would typically add many actions to the list. In this case you want the custom command to act as an alias for a built-in command the crew is trained to react to.

Click the <command> button and type one of the built-in sentences that achieves the goal "cabin crew prepare for gate departure" (or other built in command).

Don't forget to save the new flow.

From now on, speaking what comes naturally to you will act as if you spoke one of the built-in commands.

It's like a built-in translator.

You can even push things further by writing a custom command in ANY language not just English. You'll be surprised the English US speech recognizer doesn't care one bit about how words are written. It's mostly how they sound. Therefore, Germans for instance could interact with cabin crew in German, Italians in Italian etc..

Just write the custom trigger sentence the way it sounds using English phonemes (without regard for grammar rules or words validity).

On 4/8/2022 at 9:32 PM, djxmdjxm said:

Hi everyone, 

thanks to FS++ for this great piece of work that I now could get to work decently with MSFS (a reinstall with both main install and patch helped to detect the correct aircraft). 

I have noticed a few few glitches with the Flybywire A32NX (experimental build (!)): 

The following switches do not work for me: 

• "retract landing lights" doesn't switch
• "nose switch to takeoff" (T.O.) - not recognized - cannot switch to takeoff setting at all
• dome light dim / brt / off - does not do anything
• emergency exit lights is reversed (ON is OFF | OFF is ON)
• NAV & LOGO lights settings "2", "1" and "OFF" (turning OFF doesn't work)
• WIPER is reversed (FAST is SLOW | SLOW is FAST)

If this is normal with the experimental build then ignore me. But it actually works quite well. 

I'm running MCE on v2.9.61

Thanks for looking into it!

Assuming you are running MCE Ultimate Edition, please download thiz file, unzip and manually replace all files as per folder structure.

http://www.multicrewxp.com/Ultimate-Edition-Patch.zip

Landing lights retraction and extension sorted

taxi light to takeoff or taxi sorted

logo/Nav light sorted

Emergency lights sorted

Wipers either go on or off.

Dome light will require more time

3 hours ago, FS++ said:

Assuming you are running MCE Ultimate Edition, please download thiz file, unzip and manually replace all files as per folder structure.

http://www.multicrewxp.com/Ultimate-Edition-Patch.zip

Landing lights retraction and extension sorted

taxi light to takeoff or taxi sorted

logo/Nav light sorted

Emergency lights sorted

Wipers either go on or off.

Dome light will require more time

Thanks, will test later this week! I think I do own the full-fledged version. 

On 4/25/2022 at 10:22 PM, djxmdjxm said:

Thanks, will test later this week! I think I do own the full-fledged version. 

I only mentioned Ultimate so that users on MSFS edition aren't tempted to use it. They will have to wait for the other patch.

On 4/25/2022 at 7:56 PM, FS++ said:

Assuming you are running MCE Ultimate Edition, please download thiz file, unzip and manually replace all files as per folder structure.

http://www.multicrewxp.com/Ultimate-Edition-Patch.zip

Landing lights retraction and extension sorted

taxi light to takeoff or taxi sorted

logo/Nav light sorted

Emergency lights sorted

Wipers either go on or off.

Dome light will require more time

Here my test results. Thanks for your efforts!

Landing lights:

• "on" --> on
• "off" --> retract
• "retract" --> retract

I guess, that's fine. 

Taxi lights:

• Work just fine

Nav lights (Mode 1 apparently not yet supported by FBW):

• "on" --> 2
• "2" --> 2
• "off" --> off

Works!

Emergency lights:

• Work just fine

Wipers:

• "on" --> fast
• "fast" --> fast
• "slow" --> fast
• "off" --> off

That's fine. This might get more interesting as soon as MSFS supports physical wiper effects. 

ECAM:

• Requesting pages has worked once three weeks ago. But never again. 
• I always get a positive response fom FO but action is not performed. 

Autobrake:

• Positive response from FO - but no action. 

 

23 hours ago, djxmdjxm said:

ECAM:

• Requesting pages has worked once three weeks ago. But never again. 
• I always get a positive response fom FO but action is not performed. 

Autobrake:

• Positive response from FO - but no action. 

 

Thanks for feedback.

Some switches and dials do require the use of the lvar s module.

Go back to downloaded patvh and look under \MSFS\ folder.

Copy the lvars module and paste it to \MSFS\Community\ folder, overwriting anything that is there.

He should be able to handle almost anything (exception ois the EVAC Purser-Captain switch which is just a texture flip at this stage).

Should also get all FMA callouts not just "ALT star"

Edited May 1, 20224 yr by FS++

On 5/1/2022 at 3:29 PM, FS++ said:

Thanks for feedback.

Some switches and dials do require the use of the lvar s module.

Go back to downloaded patvh and look under \MSFS\ folder.

Copy the lvars module and paste it to \MSFS\Community\ folder, overwriting anything that is there.

He should be able to handle almost anything (exception ois the EVAC Purser-Captain switch which is just a texture flip at this stage).

Should also get all FMA callouts not just "ALT star"

Thanks. I actually did update the lvar files when installing your patch in the first place. I'll have a look at them. 

On 5/1/2022 at 4:29 PM, FS++ said:

Thanks for feedback.

Some switches and dials do require the use of the lvar s module.

Go back to downloaded patvh and look under \MSFS\ folder.

Copy the lvars module and paste it to \MSFS\Community\ folder, overwriting anything that is there.

He should be able to handle almost anything (exception ois the EVAC Purser-Captain switch which is just a texture flip at this stage).

Should also get all FMA callouts not just "ALT star"

The following document by FBW describes all the accessible functions: Flight Deck A32NX API - FlyByWire Simulations Documentation also the "custom LVARs" (many others are to be accessed via simConnect). However, they have names (e.G. "A32NX_AUTOBRAKES_ARMED_MODE_SET") that I cannot find in the A320.hvar file supplied with the MCE patch. Do I need to add the A32NX function names here? Can I map them somewhere within MCE? Haven't found THAT file yet. 

Let me know if I can help you with something here. Thanks!

Maybe this A32NX FSUIPC template file can help:  a32nx/flybywire-aircraft-a320-neo.evt at master · flybywiresim/a32nx · GitHub (it was referenced on this page: FlyByWire A32NX API - FlyByWire Simulations Documentation)

18 hours ago, djxmdjxm said:

The following document by FBW describes all the accessible functions: Flight Deck A32NX API - FlyByWire Simulations Documentation also the "custom LVARs" (many others are to be accessed via simConnect). However, they have names (e.G. "A32NX_AUTOBRAKES_ARMED_MODE_SET") that I cannot find in the A320.hvar file supplied with the MCE patch. Do I need to add the A32NX function names here? Can I map them somewhere within MCE? Haven't found THAT file yet. 

Let me know if I can help you with something here. Thanks!

You don't have to do anything other than to ensure the wasm module that ships in MCE installer (also included in patch) is present inside \Community\ folder.

All Lvars and hVars will then be visible to MCE. And yes, for Ecam pages, it's the hVars

4 hours ago, FS++ said:

You don't have to do anything other than to ensure the wasm module that ships in MCE installer (also included in patch) is present inside \Community\ folder.

All Lvars and hVars will then be visible to MCE. And yes, for Ecam pages, it's the hVars

Thanks for the update. I assume the file should sit here: "..\Community\fsuipc-lvar-module\modules\FSUIPC7_WASM.wasm". Correct?

BTW, do I have to explicitly "ENABLE WASM" in FSUIPC? The FSUIPC UI menu offers the option "Add-ons" > "WASM" > "Enable". 

Edited May 8, 20224 yr by djxmdjxm
I found additional details