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.

I'd really like to see benchmarks on this, because from what I know, it just isn't true. Sure, there are some options which are seen as lower quality that are actually unoptimized for modern PCs (accessible only through launch options and CVars), but models and texture quality are not part of those options.

Don't use -nod3d9ex. It only increases FPS if your card or drivers are broken with Direct3D 9EX. It improves performance otherwise by using more efficient window display techniques.

Yes we did. There are a lot of improvements that can be made on top of already popular FPS configs, especially now that Comanglia is discontinuing his.

-high does not cause input lag unless you have broken input drivers somehow. High does not prevent OS level tasks from running, they still take priority.

There is a difference between toaster cfgs and maxframes cfgs. Some CVars might be good on toasters but will decrease performance on good PCs. The maxframes cfg only increases performance where it is good for both toasters and good PCs. Comments specify further tuning you can do for toasters.

The links are to the latest version of the config, using a system called git. Git tracks the history of changes of the config as well, so you can see what the updates change.

Would anyone be interested in a max quality config?

http://i.imgur.com/6RKVllH.jpg

This is what I've gotten so far. I'm doing a repass of all the settings and comments in my config and I thought it would be fun to also see how good I can make TF2 look. Surprisingly or as expected (depending on how you look at it), it doesn't impact FPS by a ton, as most of TF2's general performance issues come from other, non graphical options (of course assuming you have a good PC).

Yeah, I wasn't really familiar with that problem so I was just guessing.

Interesting. To be honest, I thought cl_particle_batch_mode 2 was kinda snake oil but it seems like it has some actually noticeable effects. I'll have to test it further to see which one is more optimal.

tracer_extra 1 if you're using maxframes.cfg.

Not sure if cl_particle_batch_mode affects it, but if it does affect it, set it to the default of 1, not 0.

Try r_shader_srgb 1 or 0. Also what is your graphics card?

host_thread_mode 0. Remember to change it to host_thread_mode 1 when online.

And thanks! <3

Hm, interesting but I think the result will be the same with -nops2b

Thanks so much!! <3 Glad it is working well for you.

If you find even the tiniest thing you'd like to for me to make better, please leave it in the thread!

Ok, I guess I'll reserve that launch option for potatos or people who prefer the thicker fog.

<3 thank you soooo much. comments like this mean like the world to me!!!! :)

I'm assuming the other launch options you didn't mention didn't have an effect. Anyway, not sure what -r_emulate_gl will exactly do, but if it is improving mouse input, that's good to hear!

EDIT: Forgot to say that the mentioned hitreg update is not really related to cl_SetupAllBones.

process: http://imgur.com/a/Mdg7V
gullywash: http://imgur.com/a/54iA7
snakewater: http://imgur.com/a/p1Rwb

Here is -nosrgb. I think the difference is apparent enough.

Good idea.

Here is a new launch option that Windows users should try: -r_emulate_gl

More launch options for everyone to try: -64OS, -arbmode, -disable_d3d9_hacks and -mpi -mpi_AutoLocalWorker

I don't know what these will do since they are extracted from the executables and DLLs and I don't have source code access. But benchmarks should show if each of these settings do anything on different people's PCs.