Ok, I updated the config. Is the issue solved now?

Only maxperformance, or does it happen with the default config as well?

The i61 announcement was under "News", but then people were complaining about it so they moved it to "Blog".

awwww shooooo quuuute

4.0.0 beta updated to move the comfig out of autoexec, added maxperformance, maxquality and comp cfgs.

https://github.com/mastercoms/tf2cfg/tree/4.0.0/mastercoms/cfg

Try using r_worldlightmin 0.004.

I just removed textures that didn't exist from the texture preload list in order to speed up game startup time by a little bit.

I updated the config to try and fix the problem in 4.0.0b4, but I'll be able to be better figure out the problem if you could share your specs.

The black texture issue didn't happen to me on Linux, sorry :(. I made it to be default at 0 in 4.0.0b4, thanks for the report.

Hm, so I guess this net_maxpacketdrop is pretty useless if it is only used for timing out from a server. I changed it to 500 in 4.0.0b4. Hopefully that's enough to fix the problems.

New beta autoexec for 4.0.0: https://github.com/mastercoms/tf2cfg/blob/4.0.0/mastercoms/cfg/autoexec.cfg

Has improved organization and comments, as well as better defaults and options.

I'm working on new presets for 4.0.0: maxframes, competitive and maxquality.

I don't know if I should make a lowend/potato/toaster preset because usually what ends up happening is some people think lowend = fast and then use it on their modern/powerful PCs. Besides, there are a lot of variations in accomodating different lowend PCs that probably can't be accounted for in just one preset, so I think it is just better to refer to the documentation to determine the best settings for your PC in that case.

There have been a few controversial defaults in the config as well. Most of you may have had problems with host_thread_mode 1 and wonder why I have it as default when it has issues on local servers. My reasoning is that people will notice their local server games not working and will be reminded to change to host_thread_mode 0, while if it is host_thread_mode 0 by default, there is no reminder to use 1 on multiplayer games for people who do not read the documentation. Of course, I'm here to provide a good config for the community so if most of you prefer host_thread_mode 0, I'll change the default.

hm, honestly i think it would depend on the situation, idk though

good guess! i might have one of the highest, but i'm not very active in many threads and i would expect for my activity in my own thread to die down a bit once my config has been adjusted more.

also im a her

Could you specify what preloading stuff?

It deals only with memory allocations when loading lightmaps. The most likely and noticeable benefits are from load times and memory usage. Access times of lightmap data could possibly be reduced as well.

This problem only happens in a few maps with an abnormally large lightmap lump, so it is best to keep it enabled unless you encounter a map that it needs to be disabled for.

That's documented in the config. Some maps have very large lightmaps that can't be stored in the hunk.

However, most of the time, the hunk has enough space to store lightmaps and therefore that behavior is preferred.

Maybe you used -useforcedmparms -noforcemaccel -noforcemspd in your launch options?

Hm, it shouldn't make them silverish by default. Use mat_phong 1.

Hm, in that case I'm not sure. Here are my best guesses, try these one by one, see which one fixes the issue: mat_reducefillrate 0, r_lightaverage 1 or r_ambientboost 1.

Calling people to test these launch options to see if they cause TF2 to crash or not:

-tools : hacky way to increase graphical quality
-filmgrain : film grain effect

I will probably never recommend these in actual play.

Not entirely sure what has been causing this, but I believe you can work around this issue for now with mat_mipmaptextures 0. I'll try to find out the cause in a few days, sorry about this.