HBAO+ Compatibility Flags Thread

I haven't tested it yet so can't say.

This! I'm using MSI Afterburner which comes with RT Statistic Server.

 

I spoke to soon, when I run the game at 1080p (for stable fps with Reshade) I get flicker, when I run at higher resolutions with DSR I don't.

 

Try disabling Reshade then.
When doing this type of testing it is important to compare apples-to-apples, so to speak.

 

Anyone was successful in using TPP HBAO+ flag in Ground Zeroes?
People report it works, but i can't really see any difference.

Also MFAA doesn't seem to do anything, i assume that there's no MSAA in GZ so MFAA has nothing to work on.

 

It might just be subtle. And it will be hard to tell if you don't disable the built in SSAO. It might depend on resolution/aspect ratio too.

MFAA won't do anything without MSAA. In game, forced or otherwise. And it only works at a minimum of 40fps

 

Yeah, AO seems to be working in both but it's WAY more subtle than native implementation.
Though it has a bug where closing the camera up on certain objects makes your FPS tank to like 15. Had it happen few times during cutscenes.

TPP doesn't seem to be very challenging to a 970, i guess i may ultimately run SSAA or just use DSR to reduce jagging.

Though i swear to god, native FXAA seems to be doing nothing in this game.

 

That's because the built in SSAO is a terrible, low quality overtly strong piece of crap. /shrug. Like almost straight out of Crysis bad. I wish they had just implemented HBAO+ Natively with options for being strong or subtle (As FFXIV does) so people who like it strong can have it.

FXAA also does stuff. The problem is MGSV has ridiculously aliased output from every possible source. With all the ugly low precision dithering for hair, foliage adding on top of it.

 

Yeah, i've noticed transparency dithering few days ago. Seems a thing for Japanese developers, FF XIV uses it too.

 

Current HBAO setting that can be set in driver profile is just a number for four other settings, that hard coded in driver dll.
By changing parameters in driver dll, you can get different HBAO results.

No AO
0x00000028
0x00000028 mod 1
0x00000028 mod 2
0x00000028 mod 3
0x00000028 mod 4
0x00000028 mod 5
0x00000028 mod 6
0x00000028 mod 7

 

WHAT IS THIS WIZARDRY GOOD SIR?

Are you Hexediting to achieve this?

Which .dll specifically?

I would very much like to look into this!

 

Wizardry

 

For DX9
C:\Windows\SysWOW64\nvd3dum.dll

HEX-values table:

Spoiler

0x00000001
4E 91 20 18 00 00 28 18 A5 60 68 0A 00 00 00 00

0x00000002
A2 90 00 18 00 00 14 18 90 40 BF 0A 00 00 00 00

0x00000003
5E D0 00 18 00 00 16 18 75 A0 6F 07 00 00 00 00

0x00000004
26 B2 80 18 00 00 B0 18 A5 60 6E 03 00 00 00 00

0x00000005
26 B2 80 18 00 00 B0 18 A5 60 6E 03 00 00 00 00

0x00000006
16 30 00 00 00 00 00 00 A5 A0 6F 05 00 00 00 00

0x00000007
16 B0 03 18 00 00 02 1C A5 A0 6F 05 00 00 00 00

0x00000008
16 B0 03 18 00 00 02 1C A5 A0 6F 07 00 00 00 00

0x00000009
16 30 00 00 00 00 00 00 A5 A0 6F 05 00 00 00 00

0x0000000A
16 90 01 58 00 00 00 5C A5 A0 6F 07 00 00 00 00

0x0000000B
16 B0 03 18 00 00 02 1C A5 A0 6F 05 00 00 00 00

0x0000000C
13 90 00 18 00 00 16 18 A5 A0 6F 05 00 00 00 00

0x0000000D
53 30 00 00 00 00 00 00 A3 A0 BD 08 00 00 00 00

0x0000000E
DE 80 80 18 00 00 96 18 95 A0 7F 0B 00 00 00 00

0x0000000F
DA 90 80 18 00 00 96 18 B5 A0 68 08 00 00 00 00

0x00000010
AE 98 02 18 00 00 02 1C 83 A0 4F 0A 00 00 00 00

0x00000011
56 98 00 18 00 00 00 1A 75 A0 BF 05 00 00 00 00

0x00000012
16 B0 03 18 00 00 02 1C A5 A0 6F 05 00 00 00 00

0x00000013
AE 38 00 00 00 00 00 00 B3 A0 6F 0A 00 00 00 00

0x00000014
16 30 00 00 00 00 00 00 A5 20 6F 05 00 00 00 00

0x00000015
26 B2 80 18 00 00 B0 18 65 30 4F 03 00 00 00 00

0x00000016
AE 90 02 18 00 00 02 1C B3 A0 6F 05 00 00 00 00

0x00000017
2E 93 00 18 00 00 14 18 93 90 BF 0A 00 00 00 00

0x00000018
2E 93 20 18 00 00 20 18 85 90 B8 0B 00 00 00 00

0x00060019
16 B0 80 18 00 00 82 18 A5 A0 6F 0A 00 00 00 00

0x0000001A
16 90 80 18 00 00 B0 18 A5 70 BE 05 00 00 00 00

0x0000001B
2E 93 00 18 00 00 00 1C 85 60 BF 05 00 00 00 00

0x0000001C
9E 98 00 18 00 00 08 18 75 A0 BA 0A 00 00 00 00

0x0000001D
16 90 00 18 00 00 36 19 B1 A0 BF 08 00 00 01 00

0x0000001E
1E 40 00 00 00 00 00 00 95 A0 68 09 00 00 00 00

0x0000001F
16 30 00 00 00 00 00 00 A5 50 96 0C 00 00 00 00

0x00000020
EB 93 00 18 00 00 16 18 A3 90 9F 0B 00 00 00 00

0x00000021
EB 93 00 18 00 00 00 18 A4 80 AF 0B 00 00 00 00

0x00000022
13 50 00 00 00 00 00 00 84 90 76 0C 00 00 00 00

0x00000023
22 90 00 18 00 00 02 18 A3 A0 BE 0B 00 00 00 00

0x00000024
AA 90 02 18 00 00 02 1C A4 A0 BF 0B 00 00 00 00

0x00000025
EF 93 02 18 00 00 02 18 A5 A0 9E 0B 00 00 00 00

0x00000026
A6 90 40 18 00 00 40 18 A3 A0 6F 09 00 00 00 00

0x00000027
DA 80 00 20 00 00 00 28 95 A0 A8 08 01 00 00 00

0x00000028
22 B2 80 18 00 00 B0 18 95 30 AE 0B 00 00 00 00

0x00000029
26 B2 80 19 00 00 B0 19 A5 60 4E 05 00 00 00 00

0x0000002A
16 B0 03 18 00 00 02 1C A5 40 6E 09 00 00 00 00

0x0000002B
5E 83 00 18 00 00 00 1C 23 80 7D 0B 02 00 00 00

0x0000002C
16 B0 03 18 00 00 02 1C 85 A0 6F 05 00 00 00 00

0x0000002D
2E 93 00 18 00 00 16 18 A3 90 78 0B 00 00 00 00

0x0000002E
16 20 80 18 00 00 80 18 83 A0 2F 05 04 00 00 01

0x0000002F
AA 98 80 18 00 00 B4 18 A3 A0 6F 05 00 00 00 00

0x00000030
AE A8 00 18 00 00 00 1C A4 A0 7F 0B 00 00 00 00

0x00000031
2E 93 00 18 00 00 00 18 85 60 B8 09 00 00 00 00

0x00000032
16 A0 C8 04 00 00 FA 05 75 60 A8 01 03 00 00 00

0x00000033
12 80 03 10 00 00 20 10 A5 50 96 2F 00 00 02 00

0x00000034
AE 80 02 10 00 00 06 10 83 90 78 09 00 00 00 00

0x00120035
1E 80 80 18 00 00 B0 18 43 10 41 07 00 00 00 00

0x00000036
DA 80 00 20 00 00 00 28 95 A0 A8 08 01 00 00 00

0x00000037
26 82 80 00 00 00 80 00 73 30 6D 03 00 00 00 00

0x00000038
26 B2 80 18 00 00 B0 18 65 10 7E 05 00 00 00 00

0x00000039
1E 80 10 19 00 00 B0 1B 85 60 48 07 00 00 00 00

For example, setting 0x00000028 contains
22 B2 80 18 00 00 B0 18 95 30 AE 0B 00 00 00 00

This is a group of four values:
22 B2 80 18 - Insertion logic bits
00 00 B0 18 - Insertion pattern match mask
95 30 AE 0B - AO parameter bits
00 00 00 00 - ??? (Debug bits?)

AO parameter bits:
9 - ? AO FadeOff or Depth
5 - ???

3 - ? Another FadeOff or Depth
0 - ???

A - ? Directions
E - ? Samples

0 - ? Sharpness
B - Strength

By manipulating AO parameter bits, we can achieve various AO results.

0x00000028
22 B2 80 18 00 00 B0 18 95 30 AE 0B 00 00 00 00

0x00000028 mod 1
22 B2 80 18 00 00 B0 18 95 30 1E 0B 00 00 00 00

0x00000028 mod 2
22 B2 80 18 00 00 B0 18 95 30 5E 59 00 00 00 00

0x00000028 mod 3
22 B2 80 18 00 00 B0 18 F5 A0 9E E5 00 00 00 00

0x00000028 mod 4
22 B2 80 18 00 00 B0 18 C5 40 BE 33 00 00 00 00

0x00000028 mod 5
22 B2 80 18 00 00 B0 18 FF FF 22 22 00 00 00 00

 

We got a Badass Reverse Engineer here
Thanks man!

 

This is great for fine-tuning already working flags to iron out issues (like distance bleeding for 2F) but it probably won't do much for games with fundamental problems like flickering or extensive bleeding.

Guzz, did you try to tinker with pattern match mask values?

 

Very interesting find, Guzz
Did you try this with DX11 HBAO+ profiles?
The official Crysis 3 flag "0x000E0000" bleeds through water and doesn't apply AO outdoors, perhaps something can be done about this?
"0x00070000" solves this issue, but then again doesn't work indoors :wanker:

 

Thank you so much for this finding Guzz! :cheers:

Results are phenomenal, official flag for Dead Space 0x0000000F, subtle effect IMO. Simply changing that string increased effect strength without any drawbacks.

No AO
DA 90 80 18 00 00 96 18 B5 A0 68 08 00 00 00 00 Default
DA 90 80 18 00 00 96 18 B5 A0 68 0E 00 00 00 00 Modded nvd3dum.dll

 

Head esplode...
Sucks that we would have to edit it each time and revert it when needed.

Though this seems to open up all kinds of new possibilities! And maybe makes official flags make more sense (Since they always seem to be sequential in numbering)

Though I don't have the time to really test much these days.

 

We need a custom hex-edit tool to speedup the tweaking process

 

For DX11
C:\Windows\SysWOW64\nvwgf2um.dll (32-bit)
C:\Windows\System32\nvwgf2umx.dll (64-bit)

HEX-values table:

Spoiler

0x00010000
F1 31 00 88 C1 60 7E 0E 00 00 00 00

0x00020000
F6 35 00 89 65 60 7F 0C 00 00 00 00

0x00030000
77 01 00 89 35 60 BF 01 00 00 00 00

0x00040000
76 01 80 88 35 60 6F 05 00 00 00 00

0x00050000
76 01 80 88 35 60 6F 05 00 00 00 00

0x00060000
F6 30 80 89 83 70 8C 0E 00 00 00 00

0x00070000
7E 01 00 88 82 50 87 0A 00 00 00 00

0x00080000
70 01 80 89 35 60 BF 00 00 00 00 00

0x00090000
FE 31 80 89 73 80 8C 0C 00 00 00 00

0x000A0000
77 01 80 81 35 60 BF 05 00 00 00 00

0x000B0000
72 01 00 88 45 60 9F 05 00 00 00 00

0x000C0000
FA 31 80 89 85 60 8C 0A 00 00 00 00

0x000D0000
F6 35 00 88 75 60 6D 04 00 00 00 00

0x000E0000
FE 31 80 89 63 80 8C 0C 00 00 00 00

0x000F0000
76 58 00 82 73 40 5D 07 01 00 00 00

0x00100000
00 B3 03 82 45 60 9F 05 00 00 00 00

0x00110000
20 00 80 81 73 40 5D 07 00 00 00 00

0x00120035
76 01 00 81 43 10 41 07 00 00 00 00

0x00130000
76 10 00 82 73 40 5D 0E 00 00 00 00

0x00140000
26 01 00 81 63 50 86 0A 00 00 00 00

0x00150000
00 10 02 82 22 60 FF 0F 00 00 00 00

0x00160000
76 10 00 82 77 30 53 0E 02 00 00 00

0x00170000
06 10 00 82 65 30 7D 0B 00 00 00 00

0x00180000
08 00 00 99 A3 70 97 0A 00 00 00 00

For example, setting 0x000E0000 contains
FE 31 80 89 63 80 8C 0C 00 00 00 00

This is a group of three values:
FE 31 80 89 - Insertion logic bits
63 80 8C 0C - AO parameter bits
00 00 00 00 - ??? (Debug bits?)


NoAO

0x000E0000
FE 31 80 89 63 80 8C 0C 00 00 00 00

0x000E0000 mod 1
FE 31 80 89 C1 80 A4 0F 00 00 00 00

 

So with this logic is it at all possibly to get AO into wildstar? It's free to play now, i'm wondering if anyone has found anything usable? It would really make this game look that much better imo.