These instructions are only for Linux systems.
Use either the
ondemand governors when playing TF2 by using
cpupower frequency-set -g performance, for example. You can see available governors for your CPU with
GameMode is a handy utility released by Feral Interactive, which will change the CPU Governor from the default cpu governer to
performance. Recent updates allow it to change a games’ “nice priority”, which will give the game more resources to work with.
Balance IRQ interrupts across multiple cores by installing the
irqbalance package on your distro and enabling the
irqbalance service. This package is installed on most debian-based OS’s by default, like Ubuntu and Linux Mint.
You can install
schedtool and Ananicy and enable the
ananicy to get automatically applied ruled based process priority balancing to improve resources allocated to TF2.
See the Arch Linux wiki for information about improving networking parameters for performance.
Virtual memory optimization¶
See the Arch Linux wiki for information about improving virtual memory parameters.
While unlikely, it is unknown whether using native libraries is safe to do due to VAC (Valve Anti-Cheat). Continue at your own risk of having your account VAC banned, which is a permanent, non-negotiable ban that removes access to your inventory and prevents you from connecting to VAC-secured servers.
This has nothing to do with mastercomfig. mastercomfig is safe, and will not get you VAC banned.
Disabling the Steam runtime using through command line variables is not enough to use native libraries on TF2 as the TF2 launcher script shades in some libraries.
TF2_FOLDER/bin and delete
libtcmalloc_minimal.so.4. Now, Team Fortress 2 will not be able to load these libraries. The system will have to provide them, so make sure you have the 32-bit/multilib versions of
It’s unknown if you can be VAC banned for this, but it is modifying libraries, which should be restricted by VAC. So, do it at your own risk. I am not responsible for any VAC bans you may receive.
Disabling shader compilation on start¶
Although this config does allow for greater memory usage for the shader linking that is run when the game launches, and removes outdated shader listings, some of you may not want to wait at all for the shaders to self-compile (particularly if you’re running an older graphics card circa ~2009) because the device may not allow for it in a suitable amount of time.
Disabling the shader linking will decrease performance and will increase stutters as shaders are loaded on demand, or in some cases, they may not work at all.
However, for long game runs, having shader linking disabled will result in better performance over a longer period of time, since useless shaders will never have to be loaded into memory.
To disable this shader process, simply make two empty files:
glshaders.cfg, then put them in
You can also disable Steam’s shader pre-caching, which downloads shaders that match your hardware configuration. To disable this option go to
Steam > Settings > Shader Pre-Caching and Uncheck “Enable Shader Pre-Caching”.
To re-enable the shader process, simply delete