Increased ping for >specific< players.

Omega_K2Omega_K2 Join Date: 2011-12-25 Member: 139013Members, Reinforced - Shadow Posts: 558
edited January 2014 in Server Discussion
I don't know whether this is an pure server issue or client issue (or a combinaton of both), but for some unknown stupid reason NS2 sometimes increases your ping to a specific server.

It's not very consistent, but in either case it's a bug. Ping sometimes is higher then usual, and it becomes normal again as you restart NS2 (most of the time). Note that in such cases other servers do not seem to be affect.

So basically: same machine, same server, ping sometimes is 150ms, then you restart NS2, and it's 50 ms again. In terms of real ping outside of game it's the same *always*, so it's definetly a problem with NS2.

What's even better is that you can run 2 instances of the game on the same computer, and get two different pings (150ms + 50ms) at the same time.
German Slaughterhouse | GS Servers | Server Hardware
IGN: [#OMEGA] - K2 (Hive)

NS2 long standing issues (Fix ETA: Never):
Bad Netcode (no adjustable tickrate, extremly delayed hit feedback, bad hitreg),
Bad Performance (Poor Multi-threading, Mouse Lag, bad server performance, almost no multi-threading in server application)
Bad Balance (GL Spam, semi-useless exos, poor chance of comebacks, no upkeep/or RT dimishing returns...)
Technical Issues (Mouse Lag, Memory Leaks, Memory Corruption (and memory corruption server crashes))
Bad Workshop implementation (down = kicks people/connection prboelms, out of date = nobody can join server),

Comments

  • evilmaniacevilmaniac United States Join Date: 2013-12-20 Member: 190361Members, Reinforced - Shadow Posts: 6 Fully active user
    Out of curiosity is this on the Linux or Windows client, or both ?
  • Omega_K2Omega_K2 Join Date: 2011-12-25 Member: 139013Members, Reinforced - Shadow Posts: 558
    Win client, linux server
    German Slaughterhouse | GS Servers | Server Hardware
    IGN: [#OMEGA] - K2 (Hive)

    NS2 long standing issues (Fix ETA: Never):
    Bad Netcode (no adjustable tickrate, extremly delayed hit feedback, bad hitreg),
    Bad Performance (Poor Multi-threading, Mouse Lag, bad server performance, almost no multi-threading in server application)
    Bad Balance (GL Spam, semi-useless exos, poor chance of comebacks, no upkeep/or RT dimishing returns...)
    Technical Issues (Mouse Lag, Memory Leaks, Memory Corruption (and memory corruption server crashes))
    Bad Workshop implementation (down = kicks people/connection prboelms, out of date = nobody can join server),
  • ZEROibisZEROibis Join Date: 2009-10-30 Member: 69176Members, Constellation Posts: 1,017 Advanced user
    Run trace routes at the same time to establish that the actual packet time or route is not changing when this is occurring.
    image
    Server IP: NS2.IBISGaming.com
    Server IP: NS2CO.IBISGaming.com
    wopwop
  • Omega_K2Omega_K2 Join Date: 2011-12-25 Member: 139013Members, Reinforced - Shadow Posts: 558
    ZEROibis wrote: »
    Run trace routes at the same time to establish that the actual packet time or route is not changing when this is occurring.

    Ehrm, read my post again. If you run two instances at the SAME TIME, the ping will be different. Also pretty much anything BUT one instance of ns2 has the normal ping value.
    Same route, real ping is about the same: aka the problem lies within NS2.
    German Slaughterhouse | GS Servers | Server Hardware
    IGN: [#OMEGA] - K2 (Hive)

    NS2 long standing issues (Fix ETA: Never):
    Bad Netcode (no adjustable tickrate, extremly delayed hit feedback, bad hitreg),
    Bad Performance (Poor Multi-threading, Mouse Lag, bad server performance, almost no multi-threading in server application)
    Bad Balance (GL Spam, semi-useless exos, poor chance of comebacks, no upkeep/or RT dimishing returns...)
    Technical Issues (Mouse Lag, Memory Leaks, Memory Corruption (and memory corruption server crashes))
    Bad Workshop implementation (down = kicks people/connection prboelms, out of date = nobody can join server),
Sign In or Register to comment.