Thank you for the suggestions.

1) I will add a note to check the top of the config in the init section and installation instructions. I want it at the top of comfig so it is more likely for people to see they need to change -dxlevel and mat_dxlevel.

2) I'll have to think a bit more about how a better exec system would be implemented to solve this issue.

I'm sure Valve knows they should make TF2 into an esport, I just hope they execute it well.

Not sure what's there to confirm, if you can't change cl_interp_ratio while in spectating, then the server is restricting it and you'll have to use cl_interp.

How is it pointless if it works? The default is unlimited, so on a lot of servers, it will use 170016. If a server does happen to limit it, then it will be set to 100000. I don't see the problem.

It still affects network feel and gets rid of some stutters/jumping view from incorrect client prediction.

Are you using the -primarysound -snoforceformat launch options?

Also, you can try raising your snd_mixahead cvar to 0.08 or 0.1.

cl_cmdrate 66 // Send to server at this many times per second
cl_updaterate 66 // Get from server at this many times per seconds
cl_interp_ratio 1 // Reduce entity interpolation times to minimum
net_queued_packet_thread 1 // Work around bad Windows networking
cl_interp 0 // Use cl_interp_ratio for a more accurate value
net_compresspackets 1 // Compress packets to prevent split packets
net_compresspackets_minsize 1260 // Only compress packets if we would send a splitpacket
rate 170016 // High rate to reduce choke and scale to packet rate
            // Might want to lower rate if you have <1.4Mbps stable upload
net_maxcleartime 0.015 // Balance between reducing network delay and choke
net_maxpacketdrop 5000 // Use default packet drop threshold
net_splitrate 4 // Split 4 packets per frame, reduces choke but is more CPU intensive
net_splitpacket_maxrate 170016 // Scale splitpacket to rate
                               // Might want to lower rate if you have <1.4Mbps stable upload
cl_timeout 70 // Wait the maximum time before automatically timing out on client
cl_pred_optimize 2 // Skip repredicting if we do not need to do it
cl_lagcompensation 1 // Ensure lag compensation is turned on
cl_predictweapons 1 // Ensure weapon firing prediction is turned on
cl_smooth 1 // Smooth out prediction errors
cl_smoothtime 0.1 // Smooth out view for 0.1 seconds

try these net settings

Sorry, I meant that comment for CPUs with less than 4 cores with HDDs. Though, are you having any problems with snd_async_minsize 0, like any stuttering? If so, use a higher setting for it.

only 2 hours??

b4nny is tiny b4by

https://www.youtube.com/watch?v=EY74eKw0FgI

Could you also share your speedtest results?

To be fair, Dota 2 has much more that can be changed.

4.5.6 released with documentation improvements, file cleanup and a party bug fix.

Also thank you for 100 frags!!! woooo

Hi, just enter host_thread_mode 0 into console, and host_thread_mode 1 when you're done in your local server.

(as said in the troubleshooting wiki page, in a comment at the top of the config and printed to console.)

Could I get some advice on where else to put it?

If you have Linux, you might want to use cake or fq_codel on your PC to have better traffic shaping at the OS level as well.

Change mat_dxlevel in the init section of comfig.cfg.

EDIT: ninja'd. curse you slow internet!

You can't selectively change texture quality. If you want decent looking war paints, you will have to use mat_picmip 0.

Just add that to a new custom.cfg and uncomment exec custom in comfig.cfg and you should be good to go.