I honestly don't remember how exactly I came to the +1 value. I will have to check.

The distance decreases, so it's less intensive.

I would say most people would like to see how a pyro is firing, especially since people were complaining about the invisible flames bug before.

I wouldn't recommend using it though. 2 is a much more reliable value.

What are your launch options?

Remove -nops2b. It causes the thicker fog.

They're not.

What are your launch options?

Very minimally. It makes tracers collapse to one ray, and makes flames invisible half of the time.

Yes and yes.

It's how the rate is calculated for splitpackets.

Presumably it's for MvM and TFBots, but I'm not entirely sure.

That's a good idea, I'll add it to the max performance preset.

There isn't a point to that since you can disable rendering ropes directly. This is just an optimization when ropes are small on the screen.

It has a minimal performance improvement on good CPUs, and has a big effect on sound quality for sounds that repeat a lot. It was moved to stripped "due to bugginess with frequent hitsounds", as the change log says.

Yep they're Windows only.

maxperformance or comp preset with the igpu addon would be good. If the FPS isn't good enough, you can use the stripped addon.

6.1.1 released with bug fixes and documentation improvements.

custom runs after any preset and addons.

I believe that setting causes that clicking issue, so disable it.

6.1.0 released with networking improvements, performance enhancements, documentation tweaks, bug fixes and quality improvements.

that bill is written by ISPs and will include many loopholes and will strip the FCC of its regulatory power once and for all

It isn't beneficial because of how TF2 handles HLSL vs how it handles GLSL support.

The launch option already gave better performance, there isn't a reason to revisit just because of this. I haven't been able to test if flamethrower particles are still invisible on it, so that's why it was moved to silly launch options.

not sure about TF2 but I know most orgs in Dota 2 just get a percentage of the prize winnings

6.0.3 isn't out yet. 6.0.2 is the latest release.

ms*

doot doot

Just a heads up, the TF team has provided a branch called "pre_jungleinferno_demos". You can use that easily through Steam to use demos after they were broken by Jungle Inferno.

To access this branch, right click on Team Fortress 2 in your Steam Library, click Properties, go to the Betas tab, and then select "pre_jungleinferno_demos" in the dropdown menu. This will download ~430MB for that branch.

You can then go back to using the main build by selecting "NONE" in the dropdown menu.

Would it be ok if I made a few mouse commands the default rather than having them commented out?

m_limitedcapture_workaround 1 // Workaround for mouse capture issues
m_filter 0 // Do not average mouse input over two frames, more responsive mouse input
m_mousespeed 0 // Disable Windows mouse acceleration (-noforcemspd)
m_mouseaccel1 0 // ^ (-noforcemaccel)
m_mouseaccel2 0 // ^ (-noforcemaccel)
m_rawinput 1 // Use raw input from mouse
zoom_sensitivity_ratio 0.793471 // Use same sensitivity as when unscoped

cl_interp_ratio 2 because then you don't have to worry about a server update being missed, due to networking delays or server framerate drops.

cl_interp 0 so you don't have to set an inaccurate decimal value which will get the timings wrong and instead can use the exact division of cl_interp_ratio by cl_updaterate, which gets you better interp timings.