Very strange how maxfps is not having effect on FPS.

How are you installing the config? And what does your exec usage look like?

you named yourself after literally the worst god

I think it is fine to use -autoconfig while benchmarking because I believe that the autoexec runs after autoconfig.

What are your specs and OS? Also, did you -autoconfig for when you used a new config? And yes, you should be able to daisy chain exec commands (as in, have exec commands in multiple files). At the bottom of my config, there is a commented exec for using maxframes.

The FPS impact of net_queued_packet_thread is entirely dependent on your CPU.

Did you test "net_splitrate to 3"? Just making sure...

A lot of people were also saying that it is smoother/less stuttering.

I don't think there was Setsul shitstorm, just a discussion with a bunch of misunderstandings.

There is a single command that makes you unable to move in local servers, which you can fix by setting host_thread_mode 0 when you are using a local server.

You mean #193? I was saying true toaster configs would only boost FPS with very bad PCs, but my maxframes config was for boosting FPS on any PC.

Also, the launch options I suggested work best on dx9.

Did you use my maxframes.cfg addon?

cl_cmdrate 66
cl_updaterate 66
cl_interp_ratio 2
net_compresspackets 0
net_splitrate 3
rate 167580
net_maxcleartime 0.5
net_maxpacketdrop 100
net_splitpacket_maxrate 167581

Add to launch options: -reuse -usetcp

And you could also try net_queued_packet_thread 581304 if you have a really good CPU.

your steam display names are very clever

Not sure, probably not. It gives you better network performance but lower framerates, depending on your CPU.

Good to know, thanks.

Thanks for these benchmarks. Though, I would recommend testing dx9 as well, for yourself. dx9 takes better advantage of your hardware and can result in more frames with modern configs like mine. However, if it is just visual preference, then I guess dx8 is fine. Also I have a favor to ask of you, if I may. Could you individually benchmark each launch option I suggest? Maybe then we can find the culprit which is slowing everything down.

EDIT: Do you not have a space between -dxlevel and 81?

Is this from the sniper you are looking at? Or is it an impact from your firing?

I looked at TF2 network usage and determined that the best split rate to reliably transfer enough data per frame was 2 to 3, with 3 being on the safe side. However, with some reevaluation I am considering changing the value to 2.

This is based on human reaction times, though I should consider how different situations will cause different smoothing movements to occur to adjust the value further.

2 times the rate I set. Rate is in bytes per second.

This doesn't rely on your network performance, just on your CPU's ability to handle the network code. You'll probably need a beefy CPU to run fully threaded network mode.

It was from a /r/GlobalOffensive post I read about the CVar. https://www.reddit.com/r/GlobalOffensive/comments/43urd4/why_0818933027098955175_is_the_best_zoom/

Though, to be honest, I didn't investigate it myself and just took whatever he said in that post to be correct.

System specs? Avg FPS?

5. Core parking is not a bad thing. The OS is much smarter about knowing what cores to use a specific time, so it intelligently parks cores.

9. The registry key is wrong. If it was a good idea to set it, the DWORD should be in \Device Parameters\Interrupt Management\MessageSignaledInterruptProperties. However, the driver has a better idea than you to set this setting, so you shouldn't do it. It can cause overusage of the CPU and slowdowns.

Resolution is more intensive on the GPU than CPU. Things like prop physics, ragdolls, some lighting calculations, sound, etc are affected by CPU performance.