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.

i hear some guy named mojang is giving them away, but it'll cost ya

You should use -dxlevel 81 for your first launch only. You should be using mat_dxlevel 81 forever, on first launch and beyond.

Halve the config's rate and net_splitpacket_maxrate, and use net_maxcleartime 5.

I've been hearing about these issues, even from someone with a i7-6700K and GTX 1080 Ti, but apparently it only happens in casual servers and not in community. Could you try a community server and see if you still get stuttering issues?

By competing config, do you mean Comanglia's config (forum thread, download link)?

I'm not exactly sure how this config exactly compares to Comanglia's, but I've seen reports of higher FPS with mine on some PCs, with some having higher FPS on Comanglia's, both cases having small FPS differences. What I think I've seen consistently though, is that people have said it makes the game smoother and decreases load times.

I'd be happy to help with your installation process. Could you tell me what you tried to do to install it?

Are those all of your launch options? I would recommend using all of the launch options listed in the mastercomfig autoexec.cfg.

Do you also have the high performance power plan enabled?

As you say that decreasing graphical quality is not changing how much FPS you get in battles, I'm inclined to believe it is the stress the networking system is putting on your CPU.

Try these network settings and see how it affects your FPS.

Also, see how disabling the queued packet thread affects your FPS. Try these combinations:

• net_queued_packet_thread 1
  
• net_queued_packet_thread 1 and -NoQueuedPacketThread launch option
  
• net_queued_packet_thread 0 and -NoQueuedPacketThread launch option

can she headshot me pls i want it to end

hud_reloadscheme shouldn't fix the invisible players bug. The workaround command for fixing invisible players is record fix;stop

5.0.1 released with sound stability improvements and documentation tweaks.

I'd like to know if this fixes those missing sound issues people were having.