On some relevant note, there is prolonged delay and period of MCE non-responsiveness at the beginning, right before the ground mechanic speaks for the first time.

 

Is there anything showing on the communication bar? Delays for me are while the program is scanning the aircraft I have active, so it can ascertain status, what the MVP says, etc...it takes a little while and the we are good to go.

If you have installed the PMDG 600-700 series too, make sure you install the separate Sp1C.

I don't have the 600-700 package but my 800-900 is all up to date and runs flawlessly.

 

What you desribed with heading, altitude, or speed can happen when the cockpit is cold and dark.

 

The values you see on MCE may not be the ones held in the internal variables. MCE typically reads those values then increments or decrements them. Next time when in cold and dark,when altitude is showing 10000 and speed 100, try to manually change the values and see what happens. You will notice the whole panel will go dark.

Sorry yes that would have happened when i was just dddling and trying to get a response from the F.O. It was geting late last night

 

Look at the audio icon in system tray(bottom right of the screen). Click on "Mixer", and you will see a volume slider for each running application. Make sure the MCE slider isn't set to near zero. That would explain why you can't hear the FO.

No problem there

 

Gerald i can almost guarantee that there is no problem with volume or "me" speaking to MCE. the red text confirms that MCE can hear me.

 

The problem hear is getting MCE to wake up and start talking back.

 

As i mensioned Yesterday, once you wake the F.O. up he starts talking and doing as he is told. Ihave now started a cold and dark flight, Just to see if i can get to the taxi stage and have done it.

 

What i have to do is bring up a "Cold & Dark" situation and then before i do any thing, you bring up the FSX ATC dialog and find out what the ground frequency is. Then ask the F.O. to tune the COM-1 to that frequency and he will respond with ok....or whatever and does this.

 

Now this is the trigger that wakes him up, so then i ask him to perform the "Pre Flight Overhead Procedure" and away we go. At least the last two test runs it has worked.

 

Gerald, for some reason MCE doesn't want to respond until i wake it up or something is stopping it.

 

Regards,

 

Rick,

 

The flows for the NGX are silent in the preparation, but you can change that so you know what he is doing, simply go to command then select voxscrirpt, find the flow you wish to amend, hit "edit" , on the next screen put a tick on "verbose", save it and away you go

Thanks Will. I will do that.

Update: Ok, I have gone through from cold and dark to taxi 3-times without a hitch.

 

For sure the answer lies in that PTT button. With FSX ATC enabled, the first thing i do is hit that button, which brings up FSX ATC dialog. Close it again (i don't even have to tune anything) and away we go without a hitch (including GSX ground services).

 

If i don't hit that button initially: Nothing.

Update: Ok, I have gone through from cold and dark to taxi 3-times without a hitch.

 

For sure the answer lies in that PTT button. With FSX ATC enabled, the first thing i do is hit that button, which brings up FSX ATC dialog. Close it again (i don't even have to tune anything) and away we go without a hitch (including GSX ground services).

 

If i don't hit that button initially: Nothing.

 

 

Aha, that’s a good hint.

 

The PTT definitely plays a crucial part.

 

In order to manage the thousands of available voice commands, when you hold the PTT button down, all commands for talking to FO are suspended, checklist commands are suspended, UI voice control is suspended and ATC commands are made active. The opposite happens when you release the button.

 

This means that an unreliable joystick button could occasionally register as down, causing MCE to suspend the main interaction with FO.

 

I guess by hitting it, you are causing it to pop-up from the accidental “pressed position”.

 

If you can, try assigning another joystick button. MCE will only listen to buttons 1 to 12

If you can, try assigning another joystick button. MCE will only listen to buttons 1 to 12

 

Thanks Gerald, Yes that one came to mind. I will try moving the assignment around to different buttons to see if that does it. I don't want to put it back on the Keyboard, because i don't wan't to stretch over my Yoke every time i use ATC and is a real pain when TrackIR is active.

Thanks Gerald, Yes that one came to mind. I will try moving the assignment around to different buttons to see if that does it. I don't want to put it back on the Keyboard, because i don't wan't to stretch over my Yoke every time i use ATC and is a real pain when TrackIR is active.

 

You're welcome.

 

Affirmative, just assign a different button and the previous one will be ignored even if it gets stuck down permanently.

 

Another thing users should be aware of...

 

There are 2 keyboard keys reserved for people eager to use MCE on VatSim. In order to avoid situations where FO tries to interpret online chatter as commands to him to perform things, whenever the <SPACE> or <END> (the <SPACE> key can be changed if necessary) keyboard keys are held down, MCE will suspend all speech recognition.

 

Therefore, if users have joystick buttons set to emulate the above keys via FSUIPC macros for example, they need to be aware of the implications.

There are 2 keyboard keys reserved for people eager to use MCE on VatSim. In order to avoid situations where FO tries to interpret online chatter as commands to him to perform things, whenever the or (the key can be changed if necessary) keyboard keys are held down, MCE will suspend all speech recognition.

 

Therefore, if users have joystick buttons set to emulate the above keys via FSUIPC macros for example, they need to be aware of the implications.

 

Thats important information Will. Do you think it deserves a sticky?

You're welcome.

 

Affirmative, just assign a different button and the previous one will be ignored even if it gets stuck down permanently.

 

Another thing users should be aware of...

 

There are 2 keyboard keys reserved for people eager to use MCE on VatSim. In order to avoid situations where FO tries to interpret online chatter as commands to him to perform things, whenever the <SPACE> or <END> (the <SPACE> key can be changed if necessary) keyboard keys are held down, MCE will suspend all speech recognition.

 

Therefore, if users have joystick buttons set to emulate the above keys via FSUIPC macros for example, they need to be aware of the implications.

 

Here's my problem with changing button assignments for the PTT button in MCE, you can't get it to assign to anything other than BUTTON #11, hence now i know why i was assigned to my button #12 yet the panel said #11, because no matter how many times i change the assignment to lets say, button #7, it will not change and the MCE control panel just consistently shows #11.

I have even tried changing in the MCE.ini file, but it still just revert's back. So i used FSUIPC, which is probably one of the problems, if not the problem in my case.

 

So my question is How do you change that darned PTT button assignment in MCE?????

 

Regards,

So my question is How do you change that darned PTT button assignment in MCE?????

 

 

Based on feedback from users, it appears some Saitek joysticks have some buttons in the “always on” position.

 

Some CH controllers have those too, that’s why MCE only considers the first 12 buttons.

 

When trying to set the PTT button and it seems to always revert to the same unwanted button, you are in the above scenario.

 

The workaround is to edit the mce.ini under C:\Users\your_user_name\AppData\Roaming\Multi Crew Experience\mce.ini.

 

Look at the [GAMEPAD] section.

 

Leave the “JoyManID” and “JoyProdID” as they are, and only change the “JoyButton” to a value between 1 and 12 (set it to the button ID you think matches the joystick button).

 

You can later (when running MCE with the sim) check you have selected the correct button by paying attention to the background noise constantly played in the background while the assigned PTT is held down.

 

Only snag, if you restore to factory settings, you would have to do that again.

 

After that, MCE will ignore the “always on” buttons and will only consider the selected button as a trigger for PTT.

Well finally I appear to have solved the problem. In my last post i was using button #7 as an example, but in fact it turns out to be the only available button on my controllers that will replace #11 and stay without MCE changing it back and rewriting back to button #11 in the MCE.ini file.

 

I do still have to use FSUIPC as well though, because there is no other way of emulating a key being held down. However, their does not seem to be a problem as long as i can use a button matching that set in the MCE control panel.

 

I have now got MCE & GSX doing everything right and i can't shut my F.O. up.

 

Gerald & Will, thanks for your help and patience.

 

Who would have thought a simple PTT button could caused so much trouble.

 

Regards,

Who would have thought a simple PTT button could caused so much trouble.

 

Indeed.

 

Makes you wonder how many could have missed out on the Demo because of that.

 

Anyway, I'm sure it will benefit others.

 

Cheers,

Hey i am getting this error again and again... any ideas how to fix this?-

https://drive.google.com/file/d/1U_I-pkPeFwEywXHyA3qfbuIjoQgNVuyc/view?usp=sharing

please help me asap!

I did everything as mentioned, but still it is not getting fixed!

51 minutes ago, Neil_Kerman said:

Hey i am getting this error again and again... any ideas how to fix this?-

https://drive.google.com/file/d/1U_I-pkPeFwEywXHyA3qfbuIjoQgNVuyc/view?usp=sharing

please help me asap!

I did everything as mentioned, but still it is not getting fixed!

It appears you have FSX boxed edition. Please make sure you set "fsx.exe" to run as administrator.

Right-click "fsx.exe".

Select "properties" in drop-down menu

Go to <Compatibility> tab and enable option "Run this program as administrator".

If using a launcher app to start FSX (SimStarter), also set that application tom run as admin

If Windows UAC is enabled, and you don't have to disable it, you must install MCE to default C:\Program Files (x86)\Multi Crew Experience\ folder.

If still no-go, reset MCE to factory settings

Start->All Apps->Multi Crew Experience->Restore factory settings.

 

27 minutes ago, FS++ said:

It appears you have FSX boxed edition. Please make sure you set "fsx.exe" to run as administrator.

Right-click "fsx.exe".

Select "properties" in drop-down menu

Go to <Compatibility> tab and enable option "Run this program as administrator".

If using a launcher app to start FSX (SimStarter), also set that application tom run as admin

If Windows UAC is enabled, and you don't have to disable it, you must install MCE to default C:\Program Files (x86)\Multi Crew Experience\ folder.

If still no-go, reset MCE to factory settings

Start->All Apps->Multi Crew Experience->Restore factory settings.

 

i did all these before, but as you have said i repeated it once more but its still not working. I am getting depressed, i want this at any cost!

2 hours ago, Neil_Kerman said:

i did all these before, but as you have said i repeated it once more but its still not working. I am getting depressed, i want this at any cost!

Suggest you re-enable Windows UAC (2 notches up the slider and restart PC).

Go to \Flight Simulator X installation folder and check you have...

fsInsider.dll 

fsInsider.ini

A folder named <MCE dlls> folder, with many dlls inside it (about 40).

Barring that, make sure you have installed FSX SP1 followed by SP2 for the FSX boxed version (not required for FSX Steam Edition). Here are the download links

SP1: https://www.microsoft.com/Products/Games/FSInsider/downloads/Pages/FlightSimulatorXServicePack1.aspx

SP2: https://www.microsoft.com/Products/Games/FSInsider/downloads/Pages/FlightSimulatorXServicePack2.aspx