Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hi Pete,

I changed today all my files including PM GC 416 : FSUIPC 3.40 and WIDE FS 6.401.

I updated also FS9 to FS9.1.

the first client running PM GC is far behind teh server running FS. PM frame rate is poor.

Before I changed all those files everything ran well and smoothly. Now PM GC is very delayed, a good second behind FS.

I must say that I backed up the new FS9.EXE and came back to the oder no-cd FS9.EXE ( may be a mistake)

What's wrong. Are some new value in the ini file of Wide FS to be configured?

Thanks for your help

Regards

Roger

Posted

I changed today all my files including PM GC 416 : FSUIPC 3.40 and WIDE FS 6.401.

From what versions before?

the first client running PM GC is far behind teh server running FS. PM frame rate is poor. Before I changed all those files everything ran well and smoothly. Now PM GC is very delayed, a good second behind FS.

Two separate things there -- "PM frame rate is poor"? Which rate is that, the graphics rate, the data rate it measures itself, or the actual frame rate WideClient measures? There's a lot of difference depending on what you mean.

"PM GC is very delayed" may either be a symptom of a poor GC graphics update rate or blockages on the Network. Sight of your WideClient and matching WideServer Log files might be useful to differentiate between these. Close both down first so we get frame rate summaries at the end.

On the whole FS9.1 is a bit faster. The only real difference with WideFS 6.401 (from 6.3xx and earlier) is that errors are retried with a slight gap (a fraction of a second though), rather than immediately, so hopefully allowing an already blocked path to unblock rather than back up -- I believe the delays some folks reported with earlier versions derive from long queues of blocks someplace in the Windows TCP/IP stack.

Are some new value in the ini file of Wide FS to be configured?

No, none at all. Best to allow all to default.

Regards,

Pete

Posted

Pete,

From what versions before?

I update systematically Fsuipc, widefs and gc as soon as there are some new one.

Two separate things there -- "PM frame rate is poor"? Which rate is that, the graphics rate, the data rate it measures itself, or the actual frame rate WideClient measures? There's a lot of difference depending on what you mean.

When GC runs on the client for itself -not network just demo- I get an 250 OpenGL score with everything as smooth as it ever was since two years. I always had 60 graphic FPS and 30 Network FPS.

Now I cant mesure since there is a bug into PM GC with th "F" key with french keyboard.

It can only be a network problem. But nothing here has been modified, beside the new wide fs file. Yesterday I first tried 6.4 before 6.41 and it was the same. I thought first it was a bug in 6.40 and switched to 6.41

Unfortunately I have not backup of 6.3

Anyway I will see today the logs and give you more infos.

Thanks for your attention.

Regards

Roger

Posted

Here the log of this morning.

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

Date (dmy): 11/10/04, Time 09:52:07.364: Client name is ROGER-CLIENT

120 Attempting to connect now

140 Trying TCP/IP host "roger-serveur" ...

140Okay, IP Address = 192.160.0.1

1051 Error on client pre-Connection Select() [Error=10061] Connection refused

1061 Ready to try connection again

1101 Attempting to connect now

6930 New Client Application: "pmsounds" (Id=688)

10315 New Client Application: "pfd" (Id=276)

17685 Connection made okay!

122596 Error on client post-Connection Select() [Error=10053] Software caused connection abort

122606 Ready to try connection again

122666 Attempting to connect now

Posted

When GC runs on the client for itself -not network just demo- I get an 250 OpenGL score

I think that with nothing else to do and no real information to work on it jolly well ought to be fast! :wink:

It can only be a network problem.

Don't forget that the network is being used separately by PM. It isn't just WideFS using the network. Have you tried an ealrier version of the GC or other PM components?

Regards,

Pete

Posted
Here the log of this morning.

This shows nothing except the initial connection and ending on a disconnection. Please do a complete session, closing both FS and WideClient down, and send both logs.

I see you a duplicating things here and in the PM newsgroup. If you want me to look at detailed and COMPLETE logs, ZIP them up and attach them over there.

Regards,

Pete

Posted

Pete,

I dont know which log you mean.

Here is a copy of the server.dll log and shows a poor 13 FPS average, while I always had at least 25, better 30.

I changed to earlier version of all files, including PM GC, FSUIPC, WideFS and had curiously the same symptoms.

Beside the fact that I upgraded to FS9.1 there is nothing that I changed in all three networked computer.

Regards

Roger

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

Using blocksize guide of 4096 bytes

Date (dmy): 11/10/04, Time 14:24:45.546: Server name is ROGER-SERVEUR

15140 Initialising server socket now

15515 Incoming connection Accepted ok (skt=2696)

15671 Connected to computer "ROGER-CLIENT" (skt=2696)

535250 Closing down now ...

Memory managed: Offset records: 120 alloc, 120 free

Throughput maximum achieved: 30 frames/sec, 5514 bytes/sec

Throughput average achieved for complete session: 13 frames/sec, 1621 bytes/sec

********* Log file closed *********

Posted

I dont know which log you mean.

Sorry, what does that mean? It is you showing me logs, not vice versa!

Here is a copy of the server.dll log and shows a poor 13 FPS average, while I always had at least 25, better 30.

But that is the overall average since WideServer started. It includes all the period of FS running, including FS loading aircraft, sceneries and so on, and time waiting for clients. You only ran FS for something under 9 minutes altogether. The maximum is showing as 30 which seems good. What is the FS frame rate limiter set to? where's the WideClient Log?

I changed to earlier version of all files, including PM GC, FSUIPC, WideFS and had curiously the same symptoms.

Of course, especially from the WideFS perspective as nothing has changed which would affect you adversely, as I keep saying.

Beside the fact that I upgraded to FS9.1 there is nothing that I changed in all three networked computer.

Well, something has obviously changed. There are no errors or problems occurring in WideFS (though, again, you've not yet shown me a complete Wideclient log). If you suspect the FS 9.1 update, run the uninstaller and re-test.

Pete

Posted

I cant get a complete client log because Wideclient.exe runs as a process and is shut down with the computer.

I do not know how to exit properly from wide client.exe.

As I do use the old Efis Cockpit, I really do not have that display.

Here a copy of both ini files: ( may help ??)

Client

[Config]

Port=8002

UseTCPIP=Yes

ButtonScanInterval=0

Window=573,235,304,219

Visible=no

serverName=roger-serveur

ClassInstance=0

NetworkTiming=5,1

PollInterval=2000

ResponseTime=18

Timeout=12

TCPcoalesce=No

WaitForNewData=500

; -----------------------------------------------

[user]

Log=Errors+

run1=c:\PFD\PFD.exe

; ===============================================

Server

[Config]

Port=8002

useTCPIP=Yes

ButtonScanInterval=0

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

RestartTime=10

SendTimeout=15

TCPcoalesce=No

; -----------------------------------------------

[user]

Log=Errors+

; ===============================================

[ClientNames]

1=ROGER-CLIENT

2=ROGER-CLIENT2

Posted

And finally I could manage the log file from the client

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

Date (dmy): 11/10/04, Time 16:15:16.496: Client name is ROGER-CLIENT

100 Attempting to connect now

110 Trying TCP/IP host "roger-serveur" ...

110Okay, IP Address = 192.160.0.1

130 Connection made okay!

7571 New Client Application: "pfd" (Id=864)

26538 Note: Send() request depth is over 100!

172338 send() failed [0 bytes] after 40 retries, request depth is 1922

172358 Ready to try connection again

172378 Attempting to connect now

172388 Connection made okay!

187479 Note: Send() request depth is over 100!

201630 send() failed [0 bytes] after 40 retries, request depth is 384

201640 Ready to try connection again

201650 Attempting to connect now

201660 Connection made okay!

212616 Note: Send() request depth is over 100!

253675 send() failed [0 bytes] after 40 retries, request depth is 727

253685 Ready to try connection again

253695 Attempting to connect now

253705 Connection made okay!

264520 send() done [27 bytes] after 7 retries, request depth is 113

284900 send() done [27 bytes] after 6 retries, request depth is 370

336534 send() failed [0 bytes] after 40 retries, request depth is 1080

336544 Ready to try connection again

336554 Attempting to connect now

336564 Connection made okay!

349723 Note: Send() request depth is over 100!

360769 send() failed [0 bytes] after 40 retries, request depth is 361

360779 Ready to try connection again

360789 Attempting to connect now

360799 Connection made okay!

376842 send() done [27 bytes] after 14 retries, request depth is 153

401407 send() done [27 bytes] after 8 retries, request depth is 457

411371 send() done [27 bytes] after 20 retries, request depth is 598

451549 Error on client post-Connection Select() [Error=10053] Software caused connection abort

451559 Ready to try connection again

451569 Attempting to connect now

452511 Error on client pre-Connection Select() [Error=10061] Connection refused

452521 Ready to try connection again

452571 Attempting to connect now

478398 Reception maximum achieved: 65 frames/sec, 10347 bytes/sec

478398 Reception average achieved whilst connected: 43 frames/sec, 6126 bytes/sec

478398 Max receive buffer = 85395, Max send depth = 1922

478398 ********* Log file closed (Buffers: MaxUsed 1880, Alloc 14500 Freed 14500 Refused 0) *********

Posted

I do not know how to exit properly from wide client.exe.

It is a standard Windows program and can be closed just like any other. Simply find its window and click on the close button (X) top right. Or right click on its entry in the task bar and select close.

Here a copy of both ini files: ( may help ??)

Thanks, but no. And there's nothing wrong with any of the logs you've shown here or in the PM newsgroup. The only reason I wanted to see the closed log was to check what WideClient's frame rates are -- the "Data rates" shown by PM modules are the rates IT sees changes, not necessarily the rate WideClient is seeing them.

Regards,

Pete

Posted
And there's nothing wrong with any of the logs you've shown here or in the PM newsgroup. The only reason I wanted to see the closed log was to check what WideClient's frame rates are -- the "Data rates" shown by PM modules are the rates IT sees changes, not necessarily the rate WideClient is seeing them

I cannot believe it. I had during that flight delays on the PM GC going up to 3-4 seconds??

What is the meaning of the error message in the client log??

Thanks

Regards

Roger

Posted

I cannot believe it. I had during that flight delays on the PM GC going up to 3-4 seconds??

What is the meaning of the error message in the client log??

Ah, sorry, that last log crossed with my message. I've only just seen it!

(Why not use the PM newgroup for Logs, BTW. I am getting very confused talking to you in two places at the same time!).

These errors are indeed, bad. They show that the link to the Server is getting seriously blocked on occasion:

26538 Note: Send() request depth is over 100!

172338 send() failed [0 bytes] after 40 retries, request depth is 1922

187479 Note: Send() request depth is over 100!

201630 send() failed [0 bytes] after 40 retries, request depth is 384

212616 Note: Send() request depth is over 100!

253675 send() failed [0 bytes] after 40 retries, request depth is 727

264520 send() done [27 bytes] after 7 retries, request depth is 113

284900 send() done [27 bytes] after 6 retries, request depth is 370

336534 send() failed [0 bytes] after 40 retries, request depth is 1080

349723 Note: Send() request depth is over 100!

360769 send() failed [0 bytes] after 40 retries, request depth is 361

376842 send() done [27 bytes] after 14 retries, request depth is 153

401407 send() done [27 bytes] after 8 retries, request depth is 457

411371 send() done [27 bytes] after 20 retries, request depth is 598

... but the reason for this is probably this:

478398 Reception maximum achieved: 65 frames/sec, 10347 bytes/sec

478398 Reception average achieved whilst connected: 43 frames/sec, 6126 bytes/sec

The link to the Server is probably being overwhelmed by WideServer trying to send far too many frames per second. A maximum of 65 and average of 43?? Phew!

What have you set your FS frame rate limiter to?

Pete

Posted

Frame rates in FS was blocked at 50 fps. ( As it ever was without problems)

I made a test with 25 fps and still have the delays.

Why is Wideserver overhelmed now and never was before with the same hardaware???

Thanks for the help, indeed.

Regards

Roger

Posted

Why is Wideserver overhelmed now and never was before with the same hardaware???

I'm not sure it is WideServer being overwhelmed -- it looks like the link with your client. Perhaps you have changed something there? After all, you already said you tried with the older WideFS too.

BTW I've never seen any sustained 50 fps possible at all on any system so far, let alone with any WideFS also running. You must have very fast hardware all round! (It is water-cooled?)

Are you going to continue here or in the PM newsgroup? It is very confusing having you come at me from all directions! :wink:

Regards,

Pete

Posted

I have a very basic AMD 2 GHZ, but nothing else running and well tuned with an ATI 9600 XT card.

I have an Athlon 64 FX 53 (which I think runs at a speed of about twice yours), along with an ATI 9800 XT Pro, and even that won't attain 50 fps consistently, with nothing else -- including no clients or even WideFS (it is my GA machine).

My main PM FS PC is a P4 3.2 with a Parhelia, and that is certainly smoothest limited to 20 fps.

My previous system, a 2.4 GHz P4, is now used for the PM GC - it was far too slow for FS2004, and only just decent enough for FS2002 in my opinion.

Regards,

Pete

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.