FSUIPC7 intermittent disconnects: TransmitClientEvent failures

[jaxx]

Here are some more error logs.

DisconnectLogs.zip

[John Dowson]

14 hours ago, Fremmed said:

It seems like every disconnect is preceded by a: 2121.74087 [326] I/O Error! (2, 80004004)

Ok, thanks - thats what I was looking for! I'll take a look.

[John Dowson]

Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.

[John Dowson]

Btw, are you using any other SimConnect clients, or any 3rd party add-ons that use FSUIPC?

[Fremmed]

1 hour ago, John Dowson said:

Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.

Of course. Will post later today.

9 minutes ago, John Dowson said:

Btw, are you using any other SimConnect clients, or any 3rd party add-ons that use FSUIPC?

Lots usually, but during that testing, the only thing I had running in addition to FSUIPC and the sim itself was Track-IR, which I don't think is using SimConnect? 

[John Dowson]

43 minutes ago, Fremmed said:

Lots usually, but during that testing, the only thing I had running in addition to FSUIPC and the sim itself was Track-IR, which I don't think is using SimConnect? 

I'm not sure if uses Simconnect, but probably not as I can see no other 'Open' calls in your SimConnect.log.  Maybe check for that in the full log to be sure.

[Scotfleiger]

If it is any help I have been running MSFS2020 on the ground (C172) with engines running using FSUIPC7 (disconnect beta) and LINDA for over 24 hours. Inputs via SimConnect have been minimal (axes and button ipc.controls calls) and no scenery updates. I have restarted LINDA many times for development testing. There have been no disconnects to report. 

[Pete Dowson]

1 hour ago, Fremmed said:

Track-IR, which I don't think is using SimConnect? 

I'm pretty sure it always used to. but then it needs to use camera views and so far we've not had much success with the usual SimConnect controls for those. So it makes one think ...

Pete

 

[N987PL]

I'm having same issue here.  Sometimes, even though axis' show up in FSUIPC, if I click on Joystick calibration for the axis I just looked at (elevator for instance), no signal is being sent to joystick calibration.  It is intermittent and not dependent on peripheral.  Happens to all of my USB connected controls.  Most recent this morning was Redbird YK1 and RD1.

********* FSUIPC7, Version 7.0.0-Beta (28th August 2020) by John & Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 19041, Release ID: 2004 (OS 10.0)
Reading options from "H:\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
User Name="MSFS Tester"
User Addr="Time Limited 311020"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
      265 System time = 07/09/2020 08:32:44
      265 FLT path = "C:\Users\Owner\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
      296 -------------------------------------------------------------------
      312 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      343 FS path = "C:\Users\Owner\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\"
      343 ---------------------- Joystick Device Scan -----------------------
      343 Product= PFC Throttle Quadrant Console
      343    Manufacturer= Precision Flight Controls, Inc.
      343    Vendor=0689, Product=D011 (Version 2.0)
      500    GUIDs returned for product: VID_0689&PID_D011:
      500       GUID= {E263CB60-206A-11E3-8001-444553540000}
      500       Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y0,Z1023
      500 Product= JAY Rudder
      500    Manufacturer= Redbird Flight Simulations, Inc.
      500    Vendor=241D, Product=FE4E (Version 0.1)
      500    GUIDs returned for product: VID_241D&PID_FE4E:
      500       GUID= {A2FA5800-0AD8-11E9-8001-444553540000}
      500       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X569,Y575,Z1023
      515 Product= Redbird Alloy YK1
      515    Manufacturer= Redbird Flight Simulations, Inc.
      515    Vendor=241D, Product=FE8E (Version 0.1)
      515    GUIDs returned for product: VID_241D&PID_FE8E:
      515       GUID= {A2FA5800-0AD8-11E9-8002-444553540000}
      515       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X695,Y1023,Z0
      515 -------------------------------------------------------------------
      515 Device acquired for use:
      515    Joystick ID = 0 (Registry okay)
      515    0=PFC Throttle Quadrant Console
      515    0.GUID={E263CB60-206A-11E3-8001-444553540000}
      515 Device acquired for use:
      515    Joystick ID = 1 (Registry okay)
      515    1=JAY Rudder
      515    1.GUID={A2FA5800-0AD8-11E9-8001-444553540000}
      515 Device acquired for use:
      515    Joystick ID = 2 (Registry okay)
      515    2=Redbird Alloy YK1
      515    2.GUID={A2FA5800-0AD8-11E9-8002-444553540000}
      515 -------------------------------------------------------------------
      625 LogOptions=00000000 00000001
      687 Loaded PFCcom64.DLL okay!
     1078 Loaded PFChid64.dll okay!
  2245890 Simulator detected
  2316796 SimConnect_Open succeeded
  2316812 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
  2316812 MSFS version = 11.0.282174.999
  2316812 Initialising SimConnect data requests now
  2322046 Aircraft loaded: running normally now ...
  2327828 User Aircraft ID not supplied -- trying default
  2392812 C:\Users\Owner\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\liveries-tbm930\SimObjects\Airplanes\Asobo_TBM930\aircraft.CFG
  2393109 flights\other\MainMenu.FLT
  2396312 System time = 07/09/2020 09:12:40, Simulator time = 13:11:00 (14:11Z)
  2396312 Aircraft="TBM 930 Blue, Cyan & Cream"
  2407093 -------------------- Starting everything now ----------------------
  2408781 Attempt to set external joystick assigns refused
  2580468 Sim stopped: average frame rate for last 179 secs = 58.3 fps
  2580468    Max AI traffic was 1 aircraft
  2580468 -------------------------------------------------------------------
  2583703 Planned flight from KSPG to KISP
  2583703 C:\USERS\OWNER\APPDATA\LOCAL\PACKAGES\MICROSOFT.FLIGHTSIMULATOR_8WEKYB3D8BBWE\LOCALSTATE\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
  2584062 C:\Users\Owner\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
  2698625 ---------------------- Joystick Device Scan -----------------------
  2698625 Product= PFC Throttle Quadrant Console
  2698640    Manufacturer= Precision Flight Controls, Inc.
  2698640    Vendor=0689, Product=D011 (Version 2.0)
  2698640    GUIDs returned for product: VID_0689&PID_D011:
  2698640       GUID= {E263CB60-206A-11E3-8001-444553540000}
  2698640       Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y0,Z1023
  2698640 Product= JAY Rudder
  2698640    Manufacturer= Redbird Flight Simulations, Inc.
  2698640    Vendor=241D, Product=FE4E (Version 0.1)
  2698640    GUIDs returned for product: VID_241D&PID_FE4E:
  2698640       GUID= {A2FA5800-0AD8-11E9-8001-444553540000}
  2698640       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X569,Y575,Z1023
  2698640 Product= Redbird Alloy YK1
  2698640    Manufacturer= Redbird Flight Simulations, Inc.
  2698640    Vendor=241D, Product=FE8E (Version 0.1)
  2698640    GUIDs returned for product: VID_241D&PID_FE8E:
  2698640       GUID= {A2FA5800-0AD8-11E9-8002-444553540000}
  2698640       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X695,Y1023,Z0
  2698640 -------------------------------------------------------------------
  2698656 Device acquired for use:
  2698656    Joystick ID = 0 (Registry okay)
  2698656    0=PFC Throttle Quadrant Console
  2698656    0.GUID={E263CB60-206A-11E3-8001-444553540000}
  2698656 Device acquired for use:
  2698656    Joystick ID = 1 (Registry okay)
  2698656    1=JAY Rudder
  2698656    1.GUID={A2FA5800-0AD8-11E9-8001-444553540000}
  2698656 Device acquired for use:
  2698656    Joystick ID = 2 (Registry okay)
  2698656    2=Redbird Alloy YK1
  2698656    2.GUID={A2FA5800-0AD8-11E9-8002-444553540000}
  2698656 -------------------------------------------------------------------
  2744859 ---------------------- Joystick Device Scan -----------------------
  2744859 Product= PFC Throttle Quadrant Console
  2744859    Manufacturer= Precision Flight Controls, Inc.
  2744859    Vendor=0689, Product=D011 (Version 2.0)
  2744859    GUIDs returned for product: VID_0689&PID_D011:
  2744859       GUID= {E263CB60-206A-11E3-8001-444553540000}
  2744859       Details: Btns=8, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R1023,U1023,V1023,X1023,Y0,Z1023
  2744859 Product= JAY Rudder
  2744859    Manufacturer= Redbird Flight Simulations, Inc.
  2744859    Vendor=241D, Product=FE4E (Version 0.1)
  2744859    GUIDs returned for product: VID_241D&PID_FE4E:
  2744859       GUID= {A2FA5800-0AD8-11E9-8001-444553540000}
  2744859       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X569,Y575,Z1023
  2744859 Product= Redbird Alloy YK1
  2744859    Manufacturer= Redbird Flight Simulations, Inc.
  2744859    Vendor=241D, Product=FE8E (Version 0.1)
  2744859    GUIDs returned for product: VID_241D&PID_FE8E:
  2744859       GUID= {A2FA5800-0AD8-11E9-8002-444553540000}
  2744859       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X695,Y1023,Z0
  2744859 -------------------------------------------------------------------
  2744875 Device acquired for use:
  2744875    Joystick ID = 0 (Registry okay)
  2744875    0=PFC Throttle Quadrant Console
  2744875    0.GUID={E263CB60-206A-11E3-8001-444553540000}
  2744875 Device acquired for use:
  2744875    Joystick ID = 1 (Registry okay)
  2744875    1=JAY Rudder
  2744875    1.GUID={A2FA5800-0AD8-11E9-8001-444553540000}
  2744875 Device acquired for use:
  2744875    Joystick ID = 2 (Registry okay)
  2744875    2=Redbird Alloy YK1
  2744875    2.GUID={A2FA5800-0AD8-11E9-8002-444553540000}
  2744875 -------------------------------------------------------------------
  2771718 Sim stopped: average frame rate for last 167 secs = 31.2 fps
  2771718    Max AI traffic was 10 aircraft
  2771718 -------------------------------------------------------------------
  2775484 flights\other\MainMenu.FLT
  2787609 === QUIT notified! Saving "Previous Flight" ...
  2791406 MSFS no longer running - trying to find...
  2791406 === Calling SimConnect_Close ...
  2791625 === SimConnect_Close done!
  2791625 === AI slots deleted!

 

[Fremmed]

1 hour ago, Pete Dowson said:

I'm pretty sure it always used to. but then it needs to use camera views and so far we've not had much success with the usual SimConnect controls for those. So it makes one think ...

Pete

 

FWIW, the trackIR shows up as a controller in the control options now. I assumed that meant it was accessed as a HID device. I don't think that used to be the case, though. I'll do some testing with an without it nonetheless.

[Fremmed]

8 hours ago, John Dowson said:

Sorry, but I need some more logging activated in FSUIPC. Could you go to the Log -> Custom menu entry, and enter x400, then repeat your tests. The FSUIPC7.log file produced will also be very big and may need culling. Thanks.

230MB 🙂

I cut about a half million lines of simread events from the middle.

FSUIPC7-x400.zip

[Fremmed]

5 hours ago, Pete Dowson said:

I'm pretty sure it always used to. but then it needs to use camera views and so far we've not had much success with the usual SimConnect controls for those. So it makes one think ...

Pete

 

I've done more testing now, and the same crashing happens with or without TrackIR running, but at much larger (a factor 10 probably) intervals when it's not.

[zkiwi]

Log files from most recent failure. (FSUIPC and Simconnect) 

Fail log edits.zip

[pilotjohn]

Similar issues happened to me today. Taxiing on the ground as I was turning around, all axes controls (don't have any buttons), went dead. FSUIPC still connected, Axes showing correct input etc. Exiting and restarting FSUIPC did not help. It randomly recovered after a few minutes for no apparent reason as I was about to quit the sim.

[John Dowson]

@zkiwi, @jaxx& @Fremmed Thanks for the logs. I;ll take a look, but no need to provide any more at this stage. Uoi can stop the logging now (SimConnect + FSUIPC).
I also released a new build yesterday. This has the automatic re-connect in and also (hopefully) fixes the crash that this introduced - please download and try this version. Report back if it re-connects and continues working please (or if it doesn't!), bit no more logs needed at the moment for this.

@N987PL Your issue is not related to the SimConnect error. I see you are using both the PFCcom and PFChid drivers - do you need both? Your PFC throttle is also recognised as a standard USB device, so that shouldn't need either driver. This is also very strange:
  2408781 Attempt to set external joystick assigns refused

Not sure what this means at the moment, I'll check, bit maybe you can determine which driver you actually need,, if any.

 

[John Dowson]

Could those who experience the disconnect due to the SimConnect issue (with TransmitClientEvent failures) please check their ini/assignments. It seems that there is an issue when assigning to the FS control (i.e. not direct to FSUIPC calibration) but then calibrating in FSUIPC7. If you do this, can you either update to 'direct to FSUIPC calibration' and calibrate, or if you sent to the FS directly, then delete the calibration in FSUIPC7. Thanks.

[John Dowson]

1 hour ago, John Dowson said:

This is also very strange:
  2408781 Attempt to set external joystick assigns refused

Not sure what this means at the moment, I'll check

Ok, this is normal when using the PFC dlls and is nothing to worry about.

[jaxx]

1 hour ago, John Dowson said:

Could those who experience the disconnect due to the SimConnect issue (with TransmitClientEvent failures) please check their ini/assignments. It seems that there is an issue when assigning to the FS control (i.e. not direct to FSUIPC calibration) but then calibrating in FSUIPC7. If you do this, can you either update to 'direct to FSUIPC calibration' and calibrate, or if you sent to the FS directly, then delete the calibration in FSUIPC7. Thanks.

So it's fine when it's configured like this?

[Axes]
PollInterval=10
RangeRepeatRate=10
0=AX,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0	-{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0	-{ DIRECT: Rudder }-
3=BX,256,D,1,0,0,0	-{ DIRECT: Aileron }-
4=BY,256,D,2,0,0,0	-{ DIRECT: Elevator }-
5=CZ,256,D,4,0,0,0	-{ DIRECT: Throttle }-
6=CU,256,D,5,0,0,0	-{ DIRECT: PropPitch }-
7=CV,256,D,6,0,0,0	-{ DIRECT: Mixture }-

 

[John Dowson]

1 minute ago, jaxx said:

So it's fine when it's configured like this?

I'm not sure, which is why I am asking for you to check. is that the config you have when you experience this issue? If so, then no. But if your assignments were previously different, then please check again with those assignments (presuming each of those axes is also calibrated in FSUIPC7 - if not, do that first).

 

[jaxx]

2 minutes ago, John Dowson said:

I'm not sure, which is why I am asking for you to check. is that the config you have when you experience this issue? If so, then no. But if your assignments were previously different, then please check again with those assignments (presuming each of those axes is also calibrated in FSUIPC7 - if not, do that first).

I was using that config the whole time and also do not have any axis mapped in MSFS directly. But I also only had the disconnects very rarely.

[John Dowson]

9 minutes ago, jaxx said:

I was using that config the whole time and also do not have any axis mapped in MSFS directly. But I also only had the disconnects very rarely.

Ok, thanks.

[pilotjohn]

I have all my axes set to "Send direct to FSUIPC Calibration" and continue to experience disconnects. This usually happens when I'm turning on the ground tightly (e.g. with some differential breaking, although is probably irrelevant).

[John Dowson]

@pilotjohn ok. But you have reported your issue in a different thread. Your issue is distinct from this issue, which has been identified as a SimConnect error that is causing the disconnect, known by having TransmitClientEvent failures noted in the log. There are currently lots of issues with SimConnect (and many in FSUIPC7, i'm sure), but it does not help me in the investigation when cross-posting your issues to different topics/posts. Could you please refrain from doing this, and post in the topic relevant to your problem. So, if you do not see any 'TransmitClientEvent' failures in your log, please do not add or follow the advice in this thread. It just causes confusion. Thanks.

I will update the title of this thread to make this thread more specific to this issue.

John

 

[John Dowson]

1 hour ago, pilotjohn said:

I have all my axes set to "Send direct to FSUIPC Calibration" and continue to experience disconnects. This usually happens when I'm turning on the ground tightly (e.g. with some differential breaking, although is probably irrelevant).

With TransmitClientEvent failures reported in the FSUIPC7.log file?

[N987PL]

John,

Not sure on PFCcom and PFCHid comment above.  I don't seem to have the disconnect issue with the throttle.....only the Redbird Yoke and Rudder pedals disconnecting.  I'm a registered user of FSUIPC and when trying to configure PFC throttle quadrant in P3D, Pete advised me to have both in my FSUIPC Modules folder.  I just assumed the same applied here.