Page 2 of 30 FirstFirst 1 2 3 4 12 ... LastLast
Results 11 to 20 of 293

Thread: Packet loss 1/3/2016

  1. #11
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    Quote Originally Posted by murs View Post
    i'm also on rcn but i'm not on wifi i connect directly to the router which is plugged into the cable modem

    i'm wondering if one of the last updates updated the netcode for us east and the current data routing is poor for rcn customers
    Possibly. My roommate hasn't had any network issues like I have, and we use the same network card and such. However, he's been out of town for the last two weeks which is when I started having the packet loss problems. He just got back so I'll find out tonight if he has the same packet loss problems as I do. If he still doesn't, then I'm at a loss for why my PC specifically has this issue.

  2. #12
    I am playing on US-E and I am having a similar issue. I get 20 ping (fiber internet) but consistently lose packets, sometimes up to 50%. I tried a game on US-W and there was no loss at all. Very odd, but it's starting to get very annoying. Valve please help.

  3. #13
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    My roommate just tried to play a game and he had no packet loss. We are both on WiFi, and similar distances from the router (in fact, he's further away). Of course, we've both played for years without any issues and mine just recently started... so maybe after he's played a few games he'll start experiencing the same thing. But I'm getting the sense that it's not ISP related or something hardware related on our end.

  4. #14
    Basic Member
    Join Date
    Jan 2016
    Posts
    1
    50-80% packet loss today. Really need some help

  5. #15
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    Quote Originally Posted by ChikenMC View Post
    50-80% packet loss today. Really need some help
    You're ruining my daydream of leaving work, going home, and dota having magically fixed itself, man.

  6. #16
    Basic Member
    Join Date
    Jan 2016
    Posts
    1
    I have same problem here.
    Its not a ISP problem....

  7. #17
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    I played last night and had no packet loss whatsoever for the first time in weeks. My roommate, however, had the consistent 20%+ packet loss for the first time. We were in the same game, on the same WiFi, etc.

  8. #18
    Basic Member
    Join Date
    Jan 2013
    Posts
    8
    I have the same issue. Time to play on USWest I guess.

  9. #19
    Same, wired, 20 ping, 30-70% packet loss, console displays:

    Requesting session from iad#132 (162.254.192.73:27038). Ping = 38+0=38 (front+back=total).
    Switched to iad#132 (162.254.192.73:27038) as primary, session 1b291594. Ping = 38+0=38 (front+back=total). [Previous primary atl#16 (162.254.199.170:27030): Ping = 43+13=56 (front+back=total).]
    Selecting atl#16 (162.254.199.170:27030) as backup #1, session 22303efa. Ping = 43+13=56 (front+back=total).
    Telling Steam not to update the app for the next 900 seconds
    client =[][0]: high packet loss detected flow incoming: 0ms latency, 19/ 302 dropped (6.3%)
    client =[][0]: split packet seq #31 restarting, just received packet 0
    client =[][0]: high packet loss detected flow incoming: 0ms latency, 18/ 304 dropped (5.9%)
    client =[][0]: high packet loss detected flow incoming: 0ms latency, 23/ 307 dropped (7.5%)
    client =[][0]: high packet loss detected flow incoming: 0ms latency, 24/ 307 dropped (7.8%)
    Discarding inactive session on ord#67 (162.254.193.71:27045). session_inactivity_timeout
    Telling Steam not to update the app for the next 900 seconds
    client =[A:1:226319368:6253][0]: high packet loss detected flow incoming: 0ms latency, 21/ 307 dropped (6.8%)
    etc

  10. #20
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    Some samples from console as well:

    Code:
    Network socket 'client' opened on port -1
    CL:  CNetworkGameClient::OnSwitchLoopModeFinished( remoteconnect : success )
    CAsyncWriteInProgress::OnComplete( "scripts/control_groups.txt" ) -> Success at 680.091
    CAsyncWriteInProgress::OnComplete( "voice_ban.dt" ) -> Success at 680.091
    CL:  Sending connect to =[A:1:824347656:6253]
    Attempting connection to service in data center 'iad'
    Requesting session from iad#89 (162.254.192.72:27031).  Ping = 10+0=10 (front+back=total).
    Selected iad#89 (162.254.192.72:27031) as primary, session 01da3a5a.  [Ping = 10+0=10 (front+back=total).]
    Requesting session from atl#4 (162.254.199.170:27018).  Ping = 22+13=35 (front+back=total).
    Selecting atl#4 (162.254.199.170:27018) as backup #1, session 2ba5a7a4.  Ping = 22+13=35 (front+back=total).
    Code:
    client =[A:1:401025027:6253][0]:  split packet seq #252 restarting, just received packet 0
          client =[A:1:401025027:6253][0]:  split packet seq #253 restarting, just received packet 1, split packet payload will probably be dropped
          client =[A:1:401025027:6253][0]:  split packet seq #254 restarting, just received packet 1, split packet payload will probably be dropped
          client =[A:1:401025027:6253][0]:  split packet seq #256 restarting, just received packet 2, split packet payload will probably be dropped
          client =[A:1:401025027:6253][0]:  split packet seq #257 restarting, just received packet 1, split packet payload will probably be dropped
          client =[A:1:401025027:6253][0]:  split packet seq #258 restarting, just received packet 0
          client =[A:1:401025027:6253][0]:  split packet seq #259 restarting, just received packet 7
          client =[A:1:401025027:6253][0]:  high packet loss detected flow incoming:    0ms latency,   200/  241 dropped (83.0%)
    CL:  Receiving uncompressed update from server
          client =[A:1:401025027:6253][0]:  high packet loss detected flow incoming:    0ms latency,    44/  304 dropped (14.5%)
    Code:
    ChangeGameUIState: DOTA_GAME_UI_DOTA_INGAME -> DOTA_GAME_UI_DOTA_INGAME
    ChangeGameUIState: DOTA_GAME_UI_DOTA_INGAME -> DOTA_GAME_UI_DOTA_INGAME
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    60/  187 dropped (32.1%)
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    49/  303 dropped (16.2%)
    Telling Steam not to update the app for the next 900 seconds
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    68/  304 dropped (22.4%)
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    63/  305 dropped (20.7%)
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    53/  303 dropped (17.5%)
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    67/  304 dropped (22.0%)
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    66/  307 dropped (21.5%)
          client =[A:1:824347656:6253][0]:  high packet loss detected flow incoming:    0ms latency,    59/  305 dropped (19.3%)
    If I ping the server is says I'm connected to:

    Code:
    Ping statistics for 162.254.199.170:
    Packets: Sent = 119, Received = 119, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 35ms, Average = 24ms
    And a traceroute for good measure:

    Code:
    C:\Users\...>tracert 162.254.199.170
    Tracing route to 162-254-199-170.valve.net [162.254.199.170] over a maximum of 30 hops:
    1    <1 ms    <1 ms    <1 ms  10.0.0.1                                                                                  
    2     *        *        *     Request timed out.                                                                        
    3    12 ms     9 ms    11 ms  bvi7.aggr1.lnh.md.rcn.net [208.59.202.194]                                                
    4    13 ms     9 ms    13 ms  tge0-1-0-0.core1.lnh.md.rcn.net [207.172.15.18]                                           
    5    10 ms    10 ms    15 ms  hge0-3-0-0.border1.eqnx.va.rcn.net [207.172.19.86]                                       
    6    11 ms    11 ms    12 ms  eqix-dc5.highwinds.1.com [206.126.237.129]                                                
    7    15 ms    10 ms    11 ms  209.197.13.10                                                                             
    8    23 ms    22 ms    23 ms  209.197.26.9                                                                              
    9    22 ms    23 ms    24 ms  162-254-199-170.valve.net [162.254.199.170]                                                                                                                                                                     
    
    Trace complete.
    You notice it says we're connecting to data center "iad", which is Dulles. I was thinking maybe it had something to do with US East, but I get the exact same issue on US West. Really just want to be able to play some dota after work...
    Last edited by zerot_; 01-06-2016 at 07:09 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •