blinKTheManWithNoNameCabinetSo is this match being re-scheduled or is it a default win for Quantum Flux?
for all the issues that ESEA has, at least they do not (as far as we know?) threaten to give a team a FFW in the grand finals...
We could've ffw'd, but decided to wait instead.
you can't get a FFW in post season the normal way. Killing would have had to do the FFW manually in order for it to happen anyway. I think everyone wanted to see this match.
And hey if some bros can't hang on thursday i'm still down to cast this for whoever.
[quote=blinK][quote=TheManWithNoName][quote=Cabinet]So is this match being re-scheduled or is it a default win for Quantum Flux?[/quote]
for all the issues that ESEA has, at least they do not (as far as we know?) threaten to give a team a FFW in the grand finals...[/quote]
We could've ffw'd, but decided to wait instead.[/quote]
you can't get a FFW in post season the normal way. Killing would have had to do the FFW manually in order for it to happen anyway. I think everyone wanted to see this match.
And hey if some bros can't hang on thursday i'm still down to cast this for whoever.
rr has more irl fov than you
rr has more irl fov than you
No london it was very clear that we could have forfeited. We didn't think it would've taken that long to get things going so we wanted to just wait. I guess everything happened for a reason though so we'll just play Thursday. In post season you cannot ffw through the chat commands, however after 30 minutes I could msg Killing and ask for a ffw that way and he would've done it. Doesn't matter now though. I'd personally rather play it's just tough working through peoples schedules since our team is generally older than most others. Some married with children and such.
No london it was very clear that we could have forfeited. We didn't think it would've taken that long to get things going so we wanted to just wait. I guess everything happened for a reason though so we'll just play Thursday. In post season you cannot ffw through the chat commands, however after 30 minutes I could msg Killing and ask for a ffw that way and he would've done it. Doesn't matter now though. I'd personally rather play it's just tough working through peoples schedules since our team is generally older than most others. Some married with children and such.
london_callingyou can't get a FFW in post season the normal way. Killing would have had to do the FFW manually.
blinKNo london.........In post season you cannot ffw through the chat commands, however after 30 minutes I could msg Killing and ask for a ffw that way and he would've done it.
???
[quote=london_calling]
you can't get a FFW in post season the normal way. Killing would have had to do the FFW manually.[/quote]
[quote=blinK]No london.........In post season you cannot ffw through the chat commands, however after 30 minutes I could msg Killing and ask for a ffw that way and he would've done it. [/quote]
???
He read half of the post probably.
He read half of the post probably.
For future reference here are the instructions I received after submitting a ticket:
1. Go through this f.a.q and make sure you did the following suggestions ( it is important that you read this VERY carefully ), http://play.esea.net/index.php?s=support&d=faq&id=108
2. If you are still having an issue it may come down to the fact that your game may have a file or setting that is causing the issue to take place. To determine this do these steps exactly as i have written them below.
Delete the entire game folder located within your steam folder by going to your steam folder directly which should be located at c:/program files/steam/steamapps/common and then deleting the entire game folder ( DO NOT JUST DELETE THE LOCAL CONTENT ). Only save your maps folder to your desktop or any other location and do not install any gui/custom config until it works correctly. After that is done right click on your game in your steam games library and delete the local content ( if it is still present ).
*******STOP*****
If the above steps did not work then move on to step three.
3. Fully uninstall your anti virus software or any other security program you have on your computer ( temporarily of course ) so that we can eliminate that from causing the issue. Sometimes when you add an exception or even disable the software it can still cause an issue just from being on your computer and normally that is what will stop the client from being able to work properly.
As soon as you uninstall your security programs then download and install a fresh copy of the ESEA client, be sure to delete the entire ESEA folder from your program files folder after you uninstall the ESEA client before you install the new ESEA client.
Download a fresh copy of the client from here:
http://esea.net/index.php?s=downloads&am...
None of this worked for me
I remember the clientregistry.blob thing from back in the day when we were trying to figure out client errors, so I tried it before messing with anything else. Same thing happened, client would just crash ~30 seconds after launching tf2. Lange murdered my anti virus(MSE) last night via Team Viewer and it wasn't cockblocking anything. I hadn't changed a thing in my tf2 files since our most recent match so I wanted to try other shit before reinstalling. Fearmie suggested that I do a system restore to a few days ago and I looked at the restore points and they were for windows updates, and the mumble update to 1.2.4 that I installed for tf2center. I restored to before mumble update and now the client works fine. I'm assuming this was the issue since the client has some built in mumble stuff.
For future reference here are the instructions I received after submitting a ticket:
1. Go through this f.a.q and make sure you did the following suggestions ( it is important that you read this VERY carefully ), http://play.esea.net/index.php?s=support&d=faq&id=108
2. If you are still having an issue it may come down to the fact that your game may have a file or setting that is causing the issue to take place. To determine this do these steps exactly as i have written them below.
Delete the entire game folder located within your steam folder by going to your steam folder directly which should be located at c:/program files/steam/steamapps/common and then deleting the entire game folder ( DO NOT JUST DELETE THE LOCAL CONTENT ). Only save your maps folder to your desktop or any other location and do not install any gui/custom config until it works correctly. After that is done right click on your game in your steam games library and delete the local content ( if it is still present ).
*******STOP*****
If the above steps did not work then move on to step three.
3. Fully uninstall your anti virus software or any other security program you have on your computer ( temporarily of course ) so that we can eliminate that from causing the issue. Sometimes when you add an exception or even disable the software it can still cause an issue just from being on your computer and normally that is what will stop the client from being able to work properly.
As soon as you uninstall your security programs then download and install a fresh copy of the ESEA client, be sure to delete the entire ESEA folder from your program files folder after you uninstall the ESEA client before you install the new ESEA client.
Download a fresh copy of the client from here:
http://esea.net/index.php?s=downloads&am...
[b]None of this worked for me[/b]
I remember the clientregistry.blob thing from back in the day when we were trying to figure out client errors, so I tried it before messing with anything else. Same thing happened, client would just crash ~30 seconds after launching tf2. Lange murdered my anti virus(MSE) last night via Team Viewer and it wasn't cockblocking anything. I hadn't changed a thing in my tf2 files since our most recent match so I wanted to try other shit before reinstalling. Fearmie suggested that I do a system restore to a few days ago and I looked at the restore points and they were for windows updates, and the mumble update to 1.2.4 that I installed for tf2center. I restored to before mumble update and now the client works fine. I'm assuming this was the issue since the client has some built in mumble stuff.
That's pretty interesting Sean, and good for future reference. I feel like I played my last ESEA match with 1.2.4 though, but I don't remember clearly.
That's pretty interesting Sean, and good for future reference. I feel like I played my last ESEA match with 1.2.4 though, but I don't remember clearly.
a forfeit win would be a pretty fitting end to this season
a forfeit win would be a pretty fitting end to this season
Match tentatively set for 10:30pm tonight
Thanks again to TFTV, the casters, and most importantly the viewers for sticking it out so long the other night. We didn't want to put on a match with backups, or 5v6 unless absolutely necessary. No one was expecting problems to that extent, hopefully tonight goes smoother.
Match tentatively set for 10:30pm tonight
Thanks again to TFTV, the casters, and most importantly the viewers for sticking it out so long the other night. We didn't want to put on a match with backups, or 5v6 unless absolutely necessary. No one was expecting problems to that extent, hopefully tonight goes smoother.
seanbudFearmie suggested that I do a system restore to a few days ago and I looked at the restore points and they were for windows updates, and the mumble update to 1.2.4 that I installed for tf2center. I restored to before mumble update and now the client works fine. I'm assuming this was the issue since the client has some built in mumble stuff.
1.2.4 was released months ago, maybe you updated from 1.2.3 to 1.2.5 which was only a few days ago?
http://mumble.sourceforge.net/1.2.5
[quote=seanbud]Fearmie suggested that I do a system restore to a few days ago and I looked at the restore points and they were for windows updates, and the mumble update to 1.2.4 that I installed for tf2center. I restored to before mumble update and now the client works fine. I'm assuming this was the issue since the client has some built in mumble stuff.[/quote]
1.2.4 was released months ago, maybe you updated from 1.2.3 to 1.2.5 which was only a few days ago?
http://mumble.sourceforge.net/1.2.5
should be a good watch
Show Content
if it doesn't get DDOS'd
should be a good watch
[spoiler]if it doesn't get DDOS'd[/spoiler]
Thanks for the shoutie, mate.
Thanks for the shoutie, mate.
-Sal: http://youtu.be/jskQlmd8-TM?t=1m14s
very close main match gg both teams
very close main match gg both teams
yeah cosa thats exactly what happened
yeah cosa thats exactly what happened
congrats to star and whisker, for your first season of open you guys did a great job playing at such a high level.
congrats to star and whisker, for your first season of open you guys did a great job playing at such a high level.
g_Ron_Paulwhat an embarrassment
if coach had put you in 4th quarter things would be different
[quote=g_Ron_Paul]what an embarrassment[/quote]
if coach had put you in 4th quarter things would be different
powah needs to see a chiropractor
powah needs to see a chiropractor
i hope it was entertaining to watch, great season, gg
i hope it was entertaining to watch, great season, gg
[img]http://i.imgur.com/BD9cf8H.gif[/img]
Ragorismg_Ron_Paulwhat an embarrassment
take your salt elsewhere
honestly I dont even care about -frags. Both these teams took away spots from teams who worked harder and deserved it more.
[quote=Ragorism][quote=g_Ron_Paul]what an embarrassment[/quote]
take your salt elsewhere[/quote]
honestly I dont even care about -frags. Both these teams took away spots from teams who worked harder and deserved it more.
http://teamfortress.tv/forum/thread/11954-open-to-hrg-legend-of-indust/4#post-95
gg's! badlands was intense as hell. congrats to the buds
gg's! badlands was intense as hell. congrats to the buds