It's the nature of using deferred rendering.īasically think of it like this (back story): It is not a flag sent to the driver to turn off FSAA.

I still really want true anti-aliasing anyway though.) I found GemFX which seems to work in 10+ and apparently even works in Windows 8+, but SMAA is permanently grayed out no matter what I do. To this end, I wonder: might there be some way to block this? I'm getting very fed up with FXAA and even SMAA has its limits in the things I can try to force it into using the likes of SweetFX (not to mention that SweetFX isn't even compatible with DX10+. Or even if this method worked back then it doesn't now because I tried and couldn't fool it apparently.) I've been wondering if games essentially send some sort of flag to the drivers that tell them to turn off FSAA even if it's set to forced. (In fact, I saw one guide suggesting renaming games to things like 'Bioshock.exe' to try to trick drivers, but they were using nVidia.

This seems to go in league with everyone trying to force us to switch to cheap shaders like FXAA (which I'm guessing are much more console friendly since FXAA requires little by way of resources in comparison even to the far superior SMAA.) Given that FSAA works at the 3D level though, I find it inconceivable that FSAA is truly 'broken' or would actually cause problems. So one truly fun feature I've noticed in all modern games is that even if you set the drivers themselves to force FSAA the setting will be ignored.

How to use sweetfx directx 12