WietHUD :)

why do you recommend removing "-dxlevel x" from launch options after first launch? whats wrong with always having it there?

it makes the game launch slower

Also it keeps resetting your config
just put it in, open once with the -dxlevel launch option
close it
then remove it

guys i just wanted to let you know capitalism isn't all bad

hey mastercoms! two questions

do you know any commands that would improve visibility through pyro flames? i literally can't see anything if a pyro sprays in front of me rn.

also is there any way for boosting the brightness of players in dark areas (i.e. under badlands mid in that corner of the bridge) or should i just up my monitorgamma

edit: should note i'm using the standard launch options + comp config

next is hypnotize’s hud thread, but should we push our luck??

Well, there's a glitch with cl_particle_batch_mode 2 where it sometimes skips drawing the main flame particles. But besides that, I don't really know of anything that would help.

You can change r_worldlightmin to its default of 0.0002, at a slight performance decrease. There's also r_ambientboost 1, which boosts lights on models. It has a small CPU load increase.

You can also use mat_phong 1 and r_rimlight 1, which enhances reflectivity and enables lighting on model edges. Comes at a GPU load increase. Though, I don't think that's what you're looking for.

Of all the DirectX 9 options which one is the best in terms of stability and performance?

Depends on your GPU.

Hey, thought you guys should know, i've got a FPS boost, maybe you guys should try

This ^ Was on DX9 after i've put some custom commands on my custom CFG (Using "exec custom" on mastercfg)
Before the custom commands (Still on DX9)

Here are the custom commands:

r_occlusion 0
r_3dsky 0
net_compresspackets 0
net_splitrate 1
r_ambientboost 0
r_lightaverage 0
r_flex 0
flex_rules 0
r_teeth 0
r_dopixelvisibility 0
snd_mixahead 0.2
dsp_slow_cpu 1
snd_spatialize_roundrobin 3
dsp_water 0
r_queued_post_processing 1
r_drawtracers_firstperson 0
r_renderoverlayfragment 0
r_decals 0
props_break_max_pieces 0
snd_pitchquality 0

I don't really know witch command helped the most

Question, is there any benefit for "-heapsize xxxxxxx", "-gl", "-32bit" Launch options?
Do they even work?

Hello, I started using this config because I was getting an odd issue after Scream Fortress 2017 that I would drop from 150-250fps in spawn to 70-80 once enough people were within view. Even when using other configs that would boost my initial fps these exact same drops would occur. Another oddity I've noticed (even with this config) is that after respawning, my framerate in spawn will be somewhere from 100-150, but after 5-10 seconds will suddenly jump all the way to 250+. Could this have something to do with the above issue?
Anyway, not only has this config made everything appear smoother and cleaner apart from the increased framerate (which I have no idea how it did), this issue has also been fixed in almost every situation, though I'd still like to know why it would happen if anyone has an idea.
EDIT: The above drop to 70-80 still happens but only if I leave spawn before my framerate jumps back up to 250+. Is something being cached and cleared by this config that normally isn't?
EDIT2: Just realized this is related to the spawn wallhacks. As soon as the player outlines disappear my framerate skyrockets (it was still constantly low without this config)

However, 2 things I don't like are these visuals here:
https://imgur.com/a/Qf3BT
All of the characters have very simplistic lighting on the tops of their heads which makes them appear sort of gray, and there's odd blue lights on the floor in Turbine.
What commands can I change to remedy these, and what sort of performance hit can I expect from it?

Specs:
Windows 7
GeForce GTX 970
i5-3570k @3.4GHz
8GB RAM
Running at 1920x1080 on 144hz monitor

Yeah i belive that's rimlighting, as in the command r_rimlight 0/1
you can change that on console while checking your loadout, see if that's it

Probably snd_spatialize_roundrobin 3, r_3dsky 0, r_flex 0, dsp_slow_cpu 1 and flex_rules 0, which are all used in comp.cfg with the exception of snd_spatialize_roundrobin 3 since it delays sound spatialization.

About r_occlusion and r_dopixelvisibility, I've been benchmarking these to find out which is better on modern hardware, though I expect r_occlusion will be best set to 0, and r_dopixelvisibility is best set to 1 (due to building_cubemaps 1).

Seeing as those launch options don't exist, I would say there is no benefit.

There was supposed to be an optimization patch to outlines, but I guess it didn't get in this major update.

It would be helpful if you could share your preset. But, assuming you're using comp, the simplistic lighting is from mat_phong 0, so set that to 1 if you want more complicated lighting. There's a pretty decent impact on GPU load, but your 970 should be able to handle it well.

I'm not sure about the blue lights on Turbine, though it might be caused by building_cubemaps 1. This cvar is quite extensive and affects a lot of different graphical features, so the performance impact from setting it back to 0 can vary quite a bit.

By preset I'm assuming you mean which of the 3 folders I installed, yeah? I'm using the regular "mastercomfig" one.
mat_phong was causing that, forgot that I had used it a long time ago before switching to r_rimlight but thanks for the reminder.

Do you have any idea what could've been causing the consistent drops from 150+ down to 70-80 even when outlines were gone? It seemed that every config I used before this one, no matter how extensive, still had that issue but only after Scream Fortress 2017 dropped.

I meant which presets you execute from this section in the mastercomfig_exec folder, or in your own autoexec.

I wouldn't really know since I made my config from scratch and haven't really analyzed other configs to find those sorts of issues. But if I had to guess, probably something to do with the filesystem cvars.

what's the best dxlevel for a 960m? and would the dxlevel I run my game at be lower too if I were to stream and want to keep around the same amount of fps?

Oh my bad, I left everything default so all of these are still commented and I hadn't executed anything (apart from the main config file).

This issue was occurring even after resetting my game back to default, so it's not just something resulting from other configs. Either way I'm not too concerned about it since you've solved it through your config but it's always fun to figure out why.
I really appreciate you making this config and commenting it so well because I haven't seen the game run this well since launch and it's good to be able to understand why it is.

EDIT: By the way I notice you have -nogammaramp listed as a "niche" launch option, but from what I've read this is disabled in TF2. It would be majorly helpful if you know of a way to enable it or some similar effect because my monitor stinks without my .icc profile and I'm forced to play in borderless window.

Probably 95, but I can't really know for sure.

That's fine! Using no presets is a valid option too.

Well, even the default filesystem cvar values aren't very optimized.

thank you so much for the kind words <3! I'm glad you're finding it to be working well!

To be honest, I didn't really look into this launch option. It was added by someone else and upon further investigation, it seems like it isn't in the Source Engine anymore. Thanks for pointing to this error. I've now corrected it.

As for your problem, I'm not sure of another way to enable it. Maybe r_shader_srgb -1/0/1? I'll try to look around and see if there is anything else.

r_shader_srgb -1/1 seem to just make the game extremely dark. By opening the steam overlay I can easily see that the .icc profile has been overridden. Don't quote me on this but I'm guessing that these may refer more to Nvidia color management rather than desktop.

I've added -nogammaramp but I haven't used any .icc profiles nor the switch for nearly 2 years so perhaps it was removed in the meantime. It used to work for majority of source based games though. I've tested dota2, csgo, dear esther, black mesa, portal 1+2, tf2, insurgency and so on.

I'm afraid the only way to force an .icc profile would be to use some sort of an injector but that might trigger VAC so be careful.

That's what I've read and it's not a really good risk to take just to not have to play in borderless window. At least with desktop composition disabled I'm not really experiencing any noticeable input delay.

just tried a couple more maps with this config, still getting random drops to ~80 on koth_sawmill and banana bay for example. I disabled player outlines so I don't know why this is happening.

5.0.3 released with optimizations and documentation improvements.

Maybe 5.0.3 will help.

Also, you can try out the comp preset for more performance.

Still getting the same drops in the same problem areas with 5.0.3. It seems like only a few specific maps have been truly fixed by the default config.
I'll try the comp preset out tomorrow and report back, though I suspect I'm probably just hitting some CPU bottleneck (hl2.exe total usage is ~50% and Core 0 is almost maxed out). My friend with the same GPU, CPU, and monitor has almost the exact same issues.
80-90fps is by no means unplayable but the dips are jarring and make aim smoothness inconsistent.

What launch options are you using?

-windowed -noborder -novid -nojoy -nosteamcontroller -noff -nohltv -softparticlesdefaultoff -reuse -primarysound -snoforceformat -swapcores

Before the config I was just using: -windowed -noborder -novid

If possible, set borderless windowed in the video options. The launch options have been reported to lower FPS. You may also want to look into using -high.

Also, are you using any external programs or Windows settings like Game DVR, high performance power plan, window optimizations or Game Mode?

Borderless windowed isn't an option in the settings, but I can remove -windowed. I tried -high for a bit and didn't really notice any difference. I'll try running one of the benchmarks with and without it if I get a chance.

I'm using a high performance power plan but haven't tried messing with these performance options: https://i.imgur.com/q0GEghj.png
I'm also disabling desktop composition and display scaling on high DPI settings for hl2.exe.
I should note again that my friend with basically the same build but runs in fullscreen without disabling those 2 things is having the same issue in the same places.