Page 1 of 30 1 2 3 11 ... LastLast
Results 1 to 10 of 293

Thread: Packet loss 1/3/2016

  1. #1
    Basic Member
    Join Date
    Nov 2011
    Posts
    46

    Packet loss 1/3/2016

    Hey Valve -

    I've been having roughly 10-30% packet loss everygame since 2-3 days ago.
    I've tested with ping/tracert and it doesn't happen with anything else besides dota 2.
    Has anyone else rann into this problem or have any fixes they can share?


    client 208.78.164.66:28106[0]: split packet seq #422 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #424 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #425 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #428 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #430 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #431 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #432 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #434 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #435 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #436 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #443 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: high packet loss detected flow incoming: 0ms latency, 30/ 150 dropped (20.0%)
    client 208.78.164.66:28106[0]: split packet seq #445 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #449 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #452 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #453 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #455 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #456 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #457 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #459 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #461 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #462 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #464 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #470 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #472 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #473 restarting, just received packet 0
    client 208.78.164.66:28106[0]: high packet loss detected flow incoming: 0ms latency, 34/ 152 dropped (22.4%)
    client 208.78.164.66:28106[0]: split packet seq #476 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #477 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #478 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #479 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #480 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #481 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #485 restarting, just received packet 2, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #486 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #487 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #495 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #502 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #504 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #505 restarting, just received packet 0
    client 208.78.164.66:28106[0]: high packet loss detected flow incoming: 0ms latency, 32/ 154 dropped (20.8%)
    client 208.78.164.66:28106[0]: split packet seq #514 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #519 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #520 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #526 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #530 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #531 restarting, just received packet 1, split packet payload will probably be dropped
    client 208.78.164.66:28106[0]: split packet seq #532 restarting, just received packet 0
    client 208.78.164.66:28106[0]: split packet seq #536 restarting, just received packet 0
    client 208.78.164.66:28106[0]: high packet loss detected flow incoming: 0ms latency, 30/ 151 dropped (19.9%)

    Would be nice to continue to play the game i've invested a lot of time and money in.
    It's a shame valve doesn't have an actual support team....

  2. #2
    The exact same thing happened to me, but I'd like to add that when i manually ping iad.valve.net, it shows that i'm not losing any packets.

    Completely bizarre.. I don't know what to do to fix it

    See this picture:

    http://i.imgur.com/f5wZos2.jpg

  3. #3
    Exact same problem here!

  4. #4
    Basic Member
    Join Date
    Nov 2011
    Posts
    46
    i also don't have any packet loss to iad.valve.net when i put in
    ping iad.valve.net -t and let it run for a bit

    by any chance are the other 2 of you northeastern pa?

  5. #5
    Basic Member
    Join Date
    Nov 2011
    Posts
    46
    now i'm up to 50% packet loss today

    can anyone help

    i've already tried calling my isp and nothing appears to be wrong

    no issues in anything else besides dota

  6. #6
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    Exact same problem here. Identical console output to what sodiumgenerator posted above. It's been getting progressively worse, too. I started out just having my game freeze a couple times per game a month or two ago. Then a week or two ago, I started having consistent 1-5% packet loss in all my games. Then the next week, consistent 10-15% packet loss. And now, today, as I write this post after playing a match at consistent 20%+ with spikes over 65% and disconnect warnings appearing, I'm wondering what the hell is going on. I suppose it's nice to hear that it's happening to other people too, since I've reinstalled a fresh copy of Windows, reinstalled Dota multiple times, moved my router, replaced my wireless card, and probably greyed about 80% of the hair on my head trying to play like this.

    My console log as the game was ending...
    client =[A:1:3548666886:6245[0]: high packet loss detected flow incoming: 0ms latency, 206/ 211 dropped (97.6%)

    The fuck is this.

    Edit: I'm in Washington DC, playing on US East.
    Last edited by zerot_; 01-04-2016 at 07:05 PM.

  7. #7
    Basic Member
    Join Date
    Feb 2012
    Posts
    188
    Same problem:

    get: "split packet...packet will be dropped" in console
    also get: "high packet loss flow incoming" in console

  8. #8
    Basic Member
    Join Date
    Nov 2011
    Posts
    46
    Quote Originally Posted by zerot_ View Post
    Exact same problem here. Identical console output to what sodiumgenerator posted above. It's been getting progressively worse, too. I started out just having my game freeze a couple times per game a month or two ago. Then a week or two ago, I started having consistent 1-5% packet loss in all my games. Then the next week, consistent 10-15% packet loss. And now, today, as I write this post after playing a match at consistent 20%+ with spikes over 65% and disconnect warnings appearing, I'm wondering what the hell is going on. I suppose it's nice to hear that it's happening to other people too, since I've reinstalled a fresh copy of Windows, reinstalled Dota multiple times, moved my router, replaced my wireless card, and probably greyed about 80% of the hair on my head trying to play like this.

    My console log as the game was ending...
    client =[A:1:3548666886:6245[0]: high packet loss detected flow incoming: 0ms latency, 206/ 211 dropped (97.6%)

    The fuck is this.

    Edit: I'm in Washington DC, playing on US East.
    do you use RCN?

  9. #9
    Basic Member
    Join Date
    Jan 2016
    Posts
    12
    Quote Originally Posted by murs View Post
    do you use RCN?
    Yes, I'm on RCN. I'm also using WiFi, but a speedtest shows me getting 170+ down and 15+ up. Pinging my router for a few minutes shows no packet loss. Pinging the game server I'm connected to for a few minutes shows no packet loss. Quite frustrating. I've been playing for years and never had an issue like this. Nothing about my setup has changed.

  10. #10
    Basic Member
    Join Date
    Nov 2011
    Posts
    46
    Quote Originally Posted by zerot_ View Post
    Yes, I'm on RCN. I'm also using WiFi, but a speedtest shows me getting 170+ down and 15+ up. Pinging my router for a few minutes shows no packet loss. Pinging the game server I'm connected to for a few minutes shows no packet loss. Quite frustrating. I've been playing for years and never had an issue like this. Nothing about my setup has changed.
    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

Posting Permissions

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