HBAO+ Compatibility Flags Thread

MXAO in the new Reshade is MUCH faster plus it has sliders to adjust it exactly to your liking! It's working really well in Dead Rising.

 

Will have to give it a shot.

 

Any luck on Mafia 3 or Shadow Warrior 2?

 

hey I'm new with this and having problems .. it ses in the instructions to copy the dll file to the game directory either c:\Windows\SysWo64\nvd3dum.dll or c:\Windows\System32\nvd3dumx.dll but I have looked in both and there is no such dll file. what do i do? the game i want to use is Tales of Zestiria.

 

If you are using Windows 10. Those files have been removed unfortunately and aren't available to modify.

No one knew whether it was a driver update that did it, or whether it was teh W10Anniversary update.

 

ok.so is there any other way? how do i get it to work on windows 10?

 

anyone??

 

try older drivers, like this -> http://www.geforce.com/drivers/results/102997

 

o..if it meens having to downgrade drivers. id rather not..i try to stay uptodate with my drivers.

 

Then unfortunately you are SOL. They've taken away our only way to fix Nvidia's errors in official flags and make custom ones that work the best we can get for games that won't work with existing ones.

It's a shame.

Some people asked the Reshade folks to turn HBAO+ into a shader for it at one point, but they didn't out of fear because of the EULA/Licensing on the source which is freely available to just about anyone on github now. I've got a copy on my harddrive in fact.

I wish I could talk to someone at NV personally about using the source to make a HBAO+ utility injector of sorts using the source. (That could also black list certain games to keep it from being used to cheat, like in Counter Strike)
Of course, I know nothing about programming really. But it'd be a really great thing.

 

It's ironic because, Marty McFly, the guy who created MXAO, discovered that NVIDIA had copied some of HIS code for use in their ANSEL tech. He was really cool about it and they eventually credited him but God forbid if the tables were turned. Not doubt lawyers would've been involved.

 

thats really sad and pathetic.

 

Whoah. Typical corporations.

What exactly did they use?
NVM I see.
https://www.overclock3d.net/news/gp..._solution_was_allegedly_stolen_from_modders/1 :banana:
https://www.facebook.com/MartyMcModding/posts/1122337964470822

 

looking into fallout 4 flag someone posted up 0x00060000 as working so i tried this on skyrim special edition from what i have seen of right now it works without flicking like the lords of the fallen flag does to test if its working stand near some grass with it off then turn it on easiest way to check no bleeding found of yet but fps hit is pretty big

 

Might be a better idea just to use the ENB AO mods maybe. Might mesh better and perform better too in the case of Skyrim.

 

yea i get like a 30fps hit depending on where im looking on with this guess for right now mxao from reshade it is till boris gets ssao working in it

 

I find it silly, why Bethesda didn't just implement ingame HBAO+ like in Fallout 4.
Typical unfinished rush job IMO.

 

New reshade 3.0 has custom MXAO, works quite good and highly tweakable real time, worth a try for those games that have driver HBAO issues.

(tested in SilentHill Homecoming)

Code:

[MXAO.fx]
fMXAOAmbientOcclusionAmount=0.920000
bMXAOIndirectLightingEnable=0.000000
fMXAONormalBias=0.800000
fMXAOIndirectLightingAmount=4.000000
iMXAOSampleCount=32.000000
fMXAOIndirectLightingSaturation=1.000000
fMXAOSampleRadius=2.500000
bMXAOSmartSamplingEnable=1.000000
fMXAOSampleRandomization=1.000000
bMXAODebugViewEnable=0.000000
bMXAOBackfaceCheckEnable=1.000000
fMXAOBlurSharpness=1.000000
fMXAOBlurSteps=3.000000

 

Well, I did some testing for Skyrim Special Edition and I found that 0x000C0000 and 0x000E0000 both actually work very nicely ... except for not at all in interiors >.<

The only other flag that seems to work is the aforementioned 0x00060000, but it looks kinda nasty (dark blobby).

I don't suppose there are any tweaks that could address an issue with a flag such as 'does not work for interiors'...?

 

Doubtful in my experience.
Some games and certain HBAO+ flags suffer from this issue, and finding another flag is typically the only way to go

BTW we can add Lichdom: Battlemage to the "not recommended" HBAO+ list.
Only "0x00140000" gives a decent effect both indoors and outdoors in this CryEngine 3 game, but unfortunately it bleeds through fog and occasionally flickers in caves etc.