WideClient crashing repeatedly

[airforce2]

John;

I'm having a devil of a time trying to keep WideClient running.  I have it on a Win 11 laptop, for use with Pilot2ATC connected to MSFS running FSUIPC 7.3.20 on a Win 10 desktop.  I have used it successfully for years with FS9/X/P3D--this is my first attempt connecting to MSFS.  I am getting mostly silent CTDs where WideClient just disappears.  Many of the crashes show C0000374 heap corruption errors at offset 0x000ec67f.  One today, a memory access violation, was trapped by WideFS.  I have attached a file with the event log entries from a bunch of these crashes, as well as the log file from the event where the crash was trapped, and my WideClient.ini file.  Most of the crashes showed nothing in the log file after WideFS starts and connects (no end-of-session summary etc).

I've tried redownloading, uninstalling & reinstalling, UDP vs TCP, integrated ethernet vs WiFi vs a discrete USB ethernet adapter, elevated priority, run as admin, and have run sfc and dism to rule out Windows system corruption.  It keeps doing the same thing--it runs for a while and then crashes with a silent CTD.

Regards

Bob Scott

 

WideClient.ini WideClient - Copy (2).log Crash Event Logs.txt

[John Dowson]

Hi Bob,

17 hours ago, airforce2 said:

I have it on a Win 11 laptop, for use with Pilot2ATC connected to MSFS running FSUIPC 7.3.20 on a Win 10 desktop.  I have used it successfully for years with FS9/X/P3D--this is my first attempt connecting to MSFS.

So this is the same laptop that you use for WideClient with MSFS as you do for WideClient with P3D? If so, this is very strange as WideClient is the same (obviously), and the WideServer element in FSUIPC5/6 is the same as that in FSUIPC7.

I will look into your crash logs and WideClient log, but for now could you change to
    Log=Yes
in the [User] section of your WideClient.ini and show me the log file generated with this after a CTD, as well as the corresponding windows event. The log file will be large and need compressing/zipping before attaching. This should hopefully show the last things being written before the crash. Try a few times to see if this is consistent before posting the log.

if this doesn't reveal anything, we you can also try with Log=All, and Log=DebugAll

Thanks,

John

Edited June 21, 2023 by John Dowson
Changed from Log-Debug to Log=Yes

[airforce2]

John;

  No, this is the first use of WideClient on this laptop (and WideServer on the MSFS machine, as I've moved MSFS off to a different computer).

  I've now had several successful flights after changing ButtonScanInterval from 20 to 0 in the .ini file.  I have had several different HID controllers connected to the client laptop previously, but there are none presently connected, and the Windows "Devices and Printers" dialogue in the control panel shows none.  It's a little early to declare victory, still--I'll keep the logging on for the time being.

Thanks

Bob

[John Dowson]

1 minute ago, airforce2 said:

No, this is the first use of WideClient on this laptop

Ok - I expect that you would get the same with P3D...

1 minute ago, airforce2 said:

I've now had several successful flights after changing ButtonScanInterval from 20 to 0 in the .ini file. 

That's interesting.... I saw Thomas recommended this in a similar issue in another (old) thread...not sure why this would work at the moment, and I don't think it solved the OP's issue in the other thread...

3 minutes ago, airforce2 said:

It's a little early to declare victory, still--I'll keep the logging on for the time being.

Ok, let me know how it goes.

Thanks for the update. Regards,

John

[airforce2]

To close the loop on this, I've flown over 20 flights now with the ButtonScanInterval setting at zero--no more crashes in WideFS.

Regards

Bob