Jump to content

LH067U

Members
 View Profile  See their activity

  • Content Count

    52

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by LH067U

  1. Posted

    4 hours ago, FS++ said:

    Not sure whether it was you "Gu***v*" who reported same issue via e-mail.

    It appears, there was a subtle bug in one of the files that would occsionally manifest itself under specific conditions.

    Something to do with some changes made recently to ensure MCE identifies the MSFS main window correctly and not be fooled by other multi-monitor windows that are of the same type.

    To cut a long story short, download this file, unzip and replace "Simco64_Ldr.exe"

    http://www.multicrewxp.com/Simco64_ldr.zip

    Since we now have aircraft specific packages, among them Multi Crew Fenix A320, they wouldn't have the most recent file (to support more planes) which could have triggered a wave of reports.

    Please understand that while more planes are integrated and features are added, episodes like this one may happen from time to time.

    It's not practical to test every supported plane against every deemed minor MCE update.

    Users just need to notify us and we will know exactly where to look.

    Thank you for prompting to look at it.

     

    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

  2. Posted

    19 hours ago, FS++ said:

    I assume you are running the latest Fenix release.

    Just make sure....

    - The Fenix A320 is set as the plane that MSFS loads on startup

    - You haven't deleted <fsuipc-lvar-module> in \Community\ folder by accident. Eventually, just re-install MCE

    - Un case it has to do with some odd livery, try it our with Fenix livery first.

    Guaranteed to work. Fo will not just handle almost every switch, but also dial everything, including FCU SPS, HDG, ALT, VS, radios, something that you won't get in other packages.

    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.

  3. Posted · Edited by LH067U

    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

  4. Posted · Edited by LH067U

    21 hours ago, FS++ said:

    You mis-read the post.

    It was for troubleshooting purposes so you can see which of the programs needs FSUIPC main application.

    You don't have to un-installing it. Just make sure it's not running. Run Tobii and see if it works, without running MCE.

    FSUIPC has been around for decades and many MCE users who also happen to use PF3 or Pilot2Atc have it running, so no conflict as such (and never had conflicts with it for a decade for that matter).

    The Tobii is the unknown. Plenty of threads suggesting it's a hit and miss with MSFS. 

    Find out whether they have their own wasm module or whether they are using Simconnect to interact with the sim for a start.

    Last time I checked, Simconnect API had limitations with regards "views adjustments" via programming, (works only by triggering keys assigned by user) and that's why ChasePlane couldn't make it to MSFS despite being very popular in FSX & Prepar3D.

     

     

    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.

     

     

  5. Posted

    On 9/4/2022 at 9:02 PM, FS++ said:

    This is normal. With PMDG 737 once MCE loads, if it doesn't find all the lvars it needs, it instructs you to reload the plane.

    You can prevent the pop-up by reloading the plane and before you start MCE.

    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.

    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.

  6. Posted

    On 9/1/2022 at 9:04 PM, FS++ said:

    No, MCE doesn't use FSUIPC main application. We only make use of the wasm module for some airplane switches.

    I suggest the following...

    Un-install FSUIPC and manually remove <fsuipc-lvars-module> from community folder.

    Start MSFS and load the Cessna Longitude or C172.

    MCE doesn't make use of the wasm with these planes. It's exclusively via Simconnect.

    Wait until aircraft is on tarmac ready to fly, then start MCE.

    "Simco64_Ldr.exe" our other app is the gateway to MSFS. Make sure no anti-virus is blocking it.

    It is expected to be running when MCE does. If it crashes for some reason, you'll get that "Unable to detect aircraft" message.

    Just a reminder, unlike with Pepar3D or FSX, with MSFS, do not start MCE until aircraft has finished loading. For complex supported planes like PMDG 737, FENIX A320, Aerosoft CRJ and Flybywire, you are advised to set one of those as the plane MSFS loads on startup for smooth operation.

     

     

    So. Got some time for testing.

    How did I test?

    1. As instructed I de-installed FSUIPC and deleted the <fsuipc-lvars-module> from community folder manually.
    2. Started MSFS200 and loaded up the C172 on runway with running engines.
    3. Started MCE without any problems. Checklist reading passed. Everything is fine.

    Next test: FSUIPC installed

    1. Re-installed FSUIPC and stopped while reading die Mobiflight popup. Could that be a hint?
    2. Started MSFS2020, selected the PMDG 737-700 with running engines on the same runway as the C172 before.
    3. Started MCE- Initialisation fine, Aircraft frame identified correctly. Ramp agent working.
    4. MCE stopped after reading the checklist on item 2, sent MSFS2020 to taskbar and popup says to restart the flight and not the simulator.
    5. Put MSFS2020 back to fullscreen, MCE has automatically opened the option page on the sim
      1. Tobii device missing in the controls page
    6. 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?

     

  8. Posted · Edited by LH067U

    19 hours ago, FS++ said:

    You're welcome.

     

    Meanwhile, have a look at this thread that I came across today. Some users are sating that it doesn't work with MSFS well.

    Find out whether it uses Asobo Simconnect or communicates with FSUIPC.

    Also, look at the proceses you listed and check none is set to "Real time priority"

     

     

    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.

  9. Posted · Edited by LH067U

    7 hours ago, FS++ said:

    I don't have the eye tracking hardware so a bit in the dark. 

    Is TobiGameHub.the main softwarethat runs in the background and drives the device? If it's the case, will download it.

    Please state exat "mce.exe" and "Simco64_Ldr.exe" versions you are on. Thanks

     

    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

  10. Posted · Edited by 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

  11. Posted

    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.

  12. Posted

    8 hours ago, byork said:

    Hard to guess, but I suggest starting fresh:

    Clear PBE off your system entirely.

    1. Uninstall Pushback Express.

    2. Manually delete any left over Pushback Express files in Appdata should they somehow still exist.

    3. Delete the EXE.xml file.

    4. Delete FS2Crew Data Process in Community folder if it's still there.

    5. Delete FS2Crew Command Center if it's still in your Community folder.

    6.  Re-download Pushback Express via your account... some of the earlier versions had issues with the Command Center... current version is 2.2C.

    When you run the PBE installer exe, an info screen will pop up and you can see the Version #.

    7. You'll need to re-enable FSUIPC autosave to re-add FSUIPC to the EXE.xml (so FSUIPC auto starts).

    Hopefully the clean install will sort your tool bar problems.

    Remember, you can still start PBE via the desktop short cut as a backup, but the Command Center is better in my view.


     

    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?

  13. Posted · Edited by LH067U

    1 hour ago, byork said:

    Right click on Command Center EXE anyway and select run as admin.

     

    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 😞

     

  14. Posted · Edited by LH067U

    7 minutes ago, byork said:

    Is this happening randomly?

    This important line:

    The requested operation requires elevation

    Turn off your computer.  Try it again fresh.

    You're in an Admin account right?

    Go to:

    C:\Program Files (x86)\FS2Crew Command Center\FS2CrewCommandCenter.exe

    Right click on it, select always run as an Administrator in the Compatibility tab.

    Restart your computer.

    Try again.

     

    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.

  15. Posted

    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.

     

     

  19. Posted

    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.🤨

  20. Posted

    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

     

     

     

     

     

     

  23. Posted

    On 12/14/2020 at 9:46 PM, FS++ said:

    You may not be aware, unlike FSX or Prepar3D that shutdown almost immediately, it could take up to a minute for MSFS 2020 to close itself down.

    Just seeing the window close doesn't mean it has fully shutdown.

    "Simco64_Ldr.exe" typically waits until MSFS signals simconnect session is closing before shutting down.

    I suggest before you restart MCE, make sure the app above isn't running, otherwise it could still be hooked to previous simulator session.

    Use CTRL+ALT+DEL to invoke task manager and under "processes", when you shutdown MSFS, see how long "flightsimulator.exe" is still around.

     

    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

  24. Posted · Edited by LH067U

    On 12/6/2020 at 6:45 PM, FS++ said:

    If data not coming...

    Be aware MCE (mce.exe) communicates with "Simco64.ldr.exe" which in turn interacts with the sim via Simconnect.

    The files are both digitally signed and will work nicely when in default C:\Program Files (x86)\Multi Crew Experience\ folder and without disabling UAC nor running the sim as admin.

    Check your anti-virus isn't interfering with those files and that you didn't shutdown "Simco64_Ldr.exe" by accident..

    The other possibility, maybe you altered "C:\Program Files (x86)\ folders permissions, which is never a good thing to do.

    See this thread, in order to see the strange things that can happen when you override that folder access rights.

     

    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.

  25. Posted · Edited by LH067U

    20 hours ago, FS++ said:

    Usually have to wait until the mod is compatible with latest ASOBO release.

    It breaks almost on every sim update.

    I believe they have a new Beta. Do not use old one.

     

    A32NX has fixed the ASOBO bug which is going to be rolled out by ASOBO within the next update. I update the A32X mod every day to be completly up to date.

    But when MCE is able to get data from the ASOBO vanilla bug bus 1.11.6 and A32X mod have fixed the bug...why does MCE doesn't get any data? That's curious, isn't it? 😉

    LH067U

×
×
  • Create New...