Jorge Diogo Posted September 27, 2006 Report Share Posted September 27, 2006 Since a few days ago I having som problems with wideclient. I connect the wideclient, the FS detects it ok, the wideclient window says connected but nothing works. I opn thw windows xp task manager and the performance is always on 100%. Next I try to close wideclient normally but it doesn't close. Anybody with same problem? regards Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 27, 2006 Report Share Posted September 27, 2006 Since a few days ago I having som problems with wideclient. I connect the wideclient, the FS detects it ok, the wideclient window says connected but nothing works. I opn thw windows xp task manager and the performance is always on 100%. Next I try to close wideclient normally but it doesn't close. What programs are you running on WideClient? what version of wideclient, WideServer, FSUIPC? Any Log files at all? What protocol are you using? And what did you change 'a few days ago'? Pete Link to comment Share on other sites More sharing options...
Jorge Diogo Posted September 27, 2006 Author Report Share Posted September 27, 2006 I don´t remeber changing anything :cry: I only use Active Sky with wideclient. The versions are the most recent for both client and server. I'm using TCP/IP protocol. here is the log files: ********* WideClient Log [version 6.70] Class=FS98MAIN ********* Date (dmy): 27/09/06, Time 14:41:46.852: Client name is SEGUNDO 591 Attempting to connect now 1472 Server = PRINCIPAL 1472 Trying TCP/IP host "PRINCIPAL" port 8002 ... 1472Okay, IP Address = 192.168.1.100 1482 Connection made okay! 34830 ****** End of session performance summary ****** 34830 Total time connected = 32 seconds 34830 Reception maximum: 1 frames/sec, 177 bytes/sec 34830 Reception average whilst connected: 1 frames/sec, 62 bytes/sec 34830 Transmission maximum: 0 frames/sec, 20 bytes/sec 34830 Transmission average whilst connected: 0 frames/sec, 24 bytes/sec 34830 Max receive buffer = 595, Max send depth = 1, Send frames lost = 0 34830 ********* Log file closed (Buffers: MaxUsed 2, Alloc 58 Freed 58 Refused 0) ********* and when I close FS the wideclient returns to the normal performance Tanks for your help Pete :) Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 27, 2006 Report Share Posted September 27, 2006 here is the log files: Eryou ran it for 30 seconds? When did you start ActiveSky? I think that alone takes more time than that to start, doesn't it? What did ActiveSky say? Where's the WideServer Log? What version of FSUIPC? Pete Link to comment Share on other sites More sharing options...
Jorge Diogo Posted September 27, 2006 Author Report Share Posted September 27, 2006 I'm using FSUIPC 3.70. The Active Sky only says "FS Disconnected". The 32 seconds was because I noticed that its not running well and I close it. here is a new log ********* WideClient Log [version 6.70] Class=FS98MAIN *********Date (dmy): 27/09/06, Time 15:32:55.815: Client name is SEGUNDO 601 Attempting to connect now 1372 Server = PRINCIPAL 1372 Trying TCP/IP host "PRINCIPAL" port 8002 ... 1372Okay, IP Address = 192.168.1.100 1372 Connection made okay! 38636 New Client Application: "ASv6" (Id=3252) 314302 FS closing down (param=ADBC), disconnecting 314302 ********* Interim performance summary ********* 314302 Total time connected so far = 311 seconds 314302 Reception maximum so far: 2 frames/sec, 211 bytes/sec 314302 Reception average whilst connected so far: 1 frames/sec, 50 bytes/sec 314302 Transmission maximum so far: 0 frames/sec, 33 bytes/sec 314302 Transmission average whilst connected so far: 0 frames/sec, 22 bytes/sec 314302 Max receive buffer = 601, Max send depth = 1, Send frames lost = 0 314302 **************** Individual client application activity **************** 314302 Client 3252 requests: 36 (Ave 0/sec), Data: 1944 bytes (6/sec), Average 54 bytes/Process 314302 *********************************************** 318588 Received shutdown offset code = ADBC 320651 Connection closed by server! 320651 Attempting to connect now 321662 Trying to locate server: Protocol not yet decided Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 27, 2006 Report Share Posted September 27, 2006 I'm using FSUIPC 3.70.The Active Sky only says "FS Disconnected". The 32 seconds was because I noticed that its not running well and I close it. Okay. So now we must find out why it thinks it is "disconnected". It is a shame it is not more informative. In the WideClient.INI file (which I assume you have not edited?) change the Log= line to read just "Log=Yes". This should show us what it is reading, if anything, which makes it think it is disconnected. However, this part of your original report worries me: I opn thw windows xp task manager and the performance is always on 100%. Next I try to close wideclient normally but it doesn't close. The last report of this type was from someone using FSexpand as well -- it appeared that FSexpand somehow stops Wideclient running correctly. Perhaps you'd like to peruse that thread too? http://forums.simflight.com/viewtopic.php?t=55723 That got to analysing huge logs, which showed that whilst Wideclient's Network threads were quite happily exchanging messages, and, in fact, the client application was too, there was no time left over for any windows message processing, which made Wideclient looked hung, and the client program inoperative. I currently don't know of anything else like that. But maybe checking the other things you have running may show a conflict somewhere? You say you've changed nothing, but obviously something has changed. Regards Pete Link to comment Share on other sites More sharing options...
JSkorna Posted September 28, 2006 Report Share Posted September 28, 2006 Hi, Do you have ASv6 set to start paused? If yes, then you need to click on the ASv6 Refresh button to complete the FS04 connection. Link to comment Share on other sites More sharing options...
Jorge Diogo Posted September 28, 2006 Author Report Share Posted September 28, 2006 Hi,Do you have ASv6 set to start paused? If yes, then you need to click on the ASv6 Refresh button to complete the FS04 connection. that part is obvious :) regards Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Jorge Diogo Posted September 28, 2006 Author Report Share Posted September 28, 2006 Pete, I dont use any other software tha ASv6 with Widefs. I already cleaned the PC, check the network, and everything works fine. I open the Wideclient and since it detects de Flight Simulator the cpu performance goes up to 100% :( here is my last connection log with ""Log=Yes" ********* WideClient Log [version 6.70] Class=FS98MAIN *********Date (dmy): 28/09/06, Time 14:30:06.770: Client name is SEGUNDO 471 Timing Thread Started 601 SendReq Thread Started 1683 Trying to locate server: Protocol not yet decided 235779 Server = PRINCIPAL 235779 Trying TCP/IP host "PRINCIPAL" port 8002 ... 235779Okay, IP Address = 192.168.1.100 236010 Sending computer name and requesting base data ... 236010 Button Thread Started 302866 FS closing down (param=ADBC), disconnecting 302866 ********* Interim performance summary ********* 302866 Total time connected so far = 64 seconds 302866 Reception maximum so far: 2 frames/sec, 204 bytes/sec 302866 Reception average whilst connected so far: 1 frames/sec, 55 bytes/sec 302866 Transmission maximum so far: 0 frames/sec, 21 bytes/sec 302866 Transmission average whilst connected so far: 0 frames/sec, 21 bytes/sec 302866 Max receive buffer = 601, Max send depth = 1, Send frames lost = 0 302866 *********************************************** 320761 Received shutdown offset code = ADBC 320761 FS closing down (param=ADBC), disconnecting 320761 ********* Interim performance summary ********* 320761 Total time connected so far = 64 seconds 320761 Reception maximum so far: 2 frames/sec, 204 bytes/sec 320761 Reception average whilst connected so far: 1 frames/sec, 55 bytes/sec 320761 Transmission maximum so far: 0 frames/sec, 21 bytes/sec 320761 Transmission average whilst connected so far: 0 frames/sec, 21 bytes/sec 320761 Max receive buffer = 601, Max send depth = 1, Send frames lost = 0 320761 *********************************************** 320852 Received shutdown offset code = ADBC 475174 Trying to locate server: Protocol not yet decided And my wideclient.ini : ; PLEASE SEE WideFS documentation for parameter details; ===================================================== [Config] Port=8002 Window=43,44,886,589 Visible=Yes ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 Port2=9002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 ServerIPAddr=192.168.1.100 ; ----------------------------------------------- [user] Log=yes ; =============================================== Sorry for the trouble :( regards Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 28, 2006 Report Share Posted September 28, 2006 I dont use any other software tha ASv6 with Widefs. ErI didn't ask that question. I asked if you used FSexpand (which is nothing to do with WideFS). It may also be relevant to know what else you have running on that PC -- not to do with FS, just other programs, background services, etc, running. Maybe there's some antivirus or firewall checker which is clobbering it. These sorts of problems are so rare, and so far each of the few there have been are different. In the end it all comes down to a process of elimination. In the end it may be necessary to go into the windows process list and kill each background process in turn until either the problem goes away or the system crashes. In the latter case, note that one, re-boot, and continue but leave that one running! This has found some culprits before. I think one was a Kensington mouse driver. Why I've no idea, but apparently it wasn't doing anything useful so it was easily dispensed with. here is my last connection log with ""Log=Yes" Sorry, but it's no use, as you can probably see. ASV6 never ran. In the previous log at least WideClient sees ASV6 connect: "38636 New Client Application: "ASv6" (Id=3252)". That didn't happen this time. If ASV6 never connects then there's nothing to log. It needs sorting at the ASV6 side. I need to know why ASV6 doesn't see the FS window class Wideclient presents. How did you make it connect the previous time? Or is it that after setting "Log=Yes" you forgot to run ASV6? BTW why are you specifying a ServerIPAddr? Surely the ServerName would be better? Or leave both off altogether if you are running winXP both ends. Pete Link to comment Share on other sites More sharing options...
kdundon Posted September 29, 2006 Report Share Posted September 29, 2006 Just a thought, I was having problems with AS6 connecting to FS with Wideserver and found in the options page of AS6 Build 523 under Graphics that I needed to check Enable WideFS Integration Mode and then all worked again. I never noticed this option before so maybe this is your problem. Ken Link to comment Share on other sites More sharing options...
Jorge Diogo Posted September 29, 2006 Author Report Share Posted September 29, 2006 Thanks, but the problem is not with ASv6. I've erased the folder where wideclient was and instal it in another place. The problem persists, I start wideclient and everything is ok, it stays "waiting for a connection". Since the FS is running, wideclient connects ok but the CPU usage goes to 100% and stays there all the time. Here is y last log: ********* WideClient Log [version 6.50] Class=FS98MAIN *********Date (dmy): 16/11/05, Time 22:10:48.082: Client name is SEGUNDO 812 Attempting to connect now 1583 Server = PRINCIPAL 1603 Trying TCP/IP host "PRINCIPAL" port 8002 ... 1603Okay, IP Address = 192.168.1.100 1613 Connection made okay! 17055 New Client Application: "ASV" (Id=3660) 18115379 ****** End of session performance summary ****** 18115389 Total time connected = 18112 seconds 18115389 Reception maximum: 41 frames/sec, 4581 bytes/sec 18115389 Reception average whilst connected: 12 frames/sec, 68 bytes/sec 18115389 Transmission maximum: 17 frames/sec, 5199 bytes/sec 18115389 Transmission average whilst connected: 2 frames/sec, 117 bytes/sec 18115389 Max receive buffer = 741, Max send depth = 32, Send frames lost = 0 18115389 **************** Individual client application activity **************** 18115389 Client 3660 requests: 68929 (Ave 3/sec), Data: 2945507 bytes (162/sec), Average 42 bytes/Process 18115389 ********* Log file closed (Buffers: MaxUsed 32, Alloc 311293 Freed 311293 Refused 0) ********* Pete, I check all the services that are running in the backgroun, I even google to know what they are but, nothing relevant :( Sorry for this, I don't know more what to do. Regards Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2006 Report Share Posted September 29, 2006 Here is y last log: ... 17055 New Client Application: "ASV" (Id=3660) ... 18115379 ****** End of session performance summary ****** 18115389 Total time connected = 18112 seconds 18115389 Reception maximum: 41 frames/sec, 4581 bytes/sec 18115389 Reception average whilst connected: 12 frames/sec, 68 bytes/sec 18115389 Transmission maximum: 17 frames/sec, 5199 bytes/sec 18115389 Transmission average whilst connected: 2 frames/sec, 117 bytes/sec 18115389 Max receive buffer = 741, Max send depth = 32, Send frames lost = 0 18115389 **************** Individual client application activity **************** 18115389 Client 3660 requests: 68929 (Ave 3/sec), Data: 2945507 bytes (162/sec), Average 42 bytes/Process 18115389 ********* Log file closed (Buffers: MaxUsed 32, Alloc 311293 Freed 311293 Refused 0) ********* This shows a healthy connection to FS, and the fact that there have been 2 transmissions back to the FS PC every second ON AVERAGE (max of 17), means that ASV6 or something is actively sending and receiving data. It looks like you did not have Log=Yes for this test, so apart from the good performance nothing else is useful in this log. Please enable the data logging. If you don't mind making a huge file, use "Log=Debugall" -- but for me to look at that you'll need to ZIP it up and send it to petedowson@btconnect.com. I check all the services that are running in the backgroun, I even google to know what they are but, nothing relevant :( How do you know they aren't relevant? Did you try killing them? I couldn't possibly hazard any guess without such a trial-and-error process! something in your system is evidently interfering with WideFS, you need to find out what. Pete Link to comment Share on other sites More sharing options...
cknipe Posted September 29, 2006 Report Share Posted September 29, 2006 Pete, I'm afraid to say, same thing here! The moment a application connects via WideClient, 100% CPU (WideClient idle's at 0% with no applications running). I have now tried with *only* FSRealTime (which is VERY trival as far as usuage goes).... WideClient.ini: [Config] ApplicationDelay=5000 Port=8002 Port2=9002 Protocol=TCP ServerIPAddress=192.168.1.10 ServerName=SUPERMAN Visible=Yes WaitForNewData=500 Window=32000,32000,112,27 ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 MailslotTiming=2000,1000 PollInterval=2000 ResponseTime=18 TCPcoalesce=No MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 [User] ;CloseReady1=Yes ;CloseReady2=Yes ;CloseReady3=Yes ;CloseReady4=Yes ;DelayReady1=30 ;DelayReady2=5 ;DelayReady3=5 ;DelayReady4=10 ;Log=Errors+ Log=Yes ;RunReady1=C:\Games\FS2004\ActiveSky\Modules\ASv6\ASv6.exe ;RunReady2=C:\Games\FS2004\AISmooth\AISmooth.exe ;RUNReady3=C:\Games\FS2004\FSRealTime\FSRealTime.exe ;RunReady4=C:\Games\FS2004\RCV4\RCV4.exe ShowRcFrameRate=Yes WideFS.ini: [Config] AdvertiseService=1 AutoRestart=5 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port=8002 Port2=9002 Protocol=TCP RestartTime=10 SendTimeout=15 TCPcoalesce=No [User] Log=Errors+ [ClientNames] 1=MICROMAN WideFS.log: ********* WideServer.DLL Log [version 6.70] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 29/09/06, Time 17:43:01.703: Server name is SUPERMAN 391703 Initialising TCP/IP server 391703 Initialising IPX/SPX server 391703 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 391703 Failed to start IPX/SPX Server 391703 Initialising UDP/IP server 392344 Broadcasting service every 1000 mSecs 403016 Restarting service due to total lack of use 403016 Failed to start IPX/SPX Server 674250 Incoming connection Accepted ok (skt=4136) TCP 674484 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 674969 Auto restart due to low frame rates! 674969 Failed to restart IPX/SPX Server! 674984 Incoming connection Accepted ok (skt=3972) TCP 675062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 680969 Auto restart due to low frame rates! 680969 Failed to restart IPX/SPX Server! 680984 Incoming connection Accepted ok (skt=4092) TCP 681109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 686969 Auto restart due to low frame rates! 686969 Failed to restart IPX/SPX Server! 687000 Incoming connection Accepted ok (skt=3944) TCP 687125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 692969 Auto restart due to low frame rates! 692969 Failed to restart IPX/SPX Server! 692984 Incoming connection Accepted ok (skt=3852) TCP 693172 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3852) TCP 698969 Auto restart due to low frame rates! 698969 Failed to restart IPX/SPX Server! 698984 Incoming connection Accepted ok (skt=3948) TCP 699031 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 704969 Auto restart due to low frame rates! 704969 Failed to restart IPX/SPX Server! 704984 Incoming connection Accepted ok (skt=4136) TCP 705031 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 710969 Auto restart due to low frame rates! 710969 Failed to restart IPX/SPX Server! 710984 Incoming connection Accepted ok (skt=3972) TCP 711125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 718312 Auto restart due to low frame rates! 718312 Failed to restart IPX/SPX Server! 718344 Incoming connection Accepted ok (skt=4160) TCP 718516 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 724969 Auto restart due to low frame rates! 724969 Failed to restart IPX/SPX Server! 724984 Incoming connection Accepted ok (skt=3944) TCP 725062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 730969 Auto restart due to low frame rates! 730969 Failed to restart IPX/SPX Server! 730984 Incoming connection Accepted ok (skt=4136) TCP 731109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 736969 Auto restart due to low frame rates! 736969 Failed to restart IPX/SPX Server! 737000 Incoming connection Accepted ok (skt=3948) TCP 737109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 742969 Auto restart due to low frame rates! 742969 Failed to restart IPX/SPX Server! 743000 Incoming connection Accepted ok (skt=4092) TCP 743094 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 748984 Auto restart due to low frame rates! 748984 Failed to restart IPX/SPX Server! 749016 Incoming connection Accepted ok (skt=3972) TCP 749141 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 758172 Auto restart due to low frame rates! 758172 Failed to restart IPX/SPX Server! 758281 Incoming connection Accepted ok (skt=4160) TCP 758656 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 765047 Auto restart due to low frame rates! 765047 Failed to restart IPX/SPX Server! 765078 Incoming connection Accepted ok (skt=3944) TCP 765156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 770969 Auto restart due to low frame rates! 770969 Failed to restart IPX/SPX Server! 771000 Incoming connection Accepted ok (skt=4136) TCP 771203 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 776969 Auto restart due to low frame rates! 776969 Failed to restart IPX/SPX Server! 777000 Incoming connection Accepted ok (skt=3948) TCP 777203 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 783000 Auto restart due to low frame rates! 783016 Failed to restart IPX/SPX Server! 783453 Incoming connection Accepted ok (skt=4092) TCP 783641 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 789016 Auto restart due to low frame rates! 789016 Failed to restart IPX/SPX Server! 789016 Incoming connection Accepted ok (skt=3972) TCP 789234 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 795000 Auto restart due to low frame rates! 795000 Failed to restart IPX/SPX Server! 795000 Incoming connection Accepted ok (skt=4160) TCP 795312 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 800984 Auto restart due to low frame rates! 800984 Failed to restart IPX/SPX Server! 801437 Incoming connection Accepted ok (skt=3944) TCP 801578 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 806984 Auto restart due to low frame rates! 806984 Failed to restart IPX/SPX Server! 807328 Incoming connection Accepted ok (skt=4136) TCP 807578 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 813016 Auto restart due to low frame rates! 813016 Failed to restart IPX/SPX Server! 813047 Incoming connection Accepted ok (skt=3948) TCP 813312 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 818984 Auto restart due to low frame rates! 819000 Failed to restart IPX/SPX Server! 819500 Incoming connection Accepted ok (skt=4092) TCP 819625 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 825000 Auto restart due to low frame rates! 825000 Failed to restart IPX/SPX Server! 825500 Incoming connection Accepted ok (skt=3972) TCP 825594 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 831516 Auto restart due to low frame rates! 831516 Failed to restart IPX/SPX Server! 831750 Incoming connection Accepted ok (skt=4160) TCP 831750 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 837000 Auto restart due to low frame rates! 837000 Failed to restart IPX/SPX Server! 837016 Incoming connection Accepted ok (skt=3944) TCP 837125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 842984 Auto restart due to low frame rates! 842984 Failed to restart IPX/SPX Server! 843016 Incoming connection Accepted ok (skt=4136) TCP 843109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 849000 Auto restart due to low frame rates! 849000 Failed to restart IPX/SPX Server! 849016 Incoming connection Accepted ok (skt=3948) TCP 849156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 854984 Auto restart due to low frame rates! 854984 Failed to restart IPX/SPX Server! 855469 Incoming connection Accepted ok (skt=4092) TCP 855703 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 861000 Auto restart due to low frame rates! 861000 Failed to restart IPX/SPX Server! 861016 Incoming connection Accepted ok (skt=3972) TCP 861156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 867000 Auto restart due to low frame rates! 867000 Failed to restart IPX/SPX Server! 867016 Incoming connection Accepted ok (skt=4160) TCP 867172 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 872984 Auto restart due to low frame rates! 872984 Failed to restart IPX/SPX Server! 873016 Incoming connection Accepted ok (skt=3944) TCP 873172 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 879000 Auto restart due to low frame rates! 879000 Failed to restart IPX/SPX Server! 879031 Incoming connection Accepted ok (skt=4136) TCP 879219 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 885000 Auto restart due to low frame rates! 885000 Failed to restart IPX/SPX Server! 885016 Incoming connection Accepted ok (skt=3976) TCP 885266 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 891000 Auto restart due to low frame rates! 891000 Failed to restart IPX/SPX Server! 891031 Incoming connection Accepted ok (skt=4092) TCP 891250 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 896984 Auto restart due to low frame rates! 897000 Failed to restart IPX/SPX Server! 897516 Incoming connection Accepted ok (skt=3944) TCP 897828 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 903000 Auto restart due to low frame rates! 903000 Failed to restart IPX/SPX Server! 903484 Incoming connection Accepted ok (skt=4160) TCP 903531 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 909000 Auto restart due to low frame rates! 909000 Failed to restart IPX/SPX Server! 909484 Incoming connection Accepted ok (skt=4288) TCP 909594 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4288) TCP 915000 Auto restart due to low frame rates! 915000 Failed to restart IPX/SPX Server! 915484 Incoming connection Accepted ok (skt=4136) TCP 915562 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 920984 Auto restart due to low frame rates! 920984 Failed to restart IPX/SPX Server! 920984 Incoming connection Accepted ok (skt=3976) TCP 921078 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 930062 Auto restart due to low frame rates! 930062 Failed to restart IPX/SPX Server! 930094 Incoming connection Accepted ok (skt=4092) TCP 930531 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 937000 Auto restart due to low frame rates! 937000 Failed to restart IPX/SPX Server! 937078 Incoming connection Accepted ok (skt=3944) TCP 937156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 943047 Auto restart due to low frame rates! 943047 Failed to restart IPX/SPX Server! 943047 Incoming connection Accepted ok (skt=4160) TCP 943187 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 949062 Auto restart due to low frame rates! 949062 Failed to restart IPX/SPX Server! 949109 Incoming connection Accepted ok (skt=3948) TCP 949344 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 955000 Auto restart due to low frame rates! 955000 Failed to restart IPX/SPX Server! 955047 Incoming connection Accepted ok (skt=4136) TCP 955359 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 960984 Auto restart due to low frame rates! 960984 Failed to restart IPX/SPX Server! 961281 Incoming connection Accepted ok (skt=3976) TCP 961281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 966984 Auto restart due to low frame rates! 966984 Failed to restart IPX/SPX Server! 967047 Incoming connection Accepted ok (skt=4092) TCP 967281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 972984 Auto restart due to low frame rates! 972984 Failed to restart IPX/SPX Server! 973016 Incoming connection Accepted ok (skt=3944) TCP 973281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 978984 Auto restart due to low frame rates! 979000 Failed to restart IPX/SPX Server! 979000 Incoming connection Accepted ok (skt=4160) TCP 979297 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 985000 Auto restart due to low frame rates! 985016 Failed to restart IPX/SPX Server! 985016 Incoming connection Accepted ok (skt=3948) TCP 985312 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 991000 Auto restart due to low frame rates! 991016 Failed to restart IPX/SPX Server! 991016 Incoming connection Accepted ok (skt=4136) TCP 991328 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 996984 Auto restart due to low frame rates! 996984 Failed to restart IPX/SPX Server! 997016 Incoming connection Accepted ok (skt=3976) TCP 997094 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 1003016 Auto restart due to low frame rates! 1003016 Failed to restart IPX/SPX Server! 1003016 Incoming connection Accepted ok (skt=4092) TCP 1003062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1009000 Auto restart due to low frame rates! 1009000 Failed to restart IPX/SPX Server! 1009484 Incoming connection Accepted ok (skt=3944) TCP 1009609 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 1015016 Auto restart due to low frame rates! 1015016 Failed to restart IPX/SPX Server! 1015016 Incoming connection Accepted ok (skt=4160) TCP 1015109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1021016 Auto restart due to low frame rates! 1021016 Failed to restart IPX/SPX Server! 1021531 Incoming connection Accepted ok (skt=3948) TCP 1021703 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 1027000 Auto restart due to low frame rates! 1027016 Failed to restart IPX/SPX Server! 1027016 Incoming connection Accepted ok (skt=4136) TCP 1027156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1033000 Auto restart due to low frame rates! 1033016 Failed to restart IPX/SPX Server! 1033016 Incoming connection Accepted ok (skt=3976) TCP 1033187 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 1044984 Auto restart due to low frame rates! 1044984 Failed to restart IPX/SPX Server! 1045000 Incoming connection Accepted ok (skt=4092) TCP 1045219 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1050984 Auto restart due to low frame rates! 1051000 Failed to restart IPX/SPX Server! 1051000 Incoming connection Accepted ok (skt=3944) TCP 1074000 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 1074984 Auto restart due to low frame rates! 1074984 Failed to restart IPX/SPX Server! 1075000 Incoming connection Accepted ok (skt=4160) TCP 1075078 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1080984 Auto restart due to low frame rates! 1080984 Failed to restart IPX/SPX Server! 1080984 Incoming connection Accepted ok (skt=3948) TCP 1081125 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3948) TCP 1087031 Auto restart due to low frame rates! 1087031 Failed to restart IPX/SPX Server! 1087031 Incoming connection Accepted ok (skt=4136) TCP 1087062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1092984 Auto restart due to low frame rates! 1093000 Failed to restart IPX/SPX Server! 1093016 Incoming connection Accepted ok (skt=3976) TCP 1106359 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3976) TCP 1106984 Auto restart due to low frame rates! 1106984 Failed to restart IPX/SPX Server! 1106984 Incoming connection Accepted ok (skt=4092) TCP 1107062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1112984 Auto restart due to low frame rates! 1113000 Failed to restart IPX/SPX Server! 1113422 Incoming connection Accepted ok (skt=3944) TCP 1113609 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3944) TCP 1119000 Auto restart due to low frame rates! 1119000 Failed to restart IPX/SPX Server! 1119031 Incoming connection Accepted ok (skt=4160) TCP 1119094 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1149016 Auto restart due to low frame rates! 1149031 Failed to restart IPX/SPX Server! 1150437 Incoming connection Accepted ok (skt=4820) TCP 1183141 Client socket unused for too long: removing (skt=4820) TCP 1183156 Incoming connection Accepted ok (skt=4820) TCP 1219391 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4820) TCP 1221250 Auto restart due to low frame rates! 1221250 Failed to restart IPX/SPX Server! 1221687 Incoming connection Accepted ok (skt=4136) TCP 1221812 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1227000 Auto restart due to low frame rates! 1227000 Failed to restart IPX/SPX Server! 1227000 Incoming connection Accepted ok (skt=4828) TCP 1227297 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1233000 Auto restart due to low frame rates! 1233000 Failed to restart IPX/SPX Server! 1233469 Incoming connection Accepted ok (skt=4092) TCP 1233562 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1239000 Auto restart due to low frame rates! 1239000 Failed to restart IPX/SPX Server! 1239047 Incoming connection Accepted ok (skt=4840) TCP 1239281 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4840) TCP 1244984 Auto restart due to low frame rates! 1244984 Failed to restart IPX/SPX Server! 1245016 Incoming connection Accepted ok (skt=4160) TCP 1245078 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4160) TCP 1251000 Auto restart due to low frame rates! 1251000 Failed to restart IPX/SPX Server! 1251016 Incoming connection Accepted ok (skt=4820) TCP 1251062 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4820) TCP 1257000 Auto restart due to low frame rates! 1257000 Failed to restart IPX/SPX Server! 1257453 Incoming connection Accepted ok (skt=4136) TCP 1286406 Client socket unused for too long: removing (skt=4136) TCP 1286422 Incoming connection Accepted ok (skt=4136) TCP 1304109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 1305000 Auto restart due to low frame rates! 1305000 Failed to restart IPX/SPX Server! 1316047 Failed to start IPX/SPX Server 1346781 Incoming connection Accepted ok (skt=4828) TCP 1347000 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1347000 Auto restart due to low frame rates! 1347000 Failed to restart IPX/SPX Server! 1347000 Incoming connection Accepted ok (skt=4088) TCP 1347234 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4088) TCP 1353000 Auto restart due to low frame rates! 1353000 Failed to restart IPX/SPX Server! 1353000 Incoming connection Accepted ok (skt=4840) TCP 1353234 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4840) TCP 1359000 Auto restart due to low frame rates! 1359000 Failed to restart IPX/SPX Server! 1359031 Incoming connection Accepted ok (skt=4824) TCP 1359266 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4824) TCP 1365000 Auto restart due to low frame rates! 1365000 Failed to restart IPX/SPX Server! 1365000 Incoming connection Accepted ok (skt=4820) TCP 1365266 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4820) TCP 1370984 Auto restart due to low frame rates! 1371000 Failed to restart IPX/SPX Server! 1371484 Incoming connection Accepted ok (skt=4092) TCP 1371578 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1376984 Auto restart due to low frame rates! 1376984 Failed to restart IPX/SPX Server! 1376984 Incoming connection Accepted ok (skt=4828) TCP 1377047 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1382984 Auto restart due to low frame rates! 1382984 Failed to restart IPX/SPX Server! 1383469 Incoming connection Accepted ok (skt=4088) TCP 1383609 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4088) TCP 1389000 Auto restart due to low frame rates! 1389016 Failed to restart IPX/SPX Server! 1389469 Incoming connection Accepted ok (skt=3972) TCP 1389641 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 1395016 Auto restart due to low frame rates! 1395016 Failed to restart IPX/SPX Server! 1395469 Incoming connection Accepted ok (skt=4824) TCP 1395625 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4824) TCP 1401937 Auto restart due to low frame rates! 1401937 Failed to restart IPX/SPX Server! 1401984 Incoming connection Accepted ok (skt=4828) TCP 1402187 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4828) TCP 1406984 Auto restart due to low frame rates! 1407000 Failed to restart IPX/SPX Server! 1407031 Incoming connection Accepted ok (skt=4092) TCP 1407109 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4092) TCP 1413000 Auto restart due to low frame rates! 1413000 Failed to restart IPX/SPX Server! 1413437 Incoming connection Accepted ok (skt=4840) TCP 1413672 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4840) TCP 1419031 Auto restart due to low frame rates! 1419031 Failed to restart IPX/SPX Server! 1419062 Incoming connection Accepted ok (skt=4088) TCP 1419156 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4088) TCP 1424984 Auto restart due to low frame rates! 1424984 Failed to restart IPX/SPX Server! 1425000 Incoming connection Accepted ok (skt=3972) TCP 1425203 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=3972) TCP 1430453 Error 10053: client socket disconnected at Client: removing (skt=3972) TCP Interesting how it still wants to use IPX, even though I have a protocol=tcp??? Even minutes after I closed WideClient, I still get messages from FSRealTime in my simulator as well. It seems there are *massive* delays between WideServer and WideClient as far as communications go... WideClient.log attached due to size... WideClientLog.zip Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2006 Report Share Posted September 29, 2006 Jorge, I received the "DebugAll" log, and this shows ASV6 connecting, but then simply looping on the initial operations -- the part in the FSUIPC_Open call it makes when it is establishing the connection. It is reading the validity check (okay0, and the version numbers of FSUIPC and of FS okay. But it simply loops on this, retrying every 2-3 seconds. I really don't know what it is doing -- I assume it is timing out, which means it is not getting the response back in sufficient time. The actual time spent in Wideclient in that period (3 seconds), to actually process the request, is only 1-10 mSecs in most cases. Something is stopping ASV6 getting the process sufficiently, so it isn't processing the messages. This, combined with your 100% utilisation observation seems to indicate a PC system which is simply not coping. Whether this is due to other processes or just a slow processor i am afraid I don't know. Did you tell me what system you use (processor, memory, windows version and so on)? What is your typical FS frame rate? Do you have the FS frame rate limiter set? The WideFS link is flawless and the exchanges are perfect. The problem lies in the client PC somewhere -- something is preventing correct multi-tasking. Regards, Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2006 Report Share Posted September 29, 2006 I'm afraid to say, same thing here! No it isn't. In jorge's case the connection is working perfectly, but something on the client Pc is preventing correct multi-tasking so that ASV6 isn't getting past the initialisation. All of Jorge's WideFS logs show the wideFS side working perfectly. In your case this is not occurring. You have a non-working connection. completely the opposite. It looks like it isn't working because it is continually restarting! 674484 Connected to computer "MICROMAN" running WideClient version 6.700 (skt=4136) TCP 674969 Auto restart due to low frame rates! WHY have you changed the AutoRestart value from its default? AutoRestart=0: This operates a facility to automatically restart the Server (forcing all clients to reconnect) if a low frame rate (below 5) is experienced for the specified number of seconds (with a minimum of 5). The frame rate here is the total frames per second managed for all connected clients added together, so and average of less than 5 fps for over 5 seconds indicates a problem. However, this attempt at fixing it is a bit of a sledgehammer and in general should be avoided. The defalut setting of 0 switches it off. Maybe i should delete that parameter as, especially when you first connect, there's so much being done 9programs loading, initial data exchanging, etc) that it is quite possible for the frame rate to be less than 5 for 5 seconds. But why have you changed it? In all cases if you have a problem, try reverting parameters to defaults. All the stuff has been "tuned" over many years and should really be left alone except under instruction for special cases. Interesting how it still wants to use IPX, even though I have a protocol=tcp??? It doesn't want to use IPX. you are reasding it wrong. The server always sets up services for TCP. SPX and UDP. It will retry all three each time it initialises. Pete Link to comment Share on other sites More sharing options...
cknipe Posted September 29, 2006 Report Share Posted September 29, 2006 My apologies then Pete, and sorry for stealing the thread it seems 8) Interestingly, I have not changed *anything* yet as far as configs go. Same WideServer, I've downgraded WideClient to 6.47 (The only one I have on CD) - NO problem WHAT SO EVER. New WideClient 6.70, wham. Even after changing the AutoRestart=0, 6.70 still 100% CPU, 6.47 works flawlessly.... :? And this is being done on exactly the same client PC obviously, merely coping the 6.47 and 6.70 exe's the whole time.... Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2006 Report Share Posted September 29, 2006 Interestingly, I have not changed *anything* yet as far as configs go. [\quote] How long ago did you start using WideFS? Maybe that INI file you are using has values dating back a few years? Same WideServer, I've downgraded WideClient to 6.47 (The only one I have on CD) - NO problem WHAT SO EVER. New WideClient 6.70, wham. Hmmthere's a couple of years of development between the two, so that's really not a lot of help in itself. Perhaps I could compare the Logs -- but use Log=DebugAll, not "Yes" as you did before -- that only shows the exchanges between client applications and WideClient, which were fine. Do exactly the same test with 6.47 and then with 6.70, Zipping up each log separately and labelling them appropriately. Maybe if I can find some intervening release versions we can zero in a bit more -- I can see 6.65 (June 2006), but for anything earlier I'd have to delve into archives. Version 6.50 was the last major change before that, and that was August 2005! Even after changing the AutoRestart=0, 6.70 still 100% CPU, 6.47 works flawlessly.... :? If you ignore this 100% business (it may or may not be relevant, i don't know), does it work? just saying "100%" isn't helpful. Here 6.70 is working flawlessly on many systems, using a mix of TCP, UDP and IPX. It's easily the fastest version, very smooth for gauges like those in Project Magenta. But evidently there's something it does to achieve this which isn't compatible with, what a handful maybe of systems. Why, I've really no idea at present. Regards, Pete Link to comment Share on other sites More sharing options...
cknipe Posted September 29, 2006 Report Share Posted September 29, 2006 Aaah, Time for some plane spotting at KATL then and let's debug... To answer your questions quickly... I may stand corrected, but I believe I only registered FSUIPC towards the middle / end of 2005. I've included my .key file for you to have a look at if you can get the date from there, otherwise, I'll have to go and look what the order date at SimMarket was... 6.47 *may* have just been the first version I got, and hence, put it on CD. I'm pretty sure I have used later versions since then, working. Said in the same breath however, I have been hecticly busy and did not fly to much for the last 6 months or so. Naturally when I started flying again now, the first thing I did, was update my nav databases, FSUIPC, WideFS, etc etc etc... This is where I picked the problem up. The ini was changed/updated when I updated WideFS/WideClient to 6.70. If you want, I'd be happy to look at a couple of less older versions and maybe try and see from my side which version started giving the problem - you'd have to supply the binaries though :wink: Perhaps even if we can try 6.50 (and if memory served me right, was working correctly - the version number rings a bell). As to "does it work"... Up to a point! It works as far as yes, it connects to WideServer, yes, it reads / updates data in WideServer, and yes, everything populates through to the simulator. The problem however is because the CPU is spending so much time in WideClient, CPU cycles are VERY limited for the addons. The addons thus, give utter crap performance, and some even crash!!! Logs and Key (for tracking purposes I guess) attached... I'll run a search through the forums as well as Im sure I made previous posts... Perhaps I get the latest 'known' version that I ran, from there somewhere! -- Chris. PS: It just occurred to me, posting my key on here in a zip is not a good idea :twisted: SimMarket states I purchased FSUIPC+WideFS in July 2005 WideClientLogs.zip Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 29, 2006 Report Share Posted September 29, 2006 I may stand corrected, but I believe I only registered FSUIPC towards the middle / end of 2005. I've included my .key file for you to have a look at if you can get the date from there, otherwise, I'll have to go and look what the order date at SimMarket was... Why would that be of interest? Using WideFS is not at all dependent upon having an FSUIPC key. It works as far as yes, it connects to WideServer, yes, it reads / updates data in WideServer, and yes, everything populates through to the simulator. The problem however is because the CPU is spending so much time in WideClient, CPU cycles are VERY limited for the addons. If the time was being spent in my code, in Wideclient, then it would be a doddle for me to find. It would even be reasonably easy to find if it were reproducible on any of my 10 PCs. But is isn't either of these things and in fact is a very very rare occurrence. The only place in the processing it can be sepnding any time is in Windows -- probably in the Network drivers themselves. Something is locking up at such a low level that the normal Windows message processing is very slow. Again, also unfortunately, there's been very little change in the way WideFs uses the Network software in Windows -- the main differences being the addition of UDP and the broadcasting by wideServer so that clients can find servers automatically. Are you using WinXP on both machines? If so could you please just try without an INI file at either end? Just let everything default. I'll look at the Logs later, but probably tomorrow now. Regards, Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted September 30, 2006 Report Share Posted September 30, 2006 Hi Chris. The logs you attached were of no use. Well, the 6.47 one was okay, but the 6.70 one is not comparable because you only had "Log=Yes" for that. Here's what i said: "Perhaps I could compare the Logs -- but use Log=DebugAll, not "Yes" as you did before -- that only shows the exchanges between client applications and WideClient, which were fine. Do exactly the same test with 6.47 and then with 6.70, Zipping up each log separately and labelling them appropriately." I was going to spend some time on this today, but I need something to start with, please. Don't attach them here, send to petedowson@btconnect.com. Regards Pete Link to comment Share on other sites More sharing options...
Jorge Diogo Posted October 2, 2006 Author Report Share Posted October 2, 2006 Well, I had to do the last resource, I decided to format my PC. It took almost 24 Hours to put it back online but no is clean and speedy :D Thanks for your help but the problem was garbadge, not the Wide Fs, a wonderfull program. Sorry again, regards Jorge Diogo AirSim.net Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now