idk how u made a graphics config without knowing how to remove gibs and ragdolls but its a series of console commands (u can find them in most toaster configs)

LOD Tweak is this:
http://www.teamfortress.tv/35876/get-quake-like-textures-high-lod-bias-again

I know, but most ragdolls disabling configs get a value wrong and cause a memory leak (possibly fixed in Tough Break). I wanted to make sure what values they were using.

It is time you learnt about the most common perfomance-increasing tools and tricks:)

LOD Tweak aka Low Bias

Max frames very essentials:

Please don't use these settings with my config. I already set these to optimal values in my main config and maxframes.cfg.

Main offenders: r_lod 2 (sets all models lod 2, even if they can go down to a lower lod, use r_rootlod 2 instead and set r_lod to -1), blink_duration 0 (doesn't do anything except divide by zero and possibly cause some errors/memory leaks), g_ragdoll_fadespeed 0 (this is the rate at which the ragdoll fades out, if it is 0 then it just takes up memory trying to do the impossible fade task per frame, though this might have been fixed in Tough Break), and I thought violence_hgibs 0 enabled low violence mode, which is worse for performance.

It is better to remove any extra configs you have for graphics and just suggest values to me. They might be ruining performance.

I've found some launch options that you peeps might want to test:

-nosrgb : disables SRGB (limits variety of colors) results in flatter/smoother colors, and brighter lighting
-nouserclip : disables user clip planes and enables fast clipping (I experienced a fps boost with this)
-nops2b : uses pixel shaders 2.0 instead of 2.0b, reduces fps impact of some shaders
-softparticlesdefaultoff : disable depth blending for particles and sprites

-nosrgb looks really weird for my friend, but looks okay for me

I haven't noticed any visual changes with other launch options

edit: gonna run benchmarks soon
edit2: i suppose that is nouserclip's fault

Also @stabby mentioned before that cl_SetupAllBones 0 causes hitreg issues

your friend has mat_filterlightmaps and mat_filtertextures set to 1, and it looks like you have it set to 0

Eh, unlikely. Most likely placebo.

Sorry for kinda spamming, but these launch options seems really "buggy"

You know which launch option causes this? Most likely -nouserclip

Also are you still using dx8?

I removed launch options you suggested one by one and removing -nosrgb fixed that

@stabby didn't seem too sure: http://www.teamfortress.tv/post/756490/comanglias-config-fps-guide

I switched to 90

edit: -nosrgb works fine on 80

It's stabby, the guy who recommended launch options that don't exist.
You can't even afford the amount of salt you need to take his advice with.

So benchmarks soon then?

He's trying his best, and admits when he is unsure about things.

Sometimes. Sometimes he's sure about things that are definitely wrong though.
Some claims can simply be ignored and all others should be tested before trusting them. If you want to study the placebo effect he's your guy. I mean he tries to get it right and believes what he says, but that doesn't make it correct.

Experimental launch options benchmark:

-nouserclip causes texture problem on dxlevel 80 too

Wow, that's a decent perf boost. I've been quite skeptical about using launch an extended list of launch options since all/most the ones that were really well known are obsolete but now I think that some of us might want to test those out!

Config mains are so passive aggressive

without using sillygibs, what would be the best way(s) to hide the gib effects? would it be possible to preload custom files (e.g. textures and/or scripts relating to gibs that are pointed to null or missing files) such that they work on all different sv_pure server types?

my main problem with gibs is that they can appear desynchronized from the victim. ideally, i'd like to completely hide the gib effects without relying on sillygibs & reducing my framerate. however, if there was a way to make them pop into existence in a less janky fashion, i could live with that.

You should be able to preload null models to hide them. Should work with both regular and silly gibs. I forget if clean tf2 does that for gibs or not, but it'd just be a matter of copying and renaming the model files. Same thing as the no hats mod basically.

Don't commands already disable gibs though? Sorry if I'm mistaken but I thought that was an option.

mastercoms states in her config that disabling the violence_hgibs convar forces sillygibs (which, due to what i assume are other convars that aren't explicitly related to gibs, still hides them from view). i'm not sure if these hidden sillygibs still cause a performance loss versus regular gibs. if they do, i'll definitely be using your Clean TF2 mods.

there is another convar called tf_playergib, but i believe it's tied to a server setting which controls what type of gibs are shown.

also, i just realized that the major visual discrepancy that threw me off was violence_hblood. and since mastercoms verified that blood can be safely disabled, i'm satisfied as is. it has been so long since i used a config that enabled blood that it completely threw me off.

@JackStanley did you make sure to remove the -dxlevel launch option after you forced the game to use it (i.e. set it, instantly close the game after verifying in console that the dxlevel was set, and remove it)? playing the game while the launch option is active is known to cause performance & graphical problems.

I got some small gains (~+5 avg fps) from setting r_lod to "-1" from "2", and the "-softparticlesdefaultoff" and "-nouserclip" launch options. Thanks :)

As for "cl_setupallbones", I've never made any recommendations, just asked questions. Some config maker made the claim that the cvar was related to the major hit reg fix that came out a while back. I'd still be interested in knowing what the ideal value is.

I'm curious how you "find" launch options. Were these just added recently, or have they been there since release but no one has stumbled upon them yet? Is there a full list of launch options somewhere?

Also for the other launch options you list such as -nojoy, -useforcedmparms, -noforcemaccel and -noforcemspd, why did Chris tell us they don't work here?

They've been there since release. I just looked through the source code to find them.

I don't know why Chris claimed this because I can verify even without source code that nojoy does affect the game's behavior. TF2 outputs "Did not detect any valid joysticks" to stdout when nojoy is not present. Not sure about the mouse acceleration commands since I haven't used Windows in years. But from my memory, I remember them affecting mouse acceleration.

I would definitely recommend cl_SetupAllBones 0. Also any reason why you didn't use -nops2b?

After looking at the code again, I think setting any of the violence_ cvars to 0 enables low violence mode/silly gibs, but I'm pretty sure the code I'm looking at is outdated so I'll have to test in game. The best way to disable gibs is through the prop break max pieces commands, I believe. Not sure about blood, how was this done traditionally?

Found a few more launch options, though I haven't fully investigated them yet

-mat_softwaretl : forces software vertex processing, might be useful for bad GPUs
-limitvsconst : limits hardware vertex shader constants to 256, don't think this one will be too useful
-primarysound : uses a single sound buffer, not sure what the real impact of this is
-snoforceformat : skips force setting of sound buffer format, not sure what the real impact of this is
-reuse : allow network sockets to be reused when busy (sets SO_REUSEADDR), not sure about this one but i tested it earlier and i didn't have any bad results with it, maybe someone with a better feel for net settings can test this
-usetcp : allows usage of TCP, probably useless because I'm not sure where TCP would be used in TF2, I'll have to investigate further

Some more kinda useless ones:
-shadersondemand : initialize shaders on use, though it still seems to allocate memory for the shaders, so don't see any use case for this...
-random_invariant : use the same seed for local RNG every launch, don't see a use besides debugging
-small : allow resolutions smaller than 640x480
-filmgrain : may enable a film grain effect, crashed on my PC when I entered a game

is there any proof about how cl_SetupAllBones 0/1 affects hit reg?
also, why do you prefer 0 over 1?

sorry for the dumb question, but does anyone know why i can't move in walkway/other tr maps after i started using this config

Well bones affect animations in a way, but I don't think cl_SetupAllBones sets up any useful bones. There hasn't been any proof from anyone that cl_SetupAllBones actually helps hitreg.

0 is better because it doesn't force uselessly setting up bones.

In local servers, you'll have to set host_thread_mode 0. Not a dumb question. Remember to set it back to host_thread_mode 1 when you're going to join a server.

thanks a lot ^^