Jump to content
The simFlight Network Forums

FSUIPC ERROR: 13


Alexey Teplyakov

Recommended Posts

I'm 100 percent sure, although in the log file, as you already said, 10

I cannot attach images too small size only you can upload

Выпуск    Windows 11 Pro
Версия    21H2
Дата установки    ‎03.‎11.‎2021
Сборка ОС    22000.282
Взаимодействие    Windows Feature Experience Pack 1000.22000.318.0
 

Edited by Alexey Teplyakov
Link to comment
Share on other sites

Ok, yes - just checked my log file and it also says Windows 10, event though i am on 11! I will look into this.

I cannot see that image you attached - What does it say? Are you sure that this is coming from FSUIPC, and not an FSUIPC client?
I cannot see a message 'IPC request contains bad data' anywhere in FSUIPC7.
I see you are also using an unregistered version.

What FSUIPC7 clients are you using? Have they been updated for FSUIPC7/MSFS?

If the message is from a client, you need to contact the support for that client.

John

Link to comment
Share on other sites

Why are you sending me log files?
Please answer my question: What FSUIPC7 clients are you using?
Error 13 IS NOT an error message from FSUIPC as far as I can tell...

Your 'previous' log file shows that FSUIPC7 exited after about 4 minutes as MSFS was no longer running.
The second log file shows FSUIPC7 still running (i.e. not closed down) after 2 minutes.

Can you please answer my question and explain what your issue actually  is (no pictures please!). i.e. what happens when you acknowledge the message?
Is FSUIPC7 still running? If not, are there any events visible in the Windows Event Viewer?

John

Link to comment
Share on other sites

One thing you can do to try and track this down is to activate logging for IPC Reads and IPC Writes, using the FSUIPC7 Log menu.  Also Open the logging console (from the same menu).
When you get that error, take a note of the timestamp of the last message logged, then acknowledge the message and then exit FSUIPC7, and show me your FSUIPC7.log file.

John

Link to comment
Share on other sites

********* FSUIPC7, Version 7.2.12 (5th November 2021) by John Dowson *********
MS Store installation detected: Checking for FS path in 'C:\Users\alex2\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = H:\MSFS\
WebSocket server found: F:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 22000, Release ID: 2009 (OS 10.0)
Reading options from "F:\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Alexey Teplyakov"
User Addr="alex210680@inbox.ru"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       63 System time = 23/11/2021 07:48:27
       63 FLT path = "C:\Users\alex2\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\"
       78 -------------------------------------------------------------------
      125 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      141 FS path = "H:\MSFS\"
      156 ---------------------- Joystick Device Scan -----------------------
      156 Product= VPC Rudder Pedals
      156    Manufacturer= VIRPIL Controls/20210102
      156    Vendor=3344, Product=01F8 (Version 0.1)
      219    GUIDs returned for product: VID_3344&PID_01F8:
      219       GUID= {BDEDF570-60C3-11EB-8002-444553540000}
      219       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      219       GUID= {BDEDF570-60C3-11EB-8001-444553540000}
      219       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U16384,V0,X0,Y0,Z16384
      219 Product= R-VPC Stick WarBRD
      219    Manufacturer= VIRPIL Controls/20210102
      219    Vendor=3344, Product=40CC (Version 0.1)
      219    GUIDs returned for product: VID_3344&PID_40CC:
      219       GUID= {A7EA67D0-7AD2-11EB-8003-444553540000}
      219       Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U16384,V16384,X16384,Y16384,Z16384
      234 Product= L-VPC Throttle MT-50CM3
      234    Manufacturer= VIRPIL Controls/20210102
      234    Vendor=3344, Product=8194 (Version 0.1)
      234 -------------------------------------------------------------------
      234    WARNING: Joystick ID 0 is duplicated in Registry
      234 Device acquired for use:
      234    Joystick ID = 2 (Registry okay)
      234    2=VPC Rudder Pedals
      234    2.GUID={BDEDF570-60C3-11EB-8001-444553540000}
      234 Device acquired for use:
      234    Joystick ID = 0 (Registry okay)
      234    0=RIGHT VPC Stick WarBRD
      234    0.GUID={E545AF70-7B33-11EB-8001-444553540000}
      234 Device acquired for use:
      234    Joystick ID = 2 (Registry okay)
      234    2=LEFT VPC Throttle MT-50CM3
      234    2.GUID={BDEDF570-60C3-11EB-8001-444553540000}
      234 Device acquired for use:
      234    Joystick ID = 0 (Registry okay)
      234    0=LEFT VPC Throttle MT-50CM3
      234    0.GUID={E545AF70-7B33-11EB-8001-444553540000}
      234 -------------------------------------------------------------------
      250 LogOptions=00000000 00000001
  3528125 Simulator detected
  3625656 SimConnect_Open succeeded
  3625656 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
  3625656 MSFS version = 11.0.282174.999
  3625656 Initialising SimConnect data requests now
  3685375 User Aircraft ID not supplied -- trying default
  3704813 H:\MSFS\Community\flybywire-aircraft-a320-neo\SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
  3705078 Aircraft loaded: running normally now ...
  3705391 System time = 23/11/2021 08:50:12, Simulator time = 04:50:12 (05:50Z)
  3705391 Aircraft="Airbus A320 Neo (FBW) Aeroflot"
  3712391 -------------------- Starting everything now ----------------------
  3831375 Sim stopped: average frame rate for last 126 secs = 98.0 fps
  3831375    Max AI traffic was 1 aircraft
  3831375 -------------------------------------------------------------------
  3833969 C:\Users\alex2\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
  4189625  READ0[14512]  3304,   4 bytes: 00 00 12 72                                      ...r
  4189625  READ0[14512]  3308,   4 bytes: 0D 00 DE FA                                      ....
  4189625 WRITE0[14512]  330A,   4 bytes: 02 00 00 00                                      ....
  4189734  READ0[14512]  0840,   2 bytes: 00 00                                            ..
  4189734  READ0[14512]  0C1A,   2 bytes: 00 01                                            ..
  4189734  READ0[14512]  05DC,   2 bytes: 00 00                                            ..
  4189734  READ0[14512]  02BC,   4 bytes: 00 00 00 00                                      ....
  4189734  READ0[14512]  0570,   8 bytes: 7A E8 D8 7D 19 00 00 00                          z..}....
  4189734  READ0[14512]  31E4,   4 bytes: 30 97 02 00                                      0...
  4189734  READ0[14512]  0578,   4 bytes: 67 3C 46 00                                      g<F.
  4189734  READ0[14512]  057C,   4 bytes: 98 4B 0D 00                                      .K..
  4189734  READ0[14512]  0580,   4 bytes: 14 C0 76 C3                                      ..v.
  4189734  READ0[14512]  02A0,   2 bytes: 63 03                                            c.
  4189734  READ0[14512]  0AEC,   2 bytes: 02 00                                            ..
  4189734  READ0[14512]  088C,   2 bytes: 23 00                                            #.
  4189734  READ0[14512]  0924,   2 bytes: 23 00                                            #.
  4189734  READ0[14512]  09BC,   2 bytes: 00 00                                            ..
  4189734  READ0[14512]  0A54,   2 bytes: 00 00                                            ..
  4189734  READ0[14512]  0894,   2 bytes: 00 00                                            ..
  4189734  READ0[14512]  092C,   2 bytes: 00 00                                            ..
  4189734  READ0[14512]  09C4,   2 bytes: 00 00                                            ..
--------- e.t.c

Link to comment
Share on other sites

11798109  READ0[14512]  341D,   1 bytes: 00                                               .
 11798109  READ0[14512]  3365,   1 bytes: 00                                               .
 11798109  READ0[14512]  6FFF,   1 bytes: 00                                               .
 11798172 MSFS no longer running - exiting
 11798172 === Hot key unregistered
 11798172 === Stop called ...
 11798172 === Closing external processes we started ...
 11798688 === About to kill any Lua plug-ins still running ...
 11798844 === Closing global Lua thread
 11799609 === About to kill my timers ...
 11799813 === Restoring window procs ...
 11799813 === Unloading libraries ...
 11799813 === stopping other threads ...
 11799813 === ... Button scanning ...
 11799922 === ... Axis scanning ...
 11800031 === Releasing joystick devices ...
 11800031 === Freeing macro memory
 11800031 === Removing any offset overrides
 11800031 === Clearing any displays left
 11800031 === Calling SimConnect_Close ...
 11800234 === SimConnect_Close done!
 11800234 === AI slots deleted!
 11800234 === Freeing button memory ...
 11800234 === Closing my Windows ...
 11800234 === Freeing FS libraries ...
 11801250 === Closing devices ...
 11801250 === Closing the Log ... Bye Bye! ...
 11801250 System time = 23/11/2021 11:05:08
 11801250 *** FSUIPC log file being closed
Minimum frame rate was 31.2 fps, Maximum was 105.7 fps
Average frame rate for running time of 8116 secs = 60.7 fps
Maximum AI traffic for session was 1 aircraft
Traffic deletions 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 

Link to comment
Share on other sites

6 hours ago, Alexey Teplyakov said:

I didn't understand how take a note of the timestamp of the last message logged,

The timestamp is the first number of the log line. What was the last line logged when the error you see was displayed? Knowing the offset that is giving this problem may help the developer of the AflAgent client program determine what the issue is - did you contact the developer of this program?

The last offset read (from the log you posted) indicates thet your 3rd party client was trying to read offset 6FFF. This offset is in an area (6F00-6FFF) that is reserved for XPUIPC use (i.e. for X-Plane), to avoid clashes, and is not actually used in FSUIPC7. Are you sure the client you are using is working with FSUIPC, and is not XUIPC specific?

Also, did you exit MSFS/FSUIPC, or did FSUIPC close as it thinks that MSFS has closed? Your log indicates that FSUIPC7 exited very soon after the read request to that XUIPC offset:

Quote

11798109  READ0[14512]  6FFF,   1 bytes: 00                                               .
11798172 MSFS no longer running - exiting

Are you using Windows 11? If so, please also add the following to the [General] section of your FSUIPC7.ini file:

    DisableMSFSMonitor=Enum

John

 

Link to comment
Share on other sites

1893078  READ0[944]  3365,   1 bytes: 00                                               .
  1893078  READ0[944]  6FFF,   1 bytes: 00                                               .
  1893141 MSFS no longer running - exiting
  1893141 === Hot key unregistered
  1893141 === Stop called ...
  1893141 === Closing external processes we started ...
  1893656 === About to kill any Lua plug-ins still running ...
  1893812 === Closing global Lua thread
  1894594 === About to kill my timers ...
  1894797 === Restoring window procs ...
  1894797 === Unloading libraries ...
  1894797 === stopping other threads ...
  1894797 === ... Button scanning ...
  1894906 === ... Axis scanning ...
  1895000 === Releasing joystick devices ...
  1895000 === Freeing macro memory
  1895000 === Removing any offset overrides
  1895000 === Clearing any displays left
  1895000 === Calling SimConnect_Close ...
  1895219 === SimConnect_Close done!
  1895219 === AI slots deleted!
  1895219 === Freeing button memory ...
  1895219 === Closing my Windows ...
  1895219 === Freeing FS libraries ...
  1896219 === Closing devices ...
  1896219 === Closing the Log ... Bye Bye! ...
  1896219 System time = 29/11/2021 13:32:46
  1896219 *** FSUIPC log file being closed
Minimum frame rate was 35.2 fps, Maximum was 100.8 fps
Average frame rate for running time of 1833 secs = 58.8 fps
Maximum AI traffic for session was 2 aircraft
Traffic deletions 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

 

I entered everything, but continues to close itself (((

Link to comment
Share on other sites

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.