Depth buffer detection modifications

Are you using the latest DisplayDepth.fx? In an earlier version the normal derivation was not quite right: only surfaces with high curvature were colored. But that was fixed by Marty McFly at some point. Otherwise I don't know what could cause this.

Daodan wrote: Are you using the latest DisplayDepth.fx? In an earlier version the normal derivation was not quite right: only surfaces with high curvature were colored. But that was fixed by Marty McFly at some point. Otherwise I don't know what could cause this.

Thanks for the info. I was using the one that Reshade downloads automatically. I will look for the latest depth fx shader then.

Edit: I tried the normal fixing the latest version of displaydepth.fx, same results again. I think the game has broken normals. I have to disable mxao then.

If anyone could provide assistance on getting this to work in Planet Coaster I would greatly appreciate it. I know it's a bit of an obscure game though.

Hello guys

Would you please test those dlls (i try another strategy to retrieve the depth buffer before it is cleared):
d3d9_32bits.zip
d3d9_64bits.zip

Some results in RE4 HD:

Just tried it with Mass Effect 3 and it works

Double post, see below

with NO shader active there's still a corruption of the arm+weapon:

Normal Maps are fine:

HL2 (Year Long Alarm mod) seems working fine

lowenz wrote: with NO shader active there's still a corruption of the arm+weapon:

Normal Maps are fine:

Is it possible for you to display the game in wireframe mode (bind the keys to toggle the mode in the settings tab) ?
The wireframe mode only works offline, of course. It displays better with the depth representation of the game, but you can also try with the normal map one.

Video of the issue (some kind of fragment accumulation over the weapon mesh):
-> streamable.com/iliid (you can see the shadow of the weapon model too !)

Depth+Wireframe

Normal Maps+Wireframe (the red lines I've drawn show some kind of "striping" pattern on the weapon that you can see rotating the mouse - don't know if it's relatable to the issue or not)

Thks a lot, very helpful. Maybe i should consider retrieving UT3. Can you test some other games ?

Daodan wrote: Just tried it with Mass Effect 3 and it works

First, thks a lot for your normal maps shader
I tried on Mass Effect 2 with success, so Mass Effect 3 should work as well .

thalixte wrote: Thks a lot, very helpful. Maybe i should consider retrieving UT3. Can you test some other games ?

Of course.
Name some games!

lowenz wrote:

thalixte wrote: Thks a lot, very helpful. Maybe i should consider retrieving UT3. Can you test some other games ?

Of course.
Name some games!

For instance:

• RE4 HD
• Styx: Master of Shadows d3d9
• The Elder Scrolls Oblivion
• Outlast
• Left For Dead 2
• Far Cry
• Crysis d3d9

I know it works for Vanquish, but i have to add a specific option to allow resizing the depth buffer.

About OLD Source Engine games: SiN Emergence (it really needs some MXAO love to avoid the general shading flatness)
It works! BUT there are some problems (don't know if game level related or DB retrieving procedure related)
Look Up! There's (another) part of the level floating in the sky.....

Yes, i have this kind of issue in Half Life 2 in the first level: there is a square at the top left where some meshes appear.

Normally, i only disable the clearing for the depth buffer, not for the rendering, so it should not have this kind of trouble...

I have to investigate why thoses meshes appear in front. Does the meshes also appear in the normal rendering of the game ?

Of course, it only appears if you tick the "Preserve the depth buffer from being cleared" checkbox ?

Only ticking that option!

DB detection/retrieving in Halo CE and Halo 2 is good with "Preserve" BUT there's some issue (similar to the ones of UT3!)
Accumulation bug in Halo CE starting screen (see the white @right):

Far Cry and FEAR are working fine even without "Preserve" (as expected)

Halo CE has another interesting issue:
*if you start the game WITHOUT "preserve" enable and you enable it, all is fine and you got the correct access to the DB
*if you start the game with that option ALREADY enabled in the last run, you got this unexpected occlusion/depth transparency

url images

I will test it without Opensauce now.....