Ryzom

I've noticed the same thing with the ryzom server they've given us, but I know it's not a problem with NeL itself as Snowballs (the other test client/server that comes in the NeL source) doesn't have this problem. I also know that it has little or nothing to do with the speed of your computer. I haven't spent the time debugging the problem yet as it hasn't been too bad for me but I'd take a look at the FrontEnd service as that's what's talking with your client once your connected.

-Mankar

Bitter sweet, good to know its not just me. Bad to know it could be a greater issue.
But thanks for the reply and hope this can get squished.

I have the same problem.

And notice that the CPU usage is very high :

client_ryzom_r.exe*32 35 to 45

frontend_service.exe*32 48 to 50 always

plus other ryzom services, so that my total cpu usage keep 100% more high

This is the direct reason cause FS lost/please wait,I think.

But the real issues maybe connect to the high cpu usage of the frontend_service.exe process

-Red ================
Sorry for my borken spell and terrible syntx...

After a second thought...

If the CPU usage of frontend_service.exe (50%) is reasonable,then

Everyone run all services and client together on one machine(connect to localhost) like me

may have the same problem,

Is there anyone can share the frontend_service.exe CPU usage of yours and you dont have the FS lost/please wait issue?

when i tested the shard out, then frontend always took 100% cpu. client wants another 100%.

if you have multi-core cpu, then check affinity for those processes and lock them to different cpu's.
if there is only one cpu, then give FS higher priority or lower client's

After assignning frontend_service.exe(server side) to CPU#0 and client_ryzom_r.exe(client side) to CPU#1

and each CPU usage is 100% high !!!!!!!!

Then problem fixed, no more "FS lost/please wait" show up,

Thank you Nimetu :)

There's a big misunderstanding of what 100% cpu usage in the "windows task manager" means.

Look at it: "System Idle Process" takes 100% cpu! Does it means you cannot run anything more because your cpu already overloaded? NO

FS was coded to take all the cpu available, exactly the same way "System Idle Process" does. If you run other application that take cpu, then FS will give it without problem. If nobody want cpu, FS take it.

For the client, it's different, the goal of the client is to have the highest framerate possible. So, of course, it'll take as much cpu as it can to render as fast as possible.

I think "Please Wait" are not normal and should not happen and since we don't run servers on Windows, we cannot really know why it happens.

on that note, I did change around different affinity and priority settings.
Some helped a little most did not. Still every attempt left it unusable.

I'll try a few more things and see what happens.

vl wrote:

I think "Please Wait" are not normal and should not happen and since we don't run servers on Windows, we cannot really know why it happens.

It appears people are running client and server on the same machine here.
Client claims all the CPU, FS waits for whatever CPU is available and will have to wait forever because the client claims it all.

Solution would be to run on 2 machines, or maybe forcibly push each into a different CPU/core on multiCPU/core systems (on Windows, the task manager can be used for that). That of course works only if the client doesn't claim resources on both CPUs/cores, but from what I've observed the official client doing that's not the case.

Yes I tried a dedicated system for the server only. Still the same result when running the client on a different machine.

Also tried FS on core 1 while client on core 0 tried setting cpu priority to various settings on both. Also I have 2 hard drives and the server files on one client on other. All same result. Tho I did see that when tweaking the cpu priority the ping was not steady 10k plus only spiked. Out of box the ping usually stays over 10k. This makes no sense when its on a local net.

Also tried tweaking numbers in the .cfg files for networking nothing made it better but all attempts made it worse.
Lastly I tried entering all fields as the hard number for localhost instead of a router address (127.0.0.1) and changed all instances of "localhost" to 127.0.0.1 as well with client connecting to 127.0.0.1 none of this helped either. (sad attempt to bypass the router and keep network tight).

My next is to just keep trying to get a compile to work and run on my nix machine. I am at a loss on this windows issue.

also task manager is very limiting and generic. I use Process Explorer from Sysinternals