test content
Logo
What is the Arc Client?
Install Arc
Options
Lag/Rubberbanding with possible root cause
xaviermace86
Member Posts: 64 Arc User
I know there's multiple threads but I don't see any with the info you guys have always requested, so info is at the bottom of the post. To assist, I have results with no proxy, west coast proxy, and east coast proxy to give you 3 separate routes. That said I believe I may have found the issue, details on that below. I apologize to the people's STF's I may have ruined testing this.
However, I will state running /netgraph 1 ingame shows different results than the external tests below. Sitting on ESD, I get a ping time of no lower than 200ms with occasional spikes up to 1000-2000ms. That said, that means occasional rubber banding but not unplayable. Sitting on ESD playing Surface Tension (meaning Single Player) I get comparatively stable 90-120ms response times and no spikes.
STF's seemed to be far far worse, with server not responding messages just about constantly, netgraph stops responding for several seconds, shows a spike to 1000ms+ then stops responding again. But chat is completely un-effected by it. The STF can basically be completely stopped but all the players are sitting there chatting that it's not working. As with the other reports, this just started in the last couple of days. It was functioning flawlessly prior to that.
Then I realized something. This literally just started occurring when I unlocked the Reactive Repair Nanites trait from the Sarr Theln. This afternoon I played 4 STF's (2x Borg Disconnected Normal, 2x Battle of Kortez). As soon as launch my Advanced Plesh Brek Frigates and Reactive Repair kicks in, server stops responding. Dock the fighters (which takes forever due to the lag and sometimes doesn't work at all) and the lag stops as soon as they dock.
I again confirmed via chat that in every occurrence this affects everyone in the instance. Disabled the trait, played another Borg Disconnected, no issues, finished the mission. Enabled the trait, joined a Crystalline Entity but didn't launch any fighters. Works fine. Launched fighters, instant lag just like the other STF's. Again confirmed with the team that it was affecting everyone. Just to rule out the STF's as a common point, I joined a random Klingon Encounter near Sol. Same issue. Launch fighters, as soon as the nanites kick in, instant lag. To further narrow down the issue, I switched to Elite Scorpions. Issue did not seem to occur with them. However the enemies were dying too quick for the nanites to kick in I believe. I will have to test that further to be sure.
Now for the promised network tests/info.
ISP: Cox Cable (Ultimate). Speedtest is currently clocking at 170/60mbps.
No Proxy, connecting from Phoenix, AZ:
Proxy'd through Los Angeles, CA
Proxy'd through New York City, NY
Let me know if there's any other info I can provide as the game is largely unplayable right now.
However, I will state running /netgraph 1 ingame shows different results than the external tests below. Sitting on ESD, I get a ping time of no lower than 200ms with occasional spikes up to 1000-2000ms. That said, that means occasional rubber banding but not unplayable. Sitting on ESD playing Surface Tension (meaning Single Player) I get comparatively stable 90-120ms response times and no spikes.
STF's seemed to be far far worse, with server not responding messages just about constantly, netgraph stops responding for several seconds, shows a spike to 1000ms+ then stops responding again. But chat is completely un-effected by it. The STF can basically be completely stopped but all the players are sitting there chatting that it's not working. As with the other reports, this just started in the last couple of days. It was functioning flawlessly prior to that.
Then I realized something. This literally just started occurring when I unlocked the Reactive Repair Nanites trait from the Sarr Theln. This afternoon I played 4 STF's (2x Borg Disconnected Normal, 2x Battle of Kortez). As soon as launch my Advanced Plesh Brek Frigates and Reactive Repair kicks in, server stops responding. Dock the fighters (which takes forever due to the lag and sometimes doesn't work at all) and the lag stops as soon as they dock.
I again confirmed via chat that in every occurrence this affects everyone in the instance. Disabled the trait, played another Borg Disconnected, no issues, finished the mission. Enabled the trait, joined a Crystalline Entity but didn't launch any fighters. Works fine. Launched fighters, instant lag just like the other STF's. Again confirmed with the team that it was affecting everyone. Just to rule out the STF's as a common point, I joined a random Klingon Encounter near Sol. Same issue. Launch fighters, as soon as the nanites kick in, instant lag. To further narrow down the issue, I switched to Elite Scorpions. Issue did not seem to occur with them. However the enemies were dying too quick for the nanites to kick in I believe. I will have to test that further to be sure.
Now for the promised network tests/info.
ISP: Cox Cable (Ultimate). Speedtest is currently clocking at 170/60mbps.
No Proxy, connecting from Phoenix, AZ:
contacting nettest server..
Ping: 90.9 msec
Port: 80: 555 KB/sec 15 KB/sec 591 KB/sec 500
Port: 80: 530 KB/sec 16 KB/sec 560 KB/sec 500
Port: 443: 535 KB/sec 13 KB/sec 562 KB/sec 500
Port: 443: 569 KB/sec 17 KB/sec 600 KB/sec 500
Port: 7255: 484 KB/sec 10 KB/sec 510 KB/sec 500
Port: 7255: 513 KB/sec 9 KB/sec 539 KB/sec 500
Port: 7003: 586 KB/sec 17 KB/sec 620 KB/sec 500
Port: 7003: 555 KB/sec 12 KB/sec 592 KB/sec 500
Port: 7202: 524 KB/sec 10 KB/sec 554 KB/sec 500
Port: 7202: 573 KB/sec 13 KB/sec 603 KB/sec 500
Port: 7499: 579 KB/sec 11 KB/sec 609 KB/sec 500
Port: 7499: 531 KB/sec 16 KB/sec 564 KB/sec 500
Port: 80: 615 KB/sec 16 KB/sec 647 KB/sec 500
Idle NIC bandwidth Send: 2 KB/sec Recv: 3 KB/sec
hit return to exit
C:\WINDOWS\System32>tracert patchserver.crypticstudios.com
1 <1 ms <1 ms <1 ms 192.168.3.1
2 9 ms 7 ms 7 ms 10.49.80.1
3 10 ms 8 ms 9 ms 172.21.0.156
4 10 ms 14 ms 11 ms 70.169.77.248
5 35 ms 20 ms 28 ms 72.215.229.61
6 27 ms 37 ms 44 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
7 24 ms 27 ms 22 ms 68.105.30.150
8 33 ms 28 ms 27 ms ae10.cr1.lax112.us.zip.zayo.com [64.125.26.6]
9 52 ms 81 ms 51 ms ae2.cr1.iah1.us.zip.zayo.com [64.125.20.209]
10 77 ms 92 ms 77 ms ae8.cr1.dca2.us.zip.zayo.com [64.125.20.185]
11 88 ms 88 ms 81 ms ae5.cr1.lga5.us.zip.zayo.com [64.125.26.98]
12 106 ms 96 ms 96 ms ae7.mpr3.bos2.us.zip.zayo.com [64.125.21.225]
13 91 ms 100 ms 92 ms 208.184.110.70.ipyx-072053-002-zyo.above.net [208.184.110.70]
14 91 ms 92 ms 88 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]
15 115 ms 107 ms 107 ms perfectworldent-4.border11.bsn.pnap.net [216.52.61.78]
16 108 ms 107 ms 107 ms 208.95.185.225
17 95 ms 122 ms 96 ms xboxpatchserver.crypticstudios.com [208.95.185.41]
Proxy'd through Los Angeles, CA
contacting nettest server..
Ping: 90.9 msec
Port: 80: 744 KB/sec 48 KB/sec 842 KB/sec 500
Port: 80: 715 KB/sec 44 KB/sec 819 KB/sec 500
Port: 443: 805 KB/sec 48 KB/sec 907 KB/sec 500
Port: 443: 702 KB/sec 46 KB/sec 796 KB/sec 500
Port: 7255: 593 KB/sec 35 KB/sec 669 KB/sec 500
Port: 7255: 549 KB/sec 35 KB/sec 622 KB/sec 500
Port: 7003: 689 KB/sec 42 KB/sec 778 KB/sec 500
Port: 7003: 682 KB/sec 43 KB/sec 774 KB/sec 500
Port: 7202: 543 KB/sec 35 KB/sec 615 KB/sec 500
Port: 7202: 480 KB/sec 31 KB/sec 544 KB/sec 500
Port: 7499: 187 KB/sec 16 KB/sec 214 KB/sec 500
Port: 7499: 76 KB/sec 7 KB/sec 89 KB/sec 500
Port: 80: 691 KB/sec 44 KB/sec 787 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 5 KB/sec
C:\WINDOWS\System32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 20 ms 21 ms 20 ms 10.120.146.1
2 27 ms 28 ms 24 ms 198.24.140.57
3 21 ms 20 ms 21 ms eth15-2.bb2.phx0.0.170.108.in-addr.arpa [108.170
.0.38]
4 23 ms 21 ms 33 ms te0-0-1-0.nr11.b023003-0.phx02.atlas.cogentco.co
m [38.88.34.37]
5 21 ms 24 ms 23 ms 154.24.18.205
6 24 ms 22 ms 21 ms be2125.ccr22.phx02.atlas.cogentco.com [154.54.1.
101]
7 28 ms 29 ms 29 ms be2414.ccr21.elp01.atlas.cogentco.com [154.54.42
.106]
8 40 ms 42 ms 48 ms be2301.ccr21.sat01.atlas.cogentco.com [154.54.5.
173]
9 47 ms 49 ms 49 ms be2292.ccr22.iah01.atlas.cogentco.com [154.54.1.
81]
10 77 ms 90 ms 76 ms be2173.ccr42.atl01.atlas.cogentco.com [154.54.29
.117]
11 78 ms 76 ms 83 ms be2171.mpd22.dca01.atlas.cogentco.com [154.54.31
.110]
12 89 ms 82 ms 84 ms be2151.ccr42.jfk02.atlas.cogentco.com [154.54.40
.74]
13 88 ms 88 ms 88 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
14 101 ms 99 ms 88 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
15 92 ms 91 ms 105 ms 38.111.40.114
16 87 ms 89 ms 88 ms xboxpatchserver.crypticstudios.com [208.95.185.4
1]
Proxy'd through New York City, NY
contacting nettest server..
Ping: 83.3 msec
Port: 80: 765 KB/sec 48 KB/sec 866 KB/sec 500
Port: 80: 761 KB/sec 47 KB/sec 861 KB/sec 500
Port: 443: 736 KB/sec 45 KB/sec 830 KB/sec 500
Port: 443: 754 KB/sec 47 KB/sec 858 KB/sec 500
Port: 7255: 624 KB/sec 37 KB/sec 703 KB/sec 500
Port: 7255: 572 KB/sec 37 KB/sec 650 KB/sec 500
Port: 7003: 754 KB/sec 45 KB/sec 852 KB/sec 500
Port: 7003: 801 KB/sec 51 KB/sec 908 KB/sec 500
Port: 7202: 607 KB/sec 36 KB/sec 684 KB/sec 500
Port: 7202: 353 KB/sec 24 KB/sec 400 KB/sec 500
Port: 7499: 615 KB/sec 39 KB/sec 697 KB/sec 500
Port: 7499: 422 KB/sec 42 KB/sec 512 KB/sec 500
Port: 80: 804 KB/sec 48 KB/sec 912 KB/sec 500
Idle NIC bandwidth Send: 0 KB/sec Recv: 1 KB/sec
hit return to exit
C:\WINDOWS\System32>tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 76 ms 75 ms 74 ms 10.156.1.1
2 83 ms 75 ms 82 ms vl231-c6-14-c6-1.pnj1.choopa.net [209.222.18.9]
3 80 ms 83 ms 79 ms ethernet12-5-br2.pnj1.choopa.net [108.61.93.33]
4 77 ms 80 ms 77 ms ae-33.r05.nycmny01.us.bb.gin.ntt.net [128.241.2.
201]
5 76 ms 75 ms 78 ms ae-3.r06.nycmny01.us.bb.gin.ntt.net [129.250.4.2
05]
6 76 ms 77 ms 83 ms be3037.ccr21.jfk10.atlas.cogentco.com [154.54.12
.145]
7 77 ms 85 ms 76 ms be2057.ccr42.jfk02.atlas.cogentco.com [154.54.80
.177]
8 82 ms 94 ms 87 ms be2096.ccr22.bos01.atlas.cogentco.com [154.54.30
.42]
9 83 ms 82 ms 81 ms te3-2.ccr01.bos06.atlas.cogentco.com [154.54.46.
130]
10 97 ms 91 ms 87 ms 38.111.40.114
11 96 ms 84 ms 88 ms xboxpatchserver.crypticstudios.com [208.95.185.4
1]
Let me know if there's any other info I can provide as the game is largely unplayable right now.
Post edited by xaviermace86 on
0
Comments
But of course, that has nothing to do with a trait or pings does it?
Actually, you omitted the most important test, as only 'Path Ping' checks for lost or thrown away data packets on your connection through the Internet...
Packet loss is not the problem.
'Ping' is not a substitute for the 'Path Ping' diagnostics. The 'Net Test' diagnostics posted show that you can't maintain a consistent sustained network throughput bandwidth to the 'Net Test' diagnostic server (not the STO servers, which are out of the picture for the 'Net Test' diagnostic results..) so packet loss is suspect for your connection quality issue. 'Ping' is simply too simplistic a test to detect this...
nettest is testing connection from my client to a system on their network over a variety of ports. All it shows is performance between those two points, it does not show where the problem occurs. You turn their server off, and the tool will show 0KB/s transfer speed.
Every single one of the trace routes show the connection is reaching their side just fine. Ping shows no packet loss or latency spikes. I can do a speed test to a variety of servers in the San Francisco area (patchserver is in San Jose) and get a constant 50/15mbps or better connection which is more than enough for STO and with half the latency I get hitting their servers on the above tests (which is already half of what I see in game).
Again, no packet loss and half the latency I see in game. But this is standard ICMP traffic with the default packet size (32 Bytes). So, lets try bigger packets. Here's using 1KB packets:
Again no packet loss. Not to mention:
So far all these tests are "ideal" bordering on "outstanding". I can also tell you that I've played STO tethered off a 4G connection numerous times without issue.
Again, there's zero indication of packet loss and every test shows I'm reaching their servers without issue. In addition, I can stream HD video at 3Mbps from my house to the office with zero issue as well. That's 3-6 times the bandwidth they are looking for in their tests.
You're also ignoring the fact that this isn't just simple latency. It's bringing STF's to a halt for the entire team. No amount of latency on my connection would explain that.
So the only thing to do is not use the trait? Or not launch fighters? What is the point of all that work in Delta then?