Very often, apart of any server problem ryzom can have, the cause of the please wait is caused by packet loss.
Packet loss cause the client and server lose syncronization and try to resync (this is what happens during the please wait window opened) resending packets till both resync. If a resync cannot be issued after a certain time, the connection between server and client is lost.
This behaviour is mostly needed because network engine of NeL uses UDP packets for communications.
When you can get packet loss? One source can be an heavy loaded server, in this case you cannot do anything, but in this case, everyone on the server would have problems, not just you.
But there is also another reason for packet loss: network fragmentation, that means network packets are fragmented due to a wrong network configuration, client OS side (almost all windows system are never well configured by default), or because of a misconfigured router in the path.
If you are on windows system, try to use tcpoptimizer (google it) to check your connection and, most important, if you have fragmentation, then fix it. That progrram will check your connection and see if you have any fragmentation during transfers, then you can find the correct parameters to solve it.
Another parameter very important is RWIN. I'm not going to explain what it is, but it is another important source of misconfigured network. Having a wrong RWIN (almost always in windows systems) can cause a lot of performance problems. the program will help to find the correct RWIN, based on your average network ping.
Having a correct TCP/IP configuration, expecially in windows system, can help a lot in getting a good internet connection in general, not just for ryzom.
NB: generally ping will not show any packet loss, in normal situations, but is not a valid result, because ping uses by default, a packet size of 32. To see a real ping for packet loss, you should change the packet size up to MTU and see if there are packet loss. This is what tcpoptimizer do.
If you get fragmentation (and then packet loss) before you reach max size, normally 1500 or 1492 for PPPoE, you are easily into troubles.
Finally, for my actual ryzom experience, i have seen a server side problem, but in general it's not very dangerous in terms of playability.
I generally get PW's only when it's a server side problems (such as last sunday), and I don't get any (visible, because sometimes there is a slowdown but not so heavy to require the pw window opened).
Also, server side problems can also be caused by hungry yubos at datacenter, with devs trying to quiet them and wasting the performances with useless coding :D
It's obvious that the server is much more loaded than before merge, as we are getting all 3 old server people into a single one, but hopefully, WG can improve it once they can afford an upgrade.
Hope this can help a bit to solve your issues.
Packet loss cause the client and server lose syncronization and try to resync (this is what happens during the please wait window opened) resending packets till both resync. If a resync cannot be issued after a certain time, the connection between server and client is lost.
This behaviour is mostly needed because network engine of NeL uses UDP packets for communications.
When you can get packet loss? One source can be an heavy loaded server, in this case you cannot do anything, but in this case, everyone on the server would have problems, not just you.
But there is also another reason for packet loss: network fragmentation, that means network packets are fragmented due to a wrong network configuration, client OS side (almost all windows system are never well configured by default), or because of a misconfigured router in the path.
If you are on windows system, try to use tcpoptimizer (google it) to check your connection and, most important, if you have fragmentation, then fix it. That progrram will check your connection and see if you have any fragmentation during transfers, then you can find the correct parameters to solve it.
Another parameter very important is RWIN. I'm not going to explain what it is, but it is another important source of misconfigured network. Having a wrong RWIN (almost always in windows systems) can cause a lot of performance problems. the program will help to find the correct RWIN, based on your average network ping.
Having a correct TCP/IP configuration, expecially in windows system, can help a lot in getting a good internet connection in general, not just for ryzom.
NB: generally ping will not show any packet loss, in normal situations, but is not a valid result, because ping uses by default, a packet size of 32. To see a real ping for packet loss, you should change the packet size up to MTU and see if there are packet loss. This is what tcpoptimizer do.
If you get fragmentation (and then packet loss) before you reach max size, normally 1500 or 1492 for PPPoE, you are easily into troubles.
Finally, for my actual ryzom experience, i have seen a server side problem, but in general it's not very dangerous in terms of playability.
I generally get PW's only when it's a server side problems (such as last sunday), and I don't get any (visible, because sometimes there is a slowdown but not so heavy to require the pw window opened).
Also, server side problems can also be caused by hungry yubos at datacenter, with devs trying to quiet them and wasting the performances with useless coding :D
It's obvious that the server is much more loaded than before merge, as we are getting all 3 old server people into a single one, but hopefully, WG can improve it once they can afford an upgrade.
Hope this can help a bit to solve your issues.
---
GilgameeshLegion of Atys