Hello there,

MCE looks to start OK, but quits after initialization. Have done the wizard again, but no luck. No changes in anti-virus software etc.

• Connecting to FS: ok
• Wait for FO to Board the plane: OK
• Looking for changes to current plane: OK
• The UI interface disappeared at I believe this stage. It was just a blank screen
• Messsage MCE ready to go: OK
• 2 seconds later: Crew is leaving the plane - see you next time

Today I have installed a new memory bank into my PC. Did that change the machine code?

Hope you can help me.

Regards,

Daniel

I also had problems with ver 2.9.0.7. Connected as usual on p3dv5.1 but had red info text stuck on in top left (GPU memory, FPS etc) and mce wouldn't operate any switches (flying pmdg 777).

Tried uninstalling/reinstalling but only fix was reverting back to ver 2.9.0.0 and all is good again.

 

Hope this helps.

 

Regards,

Shane Burrows

P3D v5.1

 

Thanks for feedback Guys.

Did you patch the installation or did a full un-install and re-install of latest released version yesterday?

I have done a full un-install and re-install today

PS: I tried it with a few planes as I thought FBW mod was causing it at first, but also happened with Asobo A320 and Cessna 172

23 minutes ago, danbaz said:

I have done a full un-install and re-install today

PS: I tried it with a few planes as I thought FBW mod was causing it at first, but also happened with Asobo A320 and Cessna 172

OK, just in case, it's possible after adding memory modules you wanted to check the memory status using debugging tools or things like that. This may cause MCE to bail out. Adding memory doesn't ivalidate the key. It would be silly to do that.

Shutdown other apps and try again.

Confirm "mce.exe" and "Simco64_Ldr.exe" versions in \Multi Crew Experience\ installation folder.

 

Thanks for the clarification as I do not know what makes the machine code change.

I have run Windows Memory Diagnotic Tools last week a lot and PassMark Performance test today, but not while running the sim.

No other apps than the ones normally are running, were running now too.

Both files are present.

Windows Event Viewer said this:

Faulting application name: mce.exe, version: 2.9.0.7, time stamp: 0x6054cbe9
Faulting module name: mce.exe, version: 2.9.0.7, time stamp: 0x6054cbe9
Exception code: 0xc000041d
Fault offset: 0x0018443c
Faulting process id: 0x53c
Faulting application start time: 0x01d71dafaae5f8f5
Faulting application path: C:\Program Files (x86)\Multi Crew Experience\mce.exe
Faulting module path: C:\Program Files (x86)\Multi Crew Experience\mce.exe
Report Id: adf048e1-8c1d-4167-a381-de7355af147c
Faulting package full name: 
Faulting package-relative application ID: 

 

We set debug=1 to provide more details:

18:50:16:92 -Initialized global variables
18:50:16:101 -COM initialization Successful
18:50:16:352 -Application cleared to start
18:50:16:370 -Loaded application settings from ini file
18:50:16:383 -Loaded language resources
18:50:19:431 -Successfully created application window
18:50:19:552 -Voice created successfully
18:50:19:570 -Assigned voice
18:50:19:582 -Assigned voice
18:50:19:597 -Assigned voice
18:50:19:617 -Assigned voice
18:50:20:936 -Assigned voice
18:50:21:75 -Successfuly created Recognizer
18:50:21:94 -Successfully created user interface objects
18:50:27:138 -Detected Running Flight Simulator!
18:50:27:155 -Retrieved all aircraft config files
18:50:27:169 -Checked current aircraft position and status.
18:50:29:855 -Looking for aircraft related paths
18:50:29:935 -Setting OPS data for current airport!
18:50:30:248 -Finished setting OPS data for current airport
18:50:30:263 -Getting data from reference file!
18:50:30:311 -Finished getting data from reference file
18:50:30:327 -Adjusted settings to current aircraft
18:50:32:344 -Initializing Relevant FO
18:50:32:360 -Looking for FO name
18:50:32:376 -Found FO name
18:50:32:392 -Initialized First Officer!
18:50:32:408 -Thread waiting for speech engine to update
18:50:32:424 -Thread finished waiting for SR update

 

7 minutes ago, danbaz said:

We set debug=1 to provide more details:

18:50:16:92 -Initialized global variables
18:50:16:101 -COM initialization Successful
18:50:16:352 -Application cleared to start
18:50:16:370 -Loaded application settings from ini file
18:50:16:383 -Loaded language resources
18:50:19:431 -Successfully created application window
18:50:19:552 -Voice created successfully
18:50:19:570 -Assigned voice
18:50:19:582 -Assigned voice
18:50:19:597 -Assigned voice
18:50:19:617 -Assigned voice
18:50:20:936 -Assigned voice
18:50:21:75 -Successfuly created Recognizer
18:50:21:94 -Successfully created user interface objects
18:50:27:138 -Detected Running Flight Simulator!
18:50:27:155 -Retrieved all aircraft config files
18:50:27:169 -Checked current aircraft position and status.
18:50:29:855 -Looking for aircraft related paths
18:50:29:935 -Setting OPS data for current airport!
18:50:30:248 -Finished setting OPS data for current airport
18:50:30:263 -Getting data from reference file!
18:50:30:311 -Finished getting data from reference file
18:50:30:327 -Adjusted settings to current aircraft
18:50:32:344 -Initializing Relevant FO
18:50:32:360 -Looking for FO name
18:50:32:376 -Found FO name
18:50:32:392 -Initialized First Officer!
18:50:32:408 -Thread waiting for speech engine to update
18:50:32:424 -Thread finished waiting for SR update

 

Thanks.

It shows unfinished startup process.

Be aware, with MSFS it is also relyng on "Simco64_Ldr.exe" doing its job.

Latest should be V1.0.5.5

Eventually, go to Windows task manager and check "Simco64_Ldr.exe" isn't stuck and perhaps still running. Kill it in <Processes> list and try again.

after you start MCE, the other process should pop-up in <Processes> list.and should only disappear when MCE shuts down.

 

 

We renamed the MCE folder in documents, then have re-run the wizzard, then we started MSFS again, then we started MCE, which said it was already running.

Then we killed MCE and then re-started MCE. It worked.

Not sure what caused all this, but glad it works..

 

Thanks for the help!

18 minutes ago, danbaz said:

We renamed the MCE folder in documents, then have re-run the wizzard, then we started MSFS again, then we started MCE, which said it was already running.

Then we killed MCE and then re-started MCE. It worked.

Not sure what caused all this, but glad it works..

 

Thanks for the help!

OK, good.

If you also had to delete <Voxkey> folder in \My Documents\ folder, I am guessing, perhaps some damaged Voxkey profile caused it.

The wizard recreates a fresh folder with healthy profiles and default settings.

Today I have renamed the old folder to make it the active one again and MCE started just fine, so it seems the Voxkey profile was not the cause.

To see if I could trigger the issue again, I have done clean install, then the wizard. MCE started just fine, but there were no longer any Voxscripts for the Asobo aircraft. I have found those files in the installation files, so I could copy them over, if I wanted to.

Anyway, it is working again. Thanks again for the help.

Daniel

28 minutes ago, danbaz said:

Today I have renamed the old folder to make it the active one again and MCE started just fine, so it seems the Voxkey profile was not the cause.

To see if I could trigger the issue again, I have done clean install, then the wizard. MCE started just fine, but there were no longer any Voxscripts for the Asobo aircraft. I have found those files in the installation files, so I could copy them over, if I wanted to.

Anyway, it is working again. Thanks again for the help.

Daniel

The flows in installation folder are there as backup in case the modified ones (in \My Documents\ folder) are screwed.

When you run the wizard, it should recreate those folders and copy flows to them, unless it finds flows with the same name, in which case it assumes user has edited them and doesn't overwrite them.

From experience, most issues are related to overriding folders permissions, system folders moved to a different location, or other accounts on same machine taking ownership of specific folders..

This may cause Windows to deny the wizard, programmatically copy and paste operation or even folder creation task.

See these theads for weird things that may happen when user tries to take control of the m,achine a la Windows XP or Vista.

 

 

 

 

Gerald,

When trying to install new MCE 2.9.0.7, MCE will not connect to FSX. Receiving MCE error message "Could not retrieve FS data! Try restarting FS9, then MCE". I've never owned or installed FS9.

I uninstalled ver 2.9.0.0 before installation. This is the first time that the installation has gone totally haywire. fsInsider.dll and fsInsider.ini are both in the root folder of FSX. Also after installation the  wizard started to redo all the settings, such as headset, voice training and such. 

 

Any help is appreciated.

Tony J

 

10 hours ago, Fighter Guy said:

Gerald,

When trying to install new MCE 2.9.0.7, MCE will not connect to FSX. Receiving MCE error message "Could not retrieve FS data! Try restarting FS9, then MCE". I've never owned or installed FS9.

I uninstalled ver 2.9.0.0 before installation. This is the first time that the installation has gone totally haywire. fsInsider.dll and fsInsider.ini are both in the root folder of FSX. Also after installation the  wizard started to redo all the settings, such as headset, voice training and such. 

 

Any help is appreciated.

Tony J

 

You never need to redo spech training following an update. Speech profile is managed by Windows and is only lost when you delete user account or format C drive.

Wizard is expected to edit "dll.xml" file which tells FSX to load "fsInsider.dll". Otherwise, won't get any data from the sim.

Go to C:\Users\yiur_user_name\Appdata\Roaming\Microsoft\FSX\ folder and open "dll.xml"

Should see the following lines.

<Launch.Addon>
        <Name>Multi Crew Experience</Name>
        <Disabled>False</Disabled>
        <ManualLoad>False</ManualLoad>
        <Path>fsInsider.dll</Path>
    </Launch.Addon>

If missing it's an indication that you may have altered "Users" folders permissions causing Windows to deny the wizard, permission to edit files or things like that. In that case, manually add them right before the lat line

</SimBase.Document>

Gerald,

 

I checked the dll.xml file, and it indicates exactly what you have stated. There has been no changes in my system prior to the installation of 2.9.0.7. The last windows update on my system was 15 Mar. I performed an image backup on the 19th prior to installation and that was the last time I flew and everything was working correctly.  However I'm still receiving error messages about FS9, which I don't own and has never been on my computer .

 

Tony J