What's a wallbug?

Seems like pretty much all glaring performance problems should be fixed by the next release (though please let me know if you still have issues, especially on low end hardware). I'd like to some help prioritizing future tasks so let me know:

What things would you like from Jungle Inferno and later?
What features/fixes would you like from CS:GO's engine?
What TF bugs would you like fixed? (excluding le demo det fix meme, I'm already certainly aware)

For those of you who have given feedback already, thank you, I'm investigating most of what you all have mentioned already!

@mlns r_worldlightmin 0.0002

@Chris_ if you download a new preset you have to delete the old one. For example if you have mastercomfig-low-preset , you can delete that one and download mastercomfig-medium-preset for example. If you are using the pre_comfig approach you don't have to download anything.

hud_panels=on in modules.cfg

Team Comtress 0.0.5

Hopefully fixed sound issues for everyone!

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.5

You can either download a new preset, or if you want to switch presets on the fly, use the documented way of doing this.

Team Comtress 0.0.4

Should be much easier to install now!

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.4

Glad to see your interest, twiikuu! I'm open to anyone hosting servers for this, so I really appreciate your offer! Having multiplayer games for this stuff will really enhance the testing we can do.

As for the quality of life fixes in game, I think that's a wonderful idea and we can probably make more powerful/more stable fixes to the game instead of using Sourcemod hacks.

I looked at CS:GO for the basis of these networking default changes. I feel like I should be more conservative when it comes to these defaults.

Team Comtress v0.0.3

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.3

no just for fun

0.0.2

https://github.com/mastercomfig/team-comtress-2/releases/tag/0.0.2

I mean, a lot of this stuff is not very well tested. So I would understand if they would be uncomfortable to include it.

If anyone is curious, this is because DX9 should be a more efficient renderer, except for the lower quality settings only available on DX8. I'm looking to add options to enable these reduced graphics options, and along with the general performance improvements, DX8 shouldn't be needed anymore and can be stripped out for even greater performance.

only if we give the double jump to spy

Team Comtress 2

What is Team Comtress 2? It's a version of Team Fortress 2, based on the recent leak which aims to fix many bugs, performance issues, etc. Imagine it like mastercomfig on steroids!

Obviously, as a leaked build, it's not useful for getting better performance in Casual on its own (you can't use this build to connect to any existing servers), but it can help me a lot if you all can test it, so that I am more confident in sending many of these changes to Valve for them to include in the base game! Please let me know how it works for you!

Download

Remove the commands for transparent viewmodels from your autoexec, and add the mastercomfig transparent viewmodels addon to custom. Don't put VPKs in a separate folder in custom. They must be directly in custom to work.

Add this to your autoexec:

unbind w
unbind a
unbind s
unbind d

bind UPARROW +mf
bind LEFTARROW +ml
bind DOWNARROW +mb
bind RIGHTARROW +mr

The bind won't appear in the keyboard menu since it is not the default movement binding.

Generally, think of mastercomfig in "layers" rather than things you need to edit directly. You edit things by overriding things in your user "layer". Your user layer consists of a user modules layer, autoexec layer, game overrides layer, and class config layer. Modules override mastercomfig/preset modules layer. Autoexec layer overrides mastercomfig/addons layer. Game overrides layer overrides mastercomfig game overrides (run on game join/every time you change class), and per-class networking settings, for all classes. Class config layer overrides mastercomfig game overrides (class configs run after game overrides) and per-class networking settings, for a single class.

This layered approach means that the config's settings are more managed (i.e. most things are done for you, with you just changing a few things based on your own preference, so that settings don't conflict for best possible stability and performance), and contained (you can easily drop in a new version of mastercomfig, and your layers will remain in your user folder, so you don't have to re-edit anything whenever you change a version).