They're alternative vpk's that should improve fps with some added parameters, but I don't know if they're actually helping any and it's possible that those added parameters are already done by changing the shader and would just become slightly bigger files. I can't see any difference on my laptop, but I'm hoping either for someone with a different gpu to confirm it increases fps over regular _unlit or enough time will pass to just assume that there's no difference for anyone.

They change all the same files, so your game won't break or anything when using regular _unlits, but only one of them would be used so having both is pointless.

Have an animated vtf as your actual CExImageButton (with the actual always-visible button being its own imagepanel or whatever), and have the unarmed color be 255 255 255 0 and the armed color be 255 255 255 255, so that it's invisible until you roll over it.

Unfortunately, because the animation is still running even when its alpha is 0, something like "when you hover over, it gradually becomes this color" is not possible, and you'd need to do something that'd look nice starting on any frame (like you can see with what devamar's using right now).

When I removed that, I was working by a "remove first, see what happens later" philosophy. I'm almost sure that it removes the old beta muzzleflash, even if that is no longer used by the game. Not the most elegant but no harm in it either.

As a side-effect for changing the shader to a cheaper one than normal, some effects like vmt-based colors (paints and I guess botkiller silverness) get pretty messed up.

There's no real fix for it except for not using _unlit_playermodels unfortunately, since the mod works entirely by changing to that cheaper shader.

Removing the //'s before each of the steps & related sound things should remove the all-metal footsteps, and changing the "gamematerial" in default from "-" to "I" should get rid of the dust while keeping bullet holes. Pretty sure http://etf2l.org/forum/customise/topic-27554/page-1/ will do what you want.

To preload player models, all you need to do is join. You don't need to switch classes or add bots or anything, all the player models get loaded at once instead of when they exist like on props.

As for _Kermit's issue specifically, if you're not preloading, it will not work, as was said. As well, if you got rid of your _unlit vpk's and now fully use _unlit_nofog (how's that working by the way, better fps?) playermodels will not become unlit, because I'm dumb I forgot to make an _unlit_nofog_playermodels.

Unfortunately it removes all tracers, including other players', because it's just a simple material edit. It's the best I could do. And from the bit of testing I did with it, some spark particles will still hang around, but I plan on fixing that tomorrow.

UPDATED CLEAN TF2
-_particle_removal.vpk got that constant error spew in console fixed, may or may not increase/decrease fps
-added _tracer_removal.vpk as a little hotfix to remove tracers while viewmodel_fov -360 is broken

Also I'm starting work on a preload map, to get the more obscure things (bleed overlay mostly) removed without having to take the effort of getting it to show up normally on sv_pure 0 before it works on sv_pure 2. Expect it eventually :P

It doesn't improve fps but you can disable those particle effects on sv_pure 2 by editing the materials' vmt files and adding the "$no_draw" "1" parameter. Clean TF2 already gets rid of impact sparks and simplifies rocket trails and explosions by doing this, and it wouldn't be difficult to fully get rid of all of them.

Also CarlZalph, would it be possible to try to do the same method as in http://teamfortress.tv/thread/16179/no-hats-mod/?page=6#161 where the effect is disabled entirely and still works for sv_pure 2? I remember trying to do the same with other particles and it seemed to only work in some of the pcf's, but it'd be worth taking a look at.

At least from my testing, because of _unlit_playermodels.vpk, spies will appear completely uncloaked whenever they would normally be in some form visible, but still be cloaked whenever they're completely invisible.

So when a spy is cloaking or uncloaking, or you bump into one, or you're on the same team, it'll look like they're not even cloaked. But when the spy is fully invisible, which is where the whole issue would be, the spy would still be fully invisible and Clean TF2 doesn't change that.

UPDATED CLEAN TF2
-added _flat_skybox_blue.vpk and _flat_skybox_white.vpk
-added _unlit_nofog vpk's, I don't know if they affect fps positively, negatively, or at all, so they're options for now. Should remove fog and make fire particles look a lot nicer, as the two main things.

Exams have just ended though so I should be able to work on more things more often. I've got some new things I want to try out, and should finally be able to finish up moving prism hud options to ingame settings, so expect more soon.

I've had the dark overlay appear for me on certain weapons (some being stock even if I remember right) or in certain locations looking certain directions while and after taunting (it's weird), but always still got the same transparent viewmodels. I shrugged it off while I was working on it because I didn't see it doing all that much and everything still worked just fine for me.

I'm running comanglia's config so it's probably yet another issue involving settings.

EDIT: after using -Icaria-'s extra settings, I can't seem to replicate it anymore.

Without doing an exploit to completely replace the texture (which if I went with that, could just make flat textures always work), I don't believe it's possible.

How the flat textures mod works and looks all grainey on sv_pure 2 is by making the regular textures (which are usually either 512x512 or 1024x1024 pixels) take up as much space as a 4x4 texture. To get them blurred like mat_picmip, you'd need the opposite to happen, with smaller textures taking up the same amount of space as default, which afaik is not possible without fully replacing the materials and blurring the large texture itself to fake it.

I was able to get it oriented, but the crosshair is a bit smaller (was 24px big, now 20px). It works for the dot crosshair so I assume it'll work for any other of fog's crosshairs (and you could probably do the exact same with the konr wings).

FogNew
	{
		"controlName" "CExLabel"
		"fieldName" "FogNew"
		"visible" "1"
		"enabled" "1"
		"zpos" "0"

		"xpos" "c-103"
		"ypos" "c-100"
		"wide" "202"
		"tall" "200"

		"font" "Crosshairs20"
		"labelText" "3"
		"textAlignment" "center"

		"fgcolor" "phGreen"
	}

Tell me if you still run into any problems.

http://facepunch.com/showthread.php?t=1445480&p=47029420&viewfull=1#post47029420

Can't blame him for keeping it going, but yeah.

It's available for you to download you know.