fagoatseNice timing :)
Anyway, I tried net_queued_packet_thread 0 with the -NoQueuedPacketThread switch and all is good. I'm on windows 10 btw.
Alright, sounds good. Seems like we will have to find out if stabby was using -NoQueuedPacketThread.
osvaldoDunno if it's placebo but when I set net_queued_packet_thread to 1 I had some weird hit reg. Now that I have net_queued_packet_thread 0 it seems to be fine although I havent tryed experimenting with the said launch option.
Well you should also have the launch option if it is at 0. It saves memory and CPU which is being idly wasted.
Also, no, it isn't placebo. When packets are bigger than net_maxroutable, which is maxed out at 1260, Source divides them up into smaller chunks called splitpackets. These splitpackets are delivered in a sequence and with net_queued_packet_thread 1, each splitpacket after the first splitpacket is sent on another thread out after a delay that depends on your rate setting and the splitpacket size. If you have it set to 0, then the splitpackets are sent at the end of the frame immediately.