D3D8 and depth buffer range problem (?)

  • Posts: 527
5 years 4 months ago - 5 years 4 months ago #1 by lowenz
Max Payne: all-white!
File Attachment:


Chrome:
File Attachment:

and pressing ESC to change menu/exit (with animated scene):
File Attachment:

In-game I can see the SSAO applied only to the weapon model!

Range (->HUD) problem?

Please Log in or Create an account to join the conversation.

  • Posts: 527
5 years 4 months ago - 5 years 4 months ago #2 by lowenz
Up :p

Chrome's problem is clearly game-related, SSAO works perfectly in some scenes, and doesn't work well in others (look at the weapon):
File Attachment:

File Attachment:
(Perfect)

File Attachment:

File Attachment:
(Weapon Only SSAO)

But for Max Payne? Why it's all white?

Please Log in or Create an account to join the conversation.

  • Posts: 3722
5 years 4 months ago #3 by crosire
Depthbuffer in Chrome only contains the weapon model, probably because the game clears it before rendering the FPS hands/weapon. Not much can be done about that. =)
And as for Max Payne: ReShade appearently grabs the wrong one here ...

Please Log in or Create an account to join the conversation.

  • Posts: 527
5 years 4 months ago - 5 years 4 months ago #4 by lowenz
Uhm.....UT 2004:

without weapon:
File Attachment:


same place with weapon (spawn):
File Attachment:


It's exactly the Chrome problem.....so it's not Chrome, it's ReShade, somehow :p

Please Log in or Create an account to join the conversation.

  • Posts: 272
5 years 4 months ago #5 by brussell
Is this kind of problem "fixable" within reshade, or are we doomed to live with it forever...?

Please Log in or Create an account to join the conversation.

  • Posts: 3722
5 years 4 months ago #6 by crosire
In some games the depthbuffer doesn't contain environement information, because the game clears the buffer before starting to render the FPS weapons. In that case one would need to prevent that clear, which is possible, but hard to detect on a generic level (might add a "#pragma" option for it in the future to allow game specific user configuration).
Some games render environment and weapon into different depthbuffers altogether and ReShade's algorithm chooses the one with the weapon. It still needs improvement to choose the one with the most useful data (there are games with more than 30 depthbuffers, so it's no easy task to figure out the best match, though it works quite well already).

So yeah, both these cases are fixable unless there's yet another reason I did not list =)
The following user(s) said Thank You: brussell

Please Log in or Create an account to join the conversation.