Well, the material system prefers certain video modes of w, h and refresh. Not sure if deviating from those video modes will decrease performance, but it might.

it's sunday

You can also use mat_viewportscale % (% = 0.5 for 50% res, etc) to reduce the game resolution without reducing the HUD resolution.

What preset are you using? Players not showing up might be solved using host_thread_mode 0

On some systems, raw input may cause input lag.

Just drop mastercomfig in your tf/custom folder and it will work.

It's no secret that the glow outline has performance issues, which I believe will be fixed in the next major update. However, that FPS drop is a lot bigger than what I would expect.

mammoth imminent

http://www.youtube.com/playlist?list=PLHy7G7ndrUmq933tLi_nTlFlvmJKZpmAi

EDIT: they were never non-private

also, someone got the thumbnails http://www.valvetime.net/threads/thumbnails-of-new-private-team-fortress-2-videos.257895/

Those aren't errors, those are me forcing values for cheat console variables using dxsupport overrides.

Try using mat_dxlevel then mat_savechanges.

2639 frames 19.082 seconds 138.30 fps ( 7.23 ms/f) 9.900 fps variability
2639 frames 19.023 seconds 138.73 fps ( 7.21 ms/f) 8.932 fps variability
2639 frames 19.048 seconds 138.54 fps ( 7.22 ms/f) 8.677 fps variability

Glad you got it working better. However, I wouldn't recommend net_compresspackets 0, since I believe splitpackets are more CPU intensive than packet compression. Also, I would recommend doing config changes in a new config file exec'd after comfig so that you can easily update the comfig file, and so that you can easily share your own "preset" for others to use.

All of those should help. The less things the engine has to render, the better your performance will be. The biggest performance hindrances are particles and player models/animations so focus on getting those kinds of mods.

4.4.9 enables host_thread_mode by default again.

This command improves FPS by a lot, and I had it enabled by default before but then disabled it due to people asking for help with their local servers, which host_thread_mode 1 breaks.

I've decided that it is best to keep it on because the majority of people probably wouldn't remember to turn host_thread_mode on, but will remember to turn it off if they're in a local server that isn't working.

You may want to use the maxperf preset with the dxsupport_override to help with FPS issues. You may also want to try the -nouserclip launch option. However, I'm assuming this is an integrated graphics card so there's not much we can do for frames.

As for the mouse lag, are you using raw input?

2639 frames 25.869 seconds 102.01 fps ( 9.80 ms/f) 6.549 fps variability
2639 frames 25.672 seconds 102.80 fps ( 9.73 ms/f) 6.013 fps variability

Perhaps try without the -full -w 800 -h 600 -refresh 144 launch options and set your preferred resolution from the video options menu.

4.4.8 released with some minor tweaks to net settings and occlusion.

pyro update (GONE SPOOPY)

Try these launch options

-novid -nojoy -nosteamcontroller -noff -nohltv -softparticlesdefaultoff -reuse -primarysound -snoforceformat -swapcores -high -r_emulate_gl

Any reason you use windowed mode?

Delete everything in your tf/cfg folder, delete all configs you may have in tf/custom, edit all cfgs you have in Steam/userdata/<USER_ID>/440/remote/cfg to be blank, then verify game files.

Finally, launch the game with only the -default -autoconfig -console launch options. In console, enter host_writeconfig; mat_savechanges. Quit the game and then remove the launch options.