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.

Just create a file called custom.cfg in your cfg folder and add mat_picmip -1 to it.

snd_spatialize_roundrobin 0 // 1 adds a two frame delay to spatialization, not very good for competitive players

2 frame delay to sound spatialization, so sound will sound like its coming from its location 2 frames before, its slightly noticeable if you turn very quickly.

It's hard to really know what's causing stutters without any debug info. Try logging your console -condebug and turn on developer spew (developer 4).

Yep, I found that out myself and changed the documentation to say it's for Linux users only. I honestly should have initially investigated it more because it caused some trouble for people when I recommended it.

//net_splitrate 4 // Split 4 packets per frame, reduces choke but is more CPU intensive

Yeah and I would recommend using the queued packet thread.

Yeah I played the original Bridge Constructor on PC, it's pretty fun actually. It looks even more interesting with the Portal mechanics in there. And I suppose we'll get to hear more of GLaDOS, which is nice.

This release is just something extra, it isn't preventing/hindering Valve from making/releasing their own games.

not a Valve game, they just let another studio use their IP

here are some screenshots https://twitter.com/ValveTime/status/938421992512016384

Practically, the Source Engine stores snapshot (aka update) rate as an integer. It can't have decimals.

Now, it stores it as an int because of bandwidth control. Your network usage is defined in bytes per second, so therefore you have to define update rate as the number of snapshots in one second. You can't send a fraction of a snapshot, so it can't be a decimal.

You can make a new file called custom.cfg.

How would it send those 2 extra packets over 3 seconds? You can't just say that over a longer time, it would become a whole snapshot, snapshots need to be sent at a constant, discrete rate per second, which is 66 snapshots per second. Snapshot rate can't be a decimal.

net_compresspackets 1.

Yes.

6.0.0 released with a new way to install, documentation improvements, optimizations and improved organization.

http://www.teamfortress.tv/42867/mastercomfig-fps-customization-config/?page=28#836

SV_ActivateServer: setting tickrate to 66.7

Seeing as you were talking about networking,

my answer was correct. You can only send a max of 66 snapshots every second, since it's impossible to send 2/3 of a snapshot. The fact that the server ticks slightly faster is irrelevant.

Yes, because disabling compression increases the number of split packets you'll have to send, which by default are sent on another thread. If you have a weaker CPU, it would be better to use compression to avoid splitpackets whenever possible.

My settings don't do one or the other. It balances CPU load and network usage where it is useful for performance and network performance.

Besides, network usage and CPU load aren't inversely related, except for this one example with packet compression vs splitpackets, and even then the relation is not very clear most of the time.

Do you have Xbox Game DVR enabled? Here is how to disable it: https://support.steampowered.com/kb_article.php?ref=6239-DZCB-8600

Also, I believe there's a bug in TF2 at the moment which causes a strange FPS cap on any fps_max value but 0.

It won't affect benchmarks since those are local. You'll have to test in an actual multiplayer game.

The maxperformance preset will make it look like that. The commands that cause it are mat_filtertextures 0;mat_filterlightmaps 0.

Just remove cl_interp 0.

You should be putting the mastercomfig and mastercomfig_exec folders into your tf/custom folder. They do improve framerates and load times.

gl commands won't work on Windows.

I'd appreciate it if people could test net_compresspackets 0;net_maxroutable 576 to see its effects on FPS and networking (hitreg/projectiles)

Linux users: maybe try gl_batch_tex_creates 0;gl_batch_tex_destroys 0.

If that doesn't work, set them back to 1 and then try gl_nullqueries 0.

If that doesn't work, set that back to 1 and then try gl_minimize_rt_tex 0.

What are your launch options and preset?