9.3.2 released with bug fixes.

Changelog
Support me

This release took 2 hours to produce. If you like the work I do, consider supporting me!

9.3.1 released with performance improvements and bug fixes.

Changelog
Support me

This release took 10 hours to produce. If you like the work I do, consider supporting me!

That it segfaulted is pretty useless information, it technically narrows it down a bit, but you might as well anyway be saying it crashed. Seeing stdout is not what a debugger is used for. You can do that in other ways.

What a debugger is actually used for is breaking into the code, viewing variables and the stack, and in some cases, rewind in the case of time travel debugging with something like rr or WinDbg. However, as was said before to you, since you do not have debug information, it will be very hard to debug the program without very good experience with programming and especially assembly.

Also, I think in these cases, you will find Valgrind more helpful than simply using gdb.

That's strange, could you list everything you do explicitly to reinstall?

Yeah, stuffcmds doesn't work for non game DLL cvars anymore.

Anyways, RSS feed, you can use GitHub afaik

r_threaded_renderables
r_queued_decals
r_queued_post_processing
cl_threaded_client_leaf_system
cl_threaded_bone_setup

Only the r_queued cvars do anything in the current live build, so changing the values of any of the other ones would not do anything. Plus, mastercomfig does not set any of these, so if the only thing they did was update to the latest version, these would not change anything.

9.3.0 released with performance improvements and bug fixes.

Changelog
Support me

This release took 22 hours to produce. If you like the work I do, consider supporting me!

SSDs can help with dynamic model loading (cosmetics) and some sound loads.

Just use whatever you want and what works best for you! I don't recommend against DX8.

I just haven't had the time to properly explain it in the docs, since users have the tendency to pick the perceived lowest option even if it's worse for them. So, I've relied on DX8 being known in the community elsewhere to pick up the lack of documentation within the mastercomfig docs regarding this.

I simply only want DX9 to get a fair chance and people to try it and see if it works for them rather than automatically going to DX8. If it doesn't work as well for you, that's totally fine and understandable!

Yeah just in console enter cvarlist mat_motion_blur

mat_colorcorrection
mat_hdr_level, 1 is bloom, 2 is bloom + HDR
mat_dxlevel
mat_motion_blur_enabled

Aren't all of these documented (if they are at all useful) on mastercomfig docs?

https://docs.mastercomfig.com/en/latest/customization/launch_options/
https://docs.mastercomfig.com/en/latest/tf2/silly_launch_options/

-softparticlesdefaultoff is controlled by mat_reduceparticles 1, no reason to use the launch option really
-noff doesn't do anything, force feedback is never attempted to be initialized.
-gl_texclientstorage isn't a good feature, enabling it does the opposite of what you described. Client storage refers to storing textures on the client, i.e., not the GPU.
-soft doesn't exist, did you mean -mat_softwaretl?

UVF has a known crash, neither the author or I are sure why. Particles can't be preloaded.

Also, you can use the -condebug launch option to log the console to console.log, but usually crashes or their causes are not recorded to the console.

College can help a lot with getting a job, but it's obviously not the only path to getting a job. But if you don't go to college, you have to make up for it a lot with solid networking, applying for tons of jobs, and having strong outside stuff on your resume. Disregarding the job stuff, education is good for you anyways, even if you don't get it at college. It'll help you perform well in your life and job. You seem like an eager high school student, put your energy into research and learning and then you can come back to stuff once you've built up with learning and practice!

You found some new launch options. mastercomfig has already been documenting the live game's launch options and which ones to use for years.

In Source and Steam, DNS names are resolved once on connect/query. Then it uses the IP directly. Each packet send does not resolve the domain name again.

Did you think that it was resolving DNS 66 times per second or something? How would it affect performance?

Also, I don't mean to discourage you from trying new things, but I do encourage you to learn, and collaborate with others rather than spontaneously release something like this, with information against what others have advised before.