4.5.6 released with documentation improvements, file cleanup and a party bug fix.

Also thank you for 100 frags!!! woooo

Hi, just enter host_thread_mode 0 into console, and host_thread_mode 1 when you're done in your local server.

(as said in the troubleshooting wiki page, in a comment at the top of the config and printed to console.)

Could I get some advice on where else to put it?

If you have Linux, you might want to use cake or fq_codel on your PC to have better traffic shaping at the OS level as well.

Change mat_dxlevel in the init section of comfig.cfg.

EDIT: ninja'd. curse you slow internet!

You can't selectively change texture quality. If you want decent looking war paints, you will have to use mat_picmip 0.

Just add that to a new custom.cfg and uncomment exec custom in comfig.cfg and you should be good to go.

I'm sorry but I have to correct yttrium a bit.

-high improves responsiveness with better preemption and execution of tasks. It helps even with just background processes. However, these benefits depend on the CPU.

It saves a bit of memory and decreases startup time by preventing the joystick system from starting. It still works, you can check this by comparing the stdout output from TF2 when -nojoy is present and removed.

No, this tells TF2 how many worker threads are available for tasks. TF2's automatic detection for worker thread count is limited to 3 threads, so -threads allows you to force a higher count.

But some people have problems with raw input, so it is still useful for those with raw input disabled.

The whole mastercomfig folder should go in tf/custom.

Well, what are your net settings?

<3 i'm so glad to hear it's working well for you!

Well, it depends on your CPU, but usually balanced core usage uses less power so I would continue using mat_queue_mode 2.

I've now changed the documentation for this command to be more clear.

Sorry I missed this. Not sure, maybe mat_picmip 0 or r_rootlod 0. If not, I'll have to test.

4.5.5 released with better dxlevel control, improved comments/formatting and pyrovision optimizations.

Autoexec gets automatically executed on launch, hence the name. If you add +exec autoexec.cfg, you run your autoexec twice.

I couldn't find anything that would cause it for sure, but you can try removing cl_forcepreload and sv_forcepreload. Also, you have 2 maps for preloading being loaded in your config, as well as one being loaded in your launch options. Try removing those, they might be preloading too many resources.

Also a bit unrelated but you should be executing the comfig file first and then the presets.

Remove -noipx -nocrashdialog -noborder -heapsize -fullscreen and +exec autoexec.cfg

Sure, mediafire works.

What is your OS, launch options and config?

What's your OS?

Also, sorry for the plug but mastercomfig has some optimizations that will improve load times. http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config

Yes, Linux's network system isn't bad and doesn't require the additional queue. Most of it is already disabled for Linux users, but disabling it and adding the launch option will save memory and a little bit of CPU.

r_dopixelvisibility does occlusion for glows, and building_cubemaps 1 removes most of the negative performance impact from enabling it, so I think it is a net positive.