Example of WideClient.ini WideServer.ini file for IPX/SPX

[black-hawk]

Hi Peter

I would like to ask you an example of WideClient.ini and WideServer.ini adapted for a net 100mbps that and has shaped with the protocol IPX/SPX.

If you can send me them in email.

I ask you this since my net sometimes has some long pauses around 10 seconds

Thanks

Ettore Mele

[Pete Dowson]

I would like to ask you an example of WideClient.ini and WideServer.ini adapted for a net 100mbps that and has shaped with the protocol IPX/SPX.

If you can send me them in email.

There's really no point. Your INI files should allow everything to default, except just set UseTCPIP=No in both, and in the Clients you may need to provide the Server Node details, as documented for mixed systems or NT/2K/XP servers. I cannot make that happen for you as your Server node address will be unique to you.

I ask you this since my net sometimes has some long pauses around 10 seconds

If it is working at all it means the INI files are correct. Whilst there are lots of parameters you can tinker with, it is not a good idea to do this without any other information about this symptom, "some long pauses". It took me 6 months of tinkering and adjusting to get what are, for most instances, the 'ideal' settings. If you want to keep tinkering for another 6 months and get better settings, be my guest, but I would not recommend it. It is not hapy work I assure you!

If there are these massive pauses, there'll be a reason. What do the WideSever and WideClient Logs show? WHERE are these pauses? In FS, in some Application? Which Application? Are you sure it isn't the application which has the problems?

And, of course, are you using the very latest versions of both WideServer and WideClient, and FSUIPC for that matter? Please do not show me any logs of older versions. And please, if you do show logs, please close FS down and show complete logs -- there are summaries of performance added at the end which are useful.

Finally, why are you using IPX/SPX? Is your system all Windows 98SE? It certainly should be okay if so, but since version 5 WideFS has been optimised more for TCP/IP. Mixed Windows systems, and Windows XP, are probably better with the TCP/IP protocol -- not faster, certainly, but smoother and easier to sort out.

Regards,

Pete

[black-hawk]

All my computer (5) are in WindowsXP Professional Editions.

Do you think witch TCP/IP is better decision?

Ettore Mele

This is the small log of my Client with pause.

******* WideClient.DLL Log [version 6.101] Class=FS98MAIN *******

Date (dmy): 29/11/03, Time 14:57:43.484: Client name is PFD

63 Attempting to connect now

79 Connection made okay!

9500 Connection closed by server!

9500 Ready to try connection again

9563 Attempting to connect now

9563 Connection made okay!

12000 New Client Application: "pfd" (Id=1616)

310063 Reception maximum achieved: 31 frames/sec, 13989 bytes/sec

310063 Reception average achieved whilst connected: 17 frames/sec, 6633 bytes/sec

310063 Max receive buffer = 14143, Max send depth = 92

310063 ******* Log file closed (Buffers: MaxUsed 94, Alloc 11331 Freed 11331 Refused 0) *******

In the WideServer.log nothing of important

Ettore Mele

[Pete Dowson]

All my computer (5) are in WindowsXP Professional Editions. Do you think witch TCP/IP is better decision?

I never got IPX/SPX to work well on my systems with WinXP, so I am biassed in favour of TCP/IP for XP, yes. If I had ever managed to make IPX/SPX work I might be of different opinion. Maybe others can say.

12000 New Client Application: "pfd" (Id=1616)

310063 Reception maximum achieved: 31 frames/sec, 13989 bytes/sec

310063 Reception average achieved whilst connected: 17 frames/sec, 6633 bytes/sec

310063 Max receive buffer = 14143, Max send depth = 92

All that looks perfect EXCEPT the maximum send depth of 92, which seems rather excessive. However, that may have occurred if you had PFD running whilst still loading flights or aircraft of something in FS.

In the WideServer.log nothing of important

In that case I can't really see why you'd notice any pausing. You didn't say WHERE you saw these 10 second pauses in any case? In the PFD? Could they be graphics problems in its OpenGL driver interface?

The WideServer log would at least show performance. What are the reported figures at the end there? What frame rates are you getting in FS? What have you set the FS Frame Rate Limiter to? What processors are being used? Are the pauses coincidental with something going on in FS?

Regards,

Pete

[black-hawk]

I have a system based on:

Pentium 4 2,4Gbs 1Gb rams, Card video ATI Radeon 9700Pro

fs2004, more addons texture, mesh, etc.

On same Pc I have run: MCP Magenta, EPIC, EPICMAPPER, SquwakBOX, Servinfo, Teamspeek.

On other 4 PC: PFD/ND Magenta, CDU Magenta with PMSound on same PC, RCDU Magenta, EICAS Magenta.

The all has connected to the internet with a router ADSL at 640KB.

All system alone elegant works there are pauses on the net every so many seconds and not always.

[Pete Dowson]

I have a system based on:

Pentium 4 2,4Gbs 1Gb rams, Card video ATI Radeon 9700Pro

fs2004, more addons texture, mesh, etc.

On same Pc I have run: MCP Magenta, EPIC, EPICMAPPER, SquwakBOX, Servinfo, Teamspeek.

On other 4 PC: PFD/ND Magenta, CDU Magenta with PMSound on same PC, RCDU Magenta, EICAS Magenta.

The all has connected to the internet with a router ADSL at 640KB.

All system alone elegant works there are pauses on the net every so many seconds and not always.

You only showed a little of one WideClient. Is that the only one with pausing? You still haven't said where you see the pausing. You also missed some other questions. What frame rates do you get in FS2004? Do you get pausing there? I would really recommend moving stuff off the FS PC if possible.

What is your frame rate limiter in FS set to? With FS2004 on a Pentium 2.4GHz and with all those other things running on the same PC I wouldn't expect you to get smooth operation with anything more than 20 fps, probably less if you have many of FS's quality sliders turned up high.

With so many things running, you may need to start taking some off to see which ones are contributing to your problems.

Regards,

Pete