1 hour ago, FS++ said:

Now in latest build.

Ignore the version listed on website. It's currently V2.7.6.6

Do I still need to download those 2 dlls then add NoCduAction=1 under [OPTIONS] in mcfslA3X.ini to avoid MCE playing with MCDU 2D windows?

Thanks.

13 hours ago, FS++ said:

Now in latest build.

Great! Thanks for all your hard work!

11 hours ago, Dirk98 said:

Do I still need to download those 2 dlls then add NoCduAction=1 under [OPTIONS] in mcfslA3X.ini to avoid MCE playing with MCDU 2D windows?

Thanks.

No, everything included in package. All dlls up to date

Option in ini will always remain there until you delete \Prepar3D v4\ installation folder.

Just remove previous version via Windows Control Panel, "add-remove programs", download, un\ip and run "InstallMCE". That's all you're expected to do.

On 6/16/2018 at 9:11 PM, FS++ said:

Now in latest build.

Ignore the version listed on website. It's currently V2.7.6.6

If the commands for those requests aren't accepted, feel free to post the kind of verbiage you'd be using and the speech grammar would be updated accordingly.

Right now, here are some variants. Words between parenthesis arte optional

Tell (the) controller we are on downwind

Advise (the)controller we are on downwind

Inform (the) tower we are on downwind

Replace "downwind" with "base leg", "left base", "right base", "final", "short final", or "long final" for other requests.

Thank you Gerald, all seems ok...Found just some little "glitches".

1/The Fo does not say "on final", she just says "Tower + call sign" however the tower answers "clear to land and so.....".

Only "on final" is missing. The downwind and base are ok.

2/On my side something I had noticed in previous versions with me talking to the tower, if I report "Tower Callsign on base" to the tower, Mce does not understand the sentence (it does not appear at the top left of the screen). Mce understands very well "Tower Callsign on downwind or on final" but not with "on base"...

3/If I can give a suggestion, would it be possible to add the sentence : speaking to the Fo "(please) report" : "base leg", "left base", "right base", "final", "short final", or "long final", "downwind" and so...?

Thank you again for the great work !

Regards,

Edited June 21, 20187 yr by DrumsArt

On ‎6‎/‎21‎/‎2018 at 2:02 AM, DrumsArt said:

Thank you Gerald, all seems ok...Found just some little "glitches".

1/The Fo does not say "on final", she just says "Tower + call sign" however the tower answers "clear to land and so.....".

Only "on final" is missing. The downwind and base are ok.

2/On my side something I had noticed in previous versions with me talking to the tower, if I report "Tower Callsign on base" to the tower, Mce does not understand the sentence (it does not appear at the top left of the screen). Mce understands very well "Tower Callsign on downwind or on final" but not with "on base"...

3/If I can give a suggestion, would it be possible to add the sentence : speaking to the Fo "(please) report" : "base leg", "left base", "right base", "final", "short final", or "long final", "downwind" and so...?

Thank you again for the great work !

Regards,

There you go.

 

Download this zip file

Unzip and replace 4 files inside \Multi Crew Experience\CandC\ folder.

Let us know if further tweaking is required.

 

Does this patch also adress this?

 

Quote

"... ready for departure" and "... requesting takeoff" are often misinterpreted as a request for a different runway. Maybe that can be fine tuned a little.

 

Edited June 23, 20187 yr by RALF9636

1 hour ago, RALF9636 said:

Does this patch also adress this?

 

 

If I ask "request take off/landing/taxi clearance", everything work(s) every time for me. Is that what you're talking about?

Regards,

1 minute ago, DrumsArt said:

If I ask "request take off/landing/taxi clearance", everything work(s) every time for me. Is that what you're talking about?

Regards,

 

I mean when I talk to ATC myself. Then it is often understood as a request for a different runway.

 

It works fine when I ask the FO to request takeoff.

 

14 minutes ago, RALF9636 said:

 

I mean when I talk to ATC myself. Then it is often understood as a request for a different runway.

 

It works fine when I ask the FO to request takeoff.

 

Ah ok...I noticed that the words "at holding point" are necessary in the sentence. It doesn't work for you either if you add those words?

Regards,

 

Edited June 23, 20187 yr by DrumsArt

Will try that in particular next time. Thanks!

 

11 minutes ago, DrumsArt said:

Ah ok...I noticed that the words "at holding point" are necessary in the sentence. It doesn't work for you either if you add those words?

Regards,

 

Do you also add "at holding point runway 36 Left" or just "at holding point"?

 

1 minute ago, RALF9636 said:

Do you also add "at holding point runway 36 Left" or just "at holding point"?

 

If I'm not mistaken, just "at holding point".

On 6/23/2018 at 7:35 PM, DrumsArt said:

If I'm not mistaken, just "at holding point".

After several flights and multiple attempts with different phrases I found that only one sentence always was recognized properly:

 

"Tower, <callsign> at holding point runway <runway number> is ready for departure".

 

"is" is essential here. Without the "is" it is recognized as a request for a different runway. Also other variations were not successful for me. When leaving out the runway number it also wasn't recognized most of the time.

 

11 hours ago, RALF9636 said:

After several flights and multiple attempts with different phrases I found that only one sentence always was recognized properly:

 

"Tower, <callsign> at holding point runway <runway number> is ready for departure".

 

"is" is essential here. Without the "is" it is recognized as a request for a different runway. Also other variations were not successful for me. When leaving out the runway number it also wasn't recognized most of the time.

 

Please write them down and the grammar will be checked to ensure they are covered.

We encourage everyone to do the same.

It's almost impossible to get Command and Control speech to cover every possible variation of natural speech. Despite updating them hundreds of times, maybe more.

And the structure is more complex than having a set of pre-made sentences to be recognized.

A speech rule would typically have part sentences that would combine to make full sentences, and it's difficult to spot all the possible "on", "is", "the" that the user might utter here and there.

Add that, the risk of putting too many variations that would bloat the grammar and make the speech engine work harder, sometimes not returning a successful recognition because it hesitated between 2 possible sentences that sound very close.

 

10 hours ago, FS++ said:

Please write them down and the grammar will be checked to ensure they are covered.

 

Tower, <callsign> (at holding point (runway <xxx>)) (is) ready for departure

where text in () should be optional.