Segwin Posted November 13, 2005 Report Posted November 13, 2005 Hello Peter: I'm having a problem connecting with WideFS. I have installed per instructions. I start MSFS/FS9 on my desktop, start a flight, start WideFS on my laptop, it says it's connected. I try to start SB3, which is now installed on my laptop as well as the desktop, and I get the error message, SB was unable to initiate a multiplayer session - SB will now close. I try to start ASV, on my laptop, and I get the message ASV was unable to detect your FS9 folder. Please browse to it in the next screen which is a folder directory of my laptop. FS Flightkeeper doesn't connect ether. Here are the logs and ini files. [Config] AdvertiseService=Yes AutoRestart=0 AutoUpdateTime=13 MaximumBlock=4096 NoStoppedRestarts=Yes Port=8002 RestartTime=10 SendTimeout=15 TCPcoalesce=No [ClientNames] 1=TERRYS ********* WideServer.DLL Log [version 6.50] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 12/11/05, Time 20:09:02.031: Server name is TERRY-DESKTOP 86266 Initialising TCP/IP server 86266 Initialising IPX/SPX server 86266 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 86266 Failed to start IPX/SPX Server 86328 Broadcasting service every 1 mSecs 89531 Incoming connection Accepted ok (skt=5984) 89578 Connected to computer "TERRYS" running WideClient version 6.500 (skt=5984) 331734 Closing down now ... Memory managed: Offset records: 19 alloc, 19 free Throughput maximum achieved: 3 frames/sec, 183 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 15 bytes/sec Average receive rate from "TERRYS": 0 frames/sec, 57 bytes/sec ********* Log file closed ********* ********* WideServer.DLL Log [version 6.50] ********* Blocksize guide = 4096 (double allowed) Date (dmy): 12/11/05, Time 19:42:54.781: Server name is TERRY-DESKTOP 110641 Initialising TCP/IP server 110672 Initialising IPX/SPX server 110672 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family 110672 Failed to start IPX/SPX Server 111797 Incoming connection Accepted ok (skt=6072) 111859 Connected to computer "TERRYS" running WideClient version 6.500 (skt=6072) 112063 Broadcasting service every 1 mSecs 335922 Closing down now ... Memory managed: Offset records: 19 alloc, 19 free Throughput maximum achieved: 3 frames/sec, 216 bytes/sec Throughput average achieved for complete session: 0 frames/sec, 14 bytes/sec Average receive rate from "TERRYS": 1 frames/sec, 60 bytes/sec ********* Log file closed ******** Client INI and Logs [Config] ButtonScanInterval=20 ClassInstance=0 NetworkTiming=5,1 PollInterval=2000 Port=8002 ResponseTime=18 ApplicationDelay=0 TCPcoalesce=No UseTCPIP=Yes WaitForNewData=500 MaxSendQ=100 OnMaxSendQ=Log NewSendScanTime=50 Priority=3,1,2 Window=203,127,593,489 ServerIPAddr=192.168.1.99 ********* WideClient Log [version 6.50] Class=FS98MAIN ********* Date (dmy): 12/11/05, Time 19:44:39.264: Client name is TERRYS 350 Attempting to connect now 440 Connection made okay! 5698 New Client Application: "squawkbox" (Id=2912) 20699 New Client Application: "ASV" (Id=3368) 224593 Error on client post-Connection Select() [Error=10053] Software caused connection abort 224593 Connection closed by server! 224593 The connection was terminated due to a time-out or other failure! 224773 Ready to try connection again 224773 Attempting to connect now 225714 Error on client pre-Connection Select() [Error=10061] Connection refused 225744 Ready to try connection again 225744 Attempting to connect now 443788 ****** End of session performance summary ****** 443788 Total time connected = 223 seconds 443788 Reception maximum: 2 frames/sec, 107 bytes/sec 443788 Reception average whilst connected: 1 frames/sec, 40 bytes/sec 443788 Transmission maximum: 3 frames/sec, 1133 bytes/sec 443788 Transmission average whilst connected: 1 frames/sec, 61 bytes/sec 443788 Max receive buffer = 345, Max send depth = 4, Send frames lost = 0 443788 **************** Individual client application activity **************** 443788 Client 2912 requests: 3 (Ave 0/sec), Data: 197 bytes (0/sec), Average 65 bytes/Process 443788 Client 3368 requests: 368 (Ave 1/sec), Data: 12526 bytes (56/sec), Average 34 bytes/Process 443788 ********* Log file closed (Buffers: MaxUsed 4, Alloc 796 Freed 796 Refused 0) ********* ********* WideClient Log [version 6.50] Class=FS98MAIN ********* Date (dmy): 12/11/05, Time 20:10:24.156: Client name is TERRYS 371 Attempting to connect now 381 Connection made okay! 5999 New Client Application: "squawkbox" (Id=2380) 87636 New Client Application: "ASV" (Id=1964) 132120 New Client Application: "ASV" (Id=2096) 242629 Error on client post-Connection Select() [Error=10053] Software caused connection abort 242629 Connection closed by server! 242629 The connection was terminated due to a time-out or other failure! 242639 Ready to try connection again 242649 Attempting to connect now 243590 Error on client pre-Connection Select() [Error=10061] Connection refused 243680 Ready to try connection again 243680 Attempting to connect now FSUIPC Log ********* FSUIPC, Version 3.50 by Pete Dowson ********* Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="Terry McCann" User Addr="tjmccann@alltel.net" FSUIPC Key is provided WideFS Key is provided Module base=61000000 ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E WeatherOptions(Orig)=4000B72F[4000B72F] InitDelay: 0 seconds WeatherReadInterval=4 LogOptions=00000001 DebugStatus=255 3937 System time = 20:09:01 3937 C:\Program Files\Microsoft Games\Flight Simulator 9\ 3937 System time = 20:09:01, FS2004 time = 12:00:00 (00:00Z) 29546 FLIGHTS\OTHER\FLTSIM.flt 29578 AIRCRAFT\c172\Cessna172SP.air 29828 Aircraft="Cessna Skyhawk 172SP" 30859 Module [M1] identified = "sbmpjoin9.dll" 30859 Module [M1] "sbmpjoin9.dll" access registration is okay 34000 Module [M2] identified = "sbmod9.dll" 34000 Module [M2] "sbmod9.dll" access registration is okay 34000 Module [M3] identified = "sb3gaugebridge.dll" 34000 Module [M3] "sb3gaugebridge.dll" access registration is okay 34015 Module [M4] identified = "ActiveRadar.dll" 34015 Module [M4] "ActiveRadar.dll" access registration is okay 34015 Module [M5] identified = "sbtrans9.dll" 34015 Module [M5] "sbtrans9.dll" access registration is okay 34015 Module [M6] identified = "PMDGOptions.DLL" 34015 Module [M6] "PMDGOptions.DLL" access registration is okay 34437 Advanced Weather Interface Enabled 62796 C:\Documents and Settings\Terry\My Documents\Flight Simulator Files\UI generated flight.flt 63390 Clear All Weather requested: external weather discarded 85500 Traffic File #14 = "scenery\world\scenery\traffic" 187000 NWI weather clear actioned 187000 External weather discarded 226937 NWI weather clear actioned 226937 External weather discarded 324218 C:\Documents and Settings\Terry\My Documents\Flight Simulator Files\UI generated flight.flt 325406 Clear All Weather requested: external weather discarded 334093 System time = 20:14:31, FS2004 time = 11:23:27 (19:23Z) 334093 *** FSUIPC log file being closed Memory managed: 2 Allocs, 2152 Freed ********* FSUIPC Log file closed ****
Pete Dowson Posted November 13, 2005 Report Posted November 13, 2005 I try to start SB3, which is now installed on my laptop as well as the desktop, and I get the error message, SB was unable to initiate a multiplayer session - SB will now close. WideFS is quite unconnected to Multiplayer. I really don't know anything at all about multiplayer -- you need SB support on that. SB3 uses FSUIPC/WideFS for getting the aircraft position and setting stuff like weather. It uses Multiplayer to provide the images of other flyer's aircraft. I try to start ASV, on my laptop, and I get the message ASV was unable to detect your FS9 folder. Please browse to it in the next screen which is a folder directory of my laptop. Again this is nothing to do with WideFS, which doesn't connect folders. I think you need to tell ASV where FS is so it can manipulate the cloud textures. This is to do with the Cloud facilities now added to this weather program. I think the documentation covers it well. FS Flightkeeper doesn't connect ether. And what does it say? Possibly it needs access to the FS scenery files in order to build its database. Nothing you've said or shown indicates anything wrong with the WideFS connection, quite the contrary in fact. All the programs you refer to need other channels to FS's files as well as the FSUIPC/WideFS interface. I think you need to study their documentation a little more, please. Regards, Pete
Segwin Posted November 13, 2005 Author Report Posted November 13, 2005 Thanks for the reply Peter. So when WideFS say's it connected everything is ok from your viewpoint with WideFS, the problem is with SB3, ASV etc? If this is the case then I'll seek help elsewhere. TIA
Pete Dowson Posted November 13, 2005 Report Posted November 13, 2005 So when WideFS say's it connected everything is ok from your viewpoint with WideFS, the problem is with SB3, ASV etc? In at least the first two cases that is most certainly true. SB3 is complaining about the Multiplayer connection, which is outside of WideFS/FSUIPC altogether. ASV is merely asking for the full path to your FS installation so that it can manipulate the cloud graphics, something added in ASV from previous releases. it will be something like \\\... You probably need to make it a specific shared folder on the FS PC, and maybe even a mapped drive on the ASV PC. I'm pretty sure the ASV documentation goes into all this -- if not check with their support forum. As for FlightKeeper, I don't know, but I suspect it needs to scan all your scenery files in order to build a correct matching database. It may have to be run initially on the FS PC, at least for speed in doing this, then have the database copied over. I know I had to do this with TrafficBoard. The connection through WideFS looks okay from your logs, though short-lived because none of the programs actually ran for long because of the other connection issues. If this is the case then I'll seek help elsewhere. Yes, but do check the documentation for those programs more thoroughly first. I think these issues are normally covered in some detail. Regards, Pete
Segwin Posted November 13, 2005 Author Report Posted November 13, 2005 Hello Peter: Problem found at the forum at SB3. I reloaded Windows on my laptop and it installed DX 8. Upgraded to DX 9.0C, the same as my desktop, and now everyting works! Good FAQ addition!
Pete Dowson Posted November 13, 2005 Report Posted November 13, 2005 Upgraded to DX 9.0C, the same as my desktop, and now everyting works! Oh, right. I'd never have guessed it would be a DX problem. Nothing of mine uses DX so it's an area I'm rather ignorant of I'm afraid. Glad you got it sorted. Regards, Pete
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