qUINT

lowenz wrote:

lowenz wrote: The relationship between the new shaperning filter and CAS porting?

Up!
Please, can you answer?

Same relationship as with any other sharpen filter. Same principle, different execution.

Every sharpen works more or less the same. Subtract a blurred version of the image from the original image. The visual difference between all the available filters is mostly only caused by the blur method and the formula used to determine how much sharpen to apply. Luma Sharpen does it one way, NVIDIA sharpen another way, CAS sharpen yet another way and mine also does it yet another way. The special feature about mine are the depth edge detection to restrict the sharpening to textures only, but every other shader has it's own special recipe that sets them apart.

Marty McFly wrote:

lowenz wrote:

lowenz wrote: The relationship between the new shaperning filter and CAS porting?

Up!
Please, can you answer?

Same relationship as with any other sharpen filter. Same principle, different execution.

Every sharpen works more or less the same. Subtract a blurred version of the image from the original image. The visual difference between all the available filters is mostly only caused by the blur method and the formula used to determine how much sharpen to apply. Luma Sharpen does it one way, NVIDIA sharpen another way, CAS sharpen yet another way and mine also does it yet another way. The special feature about mine are the depth edge detection to restrict the sharpening to textures only, but every other shader has it's own special recipe that sets them apart.

Perfect, thanks!

Hello! Reshade newbee here.

I tried setting up MXAO in multiple games so far and it always ends up looking incorrect. Like a blocky mess, catching every polygon on models. Where I shoud look to fix that?

Have you tried setting DEPTH_BUFFER_IS_INVERTED from 1 to 0 or vice versa in the Preprocessor Definitions?

Fixed it. Depth buffer was fine.

Had to turn on Smoothed Normals. Everything is great now!

You should check this Marty McFly

-snip-

He is copying your work

> PATREON ONLY FILE - DO NOT SHARE

yeah typical matter for a DMCA takedown request to Github. They'll act swiftly. I've reported it as well

Marty McFly wrote:

lowenz wrote:

lowenz wrote: The relationship between the new shaperning filter and CAS porting?

Up!
Please, can you answer?

Same relationship as with any other sharpen filter. Same principle, different execution.

Every sharpen works more or less the same. Subtract a blurred version of the image from the original image. The visual difference between all the available filters is mostly only caused by the blur method and the formula used to determine how much sharpen to apply. Luma Sharpen does it one way, NVIDIA sharpen another way, CAS sharpen yet another way and mine also does it yet another way. The special feature about mine are the depth edge detection to restrict the sharpening to textures only, but every other shader has it's own special recipe that sets them apart.

I have a bug where its sharpening everything altough I have depth buffer available and depth mask enabled as per default.

This is on fallout 4 so it obviously has depth.

Before:


After:


This is on highest sharpening just to show the result.

The config:

[qUINT_sharp.fx]
DEPTH_MASK_ENABLE=4294967295
RMS_MASK_ENABLE=4294967295
SHARPEN_MODE=1
SHARP_STRENGTH=1.000000

Btw is "4294967295" a actual valid value?

klotim wrote: The config:

[qUINT_sharp.fx]
DEPTH_MASK_ENABLE=4294967295
RMS_MASK_ENABLE=4294967295
SHARPEN_MODE=1
SHARP_STRENGTH=1.000000

Btw is "4294967295" a actual valid value?

SO i tried to set to 1 instead and reloaded with no difference.
Also i didn't mention what to look at but look at the sky to be clear.

I have a simple question for Marty McFly: when you are using quint MXAO with GTA 5, what do you personally like to set the various values to? I know a lot of it is personal preference, but I'm also wondering if you use smooth normals, and how your depth buffer is set up.

Sorry if this isn't the right place, I posted this in the Depth Buffer Detection thread too before I saw this one, which seems to be a closer fit

That said, the depth buffer appears to be squashed and misaligned vertically and I can't figure out how to correct it, if there's even anything I can do about it at all. All anti-aliasing is disabled and I'm not running ENB or game monitoring/overlay programs that could potentially conflict.

My question is, is there anything I can do to correct this? New Vegas is the only game I've experienced this with.

Sorry for the double post but I wanted to bump this thread.

I was able to fix the misalignment issue within the DisplayDepth shader via it's "scale" parameter that let me stretch it out to the proper size, but MXAO does not have this option, so the shader is still misaligned.

How likely could a "scale" parameter be added to MXAO?



e: Well, I can confirm that RT shader Beta 0.8 with Reshade 4.3 works as it should in New Vegas.

Hi Marty, in some of my games that are fully depth accessed, the qunit MXAO does not apply any AO effct on the screen, is there something wrong? I have some pics to demonstrate:

imgchr.com/album/YG96e

Hi. In latest reshade update (4.6.0) lightroom stopped working.
it's something on my side, or we need update?

SilentPrayerCG wrote: Hi. In latest reshade update (4.6.0) lightroom stopped working.

\qUINT_lightroom.fx(854, 1): error X4568: 'PS_ProcessLUT': input parameter 'huefactors' interpolation qualifiers do not match vertex shader ones
\qUINT_lightroom.fx(860, 1): error X4568: 'PS_ApplyLUT': input parameter 'huefactors' interpolation qualifiers do not match vertex shader ones
\qUINT_lightroom.fx(874, 1): error X4568: 'PS_DisplayStatistics': input parameter 'huefactors' interpolation qualifiers do not match vertex shader ones

it's something on my side, or we need update?

Download the latest version of the shader from the github links in the first post.

I've checked github before, but it month year old, thought i already have it, apparently not.
Now it's it work OK, thanks!

Hi, I encountered a problem of strong flickering when turning on rtgi in some games, regardless of the shader settings, anti-aliasing and the frame depth buffer, tell me what the problem may be, Because of the resolution (2560Х1440)?

the screenshot is not noticeable, but the whole picture flickers

Hey, Marty.

I've been trying to reduce the Bloom Scene Exposure Bias so that I can find the sweet spot for the white point, but the exposure will only change when it goes lower or higher in increments of 1, otherwise it won't change at all. Because of this, I end up having the white point be a little too bright or a little too dark in poorly lit areas.

imgur.com/a/HpUl9dH

Hi, Marty.

Thank you so much for your work.

There's a funny problem with Euro Truck Simulator 2.
During the game MXAO works fine, but when accessing the main menu, the shader is always displayed upside down. This only happens in the menu, is there a solution?

For example, some code that says "when pressing ESC, invert" "when pressing ESC again, invert again".

I think I don't understand what lightroom is supposed to do or either something went wrong. Whenever I enable it, I get a green as hell screen.