Depends. What does your speedtest look like?

cl_hud_minmode is not being enabled by default. It is commented out in the config.

As for hud_sayttexttime, it does change it to 10 by defautl but I agree, it should be commented out by default and I've changed it to be that way now. However, to avoid settings to be overridden, you should always make sure that run your commands after the config.

What are your system specs? And you could try out my config. It is going to be updated further and might solve your FPS issue.

Sorry that you've been having issues. Could you run con_logfile console.log;developer 1 in console and then share tf/console.log when you crash? Also, what are your system specs and OS?

Could you clarify what you were having trouble with when you meant hard to read through multiple files? The only file you should be reading through is comfig.cfg, and autoexec.cfg if you already have your own autoexec.cfg. The rest of the files are just presets based on the comments in comfig.cfg for convenience.

Also, it won't make sense to put the config in the cfg folder since there are overrides for other files as well and I plan to add more after the Jungle Update. That's why the mastercoms folder needs to be in the custom folder.

Launch options:

-nops2b -softparticlesdefaultoff

Config:

// DX8 style lighting
r_ambientboost 0
r_rimlight 0
mat_phong 0
r_worldlights 0
mat_disable_lightwarp 1
mat_hdr_level 0

// DX8 style shadows
r_shadows 1
r_shadowrendertotexture 1
r_flashlightdepthtexture 1
r_flashlightdepthres 128

// DX8 style water
r_waterforceexpensive 0
r_waterforcereflectentities 0

Yeah admittedly I shouldn't have used the word scale. My bad.

3CP. It doesn't give a defensive team too much of an advantage and combines the best of KotH and 5CP.

But in all honesty/seriousness, having these dynamic team balances of defensive vs offensive aren't very well suited to the current rules of the game.

The best solution is to have one team always defending and one team always attacking like in AD or Payload. Unfortunately, those modes have their own problems, especially payload.

Yep that's why it was removed in a config update. Was just making sure no one had it in their config.

Well it is supposed to change the rate at which your pitch changes when doing some client side pitch adjustments, not sure if it works in TF2.

Setsul, perhaps you misunderstood what I was trying to assert. I was trying to say that TF2 does scale in the sense that it will use more cores as available, since the person I was replying to was saying TF2 only uses 3 threads. I was trying to correct that error. In my previous post, I thought I made it clear I was already aware of the synchronization issues so not sure why you told me about that.

Hm, apparently max performance has a problem somewhere because people have been having lower FPS with it. Also, did you use the same launch options for both configs?

I wouldn't recommend running an anticheat or any system verification stuff under WINE.

No that was causing crashing.

Interesting. I'll look into what's causing max frames to be lower than comp.

It's fixed in the 4.1.1 release, but was fixed earlier in the latest git commit. I should really be on top of making new releases.

Does your max performance config contain the option mat_forcemanagedtextureintohardware 1?