Hey guys, today I would like to officially announce that mastercomfig specifically is cancelled. I have some exciting plans in the future to provide a much more useful service that encompasses all that mastercomfig provides, and more. I'm currently in the planning stages for this idea, but it will allow me to be less reliant on TF2 specifically and also give much more benefits than just some value tweaking. It will also make updates less dependent on me and use the power of the community.

Put your preferred net settings in custom.cfg.

To think I admired Sketchek at one point. Gosh, I thought you were brave, trying to make a bold statement about video games and the sanctity of life. But no, you're just a coward. You lied to all of us just so you could lay low for a little while, reaping the rewards of our misguided kindness and love towards you. And now you have the audacity to come back like this. I won't hate on you for admitting to it, but you should have never done this in the first place and that's what I'm angry about. However, in revealing your lie, you showed no empathy or even a slight bit of consideration to our pain, so I don't even know what to think about your announcement. Did you really think you could laugh it off with all of us? Do you have no shame or dignity?

EDIT: I appreciate your genuine and heartfelt apology. I understand you made a bad choice and although I can't fully accept your apology at this moment because of how extreme and horrible your lie was, I'm glad you're making steps to improve yourself and get yourself back on track.

Try resetting your mastercomfig settings within the settings page.

0 gets rounded up to 1.

Try opening regedit, HKEY_CURRENT_USER\Software\Valve\Source\tf\Settings, then remove mat_antialias.

Not noticeably.

https://docs.microsoft.com/en-us/windows/desktop/WinProg64/performance-and-memory-consumption

I took their language to mean that they reserve the right to release a Heavy update in the future, and that just because Heavy lost doesn't mean they will never ever update Heavy again. But other people took it to mean that they were confirmed the Heavy update coming after the Pyro update, which I don't think is valid.

You can review what's in the file on GitHub, but I would recommend using tf/cfg/custom.cfg for your own stuff. This way, your config doesn't break every time mastercomfig updates, and you can be sure that your stuff runs last and gets set to what you want. It also is more efficient, especially if you use modules.

In exclusive fullscreen mode, it won't really affect performance (maybe a frame or two), but it will make Windows snappier.

66.

66.67 is useless because update rate clamps down to an integer (no decimal places). 67 is doubly useless because sv_maxupdaterate is 66 on pretty much any server. However, on servers where this is not the case, update rate is limited by the tick rate of the server (1/0.015). You might thinking you should use it then, but no, because since client side, it is still at 67, which messes up network timings when it being considered to be at (1/0.015) on the server, but 67 on the client.

dxlevel 10 in the orange box source engine means that it ignores dxsupport

so this mod is just pepega

Delete %appdata%\mastercomfig-app\Comfig to reset the cache

Did you modify the VPK? Seems like its corrupted.

The problem I have with configs like this is that console variables aren't going to change from config to config. It's the same game/engine, reading the same console variables. So there's going to be ideal values for those variables that everyone will eventually find (besides the ones that control quality vs. performance tradeoffs). That means configs can only be distinct in their usage, like how Rhapsody's Config has aliases or how mastercomfig has a modular design/app.

If effort is just being made to find the right values, rather than make the config's usage different, then I think it would be best to build off of someone else's work and collaborate.

Hey guys, just wanted to give a quick update on mastercomfig. I will not be updating this config until Valve releases any information about the next major update (or releases the update). There's just a bunch of uncertainty in the investment I have to make to update the config, because everything could change in the next update and we just don't know what's going on in general.

Don't use this, it's broken and unmaintained at the moment, unfortunately.

I could calculate the rates manually myself. niko, could you tell me your up/down speeds?

These files were moved to the app folder. But you shouldn't be messing with them anyways, you can use tf/cfg/custom.cfg and tf/cfg/modules.cfg to override the app.

are you using mastercomfig very low? that disables a bunch of hud elements