So my thinking wasn't off then. And with a 2.5 or even a 2.3gcd a 200ms(aka 0.2s) latency let's say a diff of 170ms between a 30ms player wouldn't be noticable at all... Sure if gcd would be 2s then this would have an impact due to off gcd use.Thought this as well, but got taught better: http://forum.square-enix.com/ffxiv/t...=1#post2475927
So, with pre-qeueing like FF does, it is possible to put out the same DPS numbers
They are renting the data centre in Canada not owning it. That means if all a sudden players have to leave the game and go to the new shiney SE can fallback and merge all of us back to jp servers. Thus removing anymore investment. They can do the same for EU as well. Rent the space and fallback if that many jump ship. I don't expect that to be a problem though. They market this game too heavy in the EU market and a lot of them play this game religiously. Dedicated players. All they are asking for is a localized server in their part of the world. I support this.
Yeah sadly that is the thing that can cause issues to everyone. You can try contacting your ISP to see if they can change anything or if you have an option try it on a diff ISP(friend that isn't using the same one).
Bah.
"I will show you that superior servers have their limits when they go up against superior players!" - Char Aznable
EU players are better, they don't need EU servers - that would make things too boring.
Tried WTFast and it changed -zip-. So I'm still not convinced that it is a routing issue.
With or w/o WTFast I get something in between:
Send 100-650 Receive 1000-3000
Oh well as I said: I can dodge 85% just fine, but nevertheless I will stay out of raid content that features instagib mechanics.
It just sucks to wipe the group due to latency stuff.
Hmmm since that is data/s and not latency info I wonder if there's some throthling going on by your ISP in this case(hence the link to that forum post about it)(and they could be thorthling both vpns and ffxiv).Tried WTFast and it changed -zip-. So I'm still not convinced that it is a routing issue.
With or w/o WTFast I get something in between:
Send 100-650 Receive 1000-3000
Oh well as I said: I can dodge 85% just fine, but nevertheless I will stay out of raid content that features instagib mechanics.
It just sucks to wipe the group due to latency stuff.
In our static we had someone from south africa... they had serious issues dodging stuff. In the end though we even got them to dodge divebombs. But they really had good and insanely bad days with their connection. Atm they can't do anything it takes seconds to open the retainer menus.
I myself had at one point some weird lag issues where the game would stall for 5s every 20s or so... Even with that though I was still able to do titan hm.
With wtfast try the same traceroute to see where it's going through. I would invite you to a LS so we can try running stuff together sometimes - and hell the more the merrier.
Why would they display that? ugh...
Okay... where can I see my latency then?!
Well titan HM was a mixed bag. He never hit me with the straight AE that kicks unless I derped myself, but the round thingies were a different matter.
Sometimes I am outside when they disappear, yet I still get the damage.
The randoms dropping them all over the place didn't help either, sometimes they overlapped so absurdly that there was no way out.
As far as P2P throttling goes: I don't think my provider does that. I can dl with 3 MByte/s from unencrypted torrents.
Edit:
After speaking with ruskie:
You have to manually ping your server via command prompt in order to see your latency. Currently I have 109ms, which is very good.
We came to the conclusion that "voidzone-lag" is created through the 300ms position refresh interval. combined with 100ms latency that's almost half a second. Enough for the close call: "I was out but got hit anyway scenarios".
He suggested spamming a cast to force an update of the position.
Last edited by Granyala; 10-04-2014 at 01:02 AM.
Congratulations to Aussie Wow players!!!
Oceanic servers are being physically moved to Sydney.
That takes wow servers to New York, Chicago, Phoenix, Los Angeles, Frankfurt, Paris, Stockholm, Sydney plus Chinese and Russian servers. Allowing players to select the server located nearest to them for the best play experience.
First of all, latency wise these results aren't bad. Your RTT1, RTT2 and RTT3 to the destination ip are 109, 109 and 110ms. An average of 109. In other words, it takes just 109 ms for the sent signal to reach the server AND for the response to come back. A speed which is to be expected from a western European country.
The number of hops, being at 21, is relatively high. However, there do not appear to be any specific routing delays. Yes, there are some request time outs going on in between Hamburg and New York, but this is common. In order to prevent simplistic DDoS attacks such hubs often block simple ping and tracert commands. The signal sent to that server will simply be ignored.
So one thing is pretty certain in this case, latency is not what's hindering you. What might be is packet loss. That is more commonly an issue at home rather than within the actual route though. For example wireless networks being used rather than wired networks. Cheap routers being used. Etcetera. With a 100ms polling frequency on the FFXIV servers any form of packet loss is killing. If 2 packets in a row would be dropped, you're directly on a 300 ms delay.
Check for packet loss on pingtest.net. See if you get the wanted 0% score, or whether you reach anything higher than 0% (unacceptable for gaming). Also test it during moments you notice yourself to be lagging. Certain routers may be fine on letting packets through most of the time, however may instantly start dropping once a certain number of in- and outgoing connections are opened. If someone on the network opens up a torrent client, MMO launcher with p2p updating enabled, etc. this may instantly kill your performance.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.