I tried looking around and couldn't get the exact areas (maybe it's just something with thirdperson), if you could give me some screenshots, it would help a ton!
Account Details | |
---|---|
SteamID64 | 76561198046110893 |
SteamID3 | [U:1:85845165] |
SteamID32 | STEAM_0:1:42922582 |
Country | United States |
Signed Up | August 8, 2017 |
Last Posted | May 29, 2025 at 11:21 PM |
Posts | 1557 (0.5 per day) |
Game Settings | |
---|---|
In-game Sensitivity | |
Windows Sensitivity | |
Raw Input | 1 |
DPI |
|
Resolution |
|
Refresh Rate |
Hardware Peripherals | |
---|---|
Mouse | |
Keyboard | |
Mousepad | |
Headphones | |
Monitor |
So if you have an autoexec in cfg in the custom folder, it will likely override mastercomfig. So that's why that isn't working.
I'd recommend referring to the installation instructions: https://docs.mastercomfig.com/en/latest/setup/install/#custom-configs.
i.e., you need to create a user folder in cfg and then move your own autoexec in there.
Also, I would recommend using the mastercomfig transparent viewmodels and null cancelling movement addons instead of the autoexec settings.
mlnsplayers become really dark in shadowed areas for me, any ideas on what it might be?
using the latest release on low preset, didn't happen before that
I'll adjust this in a future release. My intention for low was to only remove lighting that wasn't substantial. If you could share maps and locations where this bug happens, it would help a lot more. Thanks!
That dust cloud seems to be from incorrect surfaceproperties definitions. Check to see if you still get them when you remove any possible mods that modify them, and then if that helps, try redoing your surfaceproperties files with your intended changes. Also, mastercomfig has settings which disable bullet impact effects (they won't work in a raw autoexec), excluding the sparks which are player blood effects being replaced by their low violence equivalents (caused by violence_ cvars being 0).
8.104.2 released with bug fixes.
This release took 2 hours to produce. If you like the work I do, consider supporting me!
mastercomfig 8.105.0a1 released in early access:
Could you set these commands: sv_cheats 1;mat_debugalttab 1
And then share the output in console after alt tabbing? It might clear up what's going on with the latest driver.
8.104.1 released with bug fixes.
This release took 2 hours to produce. If you like the work I do, consider supporting me!
Updated recommended launch options to -novid -nojoy -nosteamcontroller -nohltv -particles 1
8.104.0 released with performance optimizations and bug fixes.
This release took 34 hours to produce. If you like the work I do, consider supporting me!
Updated recommended launch options to -novid -nojoy -nosteamcontroller -nohltv -particles 1 -disallowhwmorph
One of my favorite people in the TF2 community, cheers to whatever is next! And I'm sorry that these toxic people targeted and hurt you.
mastercomfig 8.104.0a5 released in early access:
https://www.ko-fi.com/post/mastercomfig-8-104-0a5-N4N21ZGYM
wonderTried all your tips and my game still crashes. I played many maps last days and It crashed only once but still. I noticed it crashes only during scrims/officials (when I play on servme servers). It doesn't crash when I play pugchamp/pickups (polish pugchamp) for example.
Could you try updating mastercomfig? Some work was done on memory in 8.103.0.
mastercomfig 8.104.0a4 released in early access:
JulezHave you considered making a version of the config that is optimized for good PCs? I've been using some modified version of the comanglia config where a bunch of the settings were actually turned to high, and it gave me better fps than any of your configs. Had to go back to using your medium-low config though, because the game feels more responsive on it for some reason. Like I can land more shots and aim better.
The whole purpose of mastercomfig is to be optimized for good PCs. I'd be interested in learning about your specs and how you measured performance, and if you compared the same graphical settings and dxlevel as with mastercomfig.
Did this start happening with an update? What version of mastercomfig do you have?