[Data Center USA] Ping increased. Report your changes here.

Quote:

---

Originally Posted by Bourne_Endeavor

Actually, double weaving is apart of optimizing your rotation. Dragoon's opener, for instance, has you Heavy Thrust (Battle Litany + Internal Release) before hitting Leg Sweep. As for Warrior, I've been do the triple Fell Cleave under Berserk for a while. That being said, Ama is just whining as per usual. :p

---

I understand that, but the ability to get two oGCD skills into the GCD gap between 2 other skills requires a fairly low latency. What I was saying is that the ability to do that would certainly be nice to have, but it's not really anticipated by the game designers as they planned the game to be playable in environments with latency up to 220ms. having a low, sub 100ms latency would appear to be an exception rather than a rule. So for those that can do it, great but I would hat for it to get to the point where the various Metas in the game started assuming everyone can handle double weaving oGCD skills between GCDs because it's highly dependent on Internet lag which is variable at the best of times. And you know how easily things can be distorted by that kind of thing.

Oh this is rich, I'm clipping even doing Fuma Shurikens now (with only 508 skill speed). Thanks, SE. Great game.

Maybe the better option was getting a center for east/west...

I've been playing at 107 on average in Arizona and 120ish in Florida and its been fine. I've never seen a major lag issue.

I think..... and I know this never happens here.... but maybe people are overreacting?

Quote:

---

Originally Posted by Gumbercules

it might take a few days, if im right. hopefully not much longer than 2 weeks.

I feel bad now though, i get to play the game without packet loss....how dare i!? O=

---

I would guess anything up to a couple of weeks as well. Even basic DNS changes can take several days to fully propagate throughout the DNS server tree beyond the major root servers. Routing tables in possibly millions of routing nodes will need to update themselves, it's not something SE can push out, it is something that has to happen on its own.

With regard to ping times though, we've seen reports from players in South America and Europe talking of ping times in the 120-150ms range which is far from poor, and perfectly playable. That demonstrates that the server relocation is not game breaking - as long as the routing between the player and the server is decent.

Quote:

---

Originally Posted by Voltres

They are most likely losing all subscriptions from South America. It got unplayable for us.

---

No they won't, and no it didn't. People need to stop running around screaming like the sky is falling and understand that the new location itself does not cause egregious ping times, bad routing and poor ISP service does. Better to give it s week or two and complain at your ISP about the bad routing than to quit the game over something that SE cannot ever control.

Quote:

---

Originally Posted by dlgc

Well, I am in Edmonton, Canada.

My geographical distance from Montreal is about 2,978km, used to have about 75ms.

My geographical distance from Sacramento is about 1,774km, and now I have about 94ms.

I did a brief test with my BLM just now in the game, and I can see no difference in how I performed.

---

So, longer geographic distance gave a lower ping time and shorter distance gives a longer ping. I believe that this is a perfect confirmation that it is routing and not geographic location that influences your ping time.

Quote:

---

Originally Posted by Kosmos992k

I would guess anything up to a couple of weeks as well. Even basic DNS changes can take several days to fully propagate throughout the DNS server tree beyond the major root servers. Routing tables in possibly millions of routing nodes will need to update themselves, it's not something SE can push out, it is something that has to happen on its own.

With regard to ping times though, we've seen reports from players in South America and Europe talking of ping times in the 120-150ms range which is far from poor, and perfectly playable. That demonstrates that the server relocation is not game breaking - as long as the routing between the player and the server is decent.

---

I'd love to see these South America pings. I'm getting 315 right now. it was 200 before.

Hah, I wish it was 120-150. My new latency in the Netherlands is 210 without a vpn and 184 with

Quote:

---

Originally Posted by Thyranne

I'd love to see these South America pings. I'm getting 315 right now. it was 200 before.

---

270 and 300, both from Brazil.

I love the move. Dropped 60ms off my ping from the West Coast of Australia, and it's now down to 230ms :)

I wonder where all the people who were complaining about the routing on the east coast of the US before went? Maybe they're too busy playing the game now.

Quote:

---

Originally Posted by ErikMynhier

I've been playing at 107 on average in Arizona and 120ish in Florida and its been fine. I've never seen a major lag issue.

I think..... and I know this never happens here.... but maybe people are overreacting?

---

No it is not an over reacting. It needs to be coded better. Abiliites should not be innate delayed to begin with. Even art 30 ms the game was laggy for this reason. I would get lbed in PvP even if I was not near the person. The worst offense to this was when I was in sprint before the lb was hit (no sound) I was already out of range when the sound started. It was released with me being 5 miles away + wall.

The only thing I can come up with is people do not know how to see lag like this and just feels 'ok' for 'passable' play. If you want to optimize or play pvp, the game is unplayable at 100 ms or more. You shouldn't intentionally delay the game processing because you think that makes it playable at 200 ms? Have you ever try getting chain 5 +? You do not have 10 seconds to renew the chain, it is 7 because how badly the game lags from a coded standpoint, with 80 + ms on top of it, it becomes unplayable. 30 MS people still die when I use Lustrate for example, the stack is used, I see the float healed number but the person dies because of the delay. So I get wasted resources for nothing, and this can happen to LBs as well, even at 30 ms.