@fatman29
A variety of factors could be leading to the lag spikes happening in game. To start troubleshooting you can follow the instructions in the link posted below.
What do I do if I have bad latency in game on PC/Mac?
@fatman29
A variety of factors could be leading to the lag spikes happening in game. To start troubleshooting you can follow the instructions in the link posted below.
What do I do if I have bad latency in game on PC/Mac?
Ping statistics for 198.20.198.110: Packets: Sent = 100, Received = 94, Lost = 6 (6% loss), Approximate round trip times in milli-seconds: Minimum = 111ms, Maximum = 178ms, Average = 160ms Ping statistics for 198.20.198.110: Packets: Sent = 100, Received = 93, Lost = 7 (7% loss), Approximate round trip times in milli-seconds: Minimum = 103ms, Maximum = 180ms, Average = 160ms
Tracing route to 198.20.198.110 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.2.1 2 <1 ms <1 ms <1 ms 10.0.0.1 3 8 ms 7 ms 11 ms cm-1-acr03.greeley.co.denver.comcast.net [96.120 .12.105] 4 9 ms 23 ms 8 ms ae-253-1215-rur101.greeley.co.denver.comcast.net [96.110.194.141] 5 11 ms 11 ms 21 ms ae-34-ar01.denver.co.denver.comcast.net [68.86.1 03.93] 6 12 ms 14 ms 16 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121] 7 19 ms 17 ms 9 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94] 8 14 ms 11 ms 12 ms 173.167.58.162 9 43 ms 36 ms 35 ms if-ae-52-2.tcore2.sqn-san-jose.as6453.net [209.5 8.57.17] 10 40 ms 36 ms 36 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243 .205.1] 11 43 ms 53 ms 50 ms 63.243.205.62 12 50 ms 47 ms 48 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200. 184.194] 13 * * * Request timed out. 14 41 ms 43 ms 39 ms ae120.access-a.sech-sjc.netarch.akamai.com [209. 200.184.197] 15 164 ms 169 ms 161 ms a72-52-29-88.deploy.static.akamaitechnologies.co m [72.52.29.88] 16 * 169 ms 165 ms 198.20.192.4 17 166 ms 157 ms 179 ms 198.20.198.110 Trace complete. Tracing route to 198.20.198.110 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.2.1 2 <1 ms <1 ms <1 ms 10.0.0.1 3 9 ms 9 ms 8 ms cm-1-acr03.greeley.co.denver.comcast.net [96.120 .12.105] 4 15 ms 9 ms 10 ms ae-253-1215-rur101.greeley.co.denver.comcast.net [96.110.194.141] 5 18 ms 10 ms 10 ms ae-34-ar01.denver.co.denver.comcast.net [68.86.1 03.93] 6 19 ms 12 ms 10 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121] 7 19 ms 11 ms 11 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94] 8 11 ms 11 ms 12 ms 173.167.58.162 9 39 ms 36 ms 36 ms if-ae-52-2.tcore2.sqn-san-jose.as6453.net [209.5 8.57.17] 10 37 ms 36 ms 40 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243 .205.1] 11 47 ms 49 ms 47 ms 63.243.205.62 12 54 ms 53 ms 49 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200. 184.194] 13 * * * Request timed out. 14 46 ms 39 ms 37 ms ae120.access-a.sech-sjc.netarch.akamai.com [209. 200.184.197] 15 162 ms 167 ms 164 ms a72-52-29-88.deploy.static.akamaitechnologies.co m [72.52.29.88] 16 168 ms * 161 ms 198.20.192.4 17 159 ms 162 ms * 198.20.198.110 18 139 ms 165 ms 164 ms 198.20.198.110 Trace complete. Tracing route to 198.20.198.110 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.2.1 2 <1 ms <1 ms <1 ms 10.0.0.1 3 8 ms 7 ms 7 ms cm-1-acr03.greeley.co.denver.comcast.net [96.120 .12.105] 4 24 ms 9 ms 9 ms ae-253-1215-rur101.greeley.co.denver.comcast.net [96.110.194.141] 5 19 ms 12 ms 15 ms ae-34-ar01.denver.co.denver.comcast.net [68.86.1 03.93] 6 13 ms 12 ms 12 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121] 7 11 ms 10 ms 17 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94] 8 13 ms 10 ms 10 ms 173.167.58.162 9 36 ms 44 ms 39 ms if-ae-52-2.tcore2.sqn-san-jose.as6453.net [209.5 8.57.17] 10 37 ms 37 ms 35 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243 .205.1] 11 41 ms 39 ms 40 ms 63.243.205.62 12 43 ms 45 ms 49 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200. 184.194] 13 * * * Request timed out. 14 48 ms 40 ms 46 ms ae120.access-a.sech-sjc.netarch.akamai.com [209. 200.184.197] 15 163 ms * 166 ms a72-52-29-88.deploy.static.akamaitechnologies.co m [72.52.29.88] 16 166 ms 155 ms 159 ms 198.20.192.4 17 * 169 ms 154 ms 198.20.198.110 Trace complete. Tracing route to 198.20.198.110 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.2.1 2 1 ms 1 ms 1 ms 10.0.0.1 3 8 ms 9 ms 8 ms cm-1-acr03.greeley.co.denver.comcast.net [96.120 .12.105] 4 15 ms 10 ms 9 ms ae-253-1215-rur101.greeley.co.denver.comcast.net [96.110.194.141] 5 11 ms 23 ms 10 ms ae-34-ar01.denver.co.denver.comcast.net [68.86.1 03.93] 6 12 ms 14 ms 12 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121] 7 18 ms 11 ms 11 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94] 8 11 ms 10 ms 14 ms 173.167.58.162 9 37 ms 36 ms 37 ms if-ae-52-2.tcore2.sqn-san-jose.as6453.net [209.5 8.57.17] 10 36 ms 37 ms 37 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243 .205.1] 11 38 ms 39 ms 39 ms 63.243.205.62 12 41 ms 45 ms 46 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200. 184.194] 13 * * * Request timed out. 14 39 ms 37 ms 39 ms ae120.access-a.sech-sjc.netarch.akamai.com [209. 200.184.197] 15 152 ms 160 ms * a72-52-29-88.deploy.static.akamaitechnologies.co m [72.52.29.88] 16 157 ms * 162 ms 198.20.192.4 17 158 ms 164 ms 163 ms 198.20.198.110 Trace complete. Tracing route to 198.20.198.110 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.2.1 2 <1 ms <1 ms <1 ms 10.0.0.1 3 9 ms 9 ms 8 ms cm-1-acr03.greeley.co.denver.comcast.net [96.120 .12.105] 4 15 ms 8 ms 8 ms ae-253-1215-rur101.greeley.co.denver.comcast.net [96.110.194.141] 5 24 ms 15 ms 14 ms ae-34-ar01.denver.co.denver.comcast.net [68.86.1 03.93] 6 11 ms 10 ms 10 ms be-33652-cr02.1601milehigh.co.ibone.comcast.net [68.86.92.121] 7 11 ms 10 ms 11 ms be-12176-pe02.910fifteenth.co.ibone.comcast.net [68.86.83.94] 8 11 ms 11 ms 11 ms 173.167.58.162 9 35 ms 35 ms 36 ms if-ae-52-2.tcore2.sqn-san-jose.as6453.net [209.5 8.57.17] 10 35 ms 35 ms 37 ms if-ae-1-2.tcore1.sqn-san-jose.as6453.net [63.243 .205.1] 11 47 ms 45 ms 56 ms 63.243.205.62 12 39 ms 37 ms 36 ms po111.bs-a.sech-sjc.netarch.akamai.com [209.200. 184.194] 13 * * * Request timed out. 14 54 ms 38 ms 35 ms ae120.access-a.sech-sjc.netarch.akamai.com [209. 200.184.197] 15 * 134 ms 157 ms a72-52-29-88.deploy.static.akamaitechnologies.co m [72.52.29.88] 16 165 ms 161 ms 159 ms 198.20.192.4 17 161 ms 164 ms 161 ms 198.20.198.110 Trace complete.
HerrPulaRau wrote: »I'm pretty sure that they are not ill-intended. They have a lot of things to do and not enough time to do it. That is a general situation in the industry. They need to prioritize some tasks over the others, and more times than not, the devs are not the persons that do that (and that is again normal, is not their expertise). Also is really counter productive for a dev to be stopped from a task and moved to another (I know, I am one). So... I do not agree that they do not care. Most devs I know love their projects (the projects are like our babies, we created them from nothing, we raised them to maturity). I do think the project managers are either not aware of the issue, they don't think is bad enough, or they think that fixing will hurt profit somehow more than leaving it there (work man-hours, infrastructure, even maybe a timebomb somewhere in code).
So... what we should do is bump this issue higher in the priority list. We can only do this by showing how many of us are affected and how bad. I'm sure there are thousands of people affected, yet I only see a couple of posts per day. 10 posts are "our" problem, 10000 posts are "their" problem. So... post, whoever is affected by this problem leave a replay; is the only way to show our pain . Well... that and auto-metrics but auto-metrics can lie in this case.