Jump to content

General Question


Donnie-Dunn

Recommended Posts

I live in Ironton Missouri. I live just a little bit out of the good Internet range, so at best I get just a bit over 500kb. (Terrible I know) I love to play advanced warfare. Sometimes I have great games for example I had one game just recently where I went 50 kills n 12 deaths just great by my standards. But most of the time I go like 10 n 20. Could this have something to do with the closer host or I just happen to find people who are worse than me? As I said before my Internet sucks, not to mention at any given time I have my PS4, 3 galaxy S5 phones, and 2 Ipads running Facebook or something else that slows down my net. My main question is: Would this help me out or would I just be wasting my money? I thank you for your time.

Link to comment
Share on other sites

I live in Ironton Missouri. I live just a little bit out of the good Internet range, so at best I get just a bit over 500kb. (Terrible I know) I love to play advanced warfare. Sometimes I have great games for example I had one game just recently where I went 50 kills n 12 deaths just great by my standards. But most of the time I go like 10 n 20. Could this have something to do with the closer host or I just happen to find people who are worse than me? As I said before my Internet sucks, not to mention at any given time I have my PS4, 3 galaxy S5 phones, and 2 Ipads running Facebook or something else that slows down my net. My main question is: Would this help me out or would I just be wasting my money? I thank you for your time.

That's not horrible internet for joining a game...my guess though, sadly when you did that well you were likely the HOST and everyone was cursing about lag.

Link to comment
Share on other sites

Makes sense. I always thought it picked a host based on the best connection. As bad as it sounds I wish it would happen all the time. I like playing that good lol.

Yeah, there is no telling obviously without recorded network usage.

 

But no "best connection" is a very loose way of saying what AW does to pick host.

Link to comment
Share on other sites

Guest Netduma_Iain

Abc could be correct about the host theory. Also as he mentions its not really possible to tell based on the information you've given. This leads me on to a very interesting point, lag is very very subjective. Some people will think a game is amazing and others will think its laggy. Furthermore the same person one day may say a connection is amazing and a next is horrible because they're in a rage mode ha!

 

This is exactly why we added the ping feature, so you get an objective value on how good the connection is.

 

Will this router benefit you? Well I'm biased so I'll just try to answer the following as factually as I can

  1. If the game is connecting you to further away hosts and the population size near you is big enough to pick closer hosts. Then the geo-filter should help you
  2. If people or devices at your home are overusing your bandwidth then our router should also help you there
  3. We have other features like aforementioned ping feature but I won't mention them as I assume you mean will it help in relation to connection quality

Hope that helps

Link to comment
Share on other sites

Guest Netduma_Iain

My pleasure,

 

I guess you could do a little experiment to see if its a local problem. Open the cmd prompt on your computer and type in "ping 8.8.8.8" and press enter. It should be under 40ms. The next time you think you're having a bad game run that command again. If it goes way above 40ms it could be a local issue.

 

Unfortunately its hard to tell if geo-filter would help, as it won't be easy to find the location of the host without our router.

Link to comment
Share on other sites

To Iain's point you might also want to try the following tools:

 

http://www.pingtest.net/- Reports your ping and jitter to a server (pick one close to you).

http://www.dslreports.com/smokepingIntensively monitor an IP address for 24 or more hours to review packet loss and/or excessive latency variability -- from three different US locations.

 

with windows you'll want to run "cmd"

ping 8.8.8.8 -t

This will ping 8.8.8.8 (google's DNS server) infinitely, close the cmd line tool to quit or hit Ctrl + C

Link to comment
Share on other sites

Thanks I will do that. I've always wondered what the 3 different NAT TYPES where. Does that affect my gameplay as well?

Yes, 100%.

 

Basically, the NAT types are as follows:

 

1. Strict: If you have a strict nat type you can only connect to someone with an open nat type.  This means that you are going to get games further away from you.

2. Moderate: You can only connect to Open and Moderate Nat Types, this means you will game further away.

4. Open: You can game with anyone, best experience.

Link to comment
Share on other sites

Ok thanks. I know almost nothing about how the games work. I just like to play, so I'm trying to learn more. That way I might have an all around better experience.

One thing you might also want to look into is your input latency (TV/Monitor)

If you aren't playing in "game mode" your TV might have 100ms latency of showing you what is happening...this makes a big difference as well.

Link to comment
Share on other sites

I used the smokeping tool for 4 hours and here's the results so far.

California : avg RTT 198.21, avg pkg loss 0.02 %

Michigan : avg RTT 180.30, avg pkg loss 1.90 %

Kansas : avg RTT 154.41, avg pkg loss 0.00 %

RTT = Round Trip Time also known as the ping.

 

So your pings to those locations are way too high, the issue here is that any ping over 100ms becomes completely noticeable.  The average human reacts in 100ms, this means that if me and you are paired against each other then even if i live in kansas and i'm the host I have 150ms of seeing you before you even see me...

 

You can see why this would hurt you so much, with this router you'd be able to not let someone in any of those states gets host.

Link to comment
Share on other sites

Guest Netduma_Iain

Thanks abc, one thing you should do though is ping 8.8.8.8 as it may be a local issue(e.g. your ISP messing up or you saturating your bandwidth).  8.8.8.8 is googles anycast address so its near everyone. So everyone should have 40ms and below to it, if not its quite likely a local issue. 

Link to comment
Share on other sites

Thanks abc, one thing you should do though is ping 8.8.8.8 as it may be a local issue(e.g. your ISP messing up or you saturating your bandwidth).  8.8.8.8 is googles anycast address so its near everyone. So everyone should have 40ms and below to it, if not its quite likely a local issue. 

This isn't always the case:

justin$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=55 time=195.077 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=55 time=190.118 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=190.540 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=107.102 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=96.607 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=55 time=129.705 ms

 

This is from a place I go to Work From Home, wifi network.  Obviously I don't control their network and they might be doing silly things but there isn't a guarantee that it is the closest router to you.

 

8.8.8.8 is a anycast address, so you will get the server "nearest" (in internet/metric terms (usually hops) - not neccessarily kilometers too) to you.

You will probably reach the googles datacenter in Frankfurt (i'm not sure if google has anything nearer to Austria).

justin$ traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
 1  192.168.0.2 (192.168.0.2)  1.301 ms  1.264 ms  1.463 ms
 2  cpe-74-134-72-1.swo.res.rr.com (74.134.72.1)  248.657 ms  93.299 ms  60.076 ms
 3  tge0-7-0-1.lsvqkydb02h.midwest.rr.com (74.128.23.149)  40.904 ms  83.962 ms  60.701 ms
 4  65.29.31.38 (65.29.31.38)  90.640 ms  70.608 ms  60.121 ms
 5  be24.clmkohpe01r.midwest.rr.com (65.189.140.162)  33.578 ms  36.520 ms  43.492 ms
 6  bu-ether15.atlngamq47w-bcr01.tbone.rr.com (107.14.19.36)  51.320 ms  49.607 ms  55.920 ms
 7  107.14.17.147 (107.14.17.147)  30.430 ms  36.934 ms  35.075 ms
 8  216.1.123.53 (216.1.123.53)  34.002 ms
    216.1.123.21 (216.1.123.21)  33.117 ms
    216.1.123.13 (216.1.123.13)  38.159 ms
 9  216.1.123.146 (216.1.123.146)  36.681 ms  34.165 ms  37.610 ms
10  209.85.243.143 (209.85.243.143)  29.920 ms
    209.85.243.99 (209.85.243.99)  38.149 ms
    66.249.94.173 (66.249.94.173)  38.829 ms
11  google-public-dns-a.google.com (8.8.8.8)  32.615 ms  29.608 ms  32.388 ms

 

But I agree that should give him a slightly better understanding of his ping times, which might be caused by his ISP (overselling his node [cable], or bad internal wiring [DSL/Cable])

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...