Am I the only one that loves to listen to game design/programming lectures/keynotes in the background?

John Carmack: QuakeCon 2013 Keynote
John Carmack: Principles of Lighting and Rendering, QuakeCon 2013
John Carmack: QuakeCon 2012 Keynote
John Carmack: Oculus Connect 2014 Keynote
John Carmack: Mobile VR, GDC 2015
Steve Wozniak: Early Days of Apple
Steve Wozniak: Video Games
Steve Wozniak's Origins, 1984
Oculus Connect Keynote - These are all fantastic, just scroll down a couple of lines.

http://puu.sh/hbX1q/ab03befd43.png

TF2 framerates are mostly CPU bound. You'll get around the same, maybe slightly less.

please see this thread

I've never seen physics issue in Source from high framerates, though it happens in other engines. I believe this is because physics are tied to the tickrate rather than framerate, but correct me if I'm wrong.

If Steven brought attention to the issue, and he's definitely involved with the issue because he's played competitively many times since like 2009, people would listen. They fucking loved it when he ran Targe in 6s, I'm sure they'd listen.

I'm on 144Hz, but I'm not running dxlevel98 because I've heard of similar issues.

First thread debunks the suggestion from this thread that reinstalling fixes it. It doesn't. It then goes on to state that mat_hdr_level 2 might cause it; mine is at 0. That's the only helpful advice from this thread, besides someone saying changing configs helped them. I don't run configs.
Second thread gives no valid suggestions, because viewmodel_fov is now clamped to a valid range. In fact, that thread ends with further complaints that it's happening again and no fixes.

Wow many potential solutions, and literally all of these you could have determined don't apply to me because I posted my entire config.

Being able to use Google is not a replacement for common sense.

I'm pretty sure Steven has a much bigger and more passionate audience than Muselk, and the comp community thinks much more highly of him than Muselk.

Because Valve will literally ever support a mode that disallows certain items in their game.

It's not the meta, it's the whitelist. Supporting Arena: Respawn has a chance because of the lack of whitelist. An unmodified HL would be possible if they altered a few weapons. Current 6s just isn't feasible to be supported by Valve, because it bans SO MANY weapons that the casual player uses. By supporting gamemodes that ban 2/3 of the weapons in the game, Valve would basically be admitting they were wrong on so many accounts, and I just don't see that happening.

2500k is still one of the best singlethreaded CPUs out there.

Read the thread next time, that's not an issue.

I think it's probably something more to do with multicore optimizations. AMD was fine compared to Intel in the Phenom 2 days. FX CPUs are historically bad at single-threaded operations.

Remember, even DX11 is single threaded.

Can't help you. Issue with SweetFX, not with the game.

Essentially Source games all use hl2.exe (or mostly use, some don't) to launch their own games. Each game is actually a "mod", which has its own folder. For example, Portal uses "-game portal". TF2 just uses "tf". You were missing that argument so it tried to launch HL2, not TF2.

Are you running DX8? You might have issues with SweetFX if so.

Thanks for the upfront answer.

It's a wrapper.

Click the hl2.exe entry, hit the Game settings button, and under launch arguments, add

-game tf

at the very beginning.

tf/materials/console/background01.vtf
tf/materials/console/background01_widescreen.vtf

How are you launching the game through SweetFX?

How does SweetFX even launch? Does it use a wrapper, or d3d9.dll?