Strange issue with WideFS

[rwebb616]

It has been working fine right along and now tonight, wideclient takes two or three times to connect. I use the buttonscreen on it and I see the buttons flash for a second then disappear about 3 times, and then it finally connects and stays. Is this any kind of known issue?

I'm using FSX and can provide the log files if you like.

Thanks,

Rich

[Pete Dowson]

It has been working fine right along and now tonight, wideclient takes two or three times to connect. I use the buttonscreen on it and I see the buttons flash for a second then disappear about 3 times, and then it finally connects and stays. Is this any kind of known issue?

No. It sounds like something is wrong on your system. Is FSX struggling to start? Maybe FSX is taking so much processor time in the initial stages that WideServer or the network side isn't getting a look in? What have you changed recently?

I'm using FSX and can provide the log files if you like.

WideClient, WideServer and FSUIPC4 logs are needed. No INI files please. Close the session first, both ends. Keep it as short as possible, paste the logs into a message here.

Regards

Pete

[rwebb616]

No. It sounds like something is wrong on your system. Is FSX struggling to start? Maybe FSX is taking so much processor time in the initial stages that WideServer or the network side isn't getting a look in? What have you changed recently?

Actually nothing, all I was doing was sitting at O'Hare on the ground and programming my buttonscreen. Each time I would make a change to the Wideclient.ini I would exit Wideclient and restart it to see my changes. It had been working all night, but then started doing what I described.

WideClient, WideServer and FSUIPC4 logs are needed.

I'm not in front of the machine at the moment, but will as soon as I can. I just wanted to give more information as to what I was doing. Also, this is a clean install - nothing else is on the computer besides FSX, FSUIPC and the aircraft I'm using is a freeware Citation-X from Simviation.

-Rich

[rwebb616]

WideClient, WideServer and FSUIPC4 logs are needed

Here they are:

Wideserver.log

15375 Initialising TCP/IP server

15375 Initialising IPX/SPX server

15375 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

15375 Failed to start IPX/SPX Server

15375 Initialising UDP/IP server

16000 Broadcasting service every 1000 mSecs

29500 Incoming connection Accepted ok (skt=3580) TCP

29625 Restarting service due to zero reception!

29625 Failed to start IPX/SPX Server

34532 Incoming connection Accepted ok (skt=7668) TCP

34735 Failed to start IPX/SPX Server

37500 Incoming connection Accepted ok (skt=7672) TCP

37594 Connected to computer "MAGENTA" running WideClient version 6.780 (skt=7672) TCP

558438 Error 10053: client socket disconnected at Client: removing (skt=7672) TCP

WideClient.log

281 Attempting to connect now

812 Server = FS

828 Trying TCP/IP host "FS" port 8002 ...

828Okay, IP Address = 192.168.5.10

828 Connection made okay!

953 Connection closed by server!

953 Attempting to connect now

953 Trying to locate server: Protocol not yet decided

5812 Server = FS

5812 Trying TCP/IP host "FS" port 8002 ...

5812Okay, IP Address = 192.168.5.10

5828 Connection made okay!

6062 Connection closed by server!

6062 Attempting to connect now

8812 Server = FS

8812 Trying TCP/IP host "FS" port 8002 ...

8812Okay, IP Address = 192.168.5.10

8828 Connection made okay!

FSUIPC.log

529719 ****** End of session performance summary ******

529719 Total time connected = 521 seconds

529719 Reception maximum: 24 frames/sec, 671 bytes/sec

529719 Reception average whilst connected: 23 frames/sec, 615 bytes/sec

529719 Transmission maximum: 1 frames/sec, 41 bytes/sec

529719 Transmission average whilst connected: 0 frames/sec, 20 bytes/sec

529719 Max receive buffer = 387, Max send depth = 1, Send frames lost = 1

47 System time = 19/10/2009 13:07:55

47 FLT UNC path = "C:\Documents and Settings\user\My Documents\Flight Simulator X Files\"

47 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

1265 LogOptions=00000000 00000001

1265 SimConnect_Open succeeded: waiting to check version okay

3734 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

3734 Initialising SimConnect data requests now

3734 FSUIPC Menu entry added

3875 C:\Documents and Settings\user\My Documents\Flight Simulator X Files\Cold and Dark.FLT

3875 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Sweeded_FSND_FSX_Citation X_750\citation.AIR

26797 System time = 19/10/2009 13:08:22, Simulator time = 13:07:59 (18:07Z)

26890 Aircraft="Citation X"

31609 Advanced Weather Interface Enabled

590875 Sim stopped: average frame rate for last 560 secs = 23.8 fps

593765 Weather Mode now = Theme

593765 C:\Documents and Settings\user\Application Data\Microsoft\FSX\Previous flight.FLT

Thanks

-Rich

[Pete Dowson]

Here they are:

At the start, even after the first connection, the server is timing out the connection "due to lack of demand" -- it's a safety measure to delay with stalled clients. However, the log shows that timeout to be coinciding with the first connection attempt from the client:

16000 Broadcasting service every 1000 mSecs

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< 13.5 seconds of nothing!

29500 Incoming connection Accepted ok (skt=3580) TCP

29625 Restarting service due to zero reception!

The timeout is 10-15 seconds initially (extending to 20 after first connection). For some reason you are starting Wideclient at just about the wrong time. Why are you starting it a good 13 seconds after FS is ready? Best to have all your clients running, ready and waiting, really, before you even start FS. I have my clients loaded as part of Windows "startup", so they automatically connect as soon as FS is ready, every time.

I suspect something has changed in the way you do things on the client, and this has managed to get the timing just wrong. A few seconds earlier and it wouldn't have fallen foul of the timeout, and few seconds later and it would have connected on the restarted Server attempt. As it is the client sees the timeout and tries to connect again, so WideServer sees two subsequent attempts. The third one works.

It isn't critical, but the answer is to start WideClient earlier/

Regards

Pete

[rwebb616]

The timeout is 10-15 seconds initially (extending to 20 after first connection). For some reason you are starting Wideclient at just about the wrong time. Why are you starting it a good 13 seconds after FS is ready? Best to have all your clients running, ready and waiting, really, before you even start FS. I have my clients loaded as part of Windows "startup", so they automatically connect as soon as FS is ready, every time.

That particular time I started it, it was only done for the test. Previously when it was happening, I was stopping and restarting wideclient several times (after adjusting the .ini file).. sometimes it would immediately connect and other times it would wait for about 10 seconds and then connect, and yet others it would do the flash thing where it connects and then drops. It seems very inconsistent as to what it is doing.

It isn't critical, but the answer is to start WideClient earlier

This time (for which I have attached the logs) wideclient was up and running well before fsx and it was a good 10-12 seconds before my button screen appeared after seeing the virtual cockpit. I also should mention that these problems did not happen on the fs9 setup I was previously using. It only seems to be on the fsx version.

Here are the logs:

Wideclient:

Date (dmy): 20/10/09, Time 15:28:30.984: Client name is MAGENTA

406 Attempting to connect now

1406 Trying to locate server: Protocol not yet decided

1406 Failed to connect: waiting to try again

3406 Attempting to connect now

67406 Trying to locate server: Protocol not yet decided

232093 Server = FS

232093 Trying TCP/IP host "FS" port 8002 ...

232093Okay, IP Address = 192.168.5.10

232093 Connection made okay!

232234 Connection closed by server!

232734 Attempting to connect now

237093 Server = FS

237093 Trying TCP/IP host "FS" port 8002 ...

237093Okay, IP Address = 192.168.5.10

237093 Connection made okay!

291484 ****** End of session performance summary ******

291484 Total time connected = 55 seconds

291484 Reception maximum: 23 frames/sec, 669 bytes/sec

291484 Reception average whilst connected: 19 frames/sec, 509 bytes/sec

291484 Transmission maximum: 0 frames/sec, 31 bytes/sec

291484 Transmission average whilst connected: 0 frames/sec, 21 bytes/sec

291484 Max receive buffer = 397, Max send depth = 1, Send frames lost = 1

Wideserver:

Blocksize guide = 4096 (double allowed)

Date (dmy): 20/10/09, Time 15:32:01.328: Server name is FS

15547 Initialising TCP/IP server

15562 Initialising IPX/SPX server

15562 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

15562 Failed to start IPX/SPX Server

15562 Initialising UDP/IP server

16015 Broadcasting service every 1000 mSecs

17531 Incoming connection Accepted ok (skt=9232) TCP

17656 Restarting service due to zero reception!

17672 Failed to start IPX/SPX Server

22547 Incoming connection Accepted ok (skt=9140) TCP

22719 Connected to computer "MAGENTA" running WideClient version 6.780 (skt=9140) TCP

77328 Error 10053: client socket disconnected at Client: removing (skt=9140) TCP

FSUIPC.log

Running inside FSX (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

203 System time = 20/10/2009 15:30:26

203 FLT UNC path = "C:\Documents and Settings\user\My Documents\Flight Simulator X Files\"

203 FS UNC path = "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

1328 LogOptions=00000000 00000001

1328 SimConnect_Open succeeded: waiting to check version okay

10375 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

10375 Initialising SimConnect data requests now

10390 FSUIPC Menu entry added

10453 C:\Documents and Settings\user\My Documents\Flight Simulator X Files\Cold and Dark.FLT

10453 C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Sweeded_FSND_FSX_Citation X_750\citation.AIR

95422 System time = 20/10/2009 15:32:02, Simulator time = 16:30:38 (20:30Z)

95515 Aircraft="Citation X"

95953 Advanced Weather Interface Enabled

161000 Sim stopped: average frame rate for last 66 secs = 23.7 fps

163734 Weather Mode now = Theme

163734 C:\Documents and Settings\user\Application Data\Microsoft\FSX\Previous flight.FLT

Hope we can resolve it!

Thanks

Rich

[Pete Dowson]

Here are the logs:

You keep making extracts from the logs, which prevents me checking version numbers. If you do that please be sure to tell me exactly what the numbers are recorded at the start of each log. That is important for me, because I don't want to waste time on older versions, and at least the logs are proof of what you are using.

In the Server log, this occurs again, and it is very strange:

17531 Incoming connection Accepted ok (skt=9232) TCP

17656 Restarting service due to zero reception!

So it isn't coincidence that just after it connects, the server decides to restart its service. Weird. I have not seen anything like that before.

You haven't changed any of the client or Server INI file settings, have you? (The Server ones are in a section of the FSUIPC4.INI file).

Hope we can resolve it!

Well, it is not a real problem in that once it starts properly it stays okay. But still, I'd like to know why it is happening -- but first, version numbers please.

And have you tried giving WideClient the explicit server details -- i.e. setting the ServerName (or ServerIPaddr) and Protocol parameters in its INI file? I'm wondering if it is related to the Broadcasting on your setup.

Regards

Pete