NVidia Anti-Aliasing Guide (updated)

Just another official AO profile failure by Nvidia of course!
 
GuruKnight said:
This is most likely caused by the official AO profile (0x00000030).
Try using 0x00000021 instead for HBAO+.

Also make sure FXAA, SSAO and Film Grain are disabled ingame when using driver SGSSAA and HBAO+.
If you are using some type of custom ENB effects, also disable these for troubleshooting.
Click to expand...

Thanks, 0x00000021 fixed it.

But why do you suggest to disable the ingame SSAO option?

Using that together with the 0x00000021 makes it look better no?
 
No, it defeats the point. You don't need 2 AO techniques competing with one another to do the same job. It doesn't look right either.
 
MrBonk said:
No, it defeats the point. You don't need 2 AO techniques competing with one another to do the same job. It doesn't look right either.
Click to expand...

Ok.

Which do you think is better to enable, the ingame SSAO or the 0x00000021 HBAO+ enabled through nvidia inspector?
 
HBAO+ is obviously the better choice if there are no bleeding or flickering issues.

But really, just use what you prefer. If you are fine with the in game SSAO and don't notice it's problems. Then that's ok too.
 
Mobius Final Fantasy has launched on Steam. And of course it's another SE FF port without FSE support. But only in DX11. Luckily the OGL mode seems to use either FSE or some strange borderless windowed mode that mimics FSE. As it allows VSync to be overridden in NPI. Which is great for Windows 7 users. And maybe everyone else if you happen to notice that DWM is doing a bad job Vsyncing the game.


HOWEVER, do not force AF through the drivers as for whatever reason it results in garbage on the screen :( Luckily the game seems to use 8-16xAF by default. So it isn't too much an issue.


Also: This game runs on Unity, and uses Unity's new Temporal AA that is basically a copycat of UE4's TAA right down to the same issues it has. (Ironic don't you think? What with Unity trying to compete with UE).

So fast motion makes it fall apart, edge quality on certain objects over time can be worse than with the default FXAA. As well it handles clamping objects very poorly. Resulting in ghosting,trails, sharp edges where the rest are AA'd very well. It's not incredibly noticeable in motion though depending on the scene. Fast motion also makes the technique falter fairly bad. Though you'd probably have to be using a CRT or LCD with a strobed backlight mode to notice.

The other thing it pilfers from UE4's TAA, is that it takes parts of the scene and does whatever the heck it does to make it look all smudgy and ****.


Both the default FXAA and TAA are viable with downsampling.



Pictures:
OGL AF forced https://abload.de/img/mobiusff_2017_02_14_0kisn7.png
Clamping problems https://abload.de/img/clamping2ebsp0.png https://abload.de/img/clamping9fs6s.png
Fast motion https://abload.de/img/asdfe9isf6.png (First is no motion or slow motion. Looks decent right?)https://abload.de/img/fastmotionidsu7.png https://abload.de/img/fastcusvv.png
Smudgy looking graphics https://abload.de/img/smudges3rwsm2.png https://abload.de/img/smudgesw1s2h.png
 
MrBonk said:
HBAO+ is obviously the better choice if there are no bleeding or flickering issues.

But really, just use what you prefer. If you are fine with the in game SSAO and don't notice it's problems. Then that's ok too.
Click to expand...

Thanks.

GGGGGRRRRRRR

0x00000021 HBAO still has the Nintendo 64 style mushed graphics through opaque fog on some levels :(



free unlimited photo hosting

I just wanted SGSSAA :(

If noone knows a better AO, how can I disable nvidia inspector HBAO and just leave the ingame SSAO enabled? I think it shouldn't mess with the SGSSAA enabled through the nvidia inspector.
 
You can try to check other UE3 flags or try playing the game at a different aspect ratio or resolution to see if the bleeding changes. (It does happen). (Also make sure the in game SSAO is still disable too, just to make sure it's not messing with anything)

If you are using Windows 7 or 8, you could probably hex edit the files to fix the bleeding.

But if you just want to disable it, then make sure the Ambient occlusion setting is set to "Off" and not "Quality" or "High Quality"

Would you mind posting a screen of your NPI set up?
 
@gold333

Interesting about the "0x00000021" AO flag.
However it really is the only option available, since "0x00000030" applies no AO effect whatsoever and bleeds through just about everything.
"0x0000002F" also works, but flickers.
 
MrBonk said:
You can try to check other UE3 flags or try playing the game at a different aspect ratio or resolution to see if the bleeding changes. (It does happen). (Also make sure the in game SSAO is still disable too, just to make sure it's not messing with anything)

If you are using Windows 7 or 8, you could probably hex edit the files to fix the bleeding.

But if you just want to disable it, then make sure the Ambient occlusion setting is set to "Off" and not "Quality" or "High Quality"

Would you mind posting a screen of your NPI set up?
Click to expand...

I disabled ingame SSAO. Still same result.
I like 1920x1080, don't really wanna change for this AO type.
I'm on Win 7 but don't really know how (or why) to hex edit.

Sure, here is a screenshot of the NIP:

delete.jpg


I never really minded the ingame SSAO. If I turn off the ambient occlusion in NVI the ingame SSAO should still work right? I don't understand because there are TWO settings for turning AO off in NVI:

Ambient Occlusion Setting - OFF
Ambient Occlusion Usage - DISABLED

I wonder what the difference is.


I actually just wanted a working SGSSAA in A:CM. I'm getting conflicting advice though. Different people in the previous years have said:

1. Borderlands 2 - 0x200012C1

2. 0x00001045 (Brothers In Arms: Hell's Highway, Qiang Shen Ji, Aliens: Colonial Marines)

3. 0x080010C1

Are the best.

I wonder which of these three is really the best bit for SGSSAA in A:CM?
 
Last edited:
gold333 said:
1. Borderlands 2 - 0x200012C1

2. 0x00001045 (Brothers In Arms: Hell's Highway, Qiang Shen Ji, Aliens: Colonial Marines)

3. 0x080010C1

Are the best.

I wonder which of these three is really the best bit for SGSSAA in A:CM?
Click to expand...

Ok to answer my own question I tested myself:

0x00001045 is terrible, black edges everywhere and 15 fps
0x080010C1 and 0x200012C1 are good. Pretty much the same though I think 0x200012C1 gives slightly higher average FPS.

Even at SGSSAA 4x the aliasing looks good. I turned off AF and multisamples in the INI but I don't think it makes an FPS difference. These are NVI HBAO disabled and just ingame SSAO.





Edit:

Actually I was wrong,... Nvidia HBAO+ (0x00000021) looks alot more real than the in game SSAO. See comparison pics below. Top in game SSAO, bottom Nvidia HBAO+. Shame about the fog on some levels. I guess the search for a better HBAO flag goes on.


 
Last edited:
@gold333

You really don't have to go through all of this for Colonial Marines.
Blaire and I (SLIKnight) have already tested SGSSAA, HBAO+ and SLI in this game in the 3DCenter forums.

The best possible solutions are 0x080010C1 for SGSSAA and 0x00000021 for HBAO+, which is also what is in my NVIDIA master list spreadsheet:
http://forums.guru3d.com/showthread.php?p=4908843#post4908843

There are no other high quality solutions, trust me I have tested the game extensively.
Those bleeding problems also seem minor in my opinion.
 
GuruKnight said:
@gold333

You really don't have to go through all of this for Colonial Marines.
Blaire and I (SLIKnight) have already tested SGSSAA, HBAO+ and SLI in this game in the 3DCenter forums.

The best possible solutions are 0x080010C1 for SGSSAA and 0x00000021 for HBAO+, which is also what is in my NVIDIA master list spreadsheet:
http://forums.guru3d.com/showthread.php?p=4908843#post4908843

There are no other high quality solutions, trust me I have tested the game extensively.
Those bleeding problems also seem minor in my opinion.
Click to expand...

Yeah, I quit messing with it. You're right. Thanks for your efforts as always.

Though in my testing 0x200012C1 looked identical to 0x080010C1 and seemed to give slightly higher average fps. Why did you guys not choose that for the master list? Flicker?
 
Little King's Story

0x000000C1

Use AA fix to make sure light source bloom works properly.
Do NOT use in game Post Processing, big performance hit, and increases aliasing on objects with heavy DoF/Bloom
To use DSR you have to have your desktop set to DSR resolution first.
Correct Vsync in Windows 7 requires Aero to be enabled
If you are going to use AA at display native. Just use the in game 8xMSAA and TRSSAA option. Not much difference from SGSSAA to be worthwhile for the performance hit.
If you are going to play at a very high resolution or use downsampling, you might want to use NPI MSAA instead of In game MSAA.
The in game MSAA for some reason wants to use a ton of VRAM, even 2xMSAA at 3200x1800 pretty much filled a GTX 980's 4GB and caused the performance to drop massively.
NPI MSAA does not do this and looks 100% the same


NoAA http://u.cubeupload.com/MrBonk/b54NoAA.png
In game 8xMSAA http://u.cubeupload.com/MrBonk/ingame8xMSAA.png
Driver 8xMSAA http://u.cubeupload.com/MrBonk/385C18xMSAA.png (Notice light bloom is reduced. This is without AAFix)
In game 8xMSAA+TrSSAA http://u.cubeupload.com/MrBonk/ingame8xmsTrSSAA.png
8xSGSSAA http://u.cubeupload.com/MrBonk/8xSG2.png
8xSGSSAA with PP http://u.cubeupload.com/MrBonk/8xSGwithPP.png
32xS enhanced (Not worth it) http://u.cubeupload.com/MrBonk/8xingameenhance32xS.png
2x2 DSR+4xSGSSAA http://u.cubeupload.com/MrBonk/2x24xSG.jpg
 
gold333 said:
Yeah, I quit messing with it. You're right. Thanks for your efforts as always.

Though in my testing 0x200012C1 looked identical to 0x080010C1 and seemed to give slightly higher average fps. Why did you guys not choose that for the master list? Flicker?
Click to expand...

Technically "0x000010C1" should be enough at least at 16:9 resolutions in Colonial Marines.
However sometimes an additional AA bit is needed for SGSSAA to be applied at all resolutions and aspect ratios.
Hence "0x080010C1" being the profile listed.
 
Hello there, someone know a good bits for Kritika Online on the international version? I tried many but thats bugged many times. The game come out this year for US and EU players too.
 
Atelier Sophie

0x000100C1 - SGSSAA,OGSSAA,HSAA(+-SGSSAA) (Use AA Fix to combat white line artifact on some models and increase sharpness slightly when using SGSSAA. Might not be worth using if not using SGSSAA as GPU usage increases)
Can also enhance in game MSAA.
Game AA will also be affected by NPI settings, even if it it's set to Application Controlled.

Also worth noting is that SGSSAA does affect the UI elements, which is painful because the game uses super compressed low resolution UI elements that are far worse than the PS4 version. So that will likely serve to make them look just a bit worse than they already do.

0x00000041 - MSAA/TRSAA (Game only offers up to 4xMSAA)

NoAA http://u.cubeupload.com/MrBonk/10NoAA.png
In game 4xMSAA http://u.cubeupload.com/MrBonk/ingame4xMS.png
Enhance 4xSGSSAA http://u.cubeupload.com/MrBonk/Enhance4xSG.png
Driver 8xMSAA http://u.cubeupload.com/MrBonk/Driver8xMS.png
Driver 8xMSAA+4xTrSSAA http://u.cubeupload.com/MrBonk/driver8xMS4xTr.png
NPI set to App.Controlled with 4xMSAA in game and 8xSGSSAA set in NPI http://u.cubeupload.com/MrBonk/4xsetingameNPIsetapp.png (Same as enhancing 4xSGSSAA oddly enough)
8xSGSSAA http://u.cubeupload.com/MrBonk/0x000100C18xSG3.png
8xSGSSAA AA Fix http://u.cubeupload.com/MrBonk/0x000100C18xSGAAfix1.png


Zoomed AA fix comparison: http://screenshotcomparison.com/comparison/201631


http://screenshotcomparison.com/comparison/201632
 
Last edited:
You must log in or register to reply here.
Back
Top