This is a longstanding issue i've had with the script. I've had to manually fix it many times and appears again every time i update. Adding anti_aliasing=msaa_8x in modules.cfg fixes the issue, but according to the site 8x should be the default option, idk why it instead defaults to off requiring manual intervention.
#High preset anti-aliasing should be MSAA 8x by default but is actually set to off
river radish
nimble zenith
that's interesting and sounds like a real problem, someone will be looking into this
river radish
if need be i can provide more info, perhaps it's due to the fact that i customize anisotropic filtering to 16x instead of the default 8x?
at any rate i have to sleep now so if more info is needed you're gonna have to wait at least 8 hours unfortunately
marble kettleBOT
@river radish has leveled up! (0 ➜ 1)
nimble zenith
if need be i can provide more info, perhaps it's due to the fact that i customiz...
what version of mastercomfig are you using and can you send a zip of your custom and cfg folders?
last cairn
I'll take a look
last cairn
@river radish I analyzed relevant files and it should be msaa_8x for the high preset by default
it's probably a custom config. issue on your part
nimble zenith
they didnt even post any files what
ruby summit
I think Tiagoquix is saying mastercomig looks all good
last cairn
yes, I'm saying about the mastercomfig config files themselves
ruby summit
I also tested the 9.10.3 and dev mastercomfigs earlier when this was posted and both set msaa 8x fine by default on the high preset
last cairn
they are fine
I have analyzed develop, release and staging branches
everything is as it should be
river radish
they didnt even post any files what
i was sleeping, i will post now
the last zip is what i got from the website
the cfg has the 8x override that fixed the issue
the custom stuff i have is just hitsounds, killsounds, toonhud (latest) and we'll be right back freezecam
river radish
that's odd, if i force it on with the override it works just fine
that may be the cause, i forgot it did that
but still, it works fine if forced on
i will mark the thread as fixed, but it might be good to check if it's necessary to disable anti aliasing for transparent viewmodels, it may be that long ago they broke but valve fixed it in an update, because if i force it on with the override or using the ingame console it does apply and transparent viemodels continue to work
ruby summit
Transparent viewmodels in tf2 are just bad all around. They probably hurt performance, they create visual bugs, and they require weird motion blur and antialiasing settings.
If the transparent viewmodels are working fine with msaa enabled you could submit a simple PR to mastercomfig on github, removing the anti_aliasing=off line from the addon
river radish
i don't feel comfortable doing that, i am a lone case using a custom hud so it may be just my setup, would need more testing
river radish
yeah i hope i'll remember the override next time