6 replies to this topic

[MauttyKoray]

What are the pros/cons and difference of these specifically in MWO? Between FXAA and MSAA I've seen minor FPS differences but haven't really seen much of a change between them, and I haven't used TXAA at all.

All my graphics settings are maxed as well, so I'm using that as a basis for the changes. Not sure if the changes are more prevalent at other settings or not.

[Signal27]

IMO, the only thing that really matters about which form of anti-aliasing you use is what YOU PERSONALLY perceive between the types.

If you need more help making up your mind, these links might help:
https://en.wikipedia...e_anti-aliasing
https://en.wikipedia...e_anti-aliasing
https://en.wikipedia...l_anti-aliasing

I personally prefer FXAA because it seems to be the fastest and I can hardly tell the difference between FXAA and all the other types of anti-aliasing unless I take screen shots and compare - and that doesn't really matter to me when I'm already focused on stomping around the battlefield trying to blow up other people's robots.

Edited by Signal27, 19 December 2015 - 04:17 PM.

[Navid A1]

FXAA: a post process effect. Blurs textures as well, but super fast!

MSAA: multi sample AA, high quality AA with no texture blur, demanding on hardware!

[YourSaviorLegion]

MWO's Texture filtering is poop, you'll do a lot better with it off

[Goose]

MauttyKoray, on 19 December 2015 - 03:52 PM, said:

Between FXAA and MSAA I've seen minor FPS differences but haven't really seen much of a change between them, and I haven't used TXAA at all.

How many cards are you using?

YourSaviorLegion, on 19 December 2015 - 05:59 PM, said:

MWO's Texture filtering is poop, you'll do a lot better with it off

Which has what to do with the question, even if your point was accurate?

[YourSaviorLegion]

Even TXAA/MSAA blurs textures in the distance for some reason in this game. They're not worth using if you value being able accurately see past 500m in game

[Goose]

… The Anisotropic filtering gets turned down at a distance by default: Ether force it to 16x in your driver, or else add

r_TexMaxAnisotropy = 16
r_TexMinAnisotropy = 0
r_Texture_Anisotropic_Level = 16

to your user.cfg