Is it me, or are these new servers EXTREMELY Lagtacular?!?

[maxmolly]

It was wednesday evening, between 7 and 10 pm CST, thats Texas in the U
SA, and I got many please waits, and two total freeze ups. This is the worst its been in a month. Upgrading servers and moving there location and then this, coincidence, I think not. I'm with Beefy, something went wrong. Lets hope it gets resolved as I do Love the game.

[zanthar]

I had similar problems last night, when a couple of guildies and I decided to trek one of our new members to Pyr from Yrk. Here's the breakdown of where we are from IRL two of us are from U.S. we had no serious problems, one from U.K. no issues, and the last was from Australia got lag spikes that lasted minutes at a time. So after this person lagged up a few times we had to abandon the trek cause we got tired of "getteing caught with our pants down" so to speak and getting wiped a couple of times. After this I went to Fount and there I started up with lag spikes and even got dropped a couple of times and called it a night!

[sprite]

Good point: (etc)

Just a point; replace "Intro" with "Enter" or "Return" and you're done

You can also use Pingplotter which is a very nice graphical program which does it more dynamically and allows you to save the result as a text file or a graph

[meitemax]

pathping is also a nice tool to figure out if any of the nodes along the road is flunky. (does the tracert thingy, just over more turns)

[forever]

The first IP I hit is this one 213.208.119.189. This seems to still be one of Jolts servers, will this server be moved to the same spot as the rest?

[neofyte]

Yes Slay, I was watching as first you, then Tinks, then Torqe all crashed within 1 minute. I have only crashed once since the server move, but I have had several longish "please waits", and to return from them to find your toon kissing the dirt, pick in hand, while the spawn clock winds down is annoying to say the least. I will be sending in a trace to gameforge ( or at least trying, it looks a little techy to me) and I urge everyone else who is experiencing these problems to do the same. We must have a bad "hop" somewhere between NA and Germany.

Dragan
Cho

(logging from western Canada)

[spursfc]

Had problems myself last night, first attempt to login resulted in a crash on the last part of loading. Finally logged into Cho/Fairhaven, lag seemed about normal. Went to switch chars and game crashed again at final loading point so I gave up . I would say that crashes like that aren't unusual for me and I'm sure its the client and my net connection rather than the servers.

[flume641]

Man, this lag/connection since the server change has been unplayable at times for me, and many others I game with, is this happening for many others as well?

I've been given "please wait" signals that never quit and froze my game up 5 times since monday, and thats not even mentioning the more bearable ones that come in the 10-20 second stall variety, or the ever popular "rapid fire" please wait flavor that has been enjoyed by thousands since ryzoms launch.

I sure hope that this is just "growing pains " of the new servers, and that this isnt to be expected or regular from now on. No matter how bad the loss of our GM/CsR's are, at least I was looking forward to the "silver lining" of having more reliable servers, which for me has most definetly not been the case since the move.

Does anyone else notice the same problems? Is it just me? Am I going crazy? Where did my pants go? .....wait...where DID my pants go?!?

Its seems like they work, but the lines from France into UK may be a bit... umn.. you get the idea

[stijn]

I had those probs too a while ago. I runned ryzom_recover a few times, and now it seems to be better, could be i got more stable with the latest patch though, not sure.

[mentloid]

Phelan.. I've got bucketloads of tracert log files you can have if you want them.

The general jist of them is this... 0% packetloss on all hops even when I get booted.

Also, I did a lotta testing with a few of the people who can't connect at all. Thier client doesn't pick of the new server name/ip. They can ping it, plot it, tracert it rDNS it etc.. but can't connect. The client.log file states that it's still trying the old JOLT IP address as a server. ATM, I've been unable to asertain where or how the client determines where the server is located. I've checked the DNS entries and lookups with the client both by analysin the data my client sends/receives on handshake, and checked with the people who can't connect. The DNS resolves correctly. I'm stuck wondering if some versions of the client have the IP hardcoded in them? In anycase, I'll be tackling it again tonight, to see if I can't figure some more out. Also... I noticed the handshaking ports might be different. I'm unsure about that yet as I don't have any documentation on the old handshake ports.