#Msaa on linux - clarification
1 messages · Page 1 of 1 (latest)
some relevant benchmarks i just did, using mcoms own file and an r5 3600 - rx 6600 configuration:
anti_aliasing=off: 266 fps
anti_aliasing=msaa_8x: 267 fps
```so, either this got fixed in the driver or in newer cards, _OR_ i am tremendously cpu bound. what can i do to further investigate this?
idk, looks like normal cpu bound fps
or it's disabled in the driver
How are you changing between runs?
i'm exiting the game, editing modules.cfg and re-launching; presence / absence of 8x msaa is pretty noticeable, i would have realized if i had a bogus run
try with really big resolution
Give source to docs in question, could be outdated info from 2013.
its been in "latest" docs for about a couple years
will do, but can i just set -w and -h in launch options? do i need to scale the desktop environment?
depends on your driver and compositor/display environment
alright, i can't seem to set the resolution higher than native in a way tf2 recognized (i tried gnome both xorg and wayland), even if i use scaling 2x2 tf2 still won't go above native, and i can't set a custom higher resolution via xrandr because it doesn't allow me to
i'm giving up for now, if someone that isn't cpu bound and has an amd card is willing to try this is more than welcome
however this shifted a bit from my original question because of the benchmark, but it still stands: how did you realize amd cards do a slow full clear when using msaa? i can't really find much online apart from users in forums mentioning it
in the source engine