Here is a list of some more command line options to use with Steam.

A few useful ones from here:

-clearbeta (Opts out of beta participation in case for some reason it can't be done via settings)
-noverifyfiles (Prevents from the client from checking files integrity. Anyone remember that bug where games would constantly keep verifying itself??)
-single_core (Force Steam to run on your primary CPU only)

That's the one I linked in my original question. The downsides of this are the 5 steamwebhelper.exe processes are always running, and instantly restart once the script kills them. The script killing them is only to stop the memory leaks and excessive usage people were reporting. Plus the game will stutter every 4 minutes (or whatever time you have this set to) once these processes are killed/restarted.

The reddit user aveyo who made this script has even said that it's useless now that steam can be configured with the launch option to prevent it from starting. This method just isn't as widely known.

So if you are using this script, please run the stop script included in the download, and use my method instead.

You are very welcome!

I'll be looking into what other launch options are available which may have a positive affect on TF2 over the next few days, so stay tuned.

Update:I've found a much easier way. You can configure the steam client itself with launch options!

Link here for more information.

On Windows, right-click your Steam shortcut, open Properties, then edit the Target line after \Steam.exe" with the line "-no-browser" (Note, you may need -console too). There are other launch options you can use, such as ones to disable any VR stuff and so forth. Feel free to experiment and see what works for you.

For example, here's mine:
"C:\Program Files (x86)\Steam\Steam.exe" -console -no-browser

This will stop the steamwebhelper service from starting up, and just means that you need to use firefox or chrome when you want to browse the store or trade etc, which a lot of people do this anyway.

Please try this out and see if you notice a difference in TF2 like I did!

That's an interesting idea, that seems a bit simpler than what I was trying to achieve. I'll look into this.

Update:

This might be common knowledge as it's been a problem for many years, but disabling steamwebhelper has given me a 10-15+ fps boost and eliminated my stuttering problem.

I originally followed this method, and while it still worked, my game would stutter every 4 minutes (or however long I set it to) when it killed the process. More importantly, these 4 or 5 processes would instantly start up again, defeating the purpose.

Only recently I have come across this solution (which gave me the fps boost and reduced my stuttering):
1. Find the file Steam/bin/cef/cef.win7/steamwebhelper.exe and go Right click -> Properties
2. Go to the "Security" tab, then click "Edit..."
3. In the appearing window, select the Group "Users" and make sure you check all of the boxes in the column "Deny" below. Repeat for the Groups "SYSTEM" and "ALL APPLICATION PACKAGES" (Though I'm not sure if that's necessary)
4. Close all the windows with "Ok" and you're done.

This works much better than the script, except for one problem. The steam client is always trying to update itself as it senses something is wrong, not to mention I would be missing out on the monthly steam client updates.

What I am hoping someone can help me with is a script or something that kills steamwebhelper, denies it from starting again, launches TF2, and once I close TF2, allows steamwebhelper to start again so I can use the steam store and profile tabs. Would this be possible to do, rather than me manually doing it each time?

In your config there's options for a bad gpu addon and a bad cpu addon, Are there any plans to make a "good cpu or gpu" addon, for commands which may be worth sacrificing fps for better hit reg or whatever?

For example, I see you have a beefy PC and are using net_splitrate 8, but the default in your config is net_splitrate 2. What are the advantages of this, and should we be doing the same if we can afford to?

But they used to be able to be turned off, yes? Or am I just hallucinating?

Hi Mastercoms, the black and yellow caution lines as seen in this image used to be able to be turned off via r_renderoverlayfragment 0 I think. But now regardless of this setting, they stay. Are there any other commands which can turn these off?

So if you have a beast pc, you should use a split rate of 4 instead of 2?

Are using the no explosion smoke script? The script could be using the env_mist particle effect (which doesn't work on dx8 afaik)

What the fuck is this new short circuit alt fire? It takes up the whole screen

If I still wanted to keep cosmetics, which folders should I be deleting after I extract the vpk?

And this requires preloading, yes?

May I ask why the zip installation method was removed? I feel like I remember reading that certain improvements could only be made using the VPK's, but when I extracted the VPK's to see what I was different, all I saw was the new game_override config file. Speaking of which, cl_detaildist and cl_detailfade always used to revert back to their default values on map change, I'm not sure if they still do though.

Looking to upgrade my PC

Current specs:
i7 4820K @ 3.7GHz (not OC'd yet)
GeForce GTX 760
16gb RAM
Gigabyte X79-UP4 motherboard

I'm looking to play some of the newer games at an acceptable framerate without having to turn everything down to low. Games like WatchDogs 2, Mafia 3, The Witcher 3, and whatever else comes out soon. It would be a bonus if it boosts my framerate in TF2.

I had my eyes set on a new graphics card only. Would you recommend either a GTX 1060 or 1070? Which brand? And would I need to change anything else to make sure everything runs smoothly?

Budget is around $650AUD.

Thanks

I'd like to ask about this command again:
cl_pred_optimize 1 // Use optimization mode 1 because 2 has a bug currently

I asked about this one quite a few pages back, and you recommended 2. Could you please explain what this bug is, and what could happen if I was to still use 2?

Also how did you find out about this recent bug? There is very limited information on this command (which I still don't quite understand how it all works) and I'm curious as to how you find out about these things.

Thanks again for putting in the time and effort to maintain this config