Upvote Upvoted 8 Downvote Downvoted
1 2
Esea stahp!
1
#1
7 Frags +

I was wondering if i could get some feed back on this issue. My team is 6in, and we had a match tonight. When we joined we noticed that the server was completely laggy. Both teams decided that we could just ask to switch servers. We moved to another server which seemed fine but just as we readied up, it was almost impossible to do very much. We had to give up mid twice just because our med couldn't event leave spawn with his lag, and our demo ended up some where in IT staring at a wall.
We paused it for a good 5 minutes to see if the lag would go away. When we unpaused, it was fine for a good 30 seconds,then started up agian, which led to another demo some where odd medic lagging ect ect. We msged killing a again asking whats going on, he asked for the time and moved us to a third server which was still a little meh. He said we only had 13 mins to play until game ends. In the end we had to play rushed and were unable to play normally. I not trying to down killing or anything because i know he cant do much. But im just wondering if theres anything we can do. We feel as if we could have done much better if not for the constant servers chokes

This picture here is of Server 2: http://minus.com/lbihKKPE6D1BZF

This picture is of 3(note the choke) http://i.imgur.com/VrQ1w.jpg

Sadly this is a minor case of it: http://www.youtube.com/watch?v=2n-XEjWqtCI&feature=youtu.be

I was wondering if i could get some feed back on this issue. My team is 6in, and we had a match tonight. When we joined we noticed that the server was completely laggy. Both teams decided that we could just ask to switch servers. We moved to another server which seemed fine but just as we readied up, it was almost impossible to do very much. We had to give up mid twice just because our med couldn't event leave spawn with his lag, and our demo ended up some where in IT staring at a wall.
We paused it for a good 5 minutes to see if the lag would go away. When we unpaused, it was fine for a good 30 seconds,then started up agian, which led to another demo some where odd medic lagging ect ect. We msged killing a again asking whats going on, he asked for the time and moved us to a third server which was still a little meh. He said we only had 13 mins to play until game ends. In the end we had to play rushed and were unable to play normally. I not trying to down killing or anything because i know he cant do much. But im just wondering if theres anything we can do. We feel as if we could have done much better if not for the constant servers chokes

This picture here is of Server 2: http://minus.com/lbihKKPE6D1BZF

This picture is of 3(note the choke) http://i.imgur.com/VrQ1w.jpg

Sadly this is a minor case of it: http://www.youtube.com/watch?v=2n-XEjWqtCI&feature=youtu.be
2
#2
2 Frags +

http://play.esea.net/index.php?s=support&d=tickets

http://play.esea.net/index.php?s=support&d=tickets
3
#3
0 Frags +

Thanks for the link, i just posted it, but thanks any way.

Thanks for the link, i just posted it, but thanks any way.
4
#4
0 Frags +

yea, it was pretty stupid, shots didn't register, roamer and demo couldn't jump, got warped back in time several times...

many thanks to killing for the support anyway

yea, it was pretty stupid, shots didn't register, roamer and demo couldn't jump, got warped back in time several times...

many thanks to killing for the support anyway
5
#5
1 Frags +

We had the same issues. I was rubber banding like crazy and it was really bad. I was slow on almost all of my rollouts and so was our roamer. I was hoping for a cleaner first match. I hope that something can be done about this soon!

We had the same issues. I was rubber banding like crazy and it was really bad. I was slow on almost all of my rollouts and so was our roamer. I was hoping for a cleaner first match. I hope that something can be done about this soon!
6
#6
2 Frags +

i was late to mid as scout wtfff

i was late to mid as scout wtfff
7
#7
13 Frags +

Our game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.

Our game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.
8
#8
2 Frags +

My team had a bad server. Luckily when we messaged killing the server he moved it to was fine. So big ups to him for that.

My team had a bad server. Luckily when we messaged killing the server he moved it to was fine. So big ups to him for that.
9
#9
0 Frags +

Yeah those lags happen alot for teams (randomly). You just have to learn to deal with it. I am not sure if there is anything ESEA can do to fix it.

What I have done in the past is keep a log of bad servers we played in, and made sure to not accept or ask for a match there again. Oh btw, if it happens alot in a match and both teams agree, you can ask an admin to switch servers if both teams have not scored yet.

Yeah those lags happen alot for teams (randomly). You just have to learn to deal with it. I am not sure if there is anything ESEA can do to fix it.

What I have done in the past is keep a log of bad servers we played in, and made sure to not accept or ask for a match there again. Oh btw, if it happens alot in a match and both teams agree, you can ask an admin to switch servers if both teams have not scored yet.
10
#10
0 Frags +

We did Cheeriss, We switched before the matched started. When we got to the other server it seemed fine, then lagged even worse then before.

We did Cheeriss, We switched before the matched started. When we got to the other server it seemed fine, then lagged even worse then before.
11
#11
0 Frags +

Ah man. That sucks. Sorry wiggles. But yes, its a risk for changing servers. Make sure your scheduler notes the servers you have played on and do not play on them again.

Ah man. That sucks. Sorry wiggles. But yes, its a risk for changing servers. Make sure your scheduler notes the servers you have played on and do not play on them again.
12
#12
0 Frags +

Yea, I know, thanks again switching to 3 different servers sucks.

Yea, I know, thanks again switching to 3 different servers sucks.
13
#13
15 Frags +

stop complaining, its not like you paid for this service

stop complaining, its not like you paid for this service
14
#14
2 Frags +
visitnigstop complaining, its not like you paid for this service

Except we did its ESEA not UGC

I also am stupid as shit ignore me

[quote=visitnig]stop complaining, its not like you paid for this service[/quote]

Except we did its ESEA not UGC

I also am stupid as shit ignore me
15
#15
6 Frags +

Whoosh.

Whoosh.
16
#16
13 Frags +

http://media.tumblr.com/tumblr_ma7c6fjIuE1r349cg.jpg

[img]http://media.tumblr.com/tumblr_ma7c6fjIuE1r349cg.jpg[/img]
17
#17
3 Frags +
fraacWhoosh.

Ya i realize this now

[quote=fraac]Whoosh.[/quote]

Ya i realize this now
18
#18
2 Frags +
KillertomatoOur game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.

You only crash if you use the preset loadouts, manually changing weapons is fine.

still retarded though

[quote=Killertomato]Our game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.[/quote]

You only crash if you use the preset loadouts, manually changing weapons is fine.

still retarded though
19
#19
1 Frags +
PereyKillertomatoOur game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.
You only crash if you use the preset loadouts, manually changing weapons is fine.

still retarded though

Unless you forget and still change presets.

[quote=Perey][quote=Killertomato]Our game had it so if our team changed loadouts we would crash. Luckily we solved this problem by getting rolled so we didn't have to forward spawn.[/quote]

You only crash if you use the preset loadouts, manually changing weapons is fine.

still retarded though[/quote]

Unless you forget and still change presets.
20
#20
1 Frags +

Apparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.

Apparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.
21
#21
2 Frags +
StealthyfraacWhoosh.
Ya i realize this now

Oh Kartike... Always so serious...

[quote=Stealthy][quote=fraac]Whoosh.[/quote]

Ya i realize this now[/quote]

Oh Kartike... Always so serious...
22
#22
4 Frags +
fosterApparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.

This often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.

[quote=foster]Apparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.[/quote]
This often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.
23
#23
0 Frags +
visitnigstop complaining, its not like you paid for this service

literally the name of my video

KalkinfosterApparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.This often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.

so if something like this is so widespread, why couldn't the match be rescheduled to a more appropriate time? maybe there was something i missed when our team captains were talking amongst themselves, but this seems like the perfect time to allow a match to happen at a later time. ideally when all 12 players can see each other in real time

[quote=visitnig]stop complaining, its not like you paid for this service[/quote]
literally the name of my video
[quote=Kalkin][quote=foster]Apparently it was a problem with most servers, just a bad day to play a match. Something to do with a CS:GO update or something messing with esea servers. Apparently a lot of people had trouble with crashing and not being able to get back in the server or just lag in general.[/quote]
This often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.[/quote]
so if something like this is so widespread, why couldn't the match be rescheduled to a more appropriate time? maybe there was something i missed when our team captains were talking amongst themselves, but this seems like the perfect time to allow a match to happen at a later time. ideally when all 12 players can see each other in real time
24
#24
0 Frags +

i delayed our match by 30-40 minutes the other day because every time i tried to join texas 307 hl2.exe would constantly crash

switching to a different texas server fixed the problem, is what i don't understand

i delayed our match by 30-40 minutes the other day because every time i tried to join texas 307 hl2.exe would constantly crash

switching to a different texas server fixed the problem, is what i don't understand
25
#25
0 Frags +
KalkinThis often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.

Would it be possible to get a heads up from ESEA in the future if this sort of work is incoming or is there not enough internal communication within ESEA for any sort of server status forecasting?

[quote=Kalkin]
This often is the case. Sometimes on huge update nights it ends up taking large amounts of server resources to update all of our CS servers. This unfortunately causes lag among the rest while we try to get stuff like CS:GO servers up to date while matches go on so we don't have to cancel all CS:GO matches completely. I do apologize for this happening; a CS:GO update was released late today that was likely the cause of the lag you were experiencing.[/quote]

Would it be possible to get a heads up from ESEA in the future if this sort of work is incoming or is there not enough internal communication within ESEA for any sort of server status forecasting?
26
#26
0 Frags +

Well valve doesn't exactly make sure that everyone is ok with the time at which they roll out updates, do they? Patches pretty much come out on a feel-like-it basis. Hard to predict server traffic based on this.

Well valve doesn't exactly make sure that everyone is ok with the time at which they roll out updates, do they? Patches pretty much come out on a feel-like-it basis. Hard to predict server traffic based on this.
27
#27
1 Frags +
PizzaWell valve doesn't exactly make sure that everyone is ok with the time at which they roll out updates, do they? Patches pretty much come out on a feel-like-it basis. Hard to predict server traffic based on this.

You're right that prediction is impossible, but even notification if there is ongoing trouble would be really helpful. ESEA has for instance a twitter that they could use to give notice if there is currently major technical work on specific servers. Right now it seems they're just posting links to CS frag vids. Actually a lot of the linked videos are to demonstrations of changes in updates in CS:GO which is a rather nice idea.

Ideally there could be another column in the ESEA client for each server giving the cpu load or whatever in the past 5 or 10 minutes as something like a green/yellow/red icon and a "state of the system" in the MOTD but I doubt they would ever go that far, especially given how much manual work by admins is required for switching servers on the fly. Maybe easier just to keep everyone in the dark.

[quote=Pizza]Well valve doesn't exactly make sure that everyone is ok with the time at which they roll out updates, do they? Patches pretty much come out on a feel-like-it basis. Hard to predict server traffic based on this.[/quote]
You're right that prediction is impossible, but even notification if there is ongoing trouble would be really helpful. ESEA has for instance a twitter that they could use to give notice if there is currently major technical work on specific servers. [s]Right now it seems they're just posting links to CS frag vids.[/s] Actually a lot of the linked videos are to demonstrations of changes in updates in CS:GO which is a rather nice idea.

Ideally there could be another column in the ESEA client for each server giving the cpu load or whatever in the past 5 or 10 minutes as something like a green/yellow/red icon and a "state of the system" in the MOTD but I doubt they would ever go that far, especially given how much manual work by admins is required for switching servers on the fly. Maybe easier just to keep everyone in the dark.
28
#28
0 Frags +

our server was laggy (like freezing every few minutes) on tuesday
wednesday had less freezing but still seemed very choppy/laggy

our server was laggy (like freezing every few minutes) on tuesday
wednesday had less freezing but still seemed very choppy/laggy
29
#29
0 Frags +

It always seems like the Texas ones are the worst when it comes to stuttering. Ours yesterday, I think 107, was like playing in a stop motion video. Also, get some more Chicago servers.

It always seems like the Texas ones are the worst when it comes to stuttering. Ours yesterday, I think 107, was like playing in a stop motion video. Also, get some more Chicago servers.
30
#30
0 Frags +

How are the ESEA servers set up? What data centers/networks/whatev in what cities?

You guys probably have your own boxes, so are there any that solely host TF2? If so, pls identify which servers are so blessed. If not, why not?

How are the ESEA servers set up? What data centers/networks/whatev in what cities?

You guys probably have your own boxes, so are there any that solely host TF2? If so, pls identify which servers are so blessed. If not, why not?
1 2
Please sign in through STEAM to post a comment.