For the realworld procedures I'm replicating in the Aerosoft CRJpro, certain built in commands don't require confirmation and in fact disrupt the flow of things. 

Is there a way to deactivate the requirement that a specific command requires confirmation?  

One of them is to request the flight director to be turned off.   This is requested on the final phase of some non precision approaches and also maneuvers (like steep turns).   

The other case is asking for an engine to be started during a normal starting sequence.    

MCE is great complimentary product to the flight sim experience!   

Wallace Wittkoff

51 minutes ago, wwslk said:

For the realworld procedures I'm replicating in the Aerosoft CRJpro, certain built in commands don't require confirmation and in fact disrupt the flow of things. 

Is there a way to deactivate the requirement that a specific command requires confirmation?  

One of them is to request the flight director to be turned off.   This is requested on the final phase of some non precision approaches and also maneuvers (like steep turns).   

The other case is asking for an engine to be started during a normal starting sequence.    

MCE is great complimentary product to the flight sim experience!   

Wallace Wittkoff

I understand.

The issue is that some commands (those that are very short) can fire accidentally.

Surely, you don't want FO to switch FD off when on CAT II approach, just before landing, nor do you want Fo to start engines before you're ready to go (prompt on first engine start only).

Therefore, most critical commands are secured against accidental trigger.

Having said that, you'll be pleased to hear that you can override that behavior as follows.

Think of a specific speech command that MCE isn't programmed to react to. Built-in commands always take precedence over custom ones.

Example "get rid of fd"

Go to "Commands> tab in MCE user interface and click <Voxscript> button.

In "Voxcript overview panel" click <new> and type "get rid of fd"

The custom command will be listed. At this point MCE will recognize it but won't know what to do with it.

Select the new speech command and click <Edit>

In next screen, enable option "Verbose" so you can hear Fo reply to request, then click <Edit script commands>

Unlike a custom flow where you add all the various actions FO is expected to perform, in this case you just want your custom command to act as an alias to built-in command "fd off".

Add that command ("fd off") and don't forget to save.

Since the custom command is seen as a flow, all commands inside it are assumed intended, therefore no prompt, unless you secure the custom command with option "Require confirmation".

Do the same for other commands if you wish.

 

Perfect, thank you for the detailed explanation.