Hi,

I used MCE in FSX and P3D and got it now successfully working in MSFS. Interaction wirh the co pilot works nice, but I cannot interact with ATC for some reason… I’m using the same terminology and same speech training profile as in my P3D setup and there ATC is working nicely. 
Did I miss smth in MSFS? My UI language in MSFS is english. The command „select two“ also works and the second entry in the ATC window is selected. But there is no reaction e.g. to „ground, ABCDE request taxi“. I hold down the DEL key and can also hear the radio beep sound. 
Any help is welcome. Thanks in advance,

michael

2 hours ago, Waldkauzi said:

Hi,

I used MCE in FSX and P3D and got it now successfully working in MSFS. Interaction wirh the co pilot works nice, but I cannot interact with ATC for some reason… I’m using the same terminology and same speech training profile as in my P3D setup and there ATC is working nicely. 
Did I miss smth in MSFS? My UI language in MSFS is english. The command „select two“ also works and the second entry in the ATC window is selected. But there is no reaction e.g. to „ground, ABCDE request taxi“. I hold down the DEL key and can also hear the radio beep sound. 
Any help is welcome. Thanks in advance,

michael

Since you're already familiar with the process, I guess might be to do with MSFS erasing the call-sign and the need to type it every time you start the sim.

It's very important because it affects which ATC speech grammar is loaded, based on whether you're flying an airliner (with call signs such as "United 437") or GA traffic (with call-sign such as "Cessna Novenmber Tango Mike").

Otherwise, speech engine won't be able to match anything you said to the MCE ATC speech rules stated in the speech grammar.

Unlike with P3D or FSX, with MSFS, besides ensuring call-sign has been entered (and hopefully next Asobo SU 6 update ensures it stays put), DO NOT start MCE until aircraft is on tarmac ready to fly (i.e. not during the flight setup process).

There are a few checks you can perform. Ask co-pilot "confirm call-sign", "confirm ATC options". Should get verbal feedback accordingly.

Keep us informed.

 

 

Edited October 7, 20214 yr by FS++

Thanks for the feedback. The co pilot correctly reads my call sign if I ask „what is our call sign“. But I always started MCE before the plane was ready to fly, so I will try this later and gibe you feedback. 

Unfortunately the issue is still there. What I did:

- Start MSFS
- Select standard airplane (C172 with G1000) and standard airport
- define a call sign
- wait until sim is running and engines of the C172 are running
- now start up MCE; MCE correctly identifies the airplane and the call sign if I say "what is our call sign"
- co pilot is working as expected, e.g. I can ask him "landing lights on" and the lights are correctly activated
- when I now hit the DEL key to talk to the ATC and I say "ground, D-ABCD request taxi" my call is recognized correctly by MCE (the correctly recogniced text is showen in red letters top left on the screen) but nothing else happens; the according command in the ATC is not selected....
- if I ask the co poliot to "select two" the according entryis selected correctly in the ATC list
- one thing that is maybe related: if I ask the co pilot "tune ground on comm one" or "set comm one to 121.75" that is not working; the co polit is saying something like "nothing to do here" or so....

Maybe also relevant is ma setup: On my PC I have two users, one with admin rights and one with standard. The admin account is set to english language and there MCE is installed and the speech training was done. MSFS is installed in the standard user account and I'm running MSFS and MCE from there. That account is set not to english language (in fact to german), the UI of MSFS is set to english language. But basically that setup works for the co pilot (and it also worked for FSX/P3D, also the ATC).

Any further ideas what goes wrong on my machine? Or is it simply my bad spelling and/or false ATC terminology? ;-)

Thanks,

Michael

1 hour ago, Waldkauzi said:

Unfortunately the issue is still there. What I did:

- Start MSFS
- Select standard airplane (C172 with G1000) and standard airport
- define a call sign
- wait until sim is running and engines of the C172 are running
- now start up MCE; MCE correctly identifies the airplane and the call sign if I say "what is our call sign"
- co pilot is working as expected, e.g. I can ask him "landing lights on" and the lights are correctly activated
- when I now hit the DEL key to talk to the ATC and I say "ground, D-ABCD request taxi" my call is recognized correctly by MCE (the correctly recogniced text is showen in red letters top left on the screen) but nothing else happens; the according command in the ATC is not selected....
- if I ask the co poliot to "select two" the according entryis selected correctly in the ATC list
- one thing that is maybe related: if I ask the co pilot "tune ground on comm one" or "set comm one to 121.75" that is not working; the co polit is saying something like "nothing to do here" or so....

Maybe also relevant is ma setup: On my PC I have two users, one with admin rights and one with standard. The admin account is set to english language and there MCE is installed and the speech training was done. MSFS is installed in the standard user account and I'm running MSFS and MCE from there. That account is set not to english language (in fact to german), the UI of MSFS is set to english language. But basically that setup works for the co pilot (and it also worked for FSX/P3D, also the ATC).

Any further ideas what goes wrong on my machine? Or is it simply my bad spelling and/or false ATC terminology? 😉

Thanks,

Michael

Because MCE doesn't want to hit ATC options by accident, before any selection is made, it checks the content of the menu. And this is why MSFS user interface language MUST be set to English-US, otherwise options would be in other languages for which MCE isn't prepared.

For instance, when you say "Tower Cessna Delta Bravo Charlie is ready for takeoff", even though the speech will be recognized and displayed, no menu selection takes place unless there is the expected "request takeoff clearance from XXXX" somewhere in the options list.

Ask co-pilot "confirm ATC options" and a TTS voice should spell out the content of the window at any time. Unless that happens, no woder it doesn't work as expected.

No need to run ANY sim as administrator. And you can rule out speech recognition.

 

Ah OK I tired the "confirm ATC options" and my co pilot responds with "No ATC options available yet". So MCE somehow cannot read the ATC window. As explained before the UI of MSFS is set to english. Could it be a problm that my Windows OS language is set to german?

Btw, during startup of MCE I get the following warning: "Failed to locate Voxkey Commands profile! Custome commands will be ignored for this session."...not sure if this is related? I'm not using any Voxkey commands.How can I get rid of that message?
 

3 hours ago, Waldkauzi said:

Btw, during startup of MCE I get the following warning: "Failed to locate Voxkey Commands profile! Custome commands will be ignored for this session."...not sure if this is related? I'm not using any Voxkey commands.How can I get rid of that message?
 

Usually caused by a corrupted profile. To revert to default, go to \My Documents\ folder and delete the <Voxkey> folder.

Next, run the app wizard briefly, without going through speech training. You'll get a new healthy folder with default settings.

Regarding ATC options...

I think you're right. Might be to do with the other account being a restricted user. Set it as admin account and it should work, even without running MSFS as admin..

THanks for the help.  ATC is now working for me. What I basically did: Unistall MCE completely, set my Standard account to be a admin account and install MCE there. That means the Windows account where you run MSFS and MCE has to be a Admin account, right? That's not 100% perfect for me (for security reasons a standard account is saver than admin) but I can live with that...I don't want to miss MCE 🙂

I would be great if you could add an according note to your installation manuals. Additionally I was shortly confused regarding the language settings, because on a non-english Windows you have to change the OS language to English in order to run the app wizard and the speech training. After that you can switch back to you native language settings (but keep the speech recognition lamguage to eng).

Beside of that MCE is a great tool and I don't want to fly without it. Thanks for you fast and great support here in the forum!

 

Edited October 14, 20214 yr by Waldkauzi
fixed typos

On 10/14/2021 at 2:39 PM, Waldkauzi said:

THanks for the help.  ATC is now working for me. What I basically did: Unistall MCE completely, set my Standard account to be a admin account and install MCE there. That means the Windows account where you run MSFS and MCE has to be a Admin account, right? That's not 100% perfect for me (for security reasons a standard account is saver than admin) but I can live with that...I don't want to miss MCE 🙂

I would be great if you could add an according note to your installation manuals. Additionally I was shortly confused regarding the language settings, because on a non-english Windows you have to change the OS language to English in order to run the app wizard and the speech training. After that you can switch back to you native language settings (but keep the speech recognition lamguage to eng).

Beside of that MCE is a great tool and I don't want to fly without it. Thanks for you fast and great support here in the forum!

 

Normally, one would need a user account with admin rights in order to install MCE in the first place, therefore not a common issue.

You raised a good point with regards the need to temporarily switch regional settings to English US in order to run speech training. I guess this would have put off some users (non-English based systems) going through the Demo and wondering why speech training isn't working and treating it as software failure. Time to do something about it. Thanks for the reminder.