Jump to content
The simFlight Network Forums

daern

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by daern

  1. Another voice to this topic - I am also experiencing similar behaviour since the Win11 update (updated on Friday using the "release preview" channel - this should be the build pushed out globally in a couple of days time). FSUIPC shuts down, and reports in the log that MSFS is no longer running. This doesn't happen immediately and seems quite random, often happening after it has been running for some time.

    This has happened a few times over the last couple of days. I shall give the suggestions given above a try and will also report back with feedback.

    Log attached

     

    FSUIPC7.log.txt

  2. 2 minutes ago, John Dowson said:

    Thanks for the update. Maybe worth checking the Asobo forums for issues with the latest release before you report - I still haven't had time to do this (or review the documentation updates for the latest release).

    Regards - and have a healthy and enjoyable festive period,

    John

    Thanks John. I've been watching the threads and, as yet, I've not seen anyone else report a combination of issues that would point to a specific SDK issue, but there's clearly a whole lot of people getting CTDs since this last release, so something is clearly up, even if there's no obvious pattern that's appeared as yet. Will keep an eye out...

    I wish you a quiet and peaceful Christmas for you and your family.

  3. 3 hours ago, John Dowson said:

    @daern I'm surprised about those events as your log shows FSUIPC7 exiting normally and that it was MSFS that crashed. I guess they are non-fatal errors due to the MSFS error.
    Your problem is almost certainly due to MSFS and you should raise a zendesk bug report. Btw, can you please ALWAYS attach your full log rather than pasting extracts, as there is further information I need to see, such as devices being used and the build version of FSUIPC (and any dlls) that you are using.

    @rvroman As you have not attached any relevant information (i.e. your logs) I can't really comment, but if it is similar to your previous log (or that of daern's) then it will also be the same issue.

    Maybe worth checking the MSFS forums for any similar reports - I haven't had much time to check out any issues with the latest release yet....

    John

    Thanks John. Because of the lack of info from MSFS itself on the cause of the crash, I'm just doing long flights to try to rule stuff out. If I can crash it without FSUIPC7 running, then this would be useful, but so far I've not managed so it does rather smell like something they've mucked up with the SDK interface.

    Thanks for the response and I'll keep you updated with what I find. If I can't get a crash without FSUIPC7 running, I'll raise a case on zendesk over the next day or two.

  4. 12 hours ago, Kevin H said:

    Is anyone else having a problem where the fuel pumps won’t turn on? I’m using the Fly-By-Wire mod as well, but I’m not sure if it is just me.

    Have you updated to the latest version (Dev or release)? The latest update broke a few things in the fbw mod which have since been fixed.

  5. So near, and yet so far! Flew all of the way from Leeds to Brussels, with barely a problem, landed cleanly and was taxiing the last half mile to the gate when the game went belly up and crashed. 

    This time (and for the first time for me), it took out FSUIPC7 as well in short succession. These are the three error reports from the Windows event viewer:

    1) 18:52:02

    Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
    Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5fda32ba
    Exception code: 0xc0000005
    Fault offset: 0x000000000043ca7a
    Faulting process ID: 0x3bc8
    Faulting application start time: 0x01d6d94b98f9592f
    Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    Report ID: a2041a77-2001-4ed3-a243-8d94f66831fe
    Faulting package full name: Microsoft.FlightSimulator_1.12.13.0_x64__8wekyb3d8bbwe
    Faulting package-relative application ID: App

    2) 18:52:10

    Faulting application name: FSUIPC7.exe, version: 7.0.0.3, time stamp: 0x5fe3432a
    Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0
    Exception code: 0xc0000005
    Fault offset: 0x0000000000045f86
    Faulting process ID: 0x215c
    Faulting application start time: 0x01d6d94baa09b00a
    Faulting application path: D:\Games\Non-Steam\FS2020\FSUIPC7\FSUIPC7.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report ID: 6e2fbe8d-0068-413e-bd33-82f86538efcd
    Faulting package full name: 
    Faulting package-relative application ID: 

    3) 18:52:14

    Faulting application name: FSUIPC7.exe, version: 7.0.0.3, time stamp: 0x5fe3432a
    Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x27bfa5f0
    Exception code: 0xc000041d
    Fault offset: 0x0000000000045f86
    Faulting process ID: 0x215c
    Faulting application start time: 0x01d6d94baa09b00a
    Faulting application path: D:\Games\Non-Steam\FS2020\FSUIPC7\FSUIPC7.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report ID: 18745916-c8e0-40d6-831d-66f3f3b5c934
    Faulting package full name: 
    Faulting package-relative application ID: 

    These are the FSUIPC7 logs:

           78 System time = 23/12/2020 16:50:05
           78 FLT path = "C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
           94 -------------------------------------------------------------------
          109 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
          125 FS path = "D:\Games\Non-Steam\FS2020\"
          141 LogOptions=00000000 00000001
         6109 Simulator detected
        45656 SimConnect_Open succeeded
        45656 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
        45656 MSFS version = 11.0.282174.999
        45656 Initialising SimConnect data requests now
        70438 User Aircraft ID not supplied -- trying default
        74500 D:\Games\Non-Steam\FS2020\Official\OneStore\asobo-aircraft-tbm930\SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG
        74703 flights\other\MainMenu.FLT
        75406 Aircraft loaded: running normally now ...
        75969 System time = 23/12/2020 16:51:21, Simulator time = 15:51:20 (16:51Z)
        83031 -------------------- Starting everything now ----------------------
       162453 D:\Games\Non-Steam\FS2020\Official\OneStore\asobo-aircraft-208b-grand-caravan-ex\SimObjects\Airplanes\Asobo_208B_GRAND_CARAVAN_EX\aircraft.CFG
       162453 Sim stopped: average frame rate for last 87 secs = 91.4 fps
       162453    Max AI traffic was 1 aircraft
       162453 -------------------------------------------------------------------
       225234 D:\Games\Non-Steam\FS2020\Community\a32nx\SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG
       225250 Sim stopped: average frame rate for last 62 secs = 99.4 fps
       225250    Max AI traffic was 0 aircraft
       225250 -------------------------------------------------------------------
       228609 C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
       237641 #### ERROR: No SimConnect data seen for more than set stall time - will attempt to reconnect...
       237641 **** SimConnect Data Stalled! Re-connecting now ... ****
       237906 SimConnect_Open succeeded
       237906 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
       237906 MSFS version = 11.0.282174.999
       237906 Initialising SimConnect data requests now
       237906 User Aircraft ID 1 supplied, now being used
       237906 SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG
       237953 User Aircraft ID 1 supplied, now being used
       238672 System time = 23/12/2020 16:54:03, Simulator time = 16:53:53 (16:53Z)
      1882281 **** Restarting traffic scanning due to non-reception ****
      7321109 MSFS no longer running - exiting
      7321109 === Hot key unregistered
      7321109 === Stop called ...
      7321125 === Closing external processes we started ...
      7322141 === About to kill any Lua plug-ins still running ...
      7323297 === About to kill my timers ...
      7323297 === Restoring window procs ...
      7323297 === Unloading libraries ...
      7323297 === stopping other threads ...
      7323297 === ... Button scanning ...
      7323406 === ... Axis scanning ...
      7323516 === Releasing joystick devices ...
      7323516 === Freeing macro memory
      7323516 === Removing any offset overrides
      7323516 === Clearing any displays left
      7323516 === Calling SimConnect_Close ...
      7323734 === SimConnect_Close done!
      7323734 === AI slots deleted!
      7323734 === Freeing button memory ...
      7323734 === Closing my Windows ...
      7323734 === Freeing FS libraries ...
      7324734 === Closing devices ...
      7324734 === Closing the Log ... Bye Bye! ...
      7324734 System time = 23/12/2020 18:52:10
      7324734 *** FSUIPC log file being closed
    Minimum frame rate was 17.1 fps, Maximum was 100.5 fps
    Average frame rate for running time of 7258 secs = 30.7 fps
    Maximum AI traffic for session was 62 aircraft
    Traffic deletions 0 aircraft
    Memory managed: 2 Allocs, 1 Freed
    ********* FSUIPC Log file closed ***********

    So, definitely different behaviour, but if I were a betting man, I would say that MSFS is blowing up and taking FSUIPC7 out with it as collateral damage. Feel free to shout if I can provide any other details.

  6. Just now, John Dowson said:

    @daern Your issue is the same as that posted by @rvroman , and so my comment above also applies.
    You could also try the attached version, v7.0.3, that I will be releasing shortly. There aren't that many changes, but it has been rebuilt against the latest SDK (0.9.0.0) which was released with 1.12.13.0.

    John

    FSUIPC7.exe 591.5 kB · 0 downloads

    Thanks @John Dowson - spotted that, installed it and am currently mid-way from Leeds to Brussels on a test flight 🙂

    Will report back on my findings.

  7. Another FSUIPC7 user here, who is now receiving CTDs from FS2020 since yesterday's update. In the case of the most recent crash, I hadn't even got the A32NX's engines switched on yet, and had just started loading passengers through SLC.

    Logs, although they look quite similar to those posted above:

           63 System time = 23/12/2020 16:22:55
           63 FLT path = "C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
           78 -------------------------------------------------------------------
           94 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
          110 FS path = "D:\Games\Non-Steam\FS2020\"
          110 LogOptions=00000000 00000001
         6094 Simulator detected
        43797 SimConnect_Open succeeded
        43797 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
        43797 MSFS version = 11.0.282174.999
        43797 Initialising SimConnect data requests now
        54078 User Aircraft ID not supplied -- trying default
        58110 D:\Games\Non-Steam\FS2020\Community\a32nx\SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG
        58297 flights\other\MainMenu.FLT
        58828 Aircraft loaded: running normally now ...
        59688 System time = 23/12/2020 16:23:54, Simulator time = 15:23:53 (16:23Z)
        68031 -------------------- Starting everything now ----------------------
       139828 Sim stopped: average frame rate for last 81 secs = 96.5 fps
       139828    Max AI traffic was 0 aircraft
       139828 -------------------------------------------------------------------
       142360 C:\Users\daern\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
       324016 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
       324016 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
       326094 MSFS no longer running - exiting
       326094 === Hot key unregistered
       326094 === Stop called ...
       326094 === Closing external processes we started ...
       327094 === About to kill any Lua plug-ins still running ...
       328266 === About to kill my timers ...
       328266 === Restoring window procs ...
       328266 === Unloading libraries ...
       328266 === stopping other threads ...
       328266 === ... Button scanning ...
       328375 === ... Axis scanning ...
       328485 === Releasing joystick devices ...
       328485 === Freeing macro memory
       328485 === Removing any offset overrides
       328485 === Clearing any displays left
       328485 === Calling SimConnect_Close ...
       328703 === SimConnect_Close done!
       328703 === AI slots deleted!
       328703 === Freeing button memory ...
       328703 === Closing my Windows ...
       328703 === Freeing FS libraries ...
       329719 === Closing devices ...
       329719 === Closing the Log ... Bye Bye! ...
       329719 System time = 23/12/2020 16:28:24
       329719 *** FSUIPC log file being closed
    Minimum frame rate was 25.8 fps, Maximum was 100.6 fps
    Average frame rate for running time of 269 secs = 58.6 fps
    Maximum AI traffic for session was 14 aircraft
    Traffic deletions 0 aircraft
    Memory managed: 2 Allocs, 1 Freed
    ********* FSUIPC Log file closed ***********

    I'm running out of things to blame here - down to just A32nx and FSUIPC7 installed...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.