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?

Are you using a custom HUD?

what cfg?

http://i.imgur.com/qMoJ0h8.jpg

Maybe host_thread_mode 0 will prevent the crashes.

IIRC I did, but it was too spammy to give any useful information. Could be wrong though, it was more than a year ago since I used network debugging to test things.

Hm, that's strange, though are you sure it has to be something with my config? It could be a TF2 bug.

I have done some debugging and a bit of decompiling but it honestly takes a long time to get anything out of it so I haven't looked at much stuff. Hopefully I'll get to figuring out what the splitpacket cvars do eventually.

I believe it works on clients, as clients still split packets if they're too big. Unfortunately, I don't have access to any source code that uses these split packet commands, so I can't be too sure about them.

The two rates for normal packets and splitpackets are the same for simplicity because rates are dependent on your Internet connection, and it is easier to adjust the rates as one value according to your upload speed, rather than mess around with trying to optimize the two rates individually for a lot of different upload speeds.

You mean the white outline that appears on your screen? I believe that's controlled by your HUD.

Is there any console output related to medibeam/mediguns?

they changed the airblast hitbox though.

Are you remembering to set host_thread_mode 0 when in local matches?