NVidia Anti-Aliasing Guide (updated)

I presume it's DX9 because DX9 is the minimum/recommended API according to the system requirements on Steam.

http://store.steampowered.com/app/240760?snr=1_41_4__42

 

DirectX 9

 

I thought so too, but it's actually running Directx 11, you can use the launch/command line option -force-d3d9 to force it back to Directx 9. Also the map seems to have an odd banding effect if you don't enable aa fix.

 

So, I forced it into dx9 and 8xsgssaa with unity flag, but here's not the most excellent result



Total blur. Why is that? It also has some weird effect when zooming in and out.

 

Simply because "0x004000C1" works without blur in some older Unity engine games doesn't mean it will do so in all Unity games.
Perhaps you could try "0x00401045" instead?

Or maybe some post process setting is causing the blur with the "C1" flag?

 

does anyone know how to enable this new dsr in games?is it through nvidia cp?

 

I think you enable it through GeForce Experience but you can tweak it in the NVCPL.

 

I think this is not yet available for fermi/kepler ?

I don't have this feature in latest whql driver...



anyway I believe that Geforce Experience only allows to select the added resolution configured in NVCP.
same as you would pick that res in game.

 

This feature works only with GTX970 and GTX980.

 

at least its officially coming to keplers soon. the end of reconfiguring custom resolutions on each driver install is near. better quality too - what a treat. I'll be waiting...

 

Doesn't look super blurry as much as smooth to me with a little blur. But anyway, try 0x004000C4 or 0x004000C5

Then try 0x004002C1 0x004010C1 0x004012C1 etc

 

If 0x004000C1 is blurry, then 0x004002C1, 0x004010C1 and 0x004012C1 will also be blurry.
Perhaps even more so in certain cases.

It is only the last two digits in the AA flags, which affect blurriness
"C1" generally gives the best AA quality in most games, but can be blurry in some.
"C4", "C5" and "45" variants can then be used/tried as alternatives.

 

No, that's not true at all.

If a certain buffer of a certain kind isn't told to be AA'd it can result in blur (IE: Street Fighter IV 12C1 produces no blur. Where as 2C1 and no bits produce the same amount of blur http://screenshotcomparison.com/comparison.php?id=83038 .)

 

In that post I only see comparisons between "12C1" and enhanced.
No "2C1" or "10C1" pictures.

The "C" part is the real supersampling AA bits, and this is also essentially what is allowing blur-free SGSSAA in most DX9 engines.
The rest of those bits are needed for compatibility and AA quality reasons.

The full truth is more complicated, I know that
But I just wanted to give people a basic guideline.

 

Any flag for Quake Live on Steam???

 

While true. Using 2C1 produces the EXACT same result as enhancing the game.

So /shrug

 

game is probably OGL


Also:

Wasteland 2 OGSSAA http://www.forum-3dcenter.org/vbulletin/showpost.php?p=10361738&postcount=6091

(You could always try 2x2 OGSSAA + a small amount of downsampling in addition.)


And I bought Gauntlet as well, but min specs recommend DX10, so game might be limited to DX11.

 

The "AA fix" is required with Wasteland 2 when you use SGSSAA, it reduces blurring and prevents SSAO glitches.

Wasteland 2

You need to run the game in DX9 mode by adding "-force-d3d9" to the end of the text in the "Target" box in the Wasteland 2 shortcut properties, or by adding it to the games "Set Launch Options" in Steam.

Flag: 0x004000C1

No AA
8x SGSSAA (AA Fix On)
8x SGSSAA (AA Fix Off)

It gets blurrier though the lower the quality of SGSSAA you use.

4x SGSSAA (AA Fix On)
2x SGSSAA (AA Fix On)

You can use "0x004000C5" for less blur but with slightly more aliasing

8x SGSSAA (AA Fix On)

It will be difficult to notice the SSAO problem in the screenshots so I have made a quick comparison video to demonstrate it.



I used 4x SGSSAA for performance reasons.

I also tested OGSSAA and it does indeed produce no blur, it doesn't have the SSAAO glitch either so the "AA fix" is not required.

2x2 OGSSAA
3x3 OGSSAA

Downsampling works aswell but you have to set your desktop resolution to the resolution that you are downsampling from, in my case it was 3840x2160, you just then have to select that resolution ingame.

3840x2160 Downsampled to 1920x1080 (HUD Scale 1.48x)

 

Btw I have now fully updated my new NVIDIA compatibility bits master threads, with all the latest profiles and information from various threads:

NVIDIA compatibility bits master thread and IQ guide (Guru3D)
NVIDIA compatibility bits master thread and IQ guide (3DCenter)

The 3DCenter thread has now been made sticky, and I very much appreciate this
But I still think its Guru3D cousin also should enjoy this honor, in order for the information in this compilation thread to reach a wider audience.

 

Awesome thread :thumbup:

By any chance, is there a good place to learn what each compatibility bit does? Learning how to build them is nearly impossible going off the info provided in Nvidia Inspector. I'm talking about something like "this bit effects 32FP Textures". I see some people in this thread know what to use in specific situations and I would love to learn that too.