Comangliacl_threaded_bone_setup 1
r_queued_decals 1 (especially if you're using more than 9 decals)
You'll get higher FPS on CPUs which can do 4 or more threads (usually Quad Cores or better)
Thanks, I'll modify those to be set to 1 shortly. I'd imagine Chris set them to 0 since they were probably unstable at the time.
You don't need to do this, and leaving that launch option in actually gives you a better average fps after consecutive launches. also -dxlevel 91 should be better optimized than 90 same goes for 81 vs 80
I'll give -dxlevel 91 a try and see if there's any improvement. The reason why you don't want to keep it in there is because when you change the DirectX level, it resets all of your graphic settings in TF2 to the default/recommended ones. I don't have any convars that enforce low settings, I think (other than maybe AA, I need to test this), specifically so that users can control it, so this is relevant.
All hud elements such as cl_showfps and net_graph 1 hurt FPS by about 2-5% each (net_graph 4 eats a lot more than net_graph 1 as well)
Hence why I provided multiple options for viewing FPS. There's no way around that.
I'd also make a separate CFG for laptop users as they tend to have PCs that overheat causing horrible stutters even at high fps, cl_fpsmax 132 should help them A LOT.
What do you recommend to add, then? I'm not really a fan of making multiple configs unless they're drastically different in some way, so perhaps I can make some aliases to toggle between these modes you're suggesting.
NinjaDCThis is a really good opportunity for people to start a community effort to get chris' tf2 configs up to date on github.
It's great that people are suggesting cVars and what works on dx8/dx9 what cVars are obsolete or useless. Also, the documentation on what cVar does is very useful.
I definitely agree. A project like this is the perfect chance to work together on making a config that can supercede Chris' once and for all, and keep this up to date. I plan on being active in this scene for some time, and if not, I'll just transfer project ownership to someone else who will be.
My personally suggestion is that Rhapsody sort the configs into dx9frames, dx8frames and maxframes similar to chris' configs. Additionally, the 'rpc_' aliases should be moved to setup.cfg which users can run from tf2 console if they need an easy way of modifying the fpsconfig.
I'm technically already doing this; after each rpc_ command I'm making it run host_writeconfig, which saves the changes the command made to config.cfg. That's how they persist through restarts. I've commented everything that the rpc_ commands can actually control so that they won't be automatically set upon each restart (so that user settings persist), and if the user wants to modify the config, all they have to do is uncomment the lines.
ComangliaHonestly you don't really need to change much if anything at all between Dx9 and Dx8 frames lol.
Separate CFGs for Systems that either do or don't have CPUs that can handle 4+ threads or if they're using a system prone to overheating.
Ex.
What should I change between these other than cl_threaded_bone_setup 1 r_queued_decals 1 (which probably wouldn't be detrimental on two-core systems anyhow)?