Hello all,

I appear to be getting a runtime error when trying to access the Monitor Tab of MCE. Clicking on OK immediately closes the application. So far, I have tried restarting MCE multiple times to no avail. I'm using MSFS 2020 and aircraft is the Flybywire A32NX Dev.

Thank you,

Nate

Alright, I seem to have solved it with a simple reinstall of the application but I'll keep an eye out for any further malfunctions.

Unfortunately, the problem has resurfaced... @FS++ would really appreciate if you could take a look at this!

Never came across such issue in more than 10 years MCE was on the market.

mce.exe is statically linked to the C++ library it needs (it has all the code to run on ANY Windows version, without needing to install any runtime), so won't have issues with C++ runtimes updates.

Since it's the monitor tab, only thing that comes to mind, perhaps a custom reference file that is out of shape and the custom data triggered a fault somehow.

Try with default FlyBwire livery and eventually, provide a link for downloading the specific livery you are operating.

Those occasionally cause glitches.

Would need to test with that livery. Thanks

 

 

On 5/17/2022 at 1:51 PM, FS++ said:

Never came across such issue in more than 10 years MCE was on the market.

mce.exe is statically linked to the C++ library it needs (it has all the code to run on ANY Windows version, without needing to install any runtime), so won't have issues with C++ runtimes updates.

Since it's the monitor tab, only thing that comes to mind, perhaps a custom reference file that is out of shape and the custom data triggered a fault somehow.

Try with default FlyBwire livery and eventually, provide a link for downloading the specific livery you are operating.

Those occasionally cause glitches.

Would need to test with that livery. Thanks

 

 

So, I got an update today for MSFS and the issue once again seems to be resolved. I can access the Monitor tab without any C++ runtime errors. I don't know if that solved it but here's the link to the livery as per your request: https://flightsim.to/file/24773/fbw320n-air-canada-8k-c-fzqs. In addition, I tried (today after the update) with the default livery for the A32NX and the default Asobo A320 and all seemed good and well!

@FS++ 

Unfortunately, the problem still persists. I've attempted multiple reinstalls of the software, reinstalling the Visual C++ libraries, uninstalling from Control Panel and then removing all directories associated with MCE in ProgramFiles, Documents, and AppData. I then attempt to reinstalling but alas, no joy. There are also other errors I'm receiving in MCE:

1. Mechanic recorded voice packs don't work. I get a dialog box that says something along the lines of "make sure the voice is installed correctly" when I've downloaded the voice pack from your website and ran the installer. I then get someone named Lee (or to something similar) instead of the installed voice. The default preinstalled voices such as Trav or Richard don't work either.
2. Checking the No Item Status Check in the checklists tab still allows my co-pilot to flip switches and such. Checklist items with a //2 or //3 flag are not read by my FO. 
3. The engine starter callouts and FMA are hit or miss; sometimes he comments (V1, 100 KIAS, etc.) but I don't hear them more often.

I really hope your team can get to the bottom of this as I thoroughly enjoy the software but frankly this is getting extremely frustrating.

Cheers,

Nate

10 hours ago, IcedOutN8 said:

@FS++ 

Unfortunately, the problem still persists. I've attempted multiple reinstalls of the software, reinstalling the Visual C++ libraries, uninstalling from Control Panel and then removing all directories associated with MCE in ProgramFiles, Documents, and AppData. I then attempt to reinstalling but alas, no joy. There are also other errors I'm receiving in MCE:

1. Mechanic recorded voice packs don't work. I get a dialog box that says something along the lines of "make sure the voice is installed correctly" when I've downloaded the voice pack from your website and ran the installer. I then get someone named Lee (or to something similar) instead of the installed voice. The default preinstalled voices such as Trav or Richard don't work either.
2. Checking the No Item Status Check in the checklists tab still allows my co-pilot to flip switches and such. Checklist items with a //2 or //3 flag are not read by my FO. 
3. The engine starter callouts and FMA are hit or miss; sometimes he comments (V1, 100 KIAS, etc.) but I don't hear them more often.

I really hope your team can get to the bottom of this as I thoroughly enjoy the software but frankly this is getting extremely frustrating.

Cheers,

Nate

Need more users to confirm the error on Monitor tab.

If it's happening after clicking the '?' and then the tab, it would trigger an audio explanation as to what you can do in that tab. And that would be using a TTS voice. The latter may be having issues if it's not the default Microsoft David voice. Just speculating.

After re-installing latest, I suggest you restore MCE to factory settings

Windows Start->Multi Crew Experience->Restore factory settings.

That will give you a fresh "mce.ini" in C:\Users\your_user_name\AppData\Roaming\Multi Crew Experience\ folder that is in synch with latest available options. This usually cures all the weird thigs happening.

Avoid manually deleteing files in MCE installation folder, as both license key and installed extra voice packs remain there when you update MCE which doesn't ship with all voices.

Resetting to factory settings will get rid of the message regarding missing voice as it would look for voices that ship in main package when it reads "mce.ini"

 

9 hours ago, FS++ said:

Need more users to confirm the error on Monitor tab.

If it's happening after clicking the '?' and then the tab, it would trigger an audio explanation as to what you can do in that tab. And that would be using a TTS voice. The latter may be having issues if it's not the default Microsoft David voice. Just speculating.

After re-installing latest, I suggest you restore MCE to factory settings

Windows Start->Multi Crew Experience->Restore factory settings.

That will give you a fresh "mce.ini" in C:\Users\your_user_name\AppData\Roaming\Multi Crew Experience\ folder that is in synch with latest available options. This usually cures all the weird thigs happening.

Avoid manually deleteing files in MCE installation folder, as both license key and installed extra voice packs remain there when you update MCE which doesn't ship with all voices.

Resetting to factory settings will get rid of the message regarding missing voice as it would look for voices that ship in main package when it reads "mce.ini"

 

To clarify some things:

It's not when I use the ? feature to explain a feature in the user interface. It's when I actually select the Monitor tab to view my takeoff data that I get the Visual C++ Error.

I only tried deleting folders manually after I started receiving all these problems with MCE. I always uninstall from Control Panel first, then remove all MCE related folders except for my custom VoxScript files, checklists, and LIC file. That still doesn't fix a things though.

I've tried using the Restore to Factory Settings wizard to no avail. In addition, I've tried using Run he App Wizard to see if that remedies anything but that didn't help either.

The only real consistent pattern I've notice with the software is, after a fresh install the Monitor tab will work for one or two flights but then somewhere down the line, will stop working and display the error along with MCE crashing to desktop. Copilot voice works (I use a Cereproc voice), but the mechanic voice doesn't save to my selection (even the three that ship with the application by default). My copliot won't ask for our takeoff runway but he used to when I first installed the software as a demo. I get no engine starter callouts but FMA callouts will work, and checklists and VoxScripts are read. The //2 or //3 flag doesn't work as my FO doesn't say his responses. The No Item Status Check checkbox (being enabled);  MCE will still challenge me and attempt to set the item and from my understanding it shouldn't as there are some items he will get "stuck" on.