Marty McFly's Ambient Obscurance (MXAO) with IL

Performance makes it not really applicable.

Marty McFly wrote: Performance makes it not really applicable.

Can high end parts like a 1080 handle it?

Hello Marty. I've known your work for a few years, so it's really an honour to finally address you.

First, thank you so much for your time and effort on making and constantly improving your effects.

Now, I'm building a nice preset (Reshade 3.0.5) for World of Warcraft and I've experimented with MXAO. It looks stunning and really adds depth to foliage, building and various models. However, the effect seem to randomly flicker (switch on and off) every once in a while. It wouldn't be so intruding if it weren't so apparent when it happens.

Do you have any idea what might cause this? I've read your original comment and tweaked a few things with no luck. I would really love to have a stable MXAO.

Marty explains it here: reshade.me/forum/shader-troubleshooting/...n-dark-souls-3#18477

World of Warcraft is an online game, so every effect that uses the depth buffer won't work properly (like MXAO)

Thank you so much for responding.

Ah! That would explain it, I guess. There's no way to to bypass or otherwise fix this then? I'm assuming every game with an online component (Battlefield series, for instance) would suffer from the same problem?

Turning off MXAO when you play online is the quick solution

From one Marty to another -- did you get ever get the latest MXAO working with Reshade 3.0?

We needs it! [shush Gollum, shush]

Yeah I did but I kinda forgot about ReShade when ENB for Skyrim SE came out. Dx11 is cool

Marty McFly wrote: Yeah I did but I kinda forgot about ReShade when ENB for Skyrim SE came out. Dx11 is cool

Not to be a bother, but is the 3.0 compatible version available for download? I'm a fan of this shader and have been looking forward to the update.

I guess that explains why MXAO doesn't work at all with American Truck Simulator? But the shader file says "only for ReShade 3.X"?

As soon as I turn on MXAO, the game just stop rendering but it's still running fine, just without graphics, stuck at where the last frame was.

Then don't experiment. With ReShade 3.0, there are strange things going on...

Eh, not really trying to experiment but I guess I'll wait until no more strange things are going on.

Well, seems like I cannot continue MXAO development.
For some reason, newer MXAO builds make the application crash (which MUST NOT happen). I know the respective code parts (SSIL in loop) but not why those cause issues - either a shader compiles or not.
Crosire once said that it was a driver bug and he filed a bug report. Now this shit happens again and it's a bitch to debug because sometimes it crashes the app, sometimes not. Only on D3D11 though. No restructuring of the code works, I'm out of ideas.
Only idea I see is cutting IL functionality entirely.

EDIT: There is a way to keep SSIL but it'd require to remove UI vars for enabling/disabling IL and backface check, and removing boundary check entirely.

Remove IL and done, honestly, I do not like IL, I've never used and will never use, killer performance and takes away all effect of AO ..

Then people must switch to inferior alternatives if they want IL. And it all depends on your configuration if AO is gone or not - on fast cards IL is not noticeable except for high sample counts.

If you make a separate IL from AO, will still crashing?

AO and IL belong together, you can't calculate IL without the occlusion data.

Marty McFly wrote: AO and IL belong together, you can't calculate IL without the occlusion data.

One more solution: make two shader techniques, both under the MXAO shader .fx file -- one hard has IL hardcoded on, the other has IL hardcoded off. People can choose which once to use. Profit!!!

Edit: or if having large swathes of code duplicated in a single file feels wrong or impacts performance, just make two separate .fx files.

Well, I chose to make it toggleable per preprocessor. Different techniques or files will usually end up in poor configs where people use both.

Martigen wrote:

Marty McFly wrote: AO and IL belong together, you can't calculate IL without the occlusion data.

One more solution: make two shader techniques, both under the MXAO shader .fx file -- one hard has IL hardcoded on, the other has IL hardcoded off. People can choose which once to use. Profit!!!

You can disable IL by setting the line #define bMXAOIndirectLightingEnable to 0.
Looks like it is off by default.