you should put this in modules.cfg

alias decals decals_low
alias decals_art decals_art_on

Have you tried out the experimental version of mastercomfig? https://gist.github.com/mastercoms/a7eeb371ac2c066feb3e0d397b8086c7

Could you elaborate on what you mean by green adjustable numbers?

Completely placebo and your ping is from the nonsensical high rate

New version with more FPS improvements. https://gist.github.com/mastercoms/a7eeb371ac2c066feb3e0d397b8086c7

The two ways you can get a virus are through zero day exploits or being irresponsible.

You can't protect yourself against a targeted zero day besides keeping software up to date and anti-virus won't help.

And if you don't click on suspicious links, click random ads or trust any website and download whatever onto your PC, you'll be good.

New version of this experimental config! Some FPS improvements hopefully. https://gist.github.com/mastercoms/a7eeb371ac2c066feb3e0d397b8086c7

Updated this experimental config some more. Please let me know how it works for you! Feedback in all aspects would be extremely helpful: sound performance/latency, input lag, FPS, networking/hitreg, load times, stability/crashes!

https://cdn.discordapp.com/attachments/389091069091905546/560622029242368001/autoexec.cfg

If this one gets good feedback I'll create a more robust version soon.

It's upload and download. This is also why it says game traffic (two ways). Download is much more important than upload because it's not used as much in tbe engine for upload purposes.

Here's a very experimental config with some settings/values I want to test out. No presets, just experimenting with optimizations. It'll probably work best on modern PCs with GPUs though. Not sure.

Note that custom.cfg is now user/autoexec.cfg. Also rename your class configs back to not use _c.

https://cdn.discordapp.com/attachments/389091069091905546/560300691369754635/autoexec.cfg

Rate is what entirely dictates how much you receive/send per second to the server. However, having a bigger update rate or cmd rate than what it can reliably transfer will cause bad networking effects. So, reduce your cl_cmdrate and cl_updaterate (update packets are larger btw, around 600 to 3000 bytes, while client packets are around 90 to 200 bytes).

I would also set cl_smooth 1 and cl_smoothtime 0.1 as there's no reason to have it off.

Launch options, remove -nosrgb

r_worldlightmin 0.0002

thankss <3. i honestly could have gone more in depth on the other stuff but I'm glad you liked it!!

and I would be glad to hear about it. I'm no longer working on mastercomfig, but that doesn't mean I'm stopping work on TF2 configs.

I also recommend cl_smooth 1 and cl_smoothtime 0.06 to reduce client view position jitter when you get juggled or pushed by being in front the payload cart. The 0.06 comes from scientifically measured human tolerances for jitter.

Finally, probably the most important of the bunch is your rate settings. These were set in 2007 to 80,000 bytes per second, which was a reasonable value back then. However, since then, Internet speeds have gotten better and although CS:GO has updated its default rate to 196608, TF2 has stuck with that same old default rate. Also, TF2 usually delays packets sent to the server based on your rate, but you can resolve this by using net_maxcleartime 0.015, which means packets will never be delayed.

So, I recommend rate 196608; net_splitpacket_maxrate 196608;net_maxcleartime 0.015, or if you want something closer to the TF2 default, rate 100000; net_splitpacket_maxrate 100000;net_maxcleartime 0.015.