NVidia Anti-Aliasing Guide (updated)

thanks! hmm is there any reason why we have to turn off Behaviour Flags? (as in I'm not questioning just trying to understand how it all works)

or if there's a good guide I can read up on - that would be great too

 

The Behavior Flags option is pretty self explanatory. Some game profiles will have it set to something like "Treat Override as Application Controlled", in other words changing Antialiasing - Mode to Override does nothing. You need to have it set to None so you can force AA again.

 

thanks thank you so much
ah so it's like a superset/universal setting that affects all the AA options
disabling it to None allows me to change individual settings
- trying to rephrase it in a way that makes sense to me lol.

----
the only thing left is trying to figure out what the plethora of AA options - what each of them does... and etc :/

 

As I pointed out to someone else just like 20 min ago.
Typically, you are going to want to stick with 2x, 4x, and 8x Multisampling (MSAA). If you want SGSSAA you need to select the matching (4x MSAA = 4x SGSSAA) Sparse Grid Supersampling from the Transparency Supersampling drop down.

 

It's worth noting that if you are trying to force AA from NVidia inspector, unless GeDoSaTo is running at a resolution you can use as a desktop resolution (And be used as "present resolution" in GeDoSaTo) forced AA will not work.

 

I understand you because I have faced same situation with Evil Within..it was weird as hell ! Though that issue was with my two 460s,not with my 970 and not very choppy as you described,without AB osd active=annoying stutter all the time, with AB's OSD on screen active no stutter at all,smooth 60s all the time. One of the weirdest stuff, I know. It has to be something with driver(?).

 

How can I activate MFAA, does the game engine need to support it ?

 

Silent Hill Homecoming flags are performing really bad with latest drivers, reverted back to 347.25 and it's all smooth again, flags behaviours are changing with each driver release :bang:

 

I wouldn't say flags, simply because the function of the bits do not change. Which means something else has somehow caused the problem

You can submit a bug report for this here https://nvidia-submit.custhelp.com/app/ask (Need to be logged into an Nvidia account to access it)I don't know what any good it will do. But it can't hurt to try.

I would also try removing that 2 that the OP of that post used in the flag

 

Game has to be DXGI(DX10 and above) and have native support for MSAA within the game unless you can force it in inspector (Unlikely given DX10 support is non existent)

 

Yes you're right, having osd enabled the issue is gone, I've monitored the gpu usage and clocks but haven't noticed anything abnormal, rivatuner is a new requirement to play games with custom aa flags. :infinity:

 

I have the little known game The Maw, but I have a couple conflicting sources regarding a working AA flag for that game. I experimented with 0x000010C1 which seemed to work well, but this SPUF thread indicated that 0x080100C5 also worked. It seemed to make no difference, but I'm not well-versed in the details of AA flags to know what to look for.

 

Neither of those flags work for me. Tried 16:10 3840x2400 and 16:9 1920x1080 as some AA flags only work with the latter screen aspect ratio.

I have been trying for ages to find a working AA flag for The Maw since I bought in a Steam Sale a couple of years ago. I see jaggies on the title screen and in-game.

Can you post your NVIDIA Inspector profile please and tell me what resolution you are playing the game at. The executable seems to be Maw.bin because I have to use that file if I want a custom Afterburner OSD for the game and it is needed because I have to play the game at 3840x2400 (using DSR @ 1920x1200) in order to mask the jaggies.

 

try enabling the OSD compatibility for the .exe but turn "show on screen display" to off. See if that helps

 

Latest Windows 10 build (10158) won't display Guild Wars 2 in fullscreen, if using SGSSAA (0x084012C0). The game will simply hang and then has to be closed via task manager. Considering the bits still work (beautifully) when starting the game in windowed mode and the game itself works normally in fullscreen if not using AA, I was wondering if there's a known set of bits I could try to change to improve fullscreen compatibility. Any clues?

 

Are you sure you're not forcing CSAA or something like that as I found a few of my games hanging because I was forcing 8 or 16xCSAA, which is not supported on Maxwell. Once I changed it to 4xMSAA or 8QxMSAA then the games loaded and worked fine.

 

A little update, in case someone gets in a similar situation.
Apparently the culprit was the xbox app that comes with win10. Previously i never incurred in the problem just cause i would remove it as soon as i finished installing the OS (via powershell). Now it can't be removed anymore, so i went in its settings and disabled the game dvr option (which is active by default). Problem solved. Ty anyway for your support .

 

thanks, but it didn't worked, can't find the source of this issue, using 34x.xx is the only fix I've found.

 

Report it to Nvidia, I posted the bug report link a few posts back. It's really the only thing you can do.

The 8 in the 2nd slot is the only thing that could improve fullscreen compatibility.

Aside from maybe 0x00000004, 0x000000E0 (This includes the function of C)

 

Ugh that's stupid