What's your OS and OS version?

To be honest, I don't know the exact answer to that question. All I know is that systems will explicitly request a TCP stream socket and if one is successfully created, it will use it. Therefore, my logical conclusion is that this launch option allows systems that prefer TCP over UDP to use TCP, and it seems to be disabled by default due to the extra memory usage it requires.

-usetcp simply allows TCP to be used. Game networking will still use UDP. You can confirm this by setting net_showudp 1.

Hi, thought I might share my list of all TF2 launch options: https://gist.github.com/mastercoms/12c51b171e2d3589eedc6bc9905e8f5e

I was hesitant to share this as it might cause a new wave of snake oil and harmful tweaks, but I figured it could help some people. So PLEASE do not just assume what something does and roll with it. It could do nothing or harm your game in some way! (or else I will find you and tell you mean words.)

Thanks to aveyo from the Dota 2 config community for the help.

Thoughts on expanding the comp.cfg preset into two presets: compperformance.cfg and compquality.cfg?

compperformance.cfg would be basically the same as it is now, reduces quality except where it would extensively decrease advantage/playability

compquality.cfg would enable any effects that would give you an advantage, even if they decreased FPS. For example, muzzle flashes, shadows and enhanced sound spatialization/effects.

Try adding

-primarysound -snoforceformat

to launch options.

I investigated the CVar further, and have concluded that the network benefits are nonexistent. I've now set it to 1. Thank you for pointing me to this.

net_queued_packet_thread is ideal to be at 0, however there is a bug/oddity with Windows where packets need to be queued or else they are ignored sometimes.

It does increase CPU load and affects performance. Vantavimeow has a 6700K so the performance impact is negligible there.

maxperformance.cfg was always about performance, not gameplay. Comp.cfg balances the two.

You can argue that 0.1 is too high, and I would agree with you if was set on the base config or comp cfg, but it's not. It is set on the maxperformance cfg which also has sound spatialization nearly disabled, occassional flickering lighting and other changes which make it only tolerable for people who had untolerable FPS. The maxperformance config isn't meant for people who can't handle those sacrifices/don't need to make those sacrifices. The only thing I want to avoid is making it completely unplayable.

Did not mean it to be.

Is it just skial servers that have this issue, or all community servers? I've heard from some people it only happens on skial servers. I still don't have a clue what causes this, but you could try removing -reuse -usetcp from launch options. I'll try to look into it more. Does it happen when you do use -default, with no other launch options as well?

Just a remnant from when I was making maxperformance.cfg for bad PCs, and comp.cfg was for max performance with decent PCs. I'm not high, nor do I condone the use of drugs. Stay safe kids.

I'll change it to 0.1.

If it is happening with -default, it is probably something on Valve's end.

Hm, the way they're connecting TF2 to this is kind of weird, but understandable.

You can most likely fix the issue by increasing the value of tf_time_loading_item_panels. This is the time in seconds that TF2 will spend on items per frame, so a reasonable higher value would be tf_time_loading_item_panels 0.0005.

i fear seeing anything relatable to me in this thread

Depends. What does your speedtest look like?