I did 3 tests each, <1 fps difference between the two

Can I get a copy of your cleaned up version?

So I have an update to the sky-box issue I was having with the Cinematic config. Original comment here. Also, it stopped crashing but was always the purple checkerboard.

Turns out the culprit was mat_use_compressed_hdr_textures 0. After doing some testing, setting it to 1 caused the skybox to start rendering again after restarting the game. You might wanna look into that. I can't have been the only one having that issue.
It should be fixed now, although I am sad that no-one here even tried to help.
Still, keep up the good work!

EDIT: while trying to fix this, I also used r_skybox 0 which stopped drawing the sky-box altogether. This caused texture bleeding (right??) but with the trail fading away so it looked like you were in a shadow-world or something. It looked cool as hell!

Thank you!, I updated the cinema config just now.

Also the video is pretty trippy. I think their might be a few editors interested in trying that.

http://images.akamai.steamusercontent.com/ugc/447332904638225547/36517564334A849B47E911914F78CEDE6B32335B/
anyone know how to fix the kill cam being so small?

mat_viewportscale affects that i believe

Is it just the kill cam that does that?

if it is just the kill cam, I'm not so sure

if it is everything in TF2; smvn is correct
mat_viewportscale 1 should fix that

mat_viewportscale does that in the kill cam, it depends on your viewportscale ratio, eg if you're using 0.05 it's gonna be small af

Personal All Time Best (using some of the most aggressive settings I know but really shouldn't be used)

2639 frames 11.042 seconds 239.00 fps ( 4.18 ms/f) 12.702 fps variability

Can you share this one too?

.

I just downloaded the config and changed from chris maxfps, and when I join a server my whole screen goes white, except for the ammo, health and stuff like that. I can still move around and shoot, but I can't see anything... When I press escape to go to the menu I can see the game in the background without a problem. I tried without cl_threaded_bone_setup on, no difference. I tried without dxlevel, no difference. I really have no idea what it could be... pls help

edit: it also unbound my movement keys, oddly enough.

edit2: FIXED!

I'm using transparent viewmodels (http://www.teamfortress.tv/21928/transparent-viewmodels-in-any-hud) and I forgot that I need to edit my fps config in order to use those viewmodels. After figuring that out, I edited the config and now it works.

Basically I disabled my hud & audio, so idk if people really want that...

one thing i find annoying is that i downloaded the stability config and i dont have that shine anymore that i did when i used chris' dx9. any fix?

http://www.teamfortress.tv/20134/mat-phong-help

nah its not even that, i have set mat_phong to 1 and it still has no shine :(

k so i have no idea what ur talking about then lol

Setting this, mat_bumpmap 1 instead of the default mat_bumpmap 0 should fix it.

Does anyone know what it is in Max FPS for High Quality PCs that changes the mouseover panel when hovering over items in the backpack? My HUD is set up to remove the white rounded border, but using Max FPS makes the panel transparent and brings back the border.

http://i.imgur.com/jvyFe4r.png

This is what I'm talking about.
There was another HUD related issue where on particular button wouldn't highlight when moused over, but that fixes itself with hud_reloadscheme. This backpack issue does not.

I'm going to be honest here. I have absolutely no idea what command did this.

I did some testing, which I should have done beforehand. It's when you change the resolution, it causes the backpack to glitch out. That thing where it's glitched/transparent on the first try, then you go back to main menu, and from then on the backpack works fine. (I'm not the only one with this issue, right?)

So now the question is: what command causes the resolution reload itself?
This might be an unavoidable side-effect but it's still kind of annoying.

EDIT: it might be mat_antialias. I play without AA anyway (mat_aaquality 0), so I'll test if it stops if I remove it from the config. IT WORKED!

EDIT2: More testing... It turns out, mat_aaquality 0 doesn't disable AA altogether. I only assumed that it did because AA breaks my demo playback, and with mat_aaquality 0 it doesn't. It also turns out that mat_aaquality didn't seem to change my FPS at all. Also, putting -mat_antialias 0 in launch options also does nothing. It keeps resetting it to 2 (my systems recommended setting).
Damn.

updating it atm..

#140 when putting cvars in your launch options you have to use + instead of -, ex -novid +mat_antialias 0

Not sure if this has been mentioned yet but in the config it says you don't have to remove dxlevel from your launch options.

You don't have to remove it but if you keep it in there it causes alt tabbing to take a long time, usually 30+ seconds. It's best to remove it once you've put it in there to put your game to dx 8 or 9.

It's best to have it in your launch options, launch the game, close the game, then remove it

it just resets your gpusettings. have no delay probs

Thank you so much :)

I kinda knew that but I looked up the launch options on the valve software website and it said -mat_antialias. But I did as you said and it works beutifully now :)

Sorry about the R4ndom cfg suggestion, a typo was made on the version I released. It lives up to my claims now.

Whenever I turn left or right, the water seems to have weird bars that move around:
http://i.imgur.com/fpHVbrq.jpg
http://i.imgur.com/caFtTLY.jpg
http://i.imgur.com/II0qO1M.jpg
Not only the water, but the config also give me weird lighting effect:
http://i.imgur.com/lSESsJ9.jpg
http://i.imgur.com/ass5GEa.jpg
http://i.imgur.com/ez0FVED.jpg
http://i.imgur.com/4FFFmcJ.jpg
The LODs are also lowered:
http://i.imgur.com/fHOMkpi.jpg
I need fix pls ;-;

Every 20 seconds i get ping spikes to 200-250 for 1-2 seconds and it sometimes freezes, any fix?

remove the -dxlevel 81 for better stability with ALT+Tabbing <------this one when do i do that?after launching the game every time?

After you launch the game once with dxlevel 81, it puts the game into dx8, so you don't need to re add it whenever you launch.

So no, just do it once, launch, then remove it.