I'd be willing to bet that you're having the same exact issues that I was before I fixed my MBP.

MBP's come from the factory with a piss-poor application of thermal paste on the gpu and cpu cores. It's a common fact. If you want more documentation on this, simply search google using the keywords "2011 mbp thermal paste." You'll find several videos, discussions, forums etc all showing evidence of what over heating directly correlated to cpu and gpu temps.

My MBP's performance was steadily going down the tubes after a year of using it. For a while I though it was because of tf2 updates, but it was just a coincidence that the updates were happening around the time my performance was really starting to sink.

After a lot of research, trial and error, and much frustration, I finally noticed that my cpu was bottlenecking the shit out of itself every time I had tf2 running. I could alt+tab out of tf2, and my cpu's multiplier would jump back up to x31. As soon as I alt+tab back into tf2, the load of hl2.exe would force my cpu to go down to x8 to avoid overheating.

[TL;DR] This is a common issue and you have to apply a new coat of grease to your cpu and gpu core. See the thread I made a while back.

http://teamfortress.tv/forum/thread/8399/

and again, search google with the keywords: "2011 mbp thermal paste"

If you've never opened up your macbook pro and performed repairs like this before, feel free to add me on steam and I'll help you.

When I did this repair on my own MBP, I was nervous, as I had never done something like this on an Apple portable. With the right tools, research, patience, and caution, I fixed my MBP and made it run better than it did when it was new.

There have been at least 3 threads about playing tf2 on an Apple computer.

All of them ended with the consensus that installing windows via bootcamp is the absolute best option to get the maximum performance of your hardware to play tf2.

It's very simple. In OSX, go to applications - bootcamp assistant. Run the program, and it will walk you through the steps to install a windows partition. The only thing you need is a windows installation copy, and you can use a disk (the most reliable method) or you use an ISO on a usb stick or external storage device. So basically, if you have some sort of windows installation file available, you already have everything you need to do this, and boot camp assitant virtually does everything for you.

I added him a week or so ago. Already reviewed demos with him. No hard feels of course if you want to get more opinions though mixo. But the big thing is that his team needs to scrim more. I told him I'd like to sit in mumble during a scrim to hear comms but I don't think they've scrimmed since I added him.

wat

I should have tried harder to get on your roster when I was trying out for you guys after season 13. I would be playing main by now. Oh wait.

.

It wasn't as bad as it could have been. To be honest, if it weren't for all of this crap happening before, and up until the last match, we would have been a lot more frustrated and pissed off. We were basically worn down past our last nerve at this point though. But my team never once got angry with me about my connection. We all stayed calm and just pressed on as best we could. Shoutout to my teammates for being awesome and understanding. love you guys.

My ping was spiking to 800 and beyond on badlands. I made sure that no one in my house was using the Internet, but it was still spiking. We were about to get a ringer but then I had the idea of plugging straight into my modem. I did that, rejoined and it was fine for most of the duration of badlands.

On gravelpit, I started getting the auto disconnect in 20 seconds warning, and my choke would explode on my net graph. For the first round this was happening every 30-45 seconds. During the second and third round it started happening every 10-15 seconds. It just got worse and worse near the end. Every time it happened, I would also temporarily disconnect from Mumble. Many times when it would cease I would be in respawn.

We didn't pause because this is the second night in a row where we've had to deal with this shit. It was obvious it wasn't going to stop. We simply just wanted it all to be over with. We didn't want to lose, but we knew there wasn't much we could do. We're all happy that we can now take a breather and say gg, good season.

If anyone knows any possible way to get records from my isp, or my own computer, or verify that it was indeed a ddos, I'd be interested in finding that out. I personally think I was being attacked because this has never happened in any match, ever. Quite a pill to swallow to say it was just coincidence.

Yeah I was totally throwing. Definitely wasn't getting ddso'd. It was all me.

Surfing is helpful because it helps you condition your muscle memory. Air strafing, depth perception, and absolutely perfect and precise mouse movement are requirements for proficient surfing.

In gaining the ability to surf well, you will inherit great control of your player model, and test the limits of your mouse sensitivity and available space on the surface your mouse is on.

I think surfing is great. It takes time, practice, and patience though, and unfortunately surfing does not appeal to everyone. But if you do choose to surf and stick to it, you won't regret it.

More like a few simple things that would have had no impact whatsoever on the outcome of this match.

This particular attack was just the esea server itself. The players as individuals were not being ddos'd, rather the server we were playing on was.

If it was Bape, you could ban him from every server, site, irc, etc you could think of, but as long as he has an internet connection, he, like anyone else, could gather the resources to do this shit.

Also you can log into irc with +x mode, but that only prevents your ip from being shown when you join. It's extremely easy to get someones IP just for using irc in general, wether you autoconnect or not.

Basically, to sum this up, there's nothing simple about any of this. I think this could have been easier to deal with, but I think that only be taking preventative measures would that be true.

The fact is, this has happened in the past for open finals. As players who watch this game and should remember that, perhaps we are at fault for not speaking up and doing something about it.

As an organization/company who has fallen victim to this before, are they even more at fault for not being responsible and learning from the past? Honestly at this point I don't really care. Me and my team really want a break, we want to win our measly sum of prize money, go enjoy whatever left we have after paying our fees, and then go take some time off to relax. I just want ESEA to fucking fix this shit so that can happen.

It wasn't the players.

If someone wants to actually ddos they're going to do it. Having the capability to prevent such an attack is what will prevent it from happening, and thus prevent "potential" ddos'ers from gaining interest.

We have two people on our team who just moved into college this week and barely have their belongings set up, this is the only day that we could make this happen. And the worst part, is that they're trying to make us reschedule this.

This is extremely inconvenient and frustrating for us, because we absolutely have little to no other time in the next several days that we can play this match again.

So, let's say we somehow manage to find a day in a reasonable timeframe to play again; what's stopping this from happening tomorrow? Or the next day? Or the day after that?

Who knows how long this could keep going. Bottom line is ESEA needs to figure out a way to prevent this from happening, or it will just keep happening.

I was pug scrimming with tictac the other day and he said he was playing in invite s15 - I believe he said with solace?

I'm just relaying to you guys what I heard straight from the dude.

I'm actually not the biggest fan of swiftkey mmyself. I really like perfect keyboard pro but Google keyboard is indeed pretty good. I just wish perfect keyboard had swipe input.