LH067U

Many thanks. The Simco64_Ldr.exe was the game changer. Now everything is fine again. I hope that a future update will run fine as well. Thanks for your brilliant support LH067U

Fenix is default aircraft on startup with default livery Re-installed MCE with version 3.0.20 Same pop up appears again and again. MCE not working. Tried spawning at gate or active runway. No chance to get it working properly.

Hi guys, after updating to the latest MCE is driving me crazy. Everytime when the Fenix A320 (set as default) has completely loaded up, fed with all data and ready to go I start MCE. It automatically arms spoilers for any reason, initialisation progress continues and steps back to MSFS2020 option page. Everytime it is said that it can only be working correctly after a restart of the flight. Shutdown of MCE and flight reloaded. Done. Same message pops up again and again and MCE is not working. Has worked under previous build number! MCE is set to admin mode and everything is on latest. Just gave another try with re-installed FSUIPC registered but not running. CTD Any ideas out there? LH067U

When MSFS2020 / FSUIPC and Tobii are running ... everything is fine. Head movements are stable (even in SU10 Beta) and the full immersion is amazing. The conflict starts after MCE has launched, initialized and the ramp agent did his annoncement. Head movents are stopped and bring me back to cockpit view. Manually head movements are only possible by using the assigned joystick button. Disableing / Enableing Tobii has not effect. WASM Module: there is not anything like that. Simconnect: Tobii support refers to Asobo. simconnect.xml shows nothing about Tobii and I can't find out which port they are using in case of interacting via simconnect. The key assignment had been done but even by pressing the assigned key Tobii is not working again when MCE is running. Complete restart without MCE ... everything is fine.

You can prevent the pop-up by reloading the plane and before you start MCE. ... I always load up my planes and do all preps. Then MCE is loaded. I suggest you un-install FSUIPC and just leave the <fsuipc-lvars-module> in \Community\ folder. That way, any app that relies on FSUIPC main program will stop working. ... am I right that you really suggest disableing FSUIPC to prevent any conflicts with MCE? Keep in mind that many virtual pilots out there have mapped lots of actions via FSUIPC. For me this solution will result in disableing MCE instead of FSUIPC until the problem will have been fixed. Sorry.

So. Got some time for testing. How did I test? As instructed I de-installed FSUIPC and deleted the <fsuipc-lvars-module> from community folder manually. Started MSFS200 and loaded up the C172 on runway with running engines. Started MCE without any problems. Checklist reading passed. Everything is fine. Next test: FSUIPC installed Re-installed FSUIPC and stopped while reading die Mobiflight popup. Could that be a hint? Started MSFS2020, selected the PMDG 737-700 with running engines on the same runway as the C172 before. Started MCE- Initialisation fine, Aircraft frame identified correctly. Ramp agent working. MCE stopped after reading the checklist on item 2, sent MSFS2020 to taskbar and popup says to restart the flight and not the simulator. Put MSFS2020 back to fullscreen, MCE has automatically opened the option page on the sim Tobii device missing in the controls page Restarted MCE, airframe identified, ramp agent annoucing, CTD again...same popup message. What did I learn? Difficult. I believe that MCE in combination with FSUIPC kicked Tobii out of my system temporarily. Tobii support was not very helpful and refers to Asobo...hahaha. Have you got another idea?

P. Dawson was very fast in responsing a request: FSUIPC Peter Dawson's reply: "...FSUIPC has nothing to do with Tobi and knows nothing about it, as do I! ..." When Tobii does not use FSUIPC but MCE does ... what else could be the reason?

First of all thank you for your response. MSFS2020 SU9 or even SU10 Beta do work reliable and fine. Just did a 90.minutes-flight and everything was great. No stutters, graphic glitches or anything else that could be adressed to Tobii. Interesting is your point about the used connection simconnect or FSUIPC. I'll will write to Tobii and FSUIPC vendors to get sure. By the way: All processes are set to normal by default.

Thank you for giving support. My task manager reports the following processes and / or services linked to Tobii: Tobii.EyeX.Interaction Tobii.EyeX.Engine platform_runtime_IS5LEYETRACKER5_service TobiiVirtualDevice service ( Tobii Eye Tracker generic service) Tobii.Service After installing the latest MCE version 2.9.79 I found a beta file which has been published here in the forum. I hope my information will help to sort out the issue. Fingers crossed and many thanks for supporting. LH067U

Hi guys, since a while I am not able to use MCE on MSFS2020 (latest stable) together with the Tobii Eytracker 5 and ends up in CTD of Tobii Eye tracker & MCE. Both are at latest versions and FSUIPC as registered as well. What does happen in detail: When launching MSFS2020 and Tobii Eye tracker 5 everything works as expected. Starting a flight at any airport is no big deal because everything works as it should be. After launching of MCE its start-up process is quite normal. But after about 2 minutes Tobii Eye Tracker stops working, led lights are still on but no head movements are possible and it can't really be restarted to solve the issue... And MCE crashes with a message of restarting MCE for a reinitialisation of the picked aircraft frame. It doesn't matter if I pick PMDG or FENIX. The outcome is the same! Does anyone out there has got either the same problem or any solution or work-around? Thanks in advance for any suitable support. Happy flying and safe landings, LH067U

I am always on admin rights when I use MSFS2020 and add-ons. I have deleted all regedit entries and all folders that have had a link to FS2Crew. On my second SSD I have discovered an old FS2Crew version that maybe was in conflict to the new one. Unfortunately it was not listed in the windows app add-on list. However. It works so far although FS2Crew CMD has to be started manually- but this is not a big deal. Thank for your support and everything is a bit more realistic now.

Did everything as instructed but it failed. Firstly the FS2Crew CMD hasn‘t start automatically. Secondly after manually starting nothing happened. Start via desktop shortcut works as it should be 🤷. Question: is it possible that the program fails because I use FBW32N dev version?

After I have de-installed and re-installed FS2Crew and FSUIPC as well the problem is still alive. This time no .net exeption error! BUT: FS2Crew CMD does not start automatically and the msfs2020 menu produces a red displayed message that the FS2Crew CMD is not running. Now inop. Probable exe.xml corruption problem. -> when I now start the FS2CREW CMD manually (admin rights) and hit the lauch app button the message disappears and nothing else happens 😞

It happens when I hit the connect button inside the MSFS2020 menu. And it pops up everytime I hit the button. I am on admin account rights. Going to turn off the computer and try again. will post what is going to happen then.

FS2CREW CMD has started normal with the sim. Unfortunalety the error comes up again. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ComponentModel.Win32Exception (0x80004005): The requested operation requires elevation at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at System.Diagnostics.Process.Start(ProcessStartInfo startInfo) at A..(Int32 ) at A. .(SimConnect , SIMCONNECT_RECV_EVENT ) at Microsoft.FlightSimulator.SimConnect.SimConnect.OnReceiveMessage(SIMCONNECT_RECV pData, UInt32 cbData) at SimConnect_CallDispatch(Void* , IntPtr , Void* ) at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal) at A..DefWndProc(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll ---------------------------------------- FS2CrewCommandCenter Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/FS2Crew%20Command%20Center/FS2CrewCommandCenter.exe ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4360.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- FS2CrewCommandCenter&& Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Program%20Files%20(x86)/FS2Crew%20Command%20Center/FS2CrewCommandCenter.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4400.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- Microsoft.FlightSimulator.SimConnect Assembly Version: 11.0.62651.3 Win32 Version: CodeBase: file:///C:/Program%20Files%20(x86)/FS2Crew%20Command%20Center/Microsoft.FlightSimulator.SimConnect.DLL ---------------------------------------- Microsoft.GeneratedCode Assembly Version: 1.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

No. After doing these two jobs the .net frameset error with unhandled exeption popped up again. Since the first v2.2 I have got this problem. I am gong to start msfs2020 again and watch and see. As the problem comes back I will past the content right here

No. Everything seems to be okay. I have restarted the computer after I had run the repair tool and Visual Studio refresh.

I have got a problem to start FS2Cew from the fsms2020 toolbar, too. It occurs a .net frameset error with unhandled exeption. I have repaired .net frameset as well as Visual Studio 2019 as described in the troubleshooting file. 3rd party add-ons have been disabled via MSAddon Linker as well. installed version: 2.2c

Thanks for your support so far! I am going to install the new patch and disable the user interface voice control to prevent any further sim rate changes. livery: It is the VA livery by Flygravity VA which has been available for about 4-5 weeks now. It is their first one for FBW and maybe not fully compartible I guess. The download itself is offered by the VA download section. The livery is neccessary for having a valid pirep accepted- alternative would be FBW vanilla one.🤨

MCE version (MCE version 2.9.1.8 / SimCo64_ldr.exe version 1.2.1.8) latest version installed, former version de-installed as published via windows checklist (default settings): livery is going to be recognised, but I am not able to do coordinated checklists, no costum checklists used other 3rd party liveries with checklists are working fine. Is there any specific variable to put into the livery's aircraft.cfg? FBW is indeed the current dev version which could be the reason- so I need to go to stable one SmartCARS entries repeating every 7-8 minutes: sim rate set 0,25 X sim rate set to normal

Hi guys, beside false log entries I can't enable coordinated checklists for a specific livery for FBW dev. But the entries are my bigger concern. Never happened before. Using latest FUIPC as well.

PROBLEM SOLVED.🙂 The hint was to disable ATC=1 to ATC=0 in the mce.cfg and set ATC=Others. Works for me and many thanks to Ben to his support.

Hi Gerald and a very merry Christmas and stay safe. My problem has not been solved after all the readings and those attempts: deinstalled MCE completely via the Windows Control Centre resetting of all folder permissions inside the C.\Program Files (x86) in comparison to a parallel W10-64 default installation to sort out permission issues default installation with UAC default settings both exe files (MCE / Simco64_Ldr) are able to start Simco64_Ldr.exe works while checking with CTRL+ALT+DEL without any problems MCE.exe starts working ... and falls back to error The program mce.exe version 2.8.9.2 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 2644 Start Time: 01d6da185535fcbd Termination Time: 10 Application Path: C:\Program Files (x86)\Multi Crew Experience\mce.exe Report Id: 0e595415-ad43-46a7-b24c-0c5ec3740089 Faulting package full name: Faulting package-relative application ID: Hang type: Unknown I try and run the A32NX mod under FS2020 Premium. Cheers, LH067U

In the meantime I have tried everything over and over again. Today another one: Re-installed MCE to default folder with UAC enabled and started MSFS2020 A32NX and MCE received data! Great 🙂 Shut down MSFS2020 to get sure it was not only a coincidence. Started MSFS2020 again, loaded everything as before ...loop again. 😞 Task manager shows Simco64.ldr.exe is running fine and mce.exe stopped with +not responding+ flag. Frustrating because nothing- really nothing- has changed my rig or folders ...except the DEC updates of MSFS2020.