Specifically, I've taken some optimization convars from Stabby's config, added snd_mixahead (to make noises not be delayed as much), and studio_queue_mode 0 (although it's commented, since on some machines it can cause crashes if not set to 1, although it does provide a small FPS boost).

I've also added some security features that prevent commands such as unbindall, closed_htmlpage, sndplaydelay, playgamesound, and soundfade from being used by abusive server owners.

I plan to add more whenever I find anything useful, and fix any reported issue. If you want to be aware of updates, you'd probably want to follow my github repo.

I didn't originally, but if there's interest, I'll do it for highframes and maxframes, I suppose. I'll have to compare the original ones to dx9frames and see what specifically changed, though, so I know what to do. I'll probably get to work on them tomorrow; I've been working on this for about six hours straight now (not counting the time I spent on it the night before), so I think I need to take a break.

Thanks!

I've provided this functionality on the project page for people that wanted to do that, but regardless, thanks for linking it (I know it sounds spiteful, but it's not, I swear).

The null movement config isn't commented out because I didn't add the ability to toggle it on and off in this release. I'll do that shortly, if you'd like.

If you want to get right into it, you can view info about and download the config here.

Rhapsody's Performance Config
Making Team Fortress 2 faster since 2014

What it is
Rhapsody's Performance Config is a project intended to supercede Chris' dx9frames config, and be superior in every way. Since Chris' configs were abandoned, this one is the better choice, being that it's active and is updated with more convars that increase performance. Alongside that, it's documented much more thoroughly than Chris' was, and is avaliable in the file for anyone interested.

This config uses Chris' dx9frames as a base, but is completely re-organized in a neater fashion, and is much more user-friendy and intuitive. Everything but the core changes are mentioned and configurable in an in-game wizard, allowing you to choose things as you want them. These changes are saved between sessions thanks to the magic of host_writeconfig, as well, so you'd only need to actually edit the config if you're an advanced user and want even more control.

How to use
In order to use this config, you first have to download it. You can do this going to the project site and pressing one of the two buttons at the top; either Raw Text or ZIP. If you download it as a ZIP, then all you have to do is extract the archive and find autoexec.cfg. Once you do, just go to the following filepath, and place it there.

C:\Program Files (x86)\Steam\SteamApps\common\Team Fortress 2\tf\cfg

or if that doesn't work, go to

C:\Program Files\Steam\SteamApps\common\Team Fortress 2\tf\cfg

For Mac:

Users/UserName/Library/Application Support/Steam/SteamApps/common/Team Fortress 2/tf/cfg

For Linux:

/.steam/SteamApps/common/Team Fortress 2/tf/cfg

After you do that, just start up your game and type 'setup' in console, and you'll be good to go.

If you chose Raw Text, then just go to the filepath stated above, copy the text from the browser window, and paste it into your autoexec.cfg file. If you don't have an autoexec.cfg file, then create it.

What's Next

• Add a toggle for null movement.
  
• Make a version for highframes and maxframes.

I added that myself as a temporary notification that this problem exists.

I'm trying to make an efficient and sorted autoexec.cfg using various elements from both Stabby's and Chris' config, along with a few others. The main problem that I have with this, however, is that whenever I set my launch options to -dxlevel 95, open the game, and then change my options back to their lower values in Options > Graphics, the DirectX level tends to revert to DirectX 9 or even DirectX 8 in some cases, ruining the entire point of this. This means that one or more of the convars in this config are messing with mat_dxlevel as a result of being changed. Technically, I could always add mat_dxlevel 95 to my config at the very end, but this occasionally resets the Graphics options and isn't worth the trouble. What convars might be causing this issue?

You can find my config here; it's long enough that I can't post it in the forum without it cutting off.

EDIT: Just noticed this might be better fit for TF2 Help. Can a moderator please move it?