Rubberbanding!

Well since the last patch I've been getting a lot of rubber banding for some reason now.

Now it doesn't happen when I don't care but it does when I'm doing things like Titan Ex and T5 when it really matters.

Don't know if I can fix it by using a VPN as my connection looks good to begin with but I don't know. Any suggestions?

C:\>tracert 184.107.107.176

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 15 ms 12 ms [0.0.0.0]
3 9 ms 12 ms 8 ms rd3bb-tge0-12-0-14-1.vc.shawcable.net [64.59.150
.9]
4 17 ms 17 ms 11 ms rc2bb-tge0-14-0-6.vc.shawcable.net [66.163.68.12
9]
5 16 ms 22 ms 15 ms rc5wt-tge0-2-0-15.wa.shawcable.net [66.163.78.22
6]
6 13 ms 12 ms 14 ms ix-1-2-2-0.tcore1.00S-Seattle.as6453.net [64.86.
123.53]
7 13 ms 14 ms 15 ms if-11-0-0-5.core1.00S-Seattle.as6453.net [64.86.
124.25]
8 83 ms 83 ms 87 ms if-8-2-3-0.tcore2.CT8-Chicago.as6453.net [64.86.
124.30]
9 87 ms 83 ms 88 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
10 104 ms 85 ms 117 ms 66.198.96.58
11 84 ms 83 ms 83 ms po22.cr1.mtl.iweb.com [184.107.1.1]
12 84 ms 97 ms 84 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
13 84 ms 86 ms 118 ms 72.55.128.44
14 85 ms 86 ms 86 ms 184.107.107.176

Trace complete.

Put in a suggestion about this in-game a minute ago, this has become an unbearable hurdle for us since our members are getting +1,5sec rubberbanding during our primetime which is stopping us from progressing.

Welcome to the club; sadly...

Quote:

Originally Posted by Gares

- snip -

Gares, try doing a continuous ping instead. What your tracert shows is a rather good ping time of <100ms but 'rubberbanding' is typically caused by packet loss which usually happens somewhere between the server and you.

1-2% packet loss is usually 'playable'. 10% means you will have a heck of a time in Titan Ex.

Shaw's connection to Montreal seems rather good from your tracert. I used Cogent recently, the ping times were easily 5x-10x greater. Especially during the 'netflix' period (local time 8pm - 10pm in the USA/North America).

-----

Although this might not be the fault of SE at all, it doesn't mean that pressure can't be brought to bear so as to improve the connection (better bandwidth allocation/peering/etc).

Also need to be looking at the proper IP... that IP is for a webserver hosting sites for games in the EIDOS brand, and forwarders for other SE affiliated sites. It's not connected to the FFXIV game servers, physically located in a different section of town, and runs on i-web lines and not Ormuco. So, you aren't getting an accurate indication of your connection to the game servers.

To find the proper IP, open resmon from the run/search line or netstat from a command prompt while you are fully logged into the game and look at your active connections. Resmon will list the ones ffxiv.exe is currently connected too, while netstat with no switches will just list the states of all recent connections that have yet to time-out completely (many may show they are in wait state). What you are looking for are IP's starting with 199 for the servers in Canada and 124 for servers in Japan.

Notice the considerably different paths to both IP's from this laptop.. it's different from the 4th hop forward:

Code:

Tracing route to 184.107.107.176 over a maximum of 30 hops Tracing route to 199.91.189.25 over a maximum of 30 hops 0 G75VXLAP [10.10.100.10] 0 G75VXLAP [10.10.100.10] 1 LPTSRV [10.10.100.1] 1 LPTSRV [10.10.100.1] 2 cpe-098-025-064-001.sc.res.rr.com [98.25.64.1] 2 cpe-098-025-064-001.sc.res.rr.com [98.25.64.1] 3 cpe-024-031-198-005.sc.res.rr.com [24.31.198.5] 3 cpe-024-031-198-005.sc.res.rr.com [24.31.198.5] 4 xe-6-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.66] 4 xe-7-0-0.rlghncpop-rtr1.southeast.rr.com [24.93.64.40] 5 107.14.19.42 5 107.14.19.44 6 so-1-1-1.c1.buf00.tbone.rr.com [66.109.1.113] 6 ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169] 7 ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149] 7 te0-16-0-23.ccr41.iad02.atlas.cogentco.com [154.54.10.209] 8 if-2-2.tcore1.AEQ-Ashburn.as6453.net [216.6.87.2] 8 be2113.mpd21.dca01.atlas.cogentco.com [154.54.6.170] 9 64.86.85.1 9 be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118] 10 if-10-2.tcore1.TTT-Scarborough.as6453.net [64.86.32.33] 10 be2108.ccr21.ymq02.atlas.cogentco.com [154.54.3.134] 11 if-9-9.tcore1.TNK-Toronto.as6453.net [64.86.33.25] 11 38.122.42.34 12 if-7-2.tcore1.W6C-Montreal.as6453.net [66.198.96.61] 12 192.34.76.10 13 66.198.96.58 13 199.91.189.242 14 te7-3.dr9.mtl.iweb.com [67.205.127.214] 14 199.91.189.25 15 72.55.128.44 16 184.107.107.176

I'm rather curious, you ended up with a longer path to s-e-m.com than to Leviathan?

My rather terrible ping from the UK.

Code:

1 282 ms 284 ms 285 ms 172.16.0.1 2 284 ms 284 ms 285 ms 93.XXX.XXX.41 3 285 ms 287 ms 285 ms router.lon-a12.as39458.net [46.23.69.50] 4 282 ms 280 ms 283 ms te0-7-0-12.ccr22.lon01.atlas.cogentco.com [149.11.142.41] 5 287 ms 287 ms 283 ms be2317.mpd22.lon13.atlas.cogentco.com [154.54.73.177] 6 284 ms 285 ms 285 ms be2314.ccr21.lon13.atlas.cogentco.com [154.54.72.253] 7 291 ms 290 ms 291 ms be2399.ccr21.lpl01.atlas.cogentco.com [130.117.0.5] 8 360 ms 361 ms 362 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137] 9 364 ms 361 ms 360 ms 38.122.42.122 10 361 ms 363 ms 361 ms te7-4.dr9.mtl.iweb.com [184.107.1.110] 11 361 ms 361 ms 361 ms 72.55.128.44 12 364 ms 364 ms 363 ms 184.107.107.176 1 283 ms 282 ms 282 ms 172.16.0.1 2 286 ms 617 ms 283 ms 93.XXX.XXX.41 3 284 ms 286 ms 284 ms router.lon-a12.as39458.net [46.23.69.49] 4 284 ms 285 ms 283 ms 92.60.249.45 5 299 ms 284 ms 284 ms ae10-161.lon11.ip4.tinet.net [141.136.102.177] 6 285 ms 284 ms 285 ms be3008.ccr21.lon01.atlas.cogentco.com [130.117.15.21] 7 285 ms 284 ms 287 ms be2314.ccr21.lon13.atlas.cogentco.com [154.54.72.253] 8 291 ms 293 ms 291 ms be2285.ccr21.lpl01.atlas.cogentco.com [130.117.49.126] 9 361 ms 361 ms 363 ms be2384.ccr21.ymq02.atlas.cogentco.com [154.54.44.137] 10 360 ms 360 ms 361 ms 38.122.42.34 11 361 ms 360 ms 361 ms 192.34.76.10 12 361 ms 360 ms 361 ms 199.91.189.242 13 362 ms 361 ms 360 ms 199.91.189.21

Ping times were the same, regardless... about 355-360ms. Going across the pond to San Diego, I'm down to 120-130ms.

-----

What did those VPN services do for the connection? I understand most of them give a free trial (disconnects every 20 minutes... about enough for a WP speedrun ^-^), so you could try them out to see if they are worth the money.

Instead of doing a tracert, do a pathping to see if you're getting packet loss anywhere on the route. Just type pathping and then the IP address. It takes a lot longer, but it will give you the route and 100 pings to each server along it, and comes out as follows:

Code:

Tracing route to 199.91.189.31 over a maximum of 30 hops 6 te0-0-0-13.ccr21.sea02.atlas.cogentco.com [38.104.127.105] 7 be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198] 8 be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65] 9 be2129.mpd21.mci01.atlas.cogentco.com [154.54.26.114] 10 be2156.ccr21.ord01.atlas.cogentco.com [154.54.6.86] 11 be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42.10] 12 be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206] 13 38.122.42.34 14 192.34.76.10 15 199.91.189.242 16 199.91.189.31 Computing statistics for 400 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 6 30ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-13.ccr21.sea02.atlas.cogentco.com [38.104.127.105] 0/ 100 = 0% | 7 38ms 0/ 100 = 0% 0/ 100 = 0% be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198] 0/ 100 = 0% | 8 49ms 0/ 100 = 0% 0/ 100 = 0% be2126.ccr21.den01.atlas.cogentco.com [154.54.25.65] 0/ 100 = 0% | 9 61ms 0/ 100 = 0% 0/ 100 = 0% be2129.mpd21.mci01.atlas.cogentco.com [154.54.26.114] 0/ 100 = 0% | 10 73ms 0/ 100 = 0% 0/ 100 = 0% be2156.ccr21.ord01.atlas.cogentco.com [154.54.6.86] 0/ 100 = 0% | 11 86ms 0/ 100 = 0% 0/ 100 = 0% be2081.ccr21.yyz02.atlas.cogentco.com [154.54.42.10] 0/ 100 = 0% | 12 94ms 0/ 100 = 0% 0/ 100 = 0% be2090.ccr21.ymq02.atlas.cogentco.com [154.54.30.206] 0/ 100 = 0% | 13 94ms 0/ 100 = 0% 0/ 100 = 0% 38.122.42.34 0/ 100 = 0% | 14 97ms 0/ 100 = 0% 0/ 100 = 0% 192.34.76.10 0/ 100 = 0% | 15 95ms 0/ 100 = 0% 0/ 100 = 0% 199.91.189.242 0/ 100 = 0% | 16 94ms 0/ 100 = 0% 0/ 100 = 0% 199.91.189.31

I removed the first 5 hops since they're local to my ISP. Any numbers at 0% and 100% are likely okay. Anything other than that, either in the Source to Here or Link columns show a problem along the path. Of course, you'd want to do this when you're actually experiencing the problem (if it comes and goes) otherwise everything will look good even though it isn't always.

Format for running one = pathping ###.###.###.###

You can type > Drive:\filename.txt to copy it into a text file.

Quote:

Originally Posted by Asphe

I'm rather curious, you ended up with a longer path to s-e-m.com than to Leviathan?

yep... While they are both in Montreal, they are in different physical locations, hosted on different companies' lines, and so you may be passing through a significantly different route depending on how the analytics have mapped out the path for your ISP and/or their partners. Where you are coming from and where you are going to can be important factors at play here... and since those two endpoints are something like 15 miles apart, it can potentially be a significant difference for some people.