Marty McFly's Ambient Obscurance (MXAO) with IL

I managed to make MXAO work at my native resolution through "brute force", and polygons now get smoothed properly with smoothed normals on. Maybe scale issues?

Marty is MXAO 2.0 included in Reshade 3.0.6 or do we need to DL this and move it over to reshade ourselves?

You can update shaders with ReShade's setup tool and will get MXAO 2.0.

crosire wrote: You can update shaders with ReShade's setup tool and will get MXAO 2.0.

Crosire would you mind expanding on that? I just recently started to use 3.0 so I am still a little new to the features. When I do a fresh install on a new game it asks if I want to download the shader packs, and I always agree. Are you saying that the install tool can be used to download updated versions of those shaders, should they be updated after the initial install?

Again I just recently started using 3.0 so I am pretty sure I have already been using MXAO 2.0, just want to be sure

Just use the same tool to "reinstall" ReShade (it will ask if you want to overwrite, click yes). It will then go ahead and update the shader files. MAXO has been officially updated in the repository 23 days ago.

How can I prevent the issue of mxao making UI elements transparent like in this screen (Ys Origin):

I'm using ReShade 3.0.6 with default mxao settings.

UI is not "transparent" there, it's only that the UI is not visible in depth buffer so AO is generated from geometry data behind the UI and applied on top of the UI. Nothing to be done about that except static mask.

What mean tooltip of IL parameter "add SSIL in preproccesor section"?
What exactly i should add? I can't find anything in google about that.

Download MXAO 2.0 from the 1st page of this thread and read the PDF that comes with it. I explained there how to enable IL in the preprocessor section of the UI, with pictures

Marty McFly wrote: Download MXAO 2.0 from the 1st page of this thread and read the PDF that comes with it. I explained there how to enable IL in the preprocessor section of the UI, with pictures

Oh. I'm downoaded it from github.
And there is pdf included.
Ok, thx!

Well i managed add IL in preprocessor section.
Checked it on new 1070 card, in Dead Space 2.

Works fine, with 60 fps. Only sad thing, that it effect renders over final game image.
Of course i understand how it works, and it need more deep integration in certain game to make draw AO before some fog or particles.

If I had deeper engine integration and access to more things, I could do some crazy shit

We need this: www.quora.com/What-does-Gbuffer-pass-Gbu...as-depth-target-mean

Please make this happen

???

You're asking for a buffer that holds depth and some other info. And then? What has this to do with MXAO? MXAO already uses a G-Buffer of some sort, it has a dedicated normal texture (alpha channel for AO sample jitter) and a linear scaled depth texture....?
Do you mean, having a G-Buffer available globally? Not useful, because different shaders might have different requirements, like the normal generation of MXAO and PiratyKitty's shaders for example are entirely different. If you need such data, create it yourself in your shader, just like I do in MXAO. You can't do much else besides adding normal buffer to the default set of color and depth.

Okay... To be honest, I would LOVE to see Reshade become an ENB alternative... What we need is to inject shaders into the graphical processors, instead of intercepting the backbuffer, and overlaying them. Having the ability to transfer shaders from game to game with little to no issues is nice, and we can still maintain that aspect; However, I would love to have the option to go deeper into the engine if I so choose. This is what I hope comes of the source code being openly available. But alas, we stand here 4 months later and still only 3 contributers... With time, I hope!

P.S: Sorry for the confusion, I was referencing this entry by Unity: docs.unity3d.com/Manual/GraphicsCommandBuffers.html
(Which might still be useful for Unity games, IDK...)

I just wanted to say thank you for a great tool. I'm very new to Reshade and have enjoyed seeing what's possible with Reshade 3.0 over the last week or so.

I have not encountered any issues with MXAO in those titles I have tried where access to the depth buffer has been available, but I am using the shader in a configuration I have not seen mentioned elsewhere. I therefore thought I'd share it in case it is useful to anyone or inspires new features.

Nothing fancy - all I'm doing is running MXAO twice. My issue with the AO produced by default was that I could either run the shader with a large sample radius, which produced a very pleasant shadow effect on larger objects such as buildings, or I could run it with a smaller sample radius to add AO to smaller, more detailed objects. I'm only interested in screenshots, so the FPS hit doesn't bother me. Anyway, sample images below.


Of course, if there is a way to get a similar effect in one pass that I have overlooked, please let me know!

The problem with running MXAO twice is that all data (normal texture, linearized depth texture, color texture mipmapped) and the blur & combine passes run twice. It's mor efficient to just run the AO generation pass twice. I might add something like this but the problem is that it complicates the shader more and more, the more values are added. What's reasonable is a second radius param and maybe a sample count param.

That would be great if possible.
I often find myself wanting to have 2 different radius sizes and was doing that all the time before when you could run 2 AO methods simultaneously. I did it even recently in rsh 2 when we had to "plug" MXAO in Reshade.fx Ofc, the performance impact was immense.

Do you play on adding some sort of HDR output support? I just tried running MXAO (resahde 3) in Mass Effect Andromeda in HDR mode and most of the bright tones get cutoff, like you applied some sort of tonemapping or filmicpass to it.
It could be a question for Crosire tho...

I thought ReShade color input was LDR only?

Marty McFly wrote: I thought ReShade color input was LDR only?

It is.