Announcement

Collapse
No announcement yet.

Ping in server Browser

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Okay, well all I'm saying is if you're not changing the provider itself that you use, but just the package, I doubt you will see a significant difference. Mark my words.. but it doesn't mean you won't see benefits.. maps will download faster obviously.

    Comment


      #17
      Your ping is a little bandwidth dependant, per example:
      by Default the ping command line of Windows uses packets of 32bytes, however if you were to use larger packets (-l packetsize) you can get higher pings because bandwidth restriction migh see the packets broken up to transmit them

      Comment


        #18
        As a quick test I pinged my router:
        Code:
        c:\> ping 192.168.0.1
        
        Pinging 192.168.0.1 with 32 bytes of data:
        
        Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
        Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
        Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
        Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
        Reply from 192.168.0.1: bytes=32 time<1ms TTL=127
        
        Ping statistics for 192.168.0.1:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
            Minimum = 0ms, Maximum = 0ms, Average = 0ms
        
        c:\>ping 192.168.0.1 -l 8000
        
        
        Pinging 192.168.0.1 with 8000 bytes of data:
        
        Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
        Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
        Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
        Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
        Reply from 192.168.0.1: bytes=32 time=3ms TTL=127
        
        Ping statistics for 192.168.0.1:
            Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
        Approximate round trip times in milli-seconds:
            Minimum = 3ms, Maximum = 3ms, Average = 3ms
        And that's over a 100MB/Sec Ethernet cable about 3 feet long.

        Comment


          #19
          I guess I'm in really good shape with my router at least then, the cable that runs to it is probably closer to 12 feet long, and my ping was a steady 1 ms

          Comment


            #20
            Originally posted by Blaaguuu View Post
            ... but i can understand many casual gamers being confused...
            Sorry to say this, but I can't. I remember well how I started playing online gaming:

            "I don't know what this ping thing is, but this server has a lot of it so it must be good."

            The very same evening (after "joining" about 2 or 3 of those server-thingies), I learned that it was the exact opposite.
            Within 2 days I started to grasp the concept of what it was and why it could never be 0...

            Saying that casual gamers will be confused by something as simple as "the lower the number, the better your connection" is IMO an insult to their intelligence.

            I'm all for simplicity in things, but there are limits to things. If Microsoft is really starting to dumb down on essentials, things won't look good for the future. It'll breed people like these people.

            Comment


              #21
              +1 color coded ping, just like color coded fps.

              Comment

              Working...
              X