Constant Disconnects = Game Unplayable

[blaah]

The server is instable, and that is due to PROTOCOLL miscommunication.
In english that would be, the server is not sending/recieving small packets of data constantly, but sending/recieving bigger packets with a 0.92 second pause.

open 'connections' window ingame (shift+n i think) and watch how up/down/ping changes. every change represents communication with server. it is contant communication and it is your router/isp problem if it disconnects (especially if it disconnects in contant time, 5min/10min, every time after login). Ryzom uses UDP and that what most cheap simple routers have trouble with (some expensive with cheap firmware too)

the fact that game does not have timeout for 'Please wait' window is unfortunate yes.

For me from port 1111 - 30499 and 47855 - 60000 are blocked.

hmm... 3724 is what wow uses. quess no-one plays it there then

[eadwig1]

open 'connections' window ingame (shift+n i think)

It's just N. It will aslo give the server state. i.e. Stalled or FSLost.

Ryzom uses UDP and that what most cheap simple routers have trouble with (some expensive with cheap firmware too).

IIRC Zerlin once said that the problem was Windows and some routers implementing UDP in a non standard way.
I guess you could blame the dev(it was Olivier Cado) for designing a network system that used a protocol that was not
properly implemented on the OS it was to be run on. On the other hand it was supposed to be open source<*cough-linux & mac clients-cough*>
And there could have been other design factors invovled.

____________
Gilmar

[falkon33]

Perhaps setting up a "Static" connection would help. This is where you manually type in what your IP, DNS and other information is and Windows wont allow it to change.

But first, you need that information! So it's

"Start, Run, cmd.exe, cd\, ipconfig /all" and there will be all the info you need.

As for creating a static connection, I would google "creating a static ip address" and a bunch of sites will show up giving much better details than I could since it's been a few years.

If you are running through a router, try running direct from your modem. If that keeps you online, you know where the problem is.

[onedreamer]

I know that I also am having the same disconnect issue and am also in America. I ran some traceroutes on the 213.208.119.98 IP and did notice that I would always timeout the packets after the 15th hop (see below for last two hops of traceroute) so as a previous poster had stated, it does seem to be an issue with the transport side of the house and not any problem with either the game or the user's computer (my computer is a 3 Ghz Sony Vaio with 1.5Mb RAM, GeForce 7800 vid card with 256Mb RAM, running on Windows XP SP2). I ran five traceroutes and always had the same results.

Tracing route to 213.208.119.98 over a maximum of 30 hops

14 111 ms 114 ms 114 ms lon1-9.nildram.net [84.12.224.14]
15 133 ms 109 ms 113 ms jolt-gw.nildram.net [195.149.20.214]
16 * * * Request timed out.
------
30 * * * Request timed out.

This most probably only means that the 16th hop will not respond to ping. If you had a response around 1.000 ms then that would be a sign of an issue.