For past few days crazy rubberband lag on a powerful rig with 10ms/70+ Mbps connect..

**Keruvinde** · 01-13-2014 09:31 AM

Code:

|------------------------------------------------------------------------------------------|
|                                      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

second batch is from an early morning test i did when i assume there was less traffic during a weekday

Code:

|------------------------------------------------------------------------------------------|
|                                      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 |
|________________________________________________|______|______|______|______|______|______|

	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
    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 right
EDIT* fixed

**Trett** · 01-13-2014 12:05 PM

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.

**Noobest** · 01-14-2014 02:25 AM

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 ._.

**KMarsara** · 01-15-2014 07:00 AM

bump for answers

**Wobbler** · 01-15-2014 09:59 AM

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.

**Oranz** · 01-15-2014 11:44 AM

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

**Vanroe** · 01-15-2014 11:47 AM

Originally Posted by Oranz

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)

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)

**Oranz** · 01-15-2014 12:04 PM

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)

I 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?

Thread: For past few days crazy rubberband lag on a powerful rig with 10ms/70+ Mbps connect..

Thread Tools

Search Thread

Display