RESOLVED

Gerald,

thanks to your fantastic support (and patience): now everything is OK.
As you suggested, replacing the FsinInsider64.dll with a fresh copy worked perfectly.

BTW: as I am discovering new commands by trial and error, is there a full list of them available? (The examples provided with MCE, although very extensive, cover only a part of MCE's capabilities...).

Once again thanks, I owe you three beers !
Giorgio 

18 hours ago, goggi said:

RESOLVED

Gerald,

thanks to your fantastic support (and patience): now everything is OK.
As you suggested, replacing the FsinInsider64.dll with a fresh copy worked perfectly.

BTW: as I am discovering new commands by trial and error, is there a full list of them available? (The examples provided with MCE, although very extensive, cover only a part of MCE's capabilities...).

Once again thanks, I owe you three beers !
Giorgio 

Thanks for feedback regarding Voxkey.

There are dozens of documents accessible via the Windows menu. Start->All Apps->Multi Crew Experience.

Alternatively go to C:\Program Files (x86)\Multi Crew Experience\Doc\ folder and you'll find them there.

Some commands (like Gear, parking brake, COM radio tuning etc..) apply to all aircraft.

Other commands such as IRS control are only enabled when a supported aircraft that has them is detected.

See "AirbusA3XX_Commands.pdf" for Airbus related commands that apply to FSL A320, Aerosoft A320, Wilco A320 (and later BBS A320 when it's supported)

In general, we assume that users aren't going to bother reading documentation and try to come up with as many speech variations as possible.

Don't forget, as explained earlier, once you have spoken a command that comes to you naturally, and it's not accepted, you can still make it work by aliasing it to a built-in one.

So, in theory, should be able to use the same verbiage you're used to in Fs2crew and have more freedom to request other things as you see fit.

You can customize the checklist as well, if you're used to a different one.