Hello,

 

I "play" around MCE from few days. Great addon !

 

Some questions about the A300 and MCE :

 

1/ from time to time the CO or FE says randomly "lnav and vnav" !? :blink:

 

2/ the speed command seems not working. For example if I command "three hundred on speed" or any number, I can see the command wrote on screen, the CO acknowledges with the right answer, he says "done" but there is no change ! The altitude and heading commands work normally.

 

3/ On the A300 there are three positions for batteries : OFF, NORM and ON.

The script command "Battery number two (or three) normal" works

The same command with battery ONE is not recognized. The only command are on or off !

 

Thank you in advance,

 

Regards,

 

Richard Portier

Hello,

 

I "play" around MCE from few days. Great addon !

 

Some questions about the A300 and MCE :

 

1/ from time to time the CO or FE says randomly "lnav and vnav" !? :blink:

 

2/ the speed command seems not working. For example if I command "three hundred on speed" or any number, I can see the command wrote on screen, the CO acknowledges with the right answer, he says "done" but there is no change ! The altitude and heading commands work normally.

 

3/ On the A300 there are three positions for batteries : OFF, NORM and ON.

The script command "Battery number two (or three) normal" works

The same command with battery ONE is not recognized. The only command are on or off !

 

Thank you in advance,

 

Regards,

 

Richard Portier

 

Despite there being no SDK to interface this bird, all items are interfaced directly except for 3 items that use the keyboard.

 

Speed, heading and altitude are read directly from the sim, and then incremented or decremented relative to the current value using whatever keyboard combination you assigned to them.

 

Go to \Flight Simulator X\A300B4\Settings\ folder

 

Open "keyboard_settings.dat" using notepad.

 

What settings do you have for these items?

 

SPD increase key=Shift+Ctrl+Num_8

SPD decrease key=Shift+Ctrl+Num_9

 

If you have different assignments and they don't work, try the above.

 

Thanks for reporting the other two glitches. They will  be fixed in next update.

Whoa ! What support !!

 

This keys assignments for speed work like a charm. Thank you.

 

However I noticed a thing about altitude, heading and speed. When I command to set any of these bugs I have to ask two times to have the requested command. For example : speed bug is 290 ; I command 240 or any number ; CO sets it at +-237 ; I ask a second time 240 and I got it. An idea about ?

 

Thanks again,

 

Regards,

 

Richard Portier

I write here the following because it"s related to the Simcheck A300 and MCE. If it's a problem I can open a new topic.

 

1/During checklists the flight engineer (//4) does not recognize/acknowledge some answers like "SET", "Retracted", "Off".

The FO (//2) does not recognize/acknowledge some answers like "SET", "Armed".

 

When these responses are expected a red message is displayed on top of the screen "The command does not exist....etcetc". At this time MCE is waiting an answer. So, I must answer on behalf the flight engineer or the FO for continued the checklist.

 

2/Just to recall my previous post : (I had no answer about).

I noticed a thing about altitude, heading and speed. When I command to set any of these bugs I have to ask two times to have the requested command. For example : speed bug is 290 ; I command 240 or any number ; CO sets it at +-237 ; I must ask a second time 240 and I got it. An idea about ?

 

3/The DC voltmeter position command "dc meter position switch to Essential TR" don't work. I tried all the suggested words and syntax without success.

 

4/If I command "set flightdirector off" the FO switch it Off then On ! However no problem if I ask him to put it On.

 

5/A request : would it be possible please to have a specific and different formulation for "boarding" and "DEboarding" ? Simon often confuses the two !

 

MCE 2.5.6.2

 

Thank you in advance,

 

Regards,

 

Richard Portier

I write here the following because it"s related to the Simcheck A300 and MCE. If it's a problem I can open a new topic.

 

1/During checklists the flight engineer (//4) does not recognize/acknowledge some answers like "SET", "Retracted", "Off".

The FO (//2) does not recognize/acknowledge some answers like "SET", "Armed".

 

When these responses are expected a red message is displayed on top of the screen "The command does not exist....etcetc". At this time MCE is waiting an answer. So, I must answer on behalf the flight engineer or the FO for continued the checklist.

 

2/Just to recall my previous post : (I had no answer about).

I noticed a thing about altitude, heading and speed. When I command to set any of these bugs I have to ask two times to have the requested command. For example : speed bug is 290 ; I command 240 or any number ; CO sets it at +-237 ; I must ask a second time 240 and I got it. An idea about ?

 

3/The DC voltmeter position command "dc meter position switch to Essential TR" don't work. I tried all the suggested words and syntax without success.

 

4/If I command "set flightdirector off" the FO switch it Off then On ! However no problem if I ask him to put it On.

 

5/A request : would it be possible please to have a specific and different formulation for "boarding" and "DEboarding" ? Simon often confuses the two !

 

MCE 2.5.6.2

 

Thank you in advance,

 

Regards,

 

Richard Portier

 

1) Will check FE behaviour. As for FO, he's trying to simulated "spoilers armed". Since the command doesn't exist in the grammar, the message is displayed. A simple edit of the grammar file should fix it.

 

2)Neither me nor Ben had a chance to look at that. Sorry about that

 

3)With a closer look, should be fixable. We definitely have full control on any 3D switch.

 

4)same as above

 

5)I could be wrong, but I don't think "Deboarding" is supported. That's probably why Simon hears" "Boarding" instead. I guess will have to add it.

Edit: Deboarding is supported. It just happens that "boarding" related requests precede the "deboarding" ones. It's a case of speech engine falling for the first word that sounds like. Will put them the other way around.

 

By the way, the "battery one" selective switching is fixed. It will be in next update, no later than next Saturday. Hopefully most of the above issues will be ironed out by then.

As usual just Great Support !!

 

Thanks a lot,

 

Kind Regards,

 

Richard Portier

As usual just Great Support !!

 

Thanks a lot,

 

Kind Regards,

 

Richard Portier

 

While waiting for the update...

 

With regards the "Deboarding"...

 

Since my understanding you are a French user, here is one possible workaround.

Create a new script which should recognize say a French way to request boarding. "allez on debarque"

 

Since we are dealing with an English tuned speech engine, you'll need to use the English phonetics.

 

"alley on debark"

The above would be the script name

 

Then associate the new voice command to one of the existing English commands "despatch please start deboarding". (I am using “Despatch” because if the agent happens to be someone else, he’ll remind you to use the correct name. Despatch will work with any agent).

 

You can do that with many other things. The stumbling block is the use are the letter "u" and “i” which the English speech engine can't handle unless you speak them with an English accent.

 

If you get the message "command doesn't exist", just check the spelling of the English command you have written. Sometimes a missing "s" in a word would invalidate it.

 

The custom voice commands you create don’t need to use valid English words. As long as they sound like English, the speech engine will be happy.

 

It doesn't apply to French users only. Anyone who understands the limitations, could eventually talk in his native language.

 

In this case Voxscript is acting as an interpreter.

 

The English speech engine doesn't care whether the words are actually valid "English words". It's more about phonetics.

 

If you can speak French the way an Englishman would, you'll be successful for sure.

 

Equally, Germans should avoid the "u" with the umlaut (the two dots on top of the letter u).

Thank you Gerald for these clarifications.

 

I made a script with "Deboard please" and "Boarding please". It seems to work (no more confusion between the two actions) but I wrote in the answer for deboard the sentence "As you like sir" and for boarding "ok no problem". In the first case there is no answering but the deboard works like a charm. However in the second case the despacher answers "ok no problem" then launch the boarding process. May be I must change the sentence in the first case ?

 

Just for info I modified some scripts (for example open the fuel pump into the before pushback procedure instead of the preparation cockpit procedure). Also I made a "go around procedure" for the A300 (N1 button ON, syncronize the heading bug just in case, Vspeed button ON. gear up, flaps eight) it works well. By now it's just necessary to think to put Vspeed manually at 1500-2000ft/mn during approach.

 

In this regard when I ask verbally to the FO the "set two thousand on vertical speed" command, he acknowledges receipt but sometimes does it, sometimes (often) he does not it !? I don't understand why.

 

Regards,

 

Richard Portier

but I wrote in the answer for deboard the sentence "As you like sir" and for boarding "ok no problem".

 

The custom replies only work well with requests made to co-pilots because they have massive recording sets and can handle most of the Aviation related terminology. 

 

The situation is different for other crewmembers.

 

For example, don't expect the flight attendant to speak anything you type unless you have assigned a TTS voice as purser.

 

Same applies to mechanic.

 

Equally ramp agents don't have the ability to speak cutom sentences. The "Ok no problem" you heard is just part of the recorded stuff. Like when you ask ramp agent "Simon requesting catering" and you hear "OK will do" or "no problem I get it for you".

ok, I understand. Thank you.

 

Regards,

 

Richard Portier

ok, I understand. Thank you.

 

Regards,

 

Richard Portier

 

You're welcome.

 

Go ahead, download and install the latest and confirm all issues raised in this thread are no more.

 

http://www.multicrewxp.com/Downloads.html

 

Thank you

Hi Gerald,

 

Thank you very much for your great/fast work !

 

All is right excepted two things :

 

1/If "Lnav and Vnav" is no more pronounced by FO, I just realized that the problem was the "LAND" command. It's this command which was associated with the sentence "Lnav and Vnav". But the problem remains because the "Land" command is called erratically or more precisely it seems to be associated with my breathing ! Should I stop breathing   :lol: ! Seriously I do not see how to get around this problem. For info it's the only command that seems to react this way.

 

2/About the checklist the issue remains for the "Set/Off" answer.

 

In the cockpit preparation :

In this checklist all is ok except the [ ] Cabin pressure  -- Set //4. I must answer on behalf the FE for continued the checklist.

 

The same with the Before or pushback checklist and in every checklists with Set, Off associated with FE or FO : [ ] Fuel System  -- Set //4 and also the [ ] Center fuel pumps -- Off //4 in the Before TO Checklist answer

 

Same issue with the CO : [ ] Transponder  -- Set //2

 

Anyway if it's not possible to solve that I can replace these answers with "Checked" or "As required"

 

Again big thanks.

 

Regards,

 

Richard Portier

 

 

Anyway if it's not possible to solve that I can replace these answers with "Checked" or "As required"

 

Leave that as a last resort.

 

Will do something about it within 2 weeks.

 

Thanks for your patience.

 

 

The same with the Before or pushback checklist and in every checklists with Set, Off associated with FE or FO : [ ] Fuel System -- Set //4 and also the [ ] Center fuel pumps -- Off //4 in the Before TO Checklist answer

 

Should be sorted in latest package

 

http://www.multicrewxp.com/Downloads.html

 

The latest also adds support for CS 777

Hi,

 

I reopen this topic because I think it's more confortable to have a topic for each plane.

 

So, the "Brake Fan" command does not work anymore. I ignore which version since it no longer works because I recently reinstalled MCE with a new computer.

 

On another subject I tried the ATC function. Whoa, it's great ! However, after some time the ATC window closes and/or opens when I press the radio button (del key). For info I need this window with text. It's more confortable for me to be more familiar with the ATC.

 

FSX Acceleration MCE Version 2.5.82

 

Thank you in advance

 

Regards,

 

Richard Portier