Depth buffer detection modifications

Here are new versions of the d3d9.dll. It should fix depth buffer detection in Outlast as well as in Vanquish and Oblivion (for Oblivion, the sword does not appear, in first person mode, sorry)... For those games, untick the autopreserve checkbox, and select the first depth buffer.

d3d9_64bits.zip
d3d9_32bits.zip

Thanks, will test!

Unreal Engine 3, same old problem (forcing autopreserve too)
See the weapon (and its shadow)

MXAO bleeds (autopreserve enabled) in Halo 2 (see the left weapon/hand)
Well, it's better than the old compenetration problem.

thalixte wrote: Here are new versions of the d3d9.dll. It should fix depth buffer detection in Outlast as well as in Vanquish and Oblivion (for Oblivion, the sword does not appear, in first person mode, sorry)... For those games, untick the autopreserve checkbox, and select the first depth buffer.

d3d9_64bits.zip
d3d9_32bits.zip

Thanks. It seems to work fine in Vanquish.

In the previous dlls, made a little mistake. Should work even better now

d3d9_64bits.zip
d3d9_32bits.zip

Thank you thalixte.

Not having the weapon dawn in the depth buffer is fine. I will Try it out.

thalixte wrote: In the previous dlls, made a little mistake. Should work even better now

d3d9_64bits.zip
d3d9_32bits.zip

Same problems reported before

What game it is ? In all the games i tested, did not see any pb... If MXAO bleeds, this is because i retrieve the main depth buffer, wich sometimes does not include the weapon...

But... maybe... Could you test this one, please:
d3d9_alternative_32bits.zip

The first screenshot is from Unreal Tournament 3 (and the problem is the same as ever, you got it solved last time but it's here now again).
The second one is from Halo 2 (+Project Cartographer): now there's no geometry compenetration (and it's good) but there's the bleeding.

thalixte wrote: What game it is ? In all the games i tested, did not see any pb... If MXAO bleeds, this is because i retrieve the main depth buffer, wich sometimes does not include the weapon...

But... maybe... Could you test this one, please:
d3d9_alternative_32bits.zip

This one solves the bleeding but there's the old geometry issue

And no luck in UT3 (and all the UE3 games I think)

Old january release didn't have this problem with UE3.

And this one ?
d3d9_alternative_32bits.zip

In the january lib, there was a multi depthstencil selection ?

1) Same as the other "alternative":

2) No, or at least I don't remember anything about it

Wow, I can't believe I just found this thread. Been struggling with TriDef in FO76 (not that it is a good game, because it really isn't), and maybe I can give this a try with SuperDepth. Is there a concrete set of instructions anywhere, or do I just try to locate the most recent version and drop it in on top of a ReShade install?

I'm fairly sure you sent me a tweak that works for Project Cars 2 way, way back on Discord. I still have that installed (but with a very old version of SuperDepth).

Playing STALKER Clear Sky atm. According to Games page, Clear sky should have perfect compatibility.
But I cant get the depth buffer to work. MSAA is disabled.

lowenz wrote: 1) Same as the other "alternative":

2) No, or at least I don't remember anything about it

Errata corrige: YES, old 2019 releases got the problem fixed using the "multiple depthstencil":

reshade.me/forum/general-discussion/4083...tion?start=700#32476

That february version is working in UT3
In Halo 2 it gives a flipping DB selection" situation (the DB selection switches between 2 DB every second).

klotim wrote: Playing STALKER Clear Sky atm. According to Games page, Clear sky should have perfect compatibility.
But I cant get the depth buffer to work. MSAA is disabled.

Just tested STALKER Clear Sky, with both the official version, and the last i upoaded (d3d9_32bits.zip, not the alternative on). No problem to retrieve the depth buffer, in both ways (preserve or not). Just a little workaround: rename the d3d9.dll to dxgi.dll, and check that you don't play not online.

thalixte wrote:

klotim wrote: Playing STALKER Clear Sky atm. According to Games page, Clear sky should have perfect compatibility.
But I cant get the depth buffer to work. MSAA is disabled.

Just tested STALKER Clear Sky, with both the official version, and the last i upoaded (d3d9_32bits.zip, not the alternative on). No problem to retrieve the depth buffer, in both ways (preserve or not). Just a little workaround: rename the d3d9.dll to dxgi.dll, and check that you don't play not online.

The steam version?
In settings, what did you set? Dx 10.1?
I did set reshade to dx10+ during install.
Im gonna keep looking hmm...

EDIT:
Okay I Tried all settings, its dx 10 enhanced render that causes the issue. If i use dx9 enhanced render, it works.

Is it possible to get the depth buffer for dx10 render? It has some nice features like the wet surface thing.

klotim wrote:

thalixte wrote:

klotim wrote: Playing STALKER Clear Sky atm. According to Games page, Clear sky should have perfect compatibility.
But I cant get the depth buffer to work. MSAA is disabled.

Just tested STALKER Clear Sky, with both the official version, and the last i upoaded (d3d9_32bits.zip, not the alternative on). No problem to retrieve the depth buffer, in both ways (preserve or not). Just a little workaround: rename the d3d9.dll to dxgi.dll, and check that you don't play not online.

The steam version?
In settings, what did you set? Dx 10.1?
I did set reshade to dx10+ during install.
Im gonna keep looking hmm...

EDIT:
Okay I Tried all settings, its dx 10 enhanced render that causes the issue. If i use dx9 enhanced render, it works.

Is it possible to get the depth buffer for dx10 render? It has some nice features like the wet surface thing.

Just use normal reshade dxgi.

About that, I re-suggest thalixte to take a look to the dxgi part, when he'll got some spare time (DX Human Revolution depth buffer detection doesn't work anymore in D3D11).