FSUIPC7 intermittent disconnects: TransmitClientEvent failures

[John Dowson]

3 minutes ago, N987PL said:

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.

That seems strange to me. I don't have any PFC devices so cannot advise. I'll leave Pete (or Thomas) to respond to this. However, it seems to me that your throttle is detected as a standard USB hid device, so I don't think you need them (if you don't have any other PFC devices). Maybe at least try without those, to be sure. 

[cbe0004]

39 minutes ago, John Dowson said:

With TransmitClientEvent failures reported in the FSUIPC7.log file?

John I have this issue too. I have my axis set to "Send Direct to FSUIPC Calibration" and have TransmitClientEvent failures in the log with disconnects. 

[Pete Dowson]

1 hour ago, N987PL said:

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.

No, I'd never say that. You choose whichever is applicable. My throttle quadrant and Thomas's are both serial port devices, and that needs PFCcom64.dll with FSUIPC5,6 or 7.  It may possibly be a HID device (USB rather than serial port) which needs PFCHid64.dll instead. The quadrants in the Cirrus consoles are like that.

But PFC also made (make?) yokes and pedals which are normal Joystick USB devices and don't need any special drivers at all. Whether they also made normal UDB throttle quadrants I really don't know. Sorry. You should get adequate documentation or other information from PFC, with the hardware.

You only install the drivers you need. You'll just confuse things otherwise.

Pete

 

[pilotjohn]

2 hours ago, John Dowson said:

@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

 

Ack, should I start a separate thread on the in-game disconnects or is "FSUIPC7 control problem" the right thread for disconnects without the error?

[John Dowson]

6 minutes ago, pilotjohn said:

Ack, should I start a separate thread on the in-game disconnects or is "FSUIPC7 control problem" the right thread for disconnects without the error?

If you read the initial post in the 'FSUIPC7 control problem' you will (hopefully) see that this is completely distinct from your issue, although you did also post your issue there (again, thread hijacking). The issue in that thread is that his controllers are no longer working, it is NOT a random disconnect issue.

Its really not difficult. Search for an issue that is the same or very similar to yours. If one exists, use that thread. If not, create a new one.

For your issue, please check your USB power management settings. If they are correct and you still have your issue, please start a new thread.

 

[zkiwi]

On 9/9/2020 at 9:01 PM, John Dowson said:

John,

I downloaded the latest version and still had crashes. I deleted the folder completely and reinstalled a clean version and set it up with just aileron, elevator, rudder and brakes. I still got crashes. I did notice that everytime i went back to FSUIPC that an axis on my throttle quadrant was always identified ( dirty/noisy pot i think) so on a chance i ignored all other axis reference that were not assigned in FSUIPC and just managed a full flight with no transientclient errors.

I'll try a few more flights over the weekend but it was a two hour flight with no transientclient errors and no obvious issues in the cockpit. I was previously getting freezing ever 10 or 15 minutes and almost always on landing.

 

Quote

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

 

Edited September 11, 2020 by zkiwi

[John Dowson]

2 hours ago, zkiwi said:

so on a chance i ignored all other axis reference that were not assigned in FSUIPC and just managed a full flight with no transientclient errors.

Sorry, what does this mean?

[zkiwi]

For all axis that i was not setting up in FSUIPC i rescanned for each one and rather than allocating any event ( direct to FSUIPC) i selected the ignore axis option at the top right of the FSUIPC screen.

 

 

[John Dowson]

14 hours ago, zkiwi said:

i selected the ignore axis option at the top right of the FSUIPC screen.

But that will only ignore that axis for that assignment "session". When you close the assignments panel, it is again 'seen' by FSUIPC. You can see this by going into the axes assignment panel again, and you will see that the axes are again visible. So, this makes no difference when the axes assignment panel is closed.

[Fremmed]

On 9/9/2020 at 11:01 AM, John Dowson said:

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.

Still crashes on disconnect on my end.

[John Dowson]

3 hours ago, Fremmed said:

Still crashes on disconnect on my end.

Could you attach your FSUIPC7.log file please.

[roniish]

So, instead of it disconnecting it's actually crashing all together. Quite frequently also, I should add. It only happens on input (again, randomly). I did a flight from ESSA-EDLP and it crashed (just disappeared from the system tray) once on taxi at ESSA, as well as on final for EDLP. The controls were never touched until the AP was disconnected on final. 

I'll try to get back with some logs, and I'll have a look in the event viewer in windows as well. Just wanted to let you know for now. 

Edited September 12, 2020 by roniish

[Fremmed]

On 9/12/2020 at 2:57 PM, John Dowson said:

Could you attach your FSUIPC7.log file please.

Sure.

FSUIPC7-still-crashing.zip

[pilotjohn]

So it looks I am now also having this issue, and my previous post about "random disconnect" my in fact have been this behavior. I was flying, all control input stopped. I started to troubleshooting and noticed FSUIPC was no longer running. I saved the log, and saw the crash entry Event Viewer. In the log (attached) you can see FSUIPC reconnecting, but then it seems like it just crashed and that's the end of the log entries.

 

 

FSUIPC7 - Crash.log

[bertranda]

Hi all,

I don't had crash anymore for a long time. not sure what I did but I remember I change some lines in the simconnect.xml.

I changed all the "local" to "global" and reboot.

maybe it worth to try.

 

Best Regards.

[Pete Dowson]

1 hour ago, bertranda said:

I don't had crash anymore for a long time. not sure what I did but I remember I change some lines in the simconnect.xml.

I changed all the "local" to "global" and reboot.

Hmmm. That's a possibility. That may change it from using a "pipe" to using TCP/IP, which, though less efficient, might not block up as easily.

Only a guess, mind.

Pete

 

[zkiwi]

I have been using Global the entire time and are still getting transmitclientevent failures and FSUIPC attempting to reconnect and then crashing. It is always event 65763 that seems to crash it for me.

8873469 *** EVENT: Cntrl= 65561 (0x00010019), Param= 0 (0x00000000) PAUSE_TOGGLE
  9150422 TransmitClientEvent failed! (Event=65763, Param=1690, nGroup=0, fSame=0
  9150484 TransmitClientEvent failed! (Event=65763, Param=1409, nGroup=0, fSame=0
  9150547 TransmitClientEvent failed! (Event=65763, Param=1280, nGroup=0, fSame=0
  9150609 TransmitClientEvent failed! (Event=65763, Param=1133, nGroup=0, fSame=0
  9150672 TransmitClientEvent failed! (Event=65763, Param=1024, nGroup=0, fSame=0
  9150672 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
  9150750 TransmitClientEvent failed! (Event=65763, Param=1419, nGroup=0, fSame=0
  9150750 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
  9150906 SimConnect_Open succeeded
  9150922 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
  9150922 MSFS version = 11.0.282174.999
  9150922 Initialising SimConnect data requests now
  9150922 User Aircraft ID 1 supplied, now being used
  9151547 System time = 14/09/2020 11:06:25, Simulator time = 11:06:22 (23:06Z)
 

[Pete Dowson]

8 hours ago, zkiwi said:

I have been using Global the entire time and are still getting transmitclientevent failures and FSUIPC attempting to reconnect and then crashing.

Ah. Bang goes another theory! 😞

Pete

 

[John Dowson]

I have released a new version that contains some changes to help me track down this problem Could you please update.

Also note that one the TransmitClientEvent failures are received, disconnecting and re-initialising the SimConnect connection does not solve this problem. So unfortunately the only thing you can do at the moment is to restart FSUIPC7. I'm not sure why FSUIPC7 is crashing on the 3rd re-connect, but I don't think its worth investigating this issue at the moment.

If/when you experience this issue with the new version, could you show me you FSUIPC7.log file please (full).

[John Dowson]

I've connected my Track-IR now, and when using this I get the TranmitClientEvent failure. However, when this occurs the re-connect kicks in and seems to work for me:

Quote

   916469 FS Control Sent: Ctrl=65763, Param=2074 AXIS_AILERONS_SET
   916500 FS Control Sent: Ctrl=65763, Param=1651 AXIS_AILERONS_SET
   916531 FS Control Sent: Ctrl=65763, Param=1325 AXIS_AILERONS_SET
   916625 TransmitClientEvent failed! (Event=65763, Param=1608, nGroup=0, fSame=0
   916625 FS Control Sent: Ctrl=65763, Param=1608 AXIS_AILERONS_SET
   916953 TransmitClientEvent failed! (Event=65762, Param=-1151, nGroup=0, fSame=0
   917094 TransmitClientEvent failed! (Event=65762, Param=-864, nGroup=0, fSame=0
   917203 TransmitClientEvent failed! (Event=65762, Param=-598, nGroup=0, fSame=0
   918140 TransmitClientEvent failed! (Event=65763, Param=1909, nGroup=0, fSame=0
   918140 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
   918344 FS Control Sent: Ctrl=65763, Param=1909 AXIS_AILERONS_SET
   918344 FS Control Sent: Ctrl=65763, Param=2332 AXIS_AILERONS_SET
   918344 FS Control Sent: Ctrl=65763, Param=2061 AXIS_AILERONS_SET
   918390 SimConnect_Open succeeded
   918390 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
   918390 MSFS version = 11.0.282174.999
   918390 Initialising SimConnect data requests now
   918390 ---------------------- Joystick Device Scan -----------------------
   918406 Product= Saitek Pro Flight X-55 Rhino Throttle
   918406    Manufacturer= Madcatz
   918406    Serial Number= G0001630
   918406    Vendor=0738, Product=A215 (Version 0.119)
   918422    GUIDs returned for product: VID_0738&PID_A215:
   918422       GUID= {8B238AC0-45DE-11EA-800C-444553540000}
   918422       Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255
   918422 Product= Saitek Pro Flight X-55 Rhino Stick
   918422    Manufacturer= Madcatz
   918422    Serial Number= G0003298
   918422    Vendor=0738, Product=2215 (Version 0.87)
   918422    GUIDs returned for product: VID_0738&PID_2215:
   918422       GUID= {8B23B1D0-45DE-11EA-800E-444553540000}
   918422       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
   918422 -------------------------------------------------------------------
   918422    WARNING: Joystick ID 1 is duplicated in Registry
   918437 Device acquired for use:
   918437    Joystick ID = 0 (Registry okay)
   918437    0=Saitek Pro Flight X-55 Rhino Throttle
   918437    0.GUID={8B238AC0-45DE-11EA-800C-444553540000}
   918437 Device acquired for use:
   918437    Joystick ID = 1 (Registry okay)
   918437    1=Saitek Pro Flight X-55 Rhino Stick
   918437    1.GUID={8B23D8E0-45DE-11EA-800F-444553540000}
   918437 -------------------------------------------------------------------
   918453 User Aircraft ID 1 supplied, now being used
   918453 Exception 7 "NAME_UNRECOGNIZED", Ref 26, Index param 2 on AddData for AI, "ATC ID"
   918453 Exception 7 "NAME_UNRECOGNIZED", Ref 27, Index param 2 on AddData for AI, "ATC AIRLINE"
   918453 C:\Users\jldow\AppData\Roaming\Microsoft Flight Simulator\AutoSave Mon 122327.FLT
   918453 C:\USERS\JLDOW\APPDATA\ROAMING\MICROSOFT FLIGHT SIMULATOR\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
   918469 C:\USERS\JLDOW\APPDATA\ROAMING\MICROSOFT FLIGHT SIMULATOR\MISSIONS\CUSTOM\CUSTOMFLIGHT\CUSTOMFLIGHT.PLN
   918500 FS Control Sent: Ctrl=65763, Param=1636 AXIS_AILERONS_SET
   918531 FS Control Sent: Ctrl=65763, Param=1210 AXIS_AILERONS_SET
   918562 FS Control Sent: Ctrl=65763, Param=891 AXIS_AILERONS_SET
   918562 FS Control Sent: Ctrl=65763, Param=545 AXIS_AILERONS_SET
   918594 FS Control Sent: Ctrl=65763, Param=-709 AXIS_AILERONS_SET
   918609 FS Control Sent: Ctrl=65763, Param=-1031 AXIS_AILERONS_SET
   918672 FS Control Sent: Ctrl=65763, Param=-1308 AXIS_AILERONS_SET
   918703 FS Control Sent: Ctrl=65763, Param=-1803 AXIS_AILERONS_SET
   918734 FS Control Sent: Ctrl=65763, Param=-2124 AXIS_AILERONS_SET
...

 

[zkiwi]

On 9/14/2020 at 9:20 PM, John Dowson said:

I have released a new version that contains some changes to help me track down this problem Could you please update.

Also note that one the TransmitClientEvent failures are received, disconnecting and re-initialising the SimConnect connection does not solve this problem. So unfortunately the only thing you can do at the moment is to restart FSUIPC7. I'm not sure why FSUIPC7 is crashing on the 3rd re-connect, but I don't think its worth investigating this issue at the moment.

If/when you experience this issue with the new version, could you show me you FSUIPC7.log file please (full).

John,

Downloaded latest version and installed with a clean install ( deleted old folder and reallocated aileron, elevator, rudder and brake axis in FSUIPC and disabled in MSFS) and managed a 1.2 hour flight with no errors in the log file. It appears for me the faulting axis was elevator and ailerons looking at all the past log files. I will try another flight a little later today.

Thanks for the attention to this.

 

EDIT: Second flight - 1.5 hours and no errors, freezing, stutters or anything and nothing unusual in the log.

Second Edit: Another 1.6 hour flight and nil errors. It looks like this is now solved and working for me.

[John Dowson]

@zkiwi Ok, thanks for the update.

[John Dowson]

I think I've found the issue. Can you try the attached build please. Using this, I no longer get the TransmitClientEvent failures, even when using Track-IR:

FSUIPC7.exe

[Fremmed]

7 hours ago, John Dowson said:

I think I've found the issue. Can you try the attached build please. Using this, I no longer get the TransmitClientEvent failures, even when using Track-IR:

I think you did. No disconnects so far here. Thank you.

[zkiwi]

9 hours ago, John Dowson said:

I think I've found the issue. Can you try the attached build please. Using this, I no longer get the TransmitClientEvent failures, even when using Track-IR:

FSUIPC7.exe 586 kB · 16 downloads

Yes seems to have fixed it after 2.5 hour flight with multiple simconnect clients loaded and Trackir running. No errors experienced.