Thanks for reminding me, I totally forgot to join the group (you'll see I'm a member now)--I've only been at Valve for about 7 months. I'm not sure about the badge. But the list is woefully out of date. :)

Also, I have about 1500 hours of /played, but most of it was from before the steam stats reset that happened about 6 years ago. Sad panda.

Anyways, good call on being a skeptic, you can never be too careful!

-McJohn@Valve

Hi folks,

This is totally unrelated to cl_loadondemand_default 0. To me, this looks like packet loss. Can you run with net_graph 5 and see if it reports loss or choke values other than 0 when this is happening?

Also, if you could try to remove your addons and custom UI stuff (and reset back to default convars) that would give a useful data point. I'm *not* saying that's a solution, merely that it would rule those out.

Regards,

McJohn@Valve

Could someone (or ideally several someones) do me a favor and try the following test?

In your autoexec.cfg, find mat_queue_mode and modify it to be -1, and set cl_loadondemand_default to be 1. Then launch tf2 and see if you still get stuttering?

That is, in autoexec.cfg:

mat_queue_mode -1 // This is probably in there somewhere already, or at least is if you use Chris' FPS configs.
cl_loadondemand_default 1

Thanks in advance!

You need to restart TF2 completely (exit from the main menu) after setting cl_loadondemand_default 0, it must be set when the app starts up. Did you do so? (Please let me know!)

Thanks!

Hi folks,

I implemented this feature, sorry it's causing you grief! If you're having trouble with it (and it sounds like a lot of you are), would you mind posting your system specs? I'm additionally interested in whether you run off of an SSD or an HDD.

If you'd prefer to email me, feel free to do so at mcjohn at valvesoftware dot com.

Thanks in advance,

-McJohn