FSUIPC7 intermittent disconnects: TransmitClientEvent failures

[roniish]

First of all, thanks a lot for creating FSUIPC7 for MSFS.

I have just downloaded the new update for MSFS (to stop the stuttering first and foremost) as well as the latest version of FSUIPC7.

 

After setting up all the axis as well as the buttons, I'm running into issues with FSUIPC just disconnecting within the sim. When I'm checking the application, it still says "Connected", and if I open up assignments -> axis (or buttons & switches), it still reacts to all the inputs I'm giving. However, all of a sudden they just stop interacting with MSFS. The physical controls (X56 HOTAS) are still working within MSFS' default axis and button setup. I can for example still pan with the joystick, but as I have removed all axis from the default controls within MSFS, it no longer responds to any movement inputs.

A restart of FSUIPC (File -> Exit and then a manual startup) results in the controls working again. I'm starting up the app with admin rights as well, at all times.

 

During a circuit with the Cessna 208, it happened once before starting up the aircraft, once when lining up and then once during the second circuit. So it would say it's frequent enough.

 

Any ideas? I guess you would like logs, but what kind of logs? Which ones do I enable? Let me know, so I can provide you with all the details you need.

Here is the log-file from the FSUIPC7-folder: https://workupload.com/file/uBAcW9mXcXm

See this image of the Console Log when the controls are not responding: https://ibb.co/R64Lz6n

Here is an image when it all of a sudden (when doing a waterlanding with the Icon A5) just stopped working: https://ibb.co/0VfVVdf

When the controls ARE responding, the console log is just being filled with whatever input I'm giving, as it should. Then all of a sudden, it's starting with the "TransmitClientEvent failed!". I've tried to check and see if I'm doing anything special, but it starts failing all different aircraft and in all different situations.

Ron

Edited September 2, 2020 by roniish

[Torkermax123]

Same here. FSUIPC sees the Axis but the Sim does not. Identical to Ron's situation, aircraft etc.

TransmitClientEvent failed!

[cellular55]

More or less same here.

I have noticed that sometimes, trying to configure the axis, the asis rescan does not respond and also after to have configured them, often the aircraft is not responding to the axis movements.

[John Dowson]

I have noticed this very occasionally - one or twice, and Thomas has also seen this a few times, but mainly after/during a long flight. I'll look into it, but this will take time as I find this difficult to reproduce. As a workaround for the time being, I'll look into automatically connecting after a certain (configurable) number of transmit failures, as we do for other simconnect failures. I'll post it here for you to test once done as it seems that you are getting this quite often.

John

 

[bertranda]

Hello,

I would like to add, that in my case, it is disconnected after about one minute of flight and remain disconnected untill fsuipc is closed and re-open.

when fsuipc launch again, after one minute it freeze again.

 

Best Regards.

 

[roniish]

11 hours ago, John Dowson said:

I have noticed this very occasionally - one or twice, and Thomas has also seen this a few times, but mainly after/during a long flight. I'll look into it, but this will take time as I find this difficult to reproduce. As a workaround for the time being, I'll look into automatically connecting after a certain (configurable) number of transmit failures, as we do for other simconnect failures. I'll post it here for you to test once done as it seems that you are getting this quite often.

John

 

Sounds great, John! Thanks a lot. I'll make sure to test it and get back to you with details.

[airforce2]

Seeing the same thing here.  Works for a while, then MSFS becomes unresponsive to inputs via FSUIPC.  I bring up the FSUIPC axis assignments window, which shows the axis inputs still moving, but the sim isn't getting them. 

In the log, there are hundreds of TransmitClientEvent failed! messages.

Edit: This was using the default C208 Caravan.

[Thomas Richter]

Hi,

can you check in Logging as well the Event (Non Axis) box. I see here that that (if I remember correct) happens/happened with specific AC's where i.e. an Event is constant sent, Cessna 208 sends constant Fuel_Selector_Set. That points already to an AC error from Asobo's side. Maybe you can as well name the AC you use when it happens.

  2956312 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2956312 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2956828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2956828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2957328 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2957328 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2957828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2957828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2958343 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2958343 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2958843 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2958843 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2959343 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2959343 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2959859 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2959859 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2960343 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2960343 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2960859 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2960859 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2961375 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2961375 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2961875 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2961875 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2962375 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2962375 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2962890 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2962890 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2963390 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2963390 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2963906 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2963906 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2964422 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2964422 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2964922 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2964922 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
  2965437 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
  2965437 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET

Thomas

[mariofsx]

FYI I have the same problem.

Thanks

Mario G.

[John Dowson]

A simconnect log file would be useful as well, although not sure how to generate one at the moment (i.e. where the SimConnect.ini goes). I'll look into this.

[John Dowson]

Could you try this version please. It should close the simconnect connection after 5 errors and attempt to reconnect.  You can  also add an ini parameter
    TransmitErrorsReconnect=n

to the [General] section of the ini to change the maximum number of errors received before reconnecting to  n (must be > 0).

Of course, it won't help much if you get this a lot, and you will lose control for a few seconds while it re-connects, so its not a solution but a temporary work-around for some folks.

I'll look into generating a simconnect log to track this down further, but as Thomas suggests it would be useful to know if this applies to just specific aircraft, and what is being transmitted/received before this occurs (by activating non-axis event logging)..

 

FSUIPC7.exe

[cbe0004]

I have the same issue. I have only tried with the TBM 930. I sat on the ramp for about 20 minutes setting up FSUIPC. Shortly after I got airborne the sim stopped seeing input from FSUIPC. 

John, I'll try that exe today. Thank you. 

[Bentree]

Same kind of issue here, after a while the throttle disconnects.

Bringing up the Axis tab in FSUIPC7 and moving the throttle seems to reactivate it.

This is in a Turboprop, in an airliner i have only one engine on the throttle....

Regards,

Ben

Edited September 4, 2020 by Bentree

[John Dowson]

3 minutes ago, Bentree said:

Bringing up the Axis tab in FSUIPC7 and moving the throttle seems to reactivate it.

Ok, thats interesting. Do you see the TransmitClientEvent failures in the log before you do this, and none afterwards?

[Bentree]

I will check that and come back to you.

[Bentree]

Just did a 20 minutes testflight in the C208, i am using the MCP Combo II Boeing style with Linda software.

The throttle disconnected when Linda reconnected, opening the FSUIPC7 axis tab and moving the throttle reconnected it.

In the log there was no sign of a Failure (none at all).

After reconnect it kept working.

Regards,

Ben

Edited September 4, 2020 by Bentree

[John Dowson]

20 minutes ago, Bentree said:

Just did a 20 minutes testflight in the C208, i am using the MCP Combo II Boeing style with Linda software.

The throttle disconnected when Linda reconnected, opening the FSUIPC7 axis tab and moving the throttle reconnected it.

In the log there was no sign of a Failure (none at all).

This sounds like an issue with LINDA then - maybe try the LINDA support forum.

[Bentree]

Just had all controls disconnected, all axis, all buttons.....

I will try another flight running only FSUIPC7, without LINDA.

In the FSUIPC.log no remark about any disconnect.....seems indeed has something to do with LINDA.

Keep you informed.

[Bentree]

Flew half an hour with only FSUIPC7 and disconnected LINDA.

No problem at all, so i will move over for my disconnections to the LINDA forum.

Thanks.

[Torkermax123]

I can't say with any certainty this solved anything but, I created a profile in MSFS for all controller and deleted all assignment and renamed it (Dowson Boys) and have not since had a disconnect issue. Performed 10 flights in the MSFS C208 with no issues. Possible bumping heads with MSFS assignments?

[John Dowson]

3 minutes ago, Torkermax123 said:

I created a profile in MSFS for all controller and deleted all assignment and renamed it (Dowson Boys) and have not since had a disconnect issue

Hmm, thats interesting. Hard to fathom why dual assignments would cause such issues though....

Thanks for the update.

[Torkermax123]

 I understand. It sure caused a mess in FSX etc having in sim assignments and FSUIPC assignment. I of course always disabled FS controllers. No option in MSFS.

[airforce2]

3 hours ago, Bentree said:

Same kind of issue here, after a while the throttle disconnects.

Bringing up the Axis tab in FSUIPC7 and moving the throttle seems to reactivate it.

This is in a Turboprop, in an airliner i have only one engine on the throttle....

This sounds like maybe the USB port powering down...check in Device Manager and make sure all your USB HID devices and hubs do not have "Allow the computer to turn off this device to save power" enabled.  This option gets turned back on regularly without asking me when Windows updates on my machines.

[Torkermax123]

3 hours ago, airforce2 said:

This sounds like maybe the USB port powering down.

Mine is disabled. 1st thing I always check.

[guenseli]

Just want to add, that I get the same issue

 

   538812 TransmitClientEvent failed! (Event=65763, Param=-256, nGroup=0, fSame=0
   538812 TransmitClientEvent failed! (Event=65762, Param=-674, nGroup=0, fSame=0
   538828 TransmitClientEvent failed! (Event=65763, Param=-511, nGroup=0, fSame=0
   538828 TransmitClientEvent failed! (Event=65762, Param=-512, nGroup=0, fSame=0
   538843 TransmitClientEvent failed! (Event=65762, Param=-256, nGroup=0, fSame=0
   538859 TransmitClientEvent failed! (Event=65762, Param=-63, nGroup=0, fSame=0
   538875 TransmitClientEvent failed! (Event=65763, Param=-256, nGroup=0, fSame=0
   538875 TransmitClientEvent failed! (Event=65762, Param=0, nGroup=0, fSame=0
   538890 TransmitClientEvent failed! (Event=65763, Param=0, nGroup=0, fSame=0
   538953 TransmitClientEvent failed! (Event=65763, Param=115, nGroup=0, fSame=0
   539000 TransmitClientEvent failed! (Event=65763, Param=0, nGroup=0, fSame=0
   539578 TransmitClientEvent failed! (Event=66387, Param=-14581, nGroup=0, fSame=0
   539703 TransmitClientEvent failed! (Event=66387, Param=-16384, nGroup=0, fSame=0

 

These are just some of hundreds as I was moving my axes a while, what is shown here as parameters, but no movement in the VC.

 

I had this twice relative shortly and in both cases I made a steep turn (with my saitek pedals) while rolling on ground. Coincidence or not.

Note: I haven't installed the provided exe from above. Just the original current FSUIPC

 

thx for having a look into it!