Linux does have VAC.

brutus has notoriously good aim. i'd love to see him fight a catbot.

I would recommend setting this on clients and on the server:

net_maxcleartime 0.001
net_compresspackets 0
net_maxroutable 1260

Though, net_maxcleartime will increase net usage some if you use it on the server, so if you aren't comfortable with doing that. Furthermore, I understand rate is capped at like 160k, but I would recommend it being 176624 at a bare minimum for 133 tick.

On the server:

net_splitrate 2

On clients:

cl_interp 0.0001
cl_updaterate 132
cl_cmdrate 132
cl_interp_ratio 1
net_splitrate 4

Nope you don't need it, the autoexec comes with the VPK

i get dizzy with any fps above 24 so id recommend tf2's default settings of

fps_min -10
fps_max 20
networking very_very_slow

it's harder to detect this kind of cheat. he wants to make a point about how "undetectable" his cheat is.

(his previous version was also "undetectable" but was eventually banned by VAC)

icec0ldconfig coming soon

welp, i can't compete with cool. nothing's cooler than cool.

It's strange people are getting this error even though the config sets it to 0 already.

6.1.2-beta

https://github.com/mastercoms/tf2cfg/archive/beta.zip

Optimizations, typo fix and new work in progress Bad CPU addon

Thanks

I've heard 81 is more stable than 80, whatever that means. 80 has less graphical features than 81, so you might get a performance boost from that.

Set fps_max to 0. There's currently a bug on some system configurations which causes the FPS cap to be much lower than what is set.

Maybe add -freq 60

I honestly don't remember how exactly I came to the +1 value. I will have to check.

The distance decreases, so it's less intensive.

I would say most people would like to see how a pyro is firing, especially since people were complaining about the invisible flames bug before.

I wouldn't recommend using it though. 2 is a much more reliable value.

What are your launch options?

Remove -nops2b. It causes the thicker fog.