It isn't beneficial because of how TF2 handles HLSL vs how it handles GLSL support.

The launch option already gave better performance, there isn't a reason to revisit just because of this. I haven't been able to test if flamethrower particles are still invisible on it, so that's why it was moved to silly launch options.

m_limitedcapture_workaround "1" is the default setting though. However, if you hadn't experienced any issues prior it was added I'd say it's safe to disable it.

Does the exec custom run after the comp preset?

Also kind of off topic but can this or a different setting make TF2 mouse capturing better? I still get issues clicking outside of TF2 when playing it full screen with a second monitor enabled.

custom runs after any preset and addons.

I believe that setting causes that clicking issue, so disable it.

6.1.0 released with networking improvements, performance enhancements, documentation tweaks, bug fixes and quality improvements.

I'm running a potato. Classic case of waiting on more money for building new pc.
Can anyone tell me if this is the best option for me?
Running slightly less than 2.0 ghz cpu, 2g ram, integrated graphics. This is a true potato. I can play a little league of legends, n64 games, and now experimenting with tf2 for the first time. Is this config going to give me best fps disregarding quality? and how do I use this method? Thanks a bunch.

maxperformance or comp preset with the igpu addon would be good. If the FPS isn't good enough, you can use the stripped addon.

6.1.1 released with bug fixes and documentation improvements.

snd_lockpartial and mat_managedtextures are treated as "unknown commands" for me. Maybe those commands don't work with OpenGL?

Yep they're Windows only.

....

mastercomfig-comp.vpk and mastercomfig-compquality.vpk appear to be the same file

Hey there, how to remove the fog?

Does cl_particle_batch_mode 2 improve performance? What are the bugs with it?

Does mat_reducefillrate 1 use more CPU? Does it reduce performance for good graphics cards? Trying to work out why it was moved to igpu.cfg.

What is the logic in setting net_splitpacket_maxrate exactly 1 higher than rate?

What effect does nb_shadow_dist have on gameplay and performance? Does it have any effect if you set r_shadows 0?
Also, the Valve developer wiki article on NextBot states that it is an AI system - how does it relate to shadows?

Could this be set to some extremely large value (ie cl_fasttempentcollision 10000) to effectively disable checking for such collisions? Would this improve performance?

Could this be set to some extremely large value (ie rope_solid_minwidth 10000) to effectively disable drawing ropes? Would this improve performance? Would this have any effect if you set rope_rendersolid 0?

Finally, does snd_cull_duplicates 1 improve performance on good CPUs? Does it have a large effect on sound quality? Interested in why it was moved to stripped.cfg.

They're not.

What are your launch options?

Very minimally. It makes tracers collapse to one ray, and makes flames invisible half of the time.

Yes and yes.

It's how the rate is calculated for splitpackets.

Presumably it's for MvM and TFBots, but I'm not entirely sure.

That's a good idea, I'll add it to the max performance preset.

There isn't a point to that since you can disable rendering ropes directly. This is just an optimization when ropes are small on the screen.

It has a minimal performance improvement on good CPUs, and has a big effect on sound quality for sounds that repeat a lot. It was moved to stripped "due to bugginess with frequent hitsounds", as the change log says.

My launch options are: -novid -nojoy -nosteamcontroller -noff -nohltv -softparticlesdefaultoff -reuse -primarysound -noforceformat -swapcores -full -w 800 -h 600 -nops2b -high, Im on dxlevel 90 and using the maxperformance and the igpu addon

Remove -nops2b. It causes the thicker fog.

Ok i'll try it

Could you elaborate on this?

What is the logic in setting it to 200 in comfig.cfg and 0 in maxperformance.cfg?

Also, I'll just comment that I always saw the bug where cl_particle_batch_mode 2 doesn't draw flames as a positive, as it means that I can actually see when being attacked by pyros.

my cl_interp is locked at .0333, how can i get it down to .0152?

youre referring to lerp right?
cl_interp_ratio 1

thanks : )

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.

I found a typo in the comfig.cfg file

Line 68:
//cl_allowupload 0 // Diisable uploading your player custom files

thoughts on dxlevel 80 vs 81?

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.

Can I switch to dxlevel 81 or will I still crash?

It’ll be fine as long as your graphics card driver still supports dx8.

Recent AMD drivers are dropping support for dx8 so you might want to roll back your drivers in order for it to work properly.

6.1.2-beta

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

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

When ever I try to join koth_lazarus I get an error 'engine hunk overflow' which commands do I need to update to fix this error?

r_hunkalloclightmaps 0 should fix it

This fixed it, thanks