Jump to content
The simFlight Network Forums

WideClient terminates


Recommended Posts

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)
 

 

 

Link to comment
Share on other sites

8 hours ago, MartyReynolds said:

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. 

That's a bit odd. How does a client crash cause the sim on the other PC to crash?

The logs don't show anything useful I'm afraid. Apart from Windows updates, are you aware of any other changes made to your long-working setup? 

Can you take a look in the 'Event Viewer' (a standard Microsoft utility, should be installed)). Look under Windows Logs -> Applications, and see if there is an error report there for WideClient. If so, please post the details.

In case it is related to some specific exchange between the client and server could you also change the Wideclient INI to have Log=Yes instead of Log=Errors+.

Pete

Link to comment
Share on other sites

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>

Link to comment
Share on other sites

16 hours ago, MartyReynolds said:

Here is the Event View text reports

Unfortunately they are relating to a crash in the Windows NTDLL library, which is a collection of many small utility functions.

The log with more data should allow me to narrow it down, but after that i may need to put extra logging in the area this suggests may be responsible.

It sounds like a Windows update has changed something in one of the NTDLL functions WideClient uses making one of the parameters being supplied  or returned need a different size reserved (the errors being the usual "access violation").

Pete

 

Link to comment
Share on other sites

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

Link to comment
Share on other sites

What I did was just copied the first 5% of the log file and saved it as a text file. Then I copied about the last 5% of the log file and saved it as a second text file. These are attached. If you need the entire log file, let me know. I could email it to you directly or take the time to break it apart into segments. It is a pretty huge file.

WideClientLog_first part.txt WideClientLog_last part.txt

Link to comment
Share on other sites

19 hours ago, MartyReynolds said:

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

I see John helped with that.  ZIPping files is best for any and all uploads, but it is especially good for text files where you'll get excellent compression.

Can you tell me what this section is about:

    61250      Write: Offset=8624, Size=0001
            83 
    61250      Write: Offset=861C, Size=0002
            14 00 
    61250      Write: Offset=8620, Size=0002
            14 00 
    61250      Write: Offset=861E, Size=0002
            00 00 
    61250      Write: Offset=8622, Size=0002
            FB FF 

Are those offsets being written by one of your programs? What for? Or is that internal to SimAvionics?

I doubt if that question is related to the crash, though, as the same values and others are being written to those offsets regularly -- about 4 times per second, in fact.

I think I'm going to need a much fuller log. Could you reproduce again, but with "Log=DebugAll" instead of "Log=Yes". This time the log will become massive, so even with ZIP you might struggle. if so just include the last few Mb.

Pete

 

 

Link to comment
Share on other sites

1 hour ago, MartyReynolds said:

Okay, I've added a link to my OneDrive that should share the file (this is the large file that is from DebugAll)

Unfortunately that reveals nothing to identify anything different going on at the end compared to what is being done all the way through.

Tomorrow I will look to see where I can best add more more logging (or rather alternative logging) to try to pin down an area in the program, before then trying to go into finer detail. i'm afraid this will take several iterations.

I think this will still point to a bug in Windows introduced by recent updates. But maybe it will suggest a workaround until the next batch of updates fixes this bug and adds different ones.

Pete

 

Link to comment
Share on other sites

Please try this version of WideClient. Only change is that it tries to trap the error and record where it as at the time. You can change back to Log=Errors+ so the log isn't large.

WideClient716.zip

I'm not expecting miracles. Most of what WideClient does is handle the network transfers and that is asynchronous (i.e. windows network functions are busy doing things whilst WideClient carries on).  I suspect a bug in one of the Windows updates to the networking functions, but being asynchronous to what WideClient is doing I might never find any fix -- except possibly further Windows updates or disabling whatever recent changes they did.

I say this because all of the networking parts of WideClient have remained unchanged since Windows XP days. The other parts have long been protected by trapping crashes and logging them -- only the extensive networking side was free of that. Not sure why, but that's what I've changed in the attached version.

Yours is the only report of this problem at present so there's no way of narrowing it down to a "common factor". I use WideClient on an 8 PC network (I use ProSim, not SimAvionics, so WideClient usage is less, but used heavily for my other applications.

Pete

 

Link to comment
Share on other sites

Hi Pete, 

Attached is the log. I did a little more investigation and manually launched the Sim-A programs instead using a batch script. I did this in order to determine which, if any, of the Sim-A programs would cause WideClient to crash.

It looks like the Sim-A program called SysBoard_Interface is the application that does this. It appears to do it near the end of the launch process where it is establishing/finalizing communication with the new Flight Deck Solutions motorized B737 throttle quadrant. This new throttle is Ethernet based, so I am hypothesizing that there could be something in Sim-A code that might be sending a network communication to WideClient this is actually intended for the throttle quadrant. It sounds consistent with the WideClient detailed log that shows a communication that is outside of the normal FSUIPC offsets (if I understood correctly your earlier post).

Anyway, I'll pass this on to Mark at Sim-Avionics to see what he has to say. Also, I've attached the log file from the customized WideClient.exe you provided me. It does show that the last program is was connecting with was SysBoard_Interface.

This is also consistent with the timing of this issue, as it only has occurred in the past few months ... I presumed it was due to a Windows update, but it was about a few months ago that I added the motorized throttle from FDS to my sim.

Thanks Pete,

Marty

 

WideClient_Special.log

Link to comment
Share on other sites

12 hours ago, MartyReynolds said:

Anyway, I'll pass this on to Mark at Sim-Avionics to see what he has to say. Also, I've attached the log file from the customized WideClient.exe you provided me. It does show that the last program is was connecting with was SysBoard_Interface.

This is also consistent with the timing of this issue, as it only has occurred in the past few months ... I presumed it was due to a Windows update, but it was about a few months ago that I added the motorized throttle from FDS to my sim.

Okay. Good detective work! Please let me know what Mark suggests.

Pete

 

Link to comment
Share on other sites

Hi,

as you know already the Offsets you could even try which one it really is bey using Deny= in WideClient.ini under [User]

Quote

Deny=: This parameter can prevent all programs on the current client changing specified areas of the FSUIPC offsets. The format
is:
Deny=<offset>,<size>
where the offset is in hexadecimal and the size is a number of bytes in decimal. If you only want to watch one byte, you can omit
the ",<size>" part.
For example
Deny=2EE0,4
This makes WideClient prevent and changes to this location from this client. This one is the Flight Director switch.
You can Deny access to up to 8 different offset areas. Just list more <offset>,<size> parameters on the same line, thus:
Deny=04E0,88,48F0,10,5400,512,5600,256,5B00,128
which means 88 bytes at 0x04E0, 10 bytes at 0x48F0, and so on.
AllowShutdown=No: Set this to Yes only if you want to allow client

Thomas

Link to comment
Share on other sites

I actually have found an easy work-around that prevents WideClient from terminating which is now my routine. I simply launch all of the Sim-Avionics applications on my secondary computer, wait a few minutes for them to complete their initialization, then launch WideClient. When I do this, WideClient is stable and never self-terminates.

I wish I could find out what is exactly happening in Sim-A causing this, but I haven't  yet heard back from Mark Hastings. 

Link to comment
Share on other sites

1 hour ago, MartyReynolds said:

I actually have found an easy work-around that prevents WideClient from terminating which is now my routine. I simply launch all of the Sim-Avionics applications on my secondary computer, wait a few minutes for them to complete their initialization, then launch WideClient. When I do this, WideClient is stable and never self-terminates.

Hmm. That's very interesting. Like you, I wish I could understand why. But the only way I could work that out would be to use SimAvionics myself in the same configuration as you. Not really possible here I'm afraid. It took me several weeks work coding, testing and debugging, when I changed over from Project Magenta to ProSim for my system!

Pete

 

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.