mat_antialias 0
mat_forceaniso 0

pConfig->m_nForceAnisotropicLevel = max( mat_forceaniso.GetInt(), 1 );

Because the values of these cvars are loaded as part of the material system config that is stored in the registry. They arent loaded and stored like normal cvars.

Specific to this discussion, a single thread allows (at most) 100% usage of a single logical core of a cpu. The equivalent load may be spread out over multiple logical cores due to windows, however.

Whether or not you agree with the rest of MasterNoob's post, I think it's impossible to deny how right he is about the current alternatives to tf2center being discussed are being created because people are angry. Let's face it, these things do not mature or even become usable overnight, and if you really are serious about creating an alternative to tf2center and marketing it so people actually use it, you're going to need a lot more than a few months.

That's pretty much just 3 threads of actual usage spread out over 8 logical cores.

Let me know when there's a good alternative to tf2center. Until then, I'll keep using whichever service works best.

This will make alt tabbing very slow. Set mat_antialias and mat_forceaniso to 1 in your config and *make sure there are no duplicate entries of this cvar in any of your configs*

Not exactly. If you were producing frames every 5ms (200 fps) then suddenly dropped to producing them every 6.6ms (150 fps), the delay between the two different frame rates would be 6.6ms. Example:

..... 5ms | 5ms | 5ms | 6.6ms | 6.6ms | 6.6ms .....

With the pipes representing frame draws.

What kind of errors are you getting?

Is your console being spammed by errors?

Nope.

You need to create a vmt for your vtf.

Can you please add to the first post how non-zero numbers on the scoreboard turn green? I'm aware it's not a bug technically, but the loss of customization caused by the pointlessly hardcoded feature its disgusting.

iirc the option won't appear unless you are running at the resolution you wish to apply the settings to. Set your desktop to your ingame resolution, look for the settings and change them, then set your desktop resolution back to native. The settings should then apply ingame when you use that resolution.

Screenshot?

Because in your case, you were very close to completely filling up the vram on your card. The addition of the few skins textures needing to be loaded caused your game to try using more vram than you actually had, meaning that every frame your driver now needed to start swapping out data to system ram.

For example, if you had 1024MB of vram and you were using 1023MB before the update, you would have 100% performance. Now that there are a couple more textures because of skins, you're using 1124MB, and that extra 100MB has to be exchanged with data in system ram every frame, which might limit you to somewhere around 50% performance.

That's why this isn't a bug with this update. It just so happened that you were super close to using up all available vram on your card, and the few more skins from this update pushed *you* over your vram limit. If someone out there has a Titan Z with 12GB of vram, they'll likely never use all that up in tf2 (cvars be damned). If someone only had 512MB of vram, they would have already gotten poor performance before this update when using mat_compressedtextures 0.

Your detective skills are right, that's pretty much bullshit. Even when I only had a 60hz monitor, I could still easily tell a difference between fps_max 150 and fps_max 300.

I use fps_max 150 when it's too hot in my room, but there are no hard and fast "best" values for this cvar really.