Ok, so i usually get 20 ping to chicago on any other server. But for some reason ESEA servers I get 100 ping. what the fuck. Is there anyway you can fix this? Also holy shit the fucking sliding doors.
ESEA Servers
posted in
TF2 General Discussion
Ok, so i usually get 20 ping to chicago on any other server. But for some reason ESEA servers I get 100 ping. what the fuck. Is there anyway you can fix this? Also holy shit the fucking sliding doors.
I died backing into a sliding door that never opened.
I died backing into a sliding door that never opened.
like there has to be problems with the tick rate or something. Buy nfo servers.
like there has to be problems with the tick rate or something. Buy nfo servers.
i've had the same thing, usually get 50 ping, now i get 150 ping
i've had the same thing, usually get 50 ping, now i get 150 ping
Also it is not just Chicago servers. Definitely happens on texas servers for me, also probably happens on every ESEA server. Also I was getting some choke as well when connected to the server(hopped up to 7-10 every so often). If anyone from ESEA could help explain why this is happening when I live like 200 miles away from chicago, that would be cool.
edit:
When in the ESEA client server browser, my pings show up as normal. But when I connect shit hits the fan, and I get +70 ping than in browser.
Also it is not just Chicago servers. Definitely happens on texas servers for me, also probably happens on every ESEA server. Also I was getting some choke as well when connected to the server(hopped up to 7-10 every so often). If anyone from ESEA could help explain why this is happening when I live like 200 miles away from chicago, that would be cool.
edit:
When in the ESEA client server browser, my pings show up as normal. But when I connect shit hits the fan, and I get +70 ping than in browser.
edit:
When in the ESEA client server browser, my pings show up as normal. But when I connect shit hits the fan, and I get +70 ping than in browser.
Another update:
I had 30 ping while in our server before our match today. However, once everyone joined up I was getting upwards of 150 ping. Towards the 2nd half I think I was getting around 80 ping. And as soon as people left I was down to 45 ping before I left. Any idea what could cause this? Is it on my end, or ESEA?
Another update:
I had 30 ping while in our server before our match today. However, once everyone joined up I was getting upwards of 150 ping. Towards the 2nd half I think I was getting around 80 ping. And as soon as people left I was down to 45 ping before I left. Any idea what could cause this? Is it on my end, or ESEA?
I had 30 ping while in our server before our match today. However, once everyone joined up I was getting upwards of 150 ping. Towards the 2nd half I think I was getting around 80 ping. And as soon as people left I was down to 45 ping before I left. Any idea what could cause this? Is it on my end, or ESEA?
why would they change because people came into the server though. It was fine when there weren't as many people in server. Also, you mean rates as in the cvar's right? Those would effect ping?
why would they change because people came into the server though. It was fine when there weren't as many people in server. Also, you mean rates as in the cvar's right? Those would effect ping?
happened to banny, lansky, justin as far as I remember during last weeks matches
happened to banny, lansky, justin as far as I remember during last weeks matches
ESEA servers have always been shit, and complaining just gets a "They are all top quality, STFU nubs."
You can basically call it GG on this already. Although if you suggest more Atlanta & Colorado servers they'd probably oblige.
ESEA servers have always been shit, and complaining just gets a "They are all top quality, STFU nubs."
You can basically call it GG on this already. Although if you suggest more Atlanta & Colorado servers they'd probably oblige.
You can basically call it GG on this already. Although if you suggest more Atlanta & Colorado servers they'd probably oblige.
Well this kind of started as a complain thread from me, but now I'm more interested in whether or not there is something I can do to prevent this.
Well this kind of started as a complain thread from me, but now I'm more interested in whether or not there is something I can do to prevent this.
Maybe remove your esea client and anything in your reg pertaining to it. Then to trace route tests to the server and save them. Then install the client and try again, this time redo the trace tests and see if you notice any specific hop jump up more then any others. So:
34 36 33
35 34 37
* 120 119 <- sudden jump or * hitting this specific router/host
And if it's on the last hop, the ESEA server, then it's something wrong with the server or client. If the jump is way before or somewhere in chicago land (hopefully you're only a few hops away and not routing through the west coast somehow) then you can bring these results up to your ISP and they can investigate a bad hop for you if you complain enough.
What is odd, as you noted, is that you say it's also on TX servers. This is why I wanted you to reinstall the client first, maybe it's a simple application issue.
Also turn off your virus scan software when you play with the client running.
Maybe remove your esea client and anything in your reg pertaining to it. Then to trace route tests to the server and save them. Then install the client and try again, this time redo the trace tests and see if you notice any specific hop jump up more then any others. So:
34 36 33
35 34 37
* 120 119 <- sudden jump or * hitting this specific router/host
And if it's on the last hop, the ESEA server, then it's something wrong with the server or client. If the jump is way before or somewhere in chicago land (hopefully you're only a few hops away and not routing through the west coast somehow) then you can bring these results up to your ISP and they can investigate a bad hop for you if you complain enough.
What is odd, as you noted, is that you say it's also on TX servers. This is why I wanted you to reinstall the client first, maybe it's a simple application issue.
Also turn off your virus scan software when you play with the client running.
34 36 33
35 34 37
* 120 119 <- sudden jump or * hitting this specific router/host
And if it's on the last hop, the ESEA server, then it's something wrong with the server or client. If the jump is way before or somewhere in chicago land (hopefully you're only a few hops away and not routing through the west coast somehow) then you can bring these results up to your ISP and they can investigate a bad hop for you if you complain enough.
What is odd, as you noted, is that you say it's also on TX servers. This is why I wanted you to reinstall the client first, maybe it's a simple application issue.
Also turn off your virus scan software when you play with the client running.
Well the thing I'm failing to understand is if it is the client. Then why does it show perfectly fine ping in the ESEA client server browser. Im not positive, but I think that even if a server is full in the client browser the ping appears fine through esea client. I'd have to test this as I'm not positive, but like I said I'm pretty sure it is normal.
Well the thing I'm failing to understand is if it is the client. Then why does it show perfectly fine ping in the ESEA client server browser. Im not positive, but I think that even if a server is full in the client browser the ping appears fine through esea client. I'd have to test this as I'm not positive, but like I said I'm pretty sure it is normal.
Please
sign in through STEAM
to post a comment.