Same thing here, Verizon FIOS in New York. My pings to google are fine but during FFXIV i get rubber banding lag like crazy recently.
For past few days crazy rubberband lag on a powerful rig with 10ms/70+ Mbps connect..
Printable View
-
12-28-2013, 12:51 PMAria_Stars
-
12-28-2013, 01:00 PMMuzzy
I's still having this issue, anyone know a response or latest updated from SE? I'm getting to a point that I don't want to play anymore. anyone know a fix or any information would be great!
-
12-28-2013, 01:01 PMMasirus
I'm having the same issue and I've seen that people are posting about it on Reddit as well. Though I haven't seen an official reply from SE addressing it.
-
12-28-2013, 01:45 PMLeet
same issue. FIOS in New York (little bit outside of NYC)
For the first 50 or so sent on #6 it was about 80% packet loss. Got better as time went on as can be seen.
Code:|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 501 | 501 | 0 | 0 | 5 | 0 |
| L100.NYCMNY-VFTTP-162.verizon-gni.net - 0 | 501 | 501 | 2 | 4 | 178 | 4 |
| G0-13-0-2.NYCMNY-LCR-21.verizon-gni.net - 0 | 501 | 501 | 5 | 8 | 43 | 7 |
|so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net - 0 | 501 | 501 | 5 | 10 | 91 | 5 |
| 0.xe-9-1-0.BR1.NYC1.ALTER.NET - 1 | 497 | 496 | 5 | 8 | 98 | 7 |
| ae11.edge2.NewYork.Level3.net - 5 | 426 | 407 | 0 | 21 | 96 | 27 |
| vlan52.ebr2.NewYork2.Level3.net - 0 | 501 | 501 | 23 | 27 | 36 | 27 |
| ae-46-46.ebr2.NewYork1.Level3.net - 0 | 501 | 501 | 22 | 28 | 41 | 26 |
| ae-5-5.car1.Montreal2.Level3.net - 0 | 501 | 501 | 23 | 54 | 436 | 26 |
| ae-11-11.car2.Montreal2.Level3.net - 21 | 273 | 216 | 12 | 29 | 209 | 14 |
| ORMUCO-COMM.car2.Montreal2.Level3.net - 0 | 501 | 501 | 22 | 28 | 40 | 30 |
| 192.34.76.10 - 1 | 489 | 486 | 25 | 28 | 93 | 25 |
| 199.91.189.242 - 1 | 497 | 496 | 25 | 27 | 44 | 26 |
| 199.91.189.30 - 2 | 479 | 473 | 30 | 31 | 37 | 31 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
-
12-28-2013, 02:10 PMMuzzy
i did the WTFast client and it works! it is going to save me
-
12-28-2013, 04:31 PMKMarsara
i wouldnt hold my breath on SE addressing anything, see that 160+ page thread on sticky, they dont even look at that... maybe itll just go away when the more people get bored and stop playing, or at least when school is back in session
-
12-28-2013, 06:25 PMAria_Stars
unfortunately until this is fixed, the best thing I can suggest is to use a proxy tunneling service like Smoothping, WTFast, Battleping, etc (and the many other variants) because it will change the route your internet takes to the FFXIV servers. It's fixed my issues so far.
-
12-29-2013, 12:45 PMcatfight
yeah, ever since the update on Sunday been getting horrible crap. can't even do HM Titan properly because of how land slide appears and crap. Please fix this crap.
-
12-30-2013, 06:53 AMContemporary
I wish for this to be addressed within one month.
-
12-30-2013, 11:30 AMSwanhavenOh my god, I could kiss everyone in this thread that recommended the WTFast. Just did several flawless dungeon runs, no problems.Quote:
Originally Posted by Kirwen
How the hell did this fix the problem so easily? -
12-30-2013, 01:13 PMKMarsara
dont you think its retarded how you have to get a 3rd party app to make the game work
-
12-30-2013, 01:27 PMRaistBecause it is a problem along the route your ISP and their partners are using to get you to SE's servers. Using a VPN or Proxy service that offers a more optimized route is allowing you to avoid the over congested hops you are being directed to normally.Quote:
Originally Posted by Swanhaven
-
12-30-2013, 07:18 PMBurien
Today I noticed hotbar actions just not firing off on command, which is slowing combos for hate. I'm hoping the problem is addressed as being on PS3 and I did the DMZ which I thought initially fixed the problems but it's back again. I have to agree with your comment, it doesn't make sense to have to pay extra to play 14. I could understand if everything had lag/spikes/disconnects but I been testing on PC/PS3 and everything runs fine but 14. I'm hoping to see a resolution but as long as my friends are playing I will have to do my best with what we have.
-
12-30-2013, 11:39 PMSwanhavenThe extra hurdles to entry is what gives that old familiar Final Fantasy MMORPG feeling. The hallmark of Square MMOs is that you practically have to fight them into letting you play their games.Quote:
Originally Posted by KMarsara
I really hope this issue gets fixed before my free trial runs out because yeah, it's a mite ridiculous that I have to go through a proxy just to not rubberband all over a dungeon. -
12-31-2013, 07:48 PMRomanianRambo
This crazy rubberband lag started happening to me since Friday. First time I've had this problem ever since I got the game a few months ago.
Saturday morning it went back to normal and I was able to play but this morning it went back to "slow motion mode". -
12-31-2013, 10:37 PMRemitahll
Just adding my two cents, I have the same issues as listed by everyone else. I would say this became noticeably bad AFTER they performed their maintenance last week on the 26th or whatever day last week. Tracert shows the same hop lagging horribly for me and I was getting consistent 90000 errors last night trying to do extreme mode primals. There would either be rubberbanding and everything freezes up for a second or two or I would just get kicked instantly with a 90k error. This is from Western Mass using Charter Internet.
-
01-01-2014, 03:11 AMnightmaric1
am I in the minority where WTFast doesn't work for me?
I was doing a Pharos and I got two 90ks and caused two wipes because of rubberbanding issues. I kind of don't want to play this game anymore due to these issues. -
01-13-2014, 02:22 AMDRay
I still have the lag issue up to now.
SE did nothing to it. -
01-13-2014, 05:24 AMVegaNovus
I'm still having this issue, uploading a video now.
http://youtu.be/3zAm9CdRyxU -
01-13-2014, 06:58 AMFlintNoireLatency Issues
Started yesterday for me 1/11/13. Issue is as described. Ability would come off cool down and be ready, however, on attempting to use i would get the "ability not ready " message. The cool down shader will then return on the ability for 2-3 secs.
-
01-13-2014, 09:31 AMKeruvindesecond batch is from an early morning test i did when i assume there was less traffic during a weekdayCode:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 1405 | 1405 | 0 | 0 | 6 | 0 |
| L100.TAMPFL-VFTTP-70.verizon-gni.net - 0 | 1405 | 1405 | 5 | 10 | 277 | 8 |
| G0-3-2-3.TAMPFL-LCR-21.verizon-gni.net - 0 | 1405 | 1405 | 8 | 13 | 39 | 14 |
|so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net - 0 | 1405 | 1405 | 7 | 18 | 184 | 24 |
| 0.ae1.BR1.MIA19.ALTER.NET - 2 | 1311 | 1287 | 0 | 15 | 56 | 14 |
| 204.255.168.30 - 4 | 1240 | 1198 | 54 | 57 | 105 | 57 |
| be2054.ccr21.mia01.atlas.cogentco.com - 6 | 1168 | 1108 | 55 | 58 | 66 | 56 |
| be2124.mpd21.atl01.atlas.cogentco.com - 1 | 1355 | 1342 | 71 | 82 | 99 | 80 |
| be2170.mpd21.dca01.atlas.cogentco.com - 4 | 1228 | 1183 | 80 | 84 | 99 | 85 |
| be2150.mpd21.jfk02.atlas.cogentco.com - 4 | 1224 | 1178 | 88 | 92 | 104 | 92 |
| be2108.ccr21.ymq02.atlas.cogentco.com - 4 | 1255 | 1217 | 95 | 99 | 107 | 100 |
| 38.122.42.34 - 1 | 1402 | 1401 | 55 | 59 | 71 | 65 |
| 192.34.76.10 - 2 | 1315 | 1292 | 68 | 74 | 128 | 74 |
| 199.91.189.242 - 2 | 1344 | 1328 | 70 | 72 | 269 | 73 |
| 199.91.189.38 - 2 | 1332 | 1313 | 70 | 73 | 83 | 72 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
i dunno how to post this O.o so it lines up rightCode:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 1087 | 1087 | 0 | 0 | 6 | 0 |
| L100.TAMPFL-VFTTP-70.verizon-gni.net - 1 | 1083 | 1082 | 5 | 11 | 231 | 8 |
| G0-3-2-3.TAMPFL-LCR-21.verizon-gni.net - 1 | 1080 | 1078 | 8 | 13 | 138 | 13 |
|so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net - 1 | 1080 | 1078 | 8 | 18 | 134 | 95 |
| 0.ae1.BR1.MIA19.ALTER.NET - 1 | 1068 | 1063 | 12 | 15 | 124 | 16 |
| 204.255.168.30 - 1 | 1076 | 1073 | 13 | 20 | 105 | 20 |
| be2054.ccr21.mia01.atlas.cogentco.com - 1 | 1083 | 1082 | 15 | 21 | 158 | 16 |
| be2124.mpd21.atl01.atlas.cogentco.com - 1 | 1080 | 1078 | 42 | 45 | 170 | 44 |
| be2170.mpd21.dca01.atlas.cogentco.com - 1 | 1083 | 1082 | 40 | 42 | 171 | 41 |
| be2150.mpd21.jfk02.atlas.cogentco.com - 0 | 1087 | 1087 | 47 | 50 | 138 | 52 |
| be2108.ccr21.ymq02.atlas.cogentco.com - 0 | 1087 | 1087 | 55 | 58 | 146 | 56 |
| 38.122.42.34 - 1 | 1080 | 1078 | 55 | 57 | 186 | 58 |
| 192.34.76.10 - 0 | 1087 | 1087 | 57 | 62 | 161 | 60 |
| 199.91.189.242 - 1 | 1079 | 1077 | 57 | 61 | 256 | 59 |
| 199.91.189.38 - 0 | 1087 | 1087 | 58 | 62 | 150 | 62 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Wireless_Broadband_Router.home - 0 | 766 | 766 | 0 | 0 | 5 | 0 |
| L100.TAMPFL-VFTTP-70.verizon-gni.net - 0 | 766 | 766 | 5 | 10 | 201 | 7 |
| G0-3-2-3.TAMPFL-LCR-21.verizon-gni.net - 0 | 766 | 766 | 7 | 13 | 60 | 24 |
|so-2-0-0-0.TPA01-BB-RTR1-verizon-gni.net - 1 | 763 | 762 | 7 | 18 | 127 | 12 |
| 0.ae1.BR1.MIA19.ALTER.NET - 2 | 719 | 707 | 13 | 16 | 50 | 15 |
| 204.255.168.30 - 7 | 602 | 560 | 55 | 57 | 70 | 58 |
| be2054.ccr21.mia01.atlas.cogentco.com - 5 | 652 | 623 | 55 | 57 | 69 | 63 |
| be2124.mpd21.atl01.atlas.cogentco.com - 1 | 744 | 738 | 0 | 83 | 100 | 90 |
| be2168.ccr21.dca01.atlas.cogentco.com - 4 | 680 | 658 | 80 | 85 | 97 | 85 |
| be2150.mpd21.jfk02.atlas.cogentco.com - 5 | 660 | 633 | 88 | 92 | 130 | 97 |
| be2108.ccr21.ymq02.atlas.cogentco.com - 2 | 712 | 698 | 96 | 100 | 159 | 102 |
| 38.122.42.34 - 0 | 766 | 766 | 56 | 63 | 86 | 60 |
| 192.34.76.10 - 2 | 728 | 718 | 69 | 73 | 126 | 73 |
| 199.91.189.242 - 2 | 723 | 712 | 70 | 72 | 124 | 71 |
| 199.91.189.38 - 1 | 747 | 742 | 70 | 73 | 124 | 72 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
EDIT* fixed -
01-13-2014, 12:05 PMTrett
I'm at my rope's end with this one. I get insane rubberbanding and not even WTFast and whatnot are helping. I really hope something gets worked out soon. It's really frustrating when I can't even get past phase one in Titan EX because the Weights detonate 5 seconds after the cast bar due to lag.
-
01-14-2014, 02:25 AMNoobest
The lags i had today don't even compare to the lags iv'e been having for months... 10-30 second lags nonstop, game is pretty much unplayable ._.
-
01-15-2014, 07:00 AMKMarsara
bump for answers
-
01-15-2014, 09:59 AMWobbler
For those of you seeking a response from Square on this, I just got a response back from a ticket I logged with them. Square said that you must start a live chat session with them to troubleshoot the issue.
After a brief 5 minute live chat the overall response from Agent Napoleon G was .....
Agent Napoleon G: When it comes to packet loses, we could not do anything about that. Only your ISP could assist you with that.
I have spoken with with my ISP and they have said that I should speak to Square Enix.
I told Agent Napoleon G that he prolly should head over to these forums and let everyone know that they are screwed, but he told me he had other customers issues to deal with. -
01-15-2014, 11:44 AMOranz
So I am having the same issues, and guess what, I HAVE FIOS TO!!! So here is my question, and im not a network person, and while i understand some generalized things about coding and the concepts, I'm not a huge computer guy. But when everyone that is on the SAME provider, and located in the same general regions, and this problem showed up ONLY AFTER a patch update.. wouldn't it be safe to say SE somewhere long the line you screwed stuff up vs blaming our ISP? Seeing as our ISP was doing the same thing it always does and the only factor that changed was you?
Sorry i don't mean to sound like an Ass, or like a "rager" but its quite frustrating when this many people have reported an issue, and for a month now it has been around, but we have yet to see you make any form of a public response, or at least so far as i have found you have not. I'd much rather have a "We have no clue whats wrong, but we are looking into it and are rying to fix the problem" then "..."(silence)
I hope someone in SE reads this, but i doubt this will happen. It would be nice to see this problem addressed before you lose most of the eastern side of the US -
01-15-2014, 11:47 AMVanroeFrom my understanding, the issue lies along the middle. I think there is some packet loss along the network, coming from an intermediary network in between the FIOS network and the SE servers. Why is it happening after 2.1, well remember they increased the server position checks to help deal with the "out of the aoe, but still get hit" problems people were having. This change/increase in traffic probably doesnt sit well with the intermediary network, and they are either throtteling it or dropping packets, that would be my guess.Quote:
Originally Posted by Oranz
Unfortunately since it lies outside the FIOS network, verizon wont/cant do anything, and Square cant do anything since its not server related. The easy fix would be to revert the server position check changes they made, if that is indeed the cause.
The fix on the client side is using a service like WTFast, to reroute your traffic around the problem network, but unfortunately that comes with a subscription fee, and it doesnt work for everyone. (there is a 30 day trial so you can see if it does fix the problem) -
01-15-2014, 12:04 PMOranzI shall try WTFast, ive never used it before bc FIOS along with a good computer have been plenty for running a smooth game on any other mo ive played, which is quite the list, but you said this doesnt work for everyone, can you touch on some of the reasons it might not be working even after using a ping program like wtfast?Quote:
From my understanding, the issue lies along the middle. I think there is some packet loss along the network, coming from an intermediary network in between the FIOS network and the SE servers. Why is it happening after 2.1, well remember they increased the server position checks to help deal with the "out of the aoe, but still get hit" problems people were having. This change/increase in traffic probably doesnt sit well with the intermediary network, and they are either throtteling it or dropping packets, that would be my guess.
Unfortunately since it lies outside the FIOS network, verizon wont/cant do anything, and Square cant do anything since its not server related. The easy fix would be to revert the server position check changes they made, if that is indeed the cause.
The fix on the client side is using a service like WTFast, to reroute your traffic around the problem network, but unfortunately that comes with a subscription fee, and it doesnt work for everyone. (there is a 30 day trial so you can see if it does fix the problem)