Wide FS - 5 Connected?!

[baw150]

Dear Pete,

I've been using your software for ages without a problem, so I don't think your programme is causing this problem, but without having done very much since last time (I installed a printer, but that's it), my FS9 is getting strangled by WideFS, with up to 15 connections.

I don't know what the process is that's behind it, but I seem to be able to have multiple connections to FS9, even though only one computer is connected to it.

Here's the log. I would really appreciate your help on this.

********* WideServer.DLL Log [version 6.47] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 27/06/05, Time 11:47:08.984: Server name is ONE

115766 Initialising TCP/IP server

115937 Initialising IPX/SPX server

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

115953 Failed to start IPX/SPX Server

116844 Incoming connection Accepted ok (skt=2940)

116922 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2940)

127797 Incoming connection Accepted ok (skt=3012)

127875 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=3012)

138703 Incoming connection Accepted ok (skt=2996)

138781 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2996)

146172 Incoming connection Accepted ok (skt=2980)

146172 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2980)

150094 Incoming connection Accepted ok (skt=2964)

150094 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=2964)

374719 Incoming connection Accepted ok (skt=3036)

374797 Connected to computer "IF-NB12" running WideClient version 6.470 (skt=3036)

What I don't understand, is why these multiple connections from the same computer are being accepted.... this didn't happen before, I'm sure!

Best wishes,

Tom

[Pete Dowson]

I've been using your software for ages without a problem, so I don't think your programme is causing this problem, but without having done very much since last time (I installed a printer, but that's it), my FS9 is getting strangled by WideFS, with up to 15 connections.

I don't know what the process is that's behind it, but I seem to be able to have multiple connections to FS9, even though only one computer is connected to it.

This phenomenon is actually described in the documentation, and has been for years -- please see the section entitled "Running WideFS". I think the explanation starts in about paragraph 5.

Here's the log.

That's the Server log, which doesn't show a problem. It's the Client which is re-connecting, probably because it is timing out messages from the Server. Something is probably stopping them in the Server, but you need to look at the Client log to see what it says, first.

Regards,

Pete

[baw150]

Hi Pete,

I've had a look at the Client Log and it's full of:

113663 Attempting to connect now

113663 Connection made okay!

131719 Timed out response: connection assumed lost!

131729 Ready to try connection again

131770 Timed out response: connection assumed lost!

131780 Attempting to connect now

131780 Connection made okay!

149886 Timed out response: connection assumed lost!

149896 Ready to try connection again

149936 Timed out response: connection assumed lost!

149946 Attempting to connect now

149956 Connection made okay!

168002 Timed out response: connection assumed lost!

...which I guess is what you were thinking of. So are you saying that there's something in the server which is stopping the messages from the Client getting through? It only seems to be happening with the Level-D 767... very strange.

Could it be that the WideClient 'problem' I'm having is just a symptom of a general crash, and not a cause? Everything else is working fine on the network.

Thanks again for your help?

Tom

[Pete Dowson]

So are you saying that there's something in the server which is stopping the messages from the Client getting through?

No, the Server is seeing messages from the Client, it is the Client not seeing anything from the Server. That's why it says "Timed out response".

The cause of the problem could actually be at either end. With only one client it is difficult to isolate -- with two it is easy because either both clients suffer or only one.

The trouble is there are no errors being reported. It simply looks like the data is transferring okay Client to server, but not Server to Client. Something is stopping it.

It only seems to be happening with the Level-D 767... very strange.

How do you mean? If you change aircraft it all springs to life?

Could it be that the WideClient 'problem' I'm having is just a symptom of a general crash, and not a cause? Everything else is working fine on the network.

What sort of "general crash"? And we don't know that it's a Client problem. If there's only a problem when using the LDS 767, maybe it is taking too much of the FS processor and not letting WideServer run -- though I've never heard of such a thing before. What processor is it? What is your FS frame rate limiter set to? What are your frame rates?

You said this started after you installed some driver -- for a printer? Try uninstalling or re-installing that. Was it a Network pronter by any cance?

Regards,

Pete

[baw150]

It only seems to be happening with the Level-D 767... very strange.

How do you mean? If you change aircraft it all springs to life?

Well, not really, but with the default aircraft there are no problems. Then when I load the Level D, during the loading process itself, the computer becomes slower and slower until it eventually freezes.

Could it be that the WideClient 'problem' I'm having is just a symptom of a general crash, and not a cause? Everything else is working fine on the network.

What sort of "general crash"? And we don't know that it's a Client problem. If there's only a problem when using the LDS 767, maybe it is taking too much of the FS processor and not letting WideServer run -- though I've never heard of such a thing before. What processor is it? What is your FS frame rate limiter set to? What are your frame rates?

This was my initial reaction. My frame rates are limited to 22, I have a 1.8GHz processor with plenty of memory. I've used Level D fine with WideFS in the recent past.

You said this started after you installed some driver -- for a printer? Try uninstalling or re-installing that. Was it a Network pronter by any cance?

It is a printer connected to the main computer, but also installed on the other computer as a network printer. I will try de-installing the network printer, and see what happens. Is this a known problem? What do you think it might be? Thankyou very much for your help.

Best wishes,

Tom

[Pete Dowson]

... with the default aircraft there are no problems. Then when I load the Level D, during the loading process itself, the computer becomes slower and slower until it eventually freezes.

Ahthere's something wrong with the Level D installation then, by the sound of it. If the computer is slowing and freezing then WideServer is too. WideServer cannot run if FS cannot run.

This was my initial reaction. My frame rates are limited to 22, I have a 1.8GHz processor with plenty of memory. I've used Level D fine with WideFS in the recent past.

They are limited to 22, but what are you getting with the level D? You just said the PC is slowing down and freezing. Surely it isn't maintaining 22 fps during those times? You aren't trying to say that WideServer is freezing the PC are you? Test without first.

1.8 seems very slow for processor speed with a complex aircraft such as the Level D. I assume you must have many features in FS2004 turned way down? Even my 3.4 GHz PC would struggle.

It is a printer connected to the main computer, but also installed on the other computer as a network printer.

Well, it's not quite the same as a Network printer, but it might be that the driver is doing something all the time across the link to the PC with the printer on it, so it would be a good idea to eliminate that possibility first.

However, that would affect everything, not just the Level D aircraft -- there's no way the printer driver would know or care what aircraft you are loading.

I will try de-installing the network printer, and see what happens. Is this a known problem?

No, I've never heard of it being a problem. But we have no idea what you've changed to cause this except that you said the only thing you've changed was to install a printer. Therefore, logically, that's the first thing to check.

However, uninstalling and re-installing the Level D aircraft seems like the logical next step after that to try, from what you've now said. Maybe something in that has got corrupted.

Regards,

Pete