I know it's been a while, but I've gone ahead and updated my config, finally. There hasn't really been a need for it, since there's been no real new discoveries about what could be added, removed, or changed. However, following the issue with mat_antialias causing crashes, I changed it in my config to prevent that.

While doing that, I also decided to remove cl_loadondemand_default (since it no longer exists in the game), and I also updated the auto-updater. I noticed that it wasn't working due to a stupid mistake on my part. I made some changes to improve reliability and it now checks if the OS is 32-bit or 64-bit and installs to the correct path without any modifications. For the people with a non-default installation path, use updater-legacy.bat and change the path there instead.

Have any suggestions or issues? I check back here every once in a while, but not as often as I could. If you really want to get my attention, add me on Steam, or post an issue on the github, since I get notifications for that. Thanks.

r_occlusion 0 // disables ambient occlusion. 2% FPS boost

sys_minidumpspewlines 500 // Basically the number of lines saved to a log file from console. No FPS boost but 15% lower FPS variance

mat_antialias 0
mat_forceaniso 0

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

mat_max_worldmesh_vertices 512

Updated my config too, thanks for the info!

Just because I'm curious, what exactly do you feel I messed up with in my config? And is it fixed now?

Yeah, that's bad knowledge that got passed around, apparently... Thanks for telling me.

*snip*

Are you using experimental features with a processor that has less than 4 cores?

This is an issue introduced by Valve's scripting system, wherein host_writeconfig doesn't actually save the changes properly. You can get around this by creating a file called autoexec2.cfg in your cfg folder and putting the rpc_ commands in that file. This makes it so that they launch every time that the game starts, since I recently added a line to my config to execute autoexec2.cfg if it's present, specifically for this.

Someone suggested that you uncomment what you want to use, but I highly suggest you use this method so that you don't have to edit the config manually and can keep the auto-updater running without issues.

Actually, they're no longer scattered throughout the config! I recently organized them, so they're all at the bottom of the config in the same area.

mat_shadowstate 1					// Set to 1 to enable.
r_shadowmaxrendered 11			// Set to 11 to enable.
r_shadowrendertotexture 1			// Set to 1 to enable, but can cause lag; 0 is the recommended setting either way.
r_shadows 1						// Set to 1 to enable.
nb_shadow_dist 400				// Distance from which shadows are visible. Uncomment to modify.

Check if there's a notable difference with the default settings that would be there without the config. The game tells you the default if you type in the convar name without specifying a value.

Does the CPU have four physical cores or are two of them hyperthreaded? Also make sure cl_threaded_client_leaf_system is set to 0.

If you continue to crash, I recommend giving this config a try and going through the in-game setup and enabling the experimental settings (or AMD-compatible settings if you have an AMD CPU). Do you still end up crashing?

The config has been updated and now matches performance with Comanglia's config as long as you enable rpc_experimental_on. Note that if you don't have four cores, you might crash when using experimental mode.

I'd like to point out that I don't check this thread out too often anymore, since this is really the only thing I do on tf.tv. If you want to report issues and make sure they're solved ASAP, I would suggest posting them on my github page instead.

On that note, I've made various improvements to my config, such as adding an automatic updater so that you're always at the latest version. If you want a full changelog, you can view it here.

New update is out, I commented host_thread_mode since people were having issues with it in some situations. If you're still experiencing issues, set it to 0 by typing 'host_thread_mode 0' in console.

This has been happening to numerous people, but not others, and I don't know how to reproduce it. All I can recommend for the time being is to put the commands you want to use at the very bottom of autoexec.cfg so that they run on each launch.

I didn't either, it looks like it binds itself to an unbinded key on startup. I'll move the F7 bind in a future version to use a different key so that it doesn't do that.

If you don't have a four-core CPU then your game will be unstable due to some of the convars in this config, and you'd be better off running my config instead since I commented out those convars on mine. Both configs provide similar FPS gain since Comanglia and I are working together on it.

Under most circumstances they don't, unless they're whitelisted. While most servers don't do this, communities like Firepowered do, and we could askaround. It's an FPS improvement in general, anyhow, so I might as well do it.

So, here's the current state of things. Comanglia and I have been working together with other people in his FPS config thread to find out what convars we can still use to make an FPS benefit. As far as we can tell, there's a potential that we're either missing some beneficial convars, or we've hit a wall and can't optimize TF2 this way any longer. That being said, I decided to fool around with the particle editor and see how it works, and you know what? It turns out that I can get my way around it extremely easily.

In other words, once I feel like getting around to it, I'll probably optimize all of the TF2 particles to be less intensive in one way or another and release it. The reason I feel like doing this myself instead of recommending another pack is because of the fact that most other packs seem to be outdated, and not optimizing new particles. Further, you can pack multiple particles into one .pcf; if Valve adds a new particle to a pcf file, that particle won't be able to be seen if you use a pack that isn't updated. I want to make a pack that WILL stay updated.