Jump to content
The simFlight Network Forums

FSUIPC 7.2.12 is terminated during the fligh


Recommended Posts

Posted

FSUIPC is terminated during the flight
Hello Pete,
I'm writing with a translator, sorry.
Windows11 with MSFS2020 and FSUIPC " 7.2.12" registered version.
Unfortunately it has not changed, when flying the FSUIPC is irregularly terminated, the Flusi continues to run. When the FSUIPC is restarted, it is active again for a while until the next shutdown. 
I cannot give a time, it varies greatly.
As I said, this error did not occur with W10. 
My computer always runs at full power - I have deactivated energy saving, etc.
DLH874 Bernd

Translated with www.DeepL.com/Translator (free version)

Posted

Please see the provided README.txt, under Problems running FSUIPC7:

Quote

...
5. Windows 11 issue: FSUIPC7 closes down soon after starting. If you experience this issue, please first try re-installing the VC++ redistributables (see item 1, above).
   If the issue still occurs after this, you need to add the following line to the [General] section of your FSIUPC7.ini file (located in your FSUIPC7 installation folder):
        DisableMSFSMonitor=Yes
 

If that does not solve your issue, please show me your FSUIPC7.log file.

John

Posted

Hi there,
I've added the line and I'm on a short flight right now.
If the problem occurs again, I will report again with the xxx.log file.
Thanks again. DLH 874 Bernd

Posted

Hi there,
I will remove the command "DisableMSFSMonitor = Yes" again.
MSFS crashed shortly before landing. With the autosave function, I was able to continue flying at the old location.
FSUIPC continued to run but no longer had any connection with the other programs. IVAO + smartcars received no more data from FSUIPC.
The next time I close the FSUIPC I will send the log files to you.
DLH874 Bernd

Posted
5 minutes ago, CFG874 said:

MSFS crashed shortly before landing.

If MSFS crashed, you need to report to Asobo. Check the Windows Event viewer - you should attach the crash event if/when reporting to Asobo.

5 minutes ago, CFG874 said:

FSUIPC continued to run but no longer had any connection with the other programs.

It won't, if MSFS crashed.

6 minutes ago, CFG874 said:

The next time I close the FSUIPC I will send the log files to you.

Only if you think there is an issue with FSUIPC. If MSFS is crashing, I cant help.

John

Posted

Hello John,
I removed the line and the problem is back. The .log file as an attachment
Kind regards
DLH874 Bernd

********* FSUIPC7, Version 7.2.12 (5th November 2021) by John Dowson *********
MS Store installation detected: Checking for FS path in 'C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\
WebSocket server found: C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Home 64 Bit reported as Build 22000, Release ID: 2009 (OS 10.0)
Reading options from "C:\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Bernd Reisener"
User Addr="reisener@t-online.de"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       31 System time = 09/11/2021 13:28:54
       31 FLT path = "C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\"
       46 -------------------------------------------------------------------
      171 Run: "C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe"
      171 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      187 FS path = "C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\"
      187 ---------------------- Joystick Device Scan -----------------------
      250 Product= TWCS Throttle
      250    Manufacturer= Thrustmaster
      250    Vendor=044F, Product=B687 (Version 1.16)
      265    GUIDs returned for product: VID_044F&PID_B687:
      265       GUID= {599F5D20-12BC-11EB-8002-444553540000}
      265       Details: Btns=14, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y1023,Z65535
      265 Product= T.A320 Copilot
      265    Manufacturer= Thrustmaster
      265    Serial Number= 1
      265    Vendor=044F, Product=0406 (Version 2.0)
      265    GUIDs returned for product: VID_044F&PID_0406:
      265       GUID= {15002840-A5A9-11EB-8001-444553540000}
      265       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255
      265 -------------------------------------------------------------------
      265 Device acquired for use:
      265    Joystick ID = 0 (Registry okay)
      265    0=TWCS Throttle
      265    0.GUID={599F5D20-12BC-11EB-8002-444553540000}
      265 Device acquired for use:
      265    Joystick ID = 1 (Registry okay)
      265    1=T.A320 Copilot
      265    1.GUID={15002840-A5A9-11EB-8001-444553540000}
      265 -------------------------------------------------------------------
      265 LogOptions=00000000 00000001
     3062 Simulator detected
     8187 SimConnect_Open succeeded
     8187 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
     8187 MSFS version = 11.0.282174.999
     8187 Initialising SimConnect data requests now
     8187 flights\other\MainMenu.FLT
     8187 SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
     8218 User Aircraft ID 1 supplied, now being used
     8218 User Aircraft ID 1 supplied, now being used
     8250 Aircraft loaded: running normally now ...
     8265 Aircraft="Lufthansa D-AIJA"
     8281 System time = 09/11/2021 13:29:02, Simulator time = 12:29:02 (12:29Z)
    34375 C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\flybywire-aircraft-a320-neo\SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
    36703 -------------------- Starting everything now ----------------------
    36921 C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
   600312 *** ERROR: Autosave couldn't delete "C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\AutoSave Sun 184702" (error 2/2)
  1199812 *** ERROR: Autosave couldn't delete "C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\AutoSave Mon 155344" (error 2/2)
  1799312 *** ERROR: Autosave couldn't delete "C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\AutoSave Mon 160344" (error 2/2)
  2398812 *** ERROR: Autosave couldn't delete "C:\Users\reise\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\AutoSave Mon 161343" (error 2/2)
  2868062 MSFS no longer running - exiting
  2868062 Stopped: "C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe"
  2868062 === Hot key unregistered
  2868062 === Stop called ...
  2868062 === Closing external processes we started ...
  2868578 === About to kill any Lua plug-ins still running ...
  2868734 === Closing global Lua thread
  2869515 === About to kill my timers ...
  2869718 === Restoring window procs ...
  2869718 === Unloading libraries ...
  2869718 === stopping other threads ...
  2869718 === ... Button scanning ...
  2869828 === ... Axis scanning ...
  2869921 === Releasing joystick devices ...
  2869921 === Freeing macro memory
  2869921 === Removing any offset overrides
  2869921 === Clearing any displays left
  2869921 === Calling SimConnect_Close ...
  2870140 === SimConnect_Close done!
  2870140 === AI slots deleted!
  2870140 === Freeing button memory ...
  2870140 === Closing my Windows ...
  2870140 === Freeing FS libraries ...
  2871156 === Closing devices ...
  2871156 === Closing the Log ... Bye Bye! ...
  2871156 System time = 09/11/2021 14:16:45
  2871156 *** FSUIPC log file being closed
Minimum frame rate was 33.9 fps, Maximum was 60.1 fps
Average frame rate for running time of 2857 secs = 46.1 fps
Maximum AI traffic for session was 24 aircraft
Traffic deletions 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 

Posted
1 hour ago, CFG874 said:

I removed the line and the problem is back.

It would be...Why did you remove the line? What did you expect?
This new ini parameter was added to circumvent this issue. I do not currently know what is causing this issue for some folks on Windows 11. If you are experiencing this, you need to add this new ini parameter.

John

Posted

Hello John,
I'll tell you my version. When I add the command, fsuipc does not end, but it also no longer sends data to other programs such as smartCars (this records my flight so that it can be settled with DLH_VA flight). I don't think any more data arrives at IVAO either. But will check it again. So command back in.
Thanks again.
DLH874 Bernd

Posted
1 hour ago, CFG874 said:

When I add the command, fsuipc does not end,

No, it won't. You need to quit FSUIPC manually.

1 hour ago, CFG874 said:

it also no longer sends data to other programs such as smartCars (this records my flight so that it can be settled with DLH_VA flight). I don't think any more data arrives at IVAO either. But will check it again. So command back in.

Then that will be a separate issue on Windows 11 that will need investigating. If this is the case, please raise a separate topic and provide full information.

John

Posted
19 hours ago, John Dowson said:
20 hours ago, CFG874 said:

When I add the command, fsuipc does not end,

No, it won't. You need to quit FSUIPC manually.

This has now been corrected in the attached version via a new ini parameter value. You need to set:
    DisableMSFSMonitor=Enum

John

 

FSUIPC7.exe

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.