I'm Interested in a T1 Line

Status
Not open for further replies.
I don't know what a predictive ping algorithm is.

And you really should mind your baseless insults regarding my, as far as you're concerned, unknown skills in gaming.

This is what 100ms gets you. I prefired this guy in the game before he even started peeking after he went behind the box to give you an idea of the lag.
http://www.youtube.com/watch?v=GwcP__uI3zY

Game KDR's like 28-4, 27-3, 43-2, 44-2, 32-2, 36-2, 19-0 are indication you're wrong.

You hit him once and the rest of your shots went high. I'm not sure what you're complaining about. Seriously, this video doesn't show what you think it does. But hey, if you want to blow cash on a T1, be my guest. I'm sure the economy appreciates your extra spending.
 
You hit him once and the rest of your shots went high. I'm not sure what you're complaining about. Seriously, this video doesn't show what you think it does. But hey, if you want to blow cash on a T1, be my guest. I'm sure the economy appreciates your extra spending.

Yeah I agree, most of this is simply just blaming high latencies, when in reality it is simply the gamer who is physically at fault.

I'm sorry if I'm wrong, but all the posts the OP has made eventually lead to this.


@OP, again, get the T1 line and try it for a month or two, if it doesn't improve anything, then you will know that it isn't latency that is killing you. ;)
 
Thanks for clarifying that, it was a great explanation. :)

EDIT:
After reading through this thread, I'm sorry, but even when I have gamed in the past, 100ms was acceptable.

NExUS1g, do you game professionally?
I understand that having low latencies is your top priority over high data transfer rates, but don't you think you've pushed this far enough?

Why not just get the T1 line for a month or two, see if it actually will improve or degrade your latency, then move on.

Everyone here has a ton of experience in this area.
I know you don't like the answers you are seeing, but there are just too many variables within the infrastructure of the Internet to give you a completely solid/truthful answer.

I tracerouted and pinged your IP that you gave, and I get between 80-90ms, and I and others are able to game on my connection very well.

I'm not trying to be rude, but when you are going through all of this to simply shave off ~10ms, I agree with the others, it's time to improve your game. ;)

This is what frustrates me. People not reading or simply not comprehending what I put simply and plainly in my OP.

All I want to do is increase the <50ms ping coverage area that I have to include more people and servers. That's it.

To answer your question, I am a very competitive amateur FPS gamer.

And perhaps when you gamed in the past when 100ms was acceptable, everyone was pinging around there. But when someone's pinging 20 and you're pinging 100, it doesn't work out the same way.
 
Yeah I agree, most of this is simply just blaming high latencies, when in reality it is simply the gamer who is physically at fault.

I'm sorry if I'm wrong, but all the posts the OP has made eventually lead to this.


@OP, again, get the T1 line and try it for a month or two, if it doesn't improve anything, then you will know that it isn't latency that is killing you. ;)

Did you watch the video I linked?
 
You hit him once and the rest of your shots went high. I'm not sure what you're complaining about. Seriously, this video doesn't show what you think it does. But hey, if you want to blow cash on a T1, be my guest. I'm sure the economy appreciates your extra spending.

No, I didn't hit him at all. And in the actual game (not the recording of the game), I was firing BEFORE he peeked. In the replay, I wasn't even firing until after he came out. And the one shot I did fire right at him didn't even register. How did you miss my description in the post and the description on the video that pointed all of this out?

This alone shows you how much latency affects gameplay:
When I was playing the game: I started shooting before he even peeked from behind the cover.
Killcam showed: I didn't even start shooting until after he was looking at me and firing.

In fact, on my screen during the game he only fired one round from his pistol that killed me, but as you can see, he clearly fired 5.

And, again, you don't post scores like I do and require blaming ping for my deaths.
 
Last edited:
NExUS1g, I read this whole thread.

Get the freaking T1 line and see for yourself whether it will work or not.
Simple concept.

Otherwise accept that you aren't the hottest at FPS games and get over yourself and this thread.

Almost everyone here is a professional within this industry, and yet you constantly continue to degrade everyone for not "reading your OP".

I read the OP, as did every other person here who helped you solve your issue.

I'm sorry, but it's you who isn't reading our posts.

In fact, on my screen during the game he only fired one round from his pistol that killed me, but as you can see, he clearly fired 5.
I'm calling bullshit on this one.
Even if you had a latency of 100ms, it wouldn't make 4 of 5 pistol rounds fired at you disappear. Maybe 1 or 2, but not 4.

Once again, you are blaming latency, when latency is not the issue.
I'm leveling this and calling you on your lack of skill in FPS games.

But hey, we're talking to a guy who is willing to invest $250+ for an ancient connection, and the crappy version at that, over other options which have been brought up by professionals in the field.

I think you need to work on more than just your aim imo. ;)
 
Last edited:
No, I didn't hit him at all. And in the actual game (not the recording of the game), I was firing BEFORE he peeked. In the replay, I wasn't even firing until after he came out. And the one shot I did fire right at him didn't even register. How did you miss my description in the post and the description on the video that pointed all of this out?

This alone shows you how much latency affects gameplay:
When I was playing the game: I started shooting before he even peeked from behind the cover.
Killcam showed: I didn't even start shooting until after he was looking at me and firing.
So you're blaming the recording software now for showing you missing and not firing as quickly as you think you do?

At 8 seconds, you haven't even taken a single shot, even though he's in your reticle. It shows you taking (possibly fatal) damage, also driving your point of aim to a different place than you think. At the very last second of that video, you do see your own shots flying past him, but they miss.

In fact, on my screen during the game he only fired one round from his pistol that killed me, but as you can see, he clearly fired 5.
Yeah, and many of those were after the first killed you. As you can see, there are shots firing overhead. He kept shooting until he was sure you were actually dead.

http://imgur.com/a/XbTpD
1) You haven't fired yet, but have already been hit and your POA (and presumably POI) is high
2) Camera pulls back from you (indicating you're already dead), and you can see another shot through/by you
3) Another shot is still headed your way as you fall

I tried to pause and get a screenshot of your shots going by, but flash is a bit too picky at the end of videos to do that.

And, again, you don't post scores like I do and require blaming ping for my deaths.

Yeah, sure you don't :rolleyes:

Hey, if you've gotta blame equipment, that's fine, but that video really doesn't prove your case. If anything, it shows the opposite of what you think.
 
Ever consider blaming the game itself? Bugs, glitches, etc?

He posted a video, which in turn proves that it is not the game, but rather his lack of skill in the FPS. :rolleyes:

He's been given about 20 answers to his latency issue, but he refuses to listen.

Read through some of his other threads, you'll see what I mean.
Even when he is answered officially in them, he never even response back, or simply, blames the other person for his problems.
 
Search for high performance/gaming/specialty ISPs.

The local phone company is rarely your only choice for DSL.

Performance wise, DSL is better than cable. However, only if done right. The local phone company was crappy back in the dial up days, what makes people think they'll be great for DSL? Search around for specialty DSL providers. Be easier on your budget than getting a T.

As a heavy online gamer...had several different cable ISPs, had several different DSL ISPs...used to work with quite a few actually...but in my peak online gaming days, I used a high performance DSL ISP (hell back in the dial up days I used a performance dial up ISP). Oh yes they're worth it....your latency will be nice and low. And yes you can tell the difference between 40ms and 100ms.
 
This thread has been seriously de-railed.

No a T1 will not improve your ping times to the east coast.

Depending on who you get a T1 from you may even be using the same Tier 1 network provider as your current cable connection.

My recommendation is check out the other ISPs in the area and see if they can offer better service. If you give them a destination to ping they'll be able to tell you what kind of response time they can offer.
 
OP, Below are the requested pings directly from the Cisco router terminating a T1 in our lab. I will post the TWC pings in a separate message in a few min. All equipment is located in central NC.


minnow#ping 8.3.5.16

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.3.5.16, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 68/69/72 ms

minnow#ping 68.232.161.42

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 68.232.161.42, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 44/44/44 ms

minnow#ping 8.6.74.195

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.6.74.195, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/40 ms

minnow#ping 8.9.37.202

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 8.9.37.202, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/40/40 ms
 
The pings from the TWC 30/5 residential cable connection. These pings made from a Checkpoint 270 fw appliance directly attached to a Ubee ddw3611 in bridged mode.


[able]# ping 8.3.5.16
PING 8.3.5.16 (8.3.5.16) 56(84) bytes of data.
64 bytes from 8.3.5.16: icmp_seq=0 ttl=54 time=79.1 ms
64 bytes from 8.3.5.16: icmp_seq=1 ttl=54 time=77.3 ms
64 bytes from 8.3.5.16: icmp_seq=2 ttl=54 time=78.3 ms
64 bytes from 8.3.5.16: icmp_seq=3 ttl=54 time=79.4 ms
64 bytes from 8.3.5.16: icmp_seq=4 ttl=54 time=96.0 ms
64 bytes from 8.3.5.16: icmp_seq=5 ttl=54 time=78.6 ms

--- 8.3.5.16 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5001ms
rtt min/avg/max/mdev = 77.336/81.502/96.079/6.558 ms, pipe 2


[able]# ping 68.232.161.42
PING 68.232.161.42 (68.232.161.42) 56(84) bytes of data.
64 bytes from 68.232.161.42: icmp_seq=0 ttl=56 time=44.7 ms
64 bytes from 68.232.161.42: icmp_seq=1 ttl=56 time=43.0 ms
64 bytes from 68.232.161.42: icmp_seq=2 ttl=56 time=43.9 ms
64 bytes from 68.232.161.42: icmp_seq=3 ttl=56 time=44.6 ms
64 bytes from 68.232.161.42: icmp_seq=4 ttl=56 time=45.6 ms
64 bytes from 68.232.161.42: icmp_seq=5 ttl=56 time=43.1 ms

--- 68.232.161.42 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5002ms
rtt min/avg/max/mdev = 43.044/44.194/45.627/0.956 ms, pipe 2


PING 8.6.74.195 (8.6.74.195) 56(84) bytes of data.
64 bytes from 8.6.74.195: icmp_seq=0 ttl=54 time=51.9 ms
64 bytes from 8.6.74.195: icmp_seq=1 ttl=54 time=50.2 ms
64 bytes from 8.6.74.195: icmp_seq=2 ttl=54 time=48.8 ms
64 bytes from 8.6.74.195: icmp_seq=3 ttl=54 time=50.6 ms
64 bytes from 8.6.74.195: icmp_seq=4 ttl=54 time=67.3 ms
64 bytes from 8.6.74.195: icmp_seq=5 ttl=54 time=69.0 ms

--- 8.6.74.195 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 48.858/56.347/69.072/8.449 ms, pipe 2

[able]# ping 8.9.37.202
PING 8.9.37.202 (8.9.37.202) 56(84) bytes of data.
64 bytes from 8.9.37.202: icmp_seq=0 ttl=53 time=45.2 ms
64 bytes from 8.9.37.202: icmp_seq=1 ttl=53 time=47.1 ms
64 bytes from 8.9.37.202: icmp_seq=2 ttl=53 time=48.0 ms
64 bytes from 8.9.37.202: icmp_seq=3 ttl=53 time=45.6 ms
64 bytes from 8.9.37.202: icmp_seq=4 ttl=53 time=46.4 ms
64 bytes from 8.9.37.202: icmp_seq=5 ttl=53 time=47.2 ms

--- 8.9.37.202 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5002ms
rtt min/avg/max/mdev = 45.227/46.634/48.074/1.007 ms, pipe 2
 
I'm sorry... This thread just cracks me up. T1s are reliable because they've been around forever. I think thats about it.

We use a few T1's.. Mostly for voice only.

So.. to further entertain my laugh for today:

Fiber.



Code:
Pinging 8.3.5.16 with 32 bytes of data:
Reply from 8.3.5.16: bytes=32 time=69ms TTL=52
Reply from 8.3.5.16: bytes=32 time=69ms TTL=52
Reply from 8.3.5.16: bytes=32 time=69ms TTL=52
Reply from 8.3.5.16: bytes=32 time=69ms TTL=52

Code:
Pinging 68.232.161.42 with 32 bytes of data:
Reply from 68.232.161.42: bytes=32 time=41ms TTL=53
Reply from 68.232.161.42: bytes=32 time=41ms TTL=53
Reply from 68.232.161.42: bytes=32 time=41ms TTL=53
Reply from 68.232.161.42: bytes=32 time=41ms TTL=53

Code:
Pinging 8.6.74.195 with 32 bytes of data:
Reply from 8.6.74.195: bytes=32 time=48ms TTL=52
Reply from 8.6.74.195: bytes=32 time=47ms TTL=52
Reply from 8.6.74.195: bytes=32 time=47ms TTL=52
Reply from 8.6.74.195: bytes=32 time=48ms TTL=52

Code:
Pinging 8.9.37.202 with 32 bytes of data:
Reply from 8.9.37.202: bytes=32 time=71ms TTL=49
Reply from 8.9.37.202: bytes=32 time=71ms TTL=49
Reply from 8.9.37.202: bytes=32 time=71ms TTL=49
Reply from 8.9.37.202: bytes=32 time=71ms TTL=49

And for kicks and giggles

Code:
Pinging 4.2.2.2 with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=43ms TTL=53
Reply from 4.2.2.2: bytes=32 time=42ms TTL=53
Reply from 4.2.2.2: bytes=32 time=42ms TTL=53
Reply from 4.2.2.2: bytes=32 time=43ms TTL=53

These times also reflect 30 people using the internet with average use. Get these same results with a t1 even with maybe 1-2 maybe 3 people. I don't see it happening.
 
I'm sorry... This thread just cracks me up. T1s are reliable because they've been around forever. I think thats about it.

There are other reasons why it's reliable....not because it's been around forever. It's the priority of it's support, how it's marked and laid out as lines...installed, it's treated as high priority (supposed to) all around.

However, these days I feel that common broadband isn't unreliable either...I have plenty of clients on common broadband that don't see downtime...and I have clients on T's that actually do experience downtime.
 
calvinj,
Same here...we have a p2p T1 for a branch office, PRI for voice, and 2 other T1s, but our main internet is 10x10 fiber.
As far as downtime goes, we had an issue with the PRI last week and at&t is just a royal pain to deal with. The problem 'fixed itself' in 2 days...
When our p2p went down they came out right away and it was fixed fast. Both ended up being outside plant related.
 
There are other reasons why it's reliable....not because it's been around forever. It's the priority of it's support, how it's marked and laid out as lines...installed, it's treated as high priority (supposed to) all around.

I know there was more to T1, but I figured the guys who have to deal with this stuff on a daily/regular basis had pretty well covered it.

calvinj,
Same here...we have a p2p T1 for a branch office, PRI for voice, and 2 other T1s, but our main internet is 10x10 fiber.
As far as downtime goes, we had an issue with the PRI last week and at&t is just a royal pain to deal with. The problem 'fixed itself' in 2 days...
When our p2p went down they came out right away and it was fixed fast. Both ended up being outside plant related.

hmm.. AT&T Imagine that. I spent a weekend arguing with them that we had dirty t1's and their tier 2 support refused to listen to me. I demanded they run a line test and they were very reluctant to do it. Got a call on Tuesday after the plant folks ran the tests. Guess what they found. Dirty T1s. Hopefully we'll be able to eliminate AT&T in 2012
 
So you're blaming the recording software now for showing you missing and not firing as quickly as you think you do?

At 8 seconds, you haven't even taken a single shot, even though he's in your reticle. It shows you taking (possibly fatal) damage, also driving your point of aim to a different place than you think. At the very last second of that video, you do see your own shots flying past him, but they miss.


Yeah, and many of those were after the first killed you. As you can see, there are shots firing overhead. He kept shooting until he was sure you were actually dead.

http://imgur.com/a/XbTpD
1) You haven't fired yet, but have already been hit and your POA (and presumably POI) is high
2) Camera pulls back from you (indicating you're already dead), and you can see another shot through/by you
3) Another shot is still headed your way as you fall

I tried to pause and get a screenshot of your shots going by, but flash is a bit too picky at the end of videos to do that.



Yeah, sure you don't :rolleyes:

Hey, if you've gotta blame equipment, that's fine, but that video really doesn't prove your case. If anything, it shows the opposite of what you think.

The killcam shows what the host saw, not what my client saw. I don't record when I'm actually playing which is why I had to explain in words what happened on my screen during the actual game. And you don't get killed with one shot from a pistol under any circumstances.
 
Last edited:
Comcast 50Mb Business Package in Milwaukee OR.

Code:
PING 8.3.5.16 (8.3.5.16) from 173.8.192.19: 56 data bytes
64 bytes from 8.3.5.16: icmp_seq=0 ttl=57 time=35.638 ms
64 bytes from 8.3.5.16: icmp_seq=1 ttl=57 time=34.038 ms
64 bytes from 8.3.5.16: icmp_seq=2 ttl=57 time=34.508 ms
64 bytes from 8.3.5.16: icmp_seq=3 ttl=57 time=37.472 ms

--- 8.3.5.16 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 34.038/35.414/37.472/1.323 ms

Code:
PING 68.232.161.42 (68.232.161.42) from 173.8.192.19: 56 data bytes
64 bytes from 68.232.161.42: icmp_seq=0 ttl=53 time=57.788 ms
64 bytes from 68.232.161.42: icmp_seq=1 ttl=53 time=58.526 ms
64 bytes from 68.232.161.42: icmp_seq=2 ttl=53 time=60.404 ms
64 bytes from 68.232.161.42: icmp_seq=3 ttl=53 time=57.440 ms

--- 68.232.161.42 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 57.440/58.539/60.404/1.146 ms

Code:
PING 8.6.74.195 (8.6.74.195) from 173.8.192.19: 56 data bytes
64 bytes from 8.6.74.195: icmp_seq=0 ttl=53 time=63.716 ms
64 bytes from 8.6.74.195: icmp_seq=1 ttl=53 time=66.804 ms
64 bytes from 8.6.74.195: icmp_seq=2 ttl=53 time=63.054 ms
64 bytes from 8.6.74.195: icmp_seq=3 ttl=53 time=64.767 ms

--- 8.6.74.195 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 63.054/64.585/66.804/1.419 ms
Code:
PING 8.9.37.202 (8.9.37.202) from 173.8.192.19: 56 data bytes
64 bytes from 8.9.37.202: icmp_seq=0 ttl=53 time=71.676 ms
64 bytes from 8.9.37.202: icmp_seq=1 ttl=53 time=71.480 ms
64 bytes from 8.9.37.202: icmp_seq=2 ttl=53 time=71.793 ms
64 bytes from 8.9.37.202: icmp_seq=3 ttl=53 time=71.321 ms

--- 8.9.37.202 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 71.321/71.567/71.793/0.181 ms

Code:
PING 4.2.2.2 (4.2.2.2) from 173.8.192.19: 56 data bytes
64 bytes from 4.2.2.2: icmp_seq=0 ttl=57 time=23.629 ms
64 bytes from 4.2.2.2: icmp_seq=1 ttl=57 time=24.054 ms
64 bytes from 4.2.2.2: icmp_seq=2 ttl=57 time=23.897 ms
64 bytes from 4.2.2.2: icmp_seq=3 ttl=57 time=23.118 ms

--- 4.2.2.2 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 23.118/23.674/24.054/0.355 ms
 
The killcam shows what the host saw, not what my client saw. I don't record when I'm actually playing which is why I had to explain in words what happened on my screen during the actual game. And you don't get killed with one shot from a pistol under any circumstances.

Still whinging that somebody else beat you?
 
Still whinging that somebody else beat you?

There are plenty of demonstrations that show that I'm very good at FPS's right at your fingertips. You can choose to ignore it if you like and just assume, against all evidence to the contrary, that I'm just bad at FPS's and latency has nothing to do with performance in an online game.

Pisses me off that the thread was hijacked from "How far will a T1 extend my <50ms service area -- please provide evidence," to, "100ms latency isn't too high for a first-person shooter, " and, "You just suck, dude."
 
Last edited:
Code:
U:\>ping 8.3.5.16

Pinging 8.3.5.16 with 32 bytes of data:
Reply from 8.3.5.16: bytes=32 time=87ms TTL=45
Reply from 8.3.5.16: bytes=32 time=86ms TTL=45
Reply from 8.3.5.16: bytes=32 time=87ms TTL=45
Reply from 8.3.5.16: bytes=32 time=88ms TTL=45

Ping statistics for 8.3.5.16:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 86ms, Maximum = 88ms, Average = 87ms

U:\>ping 68.232.161.42

Pinging 68.232.161.42 with 32 bytes of data:
Reply from 68.232.161.42: bytes=32 time=77ms TTL=45
Reply from 68.232.161.42: bytes=32 time=75ms TTL=44
Reply from 68.232.161.42: bytes=32 time=76ms TTL=45
Reply from 68.232.161.42: bytes=32 time=75ms TTL=44

Ping statistics for 68.232.161.42:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 77ms, Average = 75ms

U:\>ping 8.6.74.195

Pinging 8.6.74.195 with 32 bytes of data:
Reply from 8.6.74.195: bytes=32 time=63ms TTL=49
Reply from 8.6.74.195: bytes=32 time=63ms TTL=49
Reply from 8.6.74.195: bytes=32 time=63ms TTL=49
Reply from 8.6.74.195: bytes=32 time=62ms TTL=49

Ping statistics for 8.6.74.195:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 62ms, Maximum = 63ms, Average = 62ms

U:\>ping 8.9.37.202

Pinging 8.9.37.202 with 32 bytes of data:
Reply from 8.9.37.202: bytes=32 time=54ms TTL=47
Reply from 8.9.37.202: bytes=32 time=54ms TTL=48
Reply from 8.9.37.202: bytes=32 time=53ms TTL=47
Reply from 8.9.37.202: bytes=32 time=56ms TTL=47

Ping statistics for 8.9.37.202:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 56ms, Average = 54ms

U:\>ping 4.2.2.2

Pinging 4.2.2.2 with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=57ms TTL=51
Reply from 4.2.2.2: bytes=32 time=57ms TTL=51
Reply from 4.2.2.2: bytes=32 time=57ms TTL=51
Reply from 4.2.2.2: bytes=32 time=57ms TTL=51

Ping statistics for 4.2.2.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 57ms, Maximum = 57ms, Average = 57ms

This is from a 100/100 Fibre connection in Southern Saskatchewan Canada. 100/100 Fibre connection which is connected directly to our ISPs backbone. (It's actually on our private, provincial wide health network.)

(Did this just to entertain you.)
 
Last edited:
There are plenty of demonstrations that show that I'm very good at FPS's right at your fingertips. You can choose to ignore it if you like and just assume, against all evidence to the contrary, that I'm just bad at FPS's and latency has nothing to do with performance in an online game.

Pisses me off that the thread was hijacked from "How far will a T1 extend my <50ms service area -- please provide evidence," to, "100ms latency isn't too high for a first-person shooter, " and, "You just suck, dude."

Your question was answered many, many times. Past a certain point your packets will take the same route as cable/dsl. Different providers of T1 service will have different points at when this happens. The only way to get your answer is to get a T1 and find out if it provides the specific service that you want. The only pre-installation answer that will be useful is to find someone locally that uses the T1 provider with the same package that you are looking at and perform your tests on that T1. Ping results from random people across the country will not give you the answers you are looking for, and will only get the general answer that you have been getting, which is "Won't make much of a difference, and too many factors to have any guarantee of ping and range"

Just be glad you aren't a pro Korean Starcraft player that has to deal with 1500ms round trip to play on American servers (and yet they still dominate local American players).
 
There are plenty of demonstrations that show that I'm very good at FPS's right at your fingertips. You can choose to ignore it if you like and just assume, against all evidence to the contrary, that I'm just bad at FPS's and latency has nothing to do with performance in an online game.

Pisses me off that the thread was hijacked from "How far will a T1 extend my <50ms service area -- please provide evidence," to, "100ms latency isn't too high for a first-person shooter, " and, "You just suck, dude."

I don't know why it pisses you off when you've been given multiple answers multiple times from multiple professionals within the industry.
You just refuse to listen to what anyone here actually has to say, be it fact or opinion.


As I said before, why not just try the T1 line for a month or two.
If you don't see any improvements on latency, then try a higher teir of T1 or move to a different connection technology.

I'm not sure why you haven't done this when you are still willing to shell out $250+ per month. :confused:
 
I came home last night and laughed my ass off at the 6 pages of crap posted. Now i got up today and am laughing even more at the last two. wow.....


The only way to prove to yourself that T1 will work in your situation is to get one for 30 days or so and test it out.
 
Your question was answered many, many times. Past a certain point your packets will take the same route as cable/dsl. Different providers of T1 service will have different points at when this happens. The only way to get your answer is to get a T1 and find out if it provides the specific service that you want. The only pre-installation answer that will be useful is to find someone locally that uses the T1 provider with the same package that you are looking at and perform your tests on that T1. Ping results from random people across the country will not give you the answers you are looking for, and will only get the general answer that you have been getting, which is "Won't make much of a difference, and too many factors to have any guarantee of ping and range"

Just be glad you aren't a pro Korean Starcraft player that has to deal with 1500ms round trip to play on American servers (and yet they still dominate local American players).

I'm not arguing with anyone who has given sound advice. I may ask questions or challenge to get more information or a better understanding. Only those who are saying, "You just suck, dude," and, "100ms isn't too much," are the ones with whom I'm arguing.
 
I'm not arguing with anyone who has given sound advice. I may ask questions or challenge to get more information or a better understanding. Only those who are saying, "You just suck, dude," and, "100ms isn't too much," are the ones with whom I'm arguing.

I'm sorry but no, you've been arguing with every single person here, not just the few who pointed out the obvious. :rolleyes:

Again, as I and everyone else here are saying and what you keep missing, try the T1 line for a month and see if it helps your situation.
 
I definitely question the OP's choice of looking for a T1 for gaming, but I'm surprised how many people are telling the OP to live with 100ms lag. Are you the same people that say you can't see more than 60fps, are you the same people that say 3-way SLI is pointless, are you the same people that say eyefinity if meaningless.

What is this SOFT OCP?

He's not asking if YOU can see the difference between 20ms and 100ms of internet lag, he's telling you he CAN see the difference, and he needs help getting those pings lower.

Maybe there is no solution in his case, thats fine. But telling him he's doing something wrong because he wants lower than 100ms... are you joking?
 
I don't know why it pisses you off when you've been given multiple answers multiple times from multiple professionals within the industry.
You just refuse to listen to what anyone here actually has to say, be it fact or opinion.


As I said before, why not just try the T1 line for a month or two.
If you don't see any improvements on latency, then try a higher teir of T1 or move to a different connection technology.

I'm not sure why you haven't done this when you are still willing to shell out $250+ per month. :confused:

When I come here, it's all a part of my research and learning when I'm looking at buying or doing something. Look at the few other threads I've started the past (almost) decade. I pose a question then glean as much information as I can to assist me in making a decision. I don't come here for someone to tell me what to do; I come for information that allows me to make an educated decision, correct my incorrect thinking and understand better what I'm doing. If I didn't need those three things, I wouldn't be here asking.
 
I definitely question the OP's choice of looking for a T1 for gaming, but I'm surprised how many people are telling the OP to live with 100ms lag. Are you the same people that say you can't see more than 60fps, are you the same people that say 3-way SLI is pointless, are you the same people that say eyefinity if meaningless.

What is this SOFT OCP?

He's not asking if YOU can see the difference between 20ms and 100ms of internet lag, he's telling you he CAN see the difference, and he needs help getting those pings lower.

Maybe there is no solution in his case, thats fine. But telling him he's doing something wrong because he wants lower than 100ms... are you joking?

He's not operating at 100ms, that was just an example.
He's operating at around 50ms, which leads everyone here to believe that it's his lack of skill in these games, not the connection latency that is the problem.
Not to mention the video he posted isn't helping his argument.

Another thing, he's been given a ton of answers, solutions, and options, yet he refuses to take any of them or even try them.

Maybe he can see the difference between latencies, which we all can, but sitting here blaming everyone else for his problems really doesn't inspire us to continue helping.
 
When I come here, it's all a part of my research and learning when I'm looking at buying or doing something. Look at the few other threads I've started the past (almost) decade. I pose a question then glean as much information as I can to assist me in making a decision. I don't come here for someone to tell me what to do; I come for information that allows me to make an educated decision, correct my incorrect thinking and understand better what I'm doing. If I didn't need those three things, I wouldn't be here asking.

You've asked, and you've been answered, more times than I can count.

It's time for you to fish or cut bait.

Make a decision, I don't know what further "information" you want that hasn't already been given multiple times over. :confused:
 
I definitely question the OP's choice of looking for a T1 for gaming, but I'm surprised how many people are telling the OP to live with 100ms lag. Are you the same people that say you can't see more than 60fps, are you the same people that say 3-way SLI is pointless, are you the same people that say eyefinity if meaningless.

What is this SOFT OCP?

He's not asking if YOU can see the difference between 20ms and 100ms of internet lag, he's telling you he CAN see the difference, and he needs help getting those pings lower.

Maybe there is no solution in his case, thats fine. But telling him he's doing something wrong because he wants lower than 100ms... are you joking?

If he wants to pay out the ass for a (possibly) lower latency connection, be my guest. If you want to spend $2000 on a tri-SLI setup, be my guest. I think both are kind of a waste, but then again people probably think all my servers and network gear is a waste. To each his own. The T1 most likely won't improve his ping all that much to be honest.
 
He's not operating at 100ms, that was just an example.
He's operating at around 50ms, which leads everyone here to believe that it's his lack of skill in these games, not the connection latency that is the problem.

And that's you not reading my posts if you believe that.

Another thing, he's been given a ton of answers, solutions, and options, yet he refuses to take any of them or even try them.

I'm gathering information, not making decisions right now. I have not refused anything. Find something where I say, "I refuse to do this," or anything like it.

Maybe he can see the difference between latencies, which we all can, but sitting here blaming everyone else for his problems really doesn't inspire us to continue helping.

Who am I blaming for my "problems"? Not that I have a problem, per se, but I'd like to improve my range. I'm not interested in decreasing local west coast latencies, I want to expand my <50ms geographical range.
 
If he wants to pay out the ass for a (possibly) lower latency connection, be my guest. If you want to spend $2000 on a tri-SLI setup, be my guest. I think both are kind of a waste, but then again people probably think all my servers and network gear is a waste. To each his own. The T1 most likely won't improve his ping all that much to be honest.

Yep, in the end it's his wallet.
I don't blame him for asking so many questions, but he's been answered, again and again.

Make a decision damn it! :D :p
 
He's not operating at 100ms, that was just an example.
He's operating at around 50ms, which leads everyone here to believe that it's his lack of skill in these games, not the connection latency that is the problem.
Not to mention the video he posted isn't helping his argument..
No, he wants to expand his ring of 50ms out farther, he seems content to play at 50ms and below. However, he wants to lower all of his times that are higher than 50ms.
 
Yep, in the end it's his wallet.
I don't blame him for asking so many questions, but he's been answered, again and again.

Make a decision damn it! :D :p

I'm not asking for anyone to repeat themselves, but I will keep asking and challenging until I'm confident I understand well enough to make an educated decision.
 
No, he wants to expand his ring of 50ms out farther, he seems content to play at 50ms and below. However, he wants to lower all of his times that are higher than 50ms.

I appreciate your grasp of what I'm asking for and talking about. Thank you.
 
No, he wants to expand his ring of 50ms out farther, he seems content to play at 50ms and below. However, he wants to lower all of his times that are higher than 50ms.
I understand that.

Once again, he should just get the T1 line for a month, see if it improves his situation, then move on.

If it doesn't, then we can try a different solution.

Until then, simply talking about the situation isn't going to help anything.
He needs to make a decision at this point.

I don't understand why he doesn't just try it at this point.
He's willing to pay the money for it, so what can it hurt to try?
 
I understand that.

Once again, he should just get the T1 line for a month, see if it improves his situation, then move on.

If it doesn't, then we can try a different solution.

Until then, simply talking about the situation isn't going to help anything.
He needs to make a decision at this point.

I don't understand why he doesn't just try it at this point.
He's willing to pay the money for it, so what can it hurt to try?

It hurts merely because it's a pain in the ass to change services. That's why I like to try to find the best option in theory prior to making a decision. While, no, money is not a big deal for me, I still don't like the hassles of life like going through a few different services over a few months just to find what's best when I may be able to determine that information by picking some brains.

And to be honest, given the responses and instruction from this thread, I'm leaning towards not going with a T1 and looking deeper at other options mentioned in this thread. Some just assumed I had already made up my mind.
 
It hurts merely because it's a pain in the ass to change services. That's why I like to try to find the best option in theory prior to making a decision. While, no, money is not a big deal for me, I still don't like the hassles of life like going through a few different services over a few months just to find what's best when I may be able to determine that information by picking some brains.

And to be honest, given the responses and instruction from this thread, I'm leaning towards not going with a T1 and looking deeper at other options mentioned in this thread. Some just assumed I had already made up my mind.

You really should have said that earlier... say what you want, but we were lead to believe that.

Anyways, T1 is pretty slow. Would be even be fine with 1.5? That's dog slow with today's standards...

Use this to see if it finds anything else for you. http://www.dslserviceproviders.org/
 
Status
Not open for further replies.
Back
Top