A little testing on +mat_dxlevel 81 vs dxlevel_81
There was a bigger difference in how things look when I was using one of the other autoexecs (probably some sort of setting), but now at least we can confirm that +Mat_dxlevel 81 gives you DX9 rocket trails.

+Mat_dxlevel 81

2639 frames 19.997 seconds 131.97 fps ( 7.58 ms/f) 8.921 fps variability

Rocket Trails:

Badlands:

-Dxlevel 81

2639 frames 20.441 seconds 129.11 fps ( 7.75 ms/f) 10.373 fps variability

Rocket Trails:

Badlands:

halp!! I'm still crashing D':
changing mat_queue_mode to -1 didn't stop the crashing. now trying this: http://forums.steampowered.com/forums/showpost.php?p=33910019&postcount=2

EDIT: Holy sh&^, look what I found
https://github.com/ValveSoftware/Source-1-Games/issues/765#issuecomment-20222936

I started screwing around with my net settings to see what feels smooth, and ended up with this:

rate "60000"
cl_cmdrate "66"
cl_interp "0.0182"
cl_interp_ratio "1.2"
cl_lagcompensation "1"
cl_updaterate "66"
cl_smooth "1"
cl_smoothtime "0"
cl_pred_optimize "2"
net_queue_trace "0"
net_splitpacket_maxrate "1048576"

I used some settings from R4ndom's net settings, and got help on the interp settings from #24 (The ones that fix microstuttering/are for 120Hz): http://www.teamfortress.tv/14120/about-cl-interp-and-hit-registeration

So far, it feels really smooth, although, it's sacrificing a bit of lerp to fix microstuttering, a trade off I'm more than willing to do. Try them out, and tell me what you think.

Also, I think that +mat_dxlevel 81 makes you use DX9 rocket trails, because my rocket trails are feeling unusually large, so I'm going to switch back to -dxlevel 81. I'll take them out after the first launch like Yuki said.

Okay, I just switched back to Chris' net settings, and my game feels like sh*^ again. When I switched back to R4ndom's net settings, my game felt smooth. The smoothness issues also happen offline with the wrong net settings. I can say for certain that my game is smoother with R4ndom's net settings, but the hit registration isn't good.

Can anybody figure anything out from my posted net_graph?
Also, I'm still crashing in-game.

http://pastebin.com/xYM1rZpb
http://pastebin.com/5qAj6sua

resetting the refresh rate didn't do anything. It's literally ALL the net settings.

I'm looking to see if there are any good pocket guides that can help me out. I've been trying to play pocket for a while now, but me and the class just don't work together. Pretty much need a guide that thoroughly explains pocket mentality, roles, when to push, and other important things related to gamesense. Most people just say that pockets easy and all you do is stick with the med, but that doesn't help me at all.

The guides I've found usually just spent an hour talking about sensitivity and config, without even touching upon gamesense.

wut? so you're admitting you're an idiot???????????????

Tapley's post is legit proof that in this community you can get away with literally anything if you're well-liked enough.
Look at his +frags, look at the other people telling him to go get a job.

edit: fixed 4 clarification

Wait a moment...
If dxlevel_81 forces motion blur off, and +mat_dxlevel 81 doesn't, then with +mat_dxlevel 81, wouldn't it be possible to have transparent viewmodels?

I switched to R4ndom's config and now my game is just as smooth as it is when I play Quake, with the lower resolution. The only problem is that my game is STILL crashing. I'm very sure that R4ndom's config has at least parts of m0re's config in it, because I see some of the commands that are in m0re's config but not others. (ex: mat_maxframelatency)

autoexec: http://pastebin.com/8yt8uQjc

I did the stress test for ~10 minutes or so, the temps stuck around 74 - 76, and I'm not throttling.

Just out of curiosity, would you mind telling us what exactly you're going to get with the $500?

We can scope for deals to try and help you out, along with critiquing your build/system to make sure you get the best bang for your buck.

I searched around for some other configs, and tried Rhapsody's and m0re's. m0re's made mine feel a bit smoother, but TF2 is still nowhere near as smooth as Quake Live for me. Going from 1920 x 1080 → 1280 x 720 REALLY helped with the smoothness, and the game is now 'playable' for me, but I liked having 1920 x 1080, and it's still not 'Quake Live' smooth yet.

edit: my game now for some reason crashes w/ m0re's or comanglia's
m0re's: http://pastebin.com/3LdQAixb

Holy crap its looking good right now...

No, tried it and it didn't help.

Why not?

I did autoconfig and autoexec (in case you weren't wrong and autoexec actually did something), and right off the bat it felt a tad bit smoother, and that's with the occasional dipping below my refresh rate.
Any recommendations for another config?

Okay, I just compared the two in-game to see what happens with both of them, and they actually look REALLY different in the game. I did do a benchmark (and didn't think of copy and pasting), but the numbers were both very even. But why?

I went on Sawmill, and even though I had weather particles disabled, I ended up seeing smoke everywhere and it was just a mess. I took a look back at the particles, and found the cig_smoke works just as well, because if you're in motion the smoke gets left behind, and if you aren't the smoke isn't very prominent anyways. I think its because DX8 might filter the specific particle or something like that...

But thanks so much for getting rid of muzzle! I've been begging for something like this forever.

EDIT: Fuck my advice, cig_smoke although good as a particle causes crashing

Basically, my game feels like its running @ 30FPS when in reality I get about 200 FPS in pubs with occasional drops to 150 during action. It's recently gotten worse, and come to the point where its messing with my tracking. I track to hit airshots and even groundshots, but now I'm forced to flick as soldier so I can't hit anything. Halp!

net_graph 4:

Config(s):

Custom Folder:

Optimizations:

Important Specs:

Benchmark: