programming and drawing

Probably snd_spatialize_roundrobin 3, r_3dsky 0, r_flex 0, dsp_slow_cpu 1 and flex_rules 0, which are all used in comp.cfg with the exception of snd_spatialize_roundrobin 3 since it delays sound spatialization.

About r_occlusion and r_dopixelvisibility, I've been benchmarking these to find out which is better on modern hardware, though I expect r_occlusion will be best set to 0, and r_dopixelvisibility is best set to 1 (due to building_cubemaps 1).

Seeing as those launch options don't exist, I would say there is no benefit.

There was supposed to be an optimization patch to outlines, but I guess it didn't get in this major update.

It would be helpful if you could share your preset. But, assuming you're using comp, the simplistic lighting is from mat_phong 0, so set that to 1 if you want more complicated lighting. There's a pretty decent impact on GPU load, but your 970 should be able to handle it well.

I'm not sure about the blue lights on Turbine, though it might be caused by building_cubemaps 1. This cvar is quite extensive and affects a lot of different graphical features, so the performance impact from setting it back to 0 can vary quite a bit.

Make sure you have set m_mousespeed 0 and try out m_limitedcapture_workaround 0 and 1.

It's not a surprise. In Dota 2, Valve has a matchmaking option to match them against a team of 5 worse than them (by 1000 MMR) who are also globally muted and in the low priority punishment pool. It's apparently for "when you want an easy game".

The -dxlevel launch option will do that, since motion blur is turned on by default in DX level 98 and the launch option sets DX level defaults.

Not sure why your DX level changes to 70 when you disable motion blur. You can probably avoid this issue by disabling it through the console: mat_motion_blur_enabled 0.

Also, if you want high graphics settings, I would recommend for you to check out the maxquality preset in mastercomfig (comes with motion blur on though, so turn it off with the cvar mentioned above).

Depends on your GPU.

Well, there's a glitch with cl_particle_batch_mode 2 where it sometimes skips drawing the main flame particles. But besides that, I don't really know of anything that would help.

You can change r_worldlightmin to its default of 0.0002, at a slight performance decrease. There's also r_ambientboost 1, which boosts lights on models. It has a small CPU load increase.

You can also use mat_phong 1 and r_rimlight 1, which enhances reflectivity and enables lighting on model edges. Comes at a GPU load increase. Though, I don't think that's what you're looking for.

moldy snacks go in the trash please

guys i just wanted to let you know capitalism isn't all bad

5.0.2 released with network tweaks, documentation improvements and bug fixes.

It looks like they replace grass on the ground? So maybe try r_drawdetailprops 0 or 1. Also how did you get everyone's name on the casual bar? It looks cool! :)

For the sake of testing, could you try running TF2 without those tweaks (timer tool, razer game boost, process lasso, msi afterburner, game mode, CPU unparking)? And try setting dxlevel manually and also trying -default.

No problem! I just love helping people :)

//sys_minidumpspewlines 500 // Basically the number of lines saved to a log file from console. No FPS boost but 15% lower FPS variance
sys_minidumpspewlines 500 // You're setting it to the default value of 500. It doesn't affect FPS or FPS variance anyway, it does not become a factor in normal play as it only is used when TF2 crashes.

I don't say it affects FPS or FPS variability. Comanglia wrote that first comment. My correction is the 2nd one.

Remove -nosrgb from launch options

meh because it reminds me of my favorite movie

What is your OS? Do you have Game DVR turned off? What about window optimizations and game mode? HIgh performance power plan? What are your launch options?

I've found it very hard to debug this issue, as I don't get it on any of my PCs, on Windows or Linux, so any additional information is appreciated.

cl_interp should always be set to 0 (unless a community server is restricting cl_interp_ratio for whatever reason). Use cl_interp_ratio and cl_updaterate to control interp more precisely. (if cl_interp is set to 0, it will set to cl_interp_ratio / cl_updaterate). Your interp ratio should be set to the lowest packet interval where you don't have any packet drops. Most of the time this will be 1.

TF2's tickrate is 66. So, if you have cl_interp_ratio set to 1, and cl_updaterate set to the max of 66, you'll get a cl_interp of 0.01515151515.