Should? Maybe you aren't familiar with ISP companies. The precise reason VPN's help with ping is because ISP's don't give you good routing. Ever.
Printable View
You mean the 1.0 where the door to Quicksand caves lagged and you couldn't enter or leave. Or the awesome retainer market system where retainers wouldn't load even if you were standing on them?
Legacy players need to stop lording their dedication to a bad game over others. Plus need to stop treating certain individuals like messiahs.
I live in Rio de Janeiro. Went from 150 to 200/230. I main heal and now I cant keep activating and deactivating cleric stance constantly because it takes too long to compute. If I press swiftcast and another action it starts to cast the action as if I didnt press swiftcast. Its frustrating...
I been trying to address it for a while as well, as here is an older thread of mine:
http://forum.square-enix.com/ffxiv/t...me-too-slow%29
There was other posts where I say "I still see this lag at 30-50 ms" and the reply I get " are you on a 56k modem? your computer is out of date... Maybe people really just do not notice it? I do not see how when it goes into LBs as well, you can use the LB meter and have nothing happen because it is too slow to register and you are dead. So if you never lbed why did the meter get used? coding needs to "git gud" People with quick reaction times should be able tell the difference of lag issues as far as internet networking and something weird with the game coding. It feels different and one always happens while the other is issues here and there. So my guess people tell you that because they have slower reaction times then we do, or they are just used to it and see it as normal. Also for the people saying they can double weave at 100 ms, I bet you they are clipping off the next gcd doing that.
The real point of difference appears to be somewhere in the high 70s to low 80s. Below that point you will see zero difference in rotational throughput with identical double-weaved rotations. Previously I could occasionally get as low as 82 ms some nights but generally hovered around 100 ms. The difference was enough for me to shave off some 70 skill speed while still barely meeting bonus potencies in certain extended rotations. It's significant. It's not huge, but it IS definitely noticeable. My ping has since fallen to ~35, however, and there has been zero difference in the same gear with the same rotation between the new, reduced latency and the low-80s ms ping.
Just speaking from my experiences without using WTFast, wherein I have 40 to 100% higher ping times due to horrible routes to the server, it also seemed like the difference seemed to taper off again in terms of how oGCDs were handled after ~160-170 ms latency. Regardless at that point you're forced to single-weave for best net output (true unless you'd waste the oGCD in most cases past 110ish ms), but after 160 didn't seem to make much difference in how much the oGCD clipped the GCD, even going up to around 300 ms. It did, however, make the full difference in AoEs. There's the abysmal tick frequency, and then there's a third of a second atop it. I'd often appear to be out of an AoE circle a full second before its collapse and still be hit. By 160, it felt almost fair. 100, due to the time spent at that latency, felt very fair. And now, at 30, I feel like I'm accidentally running into AoEs by returning to my spot apparently a little too soon. Sync/desync with the server polling rate makes this hard to test, but it would seem that only the oGCDs or other queuing functions seem to follow a sort of tiered and retiered taper in regards to latency's actual effects.
I had a similar experience at Gold Saucer - I had a horrible time with the "stop the moving bar on the line" mini games...I was not used to it stopping instantly (despite only recently starting playing them) and not having to hit the button a bit ahead of time, lol.
The previous server was 3008 miles from my house according to google maps. 115 ms ping.
The new server is 280 miles from my house according to google maps. 80 ms ping.
New server with WTFast: 25 ms ping.
See where the larger difference is? *Nudge, nudge*
Admittedly though, I figured the move would be to somewhere like to get something like Denver, Chicago, Kansas City, Houston, or Dallas. Not... to one corner of the supported area.Also, SA servers and added localization support any time soon?...Annnd here's hoping that improvements to net code may shave off a bit of the effect, in my case enough to play on the JP servers if I wish, now that I have a new NA server on my doorstep. Cus why not? Need my language practice.
I know that there is a thing where you can manually enter in Google's public DNS servers. Not sure if it affects ping etc, though. It's easy to find info on this online.
Pretty much topic.
We had to drop our NIN from static because he's on the East Coast with such high ping. It's crazy.
Go on SE, you know you need to, make a NAWest and NAEast DC...