Just a heads up, the TF team has provided a branch called "pre_jungleinferno_demos". You can use that easily through Steam to use demos after they were broken by Jungle Inferno.

To access this branch, right click on Team Fortress 2 in your Steam Library, click Properties, go to the Betas tab, and then select "pre_jungleinferno_demos" in the dropdown menu. This will download ~430MB for that branch.

You can then go back to using the main build by selecting "NONE" in the dropdown menu.

Would it be ok if I made a few mouse commands the default rather than having them commented out?

m_limitedcapture_workaround 1 // Workaround for mouse capture issues
m_filter 0 // Do not average mouse input over two frames, more responsive mouse input
m_mousespeed 0 // Disable Windows mouse acceleration (-noforcemspd)
m_mouseaccel1 0 // ^ (-noforcemaccel)
m_mouseaccel2 0 // ^ (-noforcemaccel)
m_rawinput 1 // Use raw input from mouse
zoom_sensitivity_ratio 0.793471 // Use same sensitivity as when unscoped

cl_interp_ratio 2 because then you don't have to worry about a server update being missed, due to networking delays or server framerate drops.

cl_interp 0 so you don't have to set an inaccurate decimal value which will get the timings wrong and instead can use the exact division of cl_interp_ratio by cl_updaterate, which gets you better interp timings.

cl_cmdrate 66
cl_updaterate 66
cl_interp_ratio 2
cl_interp 0
net_queued_packet_thread 1
net_compresspackets 1
net_maxroutable 896
rate 187500
net_maxcleartime 4
net_maxpacketdrop 1000
net_splitrate 4
net_splitpacket_maxrate 187501
cl_pred_optimize 1
cl_lagcompensation 1
cl_predictweapons 1
cl_smooth 1
cl_smoothtime 0.07

Try these settings

Could you share your full config?

Also, what is your Internet's down/upload speed?

You bring up good points. I've removed them from the config. Instead, they are listed on a separate wiki page: https://github.com/mastercoms/tf2cfg/wiki/Silly-Launch-Options

yes

Some people may also prefer the vpk because it's less files to manage.

And yes, that will work.

6.0.2 released with documentation improvements and bug fixes.

I guess the -unbuffered_io launch option does not work then. The script scans a Source game folder for launch options.

That's what I want to find out from people testing it. Launch options can be found here: https://gist.github.com/mastercoms/12c51b171e2d3589eedc6bc9905e8f5e

I've increased the max packet size in 6.0.1 to resolve this issue.

It enables optimal buffer allocation and unbuffered IO for file loading. It works on Windows. I don't believe it works on Mac or Linux.

I was never aware that this was an issue with my config, but with custom HUDs.

6.0.1 released with network improvements and fixes, organization improvements and small tweaks to eye optimizations.

I've also created a Discord server so people can get faster help: https://discord.gg/CuPb2zV

Use the commented options https://github.com/mastercoms/tf2cfg/blob/master/mastercomfig/cfg/comfig.cfg#L438

Maybe you can also use viewmodel_fov 0.1.

Yes, you can see see the changes to the config here, or on any release by clicking the "View the code changes" link.

Yes, gibs don't impact performance as much as ragdolls.

The first two commands load data files on a separate thread, but I've found it to cause FPS drops so they're disabled.

The last two commands load all data associated with a data file, and it does this synchronously to prevent file loads from stopping the game to load stuff during a play session. If you have async data file loading on, you can turn these off, as the files can be loaded asynchronously.

New launch option to test: -unbuffered_io

Maybe try turning on the async mod_load cvars.
Also turn off cl_new_impact_effects if you have it on.

If it were not for that bug, 2 would be more optimized. The bug is that if you got server data from the last tick, it would still revert you to the predicted data for the last tick if there were no errors.

I found this bug by looking at the code.

A better rate value for you would be 90000. You can keep max clear time on 4.

Yes, 6.0.0 changes the comfig.cfg file.