v6.11.2 released with bug fixes and performance improvements.

Yes, the SteamPipe system shares the file structure with the main tf/ folder. However, I'd like to recommend using either tf/cfg or packing your custom folder into a VPK (if your custom files are supported for the VPK format) for faster load times.

v6.11.1 released with bug fixes, quality adjustments and sound tweaks.

If your class config alias was class_config_scout "exec myscout", make sure that it's at tf/cfg/myscout.cfg, and not tf/cfg/user/myscout.cfg.

It's very useful for the community if you share your problem and solution, because other people may have the same issue.

v6.11.0 released with performance enhancements, networking improvements and reworked customization system.

There are breaking changes, make sure you check the changelog!!

That's an old version of mastercomfig. I would recommend clearing your TF2 settings, and reinstalling the new config.

What was the last config you used that wasn't crashing before?

The only input lag I'm familiar with is the increased time to frame, which has diminishing returns for increased FPS. So, if you render faster, obviously you're going to see the result of your actions faster on the screen or reflected within the frame dependent input polling code.

I would say fluctuating FPS is worse. But keep in mind that frame pacing isn't affected by fps_max, so some issues will still exist even with a stable FPS from fps_max.

I lowered the FPS cap because so that more people could benefit from a stable, locked framerate by default, and so that there weren't so many excessive frames being output for many users by default.

An FPS cap is only useful if you can reach above it most of the time, and the previous value was very hard to reach. Now, more people will be able to reach this default, and can benefit from the stable, capped FPS.

240Hz is such a rare configuration, and such a rare FPS that people usually reach that it wouldn't be fair to increase the cap to a value that accommodates those users.

If you'd like to change fps_max for your own setup, you may create an autoexec.cfg file in a tf/cfg/user folder and set fps_max to anything you'd like

The problem with that is that some servers, more often in competitive server configs, restrict cl_interp_ratio to 1 for some reason.

cl_interp_ratio = 2
cl_interp = 2 / 66 = 0.0303

Always round down, so cl_interp_ratio is preferred.

I am pretty sure this 0.033 value that gets thrown around is because someone accidentally dropped a 0 along the way in a recommendation, and that got spread around.

https://gist.github.com/mastercoms/a7eeb371ac2c066feb3e0d397b8086c7

Looks we're nearing the end!

Rendering performance increased, sound quality improvements (in exchange for performance), network tweaks, and lighting quality adjustments.

This config is intended to be a basis for a future mastercomfig stable version, so make sure you get your feedback in if you notice any issues!

Remove mastercomfig-addon-no-footsteps.vpk. There is currently a bug with VPK based settings, where they are downloaded to the folder on enabling the VPK to be downloaded (like in the case of disabling footsteps), but not deleted afterwards, when the VPK download is disabled.

What's in your tf/custom folder?

https://gist.github.com/mastercoms/a7eeb371ac2c066feb3e0d397b8086c7

More experimental networking improvements! Also some bug fixes.