This isn't my exploit. My exploit requires no resolution altering, so paired with this you'd get an even higher FOV.

I'm away from my computer right now but I'll post pictures in a few hours.

I've actually played TF2 between 90 and 120 FOV. 120 is excessive and makes it hard to aim. I've found that 100-110 is optimal - whenever I have to go back to 90 it makes me vomit.

I think 100 would be a good compromise. 90 is just a little too low, but any higher and you'll compromise gameplay, like scouts and spies.

Source: I know an exploit that gives me anywhere from 90 to 120, user-selected, that can be performed even in sv_pure 2.

paging Phi

weight loss can be attributed to stress

and there's nothing more stressful than losing your first match in 5 years

now, does b4nny have an obese roommate and a German boyfriend? if so, b4nny confirmed tr4nny

i can't actually tell if this is real or not

but if it is

i would

they already did a 72 thread PC, so there's that

I'm currently in Hawaii so I can't really update it myself but if someone makes a pull request I'll approve it... it is on GitHub after all

yes but that's already been discussed earlier in that conversation chain, if you had decided to read

fact of the matter is that tf2 can run decently on almost any POS GPU from the past 5 years. single threaded CPU power is really what you need - that means it's better to buy an i5 from 2011 than to get a modern AMD CPU (at least until Zen), at least in regards to Source games.

http://pad3.whstatic.com/images/thumb/2/2c/Weaken-an-Enemy-on-Warcraft-3-Step-2.jpg/670px-Weaken-an-Enemy-on-Warcraft-3-Step-2.jpg

There's a difference between frame times and frame rate.

Frame rate is generally the average number of frames rendered per second. However, each frame might be slightly offset from the others. In an extreme case, let's say the first 50 frames take 10ms each. That's half of a second, and you've rendered 50 frames. However, then suddenly your CPU is heavily taxed, and the next 10 frames each take 50ms to render. You've rendered 60 frames in a full second, and the frame rate counter will display 60fps, but because of the huge gap in frame times, you're going to notice stutter. It won't look smooth.

My guess is that all of these old broken cvars caused horrible stuttering and unnecessary CPU stress, which in turn would increase frame time variance, decreasing smoothness.

what's broken besides main menu bg which i kind of like?

why has audio in tf2 become so horrible ever since the switch to mp3

i have to snd_restart almost every 10 minutes

obligatory "I work at Staples and we carry the G502 and can price match this, so you can drive by and pick it up"

http://puu.sh/lSdKj/ae66fc59da.png

http://puu.sh/lSdTQ/84ec59c212.png

http://puu.sh/lSesQ/72c95857ac.png

http://nicememewebsitewebsitewebsitewebsitewebsite.website/