MartyReynolds

Okay, I have the expanded WideClient log that I trapped last night. Oddly, WideClient only does this within the first ten minutes of launching. When I relaunch it for the second time, it never fails. The log file is 14.2 MB .... trying to find a way to get it to you since the upload here is limited to 4.88 MB

Hi Pete, Sorry I was not clear. The WideClient crash does NOT cause the sim on the other PC to crash. When I said "it would bring the sim down", I meant that the sim would stop working properly because of loss of communication between the Prepar3D PC and the Avionics (Sim-A) PC. I did change the WideClient INI to Log=Yes. Will look at the file immediately the next time WideClient terminates unexpectedly. The only change I have made to my simulator system is doing Windows Updates whenever they came out. I did look into Event Viewer and found about a dozen ERROR messages and INFORMATION messages tagged with WideClient. I've selected four of them for adding to this post. All of them appear to document an issue when the WideClient.exe process interacts with the Windows System 32 module: ntdll.dll. I am wondering if one of the Windows updates changed a network security setting that is intermittently causing this issue. Here is the Event View text reports (I tried to attach as a file, but the file uploaded to the this web forum appears to be not working😞 ====================================== WideClient Application Errors - Windows Logs - Event Viewer EVENT 1 (error) Log Name: Application Source: Application Error Date: 8/2/2020 8:08:38 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Avionics Description: Faulting application name: WideClient.exe, version: 7.1.5.6, time stamp: 0x5c52c65a Faulting module name: ntdll.dll, version: 10.0.19041.207, time stamp: 0x1bdbc4b8 Exception code: 0xc0000005 Fault offset: 0x0008532c Faulting process id: 0x2100 Faulting application start time: 0x01d669327a1f3b16 Faulting application path: D:\Sim-Avionics\WideFS\WideClient.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: a7162ea1-d2fc-4755-a929-375f67691c99 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-08-03T01:08:38.1895043Z" /> <EventRecordID>1022</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Avionics</Computer> <Security /> </System> <EventData> <Data>WideClient.exe</Data> <Data>7.1.5.6</Data> <Data>5c52c65a</Data> <Data>ntdll.dll</Data> <Data>10.0.19041.207</Data> <Data>1bdbc4b8</Data> <Data>c0000005</Data> <Data>0008532c</Data> <Data>2100</Data> <Data>01d669327a1f3b16</Data> <Data>D:\Sim-Avionics\WideFS\WideClient.exe</Data> <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data> <Data>a7162ea1-d2fc-4755-a929-375f67691c99</Data> <Data> </Data> <Data> </Data> </EventData> </Event> ========================================== EVENT 2 (error) Log Name: Application Source: Application Error Date: 8/2/2020 8:29:23 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Avionics Description: Faulting application name: WideClient.exe, version: 7.1.5.6, time stamp: 0x5c52c65a Faulting module name: ntdll.dll, version: 10.0.19041.207, time stamp: 0x1bdbc4b8 Exception code: 0xc0000005 Fault offset: 0x00048978 Faulting process id: 0xb18 Faulting application start time: 0x01d6693534a1b62d Faulting application path: D:\Sim-Avionics\WideFS\WideClient.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 0aa40011-b848-45bf-82df-acc0d0b5a4ee Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-08-03T01:29:23.3857484Z" /> <EventRecordID>1120</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Avionics</Computer> <Security /> </System> <EventData> <Data>WideClient.exe</Data> <Data>7.1.5.6</Data> <Data>5c52c65a</Data> <Data>ntdll.dll</Data> <Data>10.0.19041.207</Data> <Data>1bdbc4b8</Data> <Data>c0000005</Data> <Data>00048978</Data> <Data>b18</Data> <Data>01d6693534a1b62d</Data> <Data>D:\Sim-Avionics\WideFS\WideClient.exe</Data> <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data> <Data>0aa40011-b848-45bf-82df-acc0d0b5a4ee</Data> <Data> </Data> <Data> </Data> </EventData> </Event> =============================================== EVENT 3 (information) Log Name: Application Source: Windows Error Reporting Date: 8/2/2020 8:08:39 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Avionics Description: Fault bucket 1307489249861597080, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: WideClient.exe P2: 7.1.5.6 P3: 5c52c65a P4: ntdll.dll P5: 10.0.19041.207 P6: 1bdbc4b8 P7: c0000005 P8: 0008532c P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5762.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57F0.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57EE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57FF.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WideClient.exe_b06a8c9346301db607b4feeeeb31185e9e18637_44c4d7a9_9c864637-336d-43ce-ae59-53c91354db82 Analysis symbol: Rechecking for solution: 0 Report Id: a7162ea1-d2fc-4755-a929-375f67691c99 Report Status: 268435456 Hashed bucket: 29da281811931b030225228b9da47798 Cab Guid: 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-08-03T01:08:39.0899124Z" /> <EventRecordID>1023</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Avionics</Computer> <Security /> </System> <EventData> <Data>1307489249861597080</Data> <Data>1</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>WideClient.exe</Data> <Data>7.1.5.6</Data> <Data>5c52c65a</Data> <Data>ntdll.dll</Data> <Data>10.0.19041.207</Data> <Data>1bdbc4b8</Data> <Data>c0000005</Data> <Data>0008532c</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5762.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57D0.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57F0.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57EE.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57FF.tmp.txt</Data> <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WideClient.exe_b06a8c9346301db607b4feeeeb31185e9e18637_44c4d7a9_9c864637-336d-43ce-ae59-53c91354db82</Data> <Data> </Data> <Data>0</Data> <Data>a7162ea1-d2fc-4755-a929-375f67691c99</Data> <Data>268435456</Data> <Data>29da281811931b030225228b9da47798</Data> <Data>0</Data> </EventData> </Event> ========================================= EVENT 4 (information) Log Name: Application Source: Windows Error Reporting Date: 8/12/2020 4:09:22 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Avionics Description: Fault bucket 1727578094438615019, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: WideClient.exe P2: 7.1.5.6 P3: 5c52c65a P4: ntdll.dll P5: 10.0.19041.207 P6: 1bdbc4b8 P7: c0000005 P8: 00045c22 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE94.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF12.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF22.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF20.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF40.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WideClient.exe_848d9e49c4b6ba8a7855a731928913efa9f2d_44c4d7a9_b6e768bb-f885-404b-9210-7986a495224d Analysis symbol: Rechecking for solution: 0 Report Id: 327b463f-65d2-4eea-ab65-f4a2facdc83e Report Status: 268435456 Hashed bucket: 8d1b65ea41dfeed7e7f9971fb0c287eb Cab Guid: 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2020-08-12T21:09:22.9540600Z" /> <EventRecordID>1529</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Avionics</Computer> <Security /> </System> <EventData> <Data>1727578094438615019</Data> <Data>1</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>WideClient.exe</Data> <Data>7.1.5.6</Data> <Data>5c52c65a</Data> <Data>ntdll.dll</Data> <Data>10.0.19041.207</Data> <Data>1bdbc4b8</Data> <Data>c0000005</Data> <Data>00045c22</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCE94.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF12.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF22.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF20.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCF40.tmp.txt</Data> <Data>\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_WideClient.exe_848d9e49c4b6ba8a7855a731928913efa9f2d_44c4d7a9_b6e768bb-f885-404b-9210-7986a495224d</Data> <Data> </Data> <Data>0</Data> <Data>327b463f-65d2-4eea-ab65-f4a2facdc83e</Data> <Data>268435456</Data> <Data>8d1b65ea41dfeed7e7f9971fb0c287eb</Data> <Data>0</Data> </EventData> </Event>

Hi Peter, My flight simulator has been pretty much unchanged for months and running without any issues. I have a B737 sim using Prepar3D ver 4 on one computer and Sim-Avionics on a second, with WideFS7 interfacing the two computers. About a month ago I noticed that WideClient 7.15.6 would periodically terminate itself on the avionics computer, which would then bring the sim down. It could be rectified by restarting the WideClient.exe program. To troubleshoot, I did switch from TCP to UDP to see if that would make a difference. It did not. I also upgraded FSUIPC5 to FSUIPC6, but that didn't help either. I also found out that a Windows 10 update had changed network settings to require a password for local access (this took down the ActiveSky weather radar), but fixing this issue did not fix the issue of WideClient terminating itself (or crashing and being terminated by Windows). I will attach the WideServer .ini files & log files from my flight simulator computer that runs FSUIPC. I will also attach the WideClient .ini files & log files from my avionics computer that runs WideClient. I did notice a thread on the forum that was from another user that seems to be experiencing the same issue. Thanks Peter ... Marty Windows 10 Home 19041.388 FSUIPC6 ver 6.0.1.0 WideClient 7.15.6 Note: uploading files is not working, so I've attached the text of each file below ********* WideServer.DLL Log [version 7.076] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 11/08/20, Time 18:40:51.233: Server name is FLTSIM 15547 Initialising TCP/IP server 15562 Initialising UDP/IP server 16078 Broadcasting service every 1000 mSecs 17547 Connected to computer "AVIONICS" running WideClient version 7.156 (IP=192.168.2.151) UDP 3501359 Restarting service due to zero reception! 3560469 Closing down now ... Memory managed: Offset records: 2006 alloc, 2004 free Read buffer usage: 310523 alloc, 310523 free, max in session: 1 Write buffer usage: 226924 alloc, 226924 free, max in session: 1 Throughput maximum achieved: 32 frames/sec, 13970 bytes/sec Throughput average achieved for complete session: 13 frames/sec, 4054 bytes/sec Average receive rate from "AVIONICS": 87 frames/sec, 5540 bytes/sec ********* Log file closed ********* ********* WideServer.DLL Log [version 7.076] ********* Blocksize guide = 8192 (double allowed) Date (dmy): 12/08/20, Time 16:04:01.230: Server name is FLTSIM 15234 Initialising TCP/IP server 15234 Initialising UDP/IP server 16047 Broadcasting service every 1000 mSecs 29015 Connected to computer "AVIONICS" running WideClient version 7.156 (IP=192.168.2.151) UDP 380859 Restarting service due to zero reception! 843578 Connected to computer "AVIONICS" running WideClient version 7.156 (IP=192.168.2.151) UDP ********* WideClient Log [version 7.156] Class=FS98MAIN ********* Date (dmy): 12/08/20, Time 16:03:40.733: Client name is AVIONICS 78 LUA: "D:\Sim-Avionics\WideFS\Initial.LUA": not found 78 Attempting to connect now 78 Trying UDP/IP addr 192.168.2.150, port 8002 ... 78 UDP connectionless mode set up okay! 422 Connection made: receiving okay! 12250 New Client Application: "Server" (Id=1796) 14141 New Client Application: "SysBoard_Interface" (Id=4696) ********* WideClient Log [version 7.156] Class=FS98MAIN ********* Date (dmy): 12/08/20, Time 16:17:15.264: Client name is AVIONICS 125 LUA: "D:\Sim-Avionics\WideFS\Initial.LUA": not found 140 Attempting to connect now 140 Trying UDP/IP addr 192.168.2.150, port 8002 ... 140 UDP connectionless mode set up okay! 468 Connection made: receiving okay! 3812 New Client Application: "Server" (Id=1796) ; PLEASE SEE WideFS documentation for parameter details ; ===================================================== [Config] ServerIPAddr=192.168.2.150 Protocol=UDP Port=8002 Window=207,78,471,39 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=1000,1000 PollInterval=2000 Port2=9002 ReconnectMinutes=0 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ; ----------------------------------------------- [User] Log=Errors+ ; =============================================== [Sounds] Path=D:\WideClient\Sound\ Device1=Primary Sound Driver Device2=Speakers (Realtek High Definition Audio) Device3=LEN L1950wD (2- NVIDIA High Definition Audio) Device4=VA2259 Series (3- NVIDIA High Definition Audio) Device5=Realtek Digital Output (Realtek High Definition Audio)

I have a B737 sim with dual flight control yokes from Precision Flight Controls. Both controls each use an internal USB interface card that is identical. They don't have a unique serial number. When Windows 10 updates or just restarts, and USB devices are enumerated, it will sometimes shift the joystick assigned numbers and I think it applies the Windows game controller device calibration to the wrong device, since Windows cannot distinguish which PFC Yoke to apply the game controller calibration to. Even with the control yokes neutral, I observe control transferred from one control yoke to the other bu FSUIPC, despite control inputs on the desired yoke. PFC support says there is nothing they can do to make the devices unique, so that Windows will stop shifting assignments. I have tried assigning Letters in FSUIPC, but I then see additional numeric devices appear on the INI file, so it doesn't appear to be solving this. The only way I can get consistent behavior is to unplug the FO yoke, which then makes it a non-functional decoration. : ) My question is, I am considering ordering two Leo Bodnar USB interface cards and rewiring the control yokes to use these, since they have unique serial numbers and multiple cards appear to behave consistently under Windows 10. To do this I'll have to figure out how to wire up the Hall effect sensors they use since PFC doesn't use pots for position sensing. Before I did this, I would like to ask your opinion on whether or not this might solve the issue - i.e. does Windows 10 and FSUIPC look at joystick interface card serial numbers in order to prevent shifting assignments (even though the name of the device would be the same i.e. BU0836A)? Thanks - Marty

Thanks Pete. Changing the delta values back to default totally resolved the issue. I had tried to widen the delta a bit and I think the process of doing this resulted in accidentally changing one of the elevators to a delta of 1. Marty

Hi Pete, I have dual unlinked PFC control yokes and rudder pedals (recently purchased) for my B737NG sim running Sim-Avionics. I have set up my second set of flight controls (for the FO side) as recommended in your Advanced Users Guide method 2 (same method as recommended the Peter & Steve Cos at Flight Deck Solutions). The issue I am seeing is regarding when FSUIPC decides to determine which flight control is controlling. I understand it does this by looking at which control was moved and is registering the largest deflection from neutral or zero. When I test this with the ailerons and rudders, it works perfectly. When I test it with the elevators, I have noticed that it only works when the desired new active flight control is initially pushed forward (nose down). When the newly active control is initially pulled backward (nose up), it will never "take control", even if the control yoke is pulled back to maximum deflection. To make this clear in case there is confusion, let me give a scenario. The CA yoke is active and is being used to fly the aircraft. If the CA yoke is slowly released to the neutral position so that the FO yoke can be used to fly the aircraft. If the initial control input to the FO yoke is nose up (pulling the yoke back), the elevators do not move and remain in neutral position irregardless if the yoke is pulled fully back. However at anytime the FO yoke is pushed nose down forward of neutral, FSUIPC then catches that yoke and activates it as the controlling yoke. This issue does not exist if the initial control input to the FO yoke is a nose down (pushing the yoke forward). FSUIPC immediately makes the FO elevator control active and controlling in that case, and works as expected. Also, this issue does not occur with either aileron or rudder pedal input. They work normally as per your documentation. I have attempted troubleshooting by verifying Windows calibration of the USB Game Controllers for the PFC yokes. It is fine. I also have only calibrated in FSUIPC the CA yoke per FDS instructions, but when I look at the raw and output values for each yoke, they are almost identical (both yokes purchase from PFC within the last year). I am wondering if this might be a minor bug in the code that is looking at maximum deflection for the elevator axis. I can imagine that the code should be taking an absolute value of the axis value and comparing the absolute value of one control to the other. Perhaps this absolute value step was omitted? I am using FSUIPC v5.153. Most recent version of Prepar3Dv4. I did NOT install PFChid64.dll as reading the documentation, it appears this is for more complex PFC hardware and would not apply to hardware that is essentially nothing more than a USB game controller joystick device. I have attached the FSUIPC5.Joyscan.csv, FSUIPC5.ini, and FSUIPC5.log. Finally, every once and awhile I can get it to work normally with the elevators. I am thinking that this is dependent on when the neutral resting position of the yoke control changes slightly and ends up with a slightly negative raw value. This might also be consistent with the software code having a minor bug when comparing the positive and negative numbers. Thanks, Marty Reynolds FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log