Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

MCE and 747 QOTS II in FSX

Featured Replies

Hi

I have thebelow issues with QOTSII and MCE.

1. FO is not able to disengage auto pilot

2. Mechanic is not able to close cargo doors.

3. With GSX, when boarding completed, with the pmdg 777 the cargo doors are closed, but with 747 QOTS II, it does not happen.

4. When communicating with VATSIM controller, FO seems to listen in and starts pressing buttons. I have configured PTT button, this has started after I downloaded MCE version following QOTS II support.

 

Has anyone else experienced similar issues and and have or aware of a fix ?.

 

Thanks

Jeganathan Harishanker (YSSY)

i7-7700k @4.9GHz, ASUS Maximus IX Hero, 32 GB RAM @3200MHz, GA GTX 1080 G1, 2 x M.2 NVME Samsung EVO 256 GB, Kraken X61, 55" 4K TV @30Hz,  P3D v4.3, MCE, GSX, ASP4, FSUIPC, PMDG 747 v3 & 737 NGX, QW 787

  • Commercial Member
21 hours ago, ozflyer said:

Hi

I have thebelow issues with QOTSII and MCE.

1. FO is not able to disengage auto pilot

2. Mechanic is not able to close cargo doors.

3. With GSX, when boarding completed, with the pmdg 777 the cargo doors are closed, but with 747 QOTS II, it does not happen.

4. When communicating with VATSIM controller, FO seems to listen in and starts pressing buttons. I have configured PTT button, this has started after I downloaded MCE version following QOTS II support.

 

Has anyone else experienced similar issues and and have or aware of a fix ?.

 

Thanks

Items 1, 2, and 3 are confirmed and the fix is to download this zip file, unzip and replace "mcpmd74V2.dll" in \FSX\MCE dlls\ or/amd \Prepar3D\MCE dlls\ folder.

Download replacement dll here

As for the Vatsim bit, are you using a joysick button as PTT or something else?

Edited by FS++
Typo

  • Author
25 minutes ago, FS++ said:

Items 1, 2, and 3 are confirmed and the fix is to download this zip file, unzip and replace "mcpmd74V2.dll" in \FSX\MCE dlls\ or/amd \Prepar3D\MCE dlls\ folder.

Download replacement dll here

As for the Vatsim bit, are you using a joysick button as PTT or something else?

Thanks Gerald for the fix.

For PTT using a button on my CH eclipse yoke.

Jeganathan Harishanker (YSSY)

i7-7700k @4.9GHz, ASUS Maximus IX Hero, 32 GB RAM @3200MHz, GA GTX 1080 G1, 2 x M.2 NVME Samsung EVO 256 GB, Kraken X61, 55" 4K TV @30Hz,  P3D v4.3, MCE, GSX, ASP4, FSUIPC, PMDG 747 v3 & 737 NGX, QW 787

  • Commercial Member
19 minutes ago, ozflyer said:

Thanks Gerald for the fix.

For PTT using a button on my CH eclipse yoke.

You're welcome.

MCE can monitor the joystick directly via DirectX (Direct Input part).

There is no nee to emulate DEL or END key via FSUIPC programmed button.

Here is how to get MCE to mute all reco with Vatsim.

 

In "General" tab of the UI,, click <More Options> button

 

In "Advanced Options" panel, click <View Config>

mce.ini config file will open in Notepad.

Scroll down to the [GAMEPAD] section.

Leave whatever joystick name and button are listed there

Ensure "UseWithVoxAtc=1" and save the file.

De-activate the "talk to ATC controllers" in MCE UI and restart the app.

Next time you run MCE, when it sees that specific joystick button down, it will assume you're talking to some other ATC system, and will suspend all MCE speech reco until you release it.

 

 

  • Author
42 minutes ago, FS++ said:

You're welcome.

MCE can monitor the joystick directly via DirectX (Direct Input part).

There is no nee to emulate DEL or END key via FSUIPC programmed button.

Here is how to get MCE to mute all reco with Vatsim.

 

In "General" tab of the UI,, click <More Options> button

 

In "Advanced Options" panel, click <View Config>

mce.ini config file will open in Notepad.

Scroll down to the [GAMEPAD] section.

Leave whatever joystick name and button are listed there

Ensure "UseWithVoxAtc=1" and save the file.

De-activate the "talk to ATC controllers" in MCE UI and restart the app.

Next time you run MCE, when it sees that specific joystick button down, it will assume you're talking to some other ATC system, and will suspend all MCE speech reco until you release it.

 

 

Thanks Gerald

 

Will give it a go and report bask.

Cheers

 

Jeganathan Harishanker (YSSY)

i7-7700k @4.9GHz, ASUS Maximus IX Hero, 32 GB RAM @3200MHz, GA GTX 1080 G1, 2 x M.2 NVME Samsung EVO 256 GB, Kraken X61, 55" 4K TV @30Hz,  P3D v4.3, MCE, GSX, ASP4, FSUIPC, PMDG 747 v3 & 737 NGX, QW 787

  • Author
On 5/18/2017 at 6:43 PM, FS++ said:

Items 1, 2, and 3 are confirmed and the fix is to download this zip file, unzip and replace "mcpmd74V2.dll" in \FSX\MCE dlls\ or/amd \Prepar3D\MCE dlls\ folder.

Download replacement dll here

As for the Vatsim bit, are you using a joysick button as PTT or something else?

Hi Gerald

 

The DLL fixes autopilot and cargo doors, but now the FO does not handle flaps :-(

Flaps up or flaps down he does not execute.

Jeganathan Harishanker (YSSY)

i7-7700k @4.9GHz, ASUS Maximus IX Hero, 32 GB RAM @3200MHz, GA GTX 1080 G1, 2 x M.2 NVME Samsung EVO 256 GB, Kraken X61, 55" 4K TV @30Hz,  P3D v4.3, MCE, GSX, ASP4, FSUIPC, PMDG 747 v3 & 737 NGX, QW 787

  • Author

Please ignore sorted now.

 

Jeganathan Harishanker (YSSY)

i7-7700k @4.9GHz, ASUS Maximus IX Hero, 32 GB RAM @3200MHz, GA GTX 1080 G1, 2 x M.2 NVME Samsung EVO 256 GB, Kraken X61, 55" 4K TV @30Hz,  P3D v4.3, MCE, GSX, ASP4, FSUIPC, PMDG 747 v3 & 737 NGX, QW 787

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.