FSUIPC7 intermittent disconnects: TransmitClientEvent failures

[pilotjohn]

I just had another one of these events with the latest build... TransmitClientEvent failed, and an eventual crash of FSUIPC; logs attached (1).

Also, on restart input was not working until I visited Axes and clicked Ok; logs for this also attached (2).

 

logs.zip

[Thomas Richter]

Hi,

why posting this in two different threads, that is confusing for no reason ??

you might first fix the controller problem in your registry.

      109 System time = 20/09/2020 17:22:28
      109 FLT path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
      188 -------------------------------------------------------------------
      203 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      297 FS path = "C:\Users\janos\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\"
      313 ---------------------- Joystick Device Scan -----------------------
      313 Product= vJoy - Virtual Joystick
      313    Manufacturer= Shaul Eizikovich
      313    Serial Number= 2.1.9
      313    Vendor=1234, Product=BEAD (Version 2.25)
      328    GUIDs returned for product: VID_1234&PID_BEAD:
      328       GUID= {675FFD60-DD8E-11EA-8004-444553540000}
      328       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      328       GUID= {67604B80-DD8E-11EA-800A-444553540000}
      328       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      328       GUID= {67602470-DD8E-11EA-8006-444553540000}
      328       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      328       GUID= {67602470-DD8E-11EA-8008-444553540000}
      328       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      328       GUID= {67607290-DD8E-11EA-800C-444553540000}
      328       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      328       GUID= {675FD650-DD8E-11EA-8002-444553540000}
      328       Details: Btns=32, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R32767,U32767,V32767,X32767,Y32767,Z32767
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
      328 Product= VirtualFly - RUDDO+
      328    Manufacturer=                             
      328    Vendor=16D0, Product=0DA3 (Version 0.2)
      328    GUIDs returned for product: VID_16D0&PID_0DA3:
      328       GUID= {225074A0-E19B-11EA-8001-444553540000}
      328       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U4096,V4096,X4096,Y0,Z0
      328 Product= VirtualFly - YOKO+ 
      328    Manufacturer=                             
      328    Vendor=16D0, Product=0DA0 (Version 0.2)
      328    GUIDs returned for product: VID_16D0&PID_0DA0:
      328       GUID= {25CD3F50-E19B-11EA-8002-444553540000}
      328       Details: Btns=7, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X4096,Y4096,Z0
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
. . .
      344 -------------------------------------------------------------------
      344    WARNING: Joystick ID 6 is duplicated in Registry
      359    WARNING: Joystick ID 7 is duplicated in Registry
      375    WARNING: Joystick ID 8 is duplicated in Registry
      484    WARNING: Joystick ID 10 is duplicated in Registry
      484    WARNING: Joystick ID 11 is duplicated in Registry
      500 Device acquired for use:
      500    Joystick ID = 3 (Registry okay)
      500    3=vJoy Device
      500    3.GUID={675FFD60-DD8E-11EA-8004-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 4 (Registry okay)
      500    4=vJoy Device
      500    4.GUID={67604B80-DD8E-11EA-800A-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 5 (Registry okay)
      500    5=vJoy Device
      500    5.GUID={67602470-DD8E-11EA-8006-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 6 (Registry okay)
      500    6=vJoy Device
      500    6.GUID={67602470-DD8E-11EA-8008-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 7 (Registry okay)
      500    7=vJoy Device
      500    7.GUID={67607290-DD8E-11EA-800C-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 8 (Registry okay)
      500    8=vJoy Device
      500    8.GUID={675FD650-DD8E-11EA-8002-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 2 (Registry okay)
      500    2=VirtualFly - RUDDO+
      500    2.GUID={225074A0-E19B-11EA-8001-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 10 (Registry okay)
      500    10=VirtualFly - YOKO+
      500    10.GUID={25CD3F50-E19B-11EA-8002-444553540000}
      500 Device acquired for use:
      500    Joystick ID = 11 (Registry okay)
      500    11=VirtualFly - TQ6+
      500    11.GUID={F2A26C20-E19C-11EA-8003-444553540000}

Thomas

[John Dowson]

As Thomas says, you should try and correct your registry entries, but I don't think this is related to your problem.

Your log shows an earlier failure from which it recovered:
 

Quote

 

  ...
  9297906 TransmitClientEvent failed! (Event=65763, Param=-247, nGroup=0, fSame=0
  9297953 TransmitClientEvent failed! (Event=65763, Param=-256, nGroup=0, fSame=0
  9300969 TransmitClientEvent failed! (Event=65763, Param=-294, nGroup=0, fSame=0
  9301094 TransmitClientEvent failed! (Event=65763, Param=-352, nGroup=0, fSame=0
  9301203 TransmitClientEvent failed! (Event=65763, Param=-409, nGroup=0, fSame=0
  9301203 **** Too many TransmitClientEvent errors received! Re-connecting now ... ****
  9301625 **** SimConnect open event not received in required time limit: Re-connecting now...
  9302031 SimConnect_Open succeeded
  9302031 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
  9302031 MSFS version = 11.0.282174.999
  9302031 Initialising SimConnect data requests now
  9302031 ---------------------- Joystick Device Scan -----------------------
  ...

 

I've noticed TransmitClientEvent being used in another place on the same thread, so this could be interfering, but I would need to see you SimConnect.log to verify,
For now, could you try the attached version and let me know how you get on. If you get the same error with this version, could you reactivate SimConnect logging (as explained earlier in this thread) and show me the SimConnect log file(s) when this issue occurs. Thanks.
FSUIPC7.exe

[pilotjohn]

3 hours ago, John Dowson said:

As Thomas says, you should try and correct your registry entries, but I don't think this is related to your problem.

Your log shows an earlier failure from which it recovered:
 

I've noticed TransmitClientEvent being used in another place on the same thread, so this could be interfering, but I would need to see you SimConnect.log to verify,
For now, could you try the attached version and let me know how you get on. If you get the same error with this version, could you reactivate SimConnect logging (as explained earlier in this thread) and show me the SimConnect log file(s) when this issue occurs. Thanks.
FSUIPC7.exe

Do you mean try to find them in the registry and clean them up? I'll enabled SimConnect and will keep you posted when it happens again. 

[John Dowson]

3 hours ago, pilotjohn said:

Do you mean try to find them in the registry and clean them up?

Yes. It may be easier to disconnect your devices, remove all entries (back-up your registry first), and then re-connect them to get the entries regenerated. Make sure you are using the "JoyLetters"  facilities first. If you don't know what this is, just set:
    AutoAssignLetters=Yes
in the [JoyNames] section of your FSUIPC7.ini file.

[pilotjohn]

Any suggestion on what/where to delete these from? I think these were being added by vJoy during install/uninstalls.

[pilotjohn]

I'm supposed to have 6 vJoy devices, which it seems like I have. I can complete uninstall and re-install vJoy,  but not sure it will clean up the registry completely.

[pilotjohn]

20 hours ago, pilotjohn said:

Any suggestion on what/where to delete these from? I think these were being added by vJoy during install/uninstalls.

I managed to completely clean up and reinstall vJoy. I'll report back when this error occurs again.

[John Dowson]

4 minutes ago, pilotjohn said:

I managed to completely clean up and reinstall vJoy. I'll report back when this error occurs again.

Ok, that's good. Make sure you are using the latest version I posted earlier in this thread. 

[N987PL]

Just had issue where I was able to see the axis' connected under axis, but when trying to go to Joystick calibration, the axis didn't seem to be connected.  Log attached.

FSUIPC7.log PFCcom64.log PFChid64.log

[John Dowson]

Just now, N987PL said:

Just had issue where I was able to see the axis' connected under axis, but when trying to go to Joystick calibration, the axis didn't seem to be connected.  Log attached.

Why are you posting in a thread for TransmitClientEvent failures when clearly this has nothing to do with your issue? It is difficult for me to investigate issues when people cross post. Please make sure that you are experiencing the issue identified in the thread, otherwise find another appropriate thread, if available, and if not create a new thread.

You are also using both the PFCcom and PFChid drivers. Do you need both?

And what 'axis' are you referring to? Is it configured and used by FSUIPC, or is it configured via one of the PFC drivers?

Your PFChid64.log also shows various errors, and is using some sort of macro file (PFC.mcro) which I know nothing about.

I'm sorry, but not having any PFC devices or knowing how those drivers work in conjunction with FSUIPC, I really cannot advise on this. I suggest you start a new topic for this with an appropriate title (including the PFC device/driver you are having issues with) , and maybe someone else who uses such PFC devices may be able to help.

 

[John Dowson]

13 minutes ago, N987PL said:

Just had issue where I was able to see the axis' connected under axis, but when trying to go to Joystick calibration

Also, you cannot see the axis under calibration unless it is also assigned in the assignments tab. If not assigned, you can still see the movements in the axis tab, but you cannot calibrate or een movements in the calibration tab unless it is assigned in FSUIPC.

Also, be careful that it is not also assigned and calibrated in the PFC driver. Depending upon which one you are using, the driver may be sending the axis values direct to the sim and bypassing FSUIPC. I believe there is an option in the driver to changes this, so you can assign and calibrate in FSUIPC. But, you cannot assign on the driver and calibrate in FSUIPC.

There are many threads on PFC devices at the moment. Maybe review them before posting again.

[pilotjohn]

Well... I finally managed to catch this in the act again (FSUIPC crash) with the latest FSUIPC and 1.9.3.0, while also having SimConnect logging on. All logs and settings attached.

 

logs.zip

[Thomas Richter]

Hi,

just looked only at the INI file but there are some strange lines in [Buttons} section !?

Quote

[Buttons]
PollInterval=25
ButtonRepeat=25,10
5=RD,2,C65615,0     -{ELEV_TRIM_UP}-
6=RD,1,C65607,0     -{ELEV_TRIM_DN}-
7=RD,4,C66277,0     -{AILERON_TRIM_RIGHT}-
8=RD,3,C66276,0     -{AILERON_TRIM_LEFT}-
9=HD,32,K38,9     -{Key press: shft+Up}-
10=HD,34,K39,9     -{Key press: shft+Right}-
11=HD,36,K40,9     -{Key press: shft+Down}-
12=HD,38,K37,9     -{Key press: shft+Left}-
13=PD,6,K32,10     -{Key press: ctl+Space}-
15=HD,39,K38,9     -{Key press: shft+Up}-
16=HD,39,K37,9     -{Key press: shft+Left}-
17=HD,33,K38,9     -{Key press: shft+Up}-
18=HD,33,K39,9     -{Key press: shft+Right}-
19=HD,35,K40,9     -{Key press: shft+Down}-
20=HD,35,K39,9     -{Key press: shft+Right}-
21=HD,37,K40,9     -{Key press: shft+Down}-
22=HD,37,K37,9     -{Key press: shft+Left}-
23=PG,2,C65752,0     -{PARKING_BRAKES}-
24=PL,14,C66079,0     -{GEAR_UP}-
25=PL,9,C66080,0     -{GEAR_DOWN}-
26=PL,13,C65759,0     -{FLAPS_DECR}-
27=PL,8,C65758,0     -{FLAPS_INCR}-
28=PF,13,C66241,1     -{TOGGLE_MASTER_BATTERY}-
29=PF,11,C66241,2     -{TOGGLE_MASTER_BATTERY}-
30=PF,7,C66363,0     -{TOGGLE_ALTERNATOR1}-
31=PF,5,C66364,0     -{TOGGLE_ALTERNATOR2}-
32=W2E80=0 PF,1,C66701,1     -{AVIONICS_MASTER_SET}-
1032=W2E80=1 PF,1,C66701,0     -{AVIONICS_MASTER_SET}-
33=W2E80=0 PF,3,C66701,1     -{AVIONICS_MASTER_SET}-
1033=W2E80=1 PF,3,C66701,0     -{AVIONICS_MASTER_SET}-
34=PF,6,C66704,0     -{APU_STARTER}-
35=PF,2,C66705,0     -{APU_OFF_SWITCH}-
36=PF,12,C67486,0     -{Custom control: <67486>}-
37=PG,14,C66340,0     -{TOGGLE_ELECT_FUEL_PUMP1}-
38=PG,10,C66341,0     -{TOGGLE_ELECT_FUEL_PUMP2}-
39=W0609=0 RG,13,C66400,4     -{MAGNETO1_SET}-
1039=W0609>0 PG,13,C66300,0     -{TOGGLE_STARTER1}-
40=W0609=0 RG,11,C66401,4     -{MAGNETO2_SET}-
1040=W0609>0 PG,11,C66301,0     -{TOGGLE_STARTER2}-
41=PG,8,C65930,0     -{MAGNETO1_BOTH}-
1041=PG,8,C66717,0     -{TURBINE_IGNITION_SWITCH_TOGGLE}-
42=PG,6,C65936,0     -{MAGNETO2_BOTH}-
1042=PG,6,C66717,0     -{TURBINE_IGNITION_SWITCH_TOGGLE}-
43=PG,3,C65927,0     -{MAGNETO1_OFF}-
44=PG,1,C65933,0     -{MAGNETO2_OFF}-
45=PG,9,C65956,0     -{FUEL_SELECTOR_ALL}-
46=PG,4,C65955,0     -{FUEL_SELECTOR_OFF}-
47=PG,5,C66517,0     -{FUEL_SELECTOR_2_ALL}-
48=PG,0,C66516,0     -{FUEL_SELECTOR_2_OFF}-
49=PL,2,C65853,0     -{SPOILERS_ARM_TOGGLE}-
50=RL,12,C1010,0     -{}-
51=RL,7,C1011,0     -{}-
52=PL,4,C66297,0     -{TOGGLE_AUTOFEATHER_ARM}-
53=PL,3,C66287,0     -{TOGGLE_PROPELLER_SYNC}-
54=RL,6,C66329,0     -{INC_COWL_FLAPS1}-
55=RL,5,C66331,0     -{INC_COWL_FLAPS2}-
56=RL,1,C66330,0     -{DEC_COWL_FLAPS1}-
57=RL,0,C66332,0     -{DEC_COWL_FLAPS2}-
58=PH,14,C66579,0     -{TOGGLE_CABIN_LIGHTS}-
59=PH,13,C65750,0     -{PANEL_LIGHTS_TOGGLE}-
60=PH,12,C66719,0     -{CABIN_SEATBELTS_ALERT_SWITCH_TOGGLE}-
61=PH,11,C66377,0     -{TOGGLE_RECOGNITION_LIGHTS}-
62=PH,9,C66239,0     -{TOGGLE_BEACON_LIGHTS}-
63=PH,8,C66379,0     -{TOGGLE_NAV_LIGHTS}-
64=PH,7,C66240,0     -{TOGGLE_TAXI_LIGHTS}-
65=PH,6,C65751,0     -{LANDING_LIGHTS_TOGGLE}-
66=PH,5,C65560,0     -{STROBES_TOGGLE}-
67=PH,3,C65858,0     -{PITOT_HEAT_TOGGLE}-
68=PH,2,C66484,0     -{ANTI_ICE_TOGGLE_ENG1}-
69=PH,1,C66338,0     -{TOGGLE_PROPELLER_DEICE}-
70=PH,0,C66337,0     -{TOGGLE_STRUCTURAL_DEICE}-
71=RJ,1,C65883,0     -{KOHLSMAN_INC}-
72=RJ,0,C65884,0     -{KOHLSMAN_DEC}-
73=PK,3,C65860,0     -{AUTO_THROTTLE_ARM}-
74=RJ,10,C65637,0     -{COM_RADIO_WHOLE_INC}-
75=RJ,7,C65636,0     -{COM_RADIO_WHOLE_DEC}-
76=RJ,9,C65639,0     -{COM_RADIO_FRACT_INC}-
77=RJ,6,C65638,0     -{COM_RADIO_FRACT_DEC}-
78=PJ,5,C66372,0     -{COM_STBY_RADIO_SWAP}-
79=RJ,16,C66437,0     -{COM2_RADIO_WHOLE_INC}-
80=RJ,13,C66436,0     -{COM2_RADIO_WHOLE_DEC}-
81=RJ,15,C66440,0     -{COM2_RADIO_FRACT_INC}-
82=RJ,12,C66438,0     -{COM2_RADIO_FRACT_DEC}-
83=PJ,11,C66444,0     -{COM2_RADIO_SWAP}-
84=RJ,22,C65641,0     -{NAV1_RADIO_WHOLE_INC}-
85=RJ,19,C65640,0     -{NAV1_RADIO_WHOLE_DEC}-
86=RJ,21,C65643,0     -{NAV1_RADIO_FRACT_INC}-
87=RJ,18,C65642,0     -{NAV1_RADIO_FRACT_DEC}-
88=PJ,17,C66448,0     -{NAV1_RADIO_SWAP}-
89=RJ,28,C65645,0     -{NAV2_RADIO_WHOLE_INC}-
90=RJ,25,C65644,0     -{NAV2_RADIO_WHOLE_DEC}-
91=RJ,27,C65647,0     -{NAV2_RADIO_FRACT_INC}-
92=RJ,24,C65646,0     -{NAV2_RADIO_FRACT_DEC}-
93=PJ,23,C66452,0     -{NAV2_RADIO_SWAP}-

Thomas

[John Dowson]

@Thomas Richter Those assignments are fine. He's just overloading the previous button press (adding '10' to the entry number, and using offset conditions.

These are the ones that should be removed as they are assigned to controls that no longer exist:
 

Quote

50=RL,12,C1010,0     -{}-
51=RL,7,C1011,0     -{}-

For the actual problem, I'm still not sure if the TrransmitClientEvent failures are due to MSFS or FSUIPC7. However, when this occurs FSUIPC7 should be able to disconnect and reconnect successfully without crashing. This looks to be a threading issue which I'll look into.

Btw, could you also activate 'Extras' logging. This will add a but more information (namely the thread id of the thread logging the message) which may be helpful.

Thanks,

[John Dowson]

Maybe you could also try with this added to the [General] section of your FSUIPC7.ini:
     UseAIClient=No

This will instruct FSUIPC to NOT use a separate SimConnect connection for AI, and will use the main connection instead (i.e. no change in functionality). This would help me to determine if the issue is related to multiple SimConnect connections interfering somehow.

[pilotjohn]

3 hours ago, John Dowson said:

@Thomas Richter Those assignments are fine. He's just overloading the previous button press (adding '10' to the entry number, and using offset conditions.

Yes, I'm just doing this for OCD reasons and to keep the numbering grouped in some way for compound buttons. 🙂

3 hours ago, John Dowson said:

These are the ones that should be removed as they are assigned to controls that no longer exist:

I assigned these, but haven't flow a plane to try them yet (I believe they're spoilers), and was not using them in this case (unless I accidentally pushed them).

3 hours ago, John Dowson said:

For the actual problem, I'm still not sure if the TrransmitClientEvent failures are due to MSFS or FSUIPC7. However, when this occurs FSUIPC7 should be able to disconnect and reconnect successfully without crashing. This looks to be a threading issue which I'll look into.

Btw, could you also activate 'Extras' logging. This will add a but more information (namely the thread id of the thread logging the message) which may be helpful.

Thanks,

Ack, will do.

[pilotjohn]

Just now, John Dowson said:

Maybe you could also try with this added to the [General] section of your FSUIPC7.ini:
     UseAIClient=No

This will instruct FSUIPC to NOT use a separate SimConnect connection for AI, and will use the main connection instead (i.e. no change in functionality). This would help me to determine if the issue is related to multiple SimConnect connections interfering somehow.

Ok, I'll start with Extras logging to not compound issues, until it occurs again (seems to be less frequent).

[pilotjohn]

Here's another instance of FSUIPC crashing (and me, just before landing on a bush strip in strong winds:). This has "extras" logging enabled.

I will now turn on UseAIClient=No.

 

logs.zip

[John Dowson]

Hi @pilotjohn

Those last logs are pretty interesting, thanks. Getting closer to the issue...

On 10/11/2020 at 11:19 PM, pilotjohn said:

I will now turn on UseAIClient=No.

I wouldn't bother with this now - remove if you have added (although it won't make much difference). Please try the following build, and keep logging of extras active:

FSUIPC7.exe

Let me know how it goes with that version, and post your FSUIPC7.log again if you get a crash. No need for the SimConnect logs for now.

Thanks,

John

[pilotjohn]

Ack, will report back when/if it occurs again.