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.

Only for OpenGL based systems: Linux and macOS.

It is on git, so it is updated and has history of all changes (commits). I update the config almost daily according to suggestions and my own improvements. The config is constantly being improved so I don't think there will be a final version. However, I'm planning on polishing much more soon after the pyro update comes out.

Benefits of having it is you get updated graphical and memory libraries for TF2, which improves compatibility and performance. But, you might get VAC banned.

ohmg dude i hate you i had headphones and accidentally had volume on high :((

though it's mostly my fault for being dumb and having volume up

net_maxcleartime 0.5
net_maxpacketdrop 100
net_splitrate 3
rate 167580
net_splitpacket_maxrate 167581

Could you try these CVars? They'll help with network choke. Also it would be helpful if you shared your net settings, or are they Comanglia's default?

Maybe r_pixelfog 0 is the solution. However, I think the less dense fog is only possible with pixel shaders 2.0b, now that I think about it.

Hitreg update? cl_SetupAllBones has been there since release and forces every bone to be set up. Generally, the engine has a good idea of what bones to set up and which ones to not set up, so I don't think the CVar is necessary.

-noipx doesn't exist anymore, nor does -nocdaudio. Were you able to notice a difference in sound or networking with primarysound, snoforceformat and reuse?

Foggy? Could you expand on that please or maybe share a screenshot?

Well bones affect animations in a way, but I don't think cl_SetupAllBones sets up any useful bones. There hasn't been any proof from anyone that cl_SetupAllBones actually helps hitreg.

0 is better because it doesn't force uselessly setting up bones.

In local servers, you'll have to set host_thread_mode 0. Not a dumb question. Remember to set it back to host_thread_mode 1 when you're going to join a server.