1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Greetings Guest!!

    In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.

    Dismiss Notice

Extremely bad connection, unplayable lag

Discussion in 'Project Gorgon: Ask the Devs' started by picommander, Mar 1, 2014.

  1. picommander

    picommander Visitor

    Joined:
    Mar 1, 2014
    Messages:
    3
    Likes Received:
    0
    Hi guys,
    this is Rubinstein from in game and this is some kind of a cry for help. My connection quality to the game is so bad that for many hours it's just impossible to play. For several days now I'm trying to figure out the cause of the problem but after all logical conclusions and exclusions I'm pretty sure the cause is not on my site (I'm living in Germany btw). Assuming the server is at "projectgorgon.com" or at least using the same provider here's what I get from tracert when connection is really horrible: I don't post ping output here, it just shows some packet losses. The interesting stuff comes from tracert:

    Code:
    1    <1 ms    <1 ms    <1 ms  fritz.box [192.168.178.1]
      2    54 ms    26 ms    44 ms  rdsl-wprt-de01.nw.mediaways.net [213.20.58.3]
      3    53 ms    24 ms    58 ms  xmws-wprt-de02-chan-18.nw.mediaways.net [62.53.159.246]
      4    48 ms    25 ms   155 ms  rmwc-essn-de02-xe-0-0-2.nw.mediaways.net [62.53.2.140]
      5    47 ms    44 ms    72 ms  rmwc-dsdf-de02-xe-0-1-0-0.nw.mediaways.net [62.53.1.220]
      6    93 ms    54 ms    27 ms  rmwc-dsdf-de01-chan-6-0.nw.mediaways.net [62.53.1.92]
      7    33 ms    60 ms    80 ms  xmws-frnk-de17-chan-0-0.nw.mediaways.net [195.71.212.202]
      8    80 ms    31 ms    41 ms  30gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
      9    74 ms    78 ms    64 ms  100ge5-2.core1.par2.he.net [72.52.92.13]
    10   138 ms   120 ms   124 ms  10ge15-1.core1.ash1.he.net [184.105.213.93]
    11   141 ms   131 ms   142 ms  10ge12-7.core1.chi1.he.net [184.105.213.245]
    12   178 ms   177 ms   211 ms  10ge1-1.core1.mci1.he.net [72.52.92.2]
    13   180 ms   202 ms   180 ms  10ge1-1.core1.mci2.he.net [184.105.213.2]
    14     *      151 ms   151 ms  wholesale-internet-inc.10gigabitethernet1-3.core1.mci2.he.net [216.66.78.90]
    15   183 ms   149 ms   148 ms  lag-2.edge-a.clay1.mci.us.wholesaleinternet.net [69.30.209.238]
    16   180 ms   147 ms     *     lag-13.dist-1-3-a.clay1.mci.us.wholesaleinternet.net [69.30.235.5]
    17   178 ms   167 ms   146 ms  204.12.236.138 
    Problems start at hop 14 which seems to be the server company on which gorgon is running. I might be completely wrong and I'm aware of doing a lot of speculations here but please take it as a starting point *if* you want trying to help me out.

    p.s. it's not always that bad (when the ingame "ping-o-meter" shows ping times of ~2000) and I can play for several hours, but then I'm also cut off of the game for many hours. I'm also sure it's not a general oversea connection problem with my ISP since Gorgon is not the first game I'm playing on an us-server. It also doesn't happen on specific daytimes.

    Thanks a lot in advance.
     
  2. Luka Melehan

    Luka Melehan Certifiable
    Professional Stratics Veteran Alumni Campaign Patron

    Joined:
    May 12, 2008
    Messages:
    1,773
    Likes Received:
    271
    Citan will see things faster if you use the ingame bug report system, even if its to direct him to a post here.
     
  3. picommander

    picommander Visitor

    Joined:
    Mar 1, 2014
    Messages:
    3
    Likes Received:
    0
    I can do that but it should be clear that a conversation ingame is hardly possible when I'm under heavy lag. Talking about heavy lag is like typing a letter and waiting some minutes before I can see my own text (if at all). But meanwhile some other player told me that I'm not alone with this problem. Sooner or later I guess he needs to address this anyway.
     
  4. Luka Melehan

    Luka Melehan Certifiable
    Professional Stratics Veteran Alumni Campaign Patron

    Joined:
    May 12, 2008
    Messages:
    1,773
    Likes Received:
    271
    ok, i will shoot him an email then
     
  5. picommander

    picommander Visitor

    Joined:
    Mar 1, 2014
    Messages:
    3
    Likes Received:
    0
    Very kind, thank you. Meanwhile I pointed him to this forum post with the ingame report function, not sure if that went through. As an addition I did a lot of investigation to exclude the cause on my side, in particular if I have a general oversea connection problem. I found "some" other routes causing similar problems (packet loss, e.g. mmorpg.com => very bad, but only from ping results, common browsing isn't affected), but most us-servers work fine for me.

    For the sake of completeness here are some typical ping results at one of the worse lag times:

    Code:
    Antwort von 204.12.236.138: Bytes=32 Zeit=157ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=153ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=45
    Zeitberschreitung der Anforderung.
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=48
    Antwort von 204.12.236.138: Bytes=32 Zeit=156ms TTL=45
    Zeitberschreitung der Anforderung.
    Zeitberschreitung der Anforderung.
    Antwort von 204.12.236.138: Bytes=32 Zeit=154ms TTL=48
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=156ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=154ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=156ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=156ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=154ms TTL=48
    Antwort von 204.12.236.138: Bytes=32 Zeit=154ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=47
    Zeitberschreitung der Anforderung.
    Antwort von 204.12.236.138: Bytes=32 Zeit=156ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=154ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=153ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=153ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=46
    Zeitberschreitung der Anforderung.
    Zeitberschreitung der Anforderung.
    Zeitberschreitung der Anforderung.
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=45
    Antwort von 204.12.236.138: Bytes=32 Zeit=155ms TTL=46
    Antwort von 204.12.236.138: Bytes=32 Zeit=154ms TTL=47
    Antwort von 204.12.236.138: Bytes=32 Zeit=153ms TTL=48
    Zeitberschreitung der Anforderung.
    
    Ping-Statistik fr 204.12.236.138:
        Pakete: Gesendet = 40, Empfangen = 32, Verloren = 8
        (20% Verlust),
    Ca. Zeitangaben in Millisek.:
        Minimum = 153ms, Maximum = 157ms, Mittelwert = 154ms
    
    20% Packet loss here, and that's not the worst case (but already unplayable).
     
    #5 picommander, Mar 4, 2014
    Last edited: Mar 4, 2014